Critical (total float ≤ 0) and near-critical (≤ 10 working days) activities, sorted by early start - from the same CPM run as the rest of this page, not a separate calculation.
Everything below comes straight from the uploaded schedule's own PROJECT row and this page's CPM run — nothing here is estimated.
Recomputed via CPM from current schedule logic and durations. Red bars are critical (zero float).
Near-critical activities (1–10 working days of float) from this update alone — the ones most likely to become critical if anything slips.
| Activity | WBS | Float | Early Finish |
|---|
| Activity | Prior Finish | Curr. Finish | Variance | Prior TF | Curr. TF | Flag |
|---|
Sorted by how fast float is disappearing between updates, not by where it sits today — an activity that dropped from 20 days float to 8 is a bigger near-term worry right now than one that's simply sat at 8 days both updates, even though a current-float-only view treats them the same.
| Activity | WBS | Prior TF | Curr. TF | Δ Float | Trend |
|---|
The DCMA 14-point schedule quality audit, run against the current update, with a plain-English line under each check. Four checks require data this XER export doesn't carry (constraints, resources, baseline performance indices) and are marked accordingly — that's an honest gap, not a bug.
| # | Check | Result | Threshold | Status |
|---|
| Start | Activity | Duration | Finish | Float | Predecessor Status |
|---|
Activities auto-matched against a keyword library of long-lead materials, with an order-by date computed from that activity's own early start minus its typical lead time. Overdue items (order-by date already passed) are pinned to the top.
| Activity | Material | Lead Time | Early Start | Order By | Days Remaining | Float |
|---|
| Activity | Status | Physical % | Duration % | Divergence |
|---|
Computed fresh from the current schedule's logic and durations. Max-crash-days and cost/day below are pre-filled with placeholder estimates (duration-based, not from any file field — this XER format carries no per-activity cost data) so the workbench is usable immediately; replace them with real numbers for an accurate result.
| Activity | WBS | Duration | Float (CPM) | Max Crash (days) | Cost / Day Crashed ($) |
|---|
| Step | Activity Crashed | Cost this Step | Cumulative Cost | Resulting Finish | Recovered |
|---|
Uses the same cost/max-crash assumptions entered above, run against two different targets — and, optionally, a cost multiplier for Scenario B (e.g. 1.5× to model overtime/expedite rates), so you're not stuck seeing only one result at a time.