Delivery Models & the Owner's Organization

Chapter 2.1 built the schedule and named the long poles. The delivery model decides who is on the hook for each of them. An AI data center is built by a coalition: the owner, designers, a general contractor or EPC, dozens of trade and equipment vendors, a utility, and a chip vendor that sits outside all of it on an allocation clock no contract can fully control. The delivery model is the legal and organizational machinery that assigns risk, sequence and price across that coalition. You choose it once, early, and it is expensive to change. A project re-papered from EPCM to lump-sum EPC mid-design can consume schedule float while the parties reprice transferred obligations and agree new risk boundaries.

In order: the four delivery models; the three owner-side roles that exist because the contractor cannot mark its own homework; the owner-furnished line and the interface warranties it creates; multi-prime versus single-GC and the early contractor involvement that bridges them; the powered-shell handoff that splits a building in two; and the portfolio question that reframes the rest. The constraint throughout comes from Part 1: this is a power-bound, allocation-bound business. The winning delivery model protects time-to-power and absorbs long-lead and GPU-allocation risk, without pretending a contractor can guarantee what a chip vendor controls.

The models differ on three axes that matter to an owner: how many points of responsibility you contract with (one throat to choke, or many to coordinate), when the price firms up relative to design maturity, and who carries the gap between the estimate and the actual cost. Read them as a spectrum from most owner control and least risk transfer to the reverse.

Design-bid-build (DBB) is the traditional sequence. The owner hires a designer, completes the design, then bids construction competitively to a general contractor on a lump sum. That exposes a defined design to price competition and keeps design control with the owner, but construction waits for the bid package. Gaps in the documents can become GC change orders, so the apparent firm number still depends on completeness and risk allocation. For an AI build racing a power clock, reject the linear schedule when it misses the governing need date. Accept it when the design is complete and the procurement window has float.

Design-build (DB) puts designer and builder in a single entity under one contract. The owner gets one point of responsibility, fewer coordination disputes and the ability to overlap design and construction. The trade is less design control, because the design-builder optimizes for its own buildability and margin, and a price that is only as firm as the scope was when it was struck. Specialized systems (the IT fit-out, sometimes the GPUs and major electrical equipment) are often carved out of the DB scope and kept in the owner's hands. (Bracewell / National Law Review, 2026.)

Progressive design-build (PDB) is one route to a fast-track AI build when the owner can take part in design and commercial development. The owner picks the design-builder early on qualifications, before a baseline design exists, then develops design and budget together with that team. Progressive cost estimates arrive at milestones until the parties agree a construction price or GMP against defined scope. PDB brings the builder's constructability and procurement knowledge forward, lets long-lead orders and site work start against early design, and keeps the owner in the room for the decisions that matter. The costs are a deferred firm number and far more owner engagement than a hands-off lump sum. (AIA Contract Documents; FHWA, 2026.)

EPC / EPCM is the heavy-infrastructure model imported from power and process plants, and it is drawing growing appetite from owners who want to push risk onto contractors for faster delivery. A lump-sum EPC wraps engineering, procurement and construction under one contractor on a fixed price with a single point of responsibility. Risk transfer is limited to the obligations and exclusions the contractor actually signs, and the price carries a contingency the contractor owns and you pay for. EPCM (the 'M' is management) keeps the owner as the contracting party for the trade and equipment packages while the EPCM firm manages engineering, procurement and construction as the owner's agent. The owner keeps the risk and the savings, and pays a fee for expertise. The EPC-versus-EPCM choice is the same price-certainty-versus-control fork in heavy-industry clothing. (Bracewell, 2026; King & Spalding, April 2025.) CM-at-risk holds the agreed construction trade contracts; an agency CM advises an owner who retains them. EPCM adds engineering and procurement management to that owner-held structure. Compare all of them on the same axes: contracting party, price commitment, owner interface staff and retained completion risk.

Project size can affect the compensation mechanism. King & Spalding reported in April 2025 that commercial-cloud builds under $500M tended to use GMP, while $5–10B AI/hyperscale programs tended to use target-price painshare/gainshare. These pricing choices are separate from the delivery structure. The lesson from Chapter 2.1 carries straight through: the model exists to protect the critical path, and on an AI build that path runs through power and long-lead equipment. The model that keeps the owner close to those packages usually beats the one that wraps them cleanly but slowly. → Chapter 2.1 on the integrated master schedule; the long-lead register itself in Chapter 2.3.

