{"id":3906,"date":"2020-12-06T19:50:03","date_gmt":"2020-12-06T17:50:03","guid":{"rendered":"http:\/\/www.hosiaisluoma.fi\/blog\/?p=3906"},"modified":"2023-01-30T12:16:15","modified_gmt":"2023-01-30T10:16:15","slug":"make-it-work","status":"publish","type":"post","link":"https:\/\/www.hosiaisluoma.fi\/blog\/make-it-work\/","title":{"rendered":"Applied IT4IT"},"content":{"rendered":"

IT4IT<\/h1>\n

make IT work with the IT4IT<\/p>\n

1. IT Value Chain<\/h1>\n

To make the IT-function of the organization work, the IT4IT<\/strong> can be taken as a reference architecture – based on which the IT operating model can be built.\u00a0<\/span>The IT4IT can be taken as a reference for defining the operational model of an IT function. No need to reinvent the wheel. Instead, a ready-made model can be adapted to fit for purpose.\u00a0 \u00a0<\/span><\/p>\n

IT4IT is based on the value chain approach.\u00a0By default the IT value chain consists of four value streams\u00a0as follows: 1) Strategy to Portfolio (S2P), 2) Requirement to Deploy (R2D), 3) Request to Fulfill (R2F) and 4) Detect to Correct (D2C). Each of these value streams consists of specific behavioral elements that switch information. These value streams of the overall value chain are analogous to the approach of Plan, Build, Deliver, Run<\/em> -phases, as shown in the figure below.\u00a0<\/span><\/p>\n

\"\"
Figure 1<\/strong>: IT Value Chain.<\/figcaption><\/figure>\n

The IT4IT reference architecture from the Open Group defines the overall IT operating model, which covers all that is needed for organizing and running IT. IT4IT is already proven, tested and implemented in large organizations. IT4IT consists of common activities that are typical in IT functions – no matter in what sector or industry the organization is. The official IT4IT site is here: link<\/a><\/span>. <\/span><\/p>\n

This article is based on the IT4IT version 2.<\/p>\n

2. IT4IT reloaded<\/h1>\n

The IT4IT provides a good approach for analyzing from which parts an IT operating model can be built on.<\/span><\/p>\n

