15.2 Construction Administration: Submittal Reviews, Requests for Information, and Change Orders

15.2 Construction Administration: Submittal Reviews, Requests for Information, and Change Orders

Once the design phase of a mission-critical data center concludes and trade subcontracts are awarded, the project transitions into Construction Administration (CA). During this phase, the Data Center Design Consultant and the multi-disciplinary Architect/Engineer (A/E) team shift from system design to administrative oversight, quality verification, and contract enforcement.

In standard commercial construction, minor deviations in piping routing or electrical panel locations rarely threaten building operations. In contrast, in a mission-critical data center, an unapproved component substitution, an unverified busway clearance, or an unchecked protective relay setting can compromise concurrent maintainability, trigger catastrophic arc-flash incidents, or cause thermal runaway across thousands of server cabinets. Rigorous construction administration protocols are the primary defense against operational failure.

---

The Construction Administration Framework

Construction administration is governed by the contract, usually built on standard forms such as AIA Document A201 (General Conditions of the Contract for Construction) and EJCDC C-700 (Standard General Conditions of the Construction Contract). Terms differ slightly: for example, EJCDC calls a construction change directive a "Work Change Directive."

Under these standard agreements, the consultant serves as the owner's professional technical advisor. The primary objectives of construction administration include:

1. Verifying that the physical work conforms to the approved construction drawings, specifications, and the Basis of Design (BOD).
2. Reviewing and processing contractor technical submittals, shop drawings, and engineering calculations.
3. Responding to contractor Requests for Information (RFIs) to clarify ambiguities and resolve field interferences.
4. Auditing Proposed Change Orders (PCOs) and issuing Construction Change Directives (CCDs) to control costs and protect the project schedule.
5. Safeguarding the owner's capital investment and contingency reserves against unwarranted contractor claims.

---

The Technical Submittal Review Process

The submittal review process is the critical administrative gateway through which every piece of equipment, fabrication drawing, and building material must pass before it is procured, fabricated, or installed on site. Submittals confirm that the contractor and its suppliers correctly understand the contract documents.