Whatever the delivery model, the owner needs eyes that are not the contractor's. Three roles recur, and each is independent on purpose: the party doing the work cannot credibly certify its own work to the owner, the lender or the future tenant.

The owner's representative is the owner's authority on the ground: the single point of decision who manages the delivery contract, approves changes and payments, holds the schedule and budget, and speaks for the owner in the field. The role is large in an EPCM or multi-prime job and leaner under a lump-sum EPC, but never absent, because someone has to enforce the wrap. The owner's engineer (OE) is the independent technical conscience. It reviews the contractor's design against the owner's project requirements and basis of design, witnesses factory acceptance tests, and protects the owner from a design optimized for the builder's margin rather than the owner's operating life. The commissioning agent (CxA) verifies that the built plant actually performs. It owns the Level 1–5 commissioning sequence and, above all, the integrated systems test (IST) that proves power, cooling and controls work together under load before any GPU arrives. → commissioning levels in Chapter 13.1, the Level 5 IST in Chapter 13.6, and the go-live sequence in Chapter 13.10.

Price the owner's representative, owner's engineer and commissioning agent against their contracted scope and duration, and compare those fees across delivery models using the same defined construction-cost scope. The failures they catch (a mis-specified CDU loop, an undersized neutral, a controls sequence that oscillates under transient load) are the ones that strand capacity. Specify grid-facing transfer and return behavior in the acceptance scope: NERC documented approximately 1.5 GW of data-center load withdrawing from the grid as customer protection and controls transferred sites to backup during the July 10, 2024 disturbance. Give the CxA a direct reporting route to the owner and defined authority over test acceptance, so schedule pressure cannot suppress a failed test.

The next fork is what crosses the owner's procurement desk and what the contractor buys. Owner-furnished equipment (OFE) is bought by the owner directly and free-issued to the project for the contractor to install. Contractor-furnished equipment sits inside the construction scope, marked up and warranted as part of the wrap. The choice is a deliberate trade. OFE strips the equipment margin out of the GC's number and gives the owner direct control of the order date, but it moves the schedule and interface risk for that item onto the owner, who now owns the gap if the item arrives late or does not integrate.

Two categories show the decision clearly. GPUs and AI servers favor direct purchase when the owner holds the vendor allocation, the chips are a financeable asset on the owner's balance sheet, and the general contractor excludes the chip vendor's delivery date. GPU and server delivery is SKU-, system- and allocation-specific, so compare dated vendor quotes against the contractor's offer before assigning OFE. Power transformers and GSUs favor owner purchase when a dated supplier quote puts delivery on the critical path before GC selection. Wood Mackenzie reported US substation-transformer lead times above 160 weeks in May 2026. Generator step-ups are a separate generation/export package whose quoted delivery must be checked independently (Chapter 2.3). Where the owner has a release or allocation advantage, place the order or reservation before construction contracting closes.

On hyperscale work the OFE line extends further. Owners routinely buy switchgear, generators and the cooling plant (chillers/CDUs) directly to capture the margin and control the schedule, then issue them free to the job. That removes equipment margin from the GC and shifts its exposure into labor productivity, install quality and clean commissioning test results. (Industry practice, 2026.) Choose contractor furnishing when its reservation, integration staff and warranty offer beat the owner's on the same package. Record the scope here, the release conditions in 2.3 and custody and remedies in 2.4.

The hidden cost of OFE is the interface warranty. Unless the contract assigns integration duties, the OEM's equipment warranty and the EPC's installation warranty can leave the seam between them uncovered. Say the owner free-issues a transformer and the EPC installs it. If the transformer's protection settings do not coordinate with the contractor-supplied switchgear, the owner is in the middle of a two-vendor finger-point with no single wrap to fall back on. Assign protection coordination, settings, installation checks and integrated performance to a specific party each. The more OFE you take, the more of these seams you own, and the more your owner's representative and owner's engineer earn their keep stitching them together. OFE is a schedule-and-control instrument rather than a savings play: you take it to control the order date on a long-lead item, and you accept the integration burden as the price. → the OFE interface warranties as a contract problem in Chapter 2.4; the procurement mechanics of slot-reservation deposits in Chapter 2.3.

