Use a Request Change to document a proposed cost and/or schedule change. It includes the impact, any additional details about the change, and a link to an estimating spreadsheet.
All workflow categories in PM Compass share a common toolbar.
The fields that display on this tab differ from one type of change request to the next. This topic lists the default fields for the Request Change. To view the General tab field descriptions for other change request types, click on one of the following links:
This serves as the unique key field for each Request Change record. PM Compass automatically generates a value for this field, but you can also manually enter it. However, you must ensure that you enter a unique value.
Enter a title for the Request Change. You can no longer edit this field after you save the record unless the change request does not use a workflow.
Select the end date for the Request Change completion.
Select the level of urgency (priority code) for the Request Change.
Click to select a project code. The Project Search dialog box displays.
Click to select a control account. The Control Account Search dialog box displays.
When the Request Change is completed, the Update Source step action uses the information in this note field to update the note field on the control account. This process uses the same text in the Approve Change without copying and pasting the text.
A Deltek Cobra user can then see the contents of the Proposed Change note on the control account. After the Request Change is approved, the Cobra user can copy the text in this note field to the Statement of Work note and delete the contents of the memo field. If you have no requirement to print the proposed change in Cobra, you can change Proposed Change to a custom memo field and remove the Update Source step action.
If there are many change requests in progress for a single control account, the details for all in-progress changes are displayed in the Request Change. If your organization frequently has many proposed changes for a single control account at one time, you can change this from a source field to a custom field. The note will then only exist on the Request Change form.
This field is optional. If the project is using a coding scheme for Request Change, you can enter the code for reference.
Use this group box to select one or more reasons for submitting the request. This helps the PCA determine how to apply the change.
Change to the Forecast
Change to the Budget
Request MR
Contract Change
Mitigating Risk
Technical Change
Correcting a Cost Variance
Correcting a Schedule Variance
Resolving Resource Constraints
Unexpected Costs
Affects Critical Path
Other
Click the link in this field to access and complete the estimating spreadsheet to request the change. You can change the template.
If clicking the link displays an error, the template custom fields in User-Defined Data have not been configured. For steps to configure these fields, see Modify the Default Template URL.
Enter an explanation as to why the proposed change should be implemented. You can enter the text directly into the field or click .
Enter the risk(s) of not implementing (both internal and external to the project) the proposed change. You can enter the text directly into the field or click .
If the change is not approved, enter any available substitute change. You can enter the text directly into the field or click .
Automatically create the Approve Change