ITIL Version 3.0 (V.3) Service Transition Guidelines By Braun Tacon
|
|
- Matilda Tucker
- 4 years ago
- Views:
Transcription
1 ITIL Version 3.0 (V.3) Service Transition Guidelines By Braun Tacon Executive Summary: This document is seven pages. Page one is informational/background only. What follows over the next six pages are the three principles of Service Transition which are fundamental to the delivery of Services that brings Business Value. By using this document as a checklist to ensure the identification of key requirements and to assess if those requirements are being met, we can help our Service Providers transition Services to Nike that delivers Business Value. Additionally by using a common set of criteria and measurement we can baseline where we currently stand and measure progress in a consistent and relevant way from both a tower and program point of view, with a goal of managing to our commitments and deliverables. Finally, since Change is the focus of Service Transition, Change is the focus of this document. Pages four and five are entirely devoted to the topic of Change and Change Management. ITIL V. 3 is a framework for Service Management that is built around five separate lifecycle phases: Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement. In ITIL V. 3 a Service is defined as, a means of delivering value to customers by facilitating the outcomes those customers want to achieve without the ownership of specific costs and risks. Previously, we have been engaged in the Service Strategy phase. Service Strategy activities are: Define the market Develop the offerings Develop Strategic Assets Prepare for execution Next came the Service Design phase. Please review this document for a fuller understanding of Service Design. Once Service Design is complete, the next phase is Service Transition. The core activities of Service Transition are: Plan and manage the capacity and resources required to package, build, test, and deploy a release (service) into production Provide a consistent and rigorous framework for evaluating the Service capability and risk profile Establish and maintain the integrity of all identified Service Assets and configurations Provide good-quality knowledge and information Provide efficient and repeatable build and installation mechanisms Core focus: Ensure that the Service can be managed, operated, and supported according to the requirements and constraints specified within Service Design
2 The three major aspects of Service Transition are: Change Management (CM), Service Asset and Configuration Management (SACM), and Release and Deployment Management (RDM). Each of these principles is essential to effective Service Transition and each has a specific set of requirements and measures. Since CM is the most complex of these three topics, we will spend a bit more time discussing those concepts. This is not to say the other aspects are less important but since good CM will be a key dependency to our success during transition, it is also good practice to focus there. Before discussing the three aspects of Service Transition here are some general concepts and definitions that you should be familiar with: Change A Change to an existing Service or the introduction of a new Service including: addition, modification, removal, documentation, etc. From a CM perspective, all Service Change should be authorized and planned Change Advisory Board (CAB) A body that exists to support the authorization of Changes and to assist CM in the assessment and prioritization of the Changes Change History Information about all changes made to a Configuration Item during its life. Change History consists of all those Change Records that apply to the CI. Change Management The Process responsible for controlling the Lifecycle of all Changes. The primary objective of Change Management is to enable beneficial Changes to be made, with minimum disruption to IT Services. Change Model A repeatable way of dealing with a particular Category of Change. A Change Model defines specific pre-defined steps that will be followed for a Change of this Category. Change Models may be very simple, with no requirement for approval (e.g. Password Reset) or may be very complex with many steps that require approval (e.g. major software Release). See Standard Change, Change Advisory Board. Change Record A Record containing the details of a Change. Each Change Record documents the Lifecycle of a single Change. A Change Record is created for every Request for Change that is received, even those that are subsequently rejected. Change Records should reference the Configuration Items that are affected by the Change. Change Records are stored in the Configuration Management System. Change Request Synonym for Request for Change. Change Schedule A Document that lists all approved Changes and their planned implementation dates. A Change Schedule is sometimes called a Forward Schedule of Change, even though it also contains information about Changes that have already been implemented. Change Types Changes are categorized into: o Standard Change A pre-approved Change that is low Risk, relatively common and follows a Procedure or Work Instruction. For example password reset or provision of standard equipment to a new employee. RFCs are not required to implement a Standard Change, and they are logged and tracked using a different mechanism, such as a Service Request. See Change Model. o Normal Change One raised by a request from the initiator (the individual or organizational group that requires the Change) o Emergency Change A Change that must be introduced as soon as possible. For example to resolve a Major Incident or implement a Security patch. The Change Management Process will normally have a specific Procedure for handling Emergency Changes. See Emergency Change Advisory Board (ECAB). Change Window A regular, agreed time when Changes or Releases may be implemented with minimal impact on Services. Change Windows are usually documented in SLAs. Configuration Item (CI) Any Component that needs to be managed in order to deliver an IT Service. Information about each CI is recorded in a Configuration Record within the Configuration Management System and is maintained throughout its Lifecycle by Configuration Management. CIs are under the control of Change Management. CIs typically include IT Services, hardware, software, buildings, people, and formal documentation such as Process documentation and SLAs.
3 Configuration Management The Process responsible for maintaining information about Configuration Items required to deliver an IT Service, including their Relationships. This information is managed throughout the Lifecycle of the CI. Configuration Management is part of an overall Service Asset and Configuration Management Process. Configuration Management Database (CMDB) The CMDB is a database used to store Configuration Records throughout their Lifecycle. The CMS maintains one or more CMDB (Federated CMS), but it is the CMDB that is used to store the specific attributes of the CIs and their relationships with other CIs. Whenever possible, automation should be used to update and manage the CMDB in order to reduce both cost and errors Configuration Management System (CMS) The goal of a CMS is to provide reliable, quick, and easy access to accurate configuration information. Think of CMS as a process, tool, or a combination of both that will allow stakeholders to assess the impact of proposed Changes, to track Changes, and to ensure Changes are delivered to the appropriate party or into the correct environment. CI Type A Category that is used to Classify CIs. The CI Type identifies the required Attributes and Relationships for a Configuration Record. Common CI Types include: hardware, Document, User etc. Deployment The Activity responsible for movement of new or changed hardware, software, documentation, Process, etc to the Live Environment. Deployment is part of the Release and Deployment Management Process. Emergency Change Advisory Board (ECAB) A sub-set of the Change Advisory Board who make decisions about high impact Emergency Changes. Membership of the ECAB may be decided at the time a meeting is called, and depends on the nature of the Emergency Change. Release A collection of hardware, software, documentation, Processes or other Components required to implement one or more approved Changes to IT Services. The contents of each Release are managed, Tested, and Deployed as a single entity. Release and Deployment Management The Process responsible for both Release Management and Deployment. Release Management The Process responsible for Planning, scheduling and controlling the movement of Releases to Test and Live Environments. The primary Objective of Release Management is to ensure that the integrity of the Live Environment is protected and that the correct Components are released. Release Management is part of the Release and Deployment Management Process. Release Unit Components of an IT Service that are normally Released together. A Release Unit typically includes sufficient Components to perform a useful Function. For example one Release Unit could be a Desktop PC, including Hardware, Software, Licenses, Documentation etc. A different Release Unit may be the complete Payroll Application, including IT Operations Procedures and User training. Release Window Synonym for Change Window. Request for Change (RFC) A formal proposal for a Change to be made. An RFC includes details of the proposed Change, and may be recorded on paper or electronically. The term RFC is often misused to mean a Change Record, or the Change itself. Seven Rs of Change Management Answer the seven questions to understand the impact of Changes o Who Raised the Change? o What is the Reason for the Change? o What is the Return required from the Change? o What are the Risks involved the Change o What Resources are required to deliver the Change? o Who is Responsible for the build, test, and implementation of the Change? o What is the Relationship between this Change and other Changes? Utility Fit for Purpose, meets requirements and expectations Warranty Will perform as agreed to, and mitigating and compensating controls exist (SLA)
4 Change Management Objectives: The goal of the Change Management process is to ensure that Changes are recorded and then: Evaluated, Authorized, Prioritized, Planned, Tested, Implemented, and finally Documented. Change Management Concepts: CM processes should be designed and planned in conjunction with, not separate from, the Release and Deployment and Service Asset Configuration Management processes. Using this approach helps to evaluate the impact of the Change on the current and planned services and releases. Different types of Changes may require different types of Change requests (RFC). Some examples of various types of Changes are: RFC to Service Portfolios could include a new portfolio line item or an alteration to the portfolio s scope, business case or baseline RFC to Service or Service Definition could be a Change in existing or planned Service attributes, a Project Change that impacts Service Design, or something as simple as a Service improvement Some Changes do not require an RFC; these are known as Standard Changes. Two examples would be a request for User Access, or typical operational activities such as rebooting hardware on failure (as long as there is no impact on other Services) and planned maintenance Change Management Roles: There are two basic roles which support the CM process. Change Manager Receives, logs, and allocates priorities. Tables all RFCs for the CAB meeting. Decides which people will come to which meetings. Convenes the CAB or Emergency CAB (ECAB) meetings for RFC assessment. Chairs all CAB and ECAB meetings. Authorizes acceptable Changes. Change Advisory Board (CAB) Is an advisory body, requiring appropriate terms of reference such as meeting regulations and scope of influence. The CAB also ensures that formal authorization is obtained for each Change from the appropriate Change authority such as, but not limited to a Change Manager, a CAB or ECAB, an IT Management Board or a Business Executive Board Change Management Scope: The scope of the CM process covers Changes to Service Assets and CIs across the entire Service Management Lifecycle from Service Strategy to Continuous Service Improvement. Change Management Process Activities: Any CM process should include the following activities at a minimum. Planning and controlling Changes Change and Release scheduling Communications Change decision making and Change authorization Ensuring there are remediation or back out plans Measurement and control Management reporting Understanding the impact of Change Continual improvement Additionally, your processes should ensure that you have a mechanism to filter out Changes that are totally impractical, are repeats of earlier RFCs that have been previously accepted or rejected, and incomplete submissions. All Changes should be assigned a Category and Priority, and finally Changes should be
5 authorized by the appropriate authority. While a Standard Change can be done with local authorization, a high cost/risk Change probably requires decisions from executives such as the Board of Directors. Authorized Changes: All authorized Changes (and all Changes SHOULD be authorized) should be passed to the appropriate technical groups. CM is responsible for ensuring that Changes are implemented as scheduled. This Role should be viewed as a coordination function, because the implementation will be the responsibility of the Release and Deployment Management Role. Change Review: Is done on the completion of the Change. For major Changes there will be a larger customer and stakeholder input and audience, and should include any Incidents or missed SLA or Regulatory requirements. A Post-Implementation Review (PIR) is done to ensure that the Change met objectives, initiator and customer requirements are met to at least the meets expectations level, and to confirm that there has been no unexpected consequences. All lessons learned are fed back into future Change Processes. Change Management Key Metrics: The following are some useful metrics (KPIs). This is not an allencompassing list. Use whatever metrics meet your design and requirement needs, but these metrics will be useful as a guide in developing other metrics. The number of Changes implemented to services that met the customer s agreed requirements. This can be a relationship between quality/cost/time against percentage of Changes requested. Reduction in the number of disruptions, defects, or rework required caused by poor CM practices or incomplete or inaccurate specifications Percentage and reduction of unauthorized Changes Percentage and reduction of backlog RFCs Percentage and reduction of emergency or otherwise unplanned Changes Percentage and reduction of Changes where the back out plan was used Percentage and reduction of failed Changes Average time to implement based upon Urgency/Priority/Change type. Percentage and reduction of Changes which caused incidents Percentage of Changes which are fit for purpose the first time. This is a measurement of accuracy Change Management Considerations: Some topics to consider ensuring that our Change Management processes deliver the expected Business Value Are we creating a culture of CM across the org, including zero tolerance for unauthorized Changes? Do we align Service CM processes with business, project, and stakeholder CM processes? Are we prioritizing Change, and establishing accountability throughout the CM Lifecycle? Do we have a Single Point of Contact (SPOC); this could be an individual, role, function or group whose Role is to prevent uncoordinated Change from occurring across multiple functions? Do we prevent people who should not be making Changes from accessing the production environment in such a way that they could make Change? Are our CM processes integrated with other Service Management processes in a way that establishes traceability of Change? Also, do we detect unauthorized Change, and identify Change-related incidents? Do we have established Change windows, and are those windows enforced so that Change that occurs outside of those windows is being considered as Emergency Change with a higher level of justification and review? Do we conduct performance and risk evaluations on any Change that have the potential to disrupt a Service?
6 Do we have a feedback loop for Continuous Service Improvement and are we measuring our performance? Service Asset and Configuration Management Objectives: To define and control the components of Services and Infrastructure and to maintain accurate configuration information on the historical, planned and current state. Service Asset and Configuration Management Concepts: To deliver a model of the Services, Assets, and Infrastructure by recording the relationships between CIs. In an Enterprise the size of Nike, this is best accomplished with a meta-system commonly known as the CMS. While the concept could be discussed more from a very deep and technical perspective, it will suffice for the purpose of this document that you are familiar with the following two concepts and definitions: Configuration Baseline: A configuration of a Service, Product or Infrastructure that has been reviewed and agreed upon Snapshot: A snapshot of the current state of a CI, Environment, or Baseline to demonstrate Stability or Change Service Asset and Configuration Management Roles: Service Asset Manager Delivers to the overall objectives agreed upon with the IT Service Manager, evaluates existing Asset Management, and manages the scope of the Asset Management process Configuration Manager Delivers to the overall objectives agree upon with the IT Service Manager, oversees existing CMS, and manages the scope of the Configuration Management process Configuration Analyst Proposes scope, trains Asset and Configuration Management specialists, and supports the creation of Asset and Configuration Management plans CMS/Tools Administrator Evaluates tools, monitors performance and capacity, and additional duties as required Release and Deployment Management Objectives: To ensure that there are clear and comprehensive release and deployment plans that bring alignment with customer and business Change plans. To build a release package that can be built, installed, tested, and deployed efficiently and on schedule. That all new or changed Services and Systems deliver to agreed upon SLA, Utility, and Warranty. Releases will bring minimal unpredicted impact on Production, Operations, and Support Services, and that all customers are satisfied with all aspects of the Service Transition phase, including for example User Documentation and Training. Release and Deployment Management Concepts: A Release Unit is the portion of a Service or an IT Infrastructure released together. This unit may vary; one size does not fit all. When considering a Release, some options are Big bang vs. phased Push vs. pull Automation vs. manual Additionally, Release and Deployment manages the Release structure Release exit and entry criteria Control
7 Roles and Responsibilities Release and Deployment Roles: The following defines the Roles in Release and Deployment Release and Deployment Manager Is responsible for the planning, design, build, configuration, and testing of all Service, Software, and Hardware used to create the Release Package (Release Unit) Release packaging and Build Manager Is responsible for defining the final release configuration including, knowledge, information, hardware, software, infrastructure, etc Deployment Staff Deliver the final physical implementation, coordinate Release documentation and communications including training, and plan the deployment in agreement with Change and Knowledge Management
Service Transition. ITIL is a registered trade mark of AXELOS Limited.. The Swirl logo is a trade mark of AXELOS Limited.. 1
Service Transition ITIL is a registered trade mark of AXELOS Limited.. The Swirl logo is a trade mark of AXELOS Limited.. 1 Lesson Objectives Service Transition - Introduction - Purpose and Objectives
HP Service Manager. Process Designer Content Pack 9.30.1. Processes and Best Practices Guide
HP Service Manager Process Designer Content Pack 9.30.1 Processes and Best Practices Guide Document Release Date: June, 2012 Software Release Date: June, 2012 1 Legal Notices Warranty The only warranties
HP Change Configuration and Release Management (CCRM) Solution
HP Change Configuration and Release Management (CCRM) Solution HP Service Manager, HP Release Control, and HP Universal CMDB For the Windows Operating System Software Version: 9.30 Concept Guide Document
ITIL Introducing service transition
ITIL Introducing service transition The goals of service transition Aligning the new or changed service with the organisational requirements and organisational operations Plan and manage the capacity and
Free ITIL v.3. Foundation. Exam Sample Paper 1. You have 1 hour to complete all 40 Questions. You must get 26 or more correct to pass
Free ITIL v.3. Foundation Exam Sample Paper 1 You have 1 hour to complete all 40 Questions You must get 26 or more correct to pass Compliments of Advance ITSM www.advanceitsm.com 1. What is the main reason
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper A, version 5.1 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper A, version 4.1 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper A, version 5.1 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
Page 1 of 8. Any change, which meets the following criteria, will be managed using IM/IT Change Management Process.
Page 1 of 8 1. Introduction This policy describes the Authority s Information Management/Information Technology (IM/IT) change management procedures. IM/IT manages changes to applications, infrastructure
The ITIL Foundation Examination Sample Paper A, version 5.1
The ITIL Foundation Examination Sample Paper A, version 51 Multiple Choice Instructions 1 All 40 questions should be attempted 2 All answers are to be marked on the answer grid provided 3 You have 60 minutes
ITIL V3 Foundation Certification - Sample Exam 1
ITIL V3 Foundation Certification - Sample Exam 1 The new version of ITIL (Information Technology Infrastructure Library) was launched in June 2007. ITIL V3 primarily describes the Service Lifecycle of
Which statement about Emergency Change Advisory Board (ECAB) is CORRECT?
ITIL Foundation mock exam 4 1. Which of the following is NOT a purpose of Service Transition? A) To ensure that a service can be managed, operated and supported B) To provide training and certification
Process Description Change Management
Process Description Change Management Version 4.1 April, 2013 Document Change Control Version # Date of Issue Author(s) Brief Description 1.0 3/8/13 J.Worthington Initial Draft 2.0 3/25/13 J.Worthington
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper A, version 4.2 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
EXIN.Passguide.EX0-001.v2014-10-25.by.SAM.424q. Exam Code: EX0-001. Exam Name: ITIL Foundation (syllabus 2011) Exam
EXIN.Passguide.EX0-001.v2014-10-25.by.SAM.424q Number: EX0-001 Passing Score: 800 Time Limit: 120 min File Version: 24.5 http://www.gratisexam.com/ Exam Code: EX0-001 Exam Name: ITIL Foundation (syllabus
General Platform Criterion Assessment Question
Purpose: [E]nsure that the assets required to deliver services are properly controlled, and that accurate and reliable information about those assets is available when and where it is needed. (ST 4.3.1)
CHG-11-G-001 Does the tool use ITIL 2011 Edition process terms and align to ITIL 2011 N/A. Edition workflows and process integrations?
Purpose: [C]ontrol the lifecycle of all changes, enabling beneficial changes to be made with minimum disruption to IT services. (ST 4.2.1) Activities include: Assessing the impact of business change on
Integrating Project Management and Service Management
Integrating Project and Integrating Project and By Reg Lo with contributions from Michael Robinson. 1 Introduction Project has become a well recognized management discipline within IT. is also becoming
Configuration control ensures that any changes to CIs are authorized and implemented in a controlled manner.
ITIL Intermediate Capability Stream: RELEASE CONTROL AND VALIDATION (RCV) CERTIFICATE SCENARIO BOOKLET Scenario One A global company develops its own applications to support the business. The service transition
Implementing Change Management in a Regulated Environment
Implementing Change Management in a Regulated Environment Valerie Arraj Managing Director Session 227 Compliance Process Partners Service Management-focused consulting, automation and training organization
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper A, version 5.1 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
1 Why should monitoring and measuring be used when trying to improve services?
1 Why should monitoring and measuring be used when trying to improve services? a) To validate, direct, justify and intervene b) To validate, measure, monitor and change c) To validate, plan, act and improve
Which ITIL process or function deals with issues and questions about the use of services, raised by end users?
1 of 40 Which ITIL process or function deals with issues and questions about the use of services, raised by end users? A. Availability Management B. Service Level Management C. Problem Management D. Service
ITIL by Test-king. Exam code: ITIL-F. Exam name: ITIL Foundation. Version 15.0
ITIL by Test-king Number: ITIL-F Passing Score: 800 Time Limit: 120 min File Version: 15.0 Sections 1. Service Management as a practice 2. The Service Lifecycle 3. Generic concepts and definitions 4. Key
SOLUTION WHITE PAPER. Align Change and Incident Management with Business Priorities
SOLUTION WHITE PAPER Align Change and Incident Management with Business Priorities Table of Contents Executive summary 1 the Need for Business aware Service support processes 2 The Challenge of Traditional
Change Submitter: The person or business requesting or filing the Request For Change (RFC) notice.
ROLES, RESPONSIBILITIES, PROCEDUREs Change Submitter: The person or business requesting or filing the Request For Change (RFC) notice. IT Operations Change Manager: The steward of the Change Management
Subject: 1268-1 Information Technology Configuration Management Manual
Form 1221-2 (June 1969) UNITED STATES DEPARTMENT OF THE INTERIOR BUREAU OF LAND MANAGEMENT Release 1-1741 Date MANUAL TRANSMITTAL SHEET 06/19/2012 Subject: 1268-1 Information Technology Configuration Management
Yale University Change Management Process Guide
Yale University Management Process Guide Yale University Management Process 1 of 29 Table of Contents Introduction... 3 Purpose... 3 Scope... 3 Management Overview... 3 Management Key Concepts... 4 Management
ITIL v3. Service Management
ITIL v3 1 as a Practice ITIL = IT Infrastructure Library Set of books giving guidance on the provision of quality IT services Common language Best practices in delivery of IT services Not standards! Platform
The Newcastle upon Tyne Hospitals NHS Foundation Trust. IT Change Management Policy and Process
The Newcastle upon Tyne Hospitals NHS Foundation Trust Version No.: 2.0 Effective From: 16 July 2015 Expiry Date: 16 July 2018 Date Ratified: 5 June 2015 Ratified By: Director of IT 1 Introduction IT Change
GENERAL PLATFORM CRITERIA. General Platform Criterion Assessment Question
GENERAL PLATFORM CRITERIA SACM-V3-G-001 Comment: Does the tool use ITIL V3 process terms and align to ITIL V3 workflows and process integrations? SACM-V3-G-002 (OGC ISS 5.1.10) Access Controls Does the
ITSM Maturity Model. 1- Ad Hoc 2 - Repeatable 3 - Defined 4 - Managed 5 - Optimizing No standardized incident management process exists
Incident ITSM Maturity Model 1- Ad Hoc 2 - Repeatable 3 - Defined 4 - Managed 5 - Optimizing No standardized incident process exists Incident policies governing incident Incident urgency, impact and priority
1 What does the 'Service V model' represent? a) A strategy for the successful completion of all service management projects
1 What does the 'Service V model' represent? a) A strategy for the successful completion of all service management projects b) The path to Service Delivery and Service Support for efficient and effective
Problem Management: A CA Service Management Process Map
TECHNOLOGY BRIEF: PROBLEM MANAGEMENT Problem : A CA Service Process Map MARCH 2009 Randal Locke DIRECTOR, TECHNICAL SALES ITIL SERVICE MANAGER Table of Contents Executive Summary 1 SECTION 1: CHALLENGE
ITIL Foundation for IT Service Management 2011 Edition
ITIL Foundation for IT Service Management 2011 Edition ITIL Rev 03.12 3 days Description ITIL (IT Infrastructure Library) provides a practical, no-nonsense framework for identifying, planning, delivering
ITIL & The Service Oriented Approach. Vivek Shrivastava
Vivek Shrivastava Speaker Introduction Vivek Shrivastava Experienced in numerous aspects of IT during a 15 year career (Dev, QA, Bus Analysis, Project Management, Process Improvement, Service Management,
Florida Courts efiling Authority. User Forum Policy. Page 1 of 11 DRAFT
Florida Courts efiling Authority User Forum Policy Page 1 of 11 DRAFT Introduction In conjunction with the Chief Justice and the Supreme Court, the Florida Courts E-Filing Authority was established in
Change Management. Service Excellence Suite. Users Guide. Service Management and Service-now
Change Management Users Guide Service Management and Service-now Service Excellence Suite Table of Contents Introduction... 3 Overview and Objectives... 4 Overview... 4 Objectives... 4 Primary Benefits
Change Management Living with Change
Change Management Living with Change Introduction Neil Thomas Industry experience in IT & IT support ITIL Vendor Product Management ITIL Consulting Specialised in Service Catalog & CMDB Introduction Fully
Commonwealth of Massachusetts IT Consolidation Phase 2. ITIL Process Flows
Commonwealth of Massachusetts IT Consolidation Phase 2 ITIL Process Flows August 25, 2009 SERVICE DESK STRUCTURE Service Desk: A Service Desk is a functional unit made up of a dedicated number of staff
ITIL: Foundation (Revision 1.6) Course Overview. Course Outline
ITIL: Foundation (Revision 1.6) Course Overview The ITIL Foundation Certification Course introduces the new student to the fundamentals of IT Service Management as described in the IT Infrastructure Library
Internal Audit Report ITS CHANGE MANAGEMENT PROCESS. Report No. SC-11-11
Internal Audit Report ITS CHANGE MANAGEMENT PROCESS Report No. SC-11-11 March 2011 SANTA CRUZ: INTERNAL AUDIT March 31, 2011 MARY DOYLE Vice Chancellor Information Technology Re: Internal Audit Report
ITIL Example change management procedure
ITIL Example change management procedure An example change process diagram Change Intiators outside IT (users/customers/supplier/etc.) Change Initiators IT SERVICE DESK Filters change requests RFC REJECT
ITIL Roles Descriptions
ITIL Roles s Role Process Liaison Incident Analyst Operations Assurance Analyst Infrastructure Solution Architect Problem Manager Problem Owner Change Manager Change Owner CAB Member Release Analyst Test
Roles within ITIL V3. Contents
Roles within ITIL V3 Roles are employed in order to define responsibilities. In particular, they are used to assign Process Owners to the various ITIL V3 processes, and to illustrate responsibilities for
The purpose of this document is to define the Change Management policies for use across UIT.
UNIVERSITY OF UTAH - IT OPERATIONS POLICY UIT CHANGE MANAGEMENT POLICY Chapter or Section: Information Technology ID SOP-CNFM.001 UIT Configuration Management Policy Rev Date Author Change 4.4 9/29/11
Release Management Policy Aspen Marketing Services Version 1.1
Release Management Policy Version 1.1 John Toso 5/10/2010 2 Contents Release Management Policy Overview:... 3 Critical Success Factors... 3 Service Level Management (SLM)... 4 Key Performance Indicators:...
ICS Operations & Policies Manual. For State Agencies Providing and Using Consolidated Services
2010 ICS Operations & Policies Manual For State Agencies Providing and Using Consolidated Services This manual is intended to be an Idaho state operations process framework based on the Information Technology
Service Management. A framework for providing worlds class IT services
Service Management A framework for providing worlds class IT services Barry Corless MISM Slide - 1 Copyright Remarc Technologies Ltd, 2007 These course notes were produced by Remarc Service Management,
HP Service Manager software
HP Service Manager software The HP next generation IT Service Management solution is the industry leading consolidated IT service desk. Brochure HP Service Manager: Setting the standard for IT Service
ITIL - QUICK REFERENCE GUIDE
http://www.tutorialspoint.com/itil/itil_quick_guide.htm ITIL - QUICK REFERENCE GUIDE Copyright tutorialspoint.com ITIL Overview ITIL is a framework providing best practice guidelines on all aspects of
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper B, version 5.0 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
The ITIL v.3 Foundation Examination
The ITIL v.3 Foundation Examination Sample Paper A, version 3.1 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. There are no trick questions. 3. All answers are to be marked on
Service Support. 2005 Kasse Initiatives, LLC. ITIL Configuration Management - 1. version 2.0
Service Support Configuration Management ITIL Configuration Management - 1 Goals of Configuration Management The goals of Configuration Management are to: Account for all the IT assets and configurations
Deploying the CMDB for Change & Configuration Management
WHITE PAPER: CMDB, CHANGE & CONFIGURATION MANAGEMENT Deploying the CMDB for Change & Configuration Management MAY 2007 CA and BearingPoint Table of Contents Executive Summary SECTION 1 2 Pressures on IT
Foundation. Summary. ITIL and Services. Services - Delivering value to customers in the form of goods and services - End-to-end Service
ITIL ITIL Foundation Summary ITIL and s Design s - Delivering value to customers in the form of goods and services - End-to-end ITIL Best Practice - Scalable and not prescriptive - Gathered from Users,
Risk profile table for deployment of releases to the main web site. High Acceptable Unacceptable Unacceptable
ITIL V3 Intermediate Capability Stream: RELEASE, CONTROL AND VALIDATION (RC&V) CERTIFICATE SCENARIO BOOKLET Scenario One A global company develops their own applications to support the business. The Service
Determining Best Fit. for ITIL Implementations
Determining Best Fit for ITIL Implementations Michael Harris President David Consulting Group Agenda Why ITIL? The Evolution of IT Metrics Towards the Business What do businesses need from IT Introduction
FLORIDA COURTS E-FILING AUTHORITY HELP DESK POLICIES & PROCEDURES
FLORIDA COURTS E-FILING AUTHORITY HELP DESK POLICIES & PROCEDURES Introduction The Florida Courts E-Filing Authority ( Authority ) was created and established in order to: (1) design, develop, implement,
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper B, version 4.0 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
Service Integration &
This is a DRAFT document, being published for review & comment The content is therefore subject to change & revision This document is part of the XGOV Strategic SIAM reference set Service Integration &
TechExcel. ITIL Process Guide. Sample Project for Incident Management, Change Management, and Problem Management. Certified
TechExcel ITIL Process Guide Sample Project for Incident Management, Management, and Problem Management. Certified Incident Management Red Arrows indicate that the transition is done automatically using
CCIT Change Management Procedures & Documentation
CCIT Change Management Procedures & Documentation 1.0 Introduction A major challenge within any organization is the ability to manage change. This process is even more difficult within an IT organization.
The Official ITIL v3 Foundation Study Aid Glossary of Terms and Definitions
The Official ITIL v3 Foundation Study Aid Glossary of Terms and s V1.0, November 2007 Acknowledgements We would like to express our gratitude and acknowledge the contribution of Stuart Rance and Ashley
hi Information Technologies Change Management Standard
hi Information Technologies Change Management Standard Classification Service Delivery Standard # SVD-002 Approval Authority Chief Information Officer Implementation Authority Director, Service Delivery
Change Management. Bizagi Suite
Change Management Bizagi Suite Change Management 2 Table of Contents Change Management... 5 Process Elements... 6 RFC Entering... 6 Enter RFC... 6 Technical Review Required?... 9 Technical Review and Sign
Change Management: A CA Service Management Process Map. Peter Doherty
TECHNOLOGY brief: CHANGE Change : A CA Process Map Peter Doherty SENIOR PRINCIPAL CONSULTANT Table of Contents Executive Summary 1 section 1: Challenge 2 Simplifying ITIL How to Use the CA Process Maps
Achieving Control: The Four Critical Success Factors of Change Management. Technology Concepts & Business Considerations
Achieving Control: The Four Critical Success Factors of Change Management Technology Concepts & Business Considerations T e c h n i c a l W H I T E P A P E R Table of Contents Executive Summary...........................................................
The ITIL v.3 Foundation Examination
The ITIL v.3 Foundation Examination ITIL v. 3 Foundation Examination: Sample Paper B, version 3.1 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. There are no trick questions.
ITIL Intermediate Lifecycle Stream:
ITIL Intermediate Lifecycle Stream: SERVICE TRANSITION CERTIFICATE Sample Paper 1, version 6.1 Gradient Style, Complex Multiple Choice SCENARIO BOOKLET This booklet contains the scenarios upon which the
An ITIL Perspective for Storage Resource Management
An ITIL Perspective for Storage Resource Management BJ Klingenberg, IBM Greg Van Hise, IBM Abstract Providing an ITIL perspective to storage resource management supports the consistent integration of storage
NSSC Enterprise Service Desk Configuration Management Database (CMDB) Configuration Management Service Delivery Guide
National Aeronautics and Space Administration NASA Shared Services Center Stennis Space Center, MS 39529-6000 www.nssc.nasa.gov NASA Shared Services Center Version 1.0 NSSC Enterprise Service Desk Configuration
How To Create A Help Desk For A System Center System Manager
System Center Service Manager Vision and Planned Capabilities Microsoft Corporation Published: April 2008 Executive Summary The Service Desk function is the primary point of contact between end users and
ITIL V3 Service Lifecycle Key Inputs and Outputs
ITIL V3 Lifecycle & ITIL V3 Lifecycle Key 1 ITIL V3 Lifecycle & Use Material Complying with all applicable copyright laws is responsibility user No part this document may be reproduced, stored in or introduced
White Paper Case Study: How Collaboration Platforms Support the ITIL Best Practices Standard
White Paper Case Study: How Collaboration Platforms Support the ITIL Best Practices Standard Abstract: This white paper outlines the ITIL industry best practices methodology and discusses the methods in
An Implementation Roadmap
An Implementation Roadmap The 2nd Abu Dhabi IT s Forum P J Corum, CSQA, CSTE, ITSM Managing Director Quality Assurance Institute Middle East and Africa Dubai, UAE Quality Assurance Institute Middle East
Integration Technologies Group (ITG) ITIL V3 Service Asset and Configuration Management Assessment Robert R. Vespe Page 1 of 19
Service Asset and Configuration 1. Does the tool facilitate the registration and management of an organization s logical, physical and virtual Configuration Items (CIs)? For example, services, systems,
University of Waikato Change Management Process
1. Overview Information Technology Services and the Faculty and Division ICT staff have adopted the Information Technology Infrastructure Library (ITIL) systems management framework as its model for best
ITIL Essentials Study Guide
ITIL Essentials Study Guide Introduction Service Support Functions: Service Desk Incident Management Problem Management Change Management Configuration Management Release Management Service Delivery Functions:
The ITIL v.3. Foundation Examination
The ITIL v.3. Foundation Examination ITIL v. 3 Foundation Examination: Sample Paper 3, version 3.0 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. There are no trick questions.
HUIT Change Management with ServiceNow. itsm@harvard.edu September 2013
HUIT Change Management with ServiceNow itsm@harvard.edu September 2013 Module 1: Basic Training - Change Requester/Implementer Change Management with ServiceNow Agenda Session Overview HUIT Change Management
Overview of Service Support & Service
Overview of Service Support & Service Delivery Functions ITIL Service Support / Delivery- 1 Service Delivery Functions Availability Management IT Services Continuity Management Capacity Management Financial
Release and Deployment Management: A CA Service Management Process Map
TECHNOLOGY BRIEF: RELEASE AND DEPLOYMENT MANAGEMENT Release and Deployment : A CA Service Process Map JULY 2009 Malcolm Ryder ARCHITECT CA SERVICES Table of Contents Executive Summary 1 SECTION 1: CHALLENGE
ITIL V3 Application Support Volume 1
ITIL V3 Application Support Volume 1 Service Management For Application Support ITIL is a Registered Trade Mark and Community Trademark of the Office of Government and Commerce. This document may contain
Problem Management Overview HDI Capital Area Chapter September 16, 2009 Hugo Mendoza, Column Technologies
Problem Management Overview HDI Capital Area Chapter September 16, 2009 Hugo Mendoza, Column Technologies Problem Management Overview Agenda Overview of the ITIL framework Overview of Problem Management
Achieving ITSM Excellence Through Availability Management
Achieving ITSM Excellence Through Availability Management Technology Concepts and Business Considerations Abstract This white paper outlines the motivation behind Availability Management, and describes
White Paper August 2006. BMC Best Practice Process Flows for ITIL Change Management
White Paper August 2006 BMC Best Practice Process Flows for ITIL Change Management Copyright 1991 2006 BMC Software, Inc. All rights reserved. BMC, the BMC logo, all other BMC product or service names,
Service Asset & Configuration Management PinkVERIFY
-11-G-001 General Criteria Does the tool use ITIL 2011 Edition process terms and align to ITIL 2011 Edition workflows and process integrations? -11-G-002 Does the tool have security controls in place to
CHANGE MANAGEMENT PROCESS
CHANGE MANAGEMENT PROCESS PROCESS ADOPTED BY COUNCIL ON 24 APRIL 2014 AT ITEM C.14.1 Cape Winelands District Municipality Change Management Process 1. 1. OBJECTIVE The objective of this process is to manage
ITIL v3 (Lecture II) Service Management as a Practice
ITIL v3 (Lecture II) as a Practice 1 Processes Availability mgmt Knowledge mgmt Service cont mgmt Evaluation Supplier mgmt Validation & Testing Access mgmt Financial mgmt Info security mgmt Release & Deploy
Requirements Analysis/Gathering. System Requirements Specification. Software/System Design. Design Specification. Coding. Source Code.
Change Control and Configuration Management IVT 11 th Annual conference April 2010 DISCLAIMER Amgen is not responsible for the written or verbal bl content t of fthi this presentation tti Gisele Fahmi,
IT Service Management Center
IT Service Management Center Overview - 1 - OMNITRACKER ITSM Center v5 Supports your business processes according to the established ITIL processes Additionally provides supporting processes: Master Data
Chris Day, Acting Director of IT Services C Day. Configuration Manager Change Manager Change Assessors Change Implementers
Standard Operating Procedures (SOP) for: Configuration Management and Change Control SOP Number: DG25 Version Number: 1 Effective Date: 14/07/2014 Review Date: 14/07/2015 Author: Reviewer: Authorisation:
Change Management: Best Practices
Change Management: Best Practices Contents 1 Executive Summary 1.1 Introduction 1.2 Business Needs 1.3 Target Market 1.4 Description and Requirements 2 Leading Practice 2.1 Roles and Responsibilities 2.1.1
The ITIL v.3. Foundation Examination
The ITIL v.3. Foundation Examination ITIL v. 3 Foundation Examination: Sample Paper 4, version 3.0 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. There are no trick questions.
ITIL A guide to release and deployment management
ITIL A guide to release and deployment management The goal of release and deployment management Release and deployment management aims to build, test and deliver services to the customers specified by
Service Transition and Support: A CA Service Management Process Map
TECHNOLOGY BRIEF: SERVICE TRANSITION AND SUPPORT Service Transition and Support: A CA Service Process Map JUNE 2009 Malcolm Ryder ARCHITECT CA SERVICES Table of Contents Executive Summary 1 SECTION 1:
Change Management Process. June 1, 2011 Version 2.7
Change Management Process June 1, 2011 Version 2.7 Contents Document Control... 3 Overview... 4 Definition of a Change... 5 Description... 5 Objectives... 5 Key Terms & Definitions... 6 Change Management
4/1/2009. Short-termterm
Hi, my name is Susan ITIL in the Workplace The Practical Application of a Best Practice Framework Susan Ryan April 3, 2009 IT industry worker for over 25 years ITIL v2 Manager Certified itsmf Minnesota
University of Bedfordshire ISD Change Management Policy
1 Introduction 1.1 This paper documents the Change Management Policy that is used within the Information Services Directorate (ISD) in the University of Bedfordshire, as part of the Service Support process