Change Management Process
|
|
- Kristopher Stone
- 8 years ago
- Views:
Transcription
1 Change Management Process Version 1.0 1
2 Table of Contents 1 About This Document Document Objective Process Objectives Change Request Lifecycle Stages Change Request (CR) Requirements Approval Requirements Change Board (CB) Requirements Requirement Definitions Risk Assessment: Service Impact Assessment: Install Plan: Backout Plan: Test Plan: Communication Plan: Approvals: Install Results Details Post Implementation Review (PIR) Inquiries Definitions and Acronyms Reference Revision History Author Version Description Date Ken Merkel 1.0 Document Creation August 13, 2015 Sandy Stout Gemma Tungul Ken Merkel Sandy Stout Gemma Tungul Caroline Schulte 1.0 Document Publication August 31,
3 1 About This Document 1.1 Document Objective The Change Management Process document provides guidelines in order to conduct a change according to the Service Alberta Change Management process. This document applies to the changes that are managed under the Government of Alberta (GoA) Change Management control. 1.2 Process Objectives The primary objective of the Change Management process is to enable beneficial changes to be made, with minimum disruption to IT services. The Change Management process has several other objectives: To standardize Requests for Change (RFC), and formalize their handling. To investigate the impact and risk of the change to the existing infrastructure or processes, and assess the appropriateness of the change. To obtain authorization for the change by the appropriate approver(s). To schedule the implementation of the change into production. To coordinate multiple changes across the GOA service providers and customers 3
4 2 Change Request Lifecycle Stages These are the 5 Change Request Stages/Phases: Initiate A Request for Change (RFC) is initiated and populated by Change Coordinator/Change Implementer. Initial classification and impact/risk assessments are performed and the ticket is populated with the required information. Review & Authorize The Change Manager reviews the change for completeness, confirms the impact of the change and identifies the appropriate approvers for the change. Plan & Schedule The Change Manager approves and submits the change to the appropriate approvers ((optional) Change Board, Service Owner. If communication is required, the Change Manager requests the communication to be distributed. The change is then scheduled for implementation. Implement The Change Implementers perform and record the required tasks and activities to implement the Change. Closed The Change Manager will perform a Post-Implementation Review to determine if the Change met its objectives. The change is then closed. 4
5 3 Change Request (CR) Requirements In order to conduct a change, these change requirements must be entered into a Change Request (CR). These are required prior to CR implementation: 1. Risk Assessment 2. Service Impact Assessment (include ministries affected, if any) 3. Install Plan 4. Backout Plan 5. Test Plan 6. Communication Plan These are required after CR implementation 7. Install Results 8. Post Implementation Review (PIR) The CR Requirements are listed with guide in this site: 4 Approval Requirements Approvals are required within the CR Lifecycle. 5 Change Board (CB) Requirements Change Board Requirements must adhere to the Change Board classification and follow the appropriate lead time. Change Board Review is required on all changes that falls under the following guidelines: All outages longer than 10 minutes. All changes visible to the end users. 5
6 6 Requirement Definitions 6.1 Risk Assessment: Risk Assessment is the risks to the service during the change implementation and the risks to the service should the change not be implemented. The risk assessment may include: 1. What is the risk level assessment (Low, Medium, or High)? 2. Have you done this before successfully? 3. Can you test before and after implementation? 4. Risk of not doing the change (optional). Examples: Risk is assessed as low. This is a repeatable process done many times before and has been tested in UAT. Risk is assessed as low. Switch and router reloads are usually uneventful with the device coming back online within 5 minutes. There is always a chance (though very remote) that a device will fail it s reload and not come back online. In such a case a new switch or router would be provisioned during the block time. The risk of this change is low as the changes of similar type has been completed on other parts of the network and implemented as planned. The risk of not doing the change is that the current infrastructure is aged and does not meet security requirements. This could lead to vulnerabilities that may be exploited to compromise our network. 6
7 6.2 Service Impact Assessment: Service Impact Assessment is the impact of the change to end user during and after the change. The Service Impact Assessment should include: 1. How does this impact users of the service during the change? a. Is there an outage? b. How long is the outage? (Change Board review is required for all outages longer than 10 minutes). c. What time is the outage? 2. Will this impact the users after the change, a. Will there be a visible change to end users? (Change Board review is required for all changes visible to the end users). b. Will they have to do something different? 3. What Ministries are affected by this change (change board requirement only). (Change Board review is required if more than one ministry is affected). Examples: No service impact & no outage are expected during the change window. This change will be implemented seamlessly as there are 2 devices are serving user traffic simultaneously and there is no need for reboot. During this change, and file services will be unavailable. Outage should only be 15 minutes at the start of the change although I have scheduled the entire hour in case more time is required. Ministries affected are: Service Alberta, Energy. The switch will be replaced during the lunch with Ministry approval to be attached to this ticket. While connections are moved from the old to the new switch, workstations and printers will not have network access throughout the entire building. This change will affect the Ministry of Service Alberta. 6.3 Install Plan: Install Plan is the detailed description of the installation. The install plan should be detailed enough so that another team member can complete the change. Examples: 1-Rack new router; 2-power up the router: 3-Move cables from the old to the new router; 4-check network connectivity Alter Channel CLIENT.TO.QNA3 parameter HBINT from 50 to 300 using ISPF interface. Change QNA3.PARMLIB(QNA3SGCO) member HBINT parameter from 50 to 300 for channel CLIENT.TO.QNA3 definition 7
8 6.4 Backout Plan: Backout Plan is the detailed description of the backout. The backout plan should be detailed enough so that another team member can complete the backout. If backout plan is not required, describe the reason why. Example: Old router can be reconnected within 1 hour. 1-Rack old router back; 2-power up the old router: 3-Move cables from the new to the old router; 4-check network connectivity 6.5 Test Plan: Test Plan is the detailed description of the test. The test plan should be detailed enough so that another team member can organize the test. The test plan should include: 1. What is the pre-testing plan? (if no pre-testing can be done explain why) 2. If applicable, detailed information on what pre-testing was done and the outcome 3. What is the post-testing plan? Example: After the migration, logon to the SPIN2 prod database servers and verify they are working fine. 6.6 Communication Plan: Communication Plan should include detailed information on what communication is required and to who it is going to. If no communication is required enter no communication required and explain why. The communication plan should include: 1. Communication 2. Communication Distribution Checklist 3. Communication Approval ( ) Refer to this site: Approvals: The following approvals are required within the lifecycle of a change. 8
9 1. Review CR Requirement Completion Approval Approver: Change Manager 2. Business Implementation Approval Approver: (One or more of the following) Service Owner/Ministry/Change Board a. Service Owner approval is required for all changes prior to implementation b. Ministry approval is required for all changes that impacts one ministry only. c. Change Board approval is required for all changes prior to implementation according to predefined Change Board Classification 3. Close Down PIR Completion Approver: Change Manager 6.8 Install Results Details Install Results is the detailed description of the success of the change. The install results should include: 1. Information on whether the change was successful or unsuccessful (e.g. Change was successful and completed in the scheduled time frame). 2. Information on what post testing was done and the outcome. Examples: Change was Successful; Change was implemented with in the allowed time without any incidents. Communication task were successfully completed. Testing Plan was successfully complete. Change had to be backed out by restoring previous settings. This change was not successfully implemented. Will be recreated and scheduled at another time. 6.9 Post Implementation Review (PIR) Post Implementation Review is the final review completed by the Change Manager to ensure change management process compliance prior to closure. Examples: Post-Implementation Review Results - This Change implementation has been deemed successful. 9
10 7 Inquiries Refer your inquiries to 8 Definitions and Acronyms Term Change Change Board Classification Change Management Class Definition A change is the addition, modification, or removal of approved, supported or standard hardware, network, software, environment system, or associated documentation (collectively known as Configuration Items). The need for a Change can arise as a result of an Incident, Problem, Known Error and its resolution, or from proactively seeking business benefits. All Changes are classified into one of the following two classes: Operational changes are those changes which may impact the availability and/or quality of IT services while the changes are being performed, but which will not result in any visible change to customers and/or their end users once the changes are completed. Operational changes include regular maintenance and upgrades, expansion of the IT environment, etc. Business changes are defined as those changes which, once implemented, will result in a visible change in a service and its functionality to its customers and/or end-users. Business changes may include service support process and procedure changes, or upgrades or new releases of services which change the features of the service and/or how it is used by customers and/or end-users. Change Management is the process responsible for controlling the lifecycle of all changes. The primary objective of Change Management is to enable changes to be made, with minimum disruption to IT services. Class specifies the relative urgency of the change, so that the approvers can assess its magnitude. Normal is the default timing for a change. Approval from the Change Manager and the Service Owner is required. Emergency is a change which is required to resolve an incident or problem deemed critical to business continuity, or in some cases, to prevent an incident or problem that is about to occur. Change Management approval and Service Owner or alternate approver are required prior to implementation but Change Board requirements do not apply. Latent is a Change that has already been implemented. This class type should only be used for changes that were implemented without prior Change Management approval due to the urgency of the situation. Approval must be 10
11 Term Definition received by the Service Owner or alternate approver and it must be attached to the ticket. Customer End-user or user Impact The recipient of a service. In this environment, the ministries of the Government of Alberta are the customers. The person who uses the services on a day-to-day basis. In classifying Changes as operational or business changes, service provider users who are involved in the delivery of the service are not considered users of that service, although they are affected by the quality and availability of those services. Means the known or anticipated effect of a Change to service availability, service quality, business continuity, etc. Typically this will relate to the number and type of users affected by the Change being proposed. It is often equal to the extent of a distortion of agreed or expected service levels. Impact can be: Minor/Localized: The Change will have little or no effect to end users during working hours, but may require the service to be unavailable for less than 10 minutes during non-working hours. Moderate/Limited: The Change may affect a moderate number of users, probably limited to a single branch or large user group and may require the service to be unavailable for longer than 10 minutes or have a visible change to end users. Significant/Large: The Change may affect a single Ministry or several branches across multiple Ministries and may require the service to be unavailable for longer than 10 minutes or have a visible change to end users. Lead Time Extensive/Widespread: The Change affects multiple Ministries and may require the service to be unavailable for longer than 10 minutes or have a visible change to end users. Implementation Lead Time is the recommended amount of time the submission of a Change Request and the earliest time that the proposed Change implementation should begin. The following are the implementation Change Board lead times required by Service Alberta Change Management: Minimum Lead Description Time 7 business days - Must be submitted no later than Monday, 4:30pm in order for the change to appear on the Wednesday Change Board Agenda. - In case of holidays (ie. Holiday Monday) preference would be to have the CR ready by Friday, 4:30pm BUT CRs will be accepted until Tuesday at noon. - Additional 5 days for Communication 11
12 Impact Change Management Process Term Priority Definition Distribution Priority is an indicator of the relative importance of a change. It is used to determine the sequence in which a change needs to be resolved, and therefore the speed at which the resolution will be approved and deployed. It is based primarily on the Impact and Urgency, although the business risk of not implementing the change is another important criterion for determining the priority of a change. Priority can be: Low: A Change that impacts few users, and can be implemented in the longterm Medium: A Change that impacts a moderate number of users, and can be implemented in the medium-term High: A Change that impacts a significant number of users, and must be implemented in the short term Critical: A Change that impacts both a large number of users and must be implemented quickly Request for Change (RFC) or Change Request Risk Priority Urgency Critical High Medium Low Extensive Critical Critical High High Significant Critical High High Medium Moderate High High Medium Low Minor High Medium Low Low Form (or screen) used to record the details of a Change Request to any service and/or Configuration Item. This includes a description of the change, the affected components, the business justification, an impact and risk assessment, resource requirements, and approval status of the change. Submission of this form or screen is the required initial step in Change Management process. Risk assessment is concerned with analyzing threats and weaknesses that have been or would be introduced as a result of a service change. A risk occurs when a threat can exploit a weakness. The likelihood of threats exploiting a weakness, and the impact if they do, are the fundamental factors in determining risk. Risk Level 1-2 (Low): (E.g. Routine change with proven success; minimal impact if Change fails; no back out required or back out is simple) Risk Level 3-4 (Medium): (E.g. High probability of success; back out is involved but not difficult; moderate visibility potential to customers) Risk Level 5 (High): (E.g. Change is complex or high risk; implementation is difficult; back out is lengthy and/or difficult; high visibility potential to customers.) 12
13 9 Reference Change Management Documentation is located here. Change Management Sharepoint site is located here. Service Alberta Change Board Sharepoint Site (OCB/BCB) is located here. 13
Problem Management. Process Guide. Document Code: Version 2.6. January 7, 2011. Robert Jackson (updates) Ashish Naphray (updates)
Problem Management Process Guide Document Code: Version 2.6 January 7, 2011 Prepared by: R. Bruce Specht Robert Jackson (updates) Ashish Naphray (updates) Contributors: Dalibor Petrovic Karen Moses ITSM
More informationIT General Controls Domain COBIT Domain Control Objective Control Activity Test Plan Test of Controls Results
Acquire or develop application systems software Controls provide reasonable assurance that application and system software is acquired or developed that effectively supports financial reporting requirements.
More informationChange 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
More informationTechExcel. 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
More informationIntroduction... 4. Purpose... 4 Scope... 4 Manitoba ehealth Change Management... 4 Icons... 4. RFC Procedures... 5
Remedy Change Management Version 3.0 Modified: 10/27/2015 Table of Contents Introduction... 4 Purpose... 4 Scope... 4 Manitoba ehealth Change Management... 4 Icons... 4 RFC Procedures... 5 Process Flow
More informationhi 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
More informationExam : EX0-100. Title : ITIL Foundation Certificate in IT Service Management. Ver : 08.01.06
Exam : EX0-100 Title : ITIL Foundation Certificate in IT Service Management Ver : 08.01.06 QUESTION 1 The successful diagnosis of a problem results in a Known Error. On the basis of this Known Error a
More informationChange Management Service Description
Change Management Service Description Applies to: Office 365 Dedicated Topic Last Modified: 2015-06-29 Change Management Process... 3 Request for Change Process... 3 Change Windows... 3 Change Notifications
More informationContact / Escalation Guide. For OPENHIVE Managed Services provided by Capita. Version 6.0
Contact / Escalation Guide For OPENHIVE Managed Services provided by Capita Version 6.0 Contents Document Control...3 Background and Scope...4 Capita contact information...4 Service Desk Team...4 Direct
More informationContact / Escalation Guide. For OPENHIVE Managed Services provided by Capita. Version 3.0
Contact / Escalation Guide For OPENHIVE Managed Services provided by Capita Version 3.0 Contents Document Control...3 Background and Scope...4 Capita contact information...4 Service Desk Team...4 Direct
More informationFlorida 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
More informationENTERPRISE IT SERVICE MANAGEMENT BUREAU OF ENTERPRISE SYSTEMS AND TECHNOLOGY ENTERPRISE SERVICE DESCRIPTION FOR. Ocotber 2012
S T A T E O F C O N N E C T I C U T BUREAU OF ENTERPRISE SYSTEMS AND TECHNOLOGY ENTERPRISE SERVICE DESCRIPTION FOR ENTERPRISE IT SERVICE MANAGEMENT (Featuring Numara Footprints Service and Asset Management)
More informationCCIT Technical Support Policy
Executive Summary In order to ensure that your experience with CCIT is as effective and efficient as possible, CCIT outlines in this policy its technical support process, request submission mechanisms,
More informationRequest for Proposal Technology Services Maintenance and Support
Request for Proposal Technology Services Maintenance and Support Maintenance and Support July 19, 2014 Celerity Educational Group is seeking an IT consulting firm to manage Maintenance of our Network Systems
More informationColumbia College Process for Change Management Page 1 of 7
Page 1 of 7 Executive Summary Columbia College's Process for Change Management is designed to provide an orderly and documented method in which changes to the College's computing environment are requested
More informationUniversity 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
More informationCisco Change Management: Best Practices White Paper
Table of Contents Change Management: Best Practices White Paper...1 Introduction...1 Critical Steps for Creating a Change Management Process...1 Planning for Change...1 Managing Change...1 High Level Process
More informationPatch Management Procedure. e-governance
for e-governance Draft DEPARTMENT OF ELECTRONICS AND INFORMATION TECHNOLOGY Ministry of Communication and Information Technology, Government of India. Document Control S/L Type of Information Document
More informationCommunicate: Data Service Level Agreement. Author: Service Date: October 13. Communicate: Data Service Level Agreementv1.
Communicate: Data Service Level Agreement Author: Service Date: October 13 Communicate: Data Service Level Agreementv1.1 Page 1 of 12 Contents 1. Scope 3 2. Service Definitions 3 3. Service Provision 3
More informationDynatrace Support Policy
Dynatrace Support Policy Standard Support March 2015 v2 Dynatrace TECHNICAL Support ENGINEERING TEAM The Dynatrace Support team consists of seasoned technical professionals dedicated to helping you optimize
More informationHow To Manage An Ipa Print Service At A College Of Korea
1 General Overview This is a Service Level Agreement ( SLA ) between and the Student Computer Labs to document: The technology services Student Computer Labs provides to the customer The targets for response
More informationCustomized Cloud Solution
Customized Cloud Solution (Overall Cloud Performance Expectations) Last Updated: June 5, 2012 Prepared by: Polleo Systems, Inc. Notice of Confidentiality: The enclosed material is proprietary to Polleo
More informationAUGUSTA, GA INFORMATION TECHNOLOGY CHANGE MANAGEMENT POLICY & PROCEDURES
AUGUSTA, GA INFORMATION TECHNOLOGY CHANGE MANAGEMENT POLICY & PROCEDURES September 28, 2012 LEAVE THIS PAGE BLANK Contents... 3 Augusta IT Change Management... 5 Objective of Change Management... 5 Augusta
More informationPolish Financial Supervision Authority. Guidelines
Polish Financial Supervision Authority Guidelines on the Management of Information Technology and ICT Environment Security for Insurance and Reinsurance Undertakings Warsaw, 16 December 2014 Table of Contents
More informationExhibit E - Support & Service Definitions. v1.11 / 2015-07-03
Exhibit E - Support & Service Definitions v1.11 / 2015-07-03 Introduction - Support Services Table of Contents 1 Introduction... 4 2 General Definitions... 5 2.1 Support Services... 5 2.2 2.3 License or
More informationREQUEST FOR PROPOSAL-INFORMATION TECHNOLOGY SUPPORT SERVICES
Isothermal Planning & Development Commission (IPDC) REQUEST FOR PROPOSAL-INFORMATION TECHNOLOGY SUPPORT SERVICES Proposals will be received by the IPDC for Information Technology Support Services. Interested
More informationChange Management Process Guide
XXXXX (XX) IT Operational Process Change Management Process Guide XXXXX Information Technology Preface The purpose of this document is to outline the procedures that govern the Change Management process
More informationPrepared by: OIC OF SOUTH FLORIDA. May 2013
OIC OF SOUTH FLORIDA REQUEST FOR PROPOSAL INFORMATION TECHNOLOGY SUPPORT SERVICES Proposals will be received by OIC of South Florida for Information Technology Support Services. Interested vendors should
More informationProcess 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
More informationCUSTOMER SUPPORT DETAILS (CSD)
CUSTOMER SUPPORT DETAILS (CSD) Thank you for your recent purchase with NEWT, the Business Services Division of Fibernetics Corporation. You are a valued customer to us. We welcome you to contact us at
More informationData Center Colocation - SLA
1 General Overview This is a Service Level Agreement ( SLA ) between and Data Center Colocation to document: The technology services Data Center Colocation provides to the customer The targets for response
More informationChange Management Revision Date: October 10, 2014
Change Management Revision Date: October 10, 2014 Why Change Management (CM)? To ensure that standardized methods and procedures are used for efficient and prompt handling of all changes associated with
More informationJITSD Operations Framework
Delivering IT JITSD Operations Framework Change Management Function Version 1.0 Published: October 2013 The Microsoft Operations Framework 4.0 is provided with permission from Microsoft Corporation. Continuous
More informationCUNY Graduate Center Information Technology. IT Change Management Process Last Updated: April 8, 2016
CUNY Graduate Center Information Technology IT Change Management Process Last Updated: April 8, 2016 CHANGE MANAGEMENT Change Management (CM) is the process of communicating, coordinating, scheduling,
More informationMASTER SERVICE LEVEL AGREEMENT (MSLA)
MASTER SERVICE LEVEL AGREEMENT (MSLA) Charles Darwin University Document Owner Service Level Manager Zubair NAQVI Zubair NAQVI Version Date Revision/Description Author 1.00 16 February 2010 Creation Zubair
More informationBrandMaker Service Level Agreement
BrandMaker Service Level Agreement BrandMaker Service Level Agreement v1.1, 18-02-2014, page 1 of 6 I. Support 1 Object of the agreement The object of these terms and conditions is the support of standard
More informationFLORIDA 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,
More informationManaged IT Services. Maintain, manage and report
Managed IT Services Maintain, manage and report 1 2 Comunet was established in 1995 to provide professional Information Technology services to Australian businesses and organisations. Its vision now, as
More informationMANAGED FIREWALL SERVICE. Service definition
MANAGED FIREWALL SERVICE Service definition Page 1 of 4 Version 1.2 (03/02/2015) NSMS Managed Firewalls Service Definition Understanding of a firewall service The function of any firewall service is to
More informationAutomated IT Asset Management Maximize organizational value using BMC Track-It! WHITE PAPER
Automated IT Asset Management Maximize organizational value using BMC Track-It! WHITE PAPER CONTENTS ADAPTING TO THE CONSTANTLY CHANGING ENVIRONMENT....................... 1 THE FOUR KEY BENEFITS OF AUTOMATION..................................
More informationSystem Center Configuration Manager Overview
System Center Configuration Manager Overview This document provides some background information on the Microsoft Systems Center Configuration Manager (SCCM) system, which has been selected for use as an
More informationCisco TelePresence Select Operate and Cisco TelePresence Remote Assistance Service
Cisco TelePresence Select Operate and Cisco TelePresence Remote Assistance Service Cisco TelePresence Select Operate allows customers to make full use of the benefits of the Cisco TelePresence solution,
More informationInformation Systems Change Management and Control
Information Systems Change Management and Control (Sample Document - Not for Distribution) Copyright 1996-2012 Management Systems Consulting, Inc. Table of Contents Page 1.0 Procedure Description... 1
More informationThe 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
More informationOPERATIONAL SERVICE LEVEL AGREEMENT BETWEEN THE CLIENT AND FOR THE PROVISION OF PRO-ACTIVE MONITORING & SUPPORT SERVICES
OPERATIONAL SERVICE LEVEL AGREEMENT BETWEEN THE CLIENT AND FOR THE PROVISION OF PRO-ACTIVE MONITORING & SUPPORT SERVICES IN CONFIDENCE TABLE OF CONTENTS 1 CONTACT DETAILS 1 1.1 The Client Contract Management
More informationUMHLABUYALINGANA MUNICIPALITY IT CHANGE MANAGEMENT POLICY
UMHLABUYALINGANA MUNICIPALITY IT CHANGE MANAGEMENT POLICY Originator IT Change Management Policy Approval and Version Control Approval Process: Position or Meeting Number: Date: Recommended by Director
More informationPLUMgrid Toolbox: Tools to Install, Operate and Monitor Your Virtual Network Infrastructure
Toolbox: Tools to Install, Operate and Monitor Your Virtual Network Infrastructure Introduction The concept of Virtual Networking Infrastructure (VNI) is disrupting the networking space and is enabling
More informationWHITE PAPER. Automated IT Asset Management Maximize Organizational Value Using Numara Track-It! p: 813.227.4900 f: 813.227.4501 www.numarasoftware.
WHITE PAPER By Tony Thomas Senior Network Engineer and Product Manager Numara TM Software Inc. ADAPTING TO THE CONSTANTLY CHANGING IT ENVIRONMENT The challenge in controlling the corporate IT infrastructure
More informationOhio University Office of Information Technology
Standard Desktop Support General Overview Standard Desktop Support service level of the Office of Information Technology (OIT) is comprised of: The Standard Desktop Support (SDS) Service The general levels
More informationService Level Agreement Between: Computing and Informational Technology And The Finance and Business Operations Division
Service Level Agreement Between: Computing and Informational Technology And The Finance and Business Operations Division 1/9 1. Executive Summary This Service Level Agreement ( SLA ) is between Computing
More informationHUIT 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
More informationAll other issues are to be submitted via a request ticket utilizing the Web Helpdesk found at https://helpdesk.tbcdsb.on.ca
Information Technology This Information Technology (ITSLA) establishes the overall support levels for IT supported systems and services within the Thunder Bay Catholic District School Board. Goals of Technology
More informationNYSED DATA DASHBOARD SOLUTIONS RFP ATTACHMENT 6.4 MAINTENANCE AND SUPPORT SERVICES
NYSED DATA DASHBOARD SOLUTIONS RFP ATTACHMENT 6.4 MAINTENANCE AND SUPPORT SERVICES 1. Definitions. The definitions below shall apply to this Schedule. All capitalized terms not otherwise defined herein
More informationHow To Protect Your Network From Attack From A Network Security Threat
Cisco Security Services Cisco Security Services help you defend your business from evolving security threats, enhance the efficiency of your internal staff and processes, and increase the return on your
More informationManaged Support Policy
TABLE OF CONTENTS 1. SERVICE DESCRIPTION 2 2. SUPPORT OPTIONS 2 3. SERVICE SUPPORT HOURS 3 4. MONITORING AND OUTAGES 3 5. SERVICE LEVEL AGREEMENT 4 6. PLANNED MAINTENANCE AND UPGRADES 5 7. TARGET UPTIME
More informationV1.5. Standard Terms & Conditions and Service Level Agreement
Standard Terms & Conditions and Service Level Agreement Datacentreplus provides a number of services from our Manchester Data Centre. Dedicated Servers: Units that are built to our high specification or
More informationService Level Agreement for Database Hosting Services
Service Level Agreement for Database Hosting Services Objective Global Service Levels include the general areas of support that are applicable to every ITS service. The purpose of the Service Level Agreement
More informationSheridan/Gillette College IT Help Desk Service Level Agreement
Sheridan/Gillette College IT Help Desk Service Level Agreement Information Technology Help Desk The IT Help Desk is the single point of contact for all computer, telephone, networking, video conference
More informationHow To Use Adobe Software For A Business
EXHIBIT FOR MANAGED SERVICES (2013V3) This Exhibit for Managed Services, in addition to the General Terms, the OnDemand Exhibit, and any applicable PDM, applies to any Managed Services offering licensed
More informationASIAN PACIFIC TELECOMMUNICATIONS PTY LTD STANDARD FORM OF AGREEMENT. Schedule 3 Support Services
ASIAN PACIFIC TELECOMMUNICATIONS PTY LTD STANDARD FORM OF AGREEMENT Schedule 3 Support Services December 2013 Table of Contents 1. SERVICE SCHEDULE 3 SUPPORT SERVICES... 3 1.1 OVERVIEW... 3 1.2 STANDARD
More informationN(i) 2 WHITE PAPER on CHANGE MANAGEMENT
on CHANGE MANAGEMENT ABOUT THIS... 2 IT AND CHANGE MANAGEMENT... 3 RESPONDING TO PERFORMANCE AND ACCOUNTABILITY DEMANDS...3 AN EMERGING NEED FOR CHANGE MANAGEMENT...3 DEFINING CHANGE MANAGEMENT... 4 WHAT
More information.trustwave.com Updated October 9, 2007 TECHNICAL ASSISTANCE CENTER (TAC) SUPPORT GUIDE
.trustwave.com Updated October 9, 2007 TECHNICAL ASSISTANCE CENTER (TAC) SUPPORT GUIDE Legal Notice Copyright 2015 Trustwave Holdings, Inc. All rights reserved. This document is protected by copyright
More informationRUTGERS POLICY. Section Title: Legacy UMDNJ policies associated with Information Technology
RUTGERS POLICY Section: 70.2.12 Section Title: Legacy UMDNJ policies associated with Information Technology Policy Name: IT Change Management Formerly Book: 95-01-04-01:01 Approval Authority: Vice President
More informationOhio Supercomputer Center
Ohio Supercomputer Center IT Business Continuity Planning No: Effective: OSC-13 06/02/2009 Issued By: Kevin Wohlever Director of Supercomputer Operations Published By: Ohio Supercomputer Center Original
More information[name of project] Service Level Agreement
[name of project] Service Level Agreement Policies and Procedures Posting: Nov.2008 Rev# xxx CIO Sign-Off: Approved and Reviewed By: Date: Document ID: SLA Revision 001 Authors: Disclaimer: Document sign-off
More informationCommunity Anchor Institution Service Level Agreement
Community Anchor Institution Service Level Agreement Date: 3/13/2014 Version: 2.0 Prepared by: DC-Net Table of Contents 1 Service Level Agreement... 3 2 Definitions... 3 3 Service Delivery... 5 3.1 Network
More informationIT CHANGE MANAGEMENT POLICY
IT CHANGE MANAGEMENT POLICY PURPOSE The purpose of the IT Change Management Policy is to manage changes in a planned and predictable manner in order to assign resources, assess risk and minimize any potential
More informationITP01 - Patch Management Policy
IT Services Policy ITP01 - Patch Management Policy Prepared by: < Shelim Miah> Version: V1.0 Page 1 of 8 Description & Target Audience: Policy to outline the requirement of all systems and software applications
More informationRSA SecurID Tokens Service Level Agreement (SLA)
RSA SecurID Tokens Service Level Agreement (SLA) 1. Agreement This Agreement defines RSA SecurID services provided to a Customer. Service definitions include responsibilities, hours, availability, support
More informationService Support. First Level Support (Tier I) provides immediate response to emergencies and customer questions. TSD - First Level Support
Service Support 1.1. First Level Support First Level Support (Tier I) provides immediate response to emergencies and customer questions TSD - First Level Support Office: Sub-Division: Extension: E-mail:
More informationSample Vulnerability Management Policy
Sample Internal Procedures and Policy Guidelines February 2015 Document Control Title: Document Control Number: 1.0.0 Initial Release: Last Updated: February 2015, Manager IT Security February 2015, Director
More informationYale 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
More informationService Level Agreement: Support Services (Version 3.0)
Service Level Agreement: Support Services (Version 3.0) This Service Level Agreement ("SLA") is attached to the Agreement (Number [ ]) entered into between Uniware Systems Limited ("Uniware") and the Customer
More informationRequest for Proposals (RFP) Managed Services, Help Desk and Engineering Support for Safer Foundation www.saferfoundation.org
Request for Proposals (RFP) Managed Services, Help Desk and Engineering Support for Safer Foundation www.saferfoundation.org IMPORTANT NOTICE All proposal question and inquiries must be sent by email to
More informationGuide to Vulnerability Management for Small Companies
University of Illinois at Urbana-Champaign BADM 557 Enterprise IT Governance Guide to Vulnerability Management for Small Companies Andrew Tan Table of Contents Table of Contents... 1 Abstract... 2 1. Introduction...
More informationManaged Services Agreement. Hilliard Office Solutions, Ltd. PO Box 52510 Phone: 432-617-4677 Midland, Texas 79710 Fax: 432-617-3043
Managed Services Agreement Hilliard Office Solutions, Ltd. PO Box 52510 Phone: 432-617-4677 Midland, Texas 79710 Fax: 432-617-3043 SERVICE DESCRIPTIONS By purchasing these Services from Hilliard Office
More informationMSA Enterprise 1. GENERAL TERMS AND CONDITIONS
1 1. GENERAL TERMS AND CONDITIONS Herein is given a list of technical support cases, in relation to which Kaspersky Lab will provide assistance to the owner of this Extended Technical Support Certificate
More informationSERVICE LEVEL AGREEMENT
SERVICE LEVEL AGREEMENT This service level agreement ( SLA ) is incorporated into the master services agreement ( MSA ) and applies to all services delivered to customers. This SLA does not apply to the
More informationData Center Services
Data Center Services Production Support Providing Call, Incident, and Change Management for customers throughout the Johns Hopkins Enterprise The Johns Hopkins Health Systems And The Johns Hopkins University
More informationCTERA Support Policy
CTERA Support Policy May 2015 Version 2.0 2015, CTERA Networks. All rights reserved. Contents Our Commitment to Support ------------------------------------------------------------------------ 2 Terms
More informationMiServer and MiDatabase. Service Level Expectations. Service Definition
MiServer and MiDatabase Service Description Service Definition As part of the NextGen Michigan initiative, Information and Technology Services has engaged in building a private cloud offering to support
More informationINFORMATION TECHNOLOGY SERVICES TECHNICAL SERVICES June 2012
INFORMATION TECHNOLOGY SERVICES TECHNICAL SERVICES June 2012 Program Description Network Services is a service unit in Information Technology Services responsible for designing, acquiring, deploying, operating,
More informationFully Managed IT Support. Proactive Maintenance. Disaster Recovery. Remote Support. Service Desk. Call Centre. Fully Managed Services Guide July 2007
Fully Managed IT Support Proactive Maintenance Disaster Recovery Remote Support Service Desk Call Centre London Office ITVET Limited 2 nd Floor 145 157 St John Street London EC1V 4PY t: +44(0)8704 232
More informationCCIT 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.
More informationIT Services. incident criteria
IT Services IT Services incident criteria Guidance for IT Services staff on priorities to be used when logging incidents. Introduction... 2 Definitions... 2 Response time... 2 Resolution times... 2 Minimum
More informationFacilitated By: Ken M. Shaurette, CISSP, CISA, CISM, CRISC FIPCO Director IT Services
Facilitated By: Ken M. Shaurette, CISSP, CISA, CISM, CRISC FIPCO Director IT Services 1 Today s Agenda Structure of Today s Discussion Set Objectives General overview of DR/BCP Exercise Assumptions Scenarios
More informationGMS NETWORK ADVANCED WIRELESS SERVICE PRODUCT SPECIFICATION
GMS NETWORK ADVANCED WIRELESS SERVICE PRODUCT SPECIFICATION 1. INTRODUCTION This document contains product information for the GMS Network Service. If you require more detailed technical information, please
More informationHandshake Customer Support Handbook
Handbook Handshake Customer Support Handbook Document History Prepared By 8/1/2014 Handshake Software Version : 5.0 Caroline McManus +1 (850) 329-7845 cmcmanus@handshakesoftware.com Abstract: This Handbook
More informationIT Service Desk Workflow Management in versasrs HelpDesk
Service Level Management The Keystone of versasrs HelpDesk This document outlines IT Service Desk Workflow within versasrs HelpDesk. versasrs HelpDesk is a packaged application enabling organisations to
More informationEXIN IT Service Management Foundation based on ISO/IEC 20000
Sample Exam EXIN IT Service Management Foundation Edition October 2013 Copyright 2013 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing
More informationSystems Support - Standard
1 General Overview This is a Service Level Agreement ( SLA ) between document: and Enterprise Windows Services to The technology services Enterprise Windows Services provides to the customer The targets
More informationStatement of Service Enterprise Services - AID Microsoft IIS
Statement of Service Enterprise Services - AID Microsoft IIS Customer Proprietary Rights The information in this document is confidential to Arrow Managed Services, Inc. and is legally privileged. The
More informationEnterprise UNIX Services - Systems Support - Extended
1 General Overview This is a Service Level Agreement ( SLA ) between and Enterprise UNIX Services to document: The technology services Enterprise UNIX Services provides to the customer. The targets for
More informationREQUEST FOR PROPOSALS INFORMATION TECHNOLOGY SUPPORT SERVICES. Bid Packets are Due:
REQUEST FOR PROPOSALS INFORMATION TECHNOLOGY SUPPORT SERVICES Issue Date: Friday, March 15 th, 2013 Closing Date: Monday, April 15 th, 2013 University City District is requesting proposals from qualified,
More informationi. Maintenance of the operating system, applications, content on the server, or fault tolerant network connections
Physical Co-location Service Level Agreement 1. Agreement This agreement is to define Physical Server Co-location services provided to a Customer. Typically, service definitions include hours, availability,
More informationINFORMATION TECHNOLOGY SERVICES IT CHANGE MANAGEMENT POLICY & PROCESS
INFORMATION TECHNOLOGY SERVICES IT CHANGE MANAGEMENT POLICY & PROCESS Revised: 12/5/2011 Table of Contents Overview... 3 Roles and Responsibilities... 4 Management Process Definition... 6 Management Process
More information1 Introduction. 2 Design and Functionality. 3 Client Support
Changefirst Enterprise Service Level Agreement 1 Introduction This Service Level Agreement between Changefirst and the Client describes the support processes and services which Changefirst provides to
More informationInfrastructure Change Management. The process and procedures for all changes to the live environment
Infrastructure Change Management The process and procedures for all changes to the live environment Version 4.1 October 2012 1.0 Introduction... 3 2.0 The Change Process... 4 2.1 Why raise a change?...
More informationManaged Storage Service Level Agreement (SLA)
Service Level Agreement Page 1 of 8 Managed Storage Service Level Agreement (SLA) Vanderbilt Information Technology Services 1. Parties to the Agreement This service level agreement is valid from the start
More informationSTATE OF NEW JERSEY IT CIRCULAR
NJ Office of Information Technology P.O. Box 212 www.nj.gov/it/ps/ Chris Christie, Governor 300 River View E. Steven Emanuel, Chief Information Officer Trenton, NJ 08625-0212 STATE OF NEW JERSEY IT CIRCULAR
More information