Paul Industries performs data center commissioning in Arizona on the mechanical side: pressure testing, flushing and filling, equipment startup, functional tests and integrated systems tests of chilled water plants, dry cooler yards, CDUs and air handling, for data halls in Phoenix, Mesa, Chandler, Goodyear and Tucson. Arizona gives a commissioning team something few states offer: a real design day almost every summer afternoon. Paul Industries plans the tests to use that heat, keeps generator runs inside the county permit, and hands the owner a record set that matches the city’s permit file.
Request a quote or call 201-450-8280
What data center commissioning in Arizona proves before the load arrives
Data center commissioning in Arizona proves, before servers depend on it, that the cooling plant carries its design load in desert heat, survives the loss of any single component, rides through a utility outage onto generators and back, and is documented well enough for the operator to run it. The tests follow the same sequence as anywhere, from factory witness to integrated systems testing, but three Arizona conditions shape the plan: summer afternoons above 110 degrees, a county air permit that counts every hour a standby generator runs, and cities asking large water users to cut back while new piping still has to be flushed.
The national data center commissioning page lays out levels, scripts and roles in general. This page takes them into Arizona’s permit offices, weather and water rules.
What is commissioning a data center, in Arizona terms?
Commissioning a data center means proving, with signed records, that every system in the facility is installed as designed, starts and runs correctly, performs its specified functions under every operating mode, and works together with the other systems under failure and recovery, following the process defined in ASHRAE Guideline 0 and ASHRAE Standard 202. Data center projects usually organize it into five levels, each a gate the next one depends on.
| Level | What is verified | Arizona-specific point |
|---|---|---|
| 1. Factory witness | Chillers, CDUs, pumps and air handlers tested at the maker’s plant against the submittal | Capacity witnessed at an elevated ambient that matches a Phoenix yard, alongside the catalog rating point |
| 2. Delivery and inspection | Equipment received, inspected for damage and stored | Openings sealed against dust; controls and drives kept out of the sun until installed |
| 3. Installation and startup | Pressure tests, flushing, filling, rotation checks, first runs | City inspections under the mechanical code in force where the permit was issued |
| 4. Functional performance | Each system run through every sequence and alarm | Economizer and adiabatic changeover tested at real Arizona temperatures where the season allows |
| 5. Integrated systems test | Whole facility under load through utility loss, generator start and restoration | Generator hours logged for the Maricopa County permit file |
Level 1 deserves more weight in Arizona than it usually gets. A chiller or dry cooler rated at a 95 degree ambient tells the owner little about a yard that reaches 115, so purchase orders for Arizona plants can call for factory performance tests at an elevated entering air temperature, with the capacity, power and head pressure recorded at that point. A shortfall found on the test stand is corrected by the maker before shipment; the same shortfall found in July costs a summer.
The mechanical contractor’s part of that program is large. Paul Industries carries levels 2 and 3 for the systems it installs, writes and runs the level 4 functional scripts for the cooling plant with the owner’s commissioning agent, and operates the mechanical systems during the level 5 integrated test so that every valve, pump and setpoint responds the way the scripts expect.
Permits, inspections and city codes in the Valley
Permits and inspections for an Arizona data center are issued by the city or county where the building stands, because each jurisdiction adopts its own building, mechanical and energy codes. Phoenix’s council approved its 2024 Phoenix Building Construction Code by Ordinance G-7397 in June 2025, and the code took effect on August 1, 2025, bringing in the 2024 International Mechanical Code, the 2024 International Energy Conservation Code and related codes with city amendments. Mesa, Chandler, Tempe, Goodyear, Peoria and Tucson each publish their own adopted editions.
The mechanical code sets the test pressure and procedure for hydronic and refrigerant piping that the city inspector witnesses or accepts by record, and the energy code’s model text carries a commissioning section, C408, that calls for functional testing of mechanical systems and controls with documentation to the owner. Which version applies depends on the amended edition each city adopted, so Paul Industries reads the adopted code for the permit address before writing the test plan, lists every code test as a hold point in the schedule, and keeps the inspector’s sign-offs in the same binder as the commissioning scripts.
Generator hours and the Maricopa County emergency engine permit
Generator hours used for commissioning in Maricopa County count against the terms of the county’s air permit, so they are planned rather than spent freely. The Maricopa County Air Quality Department’s general permit for stationary emergency internal combustion engines covers engines used only for emergency or standby purposes and never for peak shaving, and it requires the operator to record monthly operating hours and rolling totals for each engine, document the reason each engine ran, keep fuel and maintenance records, and retain them for at least five years.
A data center’s integrated tests, load bank runs and transfer tests all put hours on those engines. Paul Industries schedules mechanical tests so that each generator run proves as much as possible: the cooling plant restart, the CDU pump ride-through, the chiller restart timing and the controls recovery are tested in the same run wherever the scripts allow. The run log Paul Industries keeps for each test shows the engine, the duration and the purpose, in a form the owner can carry straight into the permit records. Sites outside Maricopa County follow the air agency and permit that cover that county, and the same logging discipline applies.
Testing a cooling plant at true design heat
Testing a cooling plant at true design heat is possible in Phoenix on most summer afternoons: the 1991 to 2020 normals count 111 days of 100 degrees or hotter in an average year, and a typical year’s peak sits close to 116. A plant designed for a 115 degree day can be proven against a 112 degree afternoon, which is a far more convincing test than a mild-day run with the results extrapolated. In 2024 Phoenix recorded 70 days at 110 degrees or more.
Paul Industries uses that heat deliberately. Where the construction schedule allows, the level 4 capacity tests on air-cooled chillers, dry coolers and adiabatic stages run between late June and early September, with load banks holding the hall at its design load while the outdoor temperature does the rest. Redundancy is proven at the same condition: one chiller or cooler is taken out of service on a hot afternoon, and the plant must hold its supply temperature without it. The monsoon adds a second test condition, because the July and August dew point in Phoenix averages roughly 56 to 58 degrees against 39 in June, and evaporative and adiabatic equipment must still meet its numbers with the higher wet bulb.
When turnover falls in winter, the seasonal tests move to a dated slot in the following summer. The owner receives the plant tested at full load on load banks in mild weather, a written list of the hot-weather tests outstanding, and a date in the first summer when those tests run. Winter does offer one advantage: economizer and dry-only modes can be proven in January, when Phoenix highs average 68 degrees.
Flushing and filling new piping with drought-stage water
Flushing and filling new piping in the Valley now happens under a water alert, so the volume used is planned like any other resource. Phoenix declared its Stage 1 Water Alert in June 2022 and has announced a move to Stage 2 in January, with a voluntary 5 percent reduction asked of residents and businesses. A large chilled water system still has to be flushed at velocity until it runs clean, and that means a lot of water.
Paul Industries reduces it by flushing in sections with temporary strainers and recirculation where the cleaning method allows, by cleaning pipe before it is installed, and by keeping pipe ends capped during construction. That last point matters more in Arizona than in most states: construction sites in Maricopa County operate under dust control requirements for dust-generating activities, and monsoon dust storms, which the National Weather Service warns of when visibility falls to a quarter mile or less, drive fine soil into any open pipe or equipment opening. Every open end left uncapped in July becomes debris in a strainer or a plate heat exchanger in August. Fill water quality and chemical treatment are recorded before the loop is handed over, and discharge of cleaning water follows the sewer provider’s terms.
Proving controls, sensors and meters before the hall goes live
Controls, sensors and meters in an Arizona data center cooling plant are proven before the functional scripts run, because a script that passes on a mis-calibrated sensor proves nothing. Outdoor air temperature and humidity sensors deserve special attention in the desert: a sensor mounted where it sees reflected heat from a roof or a sunlit wall can read several degrees high on a July afternoon and trigger an early changeover from dry to adiabatic or mechanical cooling, wasting water and power every summer for the life of the plant.
Paul Industries checks each sensor against a calibrated reference at the point of use, confirms its location and shielding, and traces every point from the field device to the building management system graphic. Supply and return temperatures on each chiller, cooler and CDU are compared across redundant sensors, flow meters are verified against pump curves or a portable meter, and alarm thresholds are tested by simulation. Water meters on tower and adiabatic makeup get the same treatment, because Valley cities increasingly ask large users what they consume, and an owner who reports water use needs meters that were proven at turnover rather than assumed.
Adiabatic and evaporative equipment under monsoon conditions
Adiabatic and evaporative equipment is the part of an Arizona plant whose performance changes most with the season, so its commissioning covers both the dry and the humid summer. In June the Phoenix average dew point sits near 39 degrees and wetted media or spray stages deliver large temperature drops; in the monsoon months the wet bulb rises and the same equipment delivers less. A plant accepted only on a June test can disappoint in August.
Paul Industries tests the changeover setpoints, water supply, drain and bleed controls, freeze or dry-out protection and water treatment dosing on every adiabatic stage, then records the temperature drop achieved against the measured wet bulb so that later performance can be compared with a known baseline. Where turnover misses the monsoon, a humid-season test goes on the deferred list with the other seasonal checks. Dust storm recovery is part of the test as well: strainers, nozzles and media are inspected after the first storm of the season, and the inspection results are added to the turnover file.
How to commission a data center cooling plant in Arizona, step by step
How to commission a data center cooling plant in Arizona follows a fixed order from paperwork to integrated test, with each step closed out before the next begins so that a failure is found where it is cheapest to fix.
| Step | Work and records | Hold point |
|---|---|---|
| Plan | Commissioning plan, test scripts, code test list for the permit city, generator hour budget | Owner and commissioning agent approve scripts |
| Pressure test | Hydronic and refrigerant piping tested to the adopted mechanical code and design standard | City inspection or accepted test record |
| Flush and clean | Sectional flushing, chemical cleaning, strainer inspection, water quality readings | Clean-water criteria met before equipment connects |
| Fill and treat | Facility loop treated; technology loops filled with purified coolant | Fill quality logged and signed |
| Startup | Rotation, alignment, vibration, first runs of pumps, chillers, coolers and CDUs | Maker’s startup reports received |
| Functional tests | Every sequence, alarm, failover and economizer changeover | Scripts signed by the commissioning agent |
| Integrated test | Load banks, utility loss, generator start, restart and restoration | Generator hours logged for the air permit |
| Turnover | Records, training, as-built drawings, deferred test list | Owner acceptance |
Commissioning liquid cooling loops and CDUs
Commissioning liquid cooling in an Arizona hall adds steps an air-cooled room never needed: cleanliness of the technology loop to the cold plate maker’s particle limit, coolant chemistry at fill, CDU control of supply temperature and pressure across the full load range, leak detection response, and pump ride-through on a power transfer. A liquid-cooled processor heats up within seconds of losing flow, so the transfer test is the one that matters most.
Paul Industries runs the CDUs on load banks or heat-load simulators before servers arrive, trips their normal power source, and records the coolant temperature through the generator start and restoration. The facility water side is tested at the warm supply temperature the design depends on, during a hot afternoon where possible, to prove that dry coolers and trim cooling hold the setpoint together. Leak detection is tested by wetting each sensor cable at several points and confirming the alarm reaches the operator and, where the design calls for it, closes the isolation valves on that row. Coolant samples taken at fill and again after the load test are compared, so any rise in particles or conductivity during the first hours of operation is caught before servers depend on the loop. Design detail for those loops is on data center liquid cooling in Arizona.
Utility energization: SRP, APS and TEP dates
Utility energization dates set the start of integrated testing, because load banks and full-load runs need permanent power from the serving utility, usually the Salt River Project or Arizona Public Service in the Phoenix area and Tucson Electric Power in much of southern Arizona. A late energization date moves every level 5 test behind it, and in Arizona it can also push a hot-weather capacity test into the cooler months.
Paul Industries keeps the mechanical tests that need only temporary power, such as pressure tests, flushing and pump rotation checks, off the critical path, so that the plant is ready for load the day permanent power arrives. When energization slips into autumn, the hot-weather tests go on the deferred list with a date the following summer. Energy for load bank tests is a modest cost at Arizona prices: a 2,000 kilowatt load bank run for eight hours uses 16,000 kilowatt-hours, about $1,300 at the 2025 average industrial price of 8.05 cents per kilowatt-hour and about $2,000 at the commercial average of 12.45 cents (EIA).
Turnover records an Arizona operator receives
Turnover records for an Arizona data center cooling plant combine what the city requires, what the county air permit requires and what the operator needs to run the plant. Paul Industries assembles them as the work proceeds rather than at the end, so nothing depends on memory.
| Record | Contents | Who relies on it |
|---|---|---|
| Code test records | Pressure tests with medium, pressure, duration and result; inspection sign-offs | City building official and the owner’s insurer |
| Flushing and fill logs | Sections flushed, strainer findings, water quality, coolant chemistry at fill | Operator and cold plate maker |
| Startup reports | Maker’s startup sheets for chillers, coolers, pumps and CDUs | Operator and warranty claims |
| Signed test scripts | Functional and integrated tests with readings, failures and retests | Owner, commissioning agent and tenants |
| Generator run log | Engine, date, duration and purpose of every test run | Air permit records kept for five years |
| Deferred test list | Hot-weather or monsoon tests outstanding, with dates | Owner and operator |
| As-built drawings and setpoints | Final piping, valve tags, control sequences and setpoints | Operator and future expansion designers |
How much does data center commissioning cost in Arizona?
The cost of data center commissioning in Arizona is driven by the size and redundancy of the plant, the number of scripts and test conditions, how much testing is witnessed by the owner’s agent, load bank rental and energy, generator fuel and hours, the amount of flushing and chemical cleaning, and whether seasonal tests have to be returned to in a later summer. A project that keeps its pipe clean and its records current through construction spends far less on commissioning than one that discovers debris and missing paperwork at the end.
Paul Industries prices mechanical commissioning together with the installation when it builds the plant, and as a separate scope for plants that are newly installed or already operating. A budget range comes from comparable scope once the plant size and level of testing are known, and a firm price follows the review of drawings and scripts.
Who handles data center commissioning services in Arizona?
Paul Industries handles data center commissioning services in Arizona for the mechanical systems of new halls, expansions and existing plants in Phoenix, Mesa, Chandler, Tempe, Goodyear, Peoria, Casa Grande and Tucson. Paul Industries is headquartered at 256 Shore Drive in Kilmarnock, Virginia, was formerly based in northern New Jersey, then Pennsylvania, and as an East Coast contractor takes work across Arizona and in all 50 states. Owners choose commissioning as part of a design-build or complete installation contract, or as a stand-alone scope on a plant already installed.
The plant being proven is described on data center cooling in Arizona, while whole-campus mechanical packages sit under data center mechanical contractor in Arizona, and chiller faults found during testing are handled under chiller repair in Arizona. Regulated process plants follow a different protocol, described on validation and commissioning in Arizona. For comparison, county inspection practice at the headquarters state is on data center commissioning in Virginia, and testing without a statewide commercial code is on data center commissioning in Texas.
Arizona data hall testing from Paul Industries
Across Arizona, Paul Industries takes a data center cooling system from its first pressure test through flushing, fill, startup and scripted functional tests, carries it through integrated tests on load banks and generators, and turns over a record set that serves the city, the county air permit and the operator. Send the drawings, the commissioning plan or level requirements, the schedule and the energization date. Call 201-450-8280 or request a quote, and see the Arizona page for the rest of Paul Industries’ work in the state.
Standards referenced: ASHRAE Standard 202 · ASHRAE Guideline 0 · 2024 International Mechanical Code (2024 Phoenix Building Construction Code) · 2024 International Energy Conservation Code, Section C408 · ASME B31.9 · Maricopa County General Permit for Stationary Emergency Internal Combustion Engines
Frequently asked questions
Who handles data center commissioning in Phoenix and the West Valley?
Paul Industries handles data center commissioning in Phoenix, Goodyear, Avondale and Glendale for the cooling plant, piping, CDUs and air handling. West Valley campuses often turn over one building at a time while the next is still under construction, so tests are planned to protect the operating halls. Paul Industries writes and runs the mechanical scripts with the owner’s commissioning agent and keeps the generator run log for the county permit.
Does Paul Industries commission data halls in Mesa, Chandler and Tempe?
Yes. Paul Industries commissions the mechanical systems of data halls in Mesa, Chandler, Tempe and Gilbert, from pressure testing and flushing through functional and integrated tests. Each East Valley city adopts its own mechanical and energy codes, so the code tests and inspections are drawn from the edition in force at the permit address before the test plan is issued.
Who tests data center cooling systems in Tucson?
Paul Industries tests data center cooling systems in Tucson and the rest of Pima County. Tucson summers are hot enough for meaningful capacity tests, and its cooler nights, around 76 degrees in July, give a second condition for proving economizer and storage modes. Generator runs for integrated tests follow the air permit that covers the site, and the run log is kept the same way as in Maricopa County.
How does data center commissioning in Phoenix use the summer heat?
Data center commissioning in Phoenix can prove cooling capacity at real design conditions, because afternoons above 110 degrees are common from June to August. Paul Industries schedules level 4 capacity and redundancy tests for those afternoons where the construction schedule allows, with load banks holding the design load. A plant that holds its setpoint with one unit out at 112 degrees outdoors has been proven, not estimated.
What records does the Maricopa County generator permit require during commissioning?
The county’s general permit for stationary emergency engines requires monthly operating hours and rolling totals for each engine, the reason each engine was operated, fuel documentation and maintenance records, kept for at least five years, and it bars use for peak shaving. Commissioning runs add hours, so Paul Industries logs every test run with engine, date, duration and purpose for the owner’s permit file.
Can cooling tests be deferred if an Arizona hall is turned over in winter?
Yes. The plant is tested at full load on load banks in mild weather, economizer and dry-only modes are proven while it is cool, and the hot-weather capacity and redundancy tests are listed as deferred with a date in the first summer. Phoenix’s January highs average 68 degrees, ideal for economizer proof, while its summer gives true design conditions. Both seasons end up tested.
Which code sets the pressure test for chilled water piping in an Arizona data center?
The mechanical code adopted by the city or county that issued the permit sets it, along with whichever piping standard the engineer of record specifies, which for building service loops is often ASME B31.9. In Phoenix that is the 2024 International Mechanical Code as amended in the 2024 Phoenix Building Construction Code. Paul Industries records the test medium, pressure, duration and result for each section and holds the inspection sign-off with it.
Does the energy code require commissioning of an Arizona data center?
The model International Energy Conservation Code carries Section C408 on system commissioning, which calls for functional testing of mechanical systems and controls and documentation to the owner. Arizona cities adopt the energy code with their own amendments, and Phoenix adopted the 2024 edition effective August 1, 2025. Paul Industries checks the adopted text for the permit address and builds its requirements into the test plan.
How does Paul Industries work with the data center commissioning agent on an Arizona project?
On most Arizona projects the owner’s data center commissioning agent sets or approves the overall plan and witnesses tests; Paul Industries delivers the mechanical side of it. That means drafting functional scripts for the cooling systems, running equipment during tests, recording readings, correcting deficiencies and retesting, and assembling the mechanical turnover records. Early involvement lets test ports, gauges and isolation valves be placed where the scripts need them.
How is a liquid cooling loop commissioned in an Arizona hall?
The loop is pressure tested, flushed to the cold plate maker’s cleanliness limit, filled with purified coolant and recorded, then run on load banks or heat-load simulators. The key test trips the CDU’s normal power and records coolant temperature through the generator start, because processors heat up within seconds of losing flow. The facility water side is proven at its warm design temperature, on a hot afternoon where possible.
How much water does flushing a new data center chilled water system use in Phoenix?
The volume depends on pipe size, length and the cleaning method, and a large system flushed at velocity uses a great deal. Under Phoenix’s drought stages, Paul Industries cuts it by cleaning pipe before installation, capping open ends against dust, flushing in sections with recirculation and temporary strainers where the method allows, and recording the volumes used so the owner can report them.
What does monsoon dust do to a data center under construction?
Dust storms drive fine soil into any open pipe, duct or equipment opening, and the National Weather Service warns of them when visibility falls to a quarter mile or less with gusts of 40 to 60 miles per hour. Debris that enters in July shows up in strainers, plate heat exchangers and cold plates later. Capping every open end, sealing stored equipment and inspecting strainers after storms keep the commissioning schedule intact.
What do data center commissioning companies hand over at the end of an Arizona project?
The handover is a complete record set: code test records with inspection sign-offs, flushing and fill logs, makers’ startup reports, signed functional and integrated test scripts, a generator run log for the air permit, a deferred test list with dates, and as-built drawings with final setpoints. Paul Industries builds the package as work proceeds and delivers it with operator training on the cooling systems.
At what design stage should Paul Industries be brought into an Arizona commissioning plan?
At design development, before equipment is ordered. That is when factory witness tests at elevated Arizona ambient can be written into the purchase orders, test ports and isolation valves placed in the drawings, and the generator hour budget agreed against the county permit. A contractor brought in at startup inherits those decisions. Paul Industries joins at whichever stage the owner chooses and reviews the plan first.
After new chillers or rows go into a live Arizona hall, how is the plant retested?
Yes. After new chillers, coolers or liquid-cooled rows are added, the affected systems are retested functionally, and the integrated sequence is rerun in a controlled way that protects live load. Paul Industries also reviews the existing records, fills gaps where tests were never documented, and updates setpoints and as-built drawings so the plant is described accurately for the operator.
What sets the duration of mechanical testing on an Arizona data hall?
The time depends on the plant size, the number of scripts, redundancy and how many buildings are in the phase. Pressure testing and flushing run alongside installation, functional testing follows system by system, and the integrated test runs once permanent power is live. Seasonal tests can extend into the first summer. Paul Industries builds the commissioning schedule into the installation schedule from the start.
Which documents let Paul Industries scope testing for an Arizona data center?
The useful set is the mechanical drawings with control sequences, the commissioning plan or required levels, the construction and energization schedule, the generator arrangement and air permit, and any owner or tenant test standards. Paul Industries returns a test plan, the code test list for the permit city, a generator hour estimate and a budget range.
Commissioning a data hall in Arizona?
Send the drawings, sequences of operation, commissioning levels, schedule and energization date. Call 201-450-8280 or request a quote.
