Modern PMIS for AI Data Center Builds
01
The books
The whole wave, before a campus is opened.
The organisation dashboard is the first screen after sign-in. It rolls portfolio cost, open work, approvals and field activity. Every number opens the register behind it. The organisation cost sheet is where programmes and standalone projects land.
02
The region
State is the portfolio a hyperscale owner actually chairs.
In the US data center configuration, State is the branded portfolio level — the guide’s county or region. Utility, ISO or RTO, and interconnection status from Not filed to Energized are recorded here. TerraForge does not clear the queue.
03
The campus
One campus, or one power thread, held as a programme.
A programme is the container a PMO chairs: a multi-hall campus, a power programme, a cooling programme. Child projects roll into it. The cash-flow curve and the schedule are read here when the question is the campus.
04
The package
The hall, the yard, the package — where the work is approved.
A project lives under a programme, or stands alone and rolls straight to the organisation cost sheet. This is the WBS, the contract, the drawing revision, the RFI and the bid.
05
The thing built
The register counts the campuses, the megawatts and the value.
Assets are Campus, Building, Data Center, Data Hall, Substation, Generator Yard, Office and Parcel. The facility profile holds operator, tier, contracted and operational megawatts, PUE, redundancy, utility feeds, cooling and white space. Those figures roll to the state and the organisation.
Programme cost sheet
Programme Cost Sheet rolls up from child projects — Initial, Changes, Transfers, Revised. Most legacy PMIS stop at the project sheet. Abernathy HPC Campus Program is the demonstration. The composition bar is the child projects summing into Approved Revised Budget.
Hall against yard against substation is the drill, not an export rebuilt on Friday. The organisation sheet is the same arithmetic one level up. The project sheet is the cost codes.
Funding on the three money levels
Portfolio
The Fund Sheet is the portfolio view of every pot: revised value, consumed, remaining, pending demand, and funds expiring within 12 months. The organisation cost sheet shows Funding Allocations (Approved) and Budget vs Funding Δ. An allocation does not target the portfolio. It targets a programme or a project, and this level reads the result.
Programme
The programme record has a Funding tab. An allocation can name this programme. Its cost sheet carries Funding Allocations (Approved) and Budget vs Funding Δ. Break the sheet into the programme’s own lines versus its projects, or one row per child project, and see which project is driving the funding figure.
Project
The project record has a Funding tab. An allocation names this project, and the request total is its approved budget position. Priority 1 is consumed first. The split must total 100%. Approved requests are not edited — money returns only by reversal.
The operating system
From the wave, to the campus, to the hall, to the contract, then the work that keeps the asset. Each link is a working record — not a slide.
01
Budget first. Then the contract, the change, the application, the schedule of values, the draw, and the date. Funding Manager follows for owners who separate sources.
02
The owner’s view of the wave: campuses, money, MW and risk, with a cockpit for the room.
03
Primavera P6 comes in by XER or XML and updates the same schedule in place.
04
The hall itself: drawings and takeoffs, the controlled document set, RFIs and the field record.
05
After energization, work orders on campus assets draw against approved master agreements for power, cooling, fiber and fire and life safety.
06
From a secure vendor bid to the contract the award becomes.
Your cost codes, your workflow, your campuses. Write sales@terraforge.build.
