SLA Evidence Chain
N+1 on a Drawing Is Not Enough; Loaded Testing Reveals Real Weaknesses
N+1 redundancy on data center drawings cannot replace a real loaded test. Starting, transfer, load sharing, cooling, fuel, low-voltage distribution and alarm coordination expose their weaknesses only under conditions close to real operation.
Probable Causes
Many Faults Do Not Appear During No-Load Testing
A no-load test proves that the generator can start, but not that load steps, cooling recovery, fuel consumption, paralleling load sharing and the transfer chain are reliable under real load. Without records, risk remains hidden until a real outage.
Real Load Reveals Transient Problems
Voltage and frequency fluctuation, trips, load-sharing faults and cooling-start impact require loaded operation to verify.
Interdependent Systems Must Be Tested Together
UPS, ATS/STS, low-voltage distribution, cooling, fuel and monitoring cannot be proven in isolation.
Correction and Retesting Close the Loop
One test is not enough; every abnormal item must be corrected and confirmed by retesting.
Diagnostic Process
Engineers Design the Test as Auditable Reliability Evidence
- 01
Confirm the test objective, load level, maintenance window, safe isolation and rollback plan.
- 02
Record operating curves for generators, paralleling, ATS/STS, low-voltage distribution, cooling and fuel.
- 03
Analyze alarms, trips, temperature, fuel consumption, load sharing and recovery time.
- 04
Create a corrective-action list and retest results that prove the risk is closed.
When an On-Site Inspection Is Required
These Conditions Require On-Site Inspection, Not Remote Observation Alone
- Historical tests are missing, tests are no-load only, or results do not cover real load.
- The system was not retested after expansion, maintenance, control-strategy changes or cooling modifications.
- The SLA requires loaded-test evidence and a closed corrective-action loop.
Prevention and Maintenance
To Find Problems Before an Outage, Every Inspection Must Be Recorded and Reviewable
Preventive Checks
- Create an annual loaded-test plan covering target load, fault transfer and maintenance windows.
- Cover power, cooling, fuel, monitoring and operations response in the same test.
- Assign an owner, completion date and retest record to every abnormal item.
Maintenance Routine
- Before testing, confirm the risk assessment, rollback path, communication mechanism and site permissions.
- During testing, record load, temperature, fuel consumption, alarms and transfer actions on a timeline.
- After testing, produce auditable records that support the SLA and operations review.
Engineering Recommendation
Loaded testing is not a formality; it is evidence of data center standby-power credibility. N+1 without evidence is only a design assumption.