NRFC requests must be reviewed and approved by the client SME (vITM)

---

vITMs, vCIOs, and other technical approvers for NRFCs.

---

---

The end goal is to have an approved or denied NRFC.

---

Records (logs) of the approval or denial will appear in the audit logs of the NRFC and the corresponding approval request.

---

1. Initial review of the NRFC Approvals will appear in the Halo approval area, this is accessed by clicking the thumbs up icon on the lower left side of the Halo windows. If an approval is waiting you should see a red number on top of the thumb icon. Once you locate the request, open the parent NRFC and review it. If a change approval is in progress and waiting on your approval you should see a blue ribbon at the top with thumbs up and thumps down icons. Do not click those until you are ready to approve or deny the change. The vITM is the client SME and the first approver in the approval chain. It is critical to check the following areas prior to approving the change: The overall change and the execution steps:

• What is the change, does it make sense, is the change complete once all steps are completed, will it do what is intended?

• Have the appropriate system owners approved the change?

Testing and Issues

Backout Plan:

• Is there a backout plan? Does that backout plan make sense and will it achieve the end result of returning the system to its original working state?

Testing Plan:

• Does the testing plan adequately test the change and the functionality of the system post change?

Escalation Plan:

• Is there an appropriate escalation path should any issues be encountered?

Risk:

• Is there risk to this change and is that risk adequately identified?

• Is that risk properly mitigated?

• If there is uncertainty in the risk or if the risk cannot be probably mitigated please ensure it is fully reviewed with centrexIT senior technical team members and the client primary POC before approving.

2. The Final vITM check

After evaluating all the above, are you still comfortable with this change? It not, proceed to denial, if yes, then review the following questions before approving. If any of these questions below are a “yes” answer, the change should not be approved.

• Is there any business conflicts to this change?

• Will this impact any unintended systems?

• Does the system have any interdependencies that may by impacted by the change?

• Is the proposed time and implementation going to interfere with any business activity?

If all of those questions are NO answers and the change meets all the criteria and you as the client SME are comfortable with the change it can be approved.

3. Approval or Denial To approve the change, click the Green Thumbs UP icon at the top of the NRFC in the blue ribbon. If you need to reject the approval, use the Red thumbs down icon. Then speak with the owner of the NRFC to determine the next steps needed or discuss any missing elements or problems with the change.

---

1. Create a relationship back to related process. Note: Please add KB relationships to core process, process, SOPs or other WIs on the right.
2. Change Enablement Process (KB00011621)