Level 3 Enterprise Architecture Convergence — EA (Enterprise / Industry) One Enterprise One Anatomy™
- Sunil Dutt Jha

- Feb 6
- 2 min read
Updated: Feb 7

Level 3 begins only after departmental anatomy exists.
At this point:
each department already operates with one consistent P1–P6 anatomy,
departmental initiatives no longer reinvent internal structures.
Enterprise architecture does not become enterprise-level simply because departments collaborate or systems integrate. Level 3 starts when enterprise-wide initiatives begin integrating departmental anatomies into one governing structure.
Two Mandatory Conditions
1. Departmental Anatomies Exist
Before enterprise anatomy can emerge:
HR operates with one HR anatomy,
Sales operates with one Sales anatomy,
Finance operates with one Finance anatomy,
Operations operates with one Operations anatomy,
and so on.
Without this foundation, enterprise work becomes coordination rather than structural convergence.
2. Enterprise Initiatives Integrate Departments Structurally
Enterprise anatomy emerges through real initiatives that span multiple departments.
Examples include:
enterprise transformation programs,
regulatory implementations,
enterprise platforms,
operational redesign initiatives.
These initiatives explicitly connect:
P1 strategy intent across departments,
P2 process sequencing across organizational boundaries,
P3 logic and decision rules shared across systems,
P4 components reused enterprise-wide,
P5 implementation responsibilities aligned across teams,
P6 operational behavior integrated across functions.
Propagation Inside Level 3
Level 3 maturity progresses as enterprise-wide initiatives increase.
Stage A — First Enterprise Initiative
One initiative connects multiple departmental anatomies.
One can clearly see:
how processes inside one department connect to processes in others,
how strategy intent aligns across functions / departments,
how system logic must remain consistent.
Stage B — Multiple Enterprise Initiatives
5–10 enterprise initiatives instantiate the shared structure.
Patterns begin stabilizing:
cross-department sequencing becomes predictable,
shared logic prevents conflicting implementations,
enterprise dependencies stop being negotiated repeatedly.
Stage C — Enterprise-Wide Propagation
Large numbers of initiatives operate using the shared enterprise anatomy.
Example:
50+ enterprise initiatives inherit the same structure.
At this stage:
Enterprise initiatives → One Enterprise Anatomy™
Important Clarification
Enterprise integration means systems talk to each other.
Enterprise anatomy means departments behave according to one shared anatomy. Without anatomical propagation, integration remains technical connectivity rather than enterprise governance.
What Level 3 Certification Confirms
ICMG does not certify collaboration maturity.
It certifies whether:
all departmental anatomies exist, and
enterprise initiatives instantiate one shared P1–P6 anatomy consistently across departments.




