
Commissioning a data center ensures all systems - power, cooling, controls, and life safety - are tested and ready for operation. This process is critical for avoiding costly downtime, ensuring reliability, and meeting performance goals.
Here’s a quick breakdown of the commissioning process:
Preparation involves:
The goal? A seamless handover to operations with zero unresolved issues. Proper documentation, training, and walkthroughs ensure the facility is ready for day-one operations. Missed steps lead to risks, delays, and higher costs.
Pro tip: Start commissioning planning early in the project to catch design flaws before they escalate.
Data Center Commissioning: 5-Level Framework Overview
Before stepping into the field, it's crucial to complete Level 0: designing, staffing, and documenting the entire commissioning program. This groundwork can make the difference between a seamless project and one plagued by delays and budget overruns.
Every commissioning program begins with two key documents: the Owner's Project Requirements (OPR) and the Basis of Design (BOD). The OPR outlines performance goals like critical load, redundancy, rack density, cooling, and uptime. The BOD, on the other hand, explains the approach to achieving those goals.
Reconciling these documents early is essential. Addressing design inconsistencies on paper is far less costly than fixing issues during integrated testing. This phase also establishes the standards that will guide the project, such as ASHRAE Guideline 0, Uptime Institute Tier Guidelines, NFPA, and ANSI/TIA-942.
Additional studies, like the Electrical System Discrimination Study, Arc Flash Study, and CFD simulations for airflow in data halls, should be included to clarify the scope and sequence of functional and integrated testing.
The commissioning team is more than just the Commissioning Authority (CxA) and a few contractors. It’s a cross-functional group that needs to be assembled and aligned before fieldwork begins. Below is a breakdown of key stakeholder roles and their responsibilities during pre-commissioning:
| Stakeholder | Primary Pre-Commissioning Responsibility |
|---|---|
| Owner | Define the OPR, appoint the CxA, and set the project budget and schedule |
| Commissioning Authority (CxA) | Develop the Commissioning Plan, Responsibility Matrix, and initial test scripts |
| Engineer-of-Record (EOR) | Create the BOD, develop the Sequence of Operation, and review designs for OPR alignment |
| General Contractor / Trades | Review the design for site-specific constraints and prepare installation checklists |
| Operations Team | Evaluate the OPR for maintainability and contribute to the training program |
A smart move is to hire the facility manager and at least one operations supervisor during the pre-design phase. Their early involvement can help flag maintainability concerns before they’re locked into the design. Additionally, having the CxA report directly to the owner ensures the owner's priorities remain central throughout the project.
"Commissioning should first be considered, and planned for, at a project's inception and continue through the design, construction, transition-to-operations, and ongoing operations." - Ryan Orr, Uptime Institute
Aligning the team structure with broader data center construction workflows ensures commissioning isn’t treated as an afterthought. With the team in place, the focus shifts to finalizing documentation and digital tools for smooth field execution.
Once project requirements are clear and the team is assembled, confirm that all core documents and tools are ready before fieldwork begins. The Commissioning Plan acts as the strategic guide, outlining scope, schedule, risk management, and resource needs. Pair it with a complete RASCI Responsibility Matrix, a detailed Sequence of Operation (SOO) for each major system, and standardized test script templates for all commissioning levels.
The industry has largely moved away from paper-based systems, favoring digital commissioning platforms that offer real-time updates on test progress, punch lists, and sign-offs. To complement these platforms, consider using a color-coded equipment tagging system. This system provides technicians with a quick visual reference for each piece of equipment’s status in the commissioning process:
| Tag Color | Level | Status |
|---|---|---|
| Red | Level 1 | Factory Testing Complete |
| Yellow | Level 2 | Installation & Pre-Startup Complete |
| Green | Level 3 | Systems Start-Up Complete |
| Blue | Level 4 | Functional Testing Complete |
| White | Level 5 | Integrated Testing Complete |
Another helpful tool is a "First-Of-A-Kind" (FOAK) tracker. By identifying the first installed instance of each equipment type and using it as a quality benchmark, you can ensure consistency across all subsequent installations.
Once the documentation is in place and the team is aligned, the project moves into the field. This phase involves Levels 1 and 2, focusing on verifying equipment condition upon delivery and ensuring proper installation before testing begins.
Level 1 commissioning starts even before equipment leaves the factory. Factory Acceptance Testing (FAT) is performed at the manufacturer's facility to confirm electrical performance, control logic, and firmware integrity against the approved Bill of Materials. Major components like UPS units, generators, chillers, and switchgear undergo thorough testing. Results are recorded, open issues are logged, and resolutions are documented.
Tracking FAT results requires more than a simple pass/fail checkbox. Use specific status categories to provide clarity:
| FAT Disposition | Description |
|---|---|
| Passed with no exception | Equipment meets all criteria without issues. |
| Passed with documented exception | Minor issues noted but do not prevent delivery. |
| Failed and retested | Equipment failed initially but must pass before shipping. |
| Deferred to IST | Certain tests are postponed to Integrated Systems Testing. |
| Accepted by owner | Owner assumes risk of unresolved issues to keep the schedule on track. |
"Never make assumptions that products and systems will operate seamlessly unless you have the hard data to back this up." - Paul Pompili, Divisional Director, ISG [4]
When equipment arrives on-site, conduct a site acceptance inspection. Look for physical damage, verify part and label accuracy, and confirm that storage conditions meet manufacturer recommendations. This is also the time to check torque settings on electrical lugs and inspect fiber endfaces for contamination, which could cause signal loss. Identifying and fixing defects at this stage is far less costly than discovering them during functional testing.
Level 2 focuses on ensuring installation quality. Use the established FOAK (First of a Kind) benchmark to catch installation errors early - correcting a wiring mistake on the first unit prevents it from being repeated across others.
Each system type requires specific checks:
Once installation quality is confirmed, complete the pre-functional checklist to prepare systems for energization.
Before energizing systems, complete a Pre-Functional Checklist (PFC) for each one. This ensures the system is clean, safe, properly installed, and ready for startup. It also confirms that all manufacturer-recommended installation steps have been followed.
Room readiness is another critical checkpoint. Use a standardized room readiness template to ensure architectural, mechanical, and electrical prerequisites are complete before equipment installation. Pay close attention to data hall cleanliness - construction dust poses a serious threat to sensitive IT equipment during dynamic testing. Enforcing cleaning standards at this stage prevents contamination issues down the line.
Coordinate with vendors to ensure that all manufacturer startup representatives are scheduled, tools and instruments are on-site with clear ownership, and the BMS graphics and points list are approved and ready. Additionally, the network infrastructure should be independently certified before joint systems testing begins. These steps set the stage for a smooth transition into Level 3 system startup.
With pre-functional checks out of the way and systems powered up, Levels 4 and 5 shift gears. The focus moves from verifying installations to validating how everything works together, ensuring the facility performs as it should. These stages build on individual system tests and stress the importance of how systems function collectively.
Level 4 Functional Performance Testing (FPT) is all about making sure each system - whether it's UPS units, generators, chillers, or fire safety equipment - performs as intended. This involves testing under normal, emergency, and failure scenarios to confirm everything operates according to the Sequence of Operation.
Control loops are put through their paces, with engineers intentionally introducing faults to test failover mechanisms and redundancy logic. A color-coded tagging system helps track progress during this phase. Cooling systems, for instance, must be tested to ensure they deliver proper airflow and meet liquid cooling loop requirements under real tenant rack densities. Direct-to-chip (D2C) cooling setups might even require recommissioning every time new hardware is added, so early planning for these tests is crucial. These evaluations ensure each system contributes to the overall reliability of the facility.
While individual systems are tested in isolation, IST takes it a step further by evaluating how all systems work together across the entire facility. Instead of just asking, "Does this system work?" IST asks, "Do all systems work together seamlessly when something goes wrong?"
IST scenarios are carried out under simulated tenant loads using load banks, with every detail documented through time-stamped logs, photos, and videos. Key scenarios that every IST plan should address include:
| IST Scenario | Verification Objective |
|---|---|
| Utility Power Loss | Ensure the generator start sequence and ATS transitions function as expected. |
| UPS Ride-Through | Measure how long the battery or flywheel supports the load during source transitions. |
| Cooling Failover | Confirm redundant units activate and the system responds correctly to sudden load changes. |
| Fire Alarm Integration | Verify that dampers, power shut-offs, and mechanical systems respond properly to fire triggers. |
| Maintenance Bypass | Demonstrate that uptime is maintained while critical components are isolated. |
Load banks are critical for replicating the thermal and electrical conditions of live operations, providing a realistic environment for testing.
Every failure detected during testing is logged as a formal nonconformance. A centralized commissioning issues log is used to track defects, assign responsibility, document corrective actions, and schedule retesting. The goal isn't just to check off completed tests but to evaluate how issues were resolved and what improvements were made.
A clear Responsibility Matrix ensures accountability by defining who is responsible, accountable, and supportive for each issue. This prevents delays caused by miscommunication or unclear ownership. Addressing and retesting issues promptly is crucial to meeting operational readiness standards. Once corrections are made, retesting confirms compliance with all commissioning levels. A White tag is the final sign that a system is ready for handover.
Once testing is complete and all nonconformances are resolved, the project enters its final phase: transitioning control from the project team to operations. This step is all about ensuring the facility is fully prepared for day-one operations. As the Build Team succinctly puts it:
"An incoming operations team should be able to run the facility without calling the project team every day for missing context." [2]
After integrated testing wraps up, the focus shifts to compiling and delivering the turnover package. This package is essential for ensuring no critical details slip through the cracks. It should include everything from the design intent to maintenance schedules and validation records, all organized for easy reference.
| Document Category | Key Deliverables |
|---|---|
| Design Baseline | Final OPR, BOD, Commissioning Plan |
| System Logic | SOO, BMS Points List, Control Narratives |
| Validation Records | FAT/SAT Reports, Functional Test Scripts, IST Final Report |
| Safety & Analysis | Arc Flash Study, Discrimination Study, CFD Airflow Analysis |
| Closeout | As-builts, Warranties, Training Records, Final Issues Log |
A critical piece of this package is the Systems Manual, which differs from the O&M manual. While O&M manuals focus on individual components, the Systems Manual offers a comprehensive guide for operating and troubleshooting the entire facility. Both are indispensable and should be included in the turnover documentation.
Training should align with the commissioning levels. For example, individual system training happens during Level 4, while full-facility rehearsals are part of Level 5 (Integrated Systems Testing). This ensures operators get hands-on experience with real-world sequences, such as handling utility outages and generator starts. As Bob Morris from Constructandcommission.com emphasizes:
"Training is a fundamental element to the successful handover and completion of a project from the construction/commissioning team to the building operator." [3]
Training should also cover critical areas like alarm interpretation, failover timing, maintenance bypass procedures, and black start sequences - laying the groundwork for a smooth operational start.
Before officially handing over the keys, a thorough walkthrough is vital to confirm the facility's physical and operational readiness. This involves a detailed review of equipment labeling, safety markings, and as-built documentation. A Room Readiness Checklist should guide this process, ensuring that architectural, mechanical, and electrical prerequisites are met.
Key items to verify during the walkthrough include:
Additionally, performance benchmarks like PUE (Power Usage Effectiveness), cooling efficiency, and power draw should be recorded for future reference. These walkthroughs not only confirm that the facility is ready to operate but also provide valuable data for refining processes in future projects.
The turnover phase isn’t just about wrapping up the current project - it’s an opportunity to prepare for the next one. Document lessons learned, standardize templates, and archive test scripts to create a repeatable framework. This approach feeds insights back into earlier commissioning steps, improving execution for future projects.
With global data center power demand projected to climb by as much as 165% by 2030 compared to 2023 levels [2], teams that build scalable commissioning frameworks now will be better equipped to handle the growing workload. Another critical step is establishing a seasonal testing schedule during handover. Testing performance during peak summer and winter conditions after occupancy may seem easy to postpone but can be costly to overlook in the long run.
A commissioning checklist is more than just a project management tool - it’s what ensures a facility is ready to perform reliably from day one. As Averna explains:
"True readiness is only proven through rigorous testing and validation. Commissioning transforms a built installation into a verified facility." [1]
The level-based framework outlined in this guide - from early design validation to integrated systems testing and final handover - serves as a series of quality checkpoints. Each phase is designed to catch and address defects before they can disrupt operations, minimizing the risk of costly downtime. With global data center power demand projected to increase by 165% by 2030 compared to 2023 levels [2], adopting this thorough, step-by-step approach not only ensures system reliability but also creates a repeatable model for future projects.
That said, even the best checklist is ineffective without the right expertise. Commissioning mission-critical facilities demands a skilled team - professionals who can conduct arc flash studies, interpret BMS alarms, and make critical life-safety decisions. Bringing these specialists on board early, before finalizing the design, is one of the most impactful decisions a project leader can make. For insights into finding the right talent, explore data center hiring strategies to understand how to recruit for these specialized roles.
Once your commissioning process is defined, securing top-tier talent is the logical next step. That’s where iRecruit.co comes in. Founded by Dallas Bond and Tanya Runholt, iRecruit.co specializes in recruiting for mission-critical construction projects. They place experienced professionals such as commissioning managers, MEP specialists, and project executives. Their pre-screened candidates and success-based pricing model save you time and keep your project on track.
The checklist sets the foundation, but it’s the right team that brings it to life.
Planning for data center commissioning should kick off during the design phase, well before any equipment arrives on-site. This is when the Owner’s Project Requirements (OPR) are established, laying the groundwork for the commissioning scope and plan. In a level-based framework, this initial stage is called “Level 0: Design & Planning.”
The difference comes down to the scale and intricacy of the testing. Functional testing (Level 4) focuses on verifying that specific systems, such as cooling units or UPS systems, operate correctly under simulated conditions. On the other hand, Integrated Systems Testing (Level 5) evaluates the entire facility as a single, interconnected system. This level of testing mimics real-world failure scenarios - like a complete power outage - to ensure that all subsystems work together seamlessly to maintain stability.
The turnover package needs to be built progressively during the commissioning process - not left for the end. It should include the finalized Owner’s Project Requirements (OPR), Basis of Design (BoD), and the approved commissioning plan. Additionally, it must contain completed test records, an issues log, as-built drawings, equipment warranties, control sequences, maintenance procedures, training documentation, emergency procedures, and a vendor contact list. These elements are crucial for ensuring the facility is fully prepared for operation.



