How To Use The Togaf and IT4IT™ Standards Together: A White Paper by

How to Use the
®
TOGAF and IT4IT™
Standards Together
A White Paper by:

William A. Estrem, Metaplexity Associates
Michael Fulton, Nationwide
Sylvain Marie, Accenture
Łukasz Wrześniewski, Invited Expert
May 2018
How to Use the TOGAF® and IT4IT™ Standards Together
Copyright © 2018, The Open Group

The Open Group hereby authorizes you to use this document for any purpose, PROVIDED THAT any copy of this document,
or any part thereof, which you make shall retain all copyright and other proprietary notices contained herein.
This document may contain other proprietary notices and copyright information.
Nothing contained herein shall be construed as conferring by implication, estoppel, or otherwise any license or right under any
patent or trademark of The Open Group or any third party. Except as expressly provided above, nothing contained herein shall
be construed as conferring any license or right under any copyright of The Open Group.
Note that any product, process, or technology in this document may be the subject of other intellectual property rights
reserved by The Open Group, and may not be licensed hereunder.
This document is provided "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT. Some jurisdictions do not allow the exclusion of implied
warranties, so the above exclusion may not apply to you.
Any publication of The Open Group may include technical inaccuracies or typographical errors. Changes may be periodically
made to these publications; these changes will be incorporated in new editions of these publications. The Open Group may
make improvements and/or changes in the products and/or the programs described in these publications at any time without
notice.
Should any viewer of this document respond with information including feedback data, such as questions, comments,
suggestions, or the like regarding the content of this document, such information shall be deemed to be non-confidential and
The Open Group shall have no obligation of any kind with respect to such information and shall be free to reproduce, use,
disclose, and distribute the information to others without limitation. Further, The Open Group shall be free to use any ideas,
concepts, know-how, or techniques contained in such information for any purpose whatsoever including but not limited to
developing, manufacturing, and marketing products incorporating such information.
If you did not obtain this copy through The Open Group, it may not be the latest version. For your convenience, the latest
version of this publication may be downloaded at www.opengroup.org/library.
This White Paper is an informational document and does not form part of the TOGAF documentation set. Readers should note
that this document has not been approved through the formal Open Group Standards Process and does not represent the formal
consensus of The Open Group Architecture Forum.
ArchiMate®, DirecNet®, Making Standards Work®, OpenPegasus®, Platform 3.0®, The Open Group®, TOGAF®, UNIX®,
UNIXWARE®, and the Open Brand X® logo are registered trademarks and Boundaryless Information Flow™, Build with
Integrity Buy with Confidence™, Dependability Through Assuredness™, Digital Practitioner Body of Knowledge™,
DPBoK™, EMMM™, FACE™, the FACE™ logo, IT4IT™, the IT4IT™ logo, O-DEF™, O-PAS™, Open FAIR™, Open
O™ logo, Open Platform 3.0™, Open Process Automation™, Open Trusted Technology Provider™, SOSA™, and The Open
Group Certification logo (Open O and check™) are trademarks of The Open Group.
ITIL® is a registered trademark of AXELOS Limited.
SCOR™ is a trademark of APICS, Inc.
Zachman® is a registered trademark of Zachman International, Inc.
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.

Document No.: W185
Published by The Open Group, May 2018.

Any 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 email to:
ogpubs@opengroup.org
www.opengroup.org A White P aper P ublished by The Open G roup 2

Table of Contents
Executive Summary................................................................... 5
Introduction .............................................................................. 7
Different Viewpoints.................................................................. 8
The CIO Viewpoint ................................................................................. 8
The Architect Viewpoint ........................................................................ 10
How to Handle Different Viewpoints ...................................................... 11
Using the TOGAF and IT4IT Standards to Transform

Business Capabilities ............................................................... 12
Scenario: Transforming a Collaboration Capability Using the
TOGAF ADM and IT4IT Reference Architecture .................................... 15
Using the TOGAF and IT4IT Standards to Transform an IT

Capability ............................................................................... 19
Architecture Continuum ......................................................................... 19
Enterprise Repository ............................................................................ 21
Architecture Content Metamodel ............................................................ 21
Architecture Development Method (ADM) .............................................. 22
Preliminary Phase .................................................................................. 22
Requirements Management Phase ........................................................... 23
Phase A: Architecture Vision.................................................................. 23
Phase B: Business Architecture .............................................................. 23
Phase C: Data Architecture..................................................................... 23
Phase D: Technology Architecture .......................................................... 23
Phase E: Opportunities and Solutions ...................................................... 24
Phase F: Migration Planning................................................................... 24
Phase G: Implementation Governance Phase............................................ 24
Phase H: Architecture Change Management Phase ................................... 24

Architecture Capability .......................................................................... 24
Conclusion .............................................................................. 25
Appendix A: Definition of Terms ............................................. 26
Appendix B: Terminology Alignment ....................................... 30
Appendix C: Overview of the Standards................................... 31

The TOGAF Standard, Version 9.2 ......................................................... 31
IT4IT Reference Architecture 2.1 ........................................................... 32
References............................................................................... 34
About the ArchiMate® Standard .............................................. 34
About the Authors ................................................................... 35
About The Open Group ........................................................... 36

Boundaryless Information Flow

