• How to Submit an RFC
• Implementing and resolving the RFC

Submit RFC

Choose “Submit Change Request” from the services catalog, or
from the “OIT Change Advisory Board” desktop

Choose a Change Type

• Normal changes are non-emergency changes that do not have a defined, pre-approved process. They are moderate to high-risk changes that will or can have a significant impact to services and require review, communication, and coordination. These changes require CAB approval.
• Minor - Lower risk changes that have no or low impact to services that are not critical and thus only need minimal governance. Require management approval.
• Emergency changes are unexpected disruptions such as security breaches or application or server outages that need to be resolved immediately. Emergency changes sometimes handle the change request retrospectively, post-implementation, and require immediate approval to minimize the impact. It is crucial to review the implementation and document it to prepare for potential future risks. 

Set the "Change Title"

Use the following naming conventions for “Change Title” <Service Name> - <Department or Area> - <Short Description>

Complete all required fields

Submit RFC Form 
** Please note that a maintenance activity (task) will need to be created before this change request is submitted to the CAB for approval**

Create Maintenance Activity

• Use the following naming conventions for “Change Title” <Service Name> - <Short Description>
• Set Start Date/Time and End Date/Time
• Responsible (person who will be performing the change)
• Short description (technical details of activity)

To Submit RFC for CAB Approval, mark the task “Create Maintenance Activity for the Change Request” complete

Implement and Resolve RFC

Complete Maintenance Activity

Implementer Completes Maintenance Activity as soon as deployed. This signifies the technical task is completed.

Resolve RFC

RFC Requester Reviews Change and Verifies it is complete. This Resolves the Change Ticket.