+-----------------------------------------------------------------------------------------+
|                               SUBMITTAL REVIEW LIFECYCLE                                |
|                                                                                         |
|  +--------------------+       1. Transmit       +-----------------------+               |
|  |  Trade Contractor  +------------------------>+   General Contractor  |               |
|  |  (Supplier / OEM)  |                         | (Quality Review Stamp)|               |
|  +--------------------+                         +-----------+-----------+               |
|           ^                                                 |                           |
|           | 6. Resubmit                                     | 2. Formal Transmission    |
|           |    (If Required)                                v                           |
|  +--------+-----------+                         +-----------+-----------+               |
|  |  A/E Review Action |                         |    Lead Consultant    |               |
|  |  Stamp Assigned    |                         |      / Architect      |               |
|  +--------+-----------+                         +-----------+-----------+               |
|           |                                                 |                           |
|           | 5. Return Processed Submittal                   | 3. Discipline Routing     |
|           v                                                 v                           |
|  +--------------------+                         +-----------+-----------+               |
|  | General Contractor |                         | Discipline Engineers  |               |
|  | & Subcontractor    |<------------------------+ (Elec / Mech / Telecom|               |
|  | (Action Authorized)|       4. Technical      +-----------------------+               |
|  +--------------------+          Review                                                 |
+-----------------------------------------------------------------------------------------+

Primary Categories of Data Center Submittals

1. Shop Drawings: Detailed, dimensioned fabrication drawings generated by trade contractors, fabricators, or manufacturers. Examples include:
   • Structural steel framing assemblies for elevated rooftop chiller platforms.
   • Modular electrical power skids showing layout clearances, seismic snubbers, and transformer conduit entry points.
   • Mechanical pipe spool drawings showing prefabricated welded joints for 30-inch chilled water supply/return headers.
   • Telecommunications pathway layouts detailing multi-tier overhead cable conveyance, trapeze supports, and seismic bracing.
2. Product Data Cut-Sheets: Manufacturer technical brochures, performance curves, and catalog specification sheets. The contractor must highlight specific model numbers, voltage ratings, full-load amps (FLA), Short-Circuit Current Ratings (SCCR), Underwriters Laboratories (UL) listings, and seismic certifications.
3. Engineering Calculations & Specialty Studies: Contractor-provided engineering analyses required by the project specifications, such as:
   • Electrical short-circuit, protective device coordination, and arc-flash incident energy studies per IEEE 1584 and NFPA 70E.
   • Structural and mechanical seismic anchorage calculations stamped by a registered professional engineer (PE).
   • Hydronic pumping head loss and thermal expansion loop stress calculations.
4. Physical Material Samples: Actual physical samples submitted for architectural and engineering evaluation, such as raised access floor panels (evaluating static dissipative laminate finishes and concentrated load ratings), clean-agent fire suppression pipe coatings, and architectural acoustic louvers.
5. Factory Acceptance Test (FAT) Reports & Certifications: Mill test reports for structural steel, dielectric insulation test records for medium-voltage transformers, and factory load-bank test data for standby diesel generators.

A/E Review Action Stamps and Legal Liabilities

When the design consultant or engineer of record reviews a submittal, they append a formal review stamp selecting one of several dispositions defined in the project specifications:

---

Requests for Information (RFI) Management

A Request for Information (RFI) is a formal, auditable communication vehicle used by contractors during construction to seek written clarification regarding drawing ambiguities, specification conflicts, constructability issues, or unforeseen field conditions.

Formal Workflow and Chain of Custody

To maintain contractual discipline, RFIs must follow an established chain of communication:

1. The trade subcontractor (e.g., the electrical trade) drafts an RFI describing the issue, referencing specific drawing and specification sections, and proposing a potential solution.
2. The General Contractor reviews the RFI to confirm that the answer cannot be found in the contract documents, filters out redundant inquiries, and formally logs and transmits it to the Lead Consultant/Architect.
3. The Architect routes the RFI to the appropriate discipline Engineer of Record (e.g., Electrical or Telecommunications DCDC).
4. The Engineer conducts technical evaluations, coordinates with impacted disciplines, and provides a concise, unambiguous written response, often accompanied by a revised sketch or detail.
5. Response windows are set by the contract. Commercial projects commonly allow 7 to 14 calendar days, while mission-critical fast-track projects often require a 3 to 5 business day turnaround, with critical-path issues answered within 24 to 48 hours.

Root Causes and Warning Indicators

RFIs arise from distinct project conditions:

• Design Ambiguities or Document Conflicts: A discrepancy between architectural reflected ceiling plans and mechanical duct routing drawings.
• Unforeseen Site Conditions: Discovery of an unmapped municipal underground utility duct bank during foundation trenching.
• Constructability / Detailing Gaps: Inadequate physical clearance to route a 4,000A electrical busway between structural steel beams and overhead chilled water headers.
• Contractor Substitution Requests: Inquiries attempting to substitute an alternate manufacturer due to unexpected factory lead time delays.

+-----------------------------------------------------------------------------------------+
|                     RFI ROOT-CAUSE DISTRIBUTION (ILLUSTRATIVE EXAMPLE)                  |
+--------------------------------+--------------------+-----------------------------------+
| Category                       | Typical Share (%)  | Primary Mitigation Strategy       |
+--------------------------------+--------------------+-----------------------------------+
| Inter-Discipline Clashes (MEP) | 35% - 45%          | Pre-construction 3D BIM (LOD 350) |
| Specification Contradictions   | 20% - 25%          | Rigorous QA/QC cross-checking     |
| Unforeseen Field Conditions    | 15% - 20%          | Comprehensive geotechnical & radar|
| Contractor Scope Clarifications| 10% - 15%          | Detailed pre-bid scope conferences|
| Equipment Substitution Queries | 5% - 10%           | Performance-based OFCI procurement|
+--------------------------------+--------------------+-----------------------------------+

Tracking RFI metrics is a primary method for assessing project health. An unusually high RFI volume for the project's size (for example, well over a thousand RFIs on a mid-size data center build) signals inadequate pre-construction document coordination and frequently precedes major contractor delay claims.

---

Change Order Management & Financial Control

In construction administration, changes to the contract scope, price, or schedule are inevitable. However, uncontrolled changes—frequently termed "scope creep"—represent the greatest threat to a project's financial contingency and delivery milestones. A disciplined administrative hierarchy governs how changes are proposed, directed, and approved:

+-----------------------------------------------------------------------------------------+
|                             CHANGE DOCUMENTATION HIERARCHY                              |
|                                                                                         |
|  +-----------------------------------------------------------------------------------+  |
|  | 1. POTENTIAL CHANGE ORDER (PCO) / CHANGE ORDER REQUEST (COR)                      |  |
|  | Contractor's notification of scope, cost, or schedule impact resulting from an   |  |
|  | RFI, field condition, or owner design adjustment.                                 |  |
|  +-----------------------------------------+-----------------------------------------+  |
|                                            |                                            |
|                     +----------------------+----------------------+                     |
|                     | (Pricing Disputed /                  | (Pricing Agreed /          |
|                     |  Schedule Critical)                  |  Routine Work)             |
|                     v                                             v                     |
|  +-----------------------------------+   +-------------------------------------------+  |
|  | 2. CONSTRUCTION CHANGE DIRECTIVE |   | 3. PROPOSED CHANGE ORDER ACCEPTANCE       |  |
|  |    (CCD)                          |   | Consultant audits labor rates, material   |  |
|  | Unilateral order signed by Owner  |   | invoices, and schedule float impact.      |  |
|  | & A/E to proceed immediately      |   +---------------------+---------------------+  |
|  | without delay.                    |                         |                        |
|  +------------------+----------------+                         |                        |
|                     |                                          |                        |
|                     +----------------------+-------------------+                        |
|                                            |                                            |
|                                            v                                            |
|  +-----------------------------------------------------------------------------------+  |
|  | 4. FORMAL CHANGE ORDER (CO)                                                       |  |
|  | Legally binding contract amendment signed by Owner, General Contractor, and A/E,   |  |
|  | modifying the Contract Sum and/or Contract Time.                                  |  |
+-----------------------------------------------------------------------------------------+

1. Potential Change Order (PCO) / Change Order Request (COR)

A PCO is the contractor's formal submittal claiming that an RFI response, field bulletin, or unforeseen site condition falls outside the baseline contract scope and will require additional compensation, a contract time extension, or both.

2. Construction Change Directive (CCD)

A Construction Change Directive (governed by AIA Document G714) is a unilateral written order signed by the Owner and Architect directing the contractor to proceed immediately with a required change in the work, even when the parties have not yet agreed upon the cost or schedule adjustment.

• Mission-Critical Purpose: In a fast-track data center, pausing work along the critical path to negotiate a $40,000 piping reroute could delay project completion by weeks, triggering $100,000/day tenant liquidated damages. A CCD enables work to proceed immediately while commercial negotiations and audits continue in the background.
• Payment Basis: If pricing is not resolved up front, work executed under a CCD is reimbursed based on documented time and materials (force account), including actual verified labor hours, equipment rentals, material invoices, and contractual markup caps.

3. Formal Change Order (CO)

A formal Change Order (governed by AIA Document G701) is a bilateral, legally binding amendment to the construction contract. It requires the signatures of all three primary parties: the Owner, the General Contractor, and the Architect/Engineer. It establishes the final agreed adjustment to the Contract Sum and the Contract Time.

Auditing Change Proposals

The DCDC consultant must rigorously audit contractor change proposals to prevent inflated claims:

1. Labor Rate Verification: Cross-referencing claimed labor rates against prevailing wage statutes or agreed contractual master labor schedules. Auditing must eliminate unauthorized compounding of labor burden, payroll taxes, and overhead.
2. Material and Rental Invoicing: Mandating third-party subcontractor invoices and material receipts rather than flat estimated lump sums.
3. Overhead and Profit (OH&P) Markups: Contractually capping markups. Agreements commonly allow about 10% to 15% on self-performed work and a reduced markup (often about 5%) on work performed by lower-tier subcontractors.
4. Time Impact Analysis (TIA): If the contractor requests a schedule extension, they must submit a Time Impact Analysis using the project's Critical Path Method (CPM) baseline schedule. If the delay is absorbed by available float and does not push out the critical path, no contractual time extension is warranted.

Contingency Budget Management

Every data center project maintains an Owner's Project Contingency to absorb legitimate unforeseen costs. Consultants track contingency health using the following formula:

$\text{Contingency}_{\text{Remaining}} = \text{Contingency}_{\text{Initial}} - \sum \text{Approved COs} - \sum (\text{Pending PCOs} \times P_{\text{approval}})$

Where $P_{\text{approval}}$ represents the estimated historical probability of claim validation (typically modeled between 0.50 and 0.80 based on preliminary merit review).

---

Minimizing Scope Creep: 3D BIM Clash Detection

The most effective defense against change orders is pre-construction spatial coordination utilizing Building Information Modeling (BIM).

Data centers exhibit extraordinary spatial density above whitespace ceilings and within perimeter mechanical galleries. A single gallery corridor must accommodate:

• 30-inch to 36-inch chilled water supply and return headers.
• Dual 4,000A low-impedance sandwich electrical busways.
• Pre-action and wet-pipe sprinkler mains.
• Multi-tier overhead wire basket trays and optical fiber raceways (e.g., FiberRunner).
• Building Management System (BMS) and electronic security conduits.

+-----------------------------------------------------------------------------------------+
|                        BIM LEVEL OF DEVELOPMENT (LOD) PROGRESSION                       |
+---------+--------------------+----------------------------------------------------------+
| LOD     | Model Status       | Data Center Engineering Application                      |
+---------+--------------------+----------------------------------------------------------+
| LOD 200 | Schematic Design   | Approximate spatial volume, spatial massing, gray/white  |
| LOD 300 | Design Documents   | Specific system sizes, duct routing, major switchgear    |
| LOD 350 | System Interfaces  | Multi-trade coordination, clearances, wall penetrations  |
| LOD 400 | Fabrication Ready  | Spool drawings, hanger rod locations, seismic bracing    |
| LOD 500 | Field Verified     | Final As-Built operational digital twin for facilities   |
+---------+--------------------+----------------------------------------------------------+

By mandating that trade contractors model installations at LOD 350 and LOD 400, the project team runs automated collision detection software (e.g., Autodesk Navisworks or BIM 360) during the pre-construction phase. Resolving 500 spatial clashes virtually in a digital model costs a small fraction of fixing them in the field; resolving those same clashes after pipe and busways have been fabricated can cost hundreds of thousands of dollars in demolition, re-ordering, and delay change orders. (BIMForum's LOD Specification defines LOD 100 to 400; LOD 500, field-verified as-built, comes from AIA's BIM protocol documents.)

---

Practical Design Scenario: The Gallery Busway Collision

The Field Conflict

During the fit-out of an electrical gallery serving a 12 MW enterprise data hall, the electrical trade contractor discovers that an overhead 4,000A, 480V sandwich busway directly collides with a 24-inch condenser water pipe header. The mechanical piping was installed two weeks earlier strictly according to mechanical sheet M-204.

Contractor Action

The electrical contractor files RFI-142 and follows with Proposed Change Order PCO-088, requesting $220,000 to reroute the busway using custom factory-engineered elbows, alongside a claimed 4-week project time extension.

The Consultant's Construction Administration Response

1. BIM Model Audit: The consultant re-examines the approved LOD 350 coordination model. The audit reveals that the mechanical contractor deviated 8 inches downward from their approved model coordinates to avoid a structural beam clamp, without submitting an RFI or obtaining engineering approval.
2. Schedule Float Analysis: The consultant reviews the CPM master schedule. Condenser water piping installation on that branch possesses 22 calendar days of total float, whereas the 4,000A busway sits directly on the primary critical path.
3. Rejection of Nonconforming Work: Because the piping deviates from the approved coordination model, the architect rejects it as nonconforming, and the owner directs the general contractor to have it corrected at no cost to the owner under the contract's correction-of-work provisions (AIA A201 §12.2). The mechanical subcontractor lowers two pipe spools back to the approved coordinates. A CCD is not the right tool here, because a CCD orders a change in the work for an adjustment yet to be agreed, not correction of defective work.
4. Outcome: The busway installation proceeds without modification. PCO-088 is rejected in its entirety, saving the owner $220,000 and preventing a four-week critical-path delay.

---

Common Exam Traps & DCDC Pitfalls

• Misinterpreting "Approved as Noted": A frequent exam trap suggests that an "Approved as Noted" stamp requires the contractor to resubmit the drawings. This is incorrect. The contractor is authorized to proceed with fabrication immediately, provided the specific annotations are incorporated. Resubmittal is only mandatory under "Revise and Resubmit" or "Rejected."
• Backdoor Substitutions via RFIs: Contractors sometimes use RFIs to casually request product substitutions (e.g., "Manufacturer X is out of stock; can we use Manufacturer Y?"). A design consultant must never approve major equipment substitutions through an RFI response. Substitutions must be processed through the specification's formal substitution request procedure, verifying compliance with the Basis of Design.
• Authority of Construction Change Directives (CCD): Remember that a CCD does not require contractor signature to be contractually enforceable. It is a unilateral instrument signed by the Owner and Architect/Engineer to compel immediate work and protect the critical path.
• Conflating Submittal Approval with Dimensional Responsibility: An engineer's approval stamp never indemnifies the contractor for field measurement errors. If a prefabricated busway run is 6 inches too short because the contractor failed to verify field dimensions between column gridlines, the financial liability rests 100% with the contractor.