achieved through global interoperability
in a secure, reliable, and timely manner
Executive Summary
The purpose of this White Paper is to present an approach for how the TOGAF®
Standard and the IT4IT™ Reference Architecture Standard can be used together
effectively and to solicit feedback. The target audience for this White Paper is
practitioners looking for alternative ways to use the two standards together, whether
they need to improve the IT organization or are working to transform their enterprise
into a digital enterprise.
The TOGAF standard is used for delivering Enterprise Architecture and the IT4IT
Reference Architecture is used for managing the business of IT. The TOGAF and
IT4IT standards can be used effectively together to deliver IT services more closely
connected with business needs and also to leverage the Enterprise Architecture
capability through the use of an IT reference architecture.
From the perspective of the Chief Information Officer (CIO), the IT4IT standard is a
useful reference architecture to gain a better understanding of the flow of work and
improvement areas across the organization. The TOGAF framework is important for
making Enterprise Architects more efficient and effective. Together, they can be used
very effectively to transform an organization’s IT capability.
From the perspective of the Enterprise Architect, the TOGAF framework is useful for
understanding the broad organizational landscape and how this high-level view
should be connected with the day-to-day. The IT4IT standard is a valuable reference
model for use in the IT function to give a robust starting point for architecture and to
help speed up work. Together, they can be used very effectively to transform the
business capabilities of the organization.

By using the TOGAF and IT4IT standards together, organizations can speed up
delivery and improve the overall quality of IT services for the business and,
ultimately, increase the business value delivered by IT.

Introduction
Today, the effective management of the IT function is a big challenge for many enterprises. Whether it is a
small, medium, or large-sized organization, the effective management and operations of IT is a key factor
that gives competitive advantage and allows survival in the market.
Currently, IT is considered to be an important business enabler. The use of emerging technologies like cloud,
automation, big data, cybersecurity, Software-Defined Network (SDN), and cognitive systems as well as
agile approaches like DevOps allows IT to deliver products and services faster to market and better address
the customer needs.
IT departments also need to deal with a growing demand from business units for new services. On top of that,
IT must maintain the legacy systems and solve day-to-day critical business problems while dealing with
redundancy, complexity, and out-of-date technologies.
In order for IT to provide better services to the business in an agile and effective way, we need to first build
the capability to fully utilize emerging technologies. Such capability can be only enabled through a proper
architecture that will define the overall IT ecosystem.
In this challenge, standards organizations like The Open Group can play a meaningful role.
The standards created by The Open Group community provide much needed guidance by sharing industry
best practices and by allowing vendors to create a standard portfolio of products and services to fulfill
industry needs.
In this White Paper, we try to guide architects and IT managers on how to use the TOGAF framework and
IT4IT Reference Architecture together. We show two perspectives that can help understand how to create
better services and manage the entire IT ecosystem.
The purpose of this White Paper is to present an approach for how the TOGAF framework and IT4IT
Reference Architecture can effectively be used together and to solicit feedback. We will examine the
relationship between the TOGAF Standard, Version 9.2 (April 2018) and the IT4IT Reference Architecture,
Version 2.1 (February 2017) (see References).
Our target audience for this White Paper is TOGAF or IT4IT practitioners looking for alternative ways to use
the two standards together, whether they need to improve the IT organization or are working to transform
their enterprise into a digital enterprise. For more information about either standard or the terms used in this
White Paper, see Appendix A and Appendix C.

Different Viewpoints
One of the challenges when looking at the TOGAF framework and IT4IT Reference Architecture together is
that they were created for different stakeholder groups. This causes confusion because each stakeholder
group comes with its own perspective or viewpoint. Since the different stakeholders don’t understand that
there are different viewpoints, they may believe that the TOGAF and IT4IT standards are disjointed or in
conflict with each other. It becomes difficult to understand how the two standards can be used together. Let’s
look at the various stakeholders.
The CIO Viewpoint

The first stakeholder is the CIO. For the CIO, there is a significant opportunity to use the IT4IT approach to
look at the organization and better understand the flow of work and improvement opportunities across the
organization. From this strategic perspective, there are two primary views to consider: the IT Value Chain
(Figure 1) and the Level 1 Reference Architecture (Figure 2).
IT Value Chain
Plan Build Deliver Run Efficiency

Service Model Backbone &
Finance & Assets Agility
Sourcing & Vendor
Intelligence & Reporting
Resource & Project
Governance, Risk & Compliance
Figure 1: IT Value Chain

Figure 2: IT4IT Reference Architecture Level 1
From the IT Value Chain view (Figure 1), we can see the major flow of work from plan – Strategy to
Portfolio (S2P); to build – Requirement to Deploy (R2D); to deliver – Request to Fulfill (R2F); and finally to
run – Detect to Correct (D2C). We can then drill down into the Level 1 Reference Architecture (Figure 2)
and see that there are 29 different components of work that must be executed to cover the entire IT Value
Chain. When we look at it from this perspective, Enterprise Architecture is one of the 29 components in the
Reference Architecture.
Figure 3: Enterprise Architecture Component of the IT4IT Reference Architecture Level 1

If we look at it from this perspective, it doesn’t matter whether we use the TOGAF framework, the
Department of Defense Architecture Framework (DoDAF), the Federal Enterprise Architecture Framework
(FEAF), the Zachman® Framework, or any other architecture framework. It simply fits into the Enterprise
Architecture box and needs to be integrated with other parts of the IT organization through the development
of the Service Architecture.
For a CIO, the IT4IT standard enables a view across the entire IT organization; to assess all its functional
components1 for quality or maturity (or whatever other factor is important), and to decide where the biggest
pain points are.
The IT4IT standard also gives the CIO a reference architecture that could be used as a starting point to
understand the data needed to manage an IT organization and for evaluating how well that data is flowing
across the different organizational silos.
The Architect Viewpoint

The second stakeholder to consider is the Enterprise Architect. The job of the Enterprise Architect is to look
across the entire enterprise. A framework like the TOGAF framework is key to understanding both the
overall organization context and also to providing a general overview of the existing capabilities and those
needed to fulfill the organization strategy and address the different stakeholder concerns. The TOGAF
framework identifies three levels of architecture in an organization: strategic, segment, and capability.
Figure 4: TOGAF Architecture Levels
1
Functional component is an IT4IT concept that is defined as the smallest unit of technology that can stand on its own and be useful as a whole for an
IT practitioner. See Appendix B on terminology alignment.

