IT4IT 3 Foundation cheat sheet

IT4IT is an Open Group standard: a vendor-neutral reference architecture for managing the business of IT, defined as a service model plus a set of functional components and data objects.

The architecture has four levels: Level 1 IT Value Chain, Level 2 value streams, Level 3 functional components, Level 4 data objects and their relationships.

A value stream is an end-to-end, back-to-back sequence of functional components that delivers measurable value to a stakeholder; it is not an org chart or a process decomposition.

IT4IT defines four value streams: Strategy to Portfolio (S2P), Requirement to Deploy (R2D), Request to Fulfill (R2F), and Detect to Correct (D2C).

The reference architecture is prescriptive about data and interfaces, not about products: it specifies what information must flow, leaving tool selection to the adopter.

Service model is the central concept: services are described by service offerings, service contracts, and consumed by service consumers; the four value streams act on this model.

IT4IT is intended as a blueprint for integrating tooling: each functional component exposes data objects that other components consume, enabling replaceable, interoperable tools.

The standard is published as the IT4IT Reference Architecture, Version 3.0 (2022), which refined the earlier 2.1 release and added guidance on digital product management and sustainability.

The IT Value Chain (Level 1) is the top-level view: it frames IT as a set of capabilities that turn demand into services and outcomes, organized around the four value streams.

Strategy to Portfolio (S2P): governs demand, strategy, portfolio, and investment; it answers 'what should we invest in?' and feeds approved demand into R2D.

Requirement to Deploy (R2D): covers requirements, design, build, test, release, and deploy; it produces deployable services and feeds them into R2F.

Request to Fulfill (R2F): handles catalog, order, fulfillment, and consumption; it delivers services to consumers and generates usage and incident data that feed D2C.

Detect to Correct (D2C): covers monitoring, event, incident, problem, and change; it restores service and feeds back into S2P and R2D for continual improvement.

Each value stream has a defined trigger, a set of functional components, and an outcome; the streams interlock through shared data objects rather than through handoffs of documents.

The value streams are not sequential phases of a single lifecycle; they run concurrently and exchange data continuously (e.g., D2C change records inform R2D releases).

A functional component (Level 3) is a logical grouping of capabilities that produces and consumes defined data objects; it is technology-independent and may be realized by one or more tools.

Data objects (Level 4) are the nouns of IT4IT: they have defined lifecycles and relationships, and their integrity across components is what the architecture governs.

Key S2P data objects: Idea, Demand, Proposal, Portfolio Item, Initiative, and Investment; the stream moves from idea capture to funded initiative.

Key R2D data objects: Requirement, Service Design, Service Release, Build, Test Case, Defect, and Deployment; these describe what is built and how it is released.

Key R2F data objects: Service Catalog Entry, Service Offering, Service Contract, Order, Subscription, and Fulfillment Request; these describe what is consumed.

Key D2C data objects: Event, Incident, Problem, Change, Known Error, and Service Level; these describe what is detected and corrected.

Shared data objects cross value streams: Service, Service Offering, Service Contract, and Configuration Item appear in more than one stream and must be consistent across tools.

Each functional component is defined by its purpose, its consumed and produced data objects, and its interfaces; the interfaces are what allow tool substitution without redesign.

Adoption typically starts with a value-stream assessment: map current tools and data flows onto the four streams, then identify gaps, overlaps, and broken data handoffs.

A common first step is establishing a single authoritative source for shared data objects (Service, Service Offering, Service Contract, Configuration Item) to remove duplication.

IT4IT is used to rationalize tool portfolios: components with overlapping data objects are candidates for consolidation, and missing components are candidates for acquisition.

Integration is specified by data object interfaces, not by vendor APIs; this lets an organization replace a tool without redefining the value stream.

Metrics are defined per value stream: S2P on investment alignment and time-to-fund, R2D on cycle time and release quality, R2F on fulfillment time, D2C on mean time to restore.

Governance is applied through the value streams: decision rights for portfolio investment sit in S2P, release approval in R2D, and service restoration authority in D2C.

IT4IT complements ITIL and DevOps rather than replacing them: IT4IT supplies the architectural and data model, while ITIL supplies process practice and DevOps supplies delivery culture.

Maturity is assessed per functional component and per data object, allowing targeted improvement rather than a single enterprise-wide maturity score.

The IT Value Chain (Level 1) is the top-level view: it frames IT as a set of capabilities that turn demand into services and outcomes, organized around the four value streams.

Strategy to Portfolio (S2P): governs demand, strategy, portfolio, and investment; it answers 'what should we invest in?' and feeds approved demand into R2D.

Requirement to Deploy (R2D): covers requirements, design, build, test, release, and deploy; it produces deployable services and feeds them into R2F.

Request to Fulfill (R2F): handles catalog, order, fulfillment, and consumption; it delivers services to consumers and generates usage and incident data that feed D2C.

Detect to Correct (D2C): covers monitoring, event, incident, problem, and change; it restores service and feeds back into S2P and R2D for continual improvement.

Each value stream has a defined trigger, a set of functional components, and an outcome; the streams interlock through shared data objects rather than through handoffs of documents.

The value streams are not sequential phases of a single lifecycle; they run concurrently and exchange data continuously (e.g., D2C change records inform R2D releases).