Fixed windows, scoped registers, restart
Outage management software for windows where every hour of delay is measured against a generator coming back online.
A planned outage or upgrade compresses months of normal commissioning discipline into days, on assets that were already in service. Deskely scopes the register tightly to what is being touched, tracks status by the hour across shifts, and gates restart authorisation on the records the outage actually required.
- Window
- Days to weeks, fixed
- Scope
- Only assets touched
- Reporting
- By the hour, by shift
- Gate
- Restart authorisation
Choose your project type
The problem
There is no time to design an evidence approach once the outage has started.
Planned outages and upgrades run to a fixed window agreed months in advance, often with contractual penalties for late restart and a shift pattern that runs around the clock.
Paper packs and end-of-shift spreadsheets cannot report real progress hour to hour, so the restart decision is often made on a verbal handover rather than signed evidence.
Deskely is set up before the window opens, so the outage runs against a live register from the first shift rather than a system still being configured on day two.
Setting up the register
Only what is touched, plus its interfaces to the live plant.
The register is scoped tightly to the assets, upgrades and modifications within the outage boundary, plus the tie-ins and control interfaces to systems that stay in service.
Templates for the specific test and inspection records the outage requires are prepared and reviewed before the plant comes offline, so execution starts on day one rather than being designed during it.
Modification records are linked to the original asset history, so an upgrade is recorded as a continuation of the plant's history rather than a disconnected event.
Execution
Status is visible by the hour, across every shift working the window.
Technicians sign records at the machine on tablets, working offline where plant conditions require it, so evidence is captured at the moment work finishes rather than reconstructed at shift handover.
Safety circuit validation, interlock testing and modification-specific checks are recorded as prerequisites to restart, held against the assets they belong to.
Punch raised during the outage is categorised immediately as blocking restart or carried forward, so the shift handover works from a live, filtered list instead of a verbal summary.
Restart authorisation
Restart is released from the evidence the outage actually produced.
The return-to-service certificate lists exactly which records permitted restart and which punch items were carried, with an owner and a date against every one.
That evidence set is what defends the restart decision afterwards, whether the question comes from an insurer, a regulator or the plant's own management.
The modification history stays attached to the asset after restart, so the next outage starts from what was actually installed and tested, not from the original design intent.
NDT and pressure boundary weld records
A weld repair inside the window is a metallurgical record first, and the NDT report has to outlive the outage by decades, not days.
Pressure boundary repairs and modifications carried out during an outage — pipe spool replacement, header weld repair, valve body work — generate non-destructive testing records (radiography, ultrasonic, magnetic particle, dye penetrant) that a pressure system's written scheme of examination will reference for the rest of the plant's life, not just for restart.
Losing the link between a specific weld number, its welder qualification, its NDT report and its location on the pressure boundary is a routine failure mode when outage documentation is managed on paper under a fixed deadline, and it becomes an expensive one at the next statutory inspection.
Deskely records each weld or repair against the specific asset and location, with welder qualification, NDT method, technician and result attached, so the pressure system's inspection history gains a traceable entry from this outage rather than a loose report that has to be matched up manually years later.
How it runs
From last production before to first production after.
Short, fixed windows punish weak preparation more than any other scope, because there is no slack to absorb a documentation gap.
- 01
Scope the register tightly
Only the assets within the outage boundary, plus tie-ins and interfaces to the live plant.
- 02
Prepare before the window opens
Templates, access and pre-outage records set up while the plant is still running.
- 03
Execute across shifts
Records signed at the machine with status visible by the hour for every shift working the window.
- 04
Test safety and interlocks
Safety validation and interlock testing recorded as explicit prerequisites to restart.
- 05
Categorise punch by restart impact
Every item marked as blocking restart or carried, with an owner and a date.
- 06
Authorise restart
Return-to-service certificate issued from signed evidence, with the modification history retained on the asset.
FAQ
Questions about Plant upgrades and outages scopes.
Keep reading
Power and grid commissioning
The full sector view: asset registers, protection and control evidence, energisation gating and handover.
Read morePunch lists
Defects raised at the panel or the pole with photos, categorised by whether they block energisation.
Read moreWalkdowns
Pre-energisation and pre-restart inspections run as structured walks that raise punch on the spot.
Read moreOther power and grid project types: Gas turbine and combined cycle plants, Hydropower units and powerhouses, Biomass and waste-to-energy plants, Utility-scale solar farms, Battery energy storage systems, Transmission and distribution substations, Overhead lines and underground cables, District heating and cooling networks, Nuclear balance-of-plant and support systems.
