Data Center Commissioning: L1–L5 Levels, IST, and Acceptance

Learn how to structure Data Center commissioning, testing by stage, L1 to L5 levels, IST, evidence, and technical acceptance criteria.

Check it out!

Data Center commissioning is the structured verification process that follows requirements, design, manufacturing, installation, startup, functional testing, integrated testing, documentation, and transfer to operations. Its objective is to demonstrate, through traceable evidence, that the critical infrastructure was implemented according to owner requirements and can operate with safety, availability, performance, and recovery capability compatible with the project.

In Data Centers, the process must integrate power, cooling, automation, monitoring, fire protection, security, telecommunications, and operations. Individually approved equipment does not, by itself, demonstrate that the facility will respond correctly to loss of a source, removal of a component, degradation of capacity, or a contingency condition.

Therefore, technical acceptance does not arise from an isolated final test. It depends on a coherent chain of requirements, verifications, commissioning levels, readiness gates, results, open items, retests, documentation, and operational transfer. Levels L1 through L5 help organize this progression when they are contractually defined with clear entry and exit criteria.

What is Data Center commissioning?

Commissioning is a quality-oriented process that verifies and documents whether systems and assemblies have been planned, designed, installed, tested, operated, and prepared for maintenance in accordance with owner requirements. ASHRAE presents the commissioning process as a framework covering stakeholders, documents, specifications, procedures, verifications, and reports throughout the project phases.

In a Data Center, this approach must be multidisciplinary. ABNT NBR ISO/IEC 22237-1 structures the infrastructure considering availability, security, efficiency, operations, and management. The standard also addresses acceptance verification, testing, and commissioning during implementation until the Data Center becomes operational.

Within A3A Engenharia’s content architecture, the Complete Guide to Commissioning presents the general engineering process; here, the focus remains on application to Data Centers, progression through the levels, and readiness gates preceding acceptance.

Therefore, commissioning is not synonymous with:

visual inspection of the installation;
manufacturer-led startup;
isolated testing of a UPS, generator, or chiller;
energization of the infrastructure;
informal demonstration to the owner;
issuance of a final report without traceability;
construction rework or punch-list management without functional verification.

These activities may be part of the process, but they do not represent it in full.

What is Integrated Systems Testing?

Integrated Systems Testing verifies whether different systems respond together to events defined in the requirements, design, operating sequences, and approved procedures. The test should not be limited to demonstrating that each piece of equipment turns on or off; it must evaluate the interfaces that support the critical function.

A source-loss scenario, for example, may simultaneously involve:

event detection;
protective device operation;
power transfer;
support by UPS systems and batteries;
generator start and stabilization;
behavior of priority and non-priority loads;
continuity of cooling;
state updates in the EPMS, BMS, or DCIM;
alarm generation and prioritization;
operations team response;
controlled return to normal condition.

The purpose of IST is not to create random failures. Scenarios must derive from requirements, operating modes, risk analyses, functional diagrams, and response procedures. Each event must have preconditions, limits, participants, abort criteria, and a safe restoration method.

In this article, IST is treated as the integrated gate of the commissioning program. The specific methodology for building scenarios, instrumentation, execution, evidence, and retesting is explored in the content on Integrated Systems Testing in Data Centers, avoiding duplication of two pages for the same intent.

Is L1 to L5 a normative classification?

There is no universal and mandatory correspondence between the numbers L1, L2, L3, L4, and L5 and a single set of activities. The numbering is widely used in Data Center programs, but the content of each level may vary among owners, consultants, contractors, operators, and contracts.

JLL, for example, presents an expanded sequence of seven stages, with L0 for programming and design, L1 for factory acceptance, L2 for site acceptance, L3 for startup and pre-functional checks, L4 for functional testing, L5 for integrated testing, and L6 for transition to operations. This reference is useful for understanding the use of levels, but it does not make the nomenclature a universal requirement.

ASHRAE Guideline 0 and ASHRAE/IES Standard 202 structure the process by phases, responsibilities, documentation, verification, and acceptance. ABNT NBR IEC 62337 organizes milestones such as erection completion, mechanical completion, pre-commissioning, commissioning, performance testing, and acceptance. None of these references should be cited as the mandatory source of a specific L1–L5 table.

