Energy Generation Industry Pack

Energy Generation Project Forecasting

Generation projects live or die on commodity escalation, long-lead plant and a grid connection you do not control. The forecast has to hold all three at once, over a multi-year build.

How the engine works

Typical project-controls challenges in energy generation

The method is the same everywhere. These are the sector conditions that make a generic approach wrong, and what each one means for how you control the project.

Commodity and fuel escalation over a long build

Steel, copper and fuel prices move materially across a four-year programme. A forecast in today's prices is not a forecast.

Escalation must be modelled, not ignored

Grid connection is an external dependency

The connection date is set by the network operator. Finishing early simply means an asset that sits idle, earning nothing.

Early completion has no value without grid

Turbine and BOP long-leads set the critical path

Turbines, generators and balance-of-plant carry lead times of eighteen months or more. Procurement, not construction, is the programme.

Procurement is the critical path

Availability ramp defies the business case

Plant rarely reaches design output on day one. The ramp period between commissioning and full availability is habitually underestimated.

Revenue lags completion by months

Subsidy and offtake deadlines are absolute

CfD, ROC or PPA milestones carry cliff-edge consequences. Missing the date can remove the revenue basis of the whole investment.

A missed date can void the business case

Which capabilities apply

Every tool below is a separate workbook that works on its own. These are the ones energy generation teams tend to reach for, and what each one answers.

Analyse

Whether the programme you were sent is built properly, before you rely on it
Where the critical path really runs, and how much float is protecting it

Schedule Quality Analyser

Control

Cost and schedule performance against the baseline, in CPI and SPI
Change and risk exposure on one register, not in email

The core suite

Forecast

Outturn cost and completion date as a range, not a single number
The contingency needed to be 80% confident, not 50%

Forecast Engine

Measure

Progress claimed against rules of credit rather than opinion
An update block you can paste straight back into P6

Progress Measurement System

Contract & claims

Whether a submitted programme meets NEC4 clause 31.2
Productivity loss measured against an unimpacted period

NEC4 Compliance Disruption & Productivity Loss

Sustainability

Capital carbon baseline and forecast against target
Evidence trail for PAS 2080 assurance

Carbon & PAS 2080

How it runs, month to month

Export two tables from P6 or Microsoft Project. An activity list and a relationship list. Nothing in your scheduling tool changes.

Paste them in. The shaded cells are the only inputs. Everything else is formula-driven.

Check the programme is sound. The schedule quality scorecard runs the DCMA checks and tells you what to fix before you forecast from it.

Enter the period progress and cost. Earned value, actual cost and planned value by period.

Read the forecast and issue the report. CPI, SPI, EAC and the P50 to P80 range, with the assumptions recorded alongside them.

What's in the Energy Generation edition

The engine is identical across industries. The edition supplies the content that makes it speak your sector's language, so it is useful the first time you open it rather than after a fortnight of setup.

WBS skeleton

Development & consenting
Civils & foundations
Plant procurement
Erection & installation
Grid connection works
Commissioning & ramp

Cost codes

Turbine / generator supply
Balance of plant
Steel & copper indexed
Fuel & commissioning energy
Grid connection charges

Risk register

Commodity escalation above index
Grid connection delayed
Turbine delivery slip
Commissioning underperformance
Subsidy deadline missed

Commercial milestones

Financial close
Notice to proceed
Plant delivery
First synchronisation
Commercial operation date

Worked example

CCGT plant, month 22 of 40

BAC £520M. EV £268M, AC £287M, PV £276M. Steel is tracking 9% above the baseline index and the grid connection has moved four weeks later.

CPI

0.93

EAC

£559M

P80 outturn

£588M

P80 COD

+9 weeks

Nine weeks past the commercial operation date is not nine weeks of cost. It is a quarter of lost generation revenue and, if it crosses the offtake deadline, a materially different investment case. COD is the number the board needs, not EAC.

Illustrative figures, shown to demonstrate the method. Your numbers replace them.

Reports and outputs

Each of these is a sheet in the workbook. They recalculate when you enter the period progress, so there is nothing to assemble at month end.

Cost forecast

Three EAC methods side by side
CPI, SPI, cost and schedule variance
Variance at completion and TCPI

Monte Carlo

1,000 iterations, no macros
P50, P80 and P90 outturn cost
Forecast duration and delay against baseline

Earned Schedule

Time-based schedule performance
Forecast completion date
Stays honest late in the job, unlike SPI

Cash flow and resources

Payment lag and retention modelled
Peak funding requirement
Resource forecast by period

Productivity

Trend against planned rate
Early warning before CPI moves

Assumptions and audit

Every distribution, its source and date
The record that defends the number

Energy Generation questions

How is escalation applied?

Per cost code against an index you set, so steel and copper can escalate at different rates and both flow into the forecast.

Can it model the availability ramp?

Yes. Ramp is forecast separately from completion, because revenue follows availability rather than handover.

Does it handle the grid connection dependency?

As a hard external milestone. Completion earlier than the connection date is shown as idle asset time, not as float.

Is it suitable for renewables as well as thermal?

Yes. Solar, wind and storage use the same structure with different plant codes and ramp profiles.