Data center bid review: work through a shared scope omission

Follow a fictional data center bid review from a shared exclusion to a documented scope owner, clarification and carry decision.

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. Read the requirement before ranking the offers
  2. Build a common-basis review matrix
  3. Resolve ownership before changing the carry
  4. Review your package with Piper

Before carrying a mechanical number on a data center package, the chief estimator needs to know whether the combined proposals cover the project requirement, not just whether the two mechanical bidders have priced the same things. Matching exclusions can make offers look comparable while leaving the same required work outside both prices.

The fictional review below shows how to trace that problem through a requirement and three offers, then keep the decision open until the right party and price are confirmed. Piper bid leveling compares bids against project scope with source-linked findings; the estimating team reviews those findings and decides the carry. This example illustrates the method, not an actual Piper run or customer project.

Read the requirement before ranking the offers

Assume a GC is preparing a data center mechanical package for a carry decision. All document names, wording, revisions and amounts below are invented for this example. They are not excerpts from a real project. The team has three kinds of source material: a project requirement, two competing mechanical offers, and a separate controls offer.

The fictional commissioning scope, Revision B, issued with the bid package, requires mechanical startup and mechanical personnel attendance at two subsequent integrated functional test sessions. It also requires the cooling equipment status point to be integrated with the controls system and demonstrated during those sessions. The requirement does not establish which subcontract must carry the controls integration. The two sessions are an illustrative scope boundary, not an industry standard.

The fictional offers, all submitted against Revision B, say:

  • Mechanical A: base bid of $1,000,000. Includes equipment startup. Attendance at integrated functional tests is excluded; controls integration is by others.
  • Mechanical B: base bid of $1,030,000. Includes equipment startup. Attendance at integrated functional tests is excluded; controls integration is by others.
  • Controls C: base bid of $200,000. Includes controls work generally but explicitly excludes integration of the cooling equipment status point.

First compare Mechanical A with Mechanical B. Both expressly include startup and exclude the later attendance and controls integration. On these stated scope items, A is $30,000 lower. That comparison alone does not establish a complete mechanical carry or a final award recommendation: the remainder of each offer, qualifications and commercial terms still need review.

Now compare the selected mechanical offer and Controls C with Revision B. Startup is included in either mechanical alternative. Neither mechanical offer includes the later attendance, and Controls C expressly excludes the named integration point. The requirement calls for both. The controls exclusion is material because “by others” in the mechanical offers does not prove that anyone else accepted the work. The GC has two unresolved scope items even though the mechanical offers match each other.

The GSA Commissioning Guide, September 2020, describes commissioning responsibilities and team participation for GSA projects and calls for project-specific commissioning requirements in the relevant statements of work and specifications. It distinguishes activities such as startup and functional testing. It does not allocate this fictional package or establish its price. The project documents and agreed subcontract boundaries govern this review.

Build a common-basis review matrix

Use one row per required activity and keep the source boundary visible. The following register can be copied into a bid review and expanded with actual document references. “Proposed” means a question to put to a bidder, not an assignment already accepted.

Required item and sourceMechanical A / BControls CProposed owner and price statusReview decision
Startup of cooling equipment, Revision BBoth explicitly include in their respective base bidsNot needed to establish this inclusionSelected mechanical bidder; included in its base, subject to full proposal reviewConfirm selected offer and retain its source
Mechanical attendance at two later sessions, Revision BBoth explicitly excludeNot established by this offerAsk selected mechanical bidder for an itemized addition; price unresolvedOpen; estimator to approve scope and carry
Integrate and demonstrate cooling status point, Revision BBoth defer controls integration by othersExplicitly excludes that pointAsk Controls C for an itemized addition and identify any mechanical support; price unresolvedOpen; estimator to approve boundaries and carry

This table separates the required activity from the offer's response to it. It also avoids treating silence as an inclusion. For a real package, cite the exact page or section, revision, date and proposal attachment beside each entry. Check addenda acknowledgments and any clarification that supersedes an earlier qualification. If a bidder has priced a different revision, resolve the basis before comparing its number with an offer on the current set.

The two mechanical offers are alternatives. The GC would ordinarily carry the selected mechanical base once, not both A and B. In this illustration, the initial combined base using A is $1,200,000: $1,000,000 for A plus $200,000 for Controls C. That amount includes A's stated startup once. It does not price the excluded attendance or integration point. Do not add a separate startup allowance merely because both competing offers include it, and do not count both mechanical base bids as overlapping project work.

The controls base covers controls work generally, but the explicit point exclusion limits what can be treated as covered. An addition for that point should state its boundary against the existing controls base. If a proposed addition also includes startup or another already included task, obtain a breakout and agree the overlap before adding it. These checks prevent double-counting; they do not prove that the rest of either proposal is complete.

Resolve ownership before changing the carry

Send the same scope description and Revision B reference to the relevant bidders. Request written responses that identify the included work, exclusions, price, conditions and the document revision used. Useful questions for this example are:

  1. To Mechanical A and B: Does your base include a mechanical representative at both specified integrated functional test sessions after startup? If not, provide a separate price for that attendance, including your stated assumptions and any limit on return visits.
  2. To Controls C: Does your base include integration and demonstration of the cooling equipment status point? Your offer excludes it. Provide a separate price and define the boundary between that addition and your base controls work.
  3. To the proposed mechanical and controls parties: What support do you require from the other party for the point demonstration, and is that support included in your price? Identify any overlap and any remaining exclusion.
  4. To the project team: Does Revision B remain the governing scope, and is there a later addendum or written direction affecting these two sessions or the point? Resolve conflicting documents through the project's normal clarification process.

Do not assign the integration point solely because a firm is called the controls contractor, or attendance solely because a bidder is mechanical. Those are sensible parties to ask in this fixture, not proof of a contractual obligation. If the selected party cannot take the work, identify another proposed owner and obtain its scope and price. If the requirement itself is ambiguous, seek a design or owner clarification before treating an assumption as settled.

When responses arrive, update the register separately: the proposed owner, the confirmed written inclusion, the price and conditions, and the person approving the carry. Link the response to the original exclusion and requirement. A verbal expectation or an unpriced promise is not the same as a confirmed inclusion at an agreed price.

For example, if Mechanical A later offers a separately priced attendance addition and Controls C offers a separate point integration addition, review their boundaries and any support from the other trade. Only after the estimator accepts those terms should the team add the approved amounts to the relevant base. If either price is still unknown at bid time, show it as unresolved and document the team's interim carry decision and assumptions. This example supplies no invented plug or market rate, so the final evaluated amount cannot yet be calculated.

The broader construction bid leveling guide covers the comparison process. For the related decisions, see data center commissioning scope in sub bids and data center subcontractor bid coverage.

Review your package with Piper

For a source-linked review on an actual package, bring the applicable drawings and specifications, commissioning requirements and revisions, trade scope sheets, proposals and attachments, addenda, and written clarifications. Piper bid leveling compares subcontractor bids with project scope and links findings to their sources. The estimating team can inspect those sources, resolve the trade boundaries and decide what to carry or award.

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.