In today's rapidly evolving digital landscape, effective API management & Event-driven architecture (EDA) play pivotal roles in shaping organizational success. As businesses strive to innovate and adapt, the choices between a Center of Excellence (CoE) and a Center for Enablement (C4E) become crucial. Throughout this session, we'll delve into the nuanced differences between these two approaches, exploring how each contributes to organizational enablement in the context of APIs and Event-driven systems.

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. 3
DANONE CONTEXT

4. ABOUT
DANONE
4
ABOUT DANONE
80%
of the revenue come from interfaces!
€28B
Annual
Revenue
100K
Employees
120
Prescence in
Markets

5. 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

6. 6
COE VS. C4E

7. 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

8. 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

9. 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”

10. 10
STARTING A C4E

11. INSERT
SECTION
TITLE
HERE
11
API ENABLEMENT (C4E) AS A PRODUCT

12. INSERT
SECTION
TITLE
HERE
12
API ENABLEMENT AS A PRODUCT

13. INSERT
SECTION
TITLE
HERE
13
API ENABLEMENT AS A PRODUCT

14. INSERT
SECTION
TITLE
HERE
14
INTERNAL API PORTAL

15. 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

16. INSERT
SECTION
TITLE
HERE
16
ARCHITECTURE COMMITTEE

17. 17
C4E KPIS

18. 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

19. 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
…

20. 20
THANK YOU