ITIL 2011 At a Glance. John O. Long

ITIL 2011 At a Glance John O. Long

SpringerBriefs in Computer Science Series Editors Stan Zdonik Peng Ning Shashi Shekhar Jonathan Katz Xindong Wu Lakhmi C. Jain David Padua Xuemin Shen Borko Furht VS Subrahmanian Martial Hebert Katsushi Ikeuchi Bruno Siciliano For further volumes: http://www.springer.com/series/10028

John O. Long ITIL 2011 At a Glance

John O. Long Raleigh, NC, USA johnoflong@gmail.com ISSN 2191-5768 ISBN 978-1-4614-3896-0 DOI 10.1007/978-1-4614-3897-7 Springer New York Heidelberg D ordrecht London Library of Congress Control Number: 2012939343 The Autho r 2012 This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher s location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law. The use of general descriptive names, registered names, trademarks, marks, etc. in thi s publication does not imply, even in the absence of a specific statement, that such names are exemp t from the relevant protective laws and regulations and therefore free for general use. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein. Printed on acid-free paper ISSN 2191-5776 (electronic) ISBN 978-1-4614-3897-7 (ebook) Springer is part of Springer Science+Business Media (www.springer.com)

Copyright and Legal Information ITIL is a Registered Trade Mark, and a Registered Community Trade Mark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. ITIL Glossaries/Acronyms Crown Copyright Office of Government Commerce. Reproduced with the permission of the Controller of HMSO and the Office of Government Commerce. BPMN workflow diagrams created using BizAgi Process Modeler by BizAgi Ltd. This book is currently under consideration by publishers. This book may only be distributed by the author for evaluation purposes.

Table of Contents Introduction... 1 Purpose... 1 Audience... 1 Organization of the Book... 1 For more information... 2 List of ITIL Processes... 3 Strategy... 5 Overview Diagram... 6 Strategy Key Concepts... 7 Strategy for IT s... 12 Architecture Considerations... 13 Portfolio... 14 Financial for IT s... 16 Architecture Considerations... 18 Demand... 20 Architecture Considerations... 21 Business Relationship... 22 Architecture Considerations... 23 Other Practices... 24 Design... 25 Brief Description... 25 Design Key Concepts... 27 Design Coordination... 28 Architecture Considerations... 31 Catalog... 32 Level... 34 Capacity... 36 Availability... 40 IT Continuity... 44 Information Security... 46

viii Table of Contents Supplier... 48 Other Practices... 50 Additional Design Roles... 50 Transition... 51 Transition Key Concepts... 52 Asset and Configuration... 56 Change... 60 Release and Deployment... 62 Validation and Testing... 64 Transition Planning and Support... 66 Knowledge... 68 Change Evaluation... 70 Other Practices... 72 Additional Transition Roles... 72 Operation... 73 Operation Key Concepts... 75 Event... 78 Incident... 80 Request Fulfillment... 82 Problem... 84 Access... 86 Other Practices... 88 Operation Functions... 88 Additional Operation Roles... 90 Continual Improvement... 91 Seven-Step Improvement Process... 94 Additional CSI Roles... 95

1 Introduction Purpose This book is designed as a quick reference for ITIL 2011. It is not intended as an overview of ITIL 2011 but merely as a memory jogger. It is suggested that you first familiarize yourself with the ITIL 2011 documentation before using this book. This book contains references to more detailed material found in ITIL 2011. Audience This book is intended to be used by anyone involved in planning, consulting, implementing, or testing an ITIL 2011 implementation. Organization of the Book This book summarizes each of the ITIL 2011 books. Each book in the ITIL 2011 series represents a single stage in the lifecycle of an IT. The first and last books in the series, Strategy and Continual Improvement, do not contain rigorously-defined processes, but instead describe a set of practices that may be used during those stages of the lifecycle. The second, third, and fourth books in the series, Design, Transition, and Operation, contain rigorously-defined processes. The subsequent chapters in this book each summarize one of the ITIL 2011 books. The Strategy and Continual Improvement chapters contain the following structure: Brief Description of the Stage Overview Diagram of the Stage Key Concepts of the Stage Processes Each process section within a chapter is structured in the following way: Process Purpose The rationale for the process J.O. Long, ITIL 2011 At a Glance, SpringerBriefs in Computer Science, DOI 10.1007/978-1-4614-3977 8 - _ 1, The Author 2012

