Live facility, new equipment, no acceptable downtime
Data center retrofit commissioning software for upgrades where the existing IT load can never be the thing that fails.
Capacity upgrades and retrofits add UPS modules, switchgear or cooling capacity into a facility that is already carrying live IT load. Deskely separates the new-equipment commissioning path from the live base build it's being added to, with method-of-procedure evidence and hold points that keep the existing critical load protected while the new capacity is proven.
- Scope
- New capacity in a live facility
- Constraint
- Zero impact to existing load
- Method
- MOP-driven hold points
- Gate
- Redundancy re-verified
Choose your project type
The problem
The new equipment is the easy part; proving it without touching live load is the hard part.
Adding a UPS module, a switchgear section or a chiller to a facility already running IT load means every test step that could affect the live side needs its own method of procedure (MOP), its own hold point and its own rollback plan.
When that evidence lives in a MOP document reviewed once before the work and filed afterwards, there's no record of which specific steps were actually executed, by whom, and what the live-side readings looked like at each hold point.
Deskely turns the MOP into a structured, signed record — hold point by hold point — so a facilities manager can see exactly what happened during a maintenance window on a system carrying production load.
Setting up the register
New equipment is modelled as its own subsystem, tagged against the live systems it will join.
A new UPS module, switchgear lineup or chiller is registered as new scope with its own Level 1–4 commissioning path, while a reference to the existing live system it's being paralleled or tied into records the dependency explicitly.
Single-line diagrams marked up for the change, along with the MOP itself, are parsed and linked so every switching step in the register cites the drawing and the procedure step it corresponds to.
That link is what lets a reviewer confirm the new breaker's commissioning tests were completed before the MOP called for it to be closed into a live bus.
Execution against the MOP
Every hold point is a signed record, not a line ticked off on a printed procedure.
Pre-checks, go/no-go criteria, live-side readings before and after each switching step, and rollback triggers are captured as structured fields rather than free text, so a hold point can't be passed without the readings that justify it.
Where two people are required to authorise a step affecting live load, the record can require both signatures before the next step unlocks.
Redundancy is re-verified once the new equipment is in service — an N+1 lineup that briefly runs N during the cutover has to be proven back to full redundancy before the maintenance window closes.
Close-out
The upgrade is signed off with an audit trail the next outage review can use.
The completed MOP record, new equipment's own commissioning results and the redundancy re-verification form one dossier for the upgrade, distinct from but linked to the facility's base build history.
Punch raised during the work is categorised against whether it affects the live side or only the new equipment, so nothing ambiguous is left open against systems carrying production load.
If an incident review is ever needed, the exact sequence of switching steps, readings and signatures for that specific maintenance window is retrievable directly, not reconstructed from memory.
Brownfield IST proves the whole facility again
A capacity upgrade doesn't just add a UPS module, it changes the failure behaviour of every rack the shared bus already serves.
Adding capacity into a live power train means the N+1 or 2N topology the facility was originally certified against no longer exists as tested — a new UPS module paralleled onto an existing bus changes load sharing, fault current and transfer timing for equipment that was never touched during the upgrade.
Where the scope justifies it, a brownfield integrated systems test re-runs a scoped set of failure scenarios against the changed topology — a simulated utility loss or a forced transfer — rather than assuming the original IST result still applies to a bus that now behaves differently under fault.
Deskely keeps that re-test scenario matrix linked to both the new equipment's commissioning records and the facility's original IST results, so a reviewer can see exactly what changed, what was re-proven, and what the facility's redundancy claim rests on after the upgrade rather than before it.
Evidence
The MOP-verified dossier
New capacity landing inside a live facility is proven twice: once that the addition works, and once that the existing load never saw it happen. Every hold point in the method of procedure needs its own signed record.
Method of procedure (MOP) hold point sign-off log
Each step of the live-facility work was executed and verified in sequence before proceeding to the next
Continuously through the works
Pre-work redundancy baseline report
The existing N+1 or 2N configuration and load levels immediately before the works are documented
Before any live switching or tie-in
Battery impedance baseline record
Existing UPS battery strings are within acceptable impedance range before new load or capacity is added
Immediately before the upgrade begins
Load bank step-load test report for the new capacity
The added plant accepts its rated load in steps without disturbing the existing critical load
During commissioning of the new equipment, isolated from live load
Post-work redundancy re-verification record
Full redundancy is restored and confirmed at the shared plant level after the new capacity is integrated
Immediately after energisation of the new plant
SLA acceptance and witness pack
The upgraded facility meets its uptime commitments with zero recorded impact to existing tenant load
Final gate closing out the works
How it runs
From a MOP on paper to a signed, hold-point-verified upgrade.
Retrofit work on a live facility rewards the same rigour as new build, applied to a much smaller and much higher-consequence scope.
- 01
Register the new equipment
New UPS, switchgear or cooling capacity tagged as its own subsystem with a reference to the live system it joins.
- 02
Digitise the MOP
Pre-checks, go/no-go criteria and hold points structured as a signed record tied to the switching sequence.
- 03
Commission the new scope
Level 1–4 testing on the new equipment completed and signed before the MOP calls for it to close into a live bus.
- 04
Execute hold point by hold point
Live-side readings captured before and after each step, with dual sign-off where the procedure requires it.
- 05
Re-verify redundancy
Confirm the facility is back to its designed N+1 or 2N state before the maintenance window closes.
- 06
Close out and link
Upgrade dossier issued and linked to the facility's ongoing base build record, punch categorised by live-side impact.
FAQ
Questions about Retrofit and capacity upgrade scopes.
Keep reading
Data centre commissioning
The full sector view: commissioning levels, integrated systems testing, punch and the certification ladder to IT load.
Read moreWalkdowns
Pre-energisation and pre-IST inspections run as structured walks that raise punch on the spot.
Read morePreservation
Routines for switchgear, UPS and generators that sit energised but unloaded for months before IT load arrives.
Read moreOther data centre project types: Hyperscale new build data centres, Colocation facility commissioning and SLA acceptance, Edge and modular data centre commissioning, UPS and power train commissioning, Cooling, CRAH/CRAC and liquid cooling systems, Standby generators, fuel and switchgear, White space rack, power and busway fit-out, Integrated systems testing and Level 5 commissioning, Campus substation and utility interconnection.