Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
RFS (Ready for Service) is the contract-defined point when a data hall is accepted as ready to support customer IT - not when construction ends. I start with three checks: what capacity must be ready, what tests and records are required, and who can approve acceptance.
Before sign-off, your team needs to confirm:
Passing tests alone does not establish RFS. <u>The contract controls acceptance</u>, along with any links to handover, service start, and billing.
I’ll cover those checks, the testing and approval process, and how to plan the schedule and staffing for each hall or capacity block.
Data Center RFS: From Readiness to Acceptance
Use the RFS matrix as a contract-specific checklist. Turn each requirement into a readiness check tied to the contracted IT load in MW, not total utility capacity or future expansion. Define operating modes, environmental limits, and redundancy for that load. A check supports RFS sign-off only if the contract requires it, the results meet acceptance criteria, and the authorized party accepts them.[4][7]
The table outlines the minimum checks. The sections below explain what each requires in practice.
Confirm that permanent utility service - or an accepted alternate supply - is working. Verify switchgear, transformers, generators, UPS, transfer gear, distribution, grounding, and protection settings. Cooling must support the agreed IT load, not just pass startup checks. Use calibrated instruments to record temperatures in °F at agreed points. Assess performance against design conditions, not the weather on test day.[4][6][9]
Test redundancy under the specified utility-loss, equipment-failure, controls-loss, and maintenance-isolation scenarios. Check transfer times, remaining capacity, environmental limits, and recovery to stable operation. For the building management system (BMS) and electrical power monitoring system (EPMS), verify sensor accuracy, time synchronization, communications stability, alarm routing, and restoration after network failure. Having spare equipment installed does not prove redundancy works.[4][7]
Operating procedures and support systems must also be ready; passing technical tests is not enough.
Verify required water systems, leak detection, fire protection, emergency lighting, security, access control, telecom, and fiber paths. Operators need approved operating, maintenance, emergency, switching, isolation, and back-out procedures - not just equipment manuals.[5][8]
Before the construction team withdraws, confirm trained shift coverage, competency checks, physical and electronic permissions, vendor contacts, response commitments, spare-parts information, warranties, and maintenance plans.[5][8]
Leave only contract-approved minor punch-list items that do not affect safe operation, performance, maintainability, or service start. For each accepted exception, record its description, risk, owner, due date, operating restriction, mitigation, and formal approval. Contractual acceptance cannot waive statutory safety or occupancy requirements.[4][7]
Once readiness criteria are defined, back them up with test evidence and signed records. Commissioning produces the evidence; RFS requires acceptance by the contract-designated representative.[1][12]
Follow this evidence sequence: factory acceptance testing (FAT); delivery, storage, and receiving inspections; installation inspections; pre-functional checks; manufacturer startup; functional performance testing; failure-and-recovery testing; and integrated systems testing (IST).[1][10]
Write functional test scripts from approved sequences of operation. IST should verify normal, maintenance, manual (where permitted), emergency, and failure modes. Cover utility loss, UPS/generator transitions, cooling failure, controls-network loss, and recovery.[11][12][13]
Set load-bank conditions before testing: load locations, staging, duration, voltage/frequency limits, and thermal conditions. Record measured values, alarms, transfers, and operator actions. When a test fails, log the failure, correct it, and repeat the affected script. Also test connected functions to check for unintended changes.[11][12][13]
Build a requirements-to-records index rather than burying evidence in a certificate folder. Link each criterion to the exact document revision, test step, measured result, reviewer, and approval date. Keep raw trends and alarm histories alongside summaries so operations has a performance baseline after handover.[1] Assign named reviewers to that evidence and identify one accepting authority.
Technical verification, statutory approval, and contractual acceptance are separate decisions. Assign these roles in the commissioning plan and contract. The table below shows a typical division of responsibilities. The final acceptance record must list accepted capacity, effective date/time, exclusions, approved exceptions, and the person authorized to sign.
Put RFS gates into the schedule so each party knows when its testing, review, or acceptance is due.
Once RFS criteria are set, work backward from the contractual acceptance date - not physical completion. Connect utility availability, controls integration, testing, permit closeout, documentation, training, and customer reviews in the schedule. Leave time for corrections, retesting, and review.
Track blockers separately from closeout tasks. Use a readiness dashboard to show critical deficiencies, retest dates, missing records, pending approvals, and customer actions. Schedule customer onboarding and service activation after RFS acceptance, tied to the accepted RFS date.
Shared utility, cooling, fuel, and monitoring systems can put already-accepted capacity at risk. Define RFS for each hall, pod, or capacity block. Before a new phase goes live, verify shared-system isolation boundaries, alarm routing, maintenance access, and change-control procedures.
Each gate also needs a leader who owns it.
Keeping the schedule on track takes people who have delivered RFS before. Project executives and project managers own gate timing, commercial decisions, and delivery coordination. Commissioning leaders own evidence coordination, while MEP leaders, controls specialists, and field supervisors coordinate system readiness. Operations leaders own readiness to run. Schedulers and cost professionals track dependencies and recovery resources.
Bring commissioning and controls leaders in before design freeze. Keep turnover personnel and operations representatives involved in handover review.
Screen candidates against the exact RFS milestone they delivered. Ask what they owned, how much capacity reached RFS, what failed during integrated testing, how they managed corrective work and retesting, and what evidence closed acceptance. Request anonymized readiness dashboards, deficiency logs, or turnover indexes. Ask how they coordinated operators and resolved exceptions. Verify experience; a job title alone does not prove RFS capability.
Completion does not equal RFS. RFS is the contract-defined acceptance point when a specified hall or capacity block has proven its power, cooling, redundancy, and integrated performance for IT operations.[3][20]
The proof comes from commissioning evidence and turnover records.[16][17][19] Before sign-off, close blocking defects, document approved exceptions with an owner and due date, and complete the required package covering operators, procedures, approvals, and turnover.[2][15][16][17][19]
Once the evidence is complete and blocking exceptions are closed, the person authorized by the contract to sign should review the scope, capacity, effective date, exclusions, and service start conditions. Only then should they grant RFS, making verified readiness an accepted operating milestone.[14][15][18]
Substantial completion concerns the building’s physical condition. Ready for Service (RFS) confirms that the facility is ready to run. A project can reach substantial completion even if commissioning or documentation gaps remain.
RFS requires completed commissioning, energized systems, verified performance under load, validated redundancy, trained staff, and a finalized turnover package. Operations must accept the facility as ready to support IT operations safely and reliably, based on agreed requirements.
Missing an RFS date delays operational readiness and service activation, leaving the facility unable to support planned IT workloads. Common causes include equipment lead times, commissioning failures, and unresolved punch list items.
Delays with critical power systems, such as switchgear or generators, can push back the entire schedule. That can leave capacity idle or cause tenants to miss deployment targets, leading to financial and operational setbacks.
No. Ready for Service (RFS) is a technical and operational milestone. It means a facility has been commissioned, energized, and accepted by the operations team as ready to support customer IT operations.
RFS is required before handover, but it doesn’t automatically trigger customer billing. Billing is a separate process governed by the service agreement’s terms.
