The IT4IT™ Reference Architecture, Version 2.1 E-Book

The Open Group

• Herausgeber: Van Haren Publishing
• Kategorie: Bildung
• Sprache: Englisch

Seitenzahl: 235

Veröffentlichungsjahr: 2017

Beschreibung

The Open Group IT4IT™ Reference Architecture, Version 2.1, an Open Group Standard, provides a vendor-neutral, technology-agnostic, and industry-agnostic reference architecture for managing the business of IT. The Open Group IT4IT Reference Architecture standard comprises a reference architecture and a value chain-based operating model. The IT Value Chain has four value streams supported by a reference architecture to drive efficiency and agility. The four value streams are: • Strategy to Portfolio • Request to Fulfill • Requirement to Deploy • Detect to Correct Each IT Value Stream is centered on a key aspect of the service model, the essential data objects (information model), and functional components (functional model) that support it. Together, the four value streams play a vital role in helping IT control the service model as it advances through its lifecycle. The IT4IT Reference Architecture: • Provides prescriptive guidance on the specification of and interaction with a consistent service model backbone (common data model/context) • Supports real-world use-cases driven by the Digital Economy (e.g., Cloud-sourcing, Agile, DevOps, and service brokering) • Embraces and complements existing process frameworks and methodologies (e.g., ITIL®, CoBIT®, SAFe, and TOGAF®) by taking a data-focused implementation model perspective, essentially specifying an information model across the entire value chain The audience for this standard is: • IT Professionals who are responsible for delivering services in a way that is flexible, traceable, and cost-effective • IT Professionals / Practitioners who are focused on instrumenting the IT management landscape • IT Leaders who are concerned about their operating model • Enterprise Architects who are responsible for IT business transformation Topics covered include: • An introduction to the standard and the purpose of the IT4IT work • Key terminology of the standard • An introduction for executives and others introducing the IT Value Chain and IT4IT Reference Architecture concepts • IT4IT Core, which defines the structure of the IT4IT standard as well as the process and document structure used by the IT4IT standard • The Strategy to Portfolio (S2P) Value Stream • The Requirement to Deploy (R2D) Value Stream • The Request to Fulfill (R2F) Value Stream • The Detect to Correct (D2C) Value Stream • Background information on the standard.

Leseprobe

The Open Group IT4IT™ Reference Architecture, Version 2.1

The Open Group Publications available from Van Haren Publishing

The TOGAF Series:

TOGAF® Version 9.1

TOGAF® Version 9.1 – A Pocket Guide

TOGAF® 9 Foundation Study Guide, 3rd Edition

TOGAF® 9 Certified Study Guide, 3rd Edition

The Open Group Series:

The IT4IT™ Reference Architecture, Version 2.1

IT4IT™ for Managing the Business of IT – A Management Guide

IT4IT™ Foundation Study Guide

The IT4IT™ Reference Architecture, Version 2.1 – A Pocket Guide

Cloud Computing for Business – The Open Group

Guide ArchiMate® 3.0 – A Pocket Guide

ArchiMate® 2 Certification – Study Guide

ArchiMate® 3.0 Specification

The Open Group Security Series:

O-TTPS - A Management Guide

Open Information Security Management Maturity Model (O-ISM3)

Open Enterprise Security Architecture (O-ESA)

Risk Management – The Open Group Guide

The Open FAIR™ Body of Knowledge – A Pocket Guide

All titles are available to purchase from:

www.opengroup.org

www.vanharen.net

and also many international and online distributors.

Colophon

Title:

The Open Group IT4IT™ Reference Architecture, Version 2.1

A Publication of:

The Open Group

Publisher:

Van Haren Publishing, Zaltbommel, www.vanharen.net

ISBN Hard copy:

978 94 018 0112 6

ISBN eBook:

978 94 018 0113 3

ISBN ePub:

978 94 018 0114 0

Edition:

First edition, first impression, January 2016Second edition, first impression, April 2017

Production ePUB:

Coco Bookmedia, Amersfoort – NL

Copyright:

© 2015, 2017 The Open Group. All rights reserved.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owner.

Open Group Standard

The Open Group IT4IT™ Reference Architecture, Version 2.1

Document Number: C171

Published by The Open Group, April 2017.

Comments relating to the material contained in this document may be submitted to:

The Open Group

Apex Plaza

Forbury Road

Reading

Berkshire, RG1 1AX

United Kingdom

or by electronic mail to: [email protected]

For any further enquiries about Van Haren Publishing, please send an email to:[email protected].

Contents

1    Introduction

1.1   Objective