A parallel structural choice runs alongside the delivery model: do you contract one general contractor who subcontracts everything (single-GC), or hold several prime trade contracts yourself (multi-prime)? Single-GC gives you one schedule, one point of coordination and one party to hold accountable, at the price of the GC's overhead and markup on every package and a layer of distance from the trades. Multi-prime strips out that markup and lets you fast-track by awarding the long-lead and critical packages (electrical, mechanical) directly and early. But you, or your EPCM agent, now own the coordination risk the single GC was paid to absorb. Multi-prime works for a sophisticated owner with real project controls. Without them, coordination failures land on the one party with no one to subcontract them to.

The bridge between 'design first, build later' and 'build fast against immature design' is early contractor involvement (ECI) and design-assist. Both bring the builder and key trade contractors into the design phase, not to design but to price, sequence and pre-order against an evolving design. Design-assist on the mechanical and electrical packages lets the contractor lock the cooling plant and power-chain vendors and place long-lead orders while the architect is still drawing, which allows long-lead procurement to begin before the full design is complete. Direct owner orders and framework supply agreements can also release equipment early, which matters because the power clock started before the design did. ECI is what makes progressive design-build progressive: the contractor is in the room early enough to turn constructability and procurement knowledge into a schedule, not just a price. Skip it and you get the classic fast-track failure. Design and construction proceed in parallel but uncoordinated, and the rework at the seam costs more than the schedule the parallelism saved.

The largest scope split in the delivery question is whether to deliver the base building and the IT fit-out as one continuous scope or as two, joined at a powered-shell handoff. A powered shell is a secure structure with power brought to the site, the building envelope, structural readiness for high-density loads and cooling pathways stubbed in, but typically without the UPS, generators, cooling plant and IT infrastructure. (Build.inc, 2026.) The developer builds and delivers the shell; the tenant or operator fits out the inside. Part 1 framed the powered shell as a way to preserve IT-fit-out optionality and keep an irreversible decision cheap. → Chapter 1.6.

The split buys two things: parallelism (the shell rises while the fit-out design and GPU allocation are still maturing) and optionality (the operator commits to the inside only when the chips and the workload are real). The cost is a new, sharp interface: exactly what crosses the handoff line, and in what condition. Where does the developer's power delivery stop and the operator's electrical fit-out start? Are the cooling pathways merely stubbed, or actually capable of the density the operator intends? Who owns the structural rating for wet racks the developer never saw? An ambiguous boundary is costly because every gap becomes a dispute just when the operator is racing to energize. The fix is a carefully specified delivery condition: power capacity and voltage at the boundary, structural loading, cooling pathway sizing, and the conditions that trigger additional landlord obligations. Write it before the shell is designed, not at handoff. (Build.inc, 2026.)

Five drivers decide which way each fork above breaks, and they do not point the same direction. Schedule pushes toward progressive design-build, fast-track, ECI and OFE on the long poles: anything that overlaps work and protects time-to-power. Cost certainty pushes the other way, toward a complete design and a lump-sum wrap a lender can underwrite. Scope maturity is the tiebreaker. A mature, well-understood scope can be bid lump-sum cleanly. Incomplete detailed design can also support a firm price when performance requirements, package interfaces, exclusions and retained risks are defined and priced. Where those boundaries remain unresolved, develop and price the scope in phases. In-house capability decides how much risk the owner can actually hold: EPCM and multi-prime hand the owner the savings and the risk, and only an owner with real project controls should take them. The fifth driver is where the analysis changes shape.

Repeatability across a portfolio changes the payoff of everything above. Portfolio repetition changes the payoff from standardization and owner staffing; it does not automatically require a different delivery model. A single project optimizes for the certainty and speed of that one asset. A portfolio optimizes for a standardized reference design built repeatedly with the same delivery team, where design-assist, ECI and OFE master agreements amortize across buildings and the learning curve drives cost and schedule down with each repetition. A multi-GW program can spread the cost of in-house engineering, an EPCM-style organization and a templated design across repeated builds. On a one-off shell, justify those investments against the particular packages and interfaces they improve. The first question is therefore 'am I building one or building a program', and the answer reorders the other four drivers before you weigh them.