Prefabricated data centers: what is still in the site bid after factory testing?

Reconcile factory-tested module boundaries with field connections, site testing and evidence before carrying a prefabricated data center bid.

Guide6 min read

Published

Tower crane above steel reinforcement

Bring a data-center trade package. See how Piper compares the drawings, specifications and subcontractor bids, with source-linked findings your estimating team can review.

Book a demo
On this page
  1. A factory test has a defined boundary
  2. Two fictional offers, one unpriced interface
  3. Map the factory, shipping and site boundaries
  4. Ask what traveled and what must be demonstrated on site
  5. Carry the site scope on a common basis
  6. Review the module boundary against its sources

Before carrying the site electrical bid for a prefabricated data center, identify exactly where the factory-tested scope stops and who has priced the connections and proof outside it. Acceptance of each module's internal work does not, by itself, establish that the connections between modules are included in any offer or that the installed system has been demonstrated against the project requirements.

For a chief estimator, the decision is whether the combined vendor and trade prices cover that boundary on the same document revision. Piper bid leveling compares subcontractor bids with project scope and links findings to sources; the estimating team checks the evidence, clarifies the offers and decides the carry. The matrix below can also be used without software.

A factory test has a defined boundary

In its 2026 explanation of modular data centers, provider Vertiv describes factory assembly, integration and testing of components before shipment, followed by site assembly and infrastructure work. That is a provider description of an approach, not evidence that every project assigns the same work to its vendor or achieves a particular schedule or cost. The applicable contract documents and actual offers establish this project's scope.

Ask for the test boundary in terms of the actual module, interfaces, configuration and evidence, not just the name of the test. A record saying “factory acceptance” may refer to a defined set of checks inside a unit. A site proposal referring to “commissioning” may cover attendance, connections, a different test or a combination. Matching labels do not prove matching extent. Compare the listed activities and evidence against the current project requirements before deciding what remains to be priced.

This distinction is useful when modules are shipped separately and joined on site. It is less decisive if the project documents establish a different delivery configuration, but the estimator still needs the actual tested boundary and accepted scope. Do not assume a particular vendor or trade owns a task solely because it appears in a typical scope.

Two fictional offers, one unpriced interface

Consider a fictional project with two separately shipped power modules. The vendor's offer includes internal factory wiring and a factory test of each module. Its attached scope excludes inter-module field cables and field controls proving. The site electrical bidder's price covers placement of its identified site electrical work but states that the vendor provides inter-module cables and proves the controls interface. Assume the project requirements call for those connections and for evidence of the installed interface.

Both bids can be internally consistent while their combined scope leaves the same interface unpriced. A factory record for each module's internal wiring would not resolve that commercial gap. Neither would a generic statement that both parties include commissioning. The missing decision is who will furnish and install the field cables, who will participate in proving the controls interface, what evidence is required, and what each party's price covers.

The chief estimator should not add an arbitrary figure to the low bid and call the package complete. First ask both bidders for a common interface schedule and a price against the same current drawings, vendor boundary and project test requirements. If the scope cannot be settled before the carry, record a separately identified allowance or qualification under the estimate's normal rules, with an owner and the basis for it. An allowance is not a subcontract commitment or acceptance of the installed system.

Map the factory, shipping and site boundaries

Use a register for each interface, not just one row per bidder. The entries below are proposed assignments and open questions for the fictional example. Attach the actual document reference, revision and relevant proposal language in the project copy.

Boundary and evidenceProposed scope ownerConfirmed inclusion in fictional offerUnresolved price or scopeHuman approval
Factory internals: vendor scope and test recordModule vendorInternal wiring and test for each moduleIdentify test configuration and record deliverablesProject team reviews evidence against requirements
Shipping condition: packing and delivery documentsVendor and receiving party as agreedTwo modules shipped separatelyProtection, receiving inspection and corrective work not establishedProject team confirms condition and assigned responsibilities
Inter-module cables: drawings and both quotesElectrical sub proposedVendor excludes field cables; electrical sub assumes vendor provides themFurnish, route, terminate and price remain openGC assigns scope; engineer reviews technical boundary
Controls interface proving: project test requirements and both quotesVendor and electrical sub to propose rolesVendor excludes field proving; electrical sub assumes vendor performs itParticipants, attendance and price remain openEngineer and designated commissioning authority establish acceptance basis
Site assembly and infrastructure: current scope and offersGC and relevant site tradesOnly identified site electrical work includedPlacement interfaces and supporting work need reconciliationGC confirms trade coverage and project approvals
Witness and records: test plan and offersParties named in project requirementsFactory tests included; witness and field records not establishedWitness attendance, records and any repeat support openDesignated project reviewers accept required evidence

The table intentionally separates a proposed owner from a confirmed inclusion. Until a bidder accepts an instruction and provides a price or an authorized contract assigns the work, the owner cell is a question for resolution. “Open” should remain visible even if the team has a preferred trade in mind. The project team should also establish who will review the technical and acceptance boundaries; the estimator's carry does not replace that review.

Ask what traveled and what must be demonstrated on site

For each module, request the factory test scope and record, the configuration tested, identified interfaces and the condition in which the unit will be shipped. Then compare those records with the site requirements and the actual assembly boundaries. If the evidence is unavailable at bid time, record it as a pending deliverable and avoid describing the test as accepted.

A useful review distinguishes three questions. First, what internal work does the offer include? Second, what must be furnished or connected after separate units arrive? Third, what demonstration, witness attendance and records does the project require for the assembled interface? The answers can involve different parties. The site bidder may need a vendor representative, and the vendor may depend on a completed field connection before it can participate. Neither dependency assigns its own cost.

For the fictional pair of offers, send a clarification such as: “The vendor excludes inter-module field cables and field controls proving; the electrical offer assumes the vendor provides both. Identify your included work and exclusions at each module interface against the current drawings. Separately price any proposed cable supply, installation, controls proving support, required witness attendance and records. State the other party's work and readiness your price assumes.” Seek matching answers from both bidders, then resolve any overlap as well as any gap.

Carry the site scope on a common basis

Compare revised offers against the same interface list and project revision. Record the base price, accepted add-back or allowance, exclusions and open dependencies separately. A revised vendor offer may cover controls support while the electrical sub supplies the cable, or another allocation may be agreed. What matters is a documented price and a coherent handoff, not a predetermined division of labor.

Check whether receiving, protection, unloading, assembly, temporary support and site infrastructure appear in the relevant offers when the project requires them. Avoid assigning a cost twice just because two parties attend the same test: compare what each person actually does and how the quote prices it. Conversely, one party's attendance does not automatically include another party's field work or records.

For the broader contractor-side test support, use the data center commissioning scope review. If the owner purchases the modules directly, reconcile the vendor's obligations with the owner-furnished equipment bid-leveling guide, then check the remaining trade interfaces in the subcontractor bid coverage guide.

Review the module boundary against its sources

Bring the vendor scope, factory test description, shipping assumptions, site drawings and trade proposals into the project review. Piper's bid-leveling workflow compares bids with project scope and provides source-linked findings for the estimating team to inspect. The team can use those sources to request clarifications, record the revised price and make a carry decision. The project engineer and designated reviewers determine the technical and acceptance requirements; a commercial comparison does not certify the system.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

Review one data-center package with Piper

Bring a current or completed package, including drawings, specifications and subcontractor proposals. See how Piper compares scope boundaries and qualifications with the source behind each finding. Your team reviews the findings and decides what to carry.