1.2   Overview

1.3   Conformance

1.4   Normative References

1.5   Terminology

1.6   Future Directions

2    Definitions

2.1   Service Lifecycle Data Object

2.2   IT Value Chain

2.3   Value Chain

2.4   Value Stream

2.5   Functional Component

2.6   Service Model Backbone Data Object

2.7   Relationship

2.8   System of Record

2.9   IT Service

3    Overview

3.1   What is the IT Value Chain?

3.2   IT Value Chain and IT4IT Reference Architecture

3.3   IT Value Streams

3.3.1    Strategy to Portfolio

3.3.2    Requirement to Deploy

3.3.3    Request to Fulfill

3.3.4    Detect to Correct

3.4   IT4IT Reference Architecture

3.4.1    Service Model

3.4.2    Information Model

3.4.3    Functional Model

3.4.4    Integration Model

3.5   IT Service

4    IT4IT Core

4.1   Introduction

4.2   IT4IT Abstraction Levels and Class Structure

4.2.1    IT4IT Abstractions

4.2.2    Concepts at Level 1: End-to-End Overview

4.2.3    Level 1 Reference Architecture Model

4.2.4    Concepts at Level 2: Value Stream Documentation

4.2.5    Level 2 Reference Architecture Diagram (Example)

4.2.6    Concepts at Level 3: Vendor-Independent Architecture

4.2.7    Level 3 Reference Architecture Diagram (Example)

4.2.8    Concepts at Levels 4 and 5 – Vendor Extensions

5    Strategy to Portfolio (S2P) Value Stream

5.1   Objectives

5.2   Business Value Proposition

5.3   Key Performance Indicators

5.4   Value Stream Definition

5.4.1    Enterprise Architecture Functional Component

5.4.2    Policy Functional Component

5.4.3    Proposal Functional Component

5.4.4    Portfolio Demand Functional Component

5.4.5    Service Portfolio Functional Component

5.4.6    IT Investment Portfolio – Auxiliary Functional Component

6    Requirement to Deploy (R2D) Value Stream

6.1   Objectives

6.2   Business Value Proposition

6.3   Key Performance Indicators

6.4   Value Stream Definition

6.4.1    Project Functional Component

6.4.2    Requirement Functional Component

6.4.3    Service Design Functional Component

6.4.4    Source Control Functional Component

6.4.5    Build Functional Component

6.4.6    Build Package Functional Component

6.4.7    Release Composition Functional Component

6.4.8    Test Functional Component

6.4.9    Defect Functional Component

7    Request to Fulfill (R2F) Value Stream

7.1   Objectives

7.2   Business Value Proposition

7.3   Key Performance Indicators

7.4   Value Stream Definition

7.4.1    Engagement Experience Portal (Secondary Functional Component)

7.4.2    Offer Consumption Functional Component

7.4.3    Offer Management Functional Component

7.4.4    Catalog Composition Functional Component

7.4.5    Request Rationalization Functional Component

7.4.6    Fulfillment Execution Functional Component

7.4.7    Usage Functional Component

7.4.8    Chargeback/Showback Functional Component

7.4.9    Knowledge & Collaboration Supporting Function

8    Detect to Correct (D2C) Value Stream

8.1   Objectives

8.2   Business Value Proposition

8.3   Key Performance Indicators

8.4   Value Stream Definition

8.4.1    Service Monitoring Functional Component

8.4.2    Event Functional Component

8.4.3    Incident Functional Component

8.4.4    Problem Functional Component

8.4.5    Change Control Functional Component

8.4.6    Configuration Management Functional Component

8.4.7    Diagnostics & Remediation Functional Component

8.4.8    Service Level Functional Component

8.4.9    Other IT Operations Areas

A Rationale (Informative)

A.1  Introduction

A.2  Definitions

A.3  Overview

A.3.1   Business Drivers for an Improved IT Operating Model

A.3.2   The IT Value Chain

A.4  IT4IT Core

A.4.1   Value Streams

A.4.2   Functional Components

A.5  Strategy to Portfolio Value Stream

A.5.1 Related Standards, Frameworks, and Guidance

A.6  Requirement to Deploy Value Stream

A.6.1   Related Standards, Frameworks, and Guidance

A.7  Request to Fulfill Value Stream

A.7.1   Related Standards, Frameworks, and Guidance

A.8  Detect to Correct Value Stream

A.8.1   Related Standards, Frameworks, and Guidance

List of Figures

Figure 1: Documentation Structure of the IT4IT Reference Architecture

Figure 2: IT Value Chain

Figure 3: IT Value Streams and Service Models

