Various documents are created during the change process. Some information is recorded when the request for change (RFC) is initiated, and other information is collected or updated as the RFC progresses through its life cycle.
An RFC must completely describe the purpose and urgency of the change, its impact on the organization, and a backout plan in case of failure. The required level of detail depends on the size and impact of the change.
RFCs are submitted through the BMC OnDemand support portal using the Request a Change offering. This form contains all the information needed to effectively plan, manage, track, and fulfill an RFC.
The RFC should contain sufficient information to enable the Change Manager to assess the change at all review stages for approval or rejection. For example, the RFC tracks approvals before each of the following phases:
Supporting documentation, such as test plans, implementation plans, and remediation plans, might be required. The Change Submitter should also specify whether each plan is included in the RFC. These plans must describe the change before it is implemented. Smaller-scale changes typically require less detailed plans. Any required documents should be attached to the RFC form.
Additional documentation might be required. For example:
This information is also used by the Change Manager to assess the change for approval or rejection at all review stages.
For information about submitting the RFC, see Change request process.
Your scheduled changes may be viewed from the Change Calendar link in the BMC OnDemand support portal.