End User - Baseline Change Control (BCC) Register

Modified on Mon, 28 Sep at 3:18 PM

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.


content.emoticon.computer How to Use This Function or Component (End User)

You must 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. This established structure is a mandatory requirement that must be satisfied before any Baseline Changes can be processed.

  • Navigate to the Baseline Change Control Register on the Project Toolbar.

    image-20250714-171106.png

     

  • Click Add at the top-left of the register to open the details panel.

    image-20250714-171545.png

     

  • A pop-up window will appear, allowing you to select the Current baseline, Control Account, and Work Package you wish to modify and then click Save.

    • Note:

      • A project baseline is required. If one is not set, the dropdowns will appear blank, as there is no baseline to edit.

      • The Control Account and Work Package dropdowns will dynamically update based on the baseline selected in the first dropdown.

        image-20250714-171943.png
  • When the record opens, all fields—except for Description—will be initially blank or read-only.

  • Enter a Description for the baseline change, then click Save

  • After clicking Save, the Model button will appear next to the Save button.

    • Click the Model button. (record Status will update to Modeling)

      image-20250714-172742.png
    • A pop-up window will open, displaying the schedule based on the selected baseline.

    • Make any necessary edits (e.g., adjust tasks in the Gantt chart).

      • Changes are automatically saved as you click out of each cell.

    • When finished, click the “X” in the upper-right corner to close the pop-up window.

      image-20250714-172808.png
  • In the register record, the Get Changes button will now appear, when clicked data will now appear in:

    • Registers Fields

      image-20250714-173307.png
    • Impacted Work Packages

      image-20250714-173325.png
      • This indicates the work package(s) directly affected by the changes made in the model, as well as any work packages with dependencies on the modified work package.

  • Edits can be made in the Model, and the Get Changes button can be used to refresh the data as needed before submission.

  • When ready, click Submit. The Status will update to Submitted.

  • Once the change is approved, click Apply Change to implement it.

After selecting Apply Change, the Baseline Change Control is complete, and the Status will update to Closed.

image-20250714-174639.png

Dashboard

  • Baseline Change Control (BCC) is available as a dashboard widget to track details such as status, owners, raised by, and more.

  • When summarizing by Status, it is recommended to use a bar, line, or treemap chart for clearer visualization.

    image-20250714-175742.png

 

? 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

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.

image-20251014-154953.png

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

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article