Baseline Execution Index

Field	Value
ID	bei
Denominator	Eligible activities with baseline finish (target_end_date) on or before the data date, plus eligible activities missing a baseline finish
Numerator	Eligible activities completed by the data date (TK_Complete; act_end_date ≤ data date when present)
Metric	N_completed / N_planned (count-based DCMA / DAU / NDIA)
Exclusions	TT_LOE, TT_Mile, TT_FinMile, TT_WBS
Threshold	0.95
Pass condition	value ≥ 0.95 → pass; ≥ 0.80 → warning; else fail. Degraded (info) when the data date is missing or the planned denominator is empty.

Intent

Measure schedule task throughput against the baseline plan through the status date — how many activities finished versus how many were baselined to finish by that date.

Single-file XERs use PROJECT.last_recalc_date as the data date and TASK.target_end_date as baseline finish (ADR 0148). A multi-file companion baseline lens is out of scope for K8.

ADR 0138 — Scheduling Kernel authority model ADR 0140 — Schedule graph and observed-path DCMA metrics ADR 0148 — Count-based DCMA Baseline Execution Index

See the Scheduling Kernel Plan — G14 closed by K8.

Remediation playbook

Recalculate in P6 so the export includes the data date and planned finishes. Investigate slipped work when BEI is below 0.95. Do not treat a simple completion percentage as BEI.

Implementation

Computed inside runHealthAnalysis → check id bei (src/features/health/utils/dcmaAnalysis.ts via src/kernel/graph/criticalPathMetrics.ts).