Therefore, the contract and commissioning plan must declare the meaning of each level for the project, the systems and equipment included, the documents and tests that constitute each gate, the responsibilities for execution, witnessing, recommendation, and approval, the treatment of open items and exceptions, and the objective conditions that allow progression to the next level.

Recommended level mapping

The following table presents a reference structure. It must be adapted to the project.

Level	Primary objective	Examples of activities	Exit gate
L0	Plan commissioning and ensure testability	OPR/URS, BoD, design review, test matrix, instrumentation, access, and load-bank requirements	Verifiable requirements and commissioning incorporated into contracts
L1	Verify equipment before shipment	FAT/FWT, document inspection, certificates, factory tests, control simulations	Equipment released for shipment with controlled deviations
L2	Verify receipt, preservation, and installation	transport inspection, tags, storage, assembly, connections, torque, cleaning, calibration	Installation documented and ready for startup
L3	Perform startup and pre-functional tests	controlled energization, rotation checks, loops, sensors, basic interlocks, TAB, adjustments	System stable and ready for functional testing
L4	Demonstrate functional system performance	load tests, normal/abnormal modes, redundancy within the system, sequences, and alarms	Individual systems accepted for integration
L5	Demonstrate integrated facility behavior	IST, contingency scenarios, transfer, component failure, recovery, and operational response	Evidence that the Data Center meets integrated requirements
L6, when adopted	Transfer and stabilize operations	training, SOP/MOP/EOP, Systems Manual, assisted operations, deferred tests	operational readiness and controlled closeout

The value of the structure is not in the number. It is in transforming each level into an auditable gate in which inputs, procedures, results, open items, and decisions are formally recorded.

The commissioning plan must transform L1 through L5 into verifiable gates.

A3A Engenharia structures levels, responsibilities, procedures, evidence, treatment of open items, and acceptance criteria so that IST is prepared from requirements and design onward.

Structure Data Center levels, integrated tests, and acceptance criteria

L0: commissioning starts before construction

Although many contracts begin counting at L1, the process must start during the requirements and design phase. Without this preparation, the infrastructure may be technically impossible to test, or the tests may fail to demonstrate the required performance.

Owner requirements

The Owner’s Project Requirements, URS, or equivalent document must convert business objectives into measurable criteria. It is not enough to state that the Data Center must be “highly available.” Capacities, loads, autonomy, maintenance modes, environmental limits, response times, alarms, recovery, documentation, and acceptance conditions must be defined.

These documents are explored in greater depth in the article Basis of Design, OPR, and URS in Data Center projects.

Basis of Design and sequences

The BoD must explain how the proposed solution meets the requirements. For commissioning, the following are particularly important:

block diagrams and single-line diagrams;
normal, maintenance, contingency, and emergency modes;
operating sequences;
protection and selectivity philosophy;
control and monitoring architecture;
permissives, interlocks, and priorities;
capacity and redundancy criteria;
load and environmental assumptions;
measurement points and alarms;
known limitations.

Testability

A testable design provides safe means to observe, measure, and control the system. Items to assess include:

access and space for instruments;
load-bank connection points;
temporary and permanent metering;
ability to simulate states without compromising protection;
trending in BMS, EPMS, and DCIM;
clock synchronization across platforms;
consistent equipment and signal identification;
ability to isolate sectors and phases;
return conditions after testing;
compatibility between procedures and manufacturer warranties.

When these conditions are not incorporated into design and procurement, commissioning becomes dependent on field improvisation.

L1: FAT and verification before shipment

Level L1 normally concentrates tests performed at the factory or before equipment is released for shipment. Its objective is to identify deviations while the manufacturer still has the facilities, tools, and personnel to correct them with less impact on construction.

The scope varies by equipment. It may include:

review of approved submittals and drawings;
verification of model, capacity, and accessories;
material and calibration certificates;
assembly and workmanship inspection;
verification of panels, busbars, and connections;
specified electrical or mechanical tests;
simulation of inputs, outputs, and logic;
communication using defined protocols and platforms;
response to alarms and interlocks;
load testing, when applicable;
recording of firmware and configurations;
documentation of deviations and open items.

