NO MORE UPDATES TO THIS PAGE PLEASE. SUBMIT ALL FUTURE COMMENTS TO

10 pg 195

Change management is also a "Cover Your Arse" procedure for the SA. If a change has been notified through the change management system, had technical review and business sign off then the SA can't be moaned at for downtime or changes.

[ Tom's reply: Done. Status: DONE ]

10.1 pg 196

Activities can be split into BAU (Business As Usual) activities, which don't require the full change management processes (but may still use logging tools such as rcs) and "out of profile" changes, which require the formal signoff. Sample BAU activities could be account creation/deletion and DNS changes especially when such tasks have been automated (eg the Rutgers account creation process described in 6.1.8 pg 115).

-- StephenHarris - 15 Aug 2006

[ Tom's reply. This is on pg 201-202. Status: DONE ]

10.1.5 pg 205

Might be worth mentioning that "quiet time" might also be referred to as a "change freeze", or similar. When I first glanced at "quiet time" my initial thought was "the systems are quiet so we can do upgrades", which is the opposite of what is meant. "Change freeze" doesn't have that ambiguity.

[ Tom's reply. Status: DONE ]

-- StephenHarris - 16 Aug 2006