Skip to content
TerraForgeTerraForge

For hyperscale owners and operators

Modern PMIS for AI Data Center Builds

The industry’s first modern PMIS built for data center and energy buildouts — powering what’s next.

Every megawatt, on one schedule of record. Cost, cash flow and the colors of money roll from the hall to the campus to the portfolio. Turnkey for that programme. Configurable after go-live.

The scope is the full build-out: shell and civil, the data hall, the substation and the generator yard — then the work orders and master agreements that maintain them. TerraForge does not clear an interconnection queue. It records the status, the megawatts and the draw. The Operations Wall is the review screen, not the system of record.

Request a demoPortfolio, programme, project
TerraForge Organisation Dashboard, Project Management tab, portfolio roll-up for the Data Center Build Programme in US dollars — approved budget 5.75 billion, committed 4.56 billion, actuals 118.8 million, headroom 5.63 billion, 14 campuses and 43 projects
Organisation Dashboard · portfolio roll-up · US dollars
$5.75B
Approved budget
$4.56B
Committed
14
Campuses
43
Child projects
10
States lit

Demonstration tenant. $4.56B of $5.75B is committed. Actuals $118.8M. Includes a 168 MW data hall phase. These figures describe that tenant.

Owner-side PMO

Built for owners who carry the schedule risk.

Energization is the date that matters, and the owner carries the exposure between the campus build and the power build. TerraForge is the owner PMIS for that exposure — portfolio, programme and project on one set of records. It does not clear an interconnection queue, and it does not shorten a lead time.

  1. 01

    Every megawatt, on one schedule of record.

    Schedule Manager holds the critical path, the baseline and the float on the programme or the project. The portfolio dashboard reports that finish. Primavera P6 comes in by XER or XML and updates in place; keep the TerraForge baseline and slippage is computed here. The utility’s date stays the utility’s. You can see it on the same schedule as the hall.

    Schedule of record

  2. 02

    Control the long-lead path before it controls you.

    Transformers, switchgear and generators move on their own clock. A submittal can hold lead time, anticipated delivery and actual delivery, and be flagged critical path. The schedule activity can carry the cost code. Cash flow can take its months from those dates and shows drift when they move. A late delivery shows up as slippage and as a draw.

    Long-lead on the record

  3. 03

    Roll up every campus, phase, and hall.

    The organisation cost sheet rolls the programmes. A programme cost sheet breaks down by project. The project sheet is the cost codes — pending and approved apart. The portfolio dashboard reads budget, committed, spent and forecast at completion from those records. The risk heat map reads the risk register. State dashboards scope the same picture.

    Portfolio, programme, project

  4. 04

    Find any record. Open it. Come back.

    Most legacy PMIS make you hunt module by module. Global Search finds an asset, a project, a schedule, a drawing or a contract — and every other register and published custom app — then opens the live record and returns you to the results.

    Global Search

  5. 05

    Give PMO and finance the same numbers, every week.

    Freeze a cash-flow baseline and compare the forecast to it. Take a snapshot of the project or the whole portfolio — label it for the board pack — and compare it with the live plan. Actuals are approved payment applications. Forecasted total cost on the cost sheet is the figure the pack exports.

    Cash flow and the board pack

  6. 06

    From first award to handover, under owner control.

    A bid package prices a frozen bill of quantities, seals the returns, and drafts the contract from the award. Drawings keep every revision. Takeoff and the bid pin to the revision issued for takeoff, and compare shows what moved when density or cooling changes the design. Closeout submittals — O&M manuals, warranties, as-builts — stay on the project with the permit and the daily report.

    Bid through contract
  • Owner-side PMO
  • Portfolio roll-up
  • Global Search
  • Programme controls
  • Long-lead visibility
  • Cash flow forecasting
  • Change control
  • Multi-phase delivery
  • Schedule of record (P6)

The exposure

When energization is the date that matters.

Time to power is not a construction duration, and a moved energization date is a financing problem as much as a site problem. TerraForge gives the owner’s PMO one place to see that date, the commitment on the long-lead gear, and the cash-flow consequence. It does not get a project through an interconnection queue. Turnkey for day one — campuses, cost codes, schedules, bids and field records ship with the product. App Builder is how the programme team publishes the next form after go-live.

The full build-out

Energy and the campus. The shell and the hall. Then the work that keeps them.

TerraForge is the owner PMIS for the whole AI data center build-out, not the IT fit-out alone. Power, the shell, the data hall and the maintenance that follows energization are records in one portfolio.

Energy with the campus

Power sits on the same portfolio as the hall.

Substation and generator yard are asset categories, next to campus, data center and data hall. The facility profile holds contracted and operational megawatts, utility feeds, generators, cooling and PUE. The state record holds the primary utility, the ISO, contracted megawatts against what is operational, and interconnection status from not filed to energized. That status is the owner’s record of the queue. TerraForge does not clear it.

Shell, civil, and the hall

The shell package and the fit-out are one programme.

Takeoff can load a shell bill by cost code into the bid. Civil is a works category on the master agreement — the site and the foundations travel with that package, not in another system. The data hall is its own asset and its own project: white space, racks, gross area, and the fit-out that prices racks, PDUs and heat rejection. One cost sheet rolls both.

After energization

Maintenance stays on the asset.