ABNT NBR IEC 62337 recognizes the importance of factory acceptance testing and control-system integration. However, FAT does not demonstrate actual installation conditions. Cables, upstream and downstream protection, utilities, environment, integration, and operations are not yet fully represented.

L1 gate

Release for shipment should occur only after the procedure has been approved, the instruments used are valid and calibrated, results have been recorded, and deviations have been classified. Open items must have an owner and deadline, documentation must reflect the tested configuration, and preservation and transportation conditions must be defined. The gate ends with a formal decision: release, conditional release, or rejection of the supply.

L2: receipt, preservation, and installation verification

L2 confirms that the received supply matches what was approved, has not suffered relevant damage, and was installed according to the design, manufacturer instructions, and applicable requirements.

This stage must prevent physical issues from progressing to startup. Receiving inspection must identify transportation or lifting damage, supplies that differ from the approved submittal, missing accessories, and preservation failures. After installation, verification must confirm connections, identification, grounding and bonding, sensor position, compatibility of cables, piping, and ducts, maintenance access, and consistency between the installation and record drawings.

ABNT NBR IEC 62337 links mechanical completion to erection verification, test reports, the punch list, and certificate issuance. This logic is directly useful for Data Centers: equipment should only be declared ready for startup when installation checks are complete and critical open items are controlled.

Checklists do not replace evidence

Checking “yes” on a list is not sufficient when the requirement calls for a measurement, photograph, certificate, torque record, curve, trend, or report. The checklist should identify the associated evidence and the person responsible for verification.

L3: startup and pre-functional testing

L3 is the transition from a static installation to the initial operating condition. Manufacturers and contractors normally perform startup and adjustments, while the commissioning team verifies compliance with the procedure and records results.

Typical activities include:

confirmation of energization prerequisites;
verification of power supply and protection;
startup and shutdown sequence;
sensor calibration and validation;
loop and point testing;
rotation and flow direction;
protection and control adjustments;
flushing, cleaning, or conditioning when applicable;
TAB of cooling systems;
validation of local alarms;
basic communication with supervisory systems;
updating parameters and documentation.

The L3 exit condition should not merely be “equipment energized.” The system must be stable, adjusted, and documented so that L4 performance testing is valid.

Conditions that prevent progression

protection settings not approved;
uncalibrated instruments;
recurring communication failures;
leaks or mechanical anomalies;
masked alarms without formal control;
unversioned software or firmware;
unavailable trends;
open items that affect capacity or sequencing;
absence of emergency procedures;
operations still dependent on improvised interventions.

L4: functional testing by system

At L4, each system is subjected to conditions that demonstrate its function and performance. ASHRAE Guideline 0 distinguishes component tests, system tests, intersystem tests, and owner-requirement-oriented tests. In an L1–L5 program, L4 normally covers most discipline-level functional testing and prepares the interfaces for IST.

Electrical system

The scope may include:

power sources and service entrances;
transformers and switchboards;
protection, selectivity, and interlocks;
ATS, STS, and transfers;
UPS systems, batteries, and autonomy;
generators and auxiliary systems;
A/B distribution;
PDU, RPP, and busways;
grounding and bonding;
metering and EPMS.

Cooling and environmental control

chillers or direct-expansion systems;
pumps, towers, and heat rejection;
CRAH, CRAC, and precision units;
valves, dampers, and controls;
containment and airflow management;
environmental sensors;
response to load variations;
redundancy and rotation;
alarms and BMS integration.

Automation, BMS, EPMS, and DCIM

point mapping;
quality and units of variables;
alarms and priorities;
trends and history retention;
time synchronization;
permissions and profiles;
communication states;
screens, diagrams, and navigation;
integration among platforms;
behavior during communication loss and restoration.

Fire protection, security, and telecommunications

Commissioning must also cover relevant functions of fire detection and alarm, suppression, access control, video surveillance, intrusion detection, management networks, cabling, and emergency interfaces. Each system may be subject to its own standards and authorities; IST must respect these responsibilities and does not replace legal or regulatory acceptance.

L4 gate

The system should only be released for integration when:

planned functional tests have been executed;
capacity and performance have been demonstrated;
sequences and alarms have been verified;
critical failures have been corrected and retested;
configurations are under version control;
interfaces are ready;
field documentation matches the installed condition;
operations understands temporary limitations.