Figure 4: Value Stream Overview

Figure 5: Strategy to Portfolio Activities

Figure 6: Requirement to Deploy Activities

Figure 7: Request to Fulfill Activities

Figure 8: Detect to Correct Activities

Figure 9: IT4IT Service Model

Figure 10: Data Objects and Relationships

Figure 11: Engagement Experience Portal Functional Component

Figure 12: Data Flows in the IT4IT Reference Architecture

Figure 13: Engagement and Insight Information Flow

Figure 14: IT Service

Figure 15: IT4IT Reference Architecture Levels

Figure 16: Level 1 Class Model

Figure 17: Functional Component Notation

Figure 18: Functional Component to Data Object Notation

Figure 19: Functional Components and Data Objects

Figure 20: Service Lifecycle Data Object Notation

Figure 21: System of Record Fabric

Figure 22: Relationships Notation

Figure 23: IT4IT Level 1 Reference Architecture Model

Figure 24: Level 2 Class Model

Figure 25: Data Flow Notation

Figure 26: Data Object State Model Dependency Illustration

Figure 27: System of Engagement Integration Illustration

Figure 28: System of Record and Engagement Integration Notation

Figure 29: Capability Discipline Informal Notation

Figure 30: Capability Discipline Formal Notation

Figure 31: Example Level 2 Diagram (R2F Value Stream)

Figure 32: Level 3 Class Model

Figure 33: Scenario Process Flow Example

Figure 34: Essential Service Diagram Example

Figure 35: Essential Attributes Example

Figure 36: Essential Attributes Notation

Figure 37: Example of Functional Components, Data Objects, and Essential Services

Figure 38: Level 3 Notation Guide

Figure 39: Strategy to Portfolio Level 2 Value Stream Diagram

Figure 40: Enterprise Architecture Functional Component Level 2 Model

Figure 41: Policy Functional Component Level 2 Model

Figure 42: Proposal Functional Component Level 2 Model

Figure 43: Portfolio Demand Functional Component Level 2 Model

Figure 44: Service Portfolio Functional Component Level 2 Model

Figure 45: IT Investment Portfolio – Auxiliary Functional Component Level 2 Model

Figure 46: Requirement to Deploy Level 2 Value Stream Diagram

Figure 47: Project Functional Component Level 2 Model

Figure 48: Requirement Functional Component Level 2 Model

Figure 49: Service Design Functional Component Level 2 Model

Figure 50: Source Control Functional Component Level 2 Model

Figure 51: Build Functional Component Level 2 Model

Figure 52: Build Package Functional Component Level 2 Model

Figure 53: Release Composition Functional Component Level 2 Model

Figure 54: Test Functional Component Level 2 Model

Figure 55: Defect Functional Component Level 2 Model

Figure 56: Request to Fulfill Level 2 Value Stream Diagram

Figure 57: Engagement Experience Portal Level 2 Model

Figure 58: Offer Consumption Functional Component Level 2 Model

Figure 59: Offer Management Functional Component Level 2 Model

Figure 60: Catalog Composition Functional Component Level 2 Model

Figure 61: Request Rationalization Functional Component Level 2 Model

Figure 62: Fulfillment Execution Functional Component Level 2 Model

Figure 63: Usage Functional Component Level 2 Model

Figure 64: Chargeback/Showback Functional Component Level 2 Model

Figure 65: Knowledge & Collaboration Supporting Function Level 2 Model

Figure 66: Detect to Correct Level 2 Value Stream Diagram

Figure 67: Service Monitoring Functional Component Level 2 Model

Figure 68: Event Functional Component Level 2 Model

Figure 69: Incident Functional Component Level 2 Model

Figure 70: Problem Functional Component Level 2 Model

Figure 71: Change Control Functional Component Level 2 Model

Figure 72: Configuration Management Functional Component Level 2 Model

Figure 73: Diagnostics & Remediation Functional Component Level 2 Model

Figure 74: Service Level Functional Component Level 2 Model

Preface

The Open Group

The Open Group is a global consortium that enables the achievement of business objectives through IT standards. With more than 500 member organizations, The Open Group has a diverse membership that spans all sectors of the IT community – customers, systems and solutions suppliers, tool vendors, integrators, and consultants, as well as academics and researchers – to:

•   Capture, understand, and address current and emerging requirements, and establish policies and share best practices

•   Facilitate interoperability, develop consensus, and evolve and integrate specifications and open source technologies

•   Offer a comprehensive set of services to enhance the operational efficiency of consortia

•   Operate the industry’s premier certification service

