Training Heights PECB ITIL and TOGAF Alignment

Aligning ITIL/ISO 20000 Service Design

and TOGAF Enterprise Architecture

By

Orlando Olumide Odejide

www.pecb.com www.trainingheights.net

Summary

• How can we ensure we get

Enterprise Architecture and

IT Design Right?

• ITIL Service Design +

TOGAF !!!!!!!!

Business Value from ITIL Service Design

• Reduce Total Cost of Ownership

• Improve Quality and Consistency of Service

• Ease the Implementation of New or Changed

Services

• Improve Effectiveness of Service Management

and IT Processes

• Improve Service Alignment

ITIL 4P’s of Design

• People (Culture, Organization and Skills)

• Processes (How, Where, When, Who and

Why)

• Products (Services, Technology and Tools)

• Partners (Suppliers and Vendors)

Introduction to ITIL Service Design

• ITIL Service Design provides guidance for the

design and development of services and service

management capabilities and practices.

• It covers design principles and methods for

converting strategic objectives into portfolios of

services and service assets.

• The scope of ITIL Service Design includes the

changes and improvements necessary to increase

or maintain value to customers, the continuity of

services, achievement of service levels, and

conformance to standards and regulations.

ITIL Service Design Processes (8)

1. Design Coordination (This is where Architects are needed)

2. Service Catalogue Management (Customer Facing and

Supporting Services)

3. Service Level Management (SLR, SLA, OLA, UC and SIP)

4. Availability Management (Reliability, Maintainability and

Serviceability)

5. Capacity Management (Business, Service and Component)

6. IT Service Continuity Management (BIA and Risk

Assessment)

7. Information Security Management (Information Security

Policy)

8. Supplier Management (Strategic, Tactical, Operational and

Commodity)

Service Design Package (versus ADD in

TOGAF)

• Service Design Package is a document or documents

defining all aspects of an IT service and its requirements

through each stage of its lifecycle.

• It contains elements such as:

– Business requirements

– Service Functional Requirements

– Service Level Requirements

– Service and Operational management requirements

– Service Design and Topology

– Organizational Readiness Assessment

– Service Operational Acceptance Plan

Introduction to TOGAF

• TOGAF is a framework — a detailed method and a set ofsupporting tools — for developing an enterprisearchitecture. It may be used freely by any organizationwishing to develop an enterprise architecture for usewithin that organization.

• The intention of dividing the TOGAF specification intothese independent parts is to allow for different areas ofspecialization to be considered in detail and potentiallyaddressed in isolation.

• Although all parts work together as a whole, it is alsofeasible to select particular parts for adoption whileexcluding others. For example an organization may wishto adopt the ADM process, but elect not to use any of thematerials relating to Architecture Capability.

Enterprise Architecture

• The purpose of enterprise architecture is to optimize

across the enterprise the often fragmented legacy of

processes (both manual and automated) into an

integrated environment that is responsive to change and

supportive of the delivery of the business strategy.

• Today’s CEOs know that the effective management and

exploitation of information through IT is a key factor to

business success, and an indispensable means to

achieving competitive advantage.

• An enterprise architecture addresses this need, by

providing a strategic context for the evolution of the IT

system in response to the constantly changing needs of

the business environment.

Benefits of Enterprise Architecture

• A good enterprise architecture enables you to achieve

the right balance between IT efficiency and business

innovation. It allows individual business units to innovate

safely in their pursuit of competitive advantage.

• It ensures the needs of the organization for an integrated

IT strategy are met, permitting the closest possible

synergy across the extended enterprise.

• It provides a more efficient business operation

• It ensures a more efficient IT operation

• Better return on existing investment, reduced risk for

future investment

• Faster, simpler, and cheaper procurement:

Structure of TOGAF

1. Introduction

2. Architecture Development Method (Phase Narratives)

3. ADM Guidelines and Techniques

4. Architecture Content Framework (Content Metamodel, Artifacts, Deliverables and Building Blocks)

5. Enterprise Continum and Tools (Partioning and Repository)

6. TOGAF Reference Models (Technical Reference and Integrated Information Infrastructure Reference Model)

7. Architecture Capability Framework (Board, Compliance, Contracts, Governance, Maturity Model and Skills Framework)

7 Part Approach to Enterprise Architecture

Structure of TOGAF Document

Architecture Development Method (ADM)

ADM Further Explored

Architecture Definition Document

• Scope

• Goals, Objectives and Constraints

• Compliance

• Risk and Issues (Including Assumptions and Dependencies)

• Baseline Architecture (Business, Data, Application, Technology and Security)

• Rationale and Justification for Architectural Approach

• Mapping to Architecture Repository

• Target Architecture (Business, Data, Application, Technology and Security)

• Gap Analysis

• Impact Assessment

Content and Structure

BTRA – Maturity Model

Content Metamodel Vision and Concepts

Architecture Compliance Review Process

Levels of Architecture Conformance

Conclusion

• Organizations need to explore the value

that TOGAF can bring to them and ensure

they get Enterprise Architecture right.

• They also need to ensure they align

everything they are doing from an ITIL

Service Design perspective to the bigger

umbrella which is the Enterprise

Architecture perspective.

Thank You and Questions

[email protected]

N.B: Content and Diagrams from Axelos ITIL and Open

Group TOGAF Documents.