Leveling bids when the owner buys the equipment

When the owner buys the generators, switchgear, UPS and cooling units, the electrical and mechanical bids stop being prices for equipment. They become prices for a chain of steps: receiving the gear, storing it, setting it, connecting it, starting it up and helping prove it works. Leveling those bids by cover price compares how much of that chain each bidder chose to write down. Level each owner-furnished item across the same steps instead, and the gaps show up where they cost the most: between the vendor's scope and the installer's.

This guide is for GC estimators and precon managers leveling electrical and mechanical packages on data centers where the owner furnishes major equipment through its own vendor agreements. That arrangement is owner-furnished, contractor-installed (OFCI), sometimes written OFE or OFCI in Division 01. It is common on hyperscale programs and on many colocation builds. It does not apply as written when the contractor furnishes the equipment (CFCI), or where the owner's vendor installs and commissions its own gear turnkey. In that case, level the interface to the vendor using the same steps. For the general leveling method this sits inside, see the practical guide to construction bid leveling. For why data center work differs from commercial precon more broadly, see data center precon is not commercial precon with more power.

Why owner-furnished equipment changes what a bid is

On a contractor-furnished job, the equipment price carries a lot of the bid: the gear, the vendor's startup, the warranty and the sub's markup on all of it. When the owner buys the equipment, all of that leaves the subcontract. What remains is labor, coordination, installation quality and the evidence commissioning will ask for.

Three things follow.

The differences between bidders move into assumptions. Two electrical proposals can land close together on price because one assumed the manufacturer starts up the UPS and the other carried a crew to support it. Neither is wrong. They are pricing different chains.

The GC is between two contracts it does not fully control. The vendor contracts with the owner. The installer contracts with the GC. As Fenwick Elliott notes in its analysis of data center delay claims, a contractor installing owner-furnished switchgear or UPS has no direct contract with the vendor and little leverage when delivery slips.

The contract has to name each step. Guidance published in Construction Dive on data center contracts puts it plainly. The agreement should say which party will procure, transport, offload, install, integrate and test each system. If the prime contract is vague about that, the subcontract bids will be too, and leveling is where the vagueness shows.

The ten steps to level for every owner-furnished item

Treat each owner-furnished item as a row and each step as a column. For every bidder, mark each cell included, excluded, qualified or silent, then compare the pattern against what the owner's documents require.

The first two and the last three are the columns most often left silent. They sit at the start and end of the chain, where the vendor's scope and the installer's scope meet. Steps seven through nine are commissioning Levels 3 to 5 seen from the installer's side; for pricing them, see commissioning is scope.

Build the matrix from the owner's documents, not from the bid form

The rows come from the owner, not from the proposals. Start with the equipment responsibility matrix, usually in Division 01 or an owner standard attached to the prime contract, and the owner's equipment list. Then check three things before any proposal is opened.

Count units by topology. A block-redundant "4 to make 3" design and a 2N design with the same megawatt rating carry different numbers of UPS modules, switchgear lineups, generators and feeders. Take the count from the one-line diagram, and make every lineup, generator and module its own row. A bidder who priced the wrong topology is not low. They priced a different building.

Match the owner's purchase to the design. The owner's procurement team buys against its own specifications and schedule, and those do not always match the construction documents. Uptime Institute has described a case where an owner's procurement team bought a UPS without the bus needed to connect it. Check that each owner-furnished item includes the accessories, connection points and spare parts the installation assumes. If it does not, the missing piece needs an owner before it reaches the leveling sheet.

Get the delivery dates. Each row needs the owner's expected delivery window. The storage, rigging and crew-loading columns depend on it, and so does the schedule argument later.

What to read in each proposal

On OFCI packages, the risk hides in short phrases that sound complete. For each step, read the exact wording against the row it claims to cover.

• "Install owner-furnished equipment." This covers some of steps 4 through 6 and may cover none of steps 1, 2, 3 or 7 through 10. Ask which.
• "Set in place." Setting is not anchoring, leveling, seismic restraint or the crane. Confirm each.
• "Terminations by others." Every termination needs a named party. On data centers, grounding and bonding is a frequent orphan: the electrical and low-voltage bonding scopes are often designed separately, and the gap between them has no owner.
• "Startup by manufacturer." The manufacturer may start the unit, but someone has to have it ready, attend, and fix what startup finds. That labor is the installer's unless the proposal says otherwise.
• "Assist with commissioning" or "support Cx as required." Without hours, crews or levels, this is a promise without a price. Ask which commissioning levels are included and how many re-test days.
• Storage "by owner" or "at owner's facility." Owner storage still needs someone to move the gear to the site, inspect it again and maintain batteries while it waits.

The same discipline applies to exclusions and qualifications in general. For the method, see how to review subcontractor exclusions and qualifications, and for the electrical items that recur on every job, common electrical bid exclusions.

Normalizing bids that are mostly labor

