NRFC requests must be reviewed by the Change Advisory Board (CAB) to be closed. This describes the process for a CAB review and closure of a NRFC.

---

Change Advisory Board

---

Change Advisory Board Members:

VP of Technology

Senior IT Manager

Project Manager

IS Manager

---

An approved and closed NRFC.

---

Records (logs) of the approval or denial will appear in the NRFC chat history and statuses.

---

1. Prerequisites and CAB meeting opening requirements:

• Each NRFC to be reviewed by the CAB will need to be in the REVIEW status.

• Each NRFC to be reviewed must be complete and contain all required evidence and notes to indicate the status of NRFC completion.

• The Change Advisory Board meets each week as required to review and close each NRFC work ticket. Any NRFC work not reviewed will be reviewed at the next meeting. NRFC work is reviewed starting with the oldest unless exigent circumstances dictate otherwise or at the discretion of the CAB.

• Quorum for the CAB meeting is at least three members, at least two of whom must be technically able to assess the changes being reviewed.

• If quorum cannot be met, the meeting can be postponed to the following week, or if at least two members of the CAB are present, a third member of the centrexIT Senior Technical team (STT) or Executive Leadership Team (ELT) may fill in for a missing member of the CAB.

• If any NRFC has been completed by a member of the CAB, the NRFC must be reviewed by at least two other CAB members to confirm completeness prior to closure. As needed other members from ELT or STT may join to close NRFC where multiple members of the CAB may be involved.

2. Open the oldest NRFC ticket in Review or Review Complete status.

• Begin by reviewing the Testing Plan, Backout Plan, and Escalation Plans

• Review the Execution plan, each step should have evidence to support the change, the testing requirements for the step in place.

• The CAB should Verify and Review the following:

• Was the change completed as indicated, if it was deviated or reverted or other non-standard outcome, is there sufficient documentation and work to be sure there is no outstanding or negative implications of leaving the change in the incomplete state?

• Is there sufficient confirmation of billing, financial change adjustments, and client or system owner responsibility for those cost changes?

• Does the evidence attached show the complete picture of the change as best it can be documented?

• Does the evidence support any necessary changes to monitoring or alerting, or network diagrams, documentation, backup systems, Halo configurations or CIs, and passwords documented in 1Password, or any other system or documentation deemed important to the change and the support of the changed system after the change.

• If each of these above can be confirmed, the change may be marked Review Complete.

• If the above cannot be sufficiently confirmed to the acceptance of all CAB members present, then the NRFC should be marked Review Rejected, notes should be updated on the NRFC to indicate the reason for rejection, the next steps needed to be taken to remedy the discrepancy, and the owner of the NRFC work should be contact to ensure they are aware of the need to review and complete any additional work.

3. A member of the CAB must leave a note on the NRFC that the committee has approved the change for closure and save it.
4. A CAB member should change the status of the NRFC to Complete.
5. Repeat these steps for each NRFC work in Review or Review Complete Status.

---

1. Change Enablement Process (KB00011621)