In an enterprise, there will be multiple segments. Examples include Human Resources, Finance, Supply
Chain, and IT. Each of these areas might have an industry reference model appropriate for use for one or
several of the areas. Examples include ARTS, Banking Industry Architecture Network (BIAN), Supply Chain
Operations Reference Model (SCOR™), Value Chain Group (VCG), American Productivity & Quality
Center (APQC), or many others. The IT4IT standard proposes a reference architecture for managing the IT
segment, as well as providing us with the details we need to understand how IT works.
As an Enterprise Architect goes through an iteration of the TOGAF Architecture Development Method
(ADM) to develop architecture for a portion of their enterprise, they would pick and choose appropriate
reference models to help them do their work. From this perspective, it doesn’t matter if we are using the
IT4IT Reference Architecture, ITIL®, Technology Business Management (TBM), or any combination of IT
management frameworks as a reference model for the IT segment.
How to Handle Different Viewpoints

Both viewpoints – the CIO’s and the Enterprise Architect’s – are equally important. The CIO can get
significant value from using the IT4IT standard in a top-down manner as a strategic assessment tool to drive
improvement across the IT function and help transform the IT operating model. From this viewpoint, the
IT4IT standard is a valuable addition and the TOGAF standard is an important piece of the puzzle.
The Enterprise Architect can get significant value from using the TOGAF standard as the method for doing
work, and using the IT4IT standard in a bottom-up manner as a reference model to speed up architecture
work in the IT segment and to drive vendor integration and standardization in the IT management tool space.
From this viewpoint, the TOGAF standard is much more critical to overall success and the IT4IT standard is
a beneficial tool for the toolbox.
Regardless of your viewpoint, the TOGAF and IT4IT standards are mutually supportive. This White Paper
will continue to cover in more detail how the two standards can work together.

Using the TOGAF and IT4IT Standards to Transform Business

Capabilities
As we said earlier in this White Paper, the IT4IT standard offers a significant opportunity for a CIO to look at
his or her organization and better understand the flow of work and assess potential improvement
opportunities. There is a small box in the overall IT4IT Reference Architecture called Enterprise
Architecture. Our goal in this section is to clarify how this Enterprise Architecture functional component
works with other parts of the IT organization.
For this purpose, we focus on the most essential element of each standard trying to understand the
interactions between the two: the TOGAF ADM cycle and the IT4IT service lifecycle. We then illustrate
these interactions through a scenario of improving a messaging and collaborative capability.
In the IT4IT Reference Architecture specification (see Figure 5) the Enterprise Architecture functional
component takes the Business Process from the Business Strategy in input and produces a conceptual service
blueprint as an output to the Service Portfolio functional component.
• Identify strategic IT architectural components

• Develop target state business, information, application,
technology, and security blueprints
• Create and manage long-term IT investments and
execution plan-of-action
Figure 5: The Enterprise Architecture Functional Component in the IT4IT Standard
Table 1: Mapping the Enterprise Architecture Functional Component Functions with TOGAF Concepts and ADM Phases
Enterprise Architecture Functional Component Functions TOGAF Concepts
Identify strategic IT architectural components ADM Phases A, B, C, D
Develop target state business, information, application, ADM Phases A, B, C, D

technology, and security blueprints
Create and manage long-term IT investments and execution ADM Phases E, F

plan-of-action
As we can see in Table 1, most of the Enterprise Architecture functional component functions relate to the
ADM phases, or more precisely to the development phases (B to F) as they are called in the TOGAF
framework. It is, however, important to note that the IT4IT standard is also valuable in the Preliminary Phase,

helping to understand and define the interaction of the Enterprise Architecture capability with the rest of the
organization.
What comes out from ADM Phases B, C, and D are Target Architecture views to show stakeholders that their
concerns have been considered. These views contain Architecture Building Blocks and relationships. Some
of these building blocks are good candidates to give rise to conceptual services, which populate the Service
Portfolio. The Architecture Building Blocks identified in each architecture domain in Phases B, C, and D will
produce related types of services: Business Services in Phase B, IT Services in Phase C, and Infrastructure
Services in Phase D (see Figure 6).
The decision to create a service from an Architecture Building Block is an IT strategic decision based on the
re-usability of the components or the service-level commitments that are needed for that component.
Business
Service
IT Service
Infra.
Service
Solutions Roadmap
Service Portfolio
Projects Portfolio
Figure 6: Populating the Service Portfolio
The Service Portfolio is the starting point of the service lifecycle where the service is first defined in high-
level terms. The ADM Phases E and F will build the IT roadmap by choosing solutions to new Architecture
Building Blocks and grouping the work to be done into work packages. These activities are realized in
collaboration between Enterprise Architects, service owners, and project teams. Choosing solutions is part of
the Service Design functional component and evaluating resources and costs of projects is in the Proposal
functional component and IT Investment Portfolio functional component. The Requirements Management
phase in the TOGAF standard is used to manage Enterprise Architecture requirements. The Requirement
functional component in the IT4IT standard will identify and manage requirements at the project level, but
there is obviously a relationship between the two sets of requirements.