Further information on The Open Group is available at www.opengroup.org.

The Open Group publishes a wide range of technical documentation, most of which is focused on development of Open Group Standards and Guides, but which also includes white papers, technical studies, certification and testing documentation, and business titles. Full details and a catalog are available at www.opengroup.org/bookstore.

Readers should note that updates – in the form of Corrigenda – may apply to any publication. This information is published at www.opengroup.org/corrigenda.

The IT4IT™ Forum

The IT4IT Forum, a Forum of The Open Group, enables industry thought leaders to collaborate in the development of the IT4IT Value Chain and Reference Architecture standard for business benefit.

The mission of this Forum is to create and drive the adoption of the IT4IT Reference Architecture standard to manage the business of IT, enable business insight across the IT value chain, increase focus on business outcomes, and improve agility.

Participation in the IT4IT Forum enables IT practitioners, consultants, technology and training vendors, service providers, business managers, and academics to come together in a technology-agnostic, industry-agnostic, and vendor-neutral environment to solve shared IT Management challenges. Participants in IT4IT Forum work groups benefit as they:

•   Increase their depth of knowledge of the standard and how to use it to benefit their organization

•   Gain early access to the latest thinking, before it gets published broadly to the world

•   Learn from collaborating with others and networking with industry thought leaders and competitors

•   Build personal relationships and contacts that will be of benefit long into the future

•   Take advantage of opportunities to build a personal brand and develop professionally

For further information, visit www.opengroup.org/IT4IT.

This Document

The Open Group IT4IT™ Reference Architecture refers to the capability or capabilities required to manage the business of IT, covering IT end-to-end from plan, through build and operate. It assumes the principle that the business of running IT is industry-agnostic and that IT leaders share the same problems and opportunities in managing the service lifecycle effectively. At the core, these problems are rooted in IT structure, competencies, and capabilities and the missing link has been the lack of a business model for IT. The IT4IT Reference Architecture proposes that it is possible to establish an IT standard mapped to the existing IT landscape yet flexible enough to support the volatility inherent in the IT industry and accommodate changing IT paradigms (composite apps, agile development, mobile technology, multi-sourcing, etc.).

The IT Value Chain and IT4IT Reference Architecture represent the IT service lifecycle in a new and powerful way, providing the missing link between industry standard best practice guides and the technology you need to select and execute those processes. The IT Value Chain and IT4IT Reference Architecture are a new foundation on which to base your IT4IT operating model and provide a welcome blueprint for the CIO to accelerate IT’s transition to becoming a service broker to the business.

This document is The Open Group IT4IT Reference Architecture, Version 2.1, an Open Group Standard. It has been developed and approved by The Open Group.

This document is structured as follows:

•   Chapter 1 (Introduction) introduces this document and the purpose of the IT4IT work.

•   Chapter 2 (Definitions) lists important definitions needed in order to read the document.

•   Chapter 3 (Overview) is an introduction for executives and others introducing the IT Value Chain and IT4IT Reference Architecture concepts.

•   Chapter 4 (IT4IT Core) defines the structure of the IT4IT standard as well as the process and document structure used by the IT4IT standard.

•   Chapter 5 (Strategy to Portfolio (S2P) Value Stream) explains the S2P Value Stream in detail.

•   Chapter 6 (Requirement to Deploy (R2D) Value Stream) explains the R2D Value Stream in detail.

•   Chapter 7 (Request to Fulfill (R2F) Value Stream) explains the R2F Value Stream in detail.

•   Chapter 8 (Detect to Correct (D2C) Value Stream) explains the D2C Value Stream in detail.

•   Appendix A (Rationale (Informative)) contains background information on the standard.

How to Use this Standard

It is recommended that the reader start by familiarizing themselves with Chapter 3 (Overview) which introduces the concepts of the IT Value Chain. This should then be followed by the IT4IT Core (Chapter 4), and the four IT Value Streams. These are:

•   Strategy to Portfolio (S2P) Value Stream (Chapter 5)

•   Requirement to Deploy (R2D) Value Stream (Chapter 6)

•   Request to Fulfill (R2F) Value Stream (Chapter 7)

•   Detect to Correct (D2C) Value Stream (Chapter 8)

Documentation Structure of the IT4IT Reference Architecture

Figure 1 is a graphical representation of the data objects associated with the IT4IT Reference Architecture. The architecture is comprised of a set of normative documents1 and a formal model described using the ArchiMate® modeling language and UML. These define “what” the architecture is. The normative documentation includes:

•   IT4IT Reference Architecture Overview

•   IT4IT Value Stream Overview

