DCMA-14 · Check 14 of 14
BEI (Baseline Execution Index)
How much of the work planned to be done by now is actually done.
What it measures
Whether the project is keeping pace with its baseline.
How Claims Digger calculates it
Activities actually complete divided by activities that should be complete. 'Should be complete' is every baseline activity that still exists in the current schedule and whose baseline finish is on or before the current data date; 'actually complete' is how many of those have a real actual finish date. It needs a designated baseline: without one the result is N/A. 1.0 means the schedule is keeping pace; 0.95 or higher is reported as healthy, and it is shown as an indicator rather than a hard pass or fail.
Why it matters
It measures execution against the plan by counting finished work, independent of dates or float.
How to fix a failure
- A low BEI is a status finding: work planned by now hasn't finished.
- Use the missed-tasks list to see which activities are behind.
Claims Digger runs all 14 checks on any schedule you upload, and lists the exact activities behind every failure. See how the health check works.