Portfolio
Demand
Component
Enterprise
Architecture
Component
Project Service
Component Portfolio
Service
Project Portfolio
Component Component
Service
Design
Component
Figure 7: The TOGAF ADM and IT4IT Functional Components
The Enterprise Architecture development ends in Phase F. The next phase, Phase G, is a governance phase
where Enterprise Architecture will ensure that projects outcomes are compliant with Enterprise Architecture
blueprints and principles. TOGAF governance can support IT4IT governance and change management from
a high-level perspective. The Service Design functional component will produce detailed architecture
documents to be reviewed for compliance by the architecture governance board. The remaining IT4IT
functional components from the R2D and R2F value streams will be involved also in Phase G. Enterprise
Architects will assist project teams and service owners throughout the Service Design and deployment stages.

Detect to
Correct Strategy to
Portfolio
Enterprise
Architecture
Component
Request to
Fulfill
Service
Portfolio
Requirement
to Deploy
Figure 8: The TOGAF ADM and IT4IT Value Streams
Figure 8 is a summary of interactions between the ADM phases and IT4IT value streams. However, D2C and
R2F are not directly involved with Enterprise Architecture. During Phase G, Solution Building Blocks will be
developed, integrated, and deployed to become operational services. These tasks are supported by the
functional components of the R2D and R2F value streams.
Phase H is a maintenance phase for the realized architecture. Any event, business or technological, that
implies an architecture change will be recorded as a change request and will trigger an architecture update.
The D2C value stream will contribute to the detection of such events through the Incident and Problem
functional components.
Scenario: Transforming a Collaboration Capability Using the TOGAF ADM and IT4IT
Reference Architecture
To illustrate how an Enterprise Architecture framework like the TOGAF framework and the IT4IT Reference
Architecture can work together to transform an IT capability, we will go through an ADM cycle transforming
the collaboration capability of a fictitious company. This scenario will use the ArchiMate ® language as a
modeling tool (see Appendix A for a description of the ArchiMate language).
For the purposes of our scenario, a major manufacturing company, located in 35 countries around the world,
has decided to improve its collaboration capability due to current architecture obsolescence and a demand
from users to improve functionalities. The business sponsor has made a request to the Enterprise Architecture
team to build a transformation plan with projects and associated costs for the new capability.
Enterprise Architecture is using the TOGAF standard as an architecture framework and will follow the ADM
method. The following, simple example will run through the ADM phases and explain how architecture work
will help in populating the Service Portfolio.

Phase A: Architecture Vision
• Identify stakeholders and their concerns
• Collect high-level goals:
— Obsolescence of the current architecture

— Security improvement
— New needs around collaboration: new collaborative services
— Infrastructure, architecture simplification
— Realigned with state-of-the-art
• Collect and define enterprise principles in the domain of communication, collaboration, security, and
architecture
• Draft an Architecture Vision to obtain sponsor approval
Phase B: Business Architecture
The Enterprise Architecture team collects detailed business requirements and develops Business Architecture
views. Requirements are also based on the portfolio backlog items from the IT4IT Portfolio Demand
functional component.
A simple example of an architecture view that shows business services for the messaging and collaborative
capability is useful in this context. We do not know yet if these services will be based on IT technology and
competencies.
Business Service
Product
Figure 9: Target Business Services Architecture
Phase C: Information Systems Architecture (Application and Data)
Architects develop the Application and Data Architecture that will enable the Business Architecture. The
architecture view (Figure 10) shows the IT services and application components that will support the business

services. Enterprise Architects and the Service Portfolio will decide how these IT services will populate the
Service Portfolio.
Application Component
Application Service
Realization Relation
Figure 10: Target Application Architecture
Phase D: Technology Architecture
In this scenario, the new applications will use the internal network infrastructure of the enterprise and the
Internet for external communications. The only new infrastructure service that will add to the Service
Portfolio is a secure network for external document sharing.
Phase E: Opportunities and Solutions
From the previous work in Phases B to D, the Enterprise Architecture team and IT4IT Service Design
identify any existing enterprise solutions they can use, or new solutions that need to be implemented.
Service Solution
Web conferencing Web solution for remote conferences
Instant messaging Solution for messaging
Whiteboard sharing Solution for content sharing
Secure calendar/email Mail and calendar solution
Non secure calendar/email Non-secure email solution
Phase F: Migration Planning
In Phase F, the transformation plan has to be finalized with a roadmap of projects that build the new
architecture. This activity involves IT4IT Proposal functional component and IT Investment Portfolio
functional component in order to finalize the budget, cost/benefits of each project.

Service Project
Web conferencing, instant messaging, and whiteboard Solution implementation project
Secure calendar/email Solution migration project
Non-secure calendar/email Non-secure solution implementation project
Phase G: Architecture Governance
In Phase G, IT teams take the leadership to develop, implement, and support new services under the
governance of Enterprise Architects to ensure that delivered service systems are compliant with the designed
architecture.

Using the TOGAF and IT4IT Standards to Transform an IT Capability

In this section, we will look at the perspective of an Enterprise Architect who is using the TOGAF and IT4IT
standards to transform the IT function. The IT4IT standard is considered to be a reference architecture that
could be used to define the target state of the IT function within the enterprise. The TOGAF standard is
considered in this case as a transformation framework that supports the transformation to the target state.
There are several use and tailoring points between the TOGAF and IT4T standards that should be considered.
Vision of IT Business
New IT Capabilities
Figure 11: Tailoring Points Between the TOGAF and IT4IT Standards
Architecture Continuum
The IT4IT Reference Architecture is communicated using multiple levels of abstraction. Each abstraction
level expands on the previous level to expose more details and prescriptive guidance.