•   IT4IT Reference Architecture diagrams

•   IT4IT meta-model diagram

•   Glossary

The Reference Architecture diagrams will be available in other formats as part of the licensed downloads from The Open Group website.

A set of guidance documents has been developed to accompany the architecture, intended to describe “how” to apply the architecture in practice. Guidance documents include:

•   Definition of IT Service White Paper

•   Service Model Management White Paper

•   Service-Level Management White Paper

•   Multi-Supplier Management White Paper

•   IT Financial Management Scenario

•   Agile Scenario

Figure 1: Documentation Structure of the IT4IT Reference Architecture

Documents/artifacts that fall into these two categories are governed by The Open Group Standards Process. In addition, The Open Group will maintain a set of White Papers that complement the architecture and elaborate on its applicability and use in various settings.

IT4IT, Version 2.1 Release Highlights

The following topics have been included/enhanced in Version 2.1 of the IT4IT Reference Architecture.

•   Service Model simplification and enhancement – The data objects which make up the Service Model Backbone have been simplified and better defined to lead to a stronger understanding of the Reference Architecture in its entirety. The Service Model is the backbone of the entire standard.

•   Financial Management supporting functionality – The Reference Architecture has been updated to highlight how financial management capabilities are now supported by the standard. Financial Management is one of the supporting functions in the overall IT Value Chain and has impacts on core functions and data objects which have been updated to more effectively support this capability.

•   General consistency and flow of the overall standard – The Reference Architecture 2.0 was the first version of the standard which was published. There were certain sections, naming conventions, and content which lacked some consistency throughout the standard which have now been resolved.

Related Industry Standards

Most IT management standards fall into one of two categories: process and/or method-focused technology and/or implementations-centric. There are no standards that prescribe both the IT model and automation guidelines for running the IT function. Therefore, the IT4IT Reference Architecture fills this gap and as such complements a number of existing standards and best practices such as:

•   ISO/IEC 19770:2012: Information Technology – Software Asset Management

•   ISO/IEC 20000:2011: Information Technology – Service Management

•   ISO/IEC 38500:2008: Corporate Governance of Information Technology

•   ISO/TC 258: Project, Program, and Portfolio Management

•   Information Technology Infrastructure Library (ITIL)

•   Control Objectives for Information and Related Technology (COBIT)

•   Business Process Framework (eTOM)

•   The TOGAF® standard

•   The ArchiMate® modeling language

•   The Scaled Agile Framework (SAFe)

•   The Project Management Body of Knowledge (PMBOK)

_________

1 A normative document is one that provides rules, guidelines, or characteristics for activities or their results. The term “normative document” is a generic term that covers such documents as standards, technical specifications, codes of practice, and regulations; e.g., European Cooperation for Space Standardization (ECSS).

Trademarks

ArchiMate®, DirecNet®, Making Standards Work®, OpenPegasus®, The Open Group®, TOGAF®, UNIX®, UNIXWARE®, X/Open®, and the Open Brand X® logo are registered trademarks and Boundaryless Information Flow™, Build with Integrity Buy with Confidence™, Dependability Through Assuredness™, EMMM™, FACE™, the FACE™ logo, IT4IT™, the IT4IT™ logo, O-DEF™, O-PAS™, Open FAIR™, Open Platform 3.0™, Open Process Automation™, Open Trusted Technology Provider™, Platform 3.0™, SOSA™, the Open O™ logo, and The Open Group Certification logo (Open O and check™) are trademarks of The Open Group.

CMMI® is registered in the US Patent and Trademark Office by Carnegie Mellon University.

COBIT® is a registered trademark of the Information Systems Audit and Control Association (ISACA) and the IT Governance Institute.

eTOM® is a registered trademark of the TM Forum.

ITIL® is a registered trademark of AXELOS Ltd.

OASIS™ and TOSCA™ are trademarks of OASIS.

OMG®, Unified Modeling Language®, and UML®, are registered trademarks of the Object Management Group, Inc. in the United States and/or other countries.

All other brands, company, and product names are used for identification purposes only and may be trademarks that are the sole property of their respective owners.

Acknowledgements

This standard was prepared by The Open Group IT4IT™ Forum.

When The Open Group approved the IT4IT™ Reference Architecture, Version 2.1, an Open Group Standard, on January 25, 2017, the membership of the IT4IT™ Forum was as follows:

Steering Committee

Rob Akershoek, Logicalis SMC, Chair

Karel van Zeeland, Logicalis SMC, Vice-Chair

Linda Kavanagh, The Open Group, Forum Director

