GovCon: Baseline Change Control (BCC) Register
The Baseline Change Control (BCC) Register has advanced workflow for requesting, modelling, authorizing, and incorporating change to a control account work authorization. It explains the changes in the scope of work, schedule, and/or budget to an approved baseline.
Toggles
Feature Toggle(s) | Permanent Toggle(s) |
100008_Financial_Baseline_Comparison_MVP 107588_C2_Task_Changes_to_Support_Baseline_Change_ 71407_Baseline_Financial_Comparisions_Design_New_M | Updated_Baselines BaselineChangeControl AlternativeHierarchies |
67343_RateMatrix |
?️ Configuration (Admin)
Administration > System > My Installation > Features
Ensure GovCon is checked and click Update
Setting up Register
Navigate to Administration > Configuration > Project Registers.
Click Add
Enter the Name of the register (e.g., Baseline Change Control).
Set the Type to Baseline Change Control.
Note: Only one register of the Baseline Change Control type is allowed.
Click Save & navigate to Fields.
Under Fields, both standard and additional Baseline Change Control system fields will be displayed. The system fields specific to the Baseline Change Control are listed below.
All fields are under a single group. The suggested grouping of the fields as indicated in the grid below. Admin will have to create groups and place fields in groups.
Field | Type | Notes | Suggested Group |
Description | Text | Summary of Change | |
Raised By | Single Select User | History and Ownership | |
Raised Date | Date | History and Ownership | |
Owned By | Date | History and Ownership | |
Target Date | Date | History and Ownership | |
Status | Status | Values in status are hardcoded & cannot be changed. | Summary of Change |
Last Date Updated | Date | History and Ownership | |
Baseline ID | Numeric | Visibility set to no, hide in grid checked | Summary of Change |
Baseline Control Account ID | Numeric | Visibility set to no, hide in grid checked | Summary of Change |
Baseline Work Package ID | Text | Visibility set to no, hide in grid checked | Summary of Change |
Baseline Cost | Numeric, Currency | Changes from Baseline | |
Baseline Hours | Numeric | Changes from Baseline | |
Baseline Duration | Numeric | Changes from Baseline | |
Baseline Start | Date | Changes from Baseline | |
Baseline Finish | Date | Changes from Baseline | |
New Cost | Numeric, Currency | Changes from Baseline | |
New Hours | Numeric | Changes from Baseline | |
New Duration | Numeric | Changes from Baseline | |
New Start | Date | Changes from Baseline | |
New Finish | Date | Changes from Baseline | |
Delta Cost | Numeric, Currency | Changes from Baseline | |
Delta Hours | Numeric | Changes from Baseline | |
Delta Duration | Numeric | Changes from Baseline | |
Model Project ID | Numeric | autogenerated | Summary of Change |
Additional fields can be added per the customers requirements.
Once complete, click Save.
Reminder: Be sure to add your new register to the project tool bar.
Setting up Workflow
Navigate to Admin > Configuration > Workflow and click Add.
Under Workflow Details:
Enter a Name for the workflow (e.g., Baseline Change Control).
Set the Type to Project Register.
In the Project Register field, select the register created in the previous step.
Under Workflow Management:
Assign users responsible for managing the workflow.
These users will have access to the Workflow Management screen, where they can:
Update approvers
View all workflows
Monitor workflow statuses
Click Save.
Under Workflow Versions, click Add to begin configuring the version detail
When creating a workflow for Baseline Change Control register types, the following elements are required by default:
Start
End
A Baseline workflow element should not be added to a Baseline Change Control register.
Since this register is used to edit an existing baseline, it does not create a new one
You can configure additional workflow elements based on your specific requirements.
Once the workflow is complete and all elements are properly connected, click Save, then Publish to activate the workflow.
? Items to be aware of (Gotchas!)
Item | Admin, End User, or Both |
|---|---|
Project Baseline is required before Baseline Change can be made | End User |
Changes to baseline Schedules only (Planned Resources & Cost coming in Q3) | Both |
In the workflow, a Baseline element should not be used. BCC is used to edit existing baselines, not to create new ones. | Admin |
The Status field is hardcoded—statuses cannot be modified, added, or deleted. | Admin |
Status color bubbles are hardcoded and cannot be modified. As a result, pie and donut charts are not supported when using status as a data dimension. Note: A scripted version of the Status field with color is available for use in reporting where customization is required. | Both |
When summarizing by Status in the BCC Widget, colors will not differentiate between values. Therefore, pie and donut charts should be avoided. | Both |
Ensure all costs are populated before capturing the baseline. An orange triangle in the INFO column indicates that rates have not been applied.  | End User |
Ensure that your Work Breakdown Structure (WBS) Register is fully populated and that a clear hierarchical relationship exists among the WBS elements, specifically between the Summary, the Control Account, and the Work Package/Planning Package. | End User |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article