Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Apidays New York 2024 - Driving API & EDA Succe...

Apidays New York 2024 - Driving API & EDA Success by Marcelo Caponi, Danone

Driving API & EDA Success: Comparing CoE & C4E Models for Organizational Enablement
Marcelo Caponi, Global Product Manager - API & Integration at Danone

Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024)

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/

apidays

May 14, 2024
Tweet

More Decks by apidays

Other Decks in Technology

Transcript

  1. DRIVING API & INTEGRATION SUCCESS COMPARING COE & C4E MODELS

    FOR ORGANIZATIONAL ENABLEMENT MARCELO CAPONI PRODUCT MANAGER API & INTEGRATION DANONE
  2. 2 AGENDA AGENDA 1. DANONE CONTEXT 2. COE VS. C4E

    3. STARTING A C4E 4. C4E KPIS
  3. ABOUT DANONE 4 ABOUT DANONE 80% of the revenue come

    from interfaces! €28B Annual Revenue 100K Employees 120 Prescence in Markets
  4. CHALLENGES 2 YEARS AGO More than 1K of point-to-point integrations

    difficult to reuse. Integration teams working in silos in different integration platforms. No common best practices and governance in place. INTEGRATIONS AT DANONE 5 INTEGRATIONS AT DANONE MAIN GLOBAL PLATFORMS
  5. ABOUT DANONE 7 INTEGRATION CENTER OF EXCELLENCE (COE) Delivery Model

    Project Focused Governance Strict & Rigid Consumption Model Centralized, request- based through projects Assets EA patterns, Architecture Docs, Security Consumers Central IT Ownership Central IT Enablement Complex, document- driven Domain Expertise Centralized
  6. ABOUT DANONE 8 INTEGRATION CENTER FOR ENABLEMENT (C4E) Delivery Model

    IT builds capability, LoBs deliver projects independently Governance Governed through APIs, self-serve access Consumption Model Centralized, request- based through projects Assets APIs, Templates, Accelerators, Best Practices Consumers LoB, App Dev, ISVs, SIs Ownership Central IT owns the platform, access is self-service Enablement Evangelism, API communities, self-pace trainings Domain Expertise Decentralized, Federated
  7. INSERT SECTION TITLE HERE 9 VISION OF FEDERATED API PLATFORM

    TEAM “By 2026, 90% of organizations with APIs will have a federated team responsible for quality of their APIs”
  8. INTEGRATION PRODUCT TEAMS EMPOWERED BY A C4E 15 DELIVERY TEAMS

    2024 DEV FACTORY SUPPLY C POD PORTFOLIO INTEGRATION ARCHITECTURE DELIVERY PLM POD HR POD IBM MIG. POD SFDC POD API ENABLEMENT C4E POD = Product Oriented Delivery
  9. 18 KPIS TO BE DELIVERED IN THE DASHBOARDS KPIS The

    ambition is to build a “Single Pane of Glass” – Ideally on ELK SINGLE PANE OF GLASS It concentrates all KPIs on a single place It’s fully automated (ideally on ELK) KPIS Metric Domain Type Licensing vCores utilization per BG and environment Capacity # of APIs per environment (DEV/SIM/PROD) Capacity # of APIs per type (exp, proc, sys) Capacity # of APIs per domain (commercial, manufacturing, …) Reuse # of assets available (published & ready for consumption) Reuse # of assets per type (templates, data types, security, …) Reuse reusability rate per API API Usage # of transactions per API per day/week/month/year API Usage error rate per API API Usage Top 10 APIs in terms of usage
  10. 19 KPIS TO BE DELIVERED IN THE DASHBOARDS KPIS More

    KPIs! SINGLE PANE OF GLASS It concentrate all KPIs on a single place Fully automated KPIS Metric Domain Type Productivity # developers working actively on MuleSoft projects Quality # source code repositories with quality code issues Quality # API Governance compatibility rate Quality # bugs in PROD environment per api …