Data Center testability must be designed, not improvised during L5.

Measurement points, load banks, trends, sequences, access, isolation conditions, and return conditions must be incorporated into design and specifications before procurement and construction.

Design infrastructure already prepared for testing, integration, and acceptance

L5: Integrated Systems Testing

L5 must verify the facility as a system of systems. The script must represent events relevant to Data Center risk, rather than simply repeating equipment tests.

Scenario families

An IST matrix may include:

normal operation: stable conditions, scheduled rotation, capacity modulation, and monitoring;
planned maintenance: controlled removal of elements, path transfer, and return;
source or component failure: loss of power, equipment, or communication defined by the design;
degradation: reduced capacity without immediate loss of the critical load;
emergency: events that trigger protection and response procedures;
recovery: return to normal condition, restoration of redundancy, and alarm handling;
operational interface: human action according to SOP, MOP, or EOP;
combined scenarios: only when planned, technically justified, and safe.

What IST should observe

continuity of the critical function;
response and transfer times;
operation of protection devices;
stability after the event;
remaining capacity;
cooling sequence;
load prioritization;
correct, intelligible, and properly timed alarms;
consistency between local and supervisory states;
absence of hidden conditions;
team response;
ability to return safely;
complete chronological record.

IST is not a staged demonstration

A test may appear successful and still produce insufficient evidence. This occurs when:

the scenario is known only verbally;
expected results were not defined;
alarms were disabled without records;
equipment was manually operated outside the designed sequence;
trends were unavailable;
the test load did not represent the intended condition;
corrective intervention occurred during the scenario without an issue being opened;
only the final result was recorded;
intermediate failures were ignored because the load remained energized.

IST must demonstrate not only that “nothing went down,” but that the facility responded according to the requirements, architecture, and procedures.

Prerequisites for starting IST

Before authorizing L5, a formal readiness review should be performed. The minimum list includes:

updated OPR/URS and BoD;
requirements and test matrix;
approved diagrams and sequences;
systems in representative condition;
L1 through L4 completed according to the plan;
reports and certificates available;
classified punch list;
critical issues closed;
instruments and load banks available;
valid calibration;
operational monitoring and trending systems;
verified time synchronization;
approved procedures;
activity risk assessment;
participants and authorities confirmed;
communication plan;
abort criteria;
restoration plan;
compliance with manufacturer recommendations;
operations team trained for the scenario.

The presence of an open item does not automatically prevent IST. The decisive point is whether it compromises safety, representativeness, observability, capacity, sequence, or recovery. This assessment must be recorded.

How to structure a test script

The procedure must be detailed enough to allow controlled execution, repeatability, and auditability. A recommended structure includes:

Field	Expected content
Identification	code, revision, system, scenario, and associated requirement
Objective	function to be demonstrated
Scope	systems, areas, equipment, and interfaces included
References	OPR, BoD, diagrams, sequences, manuals, and standards
Participants	executor, operator, CxA, OE, designers, manufacturers, and witnesses
Preconditions	states, loads, availability, permissions, and accepted open items
Instrumentation	equipment, range, accuracy, calibration, and responsible party
Safety	risks, controls, limits, abort, and restoration
Steps	numbered actions without ambiguous commands
Expected result	observable response of each system and interface
Acceptance criterion	required tolerance, time, capacity, state, or evidence
Record	measurements, trends, photos, logs, alarms, and signatures
Issues	rule for interruption, classification, correction, and retesting
Closeout	return to normal, restoration of redundancy, and release

ASHRAE Guideline 0 recommends that procedures identify participants, prerequisites, steps, restoration, instruments, observations, and acceptable ranges. It also requires deviations from the procedure to be documented and test and retest results to remain recorded.

Instrumentation, load banks, and observability

The IST result depends on the ability to measure what occurred. Instrumentation must be selected according to the relevant variables and response times.

The following may be required:

power quality analyzers;
electrical parameter data loggers;
thermography;
temporary temperature and humidity sensors;
flow, volume flow, and pressure measurement;
resistive or reactive load banks according to the objective;
authorized signal simulators or tools;
protection-event capture;
export of BMS and EPMS trends;
logs from DCIM and security platforms;
video records of field conditions.