A work order is raised on the campus asset after energization — switchgear PM, fuel polishing, a generator ATS transfer, infrared thermography, or corrective and warranty work — and assigned to a supplier. Completing it charges the actual cost to an approved master agreement, once. Those agreements cover power, cooling, fiber and fire and life safety. ERP sync sits on the agreement. Ball-in-Court lands in My Tasks. Vendors do not sign in to the work order.

Portfolio, campuses and assets

How an owner runs it

Organisation, state, programme, project, asset.

A dashboard sits on each. Cost sheets roll and segment. Funding is visible from the portfolio to the project. The wall is only the organisation dashboard, on a screen.

  1. 01The booksOrganisation
  2. 02The regionPortfolio / State
  3. 03The campusProgramme
  4. 04The packageProject
  5. 05The thing builtAsset

Portfolio · funding

Fund Sheet for every pot. The organisation cost sheet shows Funding Allocations (Approved) and Budget vs Funding Δ.

Programme · funding

A Funding tab on the programme. An allocation can name it. The cost sheet breaks that funding out by project.

Project · funding

A Funding tab on the project. The request total is its approved budget. The dashboard shows Funding Approved and Budget vs Funding Δ.

Open the control model

The operating system

The records behind the build.

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.

  1. 01

    Capital programme

    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.

  2. 02

    Portfolio control

    The owner’s view of the wave: campuses, money, MW and risk, with a cockpit for the room.

  3. 03

    Programme delivery

    Primavera P6 comes in by XER or XML and updates the same schedule in place.

  4. 04

    Project execution

    The hall itself: drawings and takeoffs, the controlled document set, RFIs and the field record.

  5. 05

    Maintenance

    After energization, work orders on campus assets draw against approved master agreements for power, cooling, fiber and fire and life safety.

  6. 06

    Bidding

    From a secure vendor bid to the contract the award becomes.

Funding Manager

Colors of money, visible from the portfolio to the project.

The cost sheet says what a campus will cost. Funding Manager says where the money comes from, and keeps each source intact through allocation, change and reversal.

The Fund Sheet is the portfolio view. An allocation names the programme or the project it funds. The organisation, programme and project cost sheets show Funding Allocations (Approved) and Budget vs Funding Δ. The project dashboard shows Funding Approved beside that same gap.

Capital programmes and the Fund Sheet

TerraForge Fund Sheet with revised value, consumed and remaining balance, and separate pots for data center infrastructure, power and cooling
Fund Sheet. Demonstration. One row per source. Revised value, consumed, remaining. The nav is the allocation request, the source change and the reversal.
Funding Sources
The pots. The fund code locks the name, the type and the funding-breakdown group. Original amount, base currency and, for time-limited money, an expiration date.
Fund Sheet
One row per source, grouped by that structure. Revised value, consumed, remaining (revised minus consumed minus pending), pending demand, and how many funds expire within 12 months. A mixed-currency group is marked Mixed.
Allocation request
Draws from one or more sources. The split must total 100%, and priority 1 is consumed first. The target is a programme or a project. The request total is that record’s approved budget position.
Source change and reversal
A change revises a pot’s value. The original amount never changes. A reversal returns an approved allocation in the same proportions. Approved requests cannot be edited, re-split or deleted.

Where the owner reads it

Portfolio, programme, and project — the same colors.

  1. 01

    Portfolio

    Fund Sheet for every pot. The organisation cost sheet shows Funding Allocations (Approved) and Budget vs Funding Δ.

  2. 02

    Programme

    A Funding tab on the programme. An allocation can name it. The cost sheet breaks that funding out by project.

  3. 03

    Project

    A Funding tab on the project. The request total is its approved budget. The dashboard shows Funding Approved and Budget vs Funding Δ.

Funding types on the fund code

  • Corporate capex
  • Debt financing
  • Government grant
  • Partner equity
  • Operating budget
  • Lease / sale-leaseback
  • Vendor / OEM financing
  • Customer prepayment

Approved allocations are immutable. Money returns only through a reversal. A pot’s value changes only through a source change. Pending demand stays off the approved column until the workflow says so. Numbering is FS, FR, FCR and FRV.

Portfolio cockpit

The Operations Wall is the review screen for the wave.

Presentation mode walks a portfolio review through six frames. Campuses, MW, cost and energization risk go on the wall. Programme delivery and project execution stay on the records — the cost sheet, the Gantt, the bid, the RFI.

  1. 01Financial
  2. 02Campus Map
  3. 03Campus Programmes
  4. 04Spotlight
  5. 05Risk & Issues
  6. 06Assets & Operations

Auto-rotates in this order. Demonstration environment.

Operations Wall risk and issues frame for a demonstration data center portfolio — utility capacity, switchgear and UPS lead time, and energization
Operations Wall · Risk & Issues. The command-center frame further down the page. Utility capacity, long-lead electrical gear, energization. Landscape, demonstration environment.

About

Built by people who lived in it.

We build TerraForge for owner PMOs who carry the schedule risk on a capital programme. The about page is that story.

About TerraForge

Also used for highways, water, rail, energy, airports, ports, public portfolio, nuclear, and universities. Other sectors. Write sales@terraforge.build.

See the full PMIS against your campus programme.

Your cost codes, your workflow, your campuses. Write sales@terraforge.build.

Request a demo