Data Center Commissioning: What Each of the Five Levels Actually Proves

Commissioning is a cost escalation ladder. Each level exists to catch a specific class of defect before it reaches the level where the same defect costs far more to fix.

A transformer fault found at factory witness test is a manufacturer's problem. The same fault found at integrated systems test stops the whole programme. The same fault found in live operation is an outage with a customer on the other end of it.

That escalation is the entire business case, and most commissioning content skips it to list the levels.

The level that proves the most is also the one most at risk. Level 5, the integrated systems test, needs the whole plant, full load banks and a long block of uninterrupted time, which makes it the first thing schedule pressure attacks when a project runs late.

This guide covers what each level proves, what the Level 5 scripts actually contain, what documents govern the process, and where programmes fail.

What Commissioning Proves

Data center commissioning is the witnessed verification that the power and cooling plant will carry critical IT load, documented before any IT load arrives.

It is a structured process that systematically tests, validates and documents every critical system including power distribution, cooling infrastructure, UPS units, switchgear and HVAC before a facility goes live, confirming that all components perform as designed under both normal operating conditions and failure scenarios.

Commissioning is not testing

Testing confirms that a piece of equipment works. Commissioning confirms that the installed systems, together, satisfy what the owner asked for.

The distinction matters because a facility can pass every individual equipment test and still fail at the moment a generator has to pick up a UPS that is carrying a chiller plant restarting.

Why it goes beyond installation sign-off

Commissioning provides the operational evidence that a data center can sustain the uptime, energy efficiency and compliance standards that Tier II through Tier IV facilities and their tenants contractually require.

An installation certificate says the work was done. A commissioning report says the facility behaved correctly when the utility was deliberately dropped at full load.

The contractual consequence

Where a lease or a service level agreement commits to an availability standard, the commissioning record is the evidence that the facility was capable of meeting it on day one. Without that record, the first real failure becomes a dispute about whether the facility was ever capable.

The Cost Escalation Ladder

Defects caught at factory testing cost a fraction of what the same defect costs when discovered during live operations under full production load.

That is the reason the levels are sequential, and the reason each must pass before the next begins.

Why Level 5 rework is so expensive

Because an IST cannot be partially repeated. The test proves systems working together, so a defect that changes any system's behaviour invalidates the scenarios that depend on it.

Repeating it means mobilising load banks again, scheduling another uninterrupted block, and reassembling the witness group.

What happens if a level is skipped

The defect does not disappear. It moves to the next level, where it costs more and where it is harder to isolate because more systems are involved. Skipping or compressing any stage creates compounding risk for exactly that reason.

Owner's Project Requirements and Basis of Design

Every commissioning test traces back to the Owner's Project Requirements, and ASHRAE Guideline 0 puts that document first.

The Owner's Project Requirements, or OPR, is the written statement of what the owner needs the facility to do: availability, capacity, environmental conditions, redundancy, maintainability, and the operating scenarios it must survive. It is the measurable yardstick.

The Basis of Design, or BoD, is the designer's statement of how the design intends to satisfy the OPR.

The verification chain

Under ASHRAE Guideline 0 the chain runs OPR to BoD to design to installation to test, so a deficiency is judged not against opinion but against whether the built plant still satisfies the OPR.

That is the practical value of the document. Without it, every disagreement at commissioning becomes an argument about intent. With it, the question is factual: does the installed plant do what the owner wrote down?

If the OPR was never written

It frequently was not, or it exists as a scatter of requirements across a design brief, a lease and a series of emails. Reconstruct it before commissioning begins, because a test with no acceptance criterion cannot fail, and a test that cannot fail proves nothing.

What the OPR must contain to be useful

Measurable criteria rather than aspirations. "High availability" is not testable. "The facility shall maintain critical load through a loss of utility supply at design load, with no interruption to the critical bus, and shall maintain space temperature within stated limits throughout" is.

The Commissioning Authority

The commissioning authority, or CxA, is the party that plans, witnesses and reports the commissioning process, and ASHRAE Guideline 0 sets out that role.

The CxA develops the commissioning plan, writes or reviews the test procedures, witnesses the tests, maintains the issues log, and produces the final report.

Independence is the point

A commissioning authority employed by the installing contractor is checking its own work.

That arrangement exists and it is not always wrong, particularly on smaller projects where a separate appointment is uneconomic. It should be a deliberate decision with the conflict acknowledged, not a default that nobody noticed.

