How To Manage Change Management At Uni
|
|
- Herbert Payne
- 3 years ago
- Views:
Transcription
1 Change Management Process VERSION 1.0 Version Date: 1 May 2006
2 Table of Revisions REVISION NUMBER DESCRIPTION OF CHANGES (PARAGRAPH AND OR SECTION NUMBERS FOR REVISION TRACKING) DATE OF CHANGE REVIEWED / REVISED BY 0.1 Final Draft Brad Lytle 0.2 Updated procedures to reflect Lotus Notes Change Brad Lytle Request system 1.0 Formal Implementation Brad Lytle UNCG Proprietary & Confidential 2
3 Table of Contents 1.0 INTRODUCTION SCOPE AND OBJECTIVES DEFINITIONS CHANGE MANAGEMENT PROCESS PROCESS IMPLEMENTATION STANDARD CHANGES, EMERGENCY CHANGES, AND OUTAGES RISK ASSESSMENT IMPACT ASSESSMENT CHANGE NOTIFICATION REQUEST FOR CHANGE APPROVAL ROLES AND RESPONSIBILITIES CHANGE MANAGER CHANGE ADVISORY BOARD CHANGE REQUESTER CHANGE ASSIGNEE CHANGE APPROVER CHANGE MANAGEMENT PROCEDURES CREATING REQUEST FOR CHANGES STANDARD RFC s EMERGENCY RFC s APPROVAL OF RFC s PEER REVIEW CHANGE ADVISORY BOARD PROCEDURES CHANGE ADVISORY BOARD MEETINGS COMMUNICATING PLANNED CHANGES INFORMATION SECURITY UNCG Proprietary & Confidential 3
4 1.0 INTRODUCTION The Information Technology Services (ITS) Change Management process is designed to control the implementation of all changes made to any device or application within the UNCG production environment. The academic and administrative requirements of the university demand highly available and functional technology services. The ITS Change Management process exists to ensure ITS can provide a high level of availability and integrity in the delivery of technology services. 1.1 SCOPE AND OBJECTIVES The scope of the ITS Change Management Process includes all infrastructure, applications, and services used by the UNCG client community for business or academic purposes. The objectives of the ITS Change Management Process are to ensure that: All Changes are properly analyzed, documented, and communicated to ITS staff and to all functional groups and clients potentially affected by, or involved in, their execution.* Details of all Changes are tracked and stored in a central Change Management System for the purpose of historical trending and reporting. Procedures required before, during, and after Change execution and the respective areas of responsibility are clearly documented and published. The proper analysis and testing is performed to assess the need for a change versus the potential impact of the change. No Change is executed without first being properly planned, documented, peer reviewed, tested, and approved. *For details, see Section 3.3 Communicating Planned Changes 1.2 DEFINITIONS Change CAB Change Manager RFC Any modification to the systems, infrastructure, or applications that comprise the UNCG production environment, with the exception of basic object administration tasks that do not affect service functionality. Change Advisory Board Organizational entity responsible for the assessment, approval, and planning of changes. Individual responsible for the overall Change Management process and its proper execution. Request for change A request to implement a Change within the UNCG production environment. UNCG Proprietary & Confidential 4
5 CMS UNCG ITS SOC Production Environment Change Management System Software tool or combination of tools utilized for the request, approval, tracking and details of changes. The University of North Carolina at Greensboro Information Technology Services Service Operations Center All system, network, infrastructure, and software that supports the technology services utilized by the UNCG client community for business and academic purposes. Environments utilized for testing and development are not considered to be production. 2.0 CHANGE MANAGEMENT PROCESS To ensure the integrity, consistency and availability of the UNCG technology services, all changes to the UNCG production environment will be tracked via a Request for change (RFC). RFC s will be entered into and managed via the Change Management System (CMS) to ensure Changes are centrally tracked, approved, reported upon, and enforced in a reliable and consistent manner. RFC s must be reviewed and approved by the Change Advisory Board (CAB) prior to execution to ensure a proposed Change does not compromise the stability of the production environment. Changes to the UNCG production environment must be: Implemented using the standard Change Management Process. Documented prior to, during, and after Change execution. Assessed for risk to the production environment, assigned the appropriate risk level and handled according to the level assigned. Submitted with implementation and rollback plans, as well as an assessment of the probability of failure. Peer reviewed by at least one other qualified staff member. Coordinated with all people required to implement and verify functionally. Classified and submitted through the Change Management process as the proper Change type to ensure all affected parties are aware of and prepared for the impending Change* Communicated to the appropriate user community if the change has any potential impact on the user base, including a temporary service outage.** Approved by the appropriate manager(s). Monitored and closed in a timely manner. * For Change type definitions, see Section Standard Changes, Emergency Changes, and Outages **For details, see Section 3.3 Communicating Planned Changes UNCG Proprietary & Confidential 5
6 2.1 PROCESS IMPLEMENTATION While the Change Management process begins with the initial user request for change, the information presented in this section focuses primarily on those tasks necessary for the implementation of a production change STANDARD CHANGES, EMERGENCY CHANGES, AND OUTAGES As timing, impact and other factors vary due to the urgency and nature of some Changes, there is a need to define standards to differentiate between Standard Changes, Emergency Changes, and Outages. For the purposes of ITS process, these definitions are the following: Standard Change Any Change that is scheduled and receives approval for execution from the CAB prior to its execution. Emergency Change Any change that has a level of urgency that requires its execution to take place prior to the CAB having an opportunity to review and approve it. Emergency Changes must have a valid business justification and must receive approval from an ITS Manager and an ITS Associate Vice Chancellor prior to its execution. Outage An outage is a loss of one or more services delivered by ITS. Work done on infrastructure or applications supporting a service that is already unavailable due to an outage, are not considered a Change for the purposes of this process and do not need to follow the Change Management process. This work will be tracked via the Incident Management Process related to the outage. The Service Operations and Support group and Client Services must be notified of a planned change of any kind prior to its execution RISK ASSESSMENT An assessment of risk must be completed on any Change prior to its approval. This assessment should be done at a minimum of three points throughout the Change Management Process. They are: 1. By the Change Assignee at the time of creating the request. 2. By the Change Approver prior to approving the request to go before the CAB. 3. By the Change Advisory Board prior to giving final approval for the execution of the change. In assessing the risk level of a change, the following factors must be considered: Probability of customer impact Potential level of customer impact UNCG Proprietary & Confidential 6
7 Probability of success/failure Potential impact of failure Possibility of roll back Potential roll back or recovery time Once the appropriate level of risk is determined, it should be balanced with the level of need for the change prior to making the initial request or at each stage of approval IMPACT ASSESSMENT Below are guidelines for determining the appropriate level of customer impact: High Any service outage of a mission critical system or application, and/or multiple users are not able to perform their normal business functions Medium Service outage of a non mission critical system or application. Low Service interruption with no noticeable impact on end user s ability to perform their business functions. None No anticipated impact on the end user community CHANGE NOTIFICATION It is the responsibility of the Change Assignee to ensure: Any change to the production environment that has potential impact to service availability, performance or usage is communicated to the affected user communities.* All changes are communicated to the Service Desk, Service Operations Center, and Client Services. The Request for change is approved by the Change Approver. All of the above is completed prior to CAB review of the Request for change. All mass communication is sent via the ITS Communications Office. *For details, see Section 3.3 Communicating Planned Changes REQUEST FOR CHANGE APPROVAL Standard Request for change A Standard RFC must receive two levels of approval prior to execution. The first approval must come from the Change Approver. The second approval must come from the Change Advisory Board. Emergency RFC An Emergency RFC must receive two levels of approval. The first approval must come from the Change Approver. The second approval must come from an ITS Associate Vice Chancellor. UNCG Proprietary & Confidential 7
8 2.2 ROLES AND RESPONSIBILITIES Within the Change Management process, specific roles and functions have been defined. Each role is ultimately responsible for completing specific tasks within this process CHANGE MANAGER The Change Manager is responsible for the overall facilitation of the Change Management process. Responsibilities of the Change Manager include: Coordinate and chair the weekly meetings of the Change Advisory Board. Facilitate the resolution of any schedule conflicts that may arise. Maintain the policies and procedures necessary to carry necessary CM functions. Grant access to the Change Management Database. Ensure any non standard notification of user communities or POCs is performed CHANGE ADVISORY BOARD The Change Advisory Board (CAB) is a group of individuals that represent various ITS and Client communities. This group is responsible for final review and approval/rejection of all standard RFC s. The CAB meets at a regularly scheduled interval to review all pending RFC s but can also perform their function remotely ( , telephone) if necessary. In addition to the normal CAB members, the Change Assignee (or a staff member sent in their stead) who has a pending RFC submitted for review by the CAB shall attend board meetings. All Changes are reviewed by the CAB during its periodic meeting. The CAB has the authority to do any of the following: Cancel or reject changes Approve RFC s as presented Re assess the risk level of a Change Re assess the impact level of a Change Request additional information prior to approval Note: Emergency RFC s, due to their urgent nature, may be performed without prior review by the CAB only if written approval from an ITS Associate Vice Chancellor has been received. UNCG Proprietary & Confidential 8
9 2.2.3 CHANGE REQUESTER The Change Requester is the person who initially requests that a Change take place. Often, though not always, this is carried out through initiation of a support request to the ITS Service Desk, which enters and tracks support actions in the Remedy application. In such a case, the action request is ultimately assigned to the person/organization whose function it is to implement changes of the requested type. The Change Requester must provide all the requirements and objectives for the change, including an explanation of the reason and justification for the proposed change. If the Change Requester does not provide adequate detailed information, the Change Assignee or Change Approver have the authority to require it before creating the RFC. In the event that the Change Requestor is also the Change Assignee, that person will have the responsibilities of both roles. The responsibilities of the Change Requester include: Initial escalation/request for change (via Service Desk, Call Tracking Software, etc.). Provision of business and technical requirements to the Change Assignee. Resolution or escalation of Change issues. Provide input to the assessment of the change s level of risk. Provide input to the assessment of the change s level of impact. Change planning and coordination. Review of the Change plan/documentation. Ensure the user community affected by the change is notified prior to the change implementation. Facilitate any required client testing before, during or after Change execution CHANGE ASSIGNEE The Change Assignee is the owner of the Change. This person will work with the Change Requestor (if it is someone else) to gather the appropriate information required to create and represent the RFC. Responsibilities of the Change Assignee include: Creation of the RFC including Peer Review of the change. Communication and coordination of Change testing and implementation. Meet with the Change Requester, as needed, to resolve any questions or problems with a proposed change. Update any related documentation after the change has been implemented. Update the status of the RFC and enter all necessary information into the CMS, which may be helpful for historical purposes. Follow up with the Change Requester to provide status on the implementation success or failure. Provide closure status in the CMS. UNCG Proprietary & Confidential 9
10 2.2.5 CHANGE APPROVER The Change Approver is the manager who provides the first level of approval to a RFC, allowing it to go before the CAB for review. In most cases, this is the manager of the Change Assignee. If that is not possible, the Change Approver can be any ITS manager or above. Responsibilities of the Change Approver include: Review all RFC s submitted by staff members of their group Ensure all necessary communication, coordination, documentation and testing has been completed properly on all RFC s prior to approval Approve all RFC s prior to them being submitted for review by the Change Advisory Board 3.0 CHANGE MANAGEMENT PROCEDURES Change Management procedures have been developed and implemented that take into account the impact of changes to UNCG s administrative and academic activities including system availability, user impact, system efficiency and currency/usability of documentation. A major goal of the process development effort was to establish a set process that facilitated the coordination of changes within the UNCG production environment. This process will be changed as needed. 3.1 CREATING REQUEST FOR CHANGES (RFC S) STANDARD RFC S The creation and submission procedures for a Standard RFC are below, by area of responsibility: Change Assignee: 1. Complete a RFC via the Change Management Database in Lotus Notes. Completion of this request will require the Change Assignee to: a) Check the critical Events Calendar to ensure that the intended date for the change will not conflict with other activities. b) Assess the risk vs. benefit of the change (refer to Risk Assessment, section 2.1.2), and assign a risk level for the change. c) Have a peer review the changes and annotate that they have reviewed the change and concur with the planning of the change (see Peer Review, section 4.1.4) d) Communicate and coordinate with all necessary support and client personnel PRIOR to submitting the RFC.* UNCG Proprietary & Confidential 10
11 2. Once the RFC has been fully completed, submit for approval by the Change Approver. (This will initiate an notification to the Change Approver(s) alerting them to the submitted RFC) Change Approver: 3. Review the RFC and Approve or Reject the request. Approval will advance the RFC to the First Level Approved status and a notification will be sent to the next level of approvers for review. Rejection will send a notification to the Change Assignee stating that the RFC has been rejected. Change Advisory Board: 4. Review the details of the RFC and approve or reject the request. Approval will advance the RFC to the Final Approval status. Rejection will send a notification to the Change Assignee stating that the RFC has been rejected. Change Assignee: 5. For approved RFC s, create a Remedy Case for the scheduled Change. Enter the Remedy Case # in the RFC. 6. Execute the Change at the scheduled time and update the Remedy Case appropriately. 7. After the Change is complete, indicate the appropriate Disposition of the Change in the RFC. Update the Remedy Case with any details of the Change and Resolve if appropriate. *For details, see Section 3.3 Communicating Planned Changes EMERGENCY RFC S Emergency Changes are usually the result of actual or imminent hardware or software failures impacting or threatening to impact a UNCG technology service. They are implemented before the Change Advisory Board has had an opportunity to review them. These Changes must be associated with a Remedy Case and must still be communicated and documented in the Change Management process within 24 hours from the time of execution. In the event an Emergency Change is warranted, the Change Assignee will: 1. Notify a Director or above of the situation and that an Emergency Change is needed and receive written approval to execute the Change. 2. Notify the Service Desk and Service Operations Center and provide sufficient details to enable them to respond to calls from users who may be impacted by the change, as well as identify monitoring alarms that may be associated with the Change. Coordinate, as reasonable, any emergency communications necessary through the approving Director or above. UNCG Proprietary & Confidential 11
12 3. Execute the Change. 4. Once the Change is completed, notify the Service Desk and Service Operations Center and advise them of the success or failure as well as the current state of the impacted environment. 5. Complete a RFC within 24 hours of resolution of the Change execution and submit it for approval by the Director or above involved APPROVAL OF RFC S When the Change Approver is notified of a pending RFC, they will: 1. Review the RFC to ensure the appropriate actions have taken place, including but not limited to peer review of the proposed solution, plan for notification of the user community if required, and coordination of change with appropriate teams. 2. Approve or Deny the RFC. If the RFC is not approved, the Change Requester can take one of the following steps: a) Cancel the request completely, b) Complete the necessary steps as indicated at the time of Rejection, and resubmit the request c) Request that the request be forwarded on to the Change Approver s supervisor. The Change Approver s Rejection of the request will remain documented in the Change Management System PEER REVIEW Once a RFC has been completed and is ready to be submitted to the Change Approver for initial approval, the Change Assignee must request a review of the RFC from a technical peer with similar knowledge of the environment where the Change will take place. The technical peer will review the RFC and ensure that the specific technical steps planned appear to be correct. Once this is verified, the technical peer will update the RFC, indicating that they have reviewed the technical steps of the Change. Note: The technical peer chosen for Peer Review is responsible only for reviewing and validating the technical steps indicated in the RFC to complete the Change itself. This person is not responsible for ensuring other required steps (communication, coordination, scheduling, etc.) are taken. This responsibility is that of the Change Assignee, Change Approver, and CAB. UNCG Proprietary & Confidential 12
13 3.2 CHANGE ADVISORY BOARD PROCEDURES The Change Advisory Board (CAB) will meet periodically for the purpose of reviewing all pending RFC s. The CAB will either approve or reject each RFC during the course of the meeting CHANGE ADVISORY BOARD MEETINGS To prepare for the CAB meeting, the Change Manager will: Summarize and compile all RFC s received prior to the meeting start time into a report. This report will be called the Change Summary Sheet. The report must contain sufficient information for each change to ensure the Board members understand and can evaluate the change being proposed. The report contents will be further grouped by the following subcategories: New Requests Existing Requests Each report entry contains: Description of the Change Location of proposed Change Locations and user communities potentially impacted by the Change Impact on end user communities Name of the Change Requester Name of the Change Assignee Scheduled Date and Time for executing the Change Approval Status of the RFC Name of Change Approver Distribute the Change Summary Sheet to all members of the CAB prior to the scheduled meeting. During the CAB meeting, the members of the CAB will review and discuss each RFC as a group to ensure that it meets all requirements of the Change Management Process. The CAB may call upon the Change Assignee to answer any questions that may arise about their RFC during the meeting. All Change Assignees who have a RFC pending must attend the CAB meeting or send a representative from their department who can properly represent and discuss the Change. Failure to do so may result in the automatic Rejection of the RFC. Rejected RFC s can be updated and re submitted to the CAB for review at a later date. UNCG Proprietary & Confidential 13
14 3.3 COMMUNICATING PLANNED CHANGES All planned Changes that will impact, or have the potential to impact, a production service must be communicated to the users of that service prior to execution. All communication details must be coordinated by the Change Assignee and approved by the CAB PRIOR to being sent. All mass communication must be sent via the ITS Communications Office. The Change Assignee is responsible for notifying the Service Desk and Service Operations Center immediately before and immediately after the execution of an approved Change. If physical access to the machine room is required for an approved Change, the Change Assignee must be able to produce a printed copy of the approved RFC to Service Operations Center personnel before accessing the machine room to execute the Change. 3.4 INFORMATION SECURITY A staff member of ITS charged with Information Security will be a required member of the CAB and must attend all CAB meetings. ALL RFC S must be reviewed for information security implications prior to CAB approval. Considerations in this review include, but are not limited to,: Implications to the security of personal information (Social Security Number, Date of Birth, etc.) Implications to the security of university sensitive or confidential data. Implications to the security of university equipment. Compliance implications (HIPAA, FERPA, etc.) UNCG Proprietary & Confidential 14
Georgia College & State University
Georgia College & State University Milledgeville, GA Change Management Control Procedures 1 Change Management Control Table of Contents TABLE OF REVISIONS... 3 SECTION 1: INTRODUCTION... 4 1.1 Scope and
More informationProcess Owner: Change Manager Version: 1.0
BMC REMEDY 8.1 CHANGE MANAGEMENT USER GUIDE Process Owner: Change Manager Version: 1.0 DOCUMENT REVISION HISTORY Revision Description Date Approved by Number V1.0 Initial Release 6/25/2015 6/25/2015 Page
More informationWhite 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,
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 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 informationPage 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
More informationWhite Paper: BMC Service Management Process Model 7.6 BMC Best Practice Flows
White Paper: BMC Service Management Process Model 7.6 BMC Best Practice Flows October 2009 www.bmc.com Contacting BMC Software You can access the BMC Software website at http://www.bmc.com. From this website,
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 informationChange 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
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 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 informationChange Management. Change Management Procedure. Table of Contents. (Revision Date: 1/30/2014)
Change Management Change Management Procedure (Revision Date: 1/30/2014) Table of Contents I. Introduction... 2 II. Scope... 2 III. Objective... 2 IV. Definition of a Change... 2 V. Roles and Responsibilities...
More informationCHG-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
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 informationTitle: DISASTER RECOVERY/ MAJOR OUTAGE COMMUNICATION PLAN
POLICY: This policy is intended to address organizational wide communication executed during a or major IS service outage. When a disaster occurs or when any critical system/infrastructure component is
More informationThe ICT Change Management Process
CHANGE MANAGEMENT CHARTER Client Services Information Technology Services Author: Rod Walker Version: 1.0 Document Change History Version Date Changed By Modifications 0.1 19/02/2013 Rod Walker Initial
More informationColby College Information Systems and Data Security Outage and Change Management Procedures
Colby College Information Systems and Data Security Outage and Change Management Procedures 1. Purpose The following outage and change management procedures are intended to provide centralized scheduling,
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 informationFederal Business Opportunities (FedBizOpps.gov) Change Management Plan (CMP)
GSA OFFICE OF GOVERNMENTWIDE POLICY Federal Business Opportunities (FedBizOpps.gov) Change Management Plan (CMP) Issued on October 18, 2002 by the FedBizOpps Program Management Office in consultation with
More informationTECHNICAL SUPPORT GUIDE
TECHNICAL SUPPORT GUIDE Copyright 2009 Fiberlink Corporation. All rights reserved. Information in this document is subject to change without notice. The software described in this document is furnished
More informationChange Management Policy
Change Management Policy Change management refers to a formal process for making changes to IT services. The goal of change management is to increase awareness and understanding of proposed changes across
More informationCentral Agency for Information Technology
Central Agency for Information Technology Kuwait National IT Governance Framework IT Service Management How many times we felt that Business is looking to IT as Operations center not strategy enabler 1
More informationHP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Incident Management help topics for printing
HP Service Manager Software Version: 9.34 For the supported Windows and UNIX operating systems Incident Management help topics for printing Document Release Date: July 2014 Software Release Date: July
More informationINCIDENT MANAGEMENT & REQUEST FULFILLMENT PROCESSES. Process Owner: Service Desk Manager. Version: v2.0. November 2014 Page 0
INCIDENT MANAGEMENT & REQUEST FULFILLMENT PROCESSES Process Owner: Service Desk Manager Version: v2.0 November 2014 Page 0 Document Revision History Revision Description Date Approved by Number V1.0 Initial
More informationIncident Manager. Notified. Major Incident? YES. Major Incident Declared. Initial Communication Drafted. MIH At A Glance. Major Incident Ended
www.majorhling.com www.braunsblog.com A Major Hling Plan Model Desk Manager Business Resolver Teams (BRT) Communications Step 1 Record / Event Recieved Step 2 Classify Refer as Potential Major Manager
More informationITIL 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:
More informationIT-P-001 IT Helpdesk IT HELPDESK POLICY & PROCEDURE IT-P-001
IT HELPDESK POLICY & PROCEDURE IT-P-001 Date:25 September, 2013 Amemberof, LAUREATE I'.;TlRNAT'Oi'lAl. UWII[RSITIB Stamford International University Policy Policy Statement This Policy has been written
More informationITSM Process Description
ITSM Process Description Office of Information Technology Incident Management 1 Table of Contents Table of Contents 1. Introduction 2. Incident Management Goals, Objectives, CSFs and KPIs 3. Incident Management
More informationITIL 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
More informationComputer Security Incident Response Team
University of Scranton Computer Security Incident Response Team Operational Standards Information Security Office 1/27/2009 Table of Contents 1.0 Operational Standards Document Overview... 3 2.0 Establishment
More informationENTERPRISE CHANGE MANAGEMENT PROCESS
University of California San Francisco ENTERPRISE CHANGE MANAGEMENT PROCESS VERSION 2.00, REV. 6/20/2013 Table of Contents 1 About this Process Document... 6 1.1 Intended Audience... 6 1.2 Assumptions...
More informationHP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Service Desk help topics for printing
HP Service Manager Software Version: 9.34 For the supported Windows and UNIX operating systems Service Desk help topics for printing Document Release Date: July 2014 Software Release Date: July 2014 Legal
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 informationTechnology Event Notification and Escalation Procedures. Procedure: Technology Event Notification and Escalation. Procedure Date: 10/27/2009
Procedure: Technology Event Notification and Escalation Procedure Date: 10/27/2009 1.0 Purpose Information Technology Services (ITS) provides and manages technology in support of the College mission. Changes
More informationVirginia Commonwealth University School of Medicine Information Security Standard
Virginia Commonwealth University School of Medicine Information Security Standard Title: Scope: Business Continuity Management Standard for IT Systems This standard is applicable to all VCU School of Medicine
More informationProcess Description Incident/Request. HUIT Process Description v6.docx February 12, 2013 Version 6
Process Description Incident/Request HUIT Process Description v6.docx February 12, 2013 Version 6 Document Change Control Version # Date of Issue Author(s) Brief Description 1.0 1/21/2013 J.Worthington
More informationITIL 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
More informationRoles 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
More informationTHE UNIVERSITY OF NORTH CAROLINA AT GREENSBORO IDENTITY THEFT PREVENTION PROGRAM
Program Adoption THE UNIVERSITY OF NORTH CAROLINA AT GREENSBORO IDENTITY THEFT PREVENTION PROGRAM As a best practice and using as a guide the Federal Trade Commission s ( FTC ) Red Flags Rule, implementing
More informationIncident Response Team Responsibilities
Scope Any incidents that originate from, are directed towards, or transit Department of Earth and Planetary Sciences controlled computer or network resources will fall under the purview of this Incident
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 informationHP Service Manager. Service Desk help topics for printing. For the supported Windows and UNIX operating systems. Software Version: 9.
HP Service Manager For the supported Windows and UNIX operating systems Software Version: 9.32 Service Desk help topics for printing Document Release Date: August 2013 Software Release Date: August 2013
More informationBusiness & Finance Information Security Incident Response Policy
Business & Finance Information Security Incident Response Policy University of Michigan http://www.umich.edu/~busfin/ Document Version: 10 Effective Date: 6/1/2006 Review Date: 7/31/2009 Responsible: Approval
More informationAssigning Severity Codes
Technical Support Service Number:SDT-051111 Version number: 2.0 Effective Date: 2 nd Jan 2010 Assigning Severity Codes The impact of a problem is a composite of many factors: the number of clients affected,
More informationDraft Copy. Change Management. Release Date: March 18, 2012. Prepared by: Thomas Bronack
Draft Copy Change Management Release Date: March 18, 2012 Prepared by: Thomas Bronack Section Table of Contents 10. CHANGE MANAGEMENT... 5 10.1. INTRODUCTION TO CHANGE MANAGEMENT... 5 10.1.1. PURPOSE OF
More informationNovo Service Desk Software
Product Data Sheet The Novo Service Desk has helped streamline processes, reduce costs, provide better metrics, and run a more efficient help desk Lender Processing Services Novo Service Desk Software
More informationSoftware Quality Assurance (SQA) Testing
Service Description Services is a subscription fee based managed shared service, which offers a highly reliable, scalable, secure, and cost-effective testing platform that state agencies and local government
More informationOverview 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
More informationmeans the charges applied by Ancar B Technologies Limited which recur annually;
This Service Schedule is supplemental to the Master Service Agreement Net-L1-3. CONTENTS Schedule 1 - DEFINITIONS... 1 Schedule 2 - MANAGED INTERNET ACCESS SERVICE PRODUCT INFORMATION... 3 1 MANAGED INTERNET
More informationChange Management Policy
Maine State Government Dept. of Administrative & Financial Services Office of Information Technology (OIT) Change Management Policy I. Statement Information Technology (I.T.) organizations require a process
More informationComputer Security Incident Response Team
Computer Security Incident Response Team Operational Standards The University of Scranton Information Security Office August 2014 Table of Contents 1.0 Operational Standards Document Overview... 3 2.0
More informationInfasme Support. Incident Management Process. [Version 1.0]
Infasme Support Incident Management Process [Version 1.0] Table of Contents About this document... 1 Who should use this document?... 1 Summary of changes... 1 Chapter 1. Incident Process... 3 1.1. Primary
More informationIT Change Management Process Training
IT Change Management Process Training Before you begin: This course was prepared for all IT professionals with the goal of promo9ng awareness of the process. Those taking this course will have varied knowledge
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 informationBloom Enhanced Performance Monitoring Service Level Agreement
Bloom Enhanced Performance Monitoring Service Level Agreement 1 SERVICE DESCRIPTION The Enhanced Performance Monitoring Service provides an enterprise-class level of assurance with regards to the performance
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 informationUser Guide for Submitters
User Guide for Submitters Information Technology Procedure Scope: BOR Revision Date: 5/8/2015 Table of Contents 1. Introduction... 2 2. Submitter Responsibilities... 2 3. Overview of the RFC Process...
More informationCCIT Change Management Policy
CCIT Change Management Policy Executive Summary The Clemson Computing & Information Technology (IT) infrastructure at Clemson University is expanding and continuously becoming more complex. There are more
More informationUNCG Emergency Notification Policy Date Effective: September 22, 2011 Revised: September 14, 2012 Revised: May 28, 2013 Approved By: Executive Staff
UNCG Emergency Notification Policy Date Effective: September 22, 2011 Revised: September 14, 2012 Revised: May 28, 2013 Approved By: Executive Staff Table of Contents Introduction & Purpose Page 1 Definitions
More informationHP 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
More informationCompliance Procedure
Compliance Procedure Title: Reference Number: Revised: 3/2010 Monitoring & Problem Escalation Procedure 9.3.2.2A Purpose The purpose of this compliance procedure is to define the procedure in place with
More informationApplication Development and Support
Service Description The Application Development & Support (AD&S) service provides high-end design and the latest Web technologies to North Carolina government at the lowest possible rates. The service
More informationSubmitted by: Christopher Mead, Director, Department of Information Technology
Office of the City Manager INFORMATION CALENDAR March 21, 2006 To: From: Honorable Mayor and Members of the City Council Phil Kamlarz, City Manager Submitted by: Christopher Mead, Director, Department
More informationWhat is the Purpose of OA s Enterprise IT Helpdesk Procedure?... 2 How will Problems, Questions or Changes be entered?... 2
PROCEDURES FOR REPORTING REMEDY APPLICATION PROBLEMS AND ISSUES PROCEDURES FOR REPORTING REMEDY APPLICATION PROBLEMS AND ISSUES... 2 What is the Purpose of OA s Enterprise IT Helpdesk Procedure?... 2 How
More informationNew Employee Orientation
New Employee Orientation Security Awareness August 7, 2007 Chuck Curry, Assistant Vice Chancellor for Information Security John Gale, Security Consultant Scott Robards, Security Consultant Our goal is
More informationInformation & Technology Management Branch Ministry of Education. Change Management Policy
Author: Change Advisory Board Creation Date: March 26, 2001 Last Updated: June 29, 2007 Document Number: 6840 00/Change Control Version: 2.3.5 Approval Renate Butterfield ITMB Director Signature Date CIO
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 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 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 informationCITY UNIVERSITY OF HONG KONG Change Management Standard
CITY UNIVERSITY OF HONG KONG (Approved by the Information Strategy and Governance Committee in December 2013; revision 1.1 approved by Chief Information Officer in September 2015) PUBLIC Date of Issue:
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 informationESI Incident Response Procedures 1
ESI Incident Response Procedures 1 Core Document Approval Date, USNH Legal Counsel: 2/12/2010 Core Document Approval Date, UNH CIO: Pending Objectives 1. Understand which policies, procedures and laws
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 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 informationNational Commission for Academic Accreditation & Assessment. Handbook for Quality Assurance and Accreditation in Saudi Arabia PART 3
National Commission for Academic Accreditation & Assessment Handbook for Quality Assurance and Accreditation in Saudi Arabia PART 3 EXTERNAL REVIEWS FOR ACCREDITATION AND QUALITY ASSURANCE Ver. 2.0 July
More informationPolicies of the University of North Texas Health Science Center
Policies of the University of North Texas Health Science Center 14.650 UNT Health IT Change Policy Chapter 14 UNT Health Policy Statement. It is the standard operating policy of UNT Health, UNTHSC Academic
More informationHP Service Manager. Software Version: 9.40 For the supported Windows and Linux operating systems. Processes and Best Practices Guide (Codeless Mode)
HP Service Manager Software Version: 9.40 For the supported Windows and Linux operating systems Processes and Best Practices Guide (Codeless Mode) Document Release Date: December, 2014 Software Release
More informationRequirements 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,
More informationInformation Technology Services Procedure
Information Technology Services Procedure TITLE: Monitoring & Problem Escalation Procedure PROCEDURE #: 06.2.1 UNIT: Network Technology & Operations LAST UPDATED: March 2014 PURPOSE The purpose of this
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 informationHEAT Quick Reference Guide
HEAT Quick Reference Guide How to Log In 1. In a browser, enter the URL for the HEAT system (https://heat.nd.gov/heat). HEAT opens to the login page. 2. Enter your user name and password (this will be
More informationAnalytics Reporting Service
1. Rate per month $19.00 per user 2. General Overview: The provides the technologies for transforming large quantities of raw data into useable information serving the agency s functions. includes interactive
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 informationState of Washington. BHAS Help Desk Support Services. July 2015 V1.0
State of Washington BHAS Help Desk Support Services July 2015 V1.0 WA-Behavioral Health Assessment Solution (BHAS ) BHAS supports the Child and Adolescent Needs and Strengths Assessment (CANS) and Adult
More informationICS 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
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 informationCHAPTER 1 COMPUTER SECURITY INCIDENT RESPONSE TEAM (CSIRT)
CHAPTER 1 COMPUTER SECURITY INCIDENT RESPONSE TEAM (CSIRT) PURPOSE: The purpose of this procedure is to establish the roles, responsibilities, and communication procedures for the Computer Security Incident
More informationITIL Version 3.0 (V.3) Service Transition Guidelines By Braun Tacon
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
More informationASX CLEAR (FUTURES) OPERATING RULES Guidance Note 10
BUSINESS CONTINUITY AND DISASTER RECOVERY The purpose of this Guidance Note The main points it covers To assist participants to understand the disaster recovery and business continuity arrangements they
More informationICT Change Management Policy. 3 rd Party Support Guide
ICT Change Management Policy 3 rd Party Support Guide Christchurch International Airport Ltd All rights reserved No part of this document may be copied, photocopied or reproduced in any form or by any
More informationYale University Incident Management Process Guide
Yale University Management Process Guide Yale University Management Process 1 of 17 Introduction Purpose This document will serve as the official process of Management for Yale University. This document
More informationInternal Help Desk. Construction Document
Internal Help Desk Construction Document Internal Help Desk 2 Table of Contents Process Diagram... 4 Data Model... 5 System Entities... 6 WFUSER 6 Area 6 Case Type... 6 Request Type... 6 Category... 6
More informationThe Use of Information Technology Policies and Policies
Information Technology Management Procedure June 1, 2015 Information Technology Management, page 1 of 7 Contents Responsibility for Local Information Technology Policies 3 Responsibility to Maintain Functionality
More informationEXIN.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
More informationInfrastructure Technical Support Services. Request for Proposal
Infrastructure Technical Support Services Request for Proposal 15 May 2015 ISAAC reserves the right to reject any and all proposals, with or without cause, and accept proposals that it considers most favourable
More informationInformation & Technology. Change Management Policy
Makana Information Technology Division Corporate Services Information & Technology Change Management Policy 1 Information & Technology Change Management Policy Table of Contents Approval Table of Contents
More informationBMC Software Consulting Services Fermilab Computing Division Incident Management Policy
BMC Software Consulting Services Incident Management Policy Client: Fermilab Date : 01/28/2009 Version : 1.0 DOCDB 3067 Description Purpose Applicable to Supersedes GENERAL This is the policy that governs
More informationIntroduction... 4. Purpose... 4 Scope... 4 Manitoba ehealth Incident Management... 4 Icons... 4
Remedy Incident Management Version 3.0 Modified: 08/20/2015 TABLE OF CONTENTS Introduction... 4 Purpose... 4 Scope... 4 Manitoba ehealth Incident Management... 4 Icons... 4 Incident Stages Overview...
More information