Factory-built, field-repeated, dozens of identical sites
Edge data center commissioning software for sites that are built once in a factory and commissioned many times in the field.
Edge and modular deployments push most of the FAT effort into the factory and repeat a compressed field commissioning sequence at every site — a telecom hut, a retail edge node, a containerised modular data hall. Deskely templates the record set once per module type and instantiates it across every deployment, so the fiftieth site gets the same rigour as the first without the same time on site.
- Unit
- Module or containerised hall
- Sequence
- Factory FAT, ship, field commission
- Scale
- Tens to hundreds of sites
- Output
- Site acceptance per node
Choose your project type
The problem
A hundred identical sites still get a hundred slightly different commissioning packs.
Edge deployments rely on repetition — the same module design, the same UPS, the same cooling unit — but if every site team improvises its own checklist, the fleet ends up with a hundred variants of what should be one record set.
That inconsistency is invisible until an operator tries to compare fleet-wide readiness, or a factory defect discovered on site twenty needs checking against sites one through nineteen.
Deskely templates the record set once per module type, so every deployment produces directly comparable evidence and a factory-wide issue can be traced across the fleet in minutes.
Setting up the register
The module template is built once and instantiated at every site with its own site ID.
Module bill of materials, single-line diagrams and control schedules are parsed once into a template register covering UPS, cooling unit, PDU, generator (where fitted) and the module's own BMS/EPMS points.
Each field deployment instantiates that template against a site tag, inheriting the factory FAT results and carrying forward any open factory punch that has to close before field energisation.
Fleet-wide reporting rolls status up from module to site to region without anyone rebuilding a spreadsheet per deployment.
Factory to field
Factory witness testing is the evidence base; field commissioning proves the site-specific connections.
Level 1 factory witness testing at the module integrator's works covers the UPS, cooling and power path exactly as it will ship — proving those systems once rather than at every site.
Field commissioning is compressed to what's genuinely site-specific: utility connection, generator (if separately supplied), fibre and network handoff, and a functional test confirming the module survived transport and installation intact.
A module cannot be marked field-ready while factory FAT punch remains open and unowned, which stops a known factory defect being rediscovered independently at every site.
Fleet visibility
One dashboard for a hundred sites, not a hundred status calls.
Because every deployment shares the same template, a single dashboard shows exactly which sites are FAT-complete, which are mid-field-commissioning, and which are IT-load ready, without reconciling formats.
Offline mobile capture matters here more than almost anywhere else — edge sites are frequently in locations with poor or no connectivity, and field technicians need to complete and sign records that sync once back in range.
Preservation routines for sites commissioned but not yet loaded with IT equipment follow the same template, so a module sitting ready for months doesn't quietly drift out of a known state.
There is no commissioning agent on site
An edge site is commissioned by whoever the field technician is that day, often alone, often for the first time on that module type.
Unlike a hyperscale build with a resident CxA and a full commissioning team, an edge deployment is typically one or two field technicians working from an installation and test procedure on a tablet, with no senior engineer to walk over and check a marginal reading — the procedure itself has to carry the rigour a person would otherwise supply.
That makes the structure of the field record the actual safeguard: mandatory measured values instead of tick-boxes, photo evidence required at defined steps, and a record that won't let the technician mark energisation complete while a factory FAT punch item from the module's build is still open and unresolved.
When a regional technician is later dispatched to troubleshoot a fault at a site they've never visited, the record they open is the same template used at every other site of that module type, so diagnosing a UPS fault at site 84 benefits from knowing exactly how sites 1 through 83 were built and tested.
Evidence
The site acceptance dossier
With commissioning split between a factory and a field site, and repeated across tens or hundreds of nodes, the module's factory test pack has to travel with it and be checked off again on site rather than trusted blind.
Factory acceptance test (FAT) report
The module's electrical, mechanical and controls systems perform correctly before it leaves the factory
Prior to shipping
Transit and site arrival inspection record
No damage or configuration drift occurred between factory test and site placement
On module arrival, before reconnection
Field commissioning functional test script
The module performs to the same functional standard on site as it did at FAT, including any field-fitted connections
After site installation, before load bank testing
Load bank step-load test report
The module's UPS and cooling accept full rated load in steps without exceeding design excursion limits
During field commissioning
Thermal ride-through data log
The module holds its allowable temperature envelope for the specified duration on a simulated cooling failure
Captured during field IST
Site acceptance test (SAT) and witness pack
The individual node is accepted as ready for live IT load, referenced against its own FAT
Final gate per node
How it runs
From one factory template to a hundred field sites.
Edge and modular scope rewards templating discipline up front, because the value is entirely in not re-deriving the process at every site.
- 01
Build the module template
Bill of materials, single-line diagram and control schedule parsed once into a reusable record set.
- 02
Run factory witness testing
Level 1 FAT executed per module against the template, punch raised and owned before shipment.
- 03
Instantiate at each site
The template applied to a new site tag, inheriting factory results and open punch automatically.
- 04
Commission the site-specific scope
Utility connection, network handoff and functional test recorded on tablet, offline where needed.
- 05
Certify and roll up
Site acceptance issued per node, with fleet-wide status visible from one dashboard.
FAQ
Questions about Edge and modular scopes.
Keep reading
Data centre commissioning
The full sector view: commissioning levels, integrated systems testing, punch and the certification ladder to IT load.
Read moreITR records
Component verification, functional performance and IST records defined once per equipment type and instantiated across every asset.
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, Retrofit and capacity upgrade 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.