Selection should not be based solely on instrument availability. Range, resolution, accuracy, sampling time, calibration, and synchronization must be compatible with the observed phenomenon.

Test load

The load must represent the objective of the scenario. Testing a sequence at a load far below the intended condition may hide thermal limitations, autonomy times, generator behavior, or transfer capacity. Conversely, increasing load without risk analysis and without safe conditions can endanger equipment and people.

The plan should establish:

power and load profile;
physical and electrical distribution;
duration;
environmental condition;
increments and stabilization;
interruption limits;
parties responsible for connection, operation, and removal;
compatibility with equipment and warranties.

Abort and restoration criteria

Every scenario must have objective criteria for stopping the test. Conceptual examples include safety risk, behavior outside approved limits, loss of observability, inability to recover redundancy, or unexpected operation that makes continuation of the script invalid.

Aborting does not automatically mean failing the entire facility. It means the scenario is no longer safe or representative. The team must:

stabilize the system;
record the interruption point;
open an issue;
preserve logs and trends;
identify the impact;
define the correction and retest prerequisites;
approve a new execution.

The restoration plan is as important as the failure sequence. The Data Center must return to a known condition, with redundancy restored, alarms handled, configurations verified, and operations formally informed.

Safety during integrated testing

IST must not be treated as an exclusively documentary activity. Scenarios may involve power, rotating equipment, pressurized systems, fuels, batteries, heat, fire alarms, and temporary changes in redundancy.

The process must integrate:

task risk assessment;
applicable permits and lockout procedures;
limits of responsibility;
communication with operations and safety teams;
presence of required specialists;
manufacturer recommendations;
protection of people and equipment;
emergency plan;
control of temporary changes;
confirmation of return to the normal configuration.

The commissioning procedure must never be used to bypass safety requirements, legal responsibilities, or equipment operating limits.

Traceability matrix

Traceability connects what the owner requested to what was actually demonstrated.

Element	Example link
Requirement	critical load must remain supported during the defined event
BoD	architecture and sequence selected to meet the requirement
Design document	applicable single-line diagram, logic, diagram, and specification
Procedure	script that creates the condition and measures the response
Result	data, trends, times, states, and observations
Issue	deviation identified during testing
Correction	action performed by the responsible party
Retest	new evidence after correction
Acceptance	formal decision and associated residual risk

Without this chain, the report may prove that activities were performed, but not that requirements were met.

Issue, punch-list, and retest management

Not every open item has the same effect on acceptance. Classification should consider safety, continuity, capacity, redundancy, compliance, operations, documentation, and recurrence risk.

One possible structure is:

Class	Typical effect	Treatment
Critical	compromises safety, essential function, or test validity	prevents progression or acceptance until correction and retest
Major	reduces capacity, redundancy, performance, or recovery capability	requires a formal decision; generally requires correction before final acceptance
Minor	does not compromise the primary function but requires regularization	may allow conditional acceptance with deadline and responsible party
Documentary	incomplete evidence, drawing, manual, or record	assess impact on operations, maintenance, and traceability
Improvement	recommendation without requirement noncompliance	record separately to avoid confusion with a nonconformity

ABNT NBR IEC 62337 associates the punch list with incomplete work, repairs, and adjustments, providing for repeated verification until resolution. ASHRAE Guideline 0 requires previous failed tests to remain in the report in addition to the final accepted result.

Retest

The retest must verify the correction and the risk of side effects. Depending on the change, it may be necessary to repeat:

only the affected step;
the entire system procedure;
related integration scenarios;
previous tests whose validity was compromised;
the configuration or performance baseline.

The decision must be technical and documented, not based only on the construction schedule.

Technical acceptance criteria

Acceptance is not synonymous with the absolute absence of open items. It is a decision based on requirements, evidence, responsibilities, and residual risk.

Level acceptance

Each level must have its own criteria. Examples include:

planned documents delivered;
tests executed and passed;
critical open items closed;
deviations accepted by the competent authority;
signed records;
configuration frozen or controlled;
safe condition for progression.

Provisional or conditional acceptance

It may apply when the primary function has been demonstrated but controlled open items remain. The acceptance record should indicate:

