Commissioning is scope: pricing L1–L5 in data center bids

On a data center, commissioning is not a closeout activity with an allowance attached. It is priced scope, with its own equipment, fuel, crews and a final test the contract dates are tied to. The cost that goes missing is rarely the commissioning agent's fee, which the owner usually carries. It is the contractor-side support at each of the five commissioning levels. That means the crews who stand by during tests, the load banks and fuel the tests run on, the manufacturer technicians billed by the day, and the re-test days when something fails. None of it appears in a subcontract bid unless someone names it.

This guide is for GC estimators and precon managers carrying electrical, mechanical and controls packages on data centers, typically under a negotiated GMP or design-build agreement for a hyperscale or colocation owner. It assumes the owner retains an independent commissioning agent (CxA). Where the GC holds the commissioning agent role itself, as on some design-build contracts, add that scope on top. On ordinary commercial buildings commissioning participation is usually much lighter; for those packages see the commissioning items in HVAC scope gaps and double-ups and common electrical bid exclusions.

What commissioning has to prove on a data center

On an office building, commissioning verifies that systems meet the owner's requirements. On a data center it has a harder job. It has to prove that the redundancy works: that a generator, a UPS module or a chiller can fail or be taken out for maintenance while the IT load keeps running. Uptime Institute's Tier Standard describes the target as concurrent maintainability at Tier III and fault tolerance at Tier IV. Commissioning is how the owner finds out whether the building actually achieves it.

That changes the size of the job. The final test, the integrated systems test (IST), runs every system together at design load, usually on rented load banks standing in for the servers. It then deliberately drops the utility to watch the generators, transfer equipment, UPS and cooling respond. It is a staged failure of the whole building, rehearsed and repeated until it passes.

The five levels and who carries each

Commissioning runs in five levels. Terms and boundaries vary slightly by owner, so read the project's commissioning plan, but the sequence is consistent across published guidance.

Two things stand out in that table. The contractor's share grows at every level. And Level 5 is the one level where every trade has to be on site at the same time, which makes it the most expensive day on the project to repeat.

Where the cost goes missing

These are the items that most often sit in no one's number. Each needs a named owner before the carry is set.

Load banks. Rental, delivery, cabling, connection points and the technician to run them. Load banks stand in for IT load during Level 4 and Level 5 testing. Their size and quantity follow the hall's design load, and the connection points need to exist in the permanent design or be added.

Test fuel. Generators run for hours during functional and integrated testing, then have to be refilled so the owner receives a full fuel system. Uptime Institute's case notes include a job where commissioning windows were so compressed that generators never ran long enough to drain their day tanks, so fuel-system faults went unseen until later. Adequate run time costs fuel. Skipping it costs more.

Temporary power and cooling for testing. When permanent utility power arrives in phases, early testing may need temporary generation or cooling. That is separate from the load banks and is frequently assumed to be someone else's.

Manufacturer field technicians. Owner-furnished switchgear, UPS, generators and cooling units usually come with factory startup under the owner's purchase order. Additional field days for functional testing, re-tests and troubleshooting are often billed separately. If the installer's proposal says "startup by manufacturer," confirm who pays for the days after startup.

Standby crews. During Level 4 and Level 5, electricians, pipefitters and controls technicians stand by to operate equipment, reset breakers, correct findings and support the test script. Those are crew-days, not an allowance.

Re-test days. When a test fails, the day repeats: load banks, fuel, crews, manufacturer technicians and the CxA's team. One commissioning software vendor has published an example of a single re-test day costing about $27,800. Treat it as one illustration of scale, not a benchmark. The honest answer is that there is no independent data on how many re-test days a data center needs, which is exactly why the number should be explicit.

Documentation. Torque logs, insulation resistance results, thermographic scans, test reports and turnover packages. On data centers these are required evidence, and producing them takes office and field hours.

Controls integration. The building management system, the electrical power monitoring system (EPMS) and the owner's monitoring platform are often separate vendors under separate contracts. Point-to-point verification between them is commissioning work that frequently belongs to no single package.

What subcontractor proposals usually say

Commissioning language in proposals is short, and short language on this scope is where the money hides.

• "Includes startup of our equipment." Startup is Level 3. It says nothing about Levels 4 and 5.
• "Assist with commissioning" or "support Cx as required." Without levels, crews or hours, this is a promise without a price.
• "One mobilization for commissioning." Phased hall turnover means several commissioning campaigns, not one.
• "Excludes load banks, fuel and temporary power." Reasonable, but then the GC has to carry them.
• "Commissioning support per the schedule." Tie it to a specific schedule revision. A later schedule with more test windows is a change.

