Change Advisory Board (CAB) Meetings

438 Words1 Page

On a weekly basis, Change Advisory Board (CAB) meetings are held to review in progress and upcoming significant change requests. Members of the board are comprised of IS Team lead and managers. However, other department technical expertise will be included as needed.
The standard list of changes for this meeting includes, but is not limited to:
1. Release Migrations
2. Parameter Changes
3. Configuration Changes
4. Hardware Changes
5. Emergency Fixes, Patches, or Alerts
A change schedule, which is to be used at the CAB meeting, should be produced in sufficient time prior to the meeting to allow the members an opportunity to review information with their respective staff for comments and recommendations. It is during this process that much of …show more content…

The change schedule will then be updated to reflect the new status. That information is then communicated to the requester and to the interested parties. If the change is approved, the requester may proceed with the change implementation on the schedule documented in the approved Change Request. IF the change is disapproved or suspended, the request should be returned to the requester for further action as required. This could be a recommendation for a new date; a request for additional information in further support of the change; or a request for improvement to the implementation and/or back out procedures.
It is the responsibility of the requester to recycle his change through the request and approval process again. Any changes to the change request will be reflected in the notes of the CAB meeting.
At each meeting a formal agenda and minutes are required to be taken. A sample of an agenda is provided below (from this agenda, a CAB meeting reference should be documented). A CAB meeting reference should be produced in sufficient time prior to the ___ meeting to allow the RFC an opportunity to review information with their respective staff for

Open Document