Once every cell has a status, the numbers can be compared. On an OFCI package, the labor behind each step matters more than the total.

Compare labor per row, not per package. Hours per generator set, per switchgear lineup and per UPS module let you see whether a low bidder is efficient or has left steps out. A bidder with half the hours per lineup either has a better method or priced fewer steps. The matrix tells you which.

Price the missing steps before ranking. For each silent or excluded cell, add either the bidder's own clarified price or the GC's carry for that step. Only then compare totals. The bidder who wrote down the fewest steps should not win for that reason. This is the difference between tabulating bids and leveling them.

Account for unfamiliar equipment. Owner-furnished gear is chosen by the owner, not the installer. A crew installing a vendor's equipment for the first time will not match its productivity on gear it knows. A bidder with experience on that owner's standard, and that vendor's product, may be pricing a real advantage rather than a thin number.

Respect the manufacturer's role. Some steps belong to the vendor under the owner's purchase order: factory tests, field startup, certain warranty obligations. The leveling sheet should record which cells the vendor covers, so no bidder is penalized for excluding the vendor's work and no one assumes the vendor covers the installer's.

Where OFCI leveling goes wrong

These are the failure modes that recur, and the step each belongs to.

Early delivery treated as good news (step 3). Equipment that arrives before its room is ready becomes a warehouse job: climate control, battery maintenance, re-inspection and damage risk at every move. A supply-chain practitioner writing in Data Center Frontier made the point that early arrival does not put a project ahead. Someone has to price the wait.

Late delivery with no lever (steps 2 to 4). When owner gear is late, the installer's crews stand by and the GC has no contract with the vendor to enforce. Whether that is compensable depends entirely on the prime contract. Pillsbury advises defining schedule relief and compensation for late or defective owner equipment in the agreement itself, and WilmerHale notes that late owner-furnished equipment can give rise to claims about the owner's responsibility.

Damage discovered after acceptance (step 2). If receiving inspection is nobody's scope, the unit is accepted by default, and damage found at startup has no clear owner.

Loose parts with no installer (step 5). Shipping splits, loose bus links and field-installed accessories fall between the vendor's scope and the installer's.

Commissioning labor nobody priced (steps 7 to 9). Every bidder assumed someone else would supply the crews for functional and integrated testing, and the load banks and fuel sit in no proposal at all.

Warranty voided by installation (step 10). If the vendor's warranty requires its technicians to witness certain connections and the installer did not carry that coordination, the risk returns to the owner, and then to the GC.

Carry the unresolved rows forward

A leveling sheet that ends at a recommended bidder leaves the hardest part undone. On an OFCI package, each unresolved cell should go somewhere specific:

• Into the subcontract exhibit: each included step for each owner-furnished item, in words, not "per proposal."
• Into the procurement schedule: the delivery windows the storage, rigging and crew loading were priced against, so a change in delivery is visible as a change in cost.
• Into the commissioning plan: named parties and hours for each level the installer supports.
• Into the GC's own proposal to the owner: a qualification for any step that remains the owner's or the vendor's.

Precon starts earning its fee here. The number is only as good as the responsibilities behind it. On an owner-furnished job, those responsibilities are the whole bid.

Where Piper fits

An owner-furnished package is a web of documents that have to agree with each other:

• the owner's equipment list and responsibility matrix;
• the one-line and the redundancy topology it implies;
• the commissioning requirements;
• the delivery dates;
• the wording of each proposal.

Leveling fails when that web lives in separate files and one estimator has to hold the connections in their head during bid week.

Piper is the AI operating system for preconstruction. It builds an understanding of the project from those documents, together with the company's own scope standards, and uses it to show where each proposal includes, excludes, qualifies or says nothing about each step for each owner-furnished item, with the sheet or clause behind every finding. When the owner's equipment list or delivery dates change, the same understanding shows which rows, bidders and commitments the change reaches. Estimators still decide the status, the adjustment and the carry.

Sources

• Construction Dive, Tips for owners and contractors on data center contracts (naming who procures, transports, offloads, installs, integrates and tests each system).
• Fenwick Elliott, Delay claims in data centre construction, part 1 (owner-furnished equipment and the contractor's lack of a vendor contract).
• Uptime Institute, Avoiding data center construction problems (owner procurement gaps and commissioning compression).
• Data Center Frontier, The equipment arrived early. That doesn't mean the project is ahead (storage and handling risk of early deliveries; sponsored content).
• Pillsbury, Data center construction contracting, and WilmerHale, Data centers in dispute (allocating schedule relief and compensation for owner-furnished equipment).
• Schneider Electric, White Paper 75, Comparing UPS System Design Configurations (how redundancy topology changes equipment counts).
• CxPlanner, Data center commissioning levels (the five commissioning levels).
• ANSI/TIA-607-E, via TIA (telecommunications bonding and grounding for customer premises).