In order to submit a Change Request (CR), you will need to download the Change Request Form in PDF file format, complete the form and print it. You need to have Acrobat Reader installed (Click here to download Acrobat Reader) to view and complete the form.

Click here to download the Change Request Form.

Once you have downloaded the form, please fill out “Requestor Information” and the “Change Request Information” and then work through the Change Request Process to obtain the appropriate approvals

Click here to download the Change Request Process.

*NOTE: The requestor is responsible for completing ONLY the Requestor and CR Information sections. All fields MUST be filled out completely. Should the CR be approved, the FBMS PMO will be responsible for completing the Proposed Cost Estimates section of the form, and the Bureau Functional Owner associated with the CR will complete the Funding Information portion.

Please refer to the following instructions to complete the CR Form:

REQUESTOR INFORMATION

• Name: Enter the requestor’s name
• Agency: Enter the requestor’s Agency or Office
• Email: Enter the requestor’s email address
• Phone: Enter the requestor’s work phone number

CHANGE REQUEST INFORMATION

• Application: The DOI Change Request (CR) Form uses the official names of DOI systems to catalogue and evaluate potential changes.
• Priority:  Indicate the priority level by selecting low, medium or high.
• Category:  This list contains the type or Category of the change requested.
• Justification:  Enter a brief summary explaining the reason for your CR.
• Description of Change:  Describe in detail the change you are requesting.
• Planned Start/End Date:  Enter a start and end date for implementing the CR.

Reviewer Roles and Functions:

Bureau Functional Owner Reviews and Approves/Disapproves CR:  At this decision point, the Bureau Functional Owner will have to approve any new CR's before they get sent to the Bureau System Owner.  At the start of the CR process, the Bureau Functional Owner will receive each and every CR that has been completed and associated with the system(s). They are expected to review the CR to determine if it is an acceptable request for that system.

Bureau System Owner Reviews and Approves/Disapproves CR:  At this decision point, the Bureau System Owner receives the CR that has been approved by the Bureau Functional Owner.  The Bureau System Owner is responsible for reviewing and approving/disapproving the change as an acceptable modification for the system.  Specifically, the Bureau System Owner should assess whether the change request has a negative and unacceptable impact on the costs, performance, and mission intent of the system in focus.  If the Bureau System Owner finds the CR acceptable, then the acceptance form is signed and the CR is routed to the Bureau CIO.

Bureau CIO Reviews and Approves/Disapproves CR: At this decision point, the Bureau CIO receives the CR that has been approved by the Bureau System Owner.  The Bureau System Owner is responsible for ensuring that only quality and necessary change requests are routed for the Bureau CIO’s review.  Bureau CIO is expected to review the content of the change request in order to determine if it is satisfactory for the system and more importantly if it is satisfactory given the overall technology and applications environment of the Bureau.  If the CIO finds the CR acceptable, then the acceptance form is signed and the CR is routed to CTOC Co-Chairs. 

CTOC Reviews and Approves/Disapproves Technical Changes in Change Request:  At this decision point, the CTOC chair is expected to review the content of the request primarily to determine if it aligns with the approved DOI technology architecture that is embodied in the current version of the DOI Technical Reference Model (TRM).   The TRM may be viewed at www.doi.gov/ocio/architecture.   In addition, if the change request may impact other departmental/bureau systems from an infrastructure perspective, these should be assessed also.   If additional information is required from the initiator in conducting the review, the CTOC representatives may contact the CR initiator for further information.

If the CTOC finds the CR acceptable, then the acceptance form is signed and the CR is routed to the FBMS PMO.

FBMS PMO Determines if Change is Acceptable:  At this decision point the FMBS PMO analyzes the functional and technical changes proposed in the request and determines if those requests are acceptable to the FBMS project.  Specifically, the FBMS PMO would be analyzing their own project plan and target architecture and determining whether the changes are acceptable.  If the FBMS PMO finds the change request acceptable, then the acceptance is signed in the CR Form.  If the CR will pose a schedule and cost impact to the FBMS project, then the FBMS PMO will enter their specific cost and time impacts.  In order to minimize uncontrolled costs to the FBMS project, costs associated with the CR that impact the FBMS solution will be born by the requesting bureau/office.

FBMS PMO Determines Cost and Time Impacts:  At this decision point, the FBMS PMO details any cost and time impacts that the CR will have on the FBMS solution.  Specifically, the FBMS PMO will determine the extra costs and delays that will result from the CR, and the FBMS PMO will document those costs and delays in the CR Form and the CR is routed back to the Bureau System Owner for approval.  The Bureau System Owner associated with the CR can either provide the required funds or cancel the CR.  If the FBMS PMO does not determine cost and time impacts, then the results are logged in the CR Form and the CR is officially accepted.  Upon acceptance of the CR, notifications of the acceptance should be sent to the CR Initiator, the Bureau Functional Owner, the Bureau System Owner, the CTOC, and the Bureau CIO.

Bureau System Owner Determines Funding Codes for CR:  At this decision point, the Bureau System Owner associated with the CR receives the cost and timing impacts from the FBMS PMO and evaluates whether there are available funds to perform the CR, and fund the associated changes in the FBMS solution.  This step is necessary to effectively manage schedule and cost impacts to target enterprise solutions.  Specifically, the Bureau System Owner will be evaluating the new cost versus the benefits of implementing the CR.  Funding codes are required in order to ensure that total funds are available (for the total cost impact) prior to the CR being approved and implemented.  If the Bureau System Owner wishes to proceed and has available funds, the funding codes are entered into the CR Form.  Upon acceptance of the CR, notifications of the acceptance should be sent to the CR Initiator, the Bureau Functional Owner, the FBMS PMO, the CTOC, and the Bureau CIO.

.