Some modifications can be made to the default IT4IT version for simplicity, e.g. as follows:<\/span><\/p>\n

    \n
  1. The first value stream of the value chain is renamed to “Demand to Portfolio<\/strong><\/em>“, as this better conforms to what is actually happening in practice: incoming demands are prepared to concepts into the IT development portfolio<\/li>\n
  2. The capability<\/strong><\/em> -concept is used as a fundamental behavioral element of the operating model for defining WHAT<\/em> an organization shall have. A capability can then be further defined as a process, function, actor etc., based on what is appropriate in the organization – to define HOW<\/em> the organization works in practice. Some new capabilities are introduced here (Innovation Management, Quality Management, Information Management and Security Management). Capability is at a high abstraction level (like the Practice<\/em>\u00a0 -concept in ITIL4), so an element like that can be used when defining what are the things that the organization should have.<\/li>\n
  3. The fundamental unit of overall development can be either a) digital service<\/em><\/strong> or b) digital product<\/strong><\/em>, based on what is appropriate in the organization.<\/li>\n<\/ol>\n

    \"\"<\/p>\n

    2.1 Business Interface of the IT Value Chain<\/h2>\n

    The IT value chain of the IT-function represents the development value stream of the organization. The business units (lines of business, LOBs) may have several operational value streams according to the business model of the organization. In addition, the business units may have their own processes for their business development. There can be four business interfaces towards the IT-value chain as introduced in the figure below.<\/p>\n

    The IT-value chain interacts with the lines of business (business units) via interfaces as illustrated in the figure below.<\/p>\n

    \"\"<\/p>\n

    The IT development value chain receives IT-related demands and handles them within the\u00a0Demand to Portfolio<\/em>\u00a0on the IT side. In addition, there are four (4) business interfaces towards the IT value chain as follows:<\/p>\n

      \n
    1. A business idea\/demand is initiated by the Demand to Portfolio<\/em>\u00a0on the business side, then received by the Demand to Portfolio<\/em>\u00a0on the IT side<\/li>\n
    2. A business requirement\/feature is produced\u00a0by the Demand to Portfolio<\/em>\u00a0on the business side, and then received by the Requirement to Deploy<\/em> on the IT side.<\/li>\n
    3. A service request is triggered\u00a0on the business side, and then received by the Request to Fulfill<\/em> on the IT side.<\/li>\n
    4. An incident is produced\u00a0on the business side, and then received by the Detect to Correct<\/em> on the IT side.<\/li>\n<\/ol>\n

      Another illustration of this business interface is shown below.<\/p>\n

      \"\"
      Figure 4:<\/strong> Business Interface to IT Value Chain.<\/figcaption><\/figure>\n

      2.2 Business Model & Capability Model<\/h2>\n

      The applied IT4IT value chain (figure below) consists of four value streams as follows:<\/p>\n

        \n
      1. Demand to Portfolio (D2P) [ IT4IT default: Strategy to Portfolio (S2P)<\/em> ]<\/li>\n
      2. Requirement to Deploy (R2D)<\/li>\n
      3. Request to Fulfill (R2F)<\/li>\n
      4. Detect to Correct (D2C)<\/li>\n<\/ol>\n
        \"\"
        Figure 5<\/strong>: IT Capability Model.<\/figcaption><\/figure>\n

        Each value stream is connected with a set of capabilities, and the whole value chain is supported by certain “supporting capabilities”.<\/p>\n

        The capability model connected with the value streams of the value chain, defines WHAT behavioral elements the organization has. As capabilities are connected with the value streams of the value chain, this defines what is required for value creation within each value stream. This represents the business model. The operating model, instead, is a more detailed representation of the behavior of the organization. The operating model defines HOW an organization does what<\/em> it does. The operating model can be defined with processes or functions and information flows between them.<\/p>\n

        The difference between value streams and business processes is described as follows in the ArchiMate specification (link<\/a><\/span>):<\/p>\n

        Importantly, value streams and business processes may seem alike, but they are defined at different abstraction levels and serve separate purposes. A business process describes the (time-ordered) sequence of behaviors required to create some result for an individual case, and it may describe alternative paths and decision points (modeled with junctions). In contrast, a value stream focuses on the overall value-creating behavior from the perspective of the importance, worth, or usefulness of what is produced, and is not a description of time-ordered tasks for individual cases.<\/p>\n

        The difference between the business model and operating model is described as follows in ArchiMate specification:<\/p>\n

        Value streams (and capabilities) reflect an organization\u2019s business model<\/strong> and value proposition, whereas business processes (and business functions) reflect its operating model<\/strong>. At their respective abstraction levels, value streams and business processes both represent the \u201centerprise in motion\u201d, whereas capabilities and business functions both describe the \u201centerprise at rest\u201d.<\/p>\n

        2.3 Operating Model<\/h2>\n

        This version of the IT4IT operating model illustrates the process cooperation view.<\/p>\n

        \"\"
        Figure 6<\/strong>: IT Operating Model.<\/figcaption><\/figure>\n

        2.3.1 Demand to Portfolio (D2P) Value Stream<\/h3>\n
        \"\"
        Figure 7<\/strong>: Demand to Portfolio (D2P) Value Stream.<\/figcaption><\/figure>\n

        2.3.2 Requirement to Deploy (R2D)\u00a0Value Stream<\/h3>\n

        TBD: E.g. Business events that trigger processes…<\/p>\n

        \"\"
        Figure 8<\/strong>: Requirement to Deploy (R2D)\u00a0Value Stream.<\/figcaption><\/figure>\n

        2.3.3 Request to Fulfill (R2F)\u00a0Value Stream<\/h3>\n

        TBD: E.g. Business events that trigger processes…<\/p>\n

        \"\"
        Figure 9<\/strong>: Request to Fulfill (R2F)\u00a0Value Stream.<\/figcaption><\/figure>\n

        2.3.4 Detect to Correct (D2C)\u00a0Value Stream<\/h3>\n

        TBD: E.g. Business events that trigger processes…<\/p>\n

        \"\"
        Figure 10<\/strong>: Detect to Correct (D2C)\u00a0Value Stream.<\/figcaption><\/figure>\n
        \n

        For more information of the IT4IT see this reference material:<\/p>\n