Can anyone explain me difference between CAB,Pre CAB and E CAB in change management?

[Syam Prasad]

Can anyone explain to me the difference between CAB, Pre CAB and E CAB in change management?

Thanks in advance.

[AbhishekGardade]

Hello Shyam,

https://docs.servicenow.com/bundle/madrid-it-service-management/page/product/change-management/conce...

With anything in ServiceNow, what they provide is basic framework and some best practices, but most of it can be adjusted to what a business needs.

1) To view and work change requests, ITIL role is needed. But who actually works the ticket really should be determined by the business needs. In our case, for changes that are raised for business services, we are tracking a development group, implementation group, and QA group on each business service (custom fields). We then keep the ticket "assigned to" the dev group while in new or approval states. When it moves to scheduled, it goes to the implementation group. Then when it moves to review we assign it to the QA group. With non-business service changes, we autopopulate the field based on a group on the CI selected, but it's always open to the user to change as needed.

2) The way they handle approvals didn't work for our company because we don't want people to have the ability to have any group approve their changes. Instead, we are using the change_control group on the Business Service or CI for assigning approvals.

3) Again, this really depends on company needs and policy. You can update the workflow to send to an ecab instead if needed.

4) If you needed to notify people that a change is still in "implement" when the planned end hits, then you would want to add in the appropriate "wait" in the workflow that would wait until the planned end and if the change is still in implement (or tasks under are still open), then trigger an event that would trigger a notification. There is nothing OOB to handle work still being done outside the planned window that I've seen.

Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade

[KDuncan]

In the organization I work for CAB is where change requests moving to production are discussed and either approved or rejected.  PRE Cab in this sense sounds like what we used to have where the technical aspects of a change are discussed and either approved or rejected to be brought to CAB for approval to move to production.  ECAB is for emergency changes that are the result of a MIM or Security Breach and are reviewed by an Emergency Change Board for approval.  Emergency changes are created after the work has been done already so they are always backdated.