remaining items;
technical impact;
temporary controls;
responsible parties;
deadlines;
retentions or contractual conditions;
deferred tests;
condition for final acceptance.

Final acceptance

It requires verification that obligations, corrections, documents, training, tests, and deliverables have been completed in accordance with the contract. The decision must also consider operations and maintenance, not only construction.

The topic is explored in greater depth in Engineering Acceptance Criteria.

Residual risk

Even after commissioning, known limitations may remain. Residual risk must be made explicit, assessed, and accepted by the owner — not hidden in scattered observations.

The record should indicate:

affected requirement;
observed condition;
probability and consequence;
remaining capacity or redundancy;
compensating control;
operational restriction;
correction deadline;
authority that accepted it;
need for monitoring or retesting.

The commissioning authority may recommend acceptance or rejection; Owner’s Engineering may assess impacts and protect the owner’s interests; but business risk tolerance remains with the owner.

Responsibilities in Data Center commissioning

Party	Primary responsibility
Owner	approve requirements, provide representatives, decide on risk, and accept deliveries
Owner’s Engineering	technically represent the owner, review requirements, interfaces, changes, evidence, and recommendations
Commissioning authority	plan, coordinate, witness, verify, record, and report the process
Designers	remain responsible for solutions, BoD, sequences, calculations, and design corrections
Project management	integrate schedule, cost, contracts, communication, and project milestones
Contractors and integrators	execute, control quality, complete checklists, correct deviations, and operate systems during testing
Manufacturers	provide documentation, startup, assistance, testing, and warranty requirements
Operations	participate in requirements, procedures, testing, training, handover, and operational acceptance
Authorities having jurisdiction	perform applicable legal or regulatory approvals

The project RACI matrix must detail who performs, who has final accountability, who is consulted, and who is informed for each deliverable and test.

Owner’s Engineering and commissioning are not the same function

The OE protects the owner’s requirements, decisions, and interests throughout the project. The commissioning authority leads the verification process according to the approved scope. The functions may work in an integrated manner, but their boundaries must be clear.

The topic is explored specifically in Owner’s Engineering in Data Centers.

In practical terms:

the OE helps convert requirements into contractual obligations;
the CxA structures the plan, checklists, and tests;
designers define solutions and sequences;
contractors execute and correct;
operations participates in scenarios and receives the asset;
the owner decides on acceptance and residual risk.

Operations must participate before L5

The operations team should not become familiar with the facility only at handover. ABNT NBR ISO/IEC 22237-1 recommends that processes, roles, and responsibilities be defined before operation and that personnel be instructed and trained during acceptance testing.

Participation should include:

review of operating modes;
validation of alarms and priorities;
development of SOP, MOP, and EOP;
observation of startup and functional testing;
participation in IST;
hands-on training;
access to the Systems Manual;
understanding of limitations and open items;
ability to restore normal condition;
knowledge of escalation and support.

A test may demonstrate technical performance and still reveal low operational readiness. This condition must be addressed before final transfer.

Systems Manual and handover documentation

Final documentation must function as an operations resource, not merely as a contractual archive. ASHRAE Guideline 0 recommends a Systems Manual that brings together the OPR, BoD, commissioning plan and report, manuals, schematics, record drawings, tests, operating procedures, maintenance, and training.

For Data Centers, the package may include:

document index and matrix;
final requirements and approved deviations;
diagrams and as-built drawings;
relevant configurations and versions;
protection studies and settings;
L1 through L5 reports;
issue logs and punch list;
certificates and calibrations;
trends and load-test results;
SOP, MOP, and EOP;
maintenance plans;
spare-parts lists;
contacts and warranties;
training and attendance records;
limitations and residual risk;
deferred tests and planned dates.

Deferred tests

Some tests may depend on ICT load, environmental conditions, utility availability, or an operating window that does not yet exist. Deferring a test does not mean waiving it.

The report should record:

deferred test;
justification;
required precondition;
risk of operating before the test;
temporary control;
responsible party;
deadline or trigger;
contractual condition;
method for subsequent execution and acceptance.

Commissioning during expansion or modernization of an operational Data Center

