Mission

To manage all changes that could impact the ability of the IT division to deliver services through a single formal, centralized process of approval, prioritization, scheduling and control to ensure that the IT infrastructure remains aligned to campus requirements.

Scope

Managing changes to hardware, system software, network equipment and software, communications equipment and software, ‘live’ application software and environmental equipment (i.e., power, air conditioning). It encompasses all documentation, plans and procedures relevant to running, supporting and maintaining the ‘live’ systems.

Objectives

• To manage the process of requests, assessment, authorization and implementation of changes.
• To ensure no unauthorized changes are implemented.
• To minimize the risks involved in introducing new or changed elements into the IT infrastructure.
• To minimize disruption caused by changes.
• To coordinate the efforts involved in development, testing and implementing changes.
• To ensure that changes are researched and communicated to all impacted areas.
• Focus on day-to-day management of operational IT changes.
• Minimize bureaucracy associated with change management.

Change Models

A category of change that follows a pre-defined path that has been defined by Change Management process and agreed with the IT organization. A model may be specific to type, severity or impact, or any other variable that is relevant to the university. Examples may include changes to desktop, LAN or WAN.

Standard Change

A simpler or small-scale change that is well-known, follows a predefined path and is accepted response to a specified set of circumstances. They are proven tasks that are pre-authorized and initiated by the IT Service Desk. They have a predefined budget limit.

RFC Form

See Appendix X