Procedure
Effective Date
October 9, 2014
Date of Last Revision
October 8, 2014
Chapter Name
Information Management
Chapter Number
Title
Emergency Change Management
4.4.P.3
1.0 Purpose
Ensure all emergency changes are managed in a similar manner regardless of the team responsible for such changes.
2.0 Governing Policy
Number/Document Name
Effective Date
4.4 Change Management for IT Managed Systems
3.0 Procedure
1.
2.
3.
4.
5.
6.
7.
8.
Proposed change is documented in a Help Desk ticket assigned to the appropriate team/staff member for
resolution.
Changes are reviewed by the appropriate team and/or Director.
Changes are implemented in non-production system, where possible.
Changes are tested and validated to the extent possible.
Changes are approved by the appropriate Director and CIO.
Changes are communicated to relevant user community, where practical.
Changes are implemented in production system during approved emergency outage window.
Changes are logged in the appropriate change log.
4.0 Responsibility for Implementation
Implementation of this procedure is the responsibility of the appropriate IT Director.
5.0 Definitions
Term
Change
Infrastructure and
Operations Changes
Non-Production
System
Production system
Change log
Emergency Change
Definition
The addition, removal, or modification of any component of a production system. Changes may
include software, operating systems, hardware, or other components of a production system.
Changes made to servers, operating systems and other components, generally managed by the
Director of Enterprise Operations and/or Director of Network and Systems Services.
Systems managed by the Division of Information Technology that are used to test or validate
system changes.
Systems managed by the Division of Information Technology that are in active use by the
University Community supporting the routine business operations of the institution.
A spreadsheet or similar document or application used to log all changes.
Changes that Division of Information Technology management determine to be extremely urgent
such as those changes that management believes would increase risk to the institution if normal
change processes are followed.
7.0 Revision History
Description
Revised by L Rose
Approved by CIO
IT Procedure 4.4.P.3 – Emergency Change Management
Approval Date
October 9, 2014
October 9, 2014
Page 1 of 1