BCWS / BCWP / ACWP

BCWS, BCWP and ACWP are the legacy acronyms from the original US Department of Defense Cost/Schedule Control Systems Criteria (C/SCSC), introduced in 1967 and reissued as the modern EVMS standard. BCWS — Budgeted Cost of Work Scheduled — is the cumulative budget for the work that was planned to be complete by the data date; this is now called Planned Value (PV). BCWP — Budgeted Cost of Work Performed — is the cumulative budget for the work that has actually been completed, regardless of what it cost; this is now called Earned Value (EV). ACWP — Actual Cost of Work Performed — is the cumulative actual cost incurred for the work completed; this is now called Actual Cost (AC).

The terminology change from BCWS/BCWP/ACWP to PV/EV/AC was made by the Project Management Institute in PMBOK 4 to make the concepts more accessible. The maths is identical — Schedule Variance is still BCWP − BCWS (now EV − PV) and Cost Variance is still BCWP − ACWP (now EV − AC). The legacy acronyms still appear in older EVMS standards, ANSI/EIA-748 documentation, and on UK MoD programmes that have inherited US defence reporting templates. A practitioner reviewing a programme with mixed legacy and modern documentation should be fluent in both.

The pitfall to watch for is inconsistent application of the underlying definitions, regardless of which acronym is used. BCWP/EV must be earned against objective progress rules — 0/100, 50/50, weighted milestones, percent complete with apportioning — not self-reported judgement. ACWP/AC must include all costs incurred for the work, including accruals for committed-but-not-invoiced expenditure, otherwise CPI is artificially flattering. And BCWS/PV is only meaningful if the schedule and budget are integrated against a controlled Performance Measurement Baseline. Sloppy definitions at the data layer produce variance metrics that look authoritative but cannot be trusted.