Critical Power Systems Awareness

Introduction

Operational and User Acceptance Testing (UAT) represents the final technical and functional validation before a data centre’s critical power systems are accepted by the client for live operation. 

This stage ensures that every subsystem, from Uninterruptible Power Supply (UPS) strings and generator sets to Power Distribution Units (PDUs) and Automatic Transfer Switches (ATS), performs according to the design intent, resilience strategy, and operational sequence of events (SoE). 

UAT demonstrates to the client that the integrated power infrastructure is safe, resilient, maintainable, and aligned with both performance and redundancy expectations.

Following the completion of factory, site, and integrated systems testing, UAT transitions the focus from installation verification to operational performance under real-world conditions. 

It involves detailed scenario simulations, redundancy failover checks, alarm verifications, and client-driven functional testing against predefined acceptance criteria. 

Proper execution of this stage is crucial to securing client confidence and validating readiness for handover.

‍

12.3.1 Purpose and Scope of UAT

The purpose of UAT is to confirm that the installed critical power infrastructure meets operational, safety, and functional requirements under realistic load and fault conditions. 

It provides the final opportunity to validate how systems behave when operated by end users rather than commissioning engineers.

Key scope areas include:

• Verification that electrical distribution aligns with single-line diagrams and load design intent.
• Validation of switchgear and UPS operations under simulated mains failure, battery discharge, and generator start sequences.
• Assessment of system behaviour during automatic and manual transfer events between A and B supply paths.
• Confirmation that safety interlocks, alarms, and Building Management System (BMS) integrations function correctly.
• Confirmation that operational documentation, labels, and emergency procedures are clear and accessible for client teams.

Each test must align with pre-approved UAT scripts that detail the test intent, method, expected result, and success criteria.

‍

12.3.2 Structure and Methodology of Testing

UAT should be structured around progressive testing layers, building on prior commissioning evidence. 

These layers include:

1. Subsystem Verification – Ensuring individual systems (e.g. UPS, generator, ATS) operate to specification before integration.
   
   
2. System Integration Testing – Assessing how systems interact, ensuring control signals, synchronisation, and alarms align correctly.
   
   
3. Operational Scenarios – Simulating real-life conditions such as loss of utility, generator start-up, load transfers, and maintenance bypass.
   
   
4. Client Observed Demonstrations – Allowing the end user to witness tests under controlled conditions, confirming usability and performance.
   
   
5. Sign-Off and Data Capture – Documenting test results, deviations, and corrective actions in a structured UAT report for client approval.
   
   

All testing must be witnessed by client representatives, commissioning managers, and relevant trade supervisors, ensuring transparency and shared confidence in outcomes.

‍

12.3.3 Test Documentation and Traceability

Test documentation is a critical element of UAT, providing traceability between the design intent, installation verification, and operational validation. 

Documents typically include:

• UAT Plan and Schedule: 

Defines testing phases, sequence, and dependencies.

• UAT Scripts: 

Detail each test case, acceptance criteria, and responsible parties.

• UAT Logbook: 

Captures real-time data during testing, including instrument readings and observations.

• Defect and Issue Register: 

Tracks any non-conformances, corrective actions, and retest requirements.

• Client Sign-Off Forms: 

Serve as formal confirmation that each test has met its criteria.

All documentation must align with the project’s Quality Management System (QMS) and be stored in a centralised Common Data Environment (CDE). 

Accuracy and consistency in these records are essential, as they form part of the client’s operational evidence during audits or warranty claims.

‍

12.3.4 Integration with Other Systems

Critical power systems rarely operate in isolation. 

UAT must therefore verify integration across mechanical, IT, and monitoring systems to ensure end-to-end functionality. 

This includes:

• BMS/BEMS (Building Management/Environmental Management Systems): 

Verification that power alarms and trends are accurately captured.

• Fire Detection and Suppression Systems: 

Ensuring interlocks between electrical shutdowns and fire protection sequences.

• Critical Cooling Systems: 

Confirming that generator or UPS events do not disrupt essential cooling supply.

• DCIM (Data Centre Infrastructure Management) Platforms:

Validating real-time visibility of load and capacity monitoring.

Integration testing ensures that power continuity is not compromised during cross-system events and that client operations teams can trust monitoring outputs for real-time decision-making.

‍

12.3.5 Client Engagement and Acceptance Criteria

Client engagement during UAT is both technical and psychological. 

It allows the client to witness resilience under stress conditions and gain confidence in the installation. 

Acceptance criteria must be measurable, transparent, and derived directly from the project specification and commissioning plan.

Acceptance typically includes confirmation that:

• All test cases are executed successfully without unresolved defects.
• Alarms, interlocks, and control logic operate as designed.
• Power transitions occur seamlessly without equipment trips or data loss.
• Documentation is complete, signed, and collated into the handover pack.
• Operations personnel can safely replicate key procedures demonstrated during UAT.

Client sign-off marks the transition from construction-led verification to operational ownership, formally acknowledging that systems meet the agreed design intent.

‍

12.3.6 Lessons Learned and Continuous Improvement

Following UAT completion, a structured lessons-learned review must be conducted. 

This should capture performance insights, design feedback, and opportunities for improving test execution efficiency on future projects. 

Typical focus areas include:

• Testing durations and sequencing efficiency.
• Communication between commissioning, operations, and client teams.
• Effectiveness of contingency planning during live simulation tests.
• Clarity and usability of operational documentation.

Capturing these insights ensures that each project contributes to continuous improvement in both engineering delivery and client satisfaction.

‍

With operational functionality now verified and formally accepted, the next phase focuses on empowering the client’s operations personnel. 

Section 12.4 explores how structured training, detailed knowledge transfer, and shadowing programmes ensure that the client’s team can manage, maintain, and respond to critical power events with full confidence. 

This training is not merely a handover formality—it is a strategic investment in operational excellence and resilience continuity.

‍