The strongest arrangement is a CxA appointed by and reporting to the owner, with the contractor responsible for executing tests and the CxA responsible for witnessing and accepting them.

What to ask before appointing

Who employs the CxA and who do they report to. Whether they have witnessed an IST on a facility of comparable scale. Whether they write the scripts or review the contractor's. And what they do when a test fails and the programme is already late, which is the question that reveals whether the appointment is real.

For a fuller treatment of selecting an installation and commissioning partner, see our guide on choosing the right partner for installation and commissioning services.

The Five Levels

Data center commissioning is organised into five levels that climb from the factory bench to the fully integrated plant, and each level must pass before the next begins.

Some programmes add a Level 0 covering commissioning planning, including the load bank and temporary equipment plan that Level 5 depends on.

Levels 1 and 2: Before Anything Is Installed

Levels 1 and 2 catch defects while they are still the supplier's problem, which is the cheapest place for a defect to exist.

Level 1: factory witness testing

Before equipment arrives on site, the manufacturer tests it to verify that components meet design specifications. Each item is tested under controlled conditions, the results are documented, and the owner's representative witnesses the tests that matter.

The commercial point is the witnessing right. The owner must be contractually entitled to attend, and the purchase order must say which tests are witness points and which are review points.

A witness point means the manufacturer notifies the owner and the test is held for attendance. A review point means the test proceeds and the report is sent afterwards. Requesting witnessing after award is a variation.

Level 2: site acceptance

On delivery, equipment is inspected to confirm it matches the specification and arrived undamaged. This is also where the paperwork is checked: certificates, serial numbers, configuration and accessories against the order.

What to do when damage is found matters more than the inspection itself. Photograph before unwrapping, record against the delivery note, and notify the carrier and supplier within the period their terms require, which is frequently short.

Storage between delivery and installation

Equipment that arrives early sits somewhere. Switchgear, UPS modules and transformers all have storage requirements covering humidity, temperature and in some cases energised space heaters. A unit stored incorrectly for six months can fail Level 3 for reasons that began at Level 2.

Levels 3 and 4: System by System

Level 3 proves each system is installed correctly and safe to energise. Level 4 proves each system performs as designed on its own.

Level 3: pre-functional testing

This phase verifies that each system is installed correctly and ready for operation. It covers wiring and termination checks, point-to-point verification between field devices and the control system, settings against the approved schedules, safety interlocks, and initial energisation procedures.

A point-to-point check confirms that the signal from a specific sensor arrives at the correct point in the control system and reads correctly. It sounds trivial and it is where cross-wired sensors are found, which otherwise surface as inexplicable control behaviour at Level 5.

Level 3 is checklist work, and the quality of the checklist determines what gets caught. For a worked example, see our electrical commissioning checklist.

Level 4: functional performance testing

At this stage each system is tested under operating conditions to confirm it performs as specified. A UPS is tested on load. A chiller is tested at duty. A generator is run and loaded.

This is where load banks first appear, applied to individual systems rather than to the whole plant.

Each system is accepted on its own before Level 5 begins, because an IST that uncovers a single-system defect has wasted a full-plant mobilisation on something a system-level test should have caught.

Retest after remediation

When a defect is found and corrected, the affected test is repeated. The question is how much is repeated: the single test, the system, or everything that depended on it. Define the retest rule in the commissioning plan, because deciding it during a failure is a negotiation under schedule pressure.

Level 5: The Integrated Systems Test

Level 5 runs the complete power and cooling plant at design load, drops the utility deliberately, and scripts failures to prove every system responds together.

It is the keystone of the programme. Everything before it tests components and systems. Level 5 tests the facility.

What it involves

The whole mechanical, electrical and controls plant is run under load banks at design load. Failures are then injected according to written scripts, and the facility's response is recorded against the expected response defined in advance.

Why it is the level most at risk

Level 5 is the level schedule pressure attacks first, because it needs the whole plant, full load banks and a long block of uninterrupted time.

Every other level can be run in parallel with construction or in fragments between other activities. Level 5 cannot. It requires everything finished, everything available, and nothing else happening.

That makes it the obvious place to find schedule relief on a late project, and the worst possible place to find it.

Scripts come first

Test scripts are written and issued before the test, not assembled during it. Each script states the scenario, the expected response, the measurements to be recorded, the acceptance criterion and the pass or fail determination.

A script without a pre-agreed expected response is an observation exercise. The facility does something, everyone watches, and nobody can say whether it was correct.

