The DCMA 14-point assessment is a set of schedule-quality metrics from Defense Contract Management Agency guidance (DCMA-EA PAM 200.1). They check whether a CPM schedule is built well enough for its dates and float to be trusted.
| # | Check | Common threshold |
|---|---|---|
| 1 | Logic: missing predecessors or successors | 5% |
| 2 | Leads (negative lag) | 0% |
| 3 | Lags | 5% |
| 4 | Finish-to-start relationships | at least 90% |
| 5 | Hard constraints | 5% |
| 6 | High float (above 44 working days) | 5% |
| 7 | Negative float | 0% |
| 8 | High duration (above 44 working days) | 5% |
| 9 | Invalid dates around the data date | 0% |
| 10 | Resources assigned | no published threshold |
| 11 | Missed tasks against the baseline | 5% |
| 12 | Critical path test | delay propagates to the finish |
| 13 | Critical Path Length Index (CPLI) | 0.95 |
| 14 | Baseline Execution Index (BEI) | 0.95 |
Why it matters
The checks find weak logic quickly, before anyone relies on the float or the finish date. They are screening indicators, not compliance criteria. GAO’s schedule assessment guide says the thresholds “are not compliance triggers”; a red metric is a reason to look, not a finding. Several thresholds also have no published source, and the denominators shrink as a job progresses, so an unchanged schedule can fail a check late in the job.
Common mistakes
- Publishing a letter grade without saying what it is based on.
- Counting a check that couldn’t run (no baseline, no resources) as a pass.
- Fixing the metric instead of the logic, for example replacing a lag with a dummy activity.
How os.construction handles it
Schedule analysis runs all fourteen checks on a saved version. For each one it returns the value, the threshold, the threshold’s source, the counts behind the value and up to 20 offenders, which you can open in the Planner or export. Checks that can’t run are marked skipped and left out of the score. The basis statement travels with every grade. Read the GAO and DCMA review guide for context.