Date
of Last Review 6/6/08
SME: Director of Management Information Systems
Change Control
Policy
Change management establishes the process for controlling modifications to hardware; software, firmware, and documentation to ensure the Information resources are protected against undocumented modification before, during, and after system implementation. Change Management exists to coordinate and inform customers and staff of all changes that impact any shared computing system or service (e.g. servers, network devices, applications, etc.). The purpose of Change Management is to insure that all elements are in place, all parties notified and trained, and the schedule for implementation is coordinated with all other activities in the organization. The overriding goal is to provide a high level of availability and service to our customers.
UT-Network Services has created an online change notification procedure to help manage and discount interruptions to University networked resources due to the maintenance of systems and hardware that affect such resources. This notification procedure alerts all necessary areas via email with a description of the work being done along with estimated system downtimes and back out plans. The Change Notification Procedure allows system and network administrators the ability to communicate changes and coordinate optimal times for maintenance and downtime of systems.
All change request follow the Data Processing Service Request (DPSR) policy and procedure method. Final approval is signed off by each Department head for acceptance.
Procedure
All changes or downtime notifications that affect enterprise or HCPC systems are required to have an entry in our Change Management system (https://secureweb.hsc.uth.tmc.edu/lan/changes/changeAuth.asp) 5 days prior to implementation.
You will need to login to the Change Management Notification site with your UTID and password (LDAP Password).
One thing to note is, if HCPC IT Services category is selected and Email Category is set to “Yes” then the notification will only go to HCPC MIS Department. If it is set to “No” then the notification will go out to HCPC ALLEMPLOYEES.
Our system requires the following:
• Change Description: brief technical description of what change is being made
• Change Purpose: why are we doing this change?
• Change Testing: what testing has been done?
• Back out Procedures: what is the back out strategy should the proposed change fail. How will failure be determined and when will the determination to back out a change be made? By whom?
• Timing: Time when the change will be made. How long it will take and how long will the end users be affected?
• Responsibilities: Names and contact information for person responsible for the change and the on-call/on-site support.
• Impact Analysis: What applications, end users, network segments, systems or business functions could be affected or disrupted by this change?
Director of MIS
UT-HCPC
Related standards
Texas Administrative Code Chapter 202.75(5)
The Joint Commission : Management of Information
HIPAA