Duration

Level 5 is measured in days rather than hours on any facility of scale, because scripts run sequentially, the plant must stabilise between scenarios, and data has to be reviewed before the next script proceeds.

For what Level 5 proves about a specific redundancy configuration, including N+1, 2N and 2N+1, see our guide to data center power redundancy and how each level is proven.

Load Banks: Standing In for the IT Load

A load bank is equipment that creates electrical or thermal load to stand in for the IT load during testing, because the IT equipment is not there yet and would not be risked if it were.

Resistive and reactive

On the electrical side, resistive and reactive load banks pull the design kW and kVA from the power chain.

A resistive load bank draws real power at unity power factor. A reactive load bank adds the inductive component that real IT and mechanical load produces.

Testing with resistive load alone does not reproduce the power factor the UPS, generator and transformers will actually see, which means a plant that passes a resistive-only test has not been tested at its real operating condition.

Step loading

The test begins with no load bank load applied to the power distribution system, and load is applied in steps until the design electrical load is reached. At the end, load is stepped back down in the same way.

Stepping matters because it exposes transient behaviour. A generator that carries a fully applied load may misbehave on a step change, and a cooling plant stabilised at full load may not track a rapid change.

Capacity and logistics

The load bank capacity required is the design electrical load, which on a large facility means a substantial rental fleet, cabling, distribution and a defined parking area.

Temporary equipment and instruments are installed according to an approved load bank and equipment plan, typically prepared well ahead of the test, and removed only once testing is agreed complete.

If load banks are unavailable

They are a rental market and they are in demand. Book them against the programme date and hold the booking, because a Level 5 date that slips twice will find the fleet committed elsewhere.

For the generation equipment these tests exercise, see our guide to power generation equipment compared.

The Failure Scripts

The IST proves the facility by breaking it on purpose, and the scenarios are specific.

Utility loss, the pull-the-plug test

Also called the black building test. With the facility at full available load, the utility service is opened at the main switchboard to simulate a real outage.

The expected response: the UPS holds the critical bus with no interruption, the generators start and accept load, and no critical equipment sees a break. What is recorded: actual bus behaviour, transfer time, and the time to generators carrying full load.

Mechanical restart and thermal ride-through

On the same scenario, mechanical infrastructure must restart and space temperatures in critical equipment rooms must remain within thresholds throughout.

This is where many facilities are genuinely tested. Cooling has an outage window while generators start and chillers restart, and the question is whether thermal mass carries the space until cooling returns.

Utility restoration

With the facility operating on generator at full available load, utility service is restored at the main switchboard. The loads must transfer back, mechanical infrastructure must restart where it cycled, and space temperatures must stay within thresholds.

Restoration is tested because it is a transfer in its own right and because it is the scenario operators experience most often.

Transfer equipment

Automatic transfer switch and static switch transfers are scripted individually. The load must transfer without downstream equipment seeing a break, and transfer time and any voltage dip are recorded.

Bypass behaviour

One test that most descriptions omit: with the UPS system in bypass, verifying that an automatic transfer does not occur.

This is a negative test. It proves the system does not do something it must not do, and negative tests are the ones most often left out of a script.

Cooling failure scenarios

On the mechanical side, scenarios include a chiller taken out of service and a chilled water loop removed, to prove the environment holds and every system responds as designed.

Building management system behaviour

The BMS must restart previously running equipment after the generators assume load. A control system that does not re-sequence correctly produces a facility with power and no cooling, which is a failure mode that only an integrated test reveals.

For the generation and transfer equipment behind these scripts, see our guide to data center power sources.

Governing Standards

Five standards frameworks govern data center commissioning, and the specification should name which apply.

ASHRAE Guideline 0 describes a commissioning process capable of verifying that the building and its systems meet the Owner's Project Requirements from predesign through warranty expiration. Its 2020 addendum retitled the document for new buildings and new systems.

NFPA 110 and transfer time

NFPA 110 classifies emergency and standby power systems by Type, Class and Level, where Type defines the maximum time permitted between loss of normal power and the generator accepting load.

That classification is a design decision with a test consequence: the IST script measures against it, and a system that transfers slower than its classified Type fails.

NFPA 4 is a different test

NFPA 4 covers integrated testing of fire protection and life safety systems. It is a distinct requirement from the Level 5 IST and it is frequently conflated with it. Both may apply to the same facility and they test different things.

