Colocation planning needs visibility of present demand, installed capacity and customer commitments. These are related but different measures. A low measured load today does not establish the reserve available after contracted expansion. Record the basis of each capacity figure and the shared infrastructure that must support the associated demand.
Map the reach of shared dependencies
Shared cooling, UPS equipment, switchgear or control functions can connect the consequences of an outage across customer areas. Identify those common points and the isolation arrangements available during maintenance. Evaluate a proposed generator change against the facility’s actual distribution architecture and service requirements rather than a single site-wide capacity total.
Shared infrastructure
The consequence of one common failure can therefore extend across multiple customer environments.
Maintenance
When equipment is shared across multiple customers, maintenance isolation and spare capacity become especially important.
Temporary power
Colocation resilience depends on protecting shared infrastructure without losing sight of individual customer commitments.
Review the common points
Capacity allocated to different loads may still rely on shared switchgear or distribution paths. Identify which maintenance or fault conditions affect those shared points and whether the remaining arrangement can carry the required demand.
Control work within an occupied facility
Expansion and replacement work should have a defined temporary operating arrangement, agreed work boundaries and a handback plan. The facility team needs to understand which capacity or resilience conditions change during the work. Temporary generation can be considered within that plan, subject to the connection, protection and operating requirements of the installation.
Engineer My Industry Power Requirement
Engineer My Industry Power Requirement. Share the application, location and information available so the next discussion can address your actual requirement.
Related guidance
Engineering intent
Colocation Data Centre Power should be evaluated as part of the complete power system rather than as an isolated catalogue item. Operating duty, connected load, interfaces, protection, controls, installation conditions, testing requirements and lifecycle consequences determine whether the arrangement is appropriate.
Engineering considerations
Rental projects may need controlled testing before handover, especially where customer load is unavailable or staged later. For synchronised generator systems, testing may need to evaluate: Do not treat a multi-generator plant as one large single generator. Where a test includes multiple generators in parallel, record whether load is shared as intended. Total output alone can hide unequal machine behaviour. Data-centre generator testing may need strong test-boundary definition. A generator-only load-bank test should not be presented as proof of the complete data-centre power chain. Critical facilities should define the required test scope carefully. The applicable facility requirements and project test plan should govern.
Selection and design considerations
All support remains subject to generator model, load details, site access, technical feasibility, equipment availability, parts availability and written quotation. every factory can safely test on live load; 03 — Classify safety, process, essential and non-essential loads 04 — Identify motors, compressors, pumps and starting methods 05 — Review power factor, harmonics and nonlinear loads In a Data Centre, Power Failure Is Not an Event. It Is a Business-Risk Trigger. A data centre does not simply “use electricity.” It depends on continuous, clean, layered, controlled and verified power. When power quality fails, the risk is not limited to lights turning off. For data centres, generator design is not only backup power. It is continuity engineering across utility, UPS, batteries, generator, ATS, switchgear, cooling, controls, fuel and maintenance.
Integration and protection considerations
A project should not hand over drawings that no longer represent reality. Handover should explain how the system is intended to be operated. The operating team should not inherit an unexplained power system. Training does not replace technical maintenance, but it reduces operational confusion. Standby commissioning should verify readiness for source failure. Standby power is not proven by unloaded running alone. Rental commissioning may need a tighter site-specific sequence because the system is temporary. A generator-only test is not a complete data-centre power-chain proof. Critical facilities should commission according to the actual facility requirements and applicable project/professional standards.
Testing, commissioning and verification
Temporary power does not remove the need for transfer discipline. A generator-only ATS explanation is not enough for a data-centre power chain. The transfer sequence must support the process, not merely switch the source. A multi-generator standby system is not commissioned by testing only one generator start. Some systems use two generator sources without continuous paralleling. Transfer between generators is not the same as paralleling. If overlap is required, synchronisation and suitable protection become relevant. A retrofit should start with survey, I/O review and protection/sequence review.
Direct answer
Colocation planning needs visibility of present demand, installed capacity and customer commitments. These are related but different measures.
The practical decision for Colocation Data Centre Power should be based on verified load, equipment, interface and site information. Where equipment-specific data, regulatory applicability or a project study is required, this guidance does not replace that verification.