Rail Industry Pack

Rail & Transit Cost and Schedule Forecasting

Rail delivery is governed by access. Your forecast is really a forecast of how much work you can complete inside the possessions you have been granted, everything else follows from that.

How the engine works

Typical project-controls challenges in rail

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.

Possession windows cap output

A weekend blockade delivers what it delivers. Adding labour beyond the working face achieves nothing, so resource-based recovery plans are usually fiction.

Access, not resource, is the constraint

Over-running a possession is severely penalised

Handing back late incurs Schedule 8-type penalties and jeopardises future access. The incentive is to leave work undone rather than over-run.

Penalties can exceed the work value

GRIP / PACE stage gates control spend

Funding releases by stage. Forecasting outturn without forecasting the stage gate date forecasts a number nobody can authorise.

Gate dates gate the money

Setup and handback consume the window

Isolation, protection, plant on and off track, and testing before handback can take a third of a short possession before any work happens.

Short windows are mostly overhead

Third-party and stakeholder approvals

Signalling design acceptance, network change and stakeholder consents run to their own timetable, largely outside your control.

Approval lead times exceed work durations

Which capabilities apply

Every tool below is a separate workbook that works on its own. These are the ones rail 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 Rail 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

Site clearance & enabling
Earthworks & drainage
Track renewal
S&C installation
Signalling & telecoms
Testing & commissioning

Cost codes

Possession setup & handback
On-track plant & RRV
Isolation & protection staff
Materials by track metre
Over-run penalty provision

Risk register

Possession cancelled or shortened
Over-run and penalty
Signalling design late
Unrecorded buried services
Plant failure in possession

Stage milestones

GRIP / PACE stage gates
Design acceptance
Network change approval
Blockade dates confirmed
Entry into service

Worked example

Track renewal programme, 9 of 26 possessions used

BAC £31M. EV £9.1M, AC £10.7M, PV £10.2M. Average effective working time is 62% of the possession length against a 75% baseline assumption.

CPI

0.85

EAC

£36.5M

Possessions needed

P80 completion

+6 weeks

You are 13 percentage points down on effective working time, which converts directly into six extra possessions you have not booked. Access applications have a lead time. This forecast is only useful if it reaches the access planner in time to act on it.

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

Rail questions

Can I model different possession types?

Yes. Midweek nights, weekend possessions and full blockades each carry their own setup, handback and effective-output profile.

Does it forecast over-run penalty exposure?

It carries a provision driven by your historic over-run rate rather than an arbitrary allowance.

Is it aligned to GRIP or to PACE?

Stage names are configurable, so it suits either, and other national frameworks too.

Does it cover metro and light rail?

Yes. The access model is the same wherever engineering hours constrain the work.