01

What the evidence says

DOE reported Philippine projects still in testing and commissioning before commercial operation, but each private BESS needs its own approved test scope and responsible parties.

Factory, site and performance tests answer different questions. A passed factory test does not prove site wiring, protection settings, network behavior, auxiliaries or the final AC output.

Acceptance must preserve raw time-synchronised data, test conditions, settings, deviations, punch-list ownership and retest evidence so the baseline remains usable after handover.

Practical decision guide

Commission the operating system—not only the container

Start with an acceptance matrix tied to the intended use case and contract. List every function the owner expects—charge and discharge dispatch, power limit, energy delivery, solar coordination, peak control, resilience reserve, grid-loss response, alarm escalation and restart—and name the test, meter, initial condition, witness, pass/fail criterion and evidence for each. Separate statutory or utility requirements from contractual guarantees and S3 engineering recommendations. A green dashboard, an energised PCS or a completed vendor checklist cannot demonstrate the complete operating architecture. The plan must also identify tests that cannot safely be performed at full scale, the approved substitute evidence and who accepts residual risk. Commissioning begins before equipment delivery because missing meter points, network access, temporary power or test loads cannot always be added after construction without delay.

Freeze what is actually being tested. Reconcile the purchase specification, approved drawings, single-line, protection study, equipment nameplates, cell and module identifiers, rack and enclosure layout, PCS and transformer ratings, BMS/EMS versions, firmware, communication map, network addressing, meter classes, time source and settings. Record every substitution and field change with its technical review, authority implications and retest consequence. Factory acceptance evidence should identify the tested serial numbers or representative configuration and unresolved deviations; it must not be recycled from a different project or firmware. At site, verify cable terminations, torque records, polarity, insulation, earthing, phase sequence, cooling, ventilation, auxiliary supplies, emergency circuits, labels, access and environmental controls before functional operation. The approved as-built baseline is the reference for later warranty, maintenance and incident investigation.

Use factory acceptance testing, site acceptance testing and performance testing for their proper purposes. FAT can verify manufactured panels, software functions, interfaces and simulated sequences before shipment. SAT must prove the installed wiring, protection, auxiliaries, meters, communications, local controls and interaction with the real transformer, switchgear, load and point of connection. A performance test then measures power, usable energy, efficiency, response and other contracted outputs at the named AC or DC boundary under stated SOC, temperature, voltage and auxiliary-load conditions. Define calibration, sampling rate, time synchronisation, data gaps, tolerances and correction methods before testing. If the system cannot reach a required condition because the site load or grid is unavailable, record a controlled deferral and objective completion trigger; do not convert an incomplete test into an unconditional pass.

Test the control hierarchy and failure behavior, not only normal dispatch. Verify who commands the BESS when the site controller, EMS, PCS, BMS, utility signal or remote platform sends conflicting or missing information. Simulate loss and restoration of internet, cloud, time source, site LAN, meter data, BMS link, HVAC feedback and auxiliary power within the safe test plan. Confirm local operating limits remain enforced, alarms reach named roles, remote access is authenticated and logged, stale commands expire, manual control is bounded, and restart does not create an uncontrolled load or export step. Exercise emergency stop, fire and gas interfaces, isolation, safe shutdown and recovery only with the responsible safety and authority parties. A system that depends on an external cloud for a safe state or basic local protection has an operational dependency the owner must knowingly accept.

Make the performance baseline reproducible. Measure maximum charge and discharge power, ramp and response, demonstrated usable energy, round-trip efficiency where contracted, auxiliary consumption, SOC calibration and thermal behavior at the agreed meter boundary. Record ambient and cell temperatures, voltage, initial and final SOC, rest periods, power factor, reactive-power command, curtailment, alarms and any derating. A nameplate kWh value cannot substitute for AC energy after conversion and auxiliaries. Where resilience is in scope, test reserve enforcement, transfer, grid-forming or generator coordination, critical-load sequence and controlled return to grid under the exact architecture; not every PCS is grid-forming and a grid-tied BESS does not become backup by declaration. Preserve raw high-resolution data and calculation workbooks so later reference tests use the same definitions.

Do not hand over an unresolved system behind a signed certificate. Classify punch-list items by safety, regulatory, protection, functionality, performance, cybersecurity, documentation and cosmetic impact. For every open item, assign the owner, interim operating restriction, evidence required, due date, retest and consequence if not closed. Deliver approved as-builts, settings and backups, certificates and complete test reports, asset register, spares, warranties, licences, access credentials, network and data map, maintenance tasks, alarm matrix, emergency contacts, training records and restoration procedures. Train operators on normal dispatch, local fallback, abnormal alarms, isolation, escalation and evidence preservation; coordinate emergency information with responsible responders where required. Acceptance dates should align with warranty and service commencement so the owner does not lose coverage while defects remain open.

S3’s free initial commissioning-readiness screen asks for the use case, contract and acceptance schedule, single-line and site layout, approved equipment and firmware, protection and control philosophy, FAT/SAT/performance-test plans, meter and data map, authority and utility requirements, emergency interfaces, punch-list process, warranty start and decision deadline. We return a bounded gap map separating missing evidence, unsafe or untestable assumptions, owner witness points and matters reserved for Philippine authorities, utilities and licensed professionals. It is not a permit, conformity certificate, energisation authorization or acceptance sign-off. A later paid scope can be limited to test-plan review, witness matrix, data protocol, independent result review, punch-list evidence or commissioning support to the owner’s responsible engineer and advisers.

DOE Philippines — Task Force 200 testing and commissioning update, June 2026

Discuss the engineering scope →
02

What a business should do next

  1. Freeze the as-built equipment, firmware, single-line, settings, meter boundaries and responsibilities before energisation; control every deviation through an approved change record.
  2. Witness functional, protection, alarm, communication-loss, local-control, power, energy, efficiency, restart and recovery tests against predefined pass/fail criteria without bypassing safety limits.
  3. Request a free S3 commissioning-readiness screen to identify the missing test boundary, document, witness point or recovery scenario most likely to delay acceptance.