2 ITIL 2011 At a Glance Overview Diagram Shows all triggers, inputs, outputs, activities, and roles for the process Key Concepts Various diagrams for describing important concepts and a list of key terms BPMN Workflow The high-level workflow for the ITIL activities cast in very basic BPMN (Business Process Modeling Notation) Architecture Considerations Changes that could be made to the process if a rigorously-defined ITSM architecture was needed. This is the view of the author based on inconsistencies and issues found with implementing ITIL 2011. For more information The author may be contacted at johnoflong@gmail.com

3 List of ITIL Processes Process name Acronym ITIL Book What s new in ITIL 2011 Access ACC Operation Availability AVM Design Business Relationship BRM Strategy New process Capacity CAP Design Change Evaluation CHE Transition Previously known as Evaluation Change CHA Transition Build and Test Authorization separate from Deployment authorization Demand DEM Strategy Newly defined activities Design Coordination DES Design New process Event EVE Operation Workflow improved Financial for IT s FIN Strategy Newly defined activities Incident INC Operation IT Continuity SCO Design Knowledge KNO Transition Problem PRB Operation Some activities Release and Deployment RDM Transition consolidated into Deployment Request Fulfillment REQ Operation Workflow improved Asset and Configuration SAC Transition Catalog SCA Design Level SLM Design Workflow improved J.O. Long, ITIL 2011 At a Glance, SpringerBriefs in Computer Science, DOI 10.1007/978-1-4614-3977 8 - _ 2, The Author 2012

4 ITIL 2011 At a Glance Portfolio SPM Strategy Newly defined activities Validation and Testing SVT Transition Seven-Step Improvement SSI CSI Workflow improved Strategy for IT s STM Strategy New process Supplier SUP Design New repository for data Transition Planning and Support TPS Transition

5 Strategy Brief Description Strategy describes an IT organization s high-level approach to providing s. First, the IT organization must identify the market for its s. This, in turn, drives the identification of s offerings as well as the strategic assets that will constitute those s. Envisioned s will be added to the portfolio. These identified s will continue to be pursued until they are finally chartered for design (and development), which moves those s into the Design stage. Supporting this overall activity is the need to determine the IT organization s overall approach to providing s. This may include internal providers, external providers, a shared approach, preferred providers, etc. In addition, several practices play a part in determining the overall strategy, including financial management, demand management, and risk management. J.O. Long, ITIL 2011 At a Glance, SpringerBriefs in Computer Science, DOI 10.1007/978-1-4614-3977 8 - _ 3, The Author 2012

6 ITIL 2011 At a Glance Overview Diagram Strategy for IT s Business Relationship Portfolio IT Customers Supporting Processes and Practices Financial Demand Risk Key Rectangle with gray back ground - Process Rectangle with white back ground Practice strategy defines a number of processes and practices

ITIL 2011 At a Glance 7 Strategy Key Concepts Design Package and Other Artifacts Strategy Design Transition Operation Design Package Statement of Requirements (SOR) Acceptance Criteria (SAC) Level Requirements (SLR) Level Targets Contain severy thing that defines the through each stage of the lifecycle. The design package is used throughout the lifecycle

8 ITIL 2011 At a Glance Types of s Business unit Business process Business process Level Agreements Operational Level Agreements Core Core Underpinning Contracts Business s Supporting Supporting Supporting Supplier Infrastructure IT Organization Infrastructure An IT organization provides core s, supporting s, and infrastructure s

ITIL 2011 At a Glance 9 Providers The Business Business Unit Business Unit Business Unit Business Unit Internal providers Type I provider Type II provider External Business External providers Type III provider There are three types of providers

10 ITIL 2011 At a Glance Packages, Level Packages, and Lines of Customer 1 (pattern of business activity) Customer 2 (pattern of business activity) level package 1 level package 2 package 1 package 2 Core Supporting Supporting Line of (LOS) A line of consists of all packages for a

ITIL 2011 At a Glance 11 Portfolio and Catalog Pipeline Status Requirements Defined Analysed Approved Portfolio Catalog Status Chartered Designed Developed Built Test Released Operational Retired s Status Retired The portfolio includes the pipeline, the catalog, and retired s