Policy/ChangePrcoess

Change Control

  1. Change Control
    1. Description
    2. Date of the proposed change
    3. Estimated duration of the change
    4. Systems and services affected
    5. ARCS staff responsible for the change
    6. Testing procedures
    7. Backout procedures
    8. Notification
    9. Approval

Here you will find the details of planned changes to ARCS Grid infrastructure such as installation, commissioning, upgrades and decommissioning of systems and services. Each planned change should include information on the following:

  • Description of the proposed change
  • Date of the proposed change
  • Estimated duration of the change
  • Systems and services affected
  • ARCS staff responsible for the change
  • Testing procedures
  • Backout procedures
  • Notification
  • Approval

Description

Describe the reason for the planned change. Examples include:

  • Installation of a new system - description of the system and the services it will provide
  • Upgrade to an existing system - describe the changes, eg. does it resolve existing issues?
  • Decommissioning of a system - detail why the system is being decommissioned

Date of the proposed change

Indicate when the change is to occur. Make sure that there is enough advance notification unless it is a critical change that needs to be implemented immediately. For non-critical changes, there should be at least 1 weeks notice.

Estimated duration of the change

Indicate how long the affected systems are services are expected to be unavailable. This duration should include ample time for implementation and testing of the proposed change.

Systems and services affected

Detail all systems and services that will be unavailable during the change period and indicate alternate resources that may be used during this period.

ARCS staff responsible for the change

List the people who are performing the change and their contact details.

Testing procedures

Detail the test plan that will be performed to ensure that the proposed change has been successful.

Backout procedures

Detail the backout plan that will be performed if there are problems with implementation of the proposed change. This will ensure that systems and services can be restored to the state they were in prior to commencement of the change.

Notification

Ensure that a notification is sent to affected users (via relevant email lists) prior to the change, with 1 weeks advance notice. Another notification should be sent after the change process indicating its success or failure.

Approval

Indicate who has authorised this change.

Requests