Changing date after CAB approved

[busybeez]

We had a change that was CAB approved. The vendor then needed to change the date. Currently we only work with normal or emergency changes. It was suggested this be brought through as an emergency b/c the revised date did not have a peer review done in time.
We are looking to improve our process on this kind of stuff.
What does everyone else do?

[ChangeAgent]

Given your choices between normal or emergency, then emergency change is the way to go.

We have Standard, Normal, Emergency and Expedite change types / models.

Standard Changes are pre-approved, repetitive low risk, no outage changes

Normal Change meets the defined lead time and requires Assignment Group Manager, CAB and CM approval

Expedite is a Normal Change that does not meet the defined lead times and requires an additional approval level, typically from Sr. mgmt.

Emergency changes are used in production to restore service during an active high severity incident and does not require CM or CAB approval.

In your scenario, if the change does not have enough time to go through the full review and approval process, we would follow the expedite process.

[UKVIKING]

Well

Actually I think that since the CAB has approved and the Change Manager has authorised the change, the only thing is to inform the CAB Members and the CM to change the implementation date

This is also dependent on whether the new date is in the maintenance window or not. And if not, what is the service impact

That said, if the implementation group - ie the vendor - can ONLY do the work at certain times, then … shrug.. they have to do the work at certain times.

And of course, there will be post implementation reviews etc to include vendor management activities

[busybeez]

How often do you host a CAB meeting?

[UKVIKING]

We host a Application and Infrastructure CAB weekly

This is because the IT Estate is EMEA wide