Andrew Josey, The Open Group, VP Standards & Certification

Cathy Fox, The Open Group, Technical Editor

Lead Architects

Core Group: Lars Rossen, Hewlett Packard Enterprise

Service Model Management: Sue Desiderio, PricewaterhouseCoopers LLP, USA

IT Financial Management: Philippe Geneste, Accenture

IT Asset Management: Charlie Betz, Armstrong Process Group

Service-Level Management: Ohad Goldfarb, Hewlett Packard Enterprise

Lead Value Stream Editors

Core: Lars Rossen, Hewlett Packard Enterprise

S2P: Jim Johnson, Hewlett Packard Enterprise

R2D: Sue Desiderio, PricewaterhouseCoopers LLP, USA

R2F: Dan Rosenzweig, Hewlett Packard Enterprise

D2C: Ohad Goldfarb, Hewlett Packard Enterprise

Contributors

The Open Group gratefully acknowledges the contribution of the following members of the IT4IT™ Forum in the development of this standard:

Richard Aarnink

Linda Kavanagh

Rob Akershoek

Mark Luchtmeijer

Chris Armstrong

Lakshmi Malhotra

Charles Betz

Sylvain Marie

Georg Bock

Gunnar Menzel

Mark Bodman

Satya Misra

Paul Buckley

Brian Ng

James Caruso

Dan Rosenzweig

Eran Cohen

Lars Rossen

Sam Courtney

Vasu Sankhavaram

Sukumar Daniel

Peter Scheffczyk

Dwight David

Ryan Schmierer

Christopher Davis

Rick Solis

Sue Desiderio

Ken Street

Ulrich Feyer

Mary Street

Mike Fulton

Etienne Terpstra

Philippe Geneste

Richard Tian

Ohad Goldfarb

Erik van Busschbach

Mark Gray

Kees van den Brink

Claudia Guli

Karel van Zeeland

Trey Harris

Gerlan Verlouw

Rob Hengeveld

Prafull Verma

Brian Hodgdon

Floris Verschoor

Keith Jahn

Ulrich Wanka

Jim Johnson

Erik Witte

Technical Reviewers

Technical reviewers are those individuals who have submitted comments during the company review, or participated in the resolution process during the development of the IT4IT Reference Architecture, Version 2.1.

Sam Courtney

Andrew Josey

Chris Davis

Martin Kirk

Sue Desiderio

Randall Ramsey

Thorbjörn Ellefsen

Lars Rossen

Ohad Goldfarb

Mark Smalley

IT4IT™ Forum Members

Accenture Limited, USA

Achmea, The Netherlands

Action Research Foundation, India

Agency for Public Management and eGovernment (Difi), Norway

Arismore, France

Armstrong Process Group, Inc., USA

AT&T IT Architecture Solutions, USA

ATE Enterprises Ltd., UK

Biner Consulting, Sweden

BP Oil International Limited, UK

CA, Inc., USA

Capgemini S.A., The Netherlands

CC and C Solutions, USA

Conexiam Solutions, Inc., USA

Dux Diligens S.A de C.V, Mexico

EA Principals, Inc., USA

Ernst & Young, UK

ExxonMobil, USA

Fujitsu, Japan

HCL Technologies Ltd., India

Hewlett Packard Enterprise, USA

Huawei Technologies, Co. Ltd., China

IBM, USA

Logicalis SMC, The Netherlands

Microsoft, USA

Ministerie van Financien, The Netherlands

Munich Re Group, Germany

National Healthcare, USA

Nationwide Mutual Insurance Company, Inc., USA

Oracle Corporation, USA

Origin Energy, Australia

PricewaterhouseCoopers LLP, USA

Raytheon Company, USA

Real IRM Solutions (Pty) Ltd., South Africa

ServiceNow, Inc., USA

Shell Information Technology International B.V., The Netherlands

Shift Technologies LLC, United Arab Emirates

Stichting ASL BiSL Foundation, The Netherlands

Tata Consultancy Services Ltd., India

The Boeing Company, USA

UMBRiO, The Netherlands

University of South Florida, USA

Westbury Software, The Netherlands

Referenced Documents

(Please note that the links below are good at the time of writing but cannot be guaranteed for the future.)

Normative References

Normative references for this standard are defined in Section 1.4.

Informative References

The following documents are referenced in this standard:

•   Agile Alliance: Agile Manifesto and Principles (2001); retrieved 4/13/2011, from http://agilemanifesto.org/principles.html.

•   J. Allspaw, J. Robbins: Web Operations, Beijing China, Sebastopol CA, O'Reilly (2010).

