Building a Hybrid Functional Reference Architecture – Part 2 – IT4IT

In my last podcast I started the description of how we built the Hybrid Functional Reference Architecture and I introduced the three layers (Demand, Delivery, Supply). In this podcast I overlay the four IT4IT valuestreams on top of those three layers. Here are the definitions of the four valuestreams as described in version 2.1 of the standard:

  • The Strategy to Portfolio (S2P) Value Stream receives strategic demands for new or improved services from the business or IT itself and develops the Conceptual Service to represent the new or enhanced service that is requested. The Conceptual Service is the bridge between business and IT in that it provides the business context for the service along with the high-level architectural attributes.
  • The Requirement to Deploy (R2D) Value Stream receives the Conceptual Service and designs and develops the Logical Service with more detailed requirements that describe how the newly requested service and its components shall be designed. The Logical Service can be thought of as a user-friendly name for the “service system” to be created/enhanced which delivers the value to the business. The Logical Service and designs lead to the creation of a Service Release which is further described in Service Release Blueprints which ultimately describe how the service will be instantiated when delivered. The R2D Value Stream sources (builds, buys, or rents), tests, and delivers the deployable service (Service Release Blueprint) to the R2F Value Stream.
  • The Request to Fulfill (R2F) Value Stream receives the Service Release Blueprint and creates Service Catalog Entries which represent how the service is technically delivered. Service owners build out Offers based on what technical capabilities (Service Catalog Entries) are available. The Offers are viewable to the consumer and can be ordered for a set price and service contract as detailed in the Offer. Once ordered, the R2F Value Stream is responsible for the tasks to transition the service into production where the D2C Value Stream picks up the operational activities of the service.
  • The Detect to Correct (D2C) Value Stream provides a framework for integrating the monitoring, management, remediation, and other operational aspects associated with realized services and/or those under construction. It also provides a comprehensive overview of the business of IT operations and the services these teams deliver. Output from the D2C Value Stream enters the lifecycle as new demands within the S2P Value Stream.

Combining our three layers with the four value streams results in 12 areas of functionality.


Services are developed or sourced, but also require automation to ensure they can be provided to the user. This automation is created through a service release blueprint in IT4IT. With the many discussions around automation, we felt it was important enough to highlight that. In a similar way, the consumer of the service requests an instance and then uses it. For this reason we splitt R2D and R2F in two parts. Not that IT4IT needs to change, but to highlight both the service creation/usage and the service automation functions. So, our architecture is articulated around the following six areas:


That being said, listen to the podcast and you will get a mental picture how the different parts operate together. Have a great listening.

In the next podcast I will focus on the S2P pillar in the architecture.

4 Replies to “Building a Hybrid Functional Reference Architecture – Part 2 – IT4IT”

Tell me what is going through your mind.

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s