Read each against the commissioning specification and the owner's commissioning plan, not against the other bidders. The method is the same one used for any exclusion and qualification review. On data centers the commissioning line is simply larger.

Price commissioning by level, not as a percentage

A percentage allowance for commissioning hides the decisions that drive its cost. Build it up instead:

1. Start from the commissioning plan and the equipment list. List every system that will be tested at each level, by hall or phase.
2. Name the executor for each cell. Manufacturer, installing subcontractor, GC, CxA or owner. Where the contract is silent, record the gap.
3. Count crew-days and equipment for the contractor's cells. Crews by trade, load bank capacity and days, fuel quantity, temporary power, manufacturer field days beyond startup.
4. Carry re-tests as a named number. A defined number of re-test days per level is reviewable. An unstated cushion is not.
5. Attach it to the schedule. Each campaign has a window. If windows shift, the cost follows, and the connection should be visible.

This ties directly to how owner-furnished equipment is leveled. Steps seven through nine of the owner-furnished equipment leveling method are Levels 3 through 5 seen from the installer's side. Those cells, and the commissioning build-up, should agree.

Why commissioning is where the delay lands

Commissioning sits at the end of the schedule, so it absorbs every slip upstream: late gear, late utility power, late cooling water, late network. Data Center Knowledge has described the trap in phased energization. Teams do only the minimum testing needed to energize a hall and leave deeper testing for later, where it collides with the next phase.

On phased hyperscale and colocation work, Fenwick Elliott notes that a delay in one data hall can spread to others through shared plant, shared containment and shared test equipment. Contract practice raises the stakes. Firms advising on data center contracts, including Pillsbury and Bracewell, recommend tying liquidated damages to energization, integrated testing and each hall's handover rather than to one completion date. A commissioning campaign that slips can therefore trigger damages on more than one milestone.

For precon, that means carrying commissioning per hall where turnover is phased, and reading exactly which commissioning milestones carry damages before setting the re-test allowance. For how those milestones connect to procurement dates and the rest of the estimate, see on a data center, the schedule is part of the estimate.

Failure modes to check before the carry

• Commissioning priced as a closeout percentage with no level-by-level basis
• Load banks, fuel and temporary power excluded by every bidder and carried by no one
• Manufacturer field days beyond startup assumed to be in the owner's purchase order
• One commissioning mobilization priced for a job with phased hall turnover
• Controls integration between BMS, EPMS and the owner's platform left between packages
• A re-test allowance that exists only as an unstated cushion
• Test windows in the schedule shorter than the test script needs, so testing is cut instead of priced

Where Piper fits

Commissioning cost depends on documents that are rarely read together: the commissioning specification, the owner's commissioning plan, the equipment list, the one-line, the schedule and the wording of every mechanical, electrical and controls proposal. A change to any one of them moves the others. A new phase boundary changes the number of campaigns. A late switchgear delivery compresses a test window. A controls vendor change moves an integration point.

Piper is the AI operating system for preconstruction. It builds an understanding of the project from those documents and the company's own standards. It uses that understanding to show which commissioning responsibilities each proposal includes, excludes or never addresses, level by level, with the clause behind each finding. When the schedule or the equipment list changes, the same understanding shows which commissioning cells and carries the change affects. The team still decides what to carry and how much risk to price.

Sources

• Uptime Institute, Explaining the Uptime Institute's Tier Classification System and Avoiding data center construction problems (concurrent maintainability, and commissioning compression in practice).
• CxPlanner, Data center commissioning levels (the five commissioning levels).
• Anvilfield, Integrated systems test commissioning (IST at design load with utility loss simulated).
• Aggreko, Data centre commissioning (load banks for generator and integrated testing).
• Archdesk, Data center commissioning levels (vendor example of re-test day cost; illustrative only).
• Data Center Knowledge, What is phased energization (minimum testing to energize).
• Fenwick Elliott, Delay claims in data centre construction, part 1 (commissioning delays and phased handover).
• Pillsbury, Data center construction contracting, and Bracewell, Managing contractual risk in data center construction (milestone-based liquidated damages).
• ASHRAE, Guideline 0, The Commissioning Process (commissioning as verification against owner requirements).