Tier certification

Where a Tier is claimed, the Uptime Institute's Tier Certification of Constructed Facility involves demonstration testing against the Tier requirements. That is an additional process with its own criteria, not a by-product of a Level 5 IST.

Outside the United States

ASHRAE and Uptime Institute frameworks are used internationally. NFPA standards are North American, and other jurisdictions apply their own electrical and fire codes. The ISO/IEC 22237 series covers data centre facilities and infrastructure more widely. Confirm which governs before writing the specification.

Deliverables: What You Receive

Commissioning is delivered as documents, and a programme with no documentation trail has not been commissioned regardless of what was tested.

The core set

The commissioning plan, stating scope, roles, levels, procedures and schedule.

Test scripts and completed test records for every level, with measured results against expected results.

The issues log, recording every deficiency found, its disposition, the retest and its closure. This is the artefact that proves the process happened and it is the first thing a diligence process asks for.

The systems manual, which is the operational handover document covering design intent, sequences of operation, settings, and the information the operating team needs.

Training records, evidencing that the operations team was trained on the systems they are taking over.

The final commissioning report, with level close-out reports as each level completes.

Data from the test

Instrumentation data is downloaded for review after testing, and temporary equipment is removed only once the testing is agreed complete. Both belong in the sequence rather than being left to whoever demobilises last.

Ownership

Establish that the owner owns the test records, the scripts, the issues log and the systems manual, in native format, with no restriction on providing them to a different operator or a purchaser.

This is the same clause that matters on control system configuration and on CMMS data. The commissioning record is the facility's birth certificate, and a purchaser who cannot see it discounts for the uncertainty.

Insurance and warranty

Insurers assess commissioning evidence when underwriting a new facility, and a documented IST is the strongest evidence available that the design works. Equipment warranties frequently depend on correct commissioning, which means the records protect the warranty position as well as the operation.

Staffing

Training and handover are commissioning deliverables, not post-occupancy activities. The operating team should attend the IST, because watching the facility fail safely under controlled conditions is the most valuable training available and it happens exactly once.

Where Commissioning Programmes Fail

Four failure modes recur, and three of them are schedule rather than technical.

Level 5 gets compressed. The programme is late, the IST needs the whole plant and an uninterrupted block, and the script list gets shortened. The scenarios cut are usually the negative tests and the restoration tests, which are the ones that find control sequence errors.

The plant is not actually complete. Level 5 begins with outstanding work, a system runs in a temporary configuration, and the test proves the behaviour of a facility that will not exist by handover.

Levels are run out of sequence. A system that has not passed Level 4 appears in the IST, and a single-system defect consumes a full-plant mobilisation.

The issues log is not maintained. Deficiencies are raised verbally, closed informally, and there is no record of what was found, what was done, or whether it was retested.

What to do when a test fails late

Record it, assess whether the facility can accept load with the deficiency open, and make the acceptance decision explicitly and in writing. A deficiency accepted with eyes open and a remediation date is a managed risk. One accepted quietly to protect a date is a future outage with no paper trail.

The Wider Commissioning Lifecycle

The five levels describe the testing progression. They sit inside a longer lifecycle that begins before design and ends after handover.

The broader sequence runs: pre-design planning where owner project requirements are established, design review ensuring commissioning objectives are embedded in engineering specifications, equipment procurement verification, factory witness testing, site installation inspection, pre-functional and functional performance testing, and final integrated systems testing with full documentation and operational handover.

How the two frameworks relate

Levels 1 through 5 are the testing stages within that lifecycle. The stages that precede them, OPR development and design review, are commissioning activities that produce no test and determine whether the tests will mean anything.

ASHRAE Guideline 0 covers the full span, from predesign through warranty expiration, which is why it places the OPR first rather than treating commissioning as a construction-phase activity.

When commissioning should start

At design, not at energisation. A commissioning authority engaged during design reviews the specification for testability, ensures test ports and instrumentation are included, and establishes acceptance criteria while they can still be negotiated.

A CxA engaged at practical completion inherits whatever was built and tests it against criteria written after the fact.

Recommissioning

Facilities drift. Settings change, sequences are overridden during incidents and never restored, and equipment is replaced. Recommissioning re-verifies performance against the OPR after a period of operation, and it is the mechanism that catches accumulated drift before it becomes a failure.

What to Specify and How to Evaluate

A commissioning specification is reviewable only if it names the levels, the scripts, the standards and the deliverables.