In operational facilities, the process must protect the existing load. Planning must consider boundaries, maintenance windows, rollback, temporary redundancy, communication, permissions, and the risk of interaction with legacy systems.

Good governance practices include:

reliable survey of the existing condition;
validation of actual diagrams and configurations;
segregation between new and existing systems;
offline testing whenever possible;
phased implementation with gates;
impact analysis for each energization;
approved MOP for interventions;
contingency and rollback;
enhanced monitoring after changes;
assisted operations.

The Data Center and CPD Diagnostics and Modernization page presents the preceding stage required to structure this type of intervention.

Process indicators

Monitoring should not be limited to the number of tests executed. Useful indicators include:

Indicator	Interpretation
requirements covered by tests	measures traceability and gaps
approved versus planned procedures	indicates execution readiness
first-pass approval rate	reveals design, installation, and preparation quality
issues by system and criticality	shows concentration of risk
average resolution time	indicates response capability
recurrence after retest	evaluates effectiveness of corrections
tests blocked by prerequisites	highlights planning problems
open items at handover	measures risk transferred to operations
training completed by role and shift	measures operational readiness
deferred tests	identifies coverage not yet demonstrated

Indicators do not replace technical analysis. A high approval rate may result from superficial testing; a lower initial rate may indicate a rigorous process that detected and corrected problems before operations.

Common mistakes

engaging commissioning only at the end of construction;
adopting L1–L5 without defining the content of each level;
confusing FAT, SAT, startup, functional testing, and IST;
starting L5 with critical open items or without observability;
using generic scripts with no link to OPR and BoD;
testing equipment but not interfaces;
executing scenarios without abort and restoration criteria;
allowing temporary changes without configuration control;
accepting checklists without evidence;
excluding operations from the process;
recording only the passing test and deleting previous failures;
releasing the asset without a usable Systems Manual;
treating residual risk as an informal observation;
failing to provide for retests and repetition costs in contracts;
confusing technical acceptance with automatic release of all contractual obligations.

Executive Data Center commissioning checklist

Before authorizing IST, confirm:

Are the requirements measurable and linked to tests?
Do the BoD and sequences reflect the current installation?
Is the level nomenclature defined in the contract?
Do L1 through L4 have approved gates and reports?
Have systems been individually tested under representative conditions?
Are the interfaces documented?
Has the punch list been classified by criticality?
Are there no open items that invalidate the scenario?
Are configurations controlled?
Are instruments and load banks appropriate?
Are calibrations valid?
Do BMS, EPMS, and DCIM record trends and events?
Are system clocks synchronized?
Does the script include expected results and tolerances?
Are abort criteria defined?
Is there a restoration plan?
Do participants have the required authority and competence?
Does operations understand and participate in the scenario?
Have risks and safety measures been approved?
Is the recording and sign-off method defined?
Do issues and retests have a formal workflow?
Is the person responsible for acceptance identified?
Will residual risk be documented?
Do deferred tests have a plan and deadline?
Does handover have its own deliverables and criteria?

Data Center acceptance requires technical governance beyond the execution of tests.

Requirements, interfaces, changes, issues, retests, residual risk, and decisions must remain traceable on behalf of the owner throughout the implementation cycle.

Keep requirements, risks, and acceptance decisions under owner governance

A3A Engenharia’s consulting engineering scope

A3A Engenharia can structure and support Data Center commissioning from requirements and design through implementation, integrated testing, acceptance, and operational transition. The scope must be defined according to criticality, architecture, contracting model, project phase, and the responsibilities of the other parties.

The work may cover:

review of OPR, URS, and BoD;
design review focused on testability;
commissioning plan and matrix;
definition of levels, gates, and deliverables;
review of FAT, SAT, and functional procedures;
preparation or review of IST scripts;
interface and traceability matrix;
test oversight and witnessing;
technical management of issues and retests;
assessment of acceptance criteria;
technical opinions for the owner;
handover and operational-readiness audit;
integration with Owner’s Engineering and assisted operations.

Execution responsibility and technical authorship remain with the corresponding contractors and designers. Decision-making authority and approval limits must be defined in the contract and project governance.

Technical summary

