IRONCODELABS

Logo

Safe Passage to AI

View the Project on GitHub IRONCODELABS-COM/EA_STG

← Knowledge Base

ITIL and TOGAF

Audience: Enterprise Architecture Practice
Purpose: Establish ITIL as the benchmarking and standards measurement framework for IT operations; clarify its boundary with TOGAF


Framework Boundary Clarification

Concern Framework Scope
Architecture design and transformation TOGAF / ADM How to change
IT service quality and operational benchmarking ITIL How well you run

TOGAF governs the state transition. ITIL measures operational fitness of the current and target states. They are complementary, not competing. EA practice retains TOGAF for architecture governance; ITIL is adopted for IT landscape standards auditing and benchmarking.


What ITIL Provides

ITIL (IT Infrastructure Library) is a globally recognised framework for IT Service Management (ITSM). The current version, ITIL 4, is structured around the Service Value System (SVS) — a model that ensures all components of an organisation work together to create value through IT-enabled services.

Key constructs relevant to benchmarking:

Service Value Chain (SVC) — six activities (Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support) that map IT activities to business value delivery. Each activity is a measurement point.

Four Dimensions — People & Organisation, Information & Technology, Partners & Suppliers, Value Streams & Processes. These are the lens through which IT landscape health is assessed, directly aligned to EA concerns around capability and dependency mapping.

34 Management Practices — grouped into General, Service, and Technical practices. The most operationally critical for benchmarking are:


Key Benchmarking Metrics by Domain

Service Reliability

Change Quality

Incident & Problem

Service Desk

Continual Improvement


Integration with EA Practice

The EA team might use ITIL metrics as input signals to the Architecture Development Method (ADM):


Maturity Baseline (ITIL CMM Alignment)

ITIL 4 does not prescribe a formal maturity model, but the EA practice should adopt a 5-level maturity scale against each management practice:

Level Description
1 — Initial Ad hoc; no defined process
2 — Managed Process defined but inconsistently applied
3 — Defined Standardised, documented, measured
4 — Quantitatively Managed Metrics-driven; SLAs enforced
5 — Optimising Continual improvement embedded; predictive capability

Target for consolidated IT landscape: Level 3 minimum across all Tier 1 service practices before any significant architecture transformation is initiated. Level 4 for Incident, Change, and Availability management.


Potential Next Steps

  1. Conduct ITIL practice maturity assessment against current IT landscape
  2. Define service tiers (Tier 1/2/3) aligned to business criticality — EA input required
  3. Establish baseline metrics for the 7 priority practices listed above
  4. Set target benchmarks per tier; publish as EA-governed IT Standards Register
  5. Integrate ITIL reporting cadence into Architecture Review Board agenda

Document owner: Enterprise Architecture Practice
Framework references: ITIL 4 Foundation (AXELOS), TOGAF 10 (The Open Group), ICL ADM


© dbj@dbj.org , CC BY SA 4.0