CAB Change Request for Oracle

[libdgg]

Confirm who PMO for the OIT Oracle project) will be adding a change request to determine if/how we put in a change request for EUL CAB.

[CHG154478](https://emory.service-now.com/nav_to.do?uri=%2Fchange_request.do%3Fsys_id%3Db3854eff47f8a590befdb2de536d4378%26sysparm_record_target%3Dtask%26sysparm_record_row%3D2%26sysparm_record_rows%3D165%26sysparm_record_list%3Dopened_by%253Djavascript:gs.getUserID()%255Esys_class_name%2521%253Dsc_request%255Esys_class_name%2521%253Dsc_req_item%255EORDERBYDESCopened_at) (draft)

Work concluded for this ticket the week of February 27th. Clarity on compliance with CAB and Change Management process to ensure communications, awareness, team availability, backout plans, and mitigation of risks.

Mitigation 1 – database team noted that they would put in a change record on their end.

Mitigation 2 – Presented the EUL CAB draft change at OIT CAB to make the change known at that level and to understand more about when EUL CAB changes should intersect with OIT CAB. Will utilize feedback for EUL CAB process improvement.

Mitigation 3 – EUL Project Manager and EUL Change Manager are monitoring this migration, status and risks for any issues to arise for escalation.

[libdgg]

ACTION: confirm with both teams about their change requests and confirm that we can add our apps to their changes.

[libdgg]

Closing this ticket per actions taken the week of Feb 27th and mitigation items. See ticket description above for resolution notes.