The specification checklist

• The commissioning levels in scope, and who executes versus who witnesses at each.
• The commissioning authority's appointment, reporting line and independence.
• The standards that govern, named by designation.
• Script development responsibility and the approval process.
• The failure scenarios to be tested, listed, including negative tests and restoration.
• Load bank scope, capacity, duration and whose cost.
• Retest rules when a deficiency is found.
• Deliverables by name, with ownership stated.
• Training scope and attendance at the IST.

Evaluating a provider

Ask who employs the commissioning authority and who they report to. Ask for a redacted IST script from a comparable facility. Ask what their last programme found at Level 5 and how it was resolved. Ask what happens when a test fails and the programme is late.

The last question is the one that matters. Every provider has a good answer to the first three.

If scope is split across contracts

It usually is, with the electrical contractor, mechanical contractor, controls contractor and CxA all holding part of it. Define the interfaces explicitly, particularly who provides load banks, who writes scripts, who operates the plant during the test and who signs acceptance.

How Requirements Vary by Facility Type

The levels are constant. The scale, the formality and the acceptance party change.

Hyperscale facilities run the most formal programmes, with dedicated commissioning teams, extensive scripting and the owner's own standards layered over the industry frameworks.

Colocation facilities commission to a standard they can evidence to tenants, because the commissioning record becomes a sales document and a lease obligation.

Enterprise facilities commission to their own availability requirement, frequently with a smaller programme and an external CxA.

Edge and small facilities cannot economically support a full five-level programme. Levels 1, 3 and a reduced Level 5 covering the key failure scenarios is the practical minimum, and the scenarios chosen matter more than the level count.

Retrofit and live facility work is the hardest case, because the IST cannot drop a utility feed on a building carrying production load. Testing is done on isolated sections, in phases, with the limitation stated rather than hidden.

For shell scope, tier classification and density considerations that precede commissioning, see our guide to powered shell data centers. For how AI demand is reshaping facility requirements, see our analysis of AI and data centre power needs.

What Prismecs Does

Prismecs delivers installation and commissioning services for power infrastructure, covering electrical systems, controls, instrumentation and the energisation of generating plant.

Delivered project scope includes eight TM2500 dual-fuel units totalling 260 MW at Birr, Switzerland, commissioned and online in six months with a new 220 kV interconnection on a compact site; four TM2500 units totalling 110 MW at Duqm, Oman, kept grid-ready with resident O&M crews, CMMS and parts support; an LM2500XPRESS plant at Miaoli, Taiwan delivered in ten months; and an LM6000 fleet decommissioned in Norway, transported and recommissioned at a new site.

The Norway project is the relevant reference for commissioning discipline specifically. Decommissioning a fleet, transporting it and recommissioning it at a new site requires the same sequence this article describes, performed on machines that had already been in service.

Capability spans I&C services for installation, commissioning, controls and instrumentation, owner's engineering for independent technical representation and witnessing, EPCM services for project delivery, power generation asset services, O&M services for the operating phase, and data center solutions for the vertical.

One distinction worth stating plainly. The party executing commissioning and the party witnessing and accepting it should not be the same. Prismecs takes the delivery role or the owner's engineering role on a given project, not both.

Apply this article's criteria to any provider, including us. Ask who the commissioning authority reports to. Ask for a redacted IST script. Ask which failure scenarios are in scope, including the negative tests. Ask what you own at handover.

To discuss a commissioning scope, a witness programme or an independent review, send your facility capacity, redundancy standard, the commissioning levels in scope and your target energisation date to sales@prismecs.com or call +1 (888) 774-7632.

Frequently Asked Questions

What is commissioning in a data center?

A structured verification process that systematically tests, validates and documents every critical system including power distribution, cooling infrastructure, UPS units, switchgear and HVAC before a facility goes live, confirming all components perform as designed under both normal operating conditions and failure scenarios. It goes beyond installation sign-off, providing the operational evidence that a facility can sustain the uptime and compliance standards that Tier II through Tier IV facilities and their tenants contractually require.

What are the 5 levels of data center commissioning?

Level 1 is factory witness testing, verifying equipment against design specifications before shipping. Level 2 is site acceptance, confirming damage-free delivery. Level 3 is pre-functional testing, validating correct installation and safe energisation. Level 4 is functional performance testing, confirming each system performs under load on its own. Level 5 is the integrated systems test, running the whole plant at design load through scripted failures. Each level must pass before the next begins.