Data Center commissioning should operate as a continuous process, from requirements and design through testing, documentation, and transfer to operations. Levels L1 through L5 must function as documented gates, not labels. Requirements, manufacturing, installation, startup, functional testing, IST, instrumentation, safety, issues, retests, documentation, and operations must form a traceable chain.

The numerical sequence is not universal. Therefore, the commissioning plan must define the content of each level, responsibilities, evidence, and progression criteria. Technical acceptance is defensible only when the owner can link requirements to procedures, results, open items, corrections, retests, and residual risk.

Technical references

[1] ABNT. ABNT NBR ISO/IEC 22237-1:2023 — Information technology — Data centre facilities and infrastructures — Part 1: General concepts. Rio de Janeiro: Associação Brasileira de Normas Técnicas, 2023.

[2] ABNT. ABNT NBR IEC 62337:2020 — Commissioning of electrical, instrumentation and control systems in the process industry — Specific phases and milestones. Rio de Janeiro: Associação Brasileira de Normas Técnicas, 2020.

[3] ASHRAE. Guideline 0-2019 — The Commissioning Process. Atlanta: American Society of Heating, Refrigerating and Air-Conditioning Engineers, 2019.

[4] ASHRAE. Standard 202-2024 — The Commissioning Process Requirements for New Buildings and New Systems. Atlanta: American Society of Heating, Refrigerating and Air-Conditioning Engineers, 2024.

[5] AABC COMMISSIONING GROUP. ACG Commissioning Guideline for Building Owners, Design Professionals and Commissioning Service Providers. Washington, DC: ACG, 2005.

[6] JLL. Do you know the seven stages of data center commissioning? Feb. 17, 2025. Available at: https://www.jll.com/en-us/guides/do-you-know-the-seven-stages-of-data-center-commissioning. Accessed: Jul. 27, 2026.

[7] JLL. Commissioning strategies to ensure uninterrupted data center performance. 2024. Available at: https://www.jll.com/en-de/insights/commissioning-strategies-to-ensure-uninterrupted-data-center-performance. Accessed: Jul. 27, 2026.

[8] TIA. ANSI/TIA-942-C — Telecommunications Infrastructure Standard for Data Centers. Arlington: Telecommunications Industry Association, 2024.

[9] UPTIME INSTITUTE. Data Center Site Infrastructure Tier Standard: Operational Sustainability. New York: Uptime Institute.

[10] A3A ENGENHARIA. FAT, SAT and Integrated Testing in Critical Systems: how to validate deliveries before technical acceptance. Ponta Grossa: A3A Engenharia, 2026.

Frequently asked questions

What is IST in Data Centers?

IST is Integrated Systems Testing, the stage that verifies the coordinated behavior of critical infrastructure under normal, abnormal, contingency, and recovery scenarios.

What is the difference between IST and SAT?

SAT verifies field acceptance of a piece of equipment or system. IST evaluates interaction among multiple systems and the Data Center’s ability to meet integrated requirements.

Are L1 through L5 defined by ABNT or ASHRAE?

Not as a universal table. The standards structure the process, phases, testing, documentation, and acceptance. The plan and contract must define the content of each level.

What is normally tested at L5?

Integration scenarios involving power, UPS systems, batteries, generators, distribution, cooling, automation, alarms, monitoring, security, and operational response.

Can IST be performed with open items?

Only when the open items have been classified, do not compromise safety or scenario validity, and formal approval to proceed has been granted.

Who should execute commissioning tests?

Contractors and manufacturers normally operate the systems. The commissioning authority coordinates, witnesses, and documents; designers, OE, operations, and the owner participate according to the responsibility matrix.

What are the main prerequisites for IST?

Updated requirements and designs, completion of previous levels, stable systems, approved procedures, valid instrumentation, observability, risk assessment, abort criteria, and a restoration plan.

What should an IST script contain?

Objective, scope, references, participants, preconditions, instrumentation, risks, steps, expected results, tolerances, evidence, abort criteria, restoration, and issue handling.

How should a failure during IST be handled?

The system must be stabilized, the occurrence recorded, data preserved, the issue classified, the correction defined, and the retest planned according to the impact.

What is the difference between Owner’s Engineering and the commissioning authority?

OE technically represents the owner and evaluates requirements, interfaces, changes, and risks. The commissioning authority leads the verification process according to the approved plan.