•   ASL Foundation: Application Services Library (2005); retrieved 11/13/2005, from www.aslfoundation.org.

•   K. Behr, G. Kim et al: The Visible Ops Handbook – Implementing ITIL in Four Practical and Auditable Steps, Eugene OR, Information Technology Process Institute (2005).

•   R.J. Benson, T.L. Bugnitz et al: From Business Strategy to IT Action – Right Decisions for a Better Bottom Line, New York; Chichester, Wiley (2004).

•   C.T. Betz: Architecture and Patterns for IT: Service and Portfolio Management and Governance (Making Shoes for the Cobbler's Children), 2nd Edition, Amsterdam, Elsevier/Morgan Kaufman (2011).

•   P. Bourque, R.E. Fairley, Eds.: Guide to the Software Engineering Body of Knowledge, Version 3.0, IEEE Computer Society (2014).

•   J.A. Carbone: IT Architecture Toolkit, Upper Saddle River, NJ, Prentice Hall (2004).

•   CMMI Product Team: CMMI for Acquisition, Version 1.3. Pittsburgh PA, Carnegie Mellon Software Engineering Institute (2010).

•   CMMI Product Team: CMMI for Development, Version 1.3, Pittsburgh PA, Carnegie Mellon Software Engineering Institute (2010).

•   CMMI Product Team: CMMI for Services, Version 1.3, Pittsburgh PA, Carnegie Mellon Software Engineering Institute (2010).

•   A. Cockburn: Writing Effective Use-Cases, Boston, Addison-Wesley (2001).

•   M.A. Cook: Building Enterprise Information Architectures – Re-Engineering Information Systems, Upper Saddle River, NJ, Prentice Hall (1996).

•   P.M. Duvall, S. Matyas et al: Continuous Integration – Improving Software Quality and Reducing Risk, Upper Saddle River, NJ, Addison-Wesley (2007).

•   J. Humble, D. Farley: Continuous Delivery, Boston, Addison-Wesley (2011).

•   IEEE 730-2014: IEEE Standard for Software Quality Assurance Processes.

•   ISACA: Control Objectives for Information and Related Technology (COBIT 5); refer to www.isaca.org.

•   ISO/IEC 2005: Regional or National Adoption of International Standards and Other International Deliverables (Guide 21-2).

•   ISO/IEC 2008: Uncertainty of Measurement (Guide 98-3).

•   ISO/IEC 2013: ISO/IEC Directives.

•   ISO/IEC 19770:2012: Information Technology – Software Asset Management.

•   ISO/IEC 20000:2011: Information Technology – Service Management.

•   ISO/IEC 27002:2013: Information Technology – Security Techniques – Code of Practice for Information Security Controls.

•   ISO/IEC 38500:2008: Corporate Governance of Information Technology.

•   ISO/TC 258: Project, Program, and Portfolio Management.

•   J.D. Kaplan: Strategic IT Portfolio Management – Governing Enterprise Transformation, US, Pittiglio Rabin Todd & McGrath Inc. (2005).

•   H. Kern, R. Schiesser et al: IT Production Services, Upper Saddle River, NJ, Prentice Hall Professional Technical Reference (2004).

•   L. Klosterboer: Implementing ITIL Change and Release Management, Upper Saddle River, NJ, IBM; London: Pearson Education [distributor] (2009).

•   D. Leffingwell, A. Yakyma et al: Scaled Agile Framework, from http://scaledagileframework.com (2014).

•   T.A. Limoncelli, S.R. Chalup et al: The Practice of Cloud System Administration: Designing and Operating Large Distributed Systems, Vol. 2, Pearson Education Ltd. (2014).

•   D.C. Luckham: The Power of Events – An Introduction to Complex Event Processing in Distributed Enterprise Systems, Boston, MA; London, Addison-Wesley (2002).

•   B. Maizlish, R. Handler: IT Portfolio Management Step-By-Step: Unlocking the Business Value of Technology, Hoboken, MJ, John Wiley & Sons (2005).

•   J. Martin: Great Transition: Using the Seven Disciplines of Enterprise Engineering, ISBN: 978-0814403150, Amacom (January 1995).

•   F.W. McFarlan: Portfolio Approach to Information Systems, Harvard Business Review 59(5): 142-150 (1981).

•   OASIS: Topology and Orchestration Specification for Cloud Applications (TOSCA), Version 1.0 (2013).

•   G. O’Donnell, C. Casanova: The Configuration Management Database (CMDB) Imperative: How to Realize the Dream and Avoid the Nightmares, Upper Saddle River, NJ, Prentice Hall; London: Pearson Education [distributor] (2009).

•   Office of Government Commerce: Application Management, London, The Stationary Office (2002).

•   M. O’Loughlin: The Service Catalog: A Practitioner Guide, Zaltbommel, The Netherlands, Van Haren Publishing (2009).

•   M. Porter: Competitive Advantage: Creating and Sustaining Superior Performance, ISBN: 978-0684841465, Free Press; 1st Edition (June 1998).

•   Project Management Institute: A Guide to the Project Management Body of Knowledge (PMBOK) (2013).

•   T.A. Quinlan: Chargeback and IT Cost Accounting, Santa Barbara, CA, IT Financial Management Association (2003).

•   T.A. Quinlan, S.J. Quinlan: Readings in IT Financial Management, Santa Barbara, CA, IT Financial Management Association (2003).

•   Rational Software: Rational Unified Process: Best Practices for Software Development Teams (2011).

•   D. Remenyi, A.H. Money et al: The Effective Measurement and Management of ICT Costs and Benefits, Oxford; Burlington, MA, CIMA (2007).

•   R. Schiesser: IT Systems Management, Upper Saddle River, NJ, Prentice Hall (2010).

•   R. Schiesser, H. Kern: Enterprise Computing Institute: IT Systems Management, Upper Saddle River, NJ, Prentice Hall (2002).

•   SOA Reference Architecture, an Open Group Standard (C119), December 2011, published by The Open Group; refer to: www.opengroup.org/bookstore/catalog/c119.htm.

•   S.H. Spewak, S.C. Hill: Enterprise Architecture Planning – Developing a Blueprint for Data, Applications, and Technology, Boston, QED Pub. Group (1993).

•   R. Sturm, W. Morris et al: Foundations of Service-Level Management, Indianapolis, IN, SAMS (2000).

•   The Stationery Office: ITIL Continual Service Improvement, Norwich UK (2011).

•   The Stationery Office: ITIL Service Design, Norwich UK (2011).

•   The Stationery Office: ITIL Service Operation, Norwich UK (2011).

•   The Stationery Office: ITIL Service Strategy, Norwich UK (2011).

•   The Stationery Office: ITIL Service Transition, Norwich UK (2011).

•   TOGAF Version 9.1 (English version), an Open Group Standard, available online at www.opengroup.org/architecture/togaf9-doc/arch, and also available as TOGAF Version 9.1 “The Book” (ISBN: 978 90 8753 6794, G116) at www.opengroup.org/bookstore/catalog/g116.htm.

•   W. Ulrich, N. McWhorter: Business Architecture: The Art and Practice of Business Transformation, Tampa, FL, Meghan-Kiffer (2010).

•   Unified Modeling Language (UML), Object Management Group (OMG); refer to: www.uml.org.

•   W. Van Grembergen: Strategies for Information Technology Governance, Hershey, PA; London, Idea Group Publishing (2004).

•   W. Van Grembergen, S. Haes: Enterprise Governance of Information Technology – Achieving Strategic Alignment and Value, New York, Springer (2009).

•   E.A. Van Schaik: A Management System for the Information Business – Organizational Analysis, Englewood Cliffs; London, Prentice Hall (1985).

•   P. Weill, J.W. Ross: IT Governance – How Top Performers Manage IT Decision Rights for Superior Results, Boston, MA, Harvard Business School; [London: McGraw-Hill] (2004).

1 Introduction

1.1 Objective

This standard is the specification of The Open Group IT4IT Reference Architecture, Version 2.1, an Open Group Standard. It describes a reference architecture illustrated by an IT Value Chain, that can be used to manage the business of IT.

1.2 Overview

The Open Group IT4IT Reference Architecture is a standard reference architecture for managing the business of IT. It uses a value chain approach to create a model of the functions that IT performs to help organizations identify the activities that contribute to business competitiveness. This value chain framework, called the IT Value Chain and specified in this document as part of the IT4IT Reference Architecture (see Section 3.1), applies this concept to IT by defining an integrated IT management framework focusing on the lifecycle of services. It identifies the key things that IT must do – and do well. It allows IT to achieve the same level of business predictability and efficiency that supply chain management has allowed for the business, and was designed by practitioners to be industry, product, and vendor-independent.

1.3 Conformance

Readers are advised to check The Open Group website for any conformance and certification requirements referencing this standard.

1.4 Normative References

The following standard contains provisions which, through references in this standard, constitute provisions of the IT4IT Reference Architecture. At the time of publication, the edition indicated was valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent edition of the standard listed below.

•   ArchiMate®