LN: Axelos (2019) — ITIL Foundation: ITIL 4

Bibliographic Reference

Citation: Axelos. (2019). ITIL foundation: ITIL 4 edition. TSO (The Stationery Office). https://www.axelos.com/certifications/itil-service-management


Pass 1 — Bird’s Eye View (5 Cs)

CAssessment
CategoryProfessional standard / service management framework
ContextITIL (Information Technology Infrastructure Library) 4th revision. The global standard for IT service management (ITSM), adopted by 90%+ of Fortune 500 companies
CorrectnessAuthoritative — developed by Axelos, owned by the UK Cabinet Office
Contributions(1) Service Value System (SVS); (2) Service Value Chain (6 activities); (3) 34 practices (replacing ITIL v3’s processes); (4) Four Dimensions of Service Management; (5) Integration with Agile, DevOps, and Lean
ClarityGood — updated ITIL 4 is more accessible than ITIL v3; integration with agile is much improved

Relevance: ⭐⭐⭐⭐

ITIL 4 provides the vocabulary and framework for PUMA’s SmartPMO: incident management (Ticket Triage) is a core ITIL practice. MTTD and MTTR — PUMA’s Stage 5 metrics — are standard ITIL Incident Management KPIs.


Pass 2 — Key Concepts

The Service Value System (SVS)

ITIL 4’s central model: all components work together to co-create value.

Guiding Principles
        ↓
Governance → Service Value Chain → Practices → Continual Improvement
        ↑
     Opportunity/Demand ──────────────────────────────→ Value

The Service Value Chain (6 Activities)

ActivityDescriptionPUMA Mapping
PlanEnsure shared directionSprint planning (H2 story point estimation)
ImproveContinual improvementPUMA iterative benchmark improvement
EngageStakeholder interactionDeveloper → Jira issue submission
Design & TransitionNew services/featuresAgent model deployment
Obtain/BuildAcquire/develop componentsOllama + model pipeline
Deliver & SupportDeliver services, resolve incidentsIssue triage (H1) — PUMA Stage 1

Incident Management Practice

The most relevant ITIL practice for PUMA:

  • Incident: Unplanned interruption or reduction in quality of an IT service
  • Triage: Classification of incidents by type, priority, and routing
  • SLA: Service Level Agreement — defines target resolution times per priority class
PriorityITIL SLA target (typical)PUMA Mapping
CriticalResolve in 1 hourTP for Critical class
HighResolve in 4 hoursTP for High class
MediumResolve in 8 hoursTP for Medium class
LowResolve in 24 hoursTP for Low class

Correct triage classification directly determines whether SLAs are met. A misclassified Critical issue (classified as Medium) violates SLA by design.

ITIL 4 Guiding Principles (Relevant to PUMA)

PrinciplePUMA Application
Focus on valueTriage automation delivers value by reducing MTTD
Think and work holisticallySmartPMO integrates triage + estimation + routing
Keep it simple and practicalPUMA MVP: triage module only
Collaborate and promote visibilityHITL design: PM reviews agent output
Optimise and automateStage 5: progressively automate routine PM tasks

PUMA Integration

  • Ch.1 Introduction: ITIL 4 as the organisational context for automated incident management
  • SmartPMO Stage 5: ITIL Service Value Chain as the framework for automated PM operations
  • Metrics: MTTD and MTTR as standard ITIL Incident Management KPIs (defined in PN-Evaluation-Metrics-Comprehensive)

MOCs