Customer testimonal API Program Lessons learned
0 likes•455 views
The document outlines the lessons learned from a digital API program led by Gunther Bonnard at Firmenich, which focused on overcoming integration challenges through a structured governance framework and a pilot phase. Key aspects include the selection of a suitable API platform, the importance of training and communication, and the establishment of defined integration patterns. The project emphasized improving synchronization between teams and creating a clear API roadmap to enhance overall data management.
Customer testimonal API Program Lessons learned
- 1. 1 Fundamentally Digital API Program Lessons learned Gunther BONNARD Director, Enterprise Architecture
- 2. Firmenich – key figures 2 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
- 3. 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
- 4. 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
- 5. 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
- 6. Project phasing Governance definition Implementation Training Pilot Change management
- 7. Governance - Zoom RACI TARB EnterpriseArchitect SolutionArchitect IntegrationSpecialistSecurityOfficerSecuritySpecialist APIPlatform Adm inistrator APIPlatform Specialist BusinessOwnerBackendOwnerBackendDeveloperBusinessOwnerApplicationOwner ApplicationDeveloperSystem 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
- 8. 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
- 9. 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
- 10. Conclusion