Container by container, HV energisation, PAC

    BESS commissioning software built for container-by-container turnover and a first HV energisation nobody wants to get wrong.

    A battery energy storage site is dozens of identical containers — batteries, PCS, thermal management and fire suppression — feeding a shared HV interconnection that only gets energised once everything behind it is proven safe. Deskely tracks each container as a tagged asset with its own commissioning record set, and gates HV energisation on the safety systems that actually matter.

    Unit
    Battery container / PCS skid
    Safety
    Fire suppression, thermal mgmt
    Gate
    HV energisation
    Output
    PAC and reliability run
    BESS YARD — 40 CONTAINERSCONTAINER RECORD SET · REV DBESS-01BESS-02BESS-03BESS-02-PCSMV TRANSFORMERBESS YARD — 3 CONTAINERS · PCS · MV TRANSFORMERTAG REGISTERBESS-C07Battery container 07Records signedPCS-07Power conversion system 07In testMV-07Medium voltage transforme…PreservationFDR-12Collector feeder 12Punch open40 unitsunder one system hierarchy

    The problem

    Forty identical containers means forty chances to skip the same safety test.

    Each battery container carries its own battery management system, PCS, thermal management and fire suppression, and commissioning all forty the same way, in the same order, without skipping a step, is a discipline problem more than a technical one.

    Fire suppression and gas detection testing is the record regulators and insurers will ask for first, and it is exactly the kind of test that gets rushed when forty containers are queued behind a fixed energisation date.

    Deskely templates the container commissioning record once and applies it identically to every unit, so container thirty-eight gets the same fire suppression test as container one, with the same evidence retained.

    40 IDENTICAL CONTAINERS, ONE SKIPPED TESTFire suppression functional testContainer 38 needs the same fire suppression test as container 101020304050607080910111213141516171819202122232425262728293031323334353637383940WHAT A SKIPPED CONTAINER TEST RISKSFire suppression and gas detection — the record insurers ask for firstRushed the day forty containers queue behind a fixed energisation date37 of 40containers with signed fire suppression tests3containers holding up HV energisationDeskely applies the templated container record identically, unit by unit.

    Setting up the register

    Containers, PCS skids and the HV yard are subsystems with an explicit dependency chain.

    The site is modelled as battery containers, PCS skids, medium-voltage collection, the HV substation and the point of interconnection, each with its own equipment tags and prerequisites.

    Single line diagrams and equipment lists are parsed into a reviewed register, so every container's battery racks, BMS, HVAC and fire suppression panel is tagged individually rather than treated as one black box.

    Because containers are identical, the record set defined for container one is reused for every other container without redrafting.

    1 · SOURCE DOCUMENTSContainer layout rev D40 containersPCS register40 unitsBMS and thermal manageme…40 systemsFire suppression device …160 devicesPARSE + MATCHtag · description · drawing ref2 · ONE TAG REGISTERBESS-C07Battery container 07YARDPCS-07Power conversion system 07YARDMV-07Medium voltage transforme…YARDFDR-12Collector feeder 12COLLECTORTWO DOCUMENTS DISAGREEContainer layout …Power conversion system 07PCS registerAbbreviated descriptionEngineer picks the sourcedecision loggedWeeks of transcription become a draft an engineer reviews.

    Container commissioning

    Fire suppression, thermal management and BMS are proven before any container sees medium voltage.

    Fire suppression and gas detection functional tests, thermal management commissioning, and BMS communication and protection checks are captured against each container tag, with photos and readings mandatory where they matter.

    Low-voltage commissioning and initial charge of the battery racks are recorded before the container is offered for medium-voltage energisation, keeping the sequence enforced by the data rather than by memory.

    Punch raised during container commissioning is categorised for whether it blocks that container's energisation, so one faulty unit does not silently hold up the rest of the site.

    CONTAINER TO HV ENERGISATION40-container BESS siteContainer LV checks and initial charge (×40)Signed offFire suppression and BMS functional tests (×40)Signed offMV collection protection and loop checksIn progressGrid code compliance — state-of-charge, frequency responseAwaiting predecessorHV energisation certificateAwaiting predecessorCharge/discharge cycling run, PACAwaiting predecessor40 of 40containers commissioned to the same template0containers offered for MV without LV sign-offHV energisation waits on every upstream prerequisite, not just the containers.

    HV energisation

    The first HV energisation happens once prerequisites across every upstream system are signed.

    HV energisation depends on protection relay settings, loop checks, earthing verification and grid code compliance testing at the point of interconnection all being complete — a wider prerequisite set than any single container's.

    Deskely gates the energisation certificate on those prerequisites explicitly, so the certificate cannot be issued while a protection setting or a loop check anywhere upstream is still open.

    Grid code compliance tests specific to storage — state-of-charge response, frequency regulation performance, black start capability where specified — are recorded against the interconnection subsystem.

    BESS yard — energisation ladderContainer records roll up to yard energisationMCMechanical completionIssued 19 SepContainer install records40 / 40Cabling continuitycompletePCSCPCS commissioningBlocked — container 07BMS communication proven36 / 40 containersPCS parameter set34 / 40 containersGEGrid energisationBlocked — PCS commissioning openPCS commissioning certnot issuedFire system commissioning36 / 40

    PAC and the operating dossier

    Provisional acceptance follows a charge/discharge run period logged like any reliability run.

    A defined charge and discharge cycling period at rated capacity, free of unplanned trips, sits between energisation and provisional acceptance, tracked the same way a reliability run is tracked on a thermal plant.

    Interruptions during the run are logged against the responsible container or subsystem, so a pattern across several containers from the same supplier batch is visible rather than treated as forty unrelated incidents.

    The operating dossier — container commissioning records, fire suppression evidence, protection settings, grid compliance results — is exported per container and per site to the owner and the O&M contractor.

    AUDIT QUERYPCS-07BESS yard · container 07 · power conversion systemFull history retrieved in one queryINSTMechanical installationBESS integrator11 JulCOMMBMS communication checkControls engineer19 JulFUNCPCS functional testPCS vendor engineer02 AugFIREFire detection interlock testSafety engineer09 AugCERTIFICATEPCSCPCS commissioningpendingOwner's engineerPrerequisites demonstratedThe grid energisation certificate names the records that permitted it and the punch that was carried.

    Thermal runaway safety and cybersecurity commissioning

    A battery site's worst failure mode is thermal, so deflagration venting, gas detection response and the OT network's cybersecurity posture are commissioned as carefully as any electrical system.

    Thermal runaway safety systems — deflagration vent panels, off-gas detection thresholds, container isolation and suppression sequencing — are tested to a response time and trigger threshold, not just a pass or fail, and insurers increasingly ask for the recorded values rather than a signature confirming the test happened.

    Alongside physical safety, the site's SCADA, EMS and PCS communication network sits on an operational technology network that a grid-connected asset cannot afford to commission carelessly: default credentials changed, firmware versions recorded, network segmentation verified between the BMS, PCS and the utility-facing gateway.

    Deskely captures deflagration and gas detection trigger values per container alongside OT commissioning checks — firmware version, credential change, segmentation test — so the safety case and the cybersecurity sign-off are both evidenced in the same dossier the insurer and the interconnection utility will ask to see.

    CHARGE/DISCHARGE RUN AND BATCH PATTERNPAC run periodCYCLING RUN — RATED CAPACITY, TRIP-FREE TARGETDay 1–4 — Clean, no interruptionsDay 5 — Container 22 thermal trip, batch BDay 6–9 — Clean, no interruptionsCONTAINERS FROM THE SAME SUPPLIER BATCHContainer 22 — batch BContainer 31 — batch BContainer 09 — batch AContainer 15 — batch A2 of 40containers from batch B trip during the run1pattern visible, not 40 unrelated incidentsInterruptions are logged against the responsible container, surfacing a batch pattern.PAC follows the same trip-free discipline as a thermal plant's reliability run.

    What the operator brings to the market qualification review

    The system-level records a BESS owner needs to qualify for grid services, not the installer's commissioning sign-off.

    A grid-scale battery asset is judged on round-trip efficiency, response time and thermal safety at the whole-system level before a market operator will qualify it for frequency response or capacity payments. The dossier keeps augmentation baselines and safety system tests against the asset so requalification later has a starting point to measure from.

    RECORDS PRODUCED6 typesBattery management system…Commissioning, before the system is…Round-trip efficiency and response…During the performance test, ahead of…Thermal management and fire…Pre-energisation, before the system is…Grid code compliance and frequency…Pre-synchronisation, witnessed by the…Degradation and augmentation…At commissioning, before the asset…Market service qualification test…After grid compliance testing, ahead of…DOSSIERIndexed persubsystem and tagExport readyEach record lands in the same structure, so the dossier assembles itself.

    Battery management system commissioning record

    Cell balancing, state-of-charge reporting and protection thresholds match the design specification

    Commissioning, before the system is energised to the grid

    Round-trip efficiency and response time test report

    The system meets the efficiency and response speed the market service qualification requires

    During the performance test, ahead of market qualification

    Thermal management and fire suppression functional test

    Cooling and suppression systems activate correctly under simulated fault conditions

    Pre-energisation, before the system is placed in service

    Grid code compliance and frequency response witness test

    The asset's ramp rate and response match the connection agreement and the service it is qualifying for

    Pre-synchronisation, witnessed by the network or market operator

    Degradation and augmentation baseline reading

    Capacity and efficiency have a verified starting point against which later augmentation is measured

    At commissioning, before the asset accrues cycles

    Market service qualification test report

    The system meets the specific technical criteria for the ancillary service contracted

    After grid compliance testing, ahead of market registration

    How it runs

    From container commissioning to HV energisation and PAC.

    BESS projects reward templating the container record once, because the whole site is that same record repeated dozens of times under a shared HV gate.

    1. 01

      Model the site by subsystem

      Battery containers, PCS skids, MV collection, HV substation and interconnection, each with explicit prerequisites.

    2. 02

      Template the container record

      One commissioning record set — BMS, thermal management, fire suppression — defined once and reused per container.

    3. 03

      Commission containers in sequence

      Low-voltage checks and initial charge signed before any container is offered for MV energisation.

    4. 04

      Loop-check and protection-test upstream

      Protection relay settings and loop checks signed across MV collection and the HV substation.

    5. 05

      Gate HV energisation

      Certificate issued only once container, protection and grid compliance prerequisites are signed across the site.

    6. 06

      Track the charge/discharge run

      Cycling period and any interruptions logged per container, PAC issued from the signed record set.

    FAQ

    Questions about Battery energy storage scopes.

    Ready to digitize
    commissioning and
    handover?

    We use cookies to improve your experience.
    You can opt out of certain cookies.
    Find out more in our privacy policy.