What is an integrated systems test?

The Level 5 commissioning test that runs the complete mechanical, electrical and controls plant under load banks at design load and injects failures, including utility loss, a chiller out of service and a chilled water loop removed, to prove the environment holds and every system responds as designed. It is the only test that proves systems working together rather than individually, which is why it is the keystone of the programme.

Why does Level 5 get compressed on late projects?

Because it is the only level that needs the whole plant, full load banks and a long block of uninterrupted time. Every other level can run in parallel with construction or in fragments between other activities. That makes Level 5 the obvious place to find schedule relief when a project runs late, and the worst place to find it, because the scenarios cut are usually the negative and restoration tests.

What is a black building or pull-the-plug test?

The IST scenario where the utility service is opened deliberately at the main switchboard while the facility carries full available load, simulating a real outage. The expected response is that the UPS holds the critical bus with no interruption, the generators start and accept load, and no critical equipment sees a break. Recorded results include actual bus behaviour, transfer time and time to generators carrying full load.

Why do you need reactive as well as resistive load banks?

Because a resistive load bank draws real power at unity power factor, which does not reproduce the power factor that real IT and mechanical load presents. Resistive and reactive load banks together pull the design kW and kVA from the power chain. A plant tested on resistive load alone has not been tested at the operating condition its UPS, generators and transformers will actually see in service.

What is step loading and why does it matter?

The test begins with no load bank load on the power distribution system, load is applied in steps until design electrical load is reached, then stepped back down the same way. Stepping exposes transient behaviour that steady-state testing hides. A generator that carries a fully applied load may misbehave on a step change, and a cooling plant stable at full load may not track a rapid change.

What is the Owner's Project Requirements document?

The written statement of what the owner needs the facility to do: availability, capacity, environmental conditions, redundancy, maintainability and the operating scenarios it must survive. ASHRAE Guideline 0 places it first because every commissioning test traces back to it. The verification chain runs OPR to Basis of Design to design to installation to test, so a deficiency is judged against whether the built plant satisfies the OPR rather than against opinion.

What does a commissioning authority do, and who should employ them?

The commissioning authority develops the commissioning plan, writes or reviews test procedures, witnesses tests, maintains the issues log and produces the final report. The strongest arrangement is appointment by and reporting to the owner, with the contractor executing tests and the CxA witnessing and accepting them. A CxA employed by the installing contractor is checking its own work, which should be a deliberate decision rather than a default.

Which standards govern data center commissioning?

ASHRAE Guideline 0 sets the commissioning process, the role of the commissioning authority, and the framework for the OPR, Basis of Design, commissioning plan, procedures and reports. ASHRAE Guideline 1.1 covers HVAC and refrigeration technical requirements. NFPA 110 governs emergency and standby power including start-and-transfer timing. NETA specifications cover electrical acceptance testing. Uptime Institute Tier standards drive certification testing where a Tier is claimed.

Is NFPA 4 integrated testing the same as a Level 5 IST?

No. NFPA 4 covers integrated testing of fire protection and life safety systems, which is a distinct requirement from the Level 5 integrated systems test of the power and cooling plant. Both may apply to the same facility, and they test different systems against different criteria. They are frequently conflated, and a specification naming one does not satisfy the other.

What does commissioning actually deliver to the owner?

The commissioning plan, test scripts and completed records for every level, the issues log recording every deficiency and its closure, the systems manual covering design intent and sequences of operation, training records, and the final report with level close-out reports. Establish ownership of all of it in native format, because the commissioning record is the facility's birth certificate and a purchaser who cannot see it discounts for the uncertainty.

When should commissioning start?

At design, not at energisation. A commissioning authority engaged during design reviews the specification for testability, ensures test ports and instrumentation are included, and establishes acceptance criteria while they can still be negotiated. One engaged at practical completion inherits whatever was built and tests it against criteria written after the fact, which removes most of the leverage the process is supposed to provide.

Why do commissioning programmes fail?

Four reasons, three of them schedule rather than technical. Level 5 gets compressed and the negative and restoration tests are cut. The plant is not actually complete, so the test proves the behaviour of a facility that will not exist at handover. Levels are run out of sequence, so single-system defects consume full-plant mobilisations. And the issues log is not maintained, leaving no record of what was found or whether it was retested.

Tags: Data Center Commissioning Integrated Systems Testing Load Bank Testing ASHRAE Guideline 0 Commissioning Authority