Examples
Example Request for Change Example change advisory committee agenda Example change advisory committee minutes Change communication example Change Management report example
Example Request for Change

 
 
[task completed by]
Asset tag 21383
Originator
Compaq file server [server name], B Block Computer Room
Originator
Installation of server operating-system service pack
Originator
Operating-system patch available to fix bugs
Originator
  • Check backups successful
  • Shutdown server
  • Restart server
  • Login as Admin user
  • Apply service pack from supplier
  • Execute upgrade
  • Shutdown server
  • Restart server
  • Login to server (test functionality and review error logs)
Originator
  • Server unavailable for one hour
  • Users unable to login to computers for duration
  • ICT services unavailable for duration
  • Affects all users and services
Originator
  • Failure would require server rebuild and data restore
  • Estimated time to rebuild, restore and recover: 6 hours
  • Impact on services and users as above
  • Risk is low – service pack was released 2 months ago and no issues have been reported on the supplier’s website
Originator
  • Restore operating system and data from tape
  • Restart server
  • Test server and data
NB Tapes required on site in advance of change
Originator
Friday 25 April 2003
Originator
1800–1900
Originator
Originator
Andrew Powell, Network Manager
Originator
 
Signatures
 
Initial approver
Debbie Wiggins, ICT Co-ordinator
D Wiggins
Initial approver
Peer reviewer
James Burke, Supplier Representative
J Burke
Peer reviewer
Final approver
Debbie Wiggins (for School Head)
D Wiggins
Final approver
 
 
Success
Failure
 
Implementer
Andrew Powell, Network Manager
P
 
Implementer

Go back to Examples
Unique identifier example
Unique identifier
Asset tag 21383

This can be assigned during Configuration Management. Asset tagging and tracking will be useful to identify problem equipment, find equipment that requires replacing and locating equipment in the school.

Name of item to be changed example
Name of item
Compaq file server [server name], B Block Computer Room

If you have a good asset management system, this field may not be necessary.


Brief description of change example
Brief description of change
Installation of Microsoft W2000 Server Service Pack 2

Mandatory item on the request for change. Ensure as much information as required is put here to avoid confusion.

Reason for change example
Reason for change
Operating system patch available to fix bugs

Approved changes should be shown as such. You should aim to reduce the number of unapproved changes by following the FITS processes.

Full details of change example
Full details of change
  • Check backups successful
  • Shutdown server
  • Restart server
  • Login as Admin user
  • Apply service pack from supplier
  • Execute upgrade
  • Shutdown server
  • Restart server
  • Login to server (test functionality and review error logs)

You may wish to use this as a checklist to follow when implementing the change.

Impact on services and users example
Impact on services and users
  • Server unavailable for one hour
  • Users unable to login to computers for duration
  • ICT services unavailable for duration
  • Affects all users and services

This is your risk assessment, be sure to consider all your users and the time of day the request for change is due to be implemented.

Impact and risk of change failing example
Impact and risk of change failure
  • Failure would require server rebuild and data restore
  • Estimated time to rebuild, restore and recover 6 hours
  • Impact on services and users as above
  • Risk is low – service pack was released 2 months ago and no issues have been reported on the supplier’s website

This is where your risk assessment focuses on equipment rather than people.

Fallback plan in case of failure example
Fallback plan
  • Restore operating system and data from tape
  • Restart server
  • Test server and data
NB Tapes required on site in advance of change

It pays to test your fallback plans from time to time and to be sure that all involved in the implementation are aware of it.

Date and time of change example
Date of change
Friday 25 April 2003
Time of change
1800 – 1900

Ensure that where you have decided to use a 12 hour clock, that am and pm are clearly displayed and everyone knows the difference between 12pm and 12am!

Example change advisory committee agenda

Example change advisory committee agenda


Date:
Tuesday 15 April 2003
Time:
1000-1030
Venue:
Room 2, Science Block
Distribution:
Mrs A Black, Headteacher
 
Mr B White, Physics Teacher
 
Miss C Green, Network Manager (Chair)
 
Mr D Brown, ICT Co-ordinator (Minutes)
 
 
 
 

Item No.

Item description
 
 
1
Open meeting
2
Apologies for absence
3
Requests for Change for approval (papers attached)
    • RFC123 – Data server disk upgrade
    • RFC124 – Installation of network-monitoring software
    • RFC125 – Withdrawn (additional ISDN line)
    • RFC126 – Returned for further details
    • RFC127 – Router move - review outcome
4
Changes scheduled this period – reminder
5
Date of next meeting
6
Any other business
7
Close meeting




Issued by:
Miss C Green
Network manager and change advisory committee chairperson
Friday 11 April

Go back to Examples
Example change advisory committee minutes


Example change advisory committee minutes

Date:
Tuesday 15 April 2003
Time:
1000-1030
Venue:
Room 2, Science Block
Distribution:
Mrs A Black, Headteacher (AB)
 
Mr B White, Physics Teacher  (BW)
 
Miss C Green, Network Manager (Chair) (CG)
 
Mr D Brown, ICT Co-ordinator (Minutes) (DB)
 
 
 
 
Request for
Change No.

Description

Status
 
 
RFC123
Data-server disk upgrade
Initial approval
RFC124
Installation of network-monitoring software
Final approval
RFC125
Withdrawn (additional ISDN line)
Closed
RFC126
Returned for further details
Pending
RFC127
Router move
Successful-closed
 
 
Action owner
Action points
Date required
 
 
 
CG
Confirm time for server downtime on Thursday 17 April (RFC124) and issue notice to all staff
17 April 2003
 
 
 



 





 
Issued by:
Miss C Green
Network manager and change advisory committee chairperson
Tuesday 15 April
Go back to Examples
Change communication example


Notification of ICT system outage

To:          All staff
From:          ICT Technical Support
Date:      23 April 2003


Data-file server

This is to notify all ICT system users of a planned system outage:

Equipment affected:          Data-file server
Date of outage:        Friday 25 April
Time of outage:        1800-1900
Log-out time:            1745

This outage will affect all ICT users, who will be unable to access their computer files during this period.

This work is to enable the technical support department to apply new software designed to improve the reliability of the system, which will reduce the risk of unexpected failure in the future and improve the overall ICT service provided.

Please note that you are requested to save your work and log out of your computer by 1745 on Friday to enable this work to be carried out on schedule. Please let me know if you anticipate this causing a problem.

Thank you very much in advance for your co-operation.

If you require further information, please contact me on extension 123.

Regards

Andy

Andrew Powell
Network Manager


Go back to Examples
Change Management report example
Enter monthly volumes in boxes:
 
 
 
 
 
 
 
 
 
 
 
 
 
Enter current months in Current boxes:
Current
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Number of approved Requests for Change
5
1
3
5
1
2
10
3
5
 
 
 
 
Number of rejected Requests for Change
0
0
1
2
0
0
1
0
0
 
 
 
 
Total number of Requests for Change
5
1
4
7
1
2
11
3
5
0
0
0
0
Number of successfully implemented changes
4
1
2
3
1
2
8
3
4
 
 
 
 
Number of failed changes
1
0
1
2
0
0
2
0
1
 
 
 
 
Save and Print
 
 
 
 
 
 
 
 
 
 
 
 
 
graphicgraphic


graphic
graphic


Go back to Examples