What the function covers
- Baseline scope, cost, and schedule.
- Earned value measurement and reporting.
- Integrated master schedule in Primavera P6.
- Cost forecasting and cash flow.
- Procurement and long-lead tracking.
- Change order and trend management.
- Risk identification, quantification, and contingency control.
- Monthly program board reporting.
Earned value management in practice
EVM compares what you planned to do, what you did, and what it cost.
| Term | Meaning |
|---|---|
| PV (planned value) | Budgeted cost of work scheduled to date |
| EV (earned value) | Budgeted cost of work actually performed |
| AC (actual cost) | Actual cost incurred |
| SPI | EV / PV |
| CPI | EV / AC |
| EAC | Estimate at completion, commonly BAC / CPI as a starting point |
| VAC | BAC minus EAC |
Take a $400 million package with EV of $120 million, PV of $130 million, and AC of $135 million. SPI is 0.92 and CPI is 0.89. A straight BAC / CPI forecast puts EAC near $450 million, which is $50 million over. That is a starting point. A real forecast replaces it with a bottom-up estimate to complete for committed packages.
Where EVM breaks on data centers:
- Equipment deposits. A transformer deposit hits actual cost on payment and earns no value until the unit progresses. Define milestone-based earning rules for procurement (order placed, material purchased, factory test passed, delivered, set in place), or the numbers will mislead.
- Owner-furnished equipment. Decide whether it sits inside the controls baseline or alongside it. Be consistent.
- Commissioning. Test progress measures poorly against labor hours. Use level-based milestones instead.
- Aggregation. CPI averaged across a portfolio hides a failing campus behind a healthy one. Report by campus and package.
Primavera P6 schedule integration
Structure
Run a hierarchy that people can read.
- Level 1: Executive milestone schedule for the program board.
- Level 2: Integrated master schedule with design, procurement, construction, commissioning, and utility milestones.
- Level 3: Package schedules with logic and resources.
- Level 4: Weekly look-ahead for foremen.
Integration rules
- Link procurement to construction. A delivery date without a logic tie to the installation activity is a number on a page.
- Include utility interconnection milestones and equipment energization dates in the IMS. See Behind-the-Meter Power and Advanced Nuclear for why those dates deserve a conservative case.
- Code activities to the WBS and cost breakdown so schedule and cost roll up the same way.
- Resource-load the schedule with craft hours so the labor curve is real. Compare it to the plan in Labor Capacity Risk and Craft Mobilization Guarantees.
- Control the baseline. Re-baselining without approval erases the evidence of slippage.
Schedule quality
Run a schedule health check on every update. The DCMA 14-point assessment is a common standard: missing logic, excessive constraints, high float, negative float, hard constraints, long durations, and similar flags. A schedule full of constraints is a calendar, not a model.
Update weekly on active packages and monthly at the program level. Review the critical path, near-critical paths, and float erosion. On energization-driven programs, track float at the utility interface and the long-lead equipment interface separately.
Cost forecasting
A forecast has three parts: cost to date, committed cost not yet spent, and estimate to complete on uncommitted work.
- Reconcile with accounting monthly.
- Track commitments, not only actuals. Costs hidden in unbilled work in place or unprocessed invoices surface late.
- Forecast by cost category and package, with a trend log of probable changes that have not become formal changes yet.
- Separate escalation from scope growth. Copper, steel, and electrical equipment prices move, and the board needs to know which problem it has.
- Produce a cash flow forecast with deposit and milestone timing for long-lead equipment, since treasury needs it to plan.
Long-lead procurement risk tracking
Maintain a register for every long-lead item:
| Field | Purpose |
|---|---|
| Need-by date at site | From the IMS |
| Forecast delivery date | From the OEM, validated by expediting |
| Float to need-by | Calculated, trended monthly |
| Payment milestones | Cash plan |
| Specification freeze status | Late changes reset queue position |
| FAT date and status | Quality gate |
| Risk flags | Raw material, tariffs, labor actions, factory capacity |
Any item with float under the agreed threshold goes to the weekly procurement board. For commitment structures, see OEM Capacity Reservations and Supply Chain Capital Protection.
Change order management
Change orders are where money and claims live. Controls manages the process, and the discipline is boring.
- Notice. Contracts carry notice deadlines, and missing them can forfeit entitlement. Log the date a potential change is identified and the date notice is given.
- Categorize. Owner-directed, design error, differing site condition, regulatory, force majeure, contractor-caused.
- Quantify. Cost and time impact with backup. For time, use a time impact analysis against the current schedule, not a gut call.
- Approve at the right level. Authority thresholds published in the program governance structure. See Hyperscale Program Governance and Capital Risk Mitigation.
- Track. A single log with status, value, and aging. Unresolved changes older than 60 days need an escalation plan.
- Reflect. Approved changes enter the baseline through a controlled process.
Watch for trends. Dozens of small changes in one trade often point to a design or interface problem worth fixing at the source.
Capital risk on multi-gigawatt programs
The risk register is only useful if it is tied to money and to owners.
- Identify risks across utility power, equipment, labor, design, permitting, contracting, and commissioning.
- Quantify with probability and cost and schedule impact. For the schedule, run a Monte Carlo analysis on the IMS and report P50 and P80 completion dates. The distance between them is the schedule contingency you are actually carrying.
- Assign each risk to a named owner with a mitigation action and date.
- Link to contingency. Hold design, construction, and owner contingency separately and show drawdown against realized risks.
- Link to gates. Capital release gates reference open critical risks.
- Review monthly at the program board, with a short list of the top ten.
The monthly five numbers a board should see: committed cost against budget by contingency layer, long-lead delivery dates against need-by dates, utility energization milestones, craft labor on site against plan, and commissioning progress by level.
Tools and credentials
| Credential or tool | Use |
|---|---|
| Oracle Primavera P6 (training and practical experience) | Core scheduling tool |
| Cost systems and ERPs | Commitment and actual cost tracking |
| Oracle Primavera Risk Analysis, Acumen, or similar | Schedule risk and quality analysis |
| AACE PSP, CCP, or EVP | Scheduling, cost, and earned value credentials |
| PMI-SP and PMI-RMP | Scheduling and risk credentials |
| PMP | Generalist project management credential |
| Power BI or similar | Dashboards for the program board |
Compensation benchmarks
These are planning bands for US projects, not survey results.
| Level | Scope | Base planning band |
|---|---|---|
| Project controls manager | One campus or large package | $135k to $155k |
| Senior project controls manager | Large campus, multiple packages, risk ownership | $155k to $175k |
| Program controls and risk director | Multi-site program, board reporting | $175k to $185k+ |
Sources: BLS OEWS Project Management Specialists (SOC 13-1082) and Architectural and Engineering Managers (SOC 11-9041); live posting example Turner & Townsend Senior Project Cost Controls Manager – Data Center Construction (New Albany, OH). Pay data reviewed Nov 2026.
Factors that push pay up: owner-side seat, hyperscale program size, risk modeling skill, P6 expertise on integrated schedules above 20,000 activities, travel or remote assignment, and bonus tied to program milestones.
Career path
Common routes: scheduler or cost engineer to project controls lead to manager to program director. Estimators and field engineers move in through cost control. From the director level, paths lead to construction management, program management, and executive leadership, where the controls background is a significant advantage.
Common questions
Do I need a degree in engineering or construction management? It helps, and many senior controls people started in estimating, scheduling, or field engineering. P6 skill and a history of forecasts that held up carry the most weight.
How often should a data center schedule be updated? Weekly on active packages and monthly for the full program. Energization and long-lead milestones deserve closer tracking when float is thin.
What is a good CPI or SPI? Both should sit near 1.0. Persistent drift below 0.95 needs a recovery plan, and a figure that looks perfect month after month deserves an audit.
Who owns risk, the contractor or the owner? Both keep registers. The owner's register covers capital, power, procurement, and program risks. Contractors cover execution risks. Align them at the program board.