Change Management Policy
Revised: 06/30/2009
1. Purpose.
This policy describes a systematic process to document and manage changes to the TCCC-RYSS Information Technology Network in order to permit effective planning by the TCCC-RYSS Information Technology Services to serve the TCCC-RYSS user-base.
2. Scope.
This policy applies to all Authorized Users that install, maintain, or operate TCCC-RYSS information technology resources, including, but not limited to: computer Hardware, Software, and Networking devices.
3. Policy.
Any change to a TCCC-RYSS Information Technology Network information technology resource is subject to this policy, and must be performed in compliance with the TCCC-RYSS’s Change Management Procedure.
All changes affecting TCCC-RYSS Information Technology Network computer-based environmental facilities, including but not limited to air-conditioning, water, heat, plumbing, electricity, and alarms, must be reported to or coordinated with the Information Technology Services department.
A formal written change request must be submitted to the Information Technology Services department for all changes, both scheduled and unscheduled.
All scheduled change requests and supportive documentation must be submitted in compliance with the Change Management Procedure. The request will then be reviewed by the Change Management Committee, and a decision will be made whether to allow or delay the request.
The Change Management Committee may deny a scheduled or unscheduled change for reasons that include, but are not limited to, the following: inadequate planning, inadequate reversion plans, negative impact of change timing on a key business process, or inadequate resource availability.
Customer notification must be completed for each scheduled or unscheduled change, in compliance with the Change Management Procedure documentation.
A Change Review must be completed for each change to the TCCC-RYSS Information Technology Network, whether scheduled or unscheduled, successful or not.
A Change Management Log must be maintained for all changes. The Log must contain (but is not limited to):
• Date of submission
• Requestor of change
• Date of change
• Implementer of change
• Nature of the change
• Results of the change
4. Enforcement.
Any Authorized User found to be in violation of this policy will be considered an Unauthorized User, and as such are subject to disciplinary action pursuant with the Enforcement section of the Unauthorized Use Policy.
