The following steps describe the standard change request process flow.
Separate requests for change (RFCs) must be created for each customer environment, such as the development, quality assurance (QA), and production environments. You may use the 'Request Again' button from the original request to fast track submission of similar requests.
The RFC form is available from the BMC OnDemand support portal under the Request a Change offering. It lists all of the information that the change submitter (BMC SaaS Operations, or customer or project teams, on behalf of a customer) must provide to fulfill the change request.
The change submitter ensures that the following documentation is complete:
While logged into the BMC OnDemand support portal, the RFC form is accessible under the Support tab, Request a Service section. Select the "Request a Change" option. After form completion, select Submit at the bottom of the page. This will create the internal CRQ# and auto-route the request to the BMC Change Advisory Board (CAB). You may track the progress of your request under the Updates tab.
The BMC CAB reviews all submitted RFCs to ensure that:
For each change, formal authorization is obtained from a change authority (your designated change approver and a BMC CAB member).
Customer-authorized change approvers will be contacted via email by BMC SaaS Operations to request authorization.
All changes must be approved before implementation. All RFCs are reviewed by BMC CAB technical resources. If this team has any questions then they can withhold the approvals until clarification is received. The CAB meets daily (Monday to Friday) starting at 2:00 PM UTC.
Any approved change that is modified before implementation must be reapproved. Reuse of an approved change to implement additional changes is not permitted.
All authorized RFCs are scheduled by the BMC CAB using your preferred change window. In the absence of any free slot, BMC SaaS Operations will contact your emergency contact through their preferred method of contact (email or phone) to negotiate an alternate change window.
All scheduled RFCs are executed according to their schedule. BMC SaaS Operations will send a timely notification (Start, End, Delayed, Extended) to keep you updated on the status of execution.
A production change request will lead to rejection if it is not already implemented in the QA environment and successfully validated. BMC SaaS Operations will need to execute the change in the QA environment before considering this same change for the production environment.
Every now and then a BMC-instigated change will require an extension to the change window in order to complete the request. When this situation arises, BMC SaaS Operations will provide a minimum of 15 minutes notification (prior to the end of the original scheduled window) to the customer. If an extension is necessary, the change window will be extended by one hour unless the extension notification states otherwise.
BMC SaaS Operations performs technical validation of environments to ensure that their health is maintained after changes.
Any business or functional validation is considered out of scope for BMC SaaS Operations, and such validation is completely owned and performed by the submitter of the RFC or the customer. BMC SaaS Operations will address validations with the following criteria:
The requester is responsible for closing out a change request within seven days after implementation. Before closing, the status of the change request must be "Completed". You should also close any related incidents, problems, or known errors.
The status code shows the final disposition of an RFC. For more information, see RFC status codes.
After it is closed, an RFC cannot be reopened.