Level 1: End-to-End Overview
Level 2: Value Stream Documentation
Level 3: Vendor-independent Architecture
Level 4: Vendor-specific Refinement Architecture
Level 5: Solution Architecture
Figure 12: IT4IT Reference Architecture Levels of Abstraction
The upper levels (1-3) are vendor-agnostic and provide generic views that are suitable for strategy and
planning purposes as well as for creating IT management product roadmaps.
The lower levels (4-5) provide more specific details, ultimately arriving at implementation-level or vendor-
owned/controlled information. Content at these levels is suitable for developing implementation plans and for
facilitating product design.
The IT4IT Levels 1-3 should be considered as a Common Systems Architecture and the vendor-specific
Levels 4-5 should be considered as a Common Systems Solution.
IT4IT Reference
Architecture
Enterprise Continuum
(Level 1-3)
Vendor-agnostic
IT4IT Reference
Architecture
(Level 4-5)
Vendor-specific
Figure 13: Mapping IT4IT to the TOGAF Enterprise Continuum

Enterprise Repository
The IT4IT Reference Architecture specification will be documented in several parts of the Architecture
Repository:
• In the Reference Library as an architectural reference model
• In the Architecture Landscape where the architect will put the specifications of the Architecture Building
Blocks based on the IT4IT Reference Architecture; this will touch the Strategic Architectures, Segment
Architectures, and Capability Architectures
Within the Solution Repository the architects will place the Solution Building Blocks based on vendor-
specific Levels 4 and 5 of the IT4IT Reference Architecture.
IT4IT Reference
IT4IT Functional Architecture
Components and
Data Objects
Deployed Solutions
with IT4IT Standards
Figure 14: Mapping IT4IT Content to the Enterprise Repository
Architecture Content Metamodel

The use of the IT4IT standard will demand the use of selected TOGAF Content Metamodel extensions to
describe the architecture aligned with the IT4IT standard. The use of the IT4IT standard will lead the
enterprise to service-orientation.

The following selected extensions are worth considering:
• Data extension
• Service extension
• Process extension
• Infrastructure Consolidation extension
Architecture Development Method (ADM)

The ADM will play the main role with transforming the IT function. The IT4IT Reference Architecture will
be used as a reference resource to design the architecture for selected domains.
Reflecting the IT4IT

model in the Enterprise
Architecture capability –
tailoring the TOGAF
Establishing value framework to implement
monitoring and change the IT4IT standard
management process
Defining the vision of the

IT capability aligned with
Architectural oversight the IT4IT standard as a
over implementation of reference model
the IT4IT Reference
Architecture
Defining the architectures

in all domains that reflect
the IT4IT standard as a
reference model
Detailed planning of the
transformation to
service broker model
Choosing the solutions
that will implement IT4IT
functional components
and initial transformation
planning
Figure 15: Using the TOGAF ADM and the IT4IT Reference Architecture to Transform IT Capability
Preliminary Phase
The main objective of the Preliminary Phase is to establish the architecture capability that will give the
enterprise the ability to design and manage the Enterprise Architecture.
In the case of using the TOGAF standard to establish an IT capability based on the IT4IT Reference
Architecture, the Enterprise Architecture capability should consist of people with specific skills, including
knowledge and experience of IT4IT Reference Architecture as well as experience of solutions that support
the service lifecycle.

An important part of the Preliminary Phase is also to establish Enterprise Architecture principles. These
principles should be aligned with the IT4IT Reference Architecture and support the goals and courses of
action that this standard brings to the organization; e.g., service-orientation, agility, common use of
applications, and interoperability.
Requirements Management Phase

During the Requirements Management phase, the IT4IT Reference Architecture could be used as a source
material to identify the architecture requirements.
Phase A: Architecture Vision

In the Architecture Vision phase, the specific enhancement will cover the use of the IT4IT standard as a
reference for determining the desired capability of the IT segment. The IT4IT Reference Architecture Level 1
could be used as input into preparing the capability map for the IT segment.
The architecture project will be scoped to the IT segment level of detail and all architectural domains. The
reference set of Key Performance Indicators (KPIs) for each value stream will be considered.
Phase B: Business Architecture

In regards to the Business Architecture phase, the IT4IT standard does not explicitly provide a Business
Architecture, but will provide crucial reference information.
• The functional model will determine the set of responsibilities and will impact the structure of sub-
functions within IT
• The value stream activities will determine the processes that should be executed
Phase C: Data Architecture

In Phase C, Data Architecture, the system of record2 will provide the reference for the Data Architecture of
the IT function. The functional components will determine the functionalities of the application components.
Phase D: Technology Architecture

The IT4IT standard does not provide direct guidance about the Technology Architecture; although based on
the structure of functional components and data objects, the architects could define the Business, Data, and
Application Architectures that are the prerequisites to the Technology Architecture.
2
The system of record in the IT4IT standard is composed of data objects, combined with their relationships and inter-dependencies for IT management.

Phase E: Opportunities and Solutions

During the Opportunities and Solutions phase the architect could use Solution Building Blocks from vendor-
specific Level 5 (Solution Architecture) as a selected solution that will implement the Architecture Building
Blocks based on Levels 1 to 3 of the IT4T Reference Architecture.
Phase F: Migration Planning

During the Migration Planning phase the architects and implementation body representatives can use
reference information about timings, costs, and required resources that are needed to implement the solutions
aligned with the IT4IT Reference Architecture.
Phase G: Implementation Governance Phase

During the Implementation Governance phase assuring the compliance with the IT4IT Reference
Architecture will be the core responsibility of the architects as well as the proper guidance for
implementation teams.
Phase H: Architecture Change Management Phase

During the Architecture Change Management phase, the implemented architecture is monitored and
continuously improved. The KPIs established for each value stream are monitored and, based on feedback
information, the architect can identify new architecture requirements to achieve expected performance.
Architecture Capability
The IT4IT Reference Architecture defines the set of functional components that could be mapped to the set of
capabilities. Each capability needs selected skills to be operational; e.g., the Project functional component
that manages IT initiatives will demand project management skills. Being able to properly apply the IT4IT
standard will also require specialized knowledge and skills – refer to The Open Group IT4IT Certification
Program at www.opengroup.org/certifications/it4it.

Conclusion
The TOGAF and IT4IT standards are used to develop and maintain better IT services and to manage the
entire IT ecosystem. Whereas the TOGAF standard is a framework to help implement an Enterprise
Architecture capability in any type of organization, the IT4IT standard is a reference architecture specific to
the IT organization that helps to run IT as a business. This White Paper explains how we can use the two
standards together in two ways.
The first one shows how to use the Enterprise Architecture capability and the TOGAF ADM to transform an
IT capability by using the information and functional model proposed by the IT4IT Reference Architecture.
The second one explains how an IT organization built and operated according to the operating model
described in the IT4IT Reference Architecture can efficiently work and collaborate with the Enterprise
Architecture organization to build the new digital enterprise.
Using the industry-leading TOGAF and IT4IT standards individually can save your organization
considerable time and money. Using the two standards together will only increase the value delivered back to
the business.

Appendix A: Definition of Terms

Application Component (TOGAF Standard)
An encapsulation of application functionality aligned to implementation structure, which is modular and

replaceable. It encapsulates its behavior and data, provides services, and makes them available through
interfaces.
Architecture Development Method (TOGAF Standard)
The core of the TOGAF standard. A multi-phase, iterative approach to develop and use an Enterprise
Architecture to shape and govern business transformation and implementation projects.
Application Component (ArchiMate 3.0.1 Specification)
Represents an encapsulation of application functionality aligned to implementation structure, which is

modular and replaceable.
Application Service (ArchiMate 3.0.1 Specification)
Represents an explicitly defined exposed application behavior.
Artifact (TOGAF Standard)
An architectural work product that describes an aspect of the architecture.
Artifact (IT4IT Reference Architecture, Version 2.1)
The specification of a physical piece of information that is used or produced by a software development
process, or by deployment and operation of a system. Examples of artifacts include model files, source files,
scripts, and binary executable files, a table in a database system, a development deliverable, a word-
processing document, or a mail message.
Building Block (TOGAF Standard)
A (potentially re-usable) component of enterprise capability that can be combined with other building blocks
to deliver architectures and solutions.
Data Entity (TOGAF Standard)
An encapsulation of data that is recognized by a business domain expert as a thing. Logical data entities can
be tied to applications, repositories, and services and may be structured according to implementation
considerations.
Data Object (IT4IT Reference Architecture, Version 2.1)
Data or records produced and/or consumed to advance or control the service model as it progresses through
its lifecycle phases. Data objects can take a physical or digital form and are produced, consumed, or modified
by functional components. Within the IT4IT Reference Architecture there are two classifications of data
objects:
• Key – those that are essential to managing or advancing the service lifecycle

• Auxiliary – those that are important but not essential
Data Object (ArchiMate 3.0.1 Specification)
Represents data structured for automated processing.
Functional Component (IT4IT Reference Architecture, Version 2.1)
A software building block. The smallest unit of technology in the IT4IT Reference Architecture that can
stand on its own and be useful as a whole to an IT practitioner (or IT service provider). Functional
components must have defined inputs and outputs that are data objects and they must have an impact on a
key data object.
Relationship (IT4IT Reference Architecture, Version 2.1)
Primarily used to depict the connections between (or interactions with) data objects. In the IT4IT Reference
Architecture, relationships are based on three design principles:
• System of record – used to depict the relationships used to control authoritative source data via a system-
to-system interface
These relationships are prescriptive in that they must be maintained to ensure the integrity of the IT4IT
Reference Architecture.
• System of engagement – used to describe the relationships between data objects and humans or
functional components via a user experience interface
• System of insight – used to describe relationships between data objects for the purpose of generating
knowledge, information, or analytics
Metamodel (TOGAF Standard)
A model that describes how and with what the architecture will be described in a structured way.
Product (ArchiMate 3.0.1 Specification)
A coherent collection of services and/or passive structure elements, accompanied by a contract/set of

agreements, which is offered as a whole to (internal or external) customers.
Reference Architecture (IT4IT Reference Architecture, Version 2.1)
The IT4IT Reference Architecture provides a prescriptive approach to support the value chain-based IT
organization and service-centric IT management ecosystem. The service-centric IT management ecosystem
comprises internal IT functions, external tool vendors, IT management improvement consultancies, external
IT service providers (both XaaS and traditional consultancy and outsourcing services), external IT
component providers (facilities, hardware, software, data), and training and certification providers. It can be
thought of as describing the IT management, segment architecture, and relationships.

Reference Architecture (TOGAF Standard)
The TOGAF standard provides the definition3 of a reference model:
An abstract framework for understanding significant relationships among the entities of [an] environment,
and for the development of consistent standards or specifications supporting that environment.
Requirement (TOGAF Standard)
This refers to a statement of need that must be met by a particular architecture or work package.
Requirement Data Object (IT4IT Reference Architecture, Version 2.1)
A record, which details the needs or conditions to meet for a new or altered service.
IT Service (IT4IT Reference Architecture, Version 2.1)
Refers to a performance of an act that applies computing and information management competencies or
resources for the benefit of another party.
Service (TOGAF Standard)
1. A repeatable activity; a discrete behavior that a building block may be requested or otherwise triggered
to perform.
2. An element of behavior that provides specific functionality in response to requests from actors or other
services.
In addition it defines:
• Business Service: supports business capabilities through an explicitly defined interface and is explicitly
governed by an organization
• Information System Service:
— A discrete behavior requestable from an application (e.g., log in, book train seat, transfer money)
— The automated elements of a business service
• Technology Service: a technical capability required to provide enabling infrastructure that supports the
delivery of applications
Service (ArchiMate 3.0.1 Specification)
An explicitly defined exposed behavior, defined at the business, application, and technology layer.
Service Lifecycle Backbone (IT4IT Reference Architecture, Version 2.1)
The structure that binds the different abstraction levels of the service model together.
3
The source of this definition is OASIS; refer to www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm.

System Service (IT4IT Reference Architecture, Version 2.1)
The set of integrated resources across multiple resource domains including human, financial, information,
and technology that are needed to successfully implement the service offer and carry out the service
interaction.
Value Chain (TOGAF Standard)
A representation of an end-to-end collection of value-adding activities that create an overall result for a
customer, stakeholder, or end user.
Value Stream (IT4IT Reference Architecture, Version 2.1)
Describes the key activities for a discrete area within the IT Value Chain where some unit of net value is
created or added to the service as it progresses through its lifecycle. The IT4IT standard describes four value
streams (Strategy to Portfolio, Requirement to Deploy, Request to Fulfill, and Detect to Correct).

Appendix B: Terminology Alignment

Table 2 shows the terms from different standards that have similar definitions.
Table 2: Standard Definitions
TOGAF Standard ArchiMate 3.0 Standard IT4IT Reference Architecture
Application component Application component Functional component
Data entity Data object Data object
Service Service
Business service Product IT service
Application service System service
Reference architecture Reference architecture
Value stream Value stream

Appendix C: Overview of the Standards

The TOGAF Standard, Version 9.2
The TOGAF standard is an industry-leading open architecture framework that provides the methods and tools
for assisting in the acceptance, production, use, and maintenance of Enterprise Architecture. It is based on an
iterative process model supported by best practices and a re-usable set of existing architecture assets.
Figure 16: Main Elements of the TOGAF 9.2 Standard
The TOGAF standard includes:
• The Architecture Development Method (ADM) that helps architects to define a step-by-step approach for
delivering Enterprise Architectures
The method is iterative and can be adapted to a variety of other frameworks and business environments.

• A set of guidelines and techniques that support the architectural process and provide the architects with
guidance on how to perform specific steps during the process
• The Content Metamodel and a set of re-usable architectural artifacts and deliverables that can be re-used
by architects for developing architectures
• The Enterprise Continuum and tools that help to classify the architectural content and support
communication about the re-use of architectural assets
In the Enterprise Continuum part, the TOGAF standard provides architects with the model of the
Architecture Repository.
• The Architecture Capability Framework that covers guidance about establishing architectural practice
within enterprise and architecture governance
IT4IT Reference Architecture 2.1

IT Value Chain
Plan Build Deliver Run Efficiency

Service Model Backbone &
Finance & Assets Agility
Sourcing & Vendor
Intelligence & Reporting
Resource & Project
Governance, Risk & Compliance
Figure 17: IT Value Chain
The Open Group IT4IT Reference Architecture is a standard reference architecture and value chain-based
operating model 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. The IT Value Chain shown in Figure 17 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.
The functional components in the IT Value Chain are grouped into four primary IT value streams and five
supporting activities, as follows.
The primary value streams for the IT Value Chain are:
• Strategy to Portfolio (S2P)
• Requirement to Deploy (R2D)

• Request to Fulfill (R2F)
• Detect to Correct (D2C)
The primary activities are core to the IT function and have a vital role in helping to holistically run the full-
service lifecycle. These are usually hosted within IT.
The supporting activities for the IT Value Chain are:
• Finance & Assets
• Sourcing & Vendor
• Intelligence & Reporting
• Resource & Project
• Governance Risk & Compliance
The supporting activities help ensure the efficiency and effectiveness of the IT Value Chain and primary
value streams. These can be corporate or administrative functions that are hosted in the lines of business
and/or IT.
This standard defines the value streams, functional components, and associated data objects that are critical to
the service lifecycle, as depicted in Figure 18.
Figure 18: IT4IT Reference Architecture Level 1

References
(Please note that the links below are good at the time of writing but cannot be guaranteed for the future.)
• The Open Group IT4IT™ Certification Program; refer to: www.opengroup.org/certifications/it4it
• The Open Group IT4IT™ Reference Architecture, Version 2.1, an Open Group Standard (C171),
February 2017, published by The Open Group; refer to: www.opengroup.org/library/c171
• The TOGAF® Standard, Version 9.2, a standard of The Open Group (C182), April 2018, published by
The Open Group; refer to: www.opengroup.org/library/c182
About the ArchiMate® Standard

ArchiMate, an Open Group standard, is The Open Group open and independent modeling language for
Enterprise Architecture, supported by different tool vendors and consulting firms. The ArchiMate standard
provides instruments to support Enterprise Architects in describing, analyzing, and visualizing the
relationships among business domains in an unambiguous way. Well-established disciplines like civil
engineering or building and construction use internationally accepted standards for describing their designs.
Just like an architectural drawing in classical building architecture describes the various aspects of the
construction and use of a building, the ArchiMate standard offers a common language for describing the
construction and operation of business processes, organizational structures, information flows, IT systems,
and technical infrastructure. This insight helps stakeholders to design, assess, and communicate the
consequences of decisions and changes within and between these business domains.
The Open Group ArchiMate Forum maintains the ArchiMate standard. The Forum is actively working on its
adoption and further development.
The ArchiMate 3.0.1 Specification is available at www.opengroup.org/library/c179.

About the Authors

William A. Estrem, Metaplexity Associates
Bill Estrem (www.linkedin.com/in/metaplexity) is currently President at Metaplexity Associates, where he

has worked with several large organizations to develop technology strategies and enterprise information
architectures. He has also developed technical architectures for information security and directory services
and is one of the world’s leading TOGAF trainers.
Michael Fulton, Nationwide
Michael Fulton (www.linkedin.com/in/michaelfulton) is currently AVP, IT Strategy & Innovation at

Nationwide. Michael is an experienced architect with over 10 years of experience in Enterprise Architecture
and over 20 years of IT experience. He is TOGAF Certified, IT4IT Certified, and a Cloud Certified Architect
and has led IT4IT Architecture, Cloud Architecture, IT Strategic Planning, Disruptive Cost Innovation, IT
Leadership Development, and Enterprise Architecture Capability & Training Development at a Fortune 50
Company. Michael also spent time working across the entire IT Lifecycle, including time in Service
Management, Program Management, Project Management, Application Development, and IT Operations.
Michael is an experienced speaker and trainer, a practiced leadership and strategy coach and mentor, and is
well known across the industry. He brings a strategic viewpoint and the ability to communicate with all levels
of the organization.
Sylvain Marie, Accenture
Sylvain Marie (www.linkedin.com/in/sylvain-marie-b101341) is currently IT4IT Lead Architect at Accenture

where he focuses on ITIL Process Design and implementation as well as IT4IT Architecture. Sylvain has 10
years of experience in Enterprise Architecture and more than 20 years in IT Service Management. He is
TOGAF Certified, IT4IT Certified, and ITIL Expert Certified. He has led ITSM and IT4IT projects in major
European companies and is also an experienced TOGAF, IT4IT, and ITIL trainer.
Łukasz Wrześniewski, Invited Expert
Łukasz Wrześniewski (www.linkedin.com/in/lukaszwrzesniewski) works as an Agile Transformation and

Enterprise Architecture consultant. He specializes in Agile Enterprise Architecture and Agile Program
Management. He provides accredited TOGAF, IT4IT, ArchiMate, and Scaled Agile training courses.

About The Open Group

The Open Group is a global consortium that enables the achievement of business objectives through
technology standards. Our diverse membership of more than 600 organizations includes customers, systems
and solutions suppliers, tools vendors, integrators, academics, and consultants across multiple industries.
The Open Group aims to:
• Capture, understand, and address current and emerging requirements, establish policies, and share best
practices
• Facilitate interoperability, develop consensus, and evolve and integrate specifications and open source
technologies
• Operate the industry’s premier certification service
Further information on The Open Group is available at www.opengroup.org.

How To Use The Togaf and IT4IT™ Standards Together: A White Paper by

Uploaded by

Copyright:

Available Formats

How To Use The Togaf and IT4IT™ Standards Together: A White Paper by

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

How To Use The Togaf and IT4IT™ Standards Together: A White Paper by

Uploaded by

Copyright:

Available Formats

How to Use the

A White Paper by:

Copyright © 2018, The Open Group

How to Use the TOGAF® and IT4IT™ Standards Together

Published by The Open Group, May 2018.

www.opengroup.org A White P aper P ublished by The Open G roup 2

Using the TOGAF and IT4IT Standards to Transform

Using the TOGAF and IT4IT Standards to Transform an IT

www.opengroup.org A White P aper P ublished by The Open G roup 3

Architecture Capability .......................................................................... 24

Appendix A: Definition of Terms ............................................. 26

Appendix B: Terminology Alignment ....................................... 30

Appendix C: Overview of the Standards................................... 31

About the ArchiMate® Standard .............................................. 34

About the Authors ................................................................... 35

About The Open Group ........................................................... 36

www.opengroup.org A White P aper P ublished by The Open G roup 4

Boundaryless Information Flow

www.opengroup.org A White P aper P ublished by The Open G roup 5

www.opengroup.org A White P aper P ublished by The Open G roup 6

www.opengroup.org A White P aper P ublished by The Open G roup 7

The CIO Viewpoint

Plan Build Deliver Run Efficiency

Intelligence & Reporting

Resource & Project

Governance, Risk & Compliance

Figure 1: IT Value Chain

www.opengroup.org A White P aper P ublished by The Open G roup 8

Figure 2: IT4IT Reference Architecture Level 1

Figure 3: Enterprise Architecture Component of the IT4IT Reference Architecture Level 1

www.opengroup.org A White P aper P ublished by The Open G roup 9

The Architect Viewpoint

Figure 4: TOGAF Architecture Levels

www.opengroup.org A White P aper P ublished by The Open G roup 10

How to Handle Different Viewpoints

www.opengroup.org A White P aper P ublished by The Open G roup 11

Using the TOGAF and IT4IT Standards to Transform Business

• Identify strategic IT architectural components

Figure 5: The Enterprise Architecture Functional Component in the IT4IT Standard

Enterprise Architecture Functional Component Functions TOGAF Concepts

Identify strategic IT architectural components ADM Phases A, B, C, D

Develop target state business, information, application, ADM Phases A, B, C, D

Create and manage long-term IT investments and execution ADM Phases E, F

www.opengroup.org A White P aper P ublished by The Open G roup 12

Figure 6: Populating the Service Portfolio

www.opengroup.org A White P aper P ublished by The Open G roup 13

Figure 7: The TOGAF ADM and IT4IT Functional Components

www.opengroup.org A White P aper P ublished by The Open G roup 14

Figure 8: The TOGAF ADM and IT4IT Value Streams

www.opengroup.org A White P aper P ublished by The Open G roup 15

Phase A: Architecture Vision

• Identify stakeholders and their concerns

• Collect high-level goals:

— Obsolescence of the current architecture

• Draft an Architecture Vision to obtain sponsor approval

Phase B: Business Architecture

Figure 9: Target Business Services Architecture

Phase C: Information Systems Architecture (Application and Data)

www.opengroup.org A White P aper P ublished by The Open G roup 16