Approval Flow for Change Management

[Aashish_D]

Hello All,

Can anyone explain how the OOTB approval flow is for the normal Change Requests?

As per my understanding:

1. If the risk is low then Approval goes to Assignment group manager and then assignment group members.
2. If the risk is moderate/ high then the Approval goes to CAB and Assignment group manager.

Is this flow suitable for most IT/ Infra related Change Requests? Or is their any other widely used approval flow which suits most IT/ Infra related changes. 

Thanks,

ADD

[J Siva]

HI @Aashish_D 

We don't have a defined approval flow. It varies based on client.
In general to implement he change, the requetser or the implementer must get as approval from the system owners/custodians, then peer approval (Tech leads) and at the end if required CAB approval. This flow covers all the necessary approval.

Ops approval (system owner) -> Tech approval (Tech leam leads) -> CAB (If required)

Hope this helps.
Reagrds,
Siva

[Dr Atul G- LNG]

Hi @Aashish_D 

As per my understanding:

1. If the risk is low then Approval goes to Assignment group manager and then assignment group members. ---> You need to check in the flow as well as the approval policy to see the conditions under which the approval is defined.
2. If the risk is moderate/ high then the Approval goes to CAB and Assignment group manager. -->

   If the risk is high and the change type is normal, then yes, it goes to CAB, not the assignment group, and that is the authorized state.

   In the out-of-the-box way:

   A normal change has two levels:

   • Assess – Goes to the assignment group

   • Authorize – Only CAB (Now, it can also be based on Risk)

You can test the same in PDI.

https://youtu.be/YNT-kaQOxDs

https://youtu.be/Ke6JaBiNd6Q

https://youtu.be/ahJoO5sKE9g