Factory-fabricated modules, standardised ITPs and repeatable fleet commissioning
Commissioning software for small modular reactors where the commissioning model has to repeat cleanly from the first unit to the tenth without re-inventing the register each time.
SMR programmes are built on repeatability: factory-fabricated modules arrive with much of their QA history already established, and the site commissioning programme has to pick that history up rather than start from zero, while still proving every safety-classified system on-site. Deskely holds the factory QA record, the site ITP and the fleet-wide template in one register, so unit two starts from a proven baseline instead of a blank spreadsheet.
- Assets
- Factory modules, site tie-ins, integrated systems
- Test
- Factory FAT, site integration, first criticality prep
- Model
- Fleet-standardised ITP templates
- Gate
- Unit acceptance and fleet rollout
Choose your project type
The problem
A fabrication yard's QA record and a site's commissioning record are usually two disconnected systems, and the gap is where traceability gets lost.
SMR modules — reactor vessels, steam generators, integrated primary system packages — are fabricated and factory-acceptance-tested off-site under their own QA programme, then shipped and installed at a site that runs its own separate commissioning system.
When the factory's material certificates, weld records and FAT results are not linked to the site's ITP for the same component, a hold point witnessed at the factory has to be re-proven or manually cross-referenced on-site, and the second and third units of a fleet inherit the same disconnect instead of a faster start.
Deskely carries the factory QA record forward against the same tag used on-site, so a module's fabrication history, FAT results and site integration tests sit in one continuous record instead of two systems that never talk to each other.
Setting up the register
Modules, tie-ins and fleet templates are structured so unit two starts from a proven baseline, not a blank register.
Factory fabrication drawings, module datasheets and FAT reports are parsed into the register alongside the site P&IDs, so a module's tag carries its factory QA history the moment it arrives on-site.
ITPs, hold point sequences and safety classifications are templated once at the fleet level and instantiated per unit, so the second and subsequent units in a programme inherit a proven test structure instead of a re-derived one.
Site tie-in points — where the factory module interfaces with site-erected piping, electrical and I&C — are tracked as their own boundary asset, so the handoff between factory scope and site scope has a single, unambiguous test record.
Execution
Site integration testing and first-unit learning are captured so the fleet gets faster, not just the paperwork gets bigger.
Site integration testing proves the factory module and site-erected systems function together, with tie-in test records referencing both the factory FAT baseline and the on-site as-built condition for the same boundary.
NCRs and lessons from the first unit are tagged against the specific ITP step or component type, so when unit two's commissioning team hits the same interface, the resolution and the updated test procedure are already attached to the template.
Fleet-wide readiness dashboards roll up status across all units under construction, so a programme director can see which unit is ahead of schedule on system turnover and which is repeating an issue the first unit already solved.
Unit acceptance and fleet rollout
Unit acceptance closes with a record that feeds the next unit, not a one-off dossier that gets filed away and forgotten.
Unit acceptance draws on the combined factory and site record for every module and tie-in, giving the regulator and the owner a single evidence chain from fabrication through to on-site integration testing.
The as-built dossier for each unit is structured against the same fleet template used for the next unit, so lessons on ITP wording, hold point placement or NCR trends carry forward automatically rather than depending on institutional memory.
Every signature carries a name, role and timestamp across both factory and site records, satisfying the traceability a fleet licensing basis and the licensee's QA programme both require.
N-stamp pedigree and factory-to-site QA continuity
A reactor vessel or steam generator module arrives on-site with an N-stamp and a pedigree file, and the site programme's job is to extend that pedigree, never to quietly restart it.
SMR pressure boundary modules are fabricated under ASME N-stamp certification, with material traceability, weld procedure qualification and non-destructive examination records forming a pedigree file that has to survive shipping, storage and installation intact, because a break in that chain forces re-verification the fleet business case was never designed to absorb.
Independent nuclear assurance for a fleet programme increasingly certifies to ISO 19443 rather than a bespoke nuclear QA manual, and an ISO 19443-certified supplier's own audit evidence has to be recognised inside the site's register rather than re-collected from scratch, or the standardisation the certification exists to deliver never actually reaches the licensee's cost line.
Deskely carries the N-stamp data report and pedigree file forward against the same module tag used on-site, with the ISO 19443 supplier audit trail attached, so a site QA reviewer can confirm pedigree continuity in the register instead of requesting the fabricator's files by email during a fuel load readiness push.
The fleet acceptance evidence set
Six record types carry a module's QA pedigree from the factory floor to unit acceptance, and again for every unit after it.
SMR commissioning inherits much of its QA history from the factory, so the site register has to preserve that history rather than restart it. These records are what unit acceptance and fleet rollout actually depend on, distinct from the site-only paperwork a first-of-a-kind build generates.
Factory acceptance test (FAT) certificate
That a fabricated module passed its factory test programme against the design specification before shipment, including any pressure or leak testing performed off-site.
Issued at the factory, before module dispatch to site.
Module transport and receipt inspection record
That a module arrived on-site undamaged and matches its shipped configuration, with any transit damage logged before site tie-in work begins.
Completed on receipt, before site integration.
Site integration test record
That the interconnection between two or more factory modules — piping, electrical, I&C — functions correctly once tied in at site, not just within each module individually.
Executed after module tie-in, before system-level testing.
Fleet ITP variance log
That any deviation from the standardised fleet ITP on a specific unit is recorded and justified, so the template itself stays trustworthy for the next unit.
Maintained across each unit's commissioning programme.
N-stamp or equivalent code data report
That pressure-retaining components carry unbroken code stamping and material traceability from fabrication through installation.
Compiled before hydrostatic or pneumatic testing on-site.
Unit acceptance certificate
That a specific unit's site integration testing, first criticality preparation and fleet-standard ITPs are complete and accepted by the licensee.
Issued per unit, feeding the fleet rollout baseline.
How it runs
From first module fabrication to fleet rollout.
SMR programmes reward a register that treats the fleet, not the unit, as the unit of improvement, because the value of standardisation is lost the moment each site starts its own spreadsheet.
- 01
Model modules and tie-ins
Factory modules and site tie-in boundaries modelled as tagged assets carrying both factory and site QA history.
- 02
Carry factory QA forward
Material certificates, weld records and FAT results parsed into the same register the site ITP will reference.
- 03
Template at fleet level
ITPs, hold points and safety classifications defined once per component type, instantiated across every unit in the programme.
- 04
Roll forward lessons per unit
NCRs and procedure updates from one unit attached to the fleet template so the next unit starts ahead, not from zero.
FAQ
Questions about Small modular reactors scopes.
Keep reading
Nuclear commissioning
The full sector view: safety classification, ITP hold points, QA records and the terminology behind them.
Read moreMaster data
Component and system registers aligned to the plant's configuration baseline instead of scattered vendor binders.
Read moreITR records
Test and inspection records defined once per component type and instantiated across every safety-classified system.
Read moreOther nuclear project types: New-build reactor commissioning, Nuclear plant life extension commissioning, Nuclear outage and refuelling commissioning, Nuclear decommissioning and waste management commissioning, Nuclear fuel handling and storage commissioning, Nuclear balance-of-plant commissioning, Nuclear instrumentation and control (I&C) upgrade commissioning, Nuclear safety system commissioning and equipment qualification, Research reactor and fusion facility commissioning.
