Change Management Blackout Schedules and Dealing with Exceptions

Damon3
Tera Contributor

Hello,

Investigating the usage of Blackout Schedules.

Once we have those in place, I would be interested in hearing what others are doing when there is an "exception".

Example: Our Blackout Schedule may exclude Production Changes from taking place during Core business hours.

If there is an Exception needed (Vulnerability/Patch/BreakFix) that may be required during that window, how are you dealing with that?

I would be very interested in the usage of having approvers (not Change Management) - be brought in to the Change and Required, if Production Change is requested. Also intested in the "trigger" you may use to do so.  I am not a developer, but would be interested in this process and process exception.

Thanks in advance.

 

1 REPLY 1

Community Alums
Not applicable

I think the nearest use-case I've seen to this was: 

 

Changes can only be made to a CI during it's scheduled maintenance window (listed on the CI). An exception was for Emergency changes. If an emergency change occurred outside of the Maintenance schedule for the application involved, there was a Service Manager listed on the CI and approval went to that person to approve the change record.