ICMG Banking Enterprise Architecture Convergence Model : Level 1–3 Certification Framework
- Sunil Dutt Jha
- Feb 7
- 5 min read
Updated: Feb 28
Enterprise Architecture within banking is commonly associated with IT governance, IT architectural standards, IT review boards, and technology frameworks. Many organizations evaluate maturity based on how IT architecture is practiced — the existence of processes, documentation, tooling, or governance structures.
However, experience across banking transformations shows that governance activity alone does not ensure enterprise consistency.
Banks frequently operate hundreds of concurrent initiatives — lending platforms, regulatory programs, payments modernization, digital channels — yet similar initiatives often interpret architecture differently. Workflow sequencing changes between programs, decision logic diverges subtly, data definitions evolve independently, and integration patterns are recreated repeatedly.
Architecture exists, but not as a one bank one anatomy.
The ICMG Banking Enterprise Architecture Convergence Model addresses this gap.
Instead of measuring maturity through architectural processes, the model evaluates whether one anatomy actually exists — and how far convergence toward that one anatomy has progressed.
Convergence is assessed across three levels:
Level 1 — IT Architecture convergence
Level 2 — Department architecture convergence
Level 3 — Enterprise architecture convergence
Each level progresses through three stages:
Foundation — anatomy exists and is actively used
Expansion — anatomy model spreads across initiatives
Enterprise — single anatomy model governs the full scope.
How the ICMG Model Differs from Generic EA Maturity Models
Traditional EA maturity models assess how IT architecture is practiced. They evaluate:
IT governance mechanisms
IT framework adoption
IT documentation completeness
IT tooling maturity
organizational roles.
These indicators measure architectural discipline but do not confirm whether initiatives operate under one consistent anatomy.
Organizations often achieve high maturity ratings while still operating multiple competing architectureacross programs and departments.
The ICMG model evaluates convergence instead of capability.
It asks:
Do initiatives share the same enterprise logic?
Do departments operate under one consistent anatomy?
Does enterprise behaviour follow a shared anatomical model?
Certification is based on anatomy evidence:
inheritance of architecture across initiatives
consistent decision logic
reduction of anatomy reinterpretation.
LEVEL 1 — EA (IT)
One Banking IT Architecture
Level 1 evaluates convergence within the IT function.
Architecture exists when one consistent anatomy across P1–P6 governs projects across IT initiatives.
P1 — Strategy intent
P2 — Process sequencing
P3 — Systems and decision logic
P4 — Components and platforms
P5 — Implementation execution
P6 — Operational behaviour.
Governance practices alone do not qualify unless anatomy consistency is observable.
Foundation — First IT Architecture
A banking IT initiative is explicitly structured across P1–P6 and actively used for decision-making.
Examples:
core banking modernization
payments platform
digital onboarding.
Indicators:
architectural conflicts resolved through anatomical reasoning
workflow sequencing explicitly defined
decision logic documented and applied.
If the architecture exists only as documentation without influencing decisions, Foundation is not achieved.
Expansion — Multiple IT Initiatives
Additional initiatives inherit the same anatomy model.
Indicators:
consistent sequencing across initiatives
shared decision logic patterns
aligned data definitions
reusable integration patterns.
Certification rule:
Multiple IT initiatives operate using one anatomy model.
Enterprise — Portfolio Convergence
Entire IT portfolio governed by one anatomy.
Indicators:
new initiatives use architecture automatically
parallel architecture interpretations disappear
portfolio decisions traceable to shared anatomy logic.
Boundary:
Convergence remains inside IT. Business departments may still operate independently.
LEVEL 2 — EA (Departments / Functions)
One Department One Architecture (Anatomy)
Level 2 evaluates convergence inside banking functions such as:
Retail Lending
Corporate Banking
Risk & Compliance
Treasury
Operations
Customer Service.
Departments achieve convergence when all initiatives operate under one consistent structure.
Foundation — First Department Architecture
One sub-function structured across P1–P6.
Example:
Retail lending underwriting:
strategy intent defined
loan lifecycle sequencing explicit
eligibility and pricing logic consistent
operational monitoring defined.
Indicators:
anatomy governs real decisions
manual and IT activities aligned.
Expansion — Sub-Function Propagation
Multiple sub-functions adopt the same structure.
Example: mortgages, SME lending, credit cards share structural principles.
Indicators:
consistent workflow sequencing
unified decision logic ownership
operational behaviour aligned.
Certification rule:
Multiple initiatives within a department follow one anatomy.
Enterprise — Department Convergence
Entire department governed by one architecture (anatomy).
Indicators:
new initiatives inherit anatomy automatically
decision conflicts resolved anatomically
operational behaviour predictable across sub-functions.
Boundary:
Cross-department behaviour still relies on coordination rather than one enterprise anatomy.
LEVEL 3 — EA (Enterprise Banking)
One Bank One Architecture
Level 3 evaluates enterprise-wide convergence.
Enterprise architecture exists when multiple departmental anatomy integrate into one enterprise anatomy shaping decisions across the bank. Enterprise integration alone does not qualify.
Foundation — First Enterprise Initiative
One cross-department initiative integrates departmental anatomy.
Examples:
enterprise customer lifecycle
regulatory transformation
enterprise lending transformation.
Indicators:
shared strategy intent across departments
common decision logic governing systems.
Expansion — Multiple Enterprise Initiatives
Several enterprise initiatives instantiate shared anatomy.
Indicators:
cross-department sequencing predictable
shared rules prevent conflicting implementations
dependencies anatomically visible.
Certification rule:
Multiple enterprise initiatives adopt shared enterprise anatomy.
Enterprise — Enterprise Convergence
Entire bank governed by one enterprise architecture (anatomy).
Indicators:
departmental interpretation reduces significantly
enterprise constraints guide decisions
cross-functional initiatives inherit shared anatomy automatically.
Unified Convergence Grid (Level 1–3)
Level | Scope | Foundation (first structure exists) | Expansion (multiple initiatives adopt) | Enterprise (structure governs scope) | Certification Confirms |
Level 1 — EA (IT) | Banking IT function | One IT initiative structured across P1–P6 and used for decisions. Example: core banking or payments program. | Multiple IT initiatives inherit same structure. Lending, channels, payments follow consistent sequencing and logic. | Entire IT portfolio governed by one structure. New projects inherit automatically; no parallel architectures. | One Banking IT Architecture governing decisions across IT initiatives. |
Level 2 — EA (Departments) | Banking business functions (e.g., Retail Lending, Risk, Treasury) | One sub-function structured end-to-end. Example: retail lending underwriting anatomy defined and used. | Multiple sub-functions adopt same structure. Mortgages, SME lending, credit cards follow shared sequencing and logic. | Entire department governed by one structure. Operational behaviour and decision logic consistent across initiatives. | One Department Architecture governing departmental initiatives. |
Level 3 — EA (Enterprise Banking) | Whole bank (cross-department) | First enterprise initiative integrates departmental structures. Example: enterprise customer lifecycle or regulatory transformation. | Multiple enterprise initiatives adopt shared structure; cross-department sequencing stabilizes. | Entire bank governed by one enterprise architecture. Decisions driven by shared enterprise structure rather than negotiation. | One Enterprise Architecture governing cross-department decisions. |
Anatomical Progression (What Actually Changes)
Level 1: competing IT architectures reduce → one IT Anatomy emerges.
Level 2: competing departmental structures reduce → one anatomy per department (function).
Level 3: departmental interpretation reduces → one enterprise anatomy governs behaviour.
Simple Mental Model
Level 1 — Many IT projects → One IT Architecture
Level 2 — Many initiatives per department → One Department Architecture
Level 3 — Many departments → One Enterprise Architecture
The ICMG Banking Enterprise Architecture Convergence Model reframes maturity as anatomy convergence rather than procedural sophistication.
Banks do not become mature by adding more governance layers or adopting additional frameworks. Maturity emerges when competing architectural interpretations reduce and one governing anatomy becomes visible across initiatives, departments, and enterprise behaviour.
Level 1 stabilizes architecture within IT. Level 2 establishes anatomy consistency within banking functions. Level 3 represents true enterprise architecture — where one shared anatomy governs how the bank operates.
The model recognizes that architecture already exists inside every organization. The question is not whether architecture is practiced, but whether it has converged into one governing anatomy.
