API Program Lessons learned
0 likes437 views
Firmenich conducted an API management project to improve integration and reduce data duplication, resulting in a well-defined API platform and better cooperation among teams. The project comprised a three-month lifecycle with a focus on governance, training, and communication, leading to enhanced perception of integration architecture. Key lessons included the importance of pilot phases and defining clear roles and responsibilities.
API Program Lessons learned
- 1. 1 Fundamentally Digital API Program Lessons learned Gunther BONNARD Director, Data Architecture & Governance at Firmenich Jérémie DENOYER API Management Consultant at SmartWave
- 2. 2 Context API Management Project Outcomes & Lessons learned AGENDA
- 3. 33 CONTEXT
- 4. Firmenich – key figures 4 1895 Founding year 3.7 Billion CHF Revenues #1 Privately Owned Perfume & Taste Company #1 in Fine Fragrance #1 in Ingredients 370 Million CHF Invested in R&D 3,100+ Patents 63 Countries Nobel Prize 1939 40% Female Senior Leadership
- 5. Context •Low integration •Data duplication / synchronization •Few existing API, “newbie” •No control on interfaces Current Situation •Service Oriented Architecture •Central team for Integration •Expose data •API-ation of the IT industry •Manage interfaces with tooling Drivers
- 6. Context •Low integration •Data duplication / synchronization •Few existing API, “newbie” •No control on interfaces Current Situation •Service Oriented Architecture •Central team for Integration •Expose data •“API-zation” of the IT industry •Manage interfaces with tooling Drivers
- 8. Project lifecycle • 3 months • 3 bidders selected (Webmethods, Apigee, Axway) • PoC • Demo RFP Process • Solution capability : architecture oriented • Commercial relationship • Quality of the answer – fit to purpose • Cost • Local supplier Selection (winning) criteria • 6 months • 4 phases • Involvement of security and architecture team Project
- 9. Project phasing Governance definition Implementation Training Pilot Change management
- 10. Axway API Management Solution CREATION Services Applications Data Backend Services Messaging BACK-END API Creation Appcelerator Mbaas API Builder REST Analytics UX Multi-canal Cloud and on premise Partners CONSUME Application Development Titanium - SDK REST, SOAP CONTROL REST API Management API Gateway API Portal API Manager REST API Gateway APIs REST, SOAP
- 11. INTERNAL Platform - Zoom API Manager API Manager API Portal LDAP API GatewayAPI Gateway DMZ Microsoft Azure AD Analytics ESB ESBInternal Systems
- 12. Governance - Zoom RACI TARB Enterprise Architect Solution Architect Integration Specialist SecurityOfficerSecuritySpecialist APIPlatform Adm inistrator APIPlatform Specialist BusinessOwnerBackend Ow ner Backend Developer BusinessOwner Application Ow ner Application Developer System Adm inNetworkAdm in OperationalSupportSpecialist Architecture Application Team(s)Backend Team(s)API Platform InfraSecurityActivities TARB Ops GOVERN Define default API Quota C A R I Publish API C A I R I Confirm API publication (optional) C A / R C C I Validate to grant to Org A /R Grant to Org I R A Validate to deprecate API A / R Deprecate API R A I Validate to decomission API A / R Decomission API R A I Architecture Application Team(s)Backend Team(s)API Platform InfraSecurity
- 13. Communication Kit for API Provider
- 14. Communication kit for API Consumer
- 16. Outcomes API platform with API developed during the pilot phase API organization : people, processes, governance, KPI Integration pattern clearly defined and shared Better perception of integration architecture Better synchronization between security, integration and architecture team
- 17. Lessons learned Whatwassuccessful? WhatIwilldodifferently? • Definition of Governance • Pilot phase • Training • Communication • Tandem Axway- Smartwave • Integration patterns • Scope of pilot • Local PM • API roadmap definition in the project • Use case during the training on pilot
- 18. Conclusion
Editor's Notes
- #5: Année de foundation 1895 63 countries NObel Prize 1939 e croate Lavoslav Ružička alors privatdocent à l'École polytechnique fédérale de Zurich. En 1939, celui-ci reçoit le prix Nobel de chimie pour ses travaux16.
- #6: Low security
- #7: API-ation of the IT industry Need fondation for data monitization
- #10: Importance du pilote et phase de gouv Securité 2 API : une externe, une interne avec des niveaux de sécu différente Next steps : change – API roadmap => Decomissionning existant
- #13: RACI Process diagram Custom with role into the organization => Feasibility : do we have the resource and skills to do that ?