C&I ESS Grid Connection Handover Checklist: SLD, Protection and Utility Documents

A C&I ESS grid connection handover is complete only when the installed system, approved electrical design, protection settings, meters, controls and utility-facing records describe the same configuration. A cabinet that is energized is not automatically a project that is ready for operational ownership. The handover pack must show what was built, who approved it, how it is controlled and which tests remain open.

This checklist is for industrial owners, EPC teams, distributors and project coordinators preparing a commercial and industrial energy storage handover. It organizes evidence; it does not replace local grid rules, a protection study, an electrician's verification or utility approval. Qualified professionals must approve the actual single-line diagram, settings, tests and energization sequence.

1. Define the handover boundary and responsible parties

Start by naming the point of handover. It may be the battery system, the PCS and transformer package, the whole customer-side installation or the grid connection as accepted by the utility. These boundaries are not interchangeable. Write which equipment, documents, defects and future obligations transfer at each milestone.

List the owner, EPC, electrical contractor, battery and PCS suppliers, EMS provider, metering party, commissioning lead and utility contact. Give each open item one accountable owner and due date. A commercial delivery term does not decide who owns protection coordination, meter certification or future firmware changes.

Separate construction completion from operational acceptance

Construction completion can mean that equipment is installed and safe for inspection. Operational acceptance may additionally require functional tests, utility witness, approved settings, training and a complete record pack. Keep these milestones separate so an early invoice or delivery certificate cannot be mistaken for permission to operate every mode.

2. Freeze the as-built single-line diagram

The as-built single-line diagram should identify the battery racks or cabinets, PCS, transformer, switchgear, protection devices, meters, auxiliary supplies, PV or generator interfaces and the grid point of connection. Match equipment tags to the physical labels and the approved bill of materials.

Record drawing number, revision, approval date and the changes from the construction issue. A clean PDF without revision history is difficult to trust when the installed CT locations, breaker ratings or cable routes differ from the quotation. Link the diagram to the design-freeze and change-approval checklist.

Do not treat a simplified marketing schematic as a protection or energization drawing. The responsible electrical designer should confirm conductor, earthing, isolation and protection details under the applicable local requirements.

3. Reconcile equipment identity and configuration

Create an equipment register with manufacturer, model, serial number, firmware, rated power, battery configuration and installation location. Include the PCS, battery cabinets or racks, transformer, switchgear, protection relays, meters, gateway and fire or HVAC interfaces that affect operation.

Compare the register with the purchase order, packing list, factory test records and commissioning record. A component substitution can change fault levels, communication points, thermal limits or warranty responsibilities even when the enclosure looks similar. Capture approved deviations instead of silently replacing the original document.

For batteries, preserve rack or cabinet identifiers and the BMS configuration reference. For the PCS and EMS, record parameter exports and the software versions used during testing. Use the BESS quality-assessment checklist to connect identity evidence with FAT, shipment and receiving records.

4. Confirm protection study, settings and test evidence

The handover pack should include the approved protection study or coordination basis, relay and breaker settings, trip logic, interlocks and test results appropriate to the project. The exact requirements depend on voltage level, network arrangement, utility rules and the responsible engineer.

Record setting files, revision, checksum or controlled export where available, together with the person who approved them. A screenshot of a relay screen is not a substitute for the controlled setting file. Confirm that the tested setting matches the energized setting and the as-built equipment.

Keep primary and secondary injection or functional test records where required. Include test instrument identity, date, scope, measured result, witness and exceptions. Do not invent a universal pickup value, clearing time or pass tolerance; those belong to the approved study and applicable requirements.

5. Verify metering, CTs and data ownership

Identify every meter used for protection, export control, energy settlement, performance reporting or EMS control. Record meter location, serial number, scaling, phase association, direction convention, communications path and time source. The meter that drives an EMS command may not be the same meter used for utility settlement.

Confirm CT and VT ratios, polarity, phase sequence and installation evidence through the authorized test process. Incorrect scaling can produce plausible but unusable values. Do not open energized equipment or improvise CT-secondary work; follow the site's electrical-safety procedure and qualified-person requirements, with the HSE electricity-safety resources as general background rather than project approval.

Agree who owns raw data, access credentials, time synchronization, retention and export format. Link the record to the auxiliary-power and net-energy checklist when auxiliary loads affect the reported boundary.

6. Document EMS, PCS and grid-control behavior

Describe the operating modes that are included in handover: grid-connected dispatch, peak shaving, PV charging, export limitation, backup or islanded operation where approved, generator coordination and controlled shutdown. For each mode, identify the authority that can issue a command and the conditions that limit or block it.

List point names, units, update rates, alarm states and communication-loss behavior. Distinguish a display-only dashboard from a controller with authority to change PCS power. Record priority between local controls, EMS schedules, utility commands, protection trips and emergency stops.

Use the EMS integration checklist to preserve point-list and control-test evidence. The zero-export SAT guide is relevant when the grid connection includes an export restriction; it does not replace the project's utility approval.

7. Close functional tests before handover

Build a test index that maps each requirement to a procedure, result, evidence file, witness and status. Include safe start-up, shutdown, alarm acknowledgement, emergency stop, meter direction, communications, setpoint response, reserve behavior and the operating modes promised in the contract.

Separate “tested and passed,” “tested with exception,” “not tested” and “not applicable.” A system that starts once has not necessarily demonstrated recovery after communication loss, an approved mode transition or a protection trip. Retain event times and time-aligned traces for tests where response matters.

Use the FAT, SAT and commissioning checklist to connect factory records with site handover. Capacity, efficiency and availability are separate performance questions; do not use a successful control test as evidence of a capacity guarantee.

8. Build the utility and authority submission file

Identify the documents the network operator, inspector or authority actually requires for the project. Depending on jurisdiction and connection type, the file may include the application, approved drawings, equipment certificates, protection settings, test results, meter information, witness forms, operating limits and contact details.

Record submission date, version, response, conditions and the person responsible for closing comments. A supplier declaration or generic certificate does not automatically satisfy the local connection process. Keep the approved utility copy linked to the exact equipment and setting revision that was tested.

The US Department of Energy's energy-storage resources provide general program and performance context, not project-specific grid permission. Local utility rules and the responsible design professionals govern the actual connection.

9. Record open points, temporary settings and restrictions

Do not hide an incomplete handover behind a long attachment list. Create an exception register with item, risk, owner, due date, temporary control, acceptance authority and closure evidence. Include missing labels, pending utility comments, restricted operating modes, unavailable spare parts and unresolved data access.

Temporary settings need an expiry or review date. State whether the system may operate in a limited mode and who can authorize a change. A temporary export limit, disabled schedule or manual dispatch arrangement can affect safety, revenue and warranty assumptions.

For abnormal conditions, the operator should know which modes are prohibited and which phone numbers to call. The BESS fire-safety document checklist helps connect emergency interfaces with the handover pack; it is not a substitute for the site's emergency plan.

10. Transfer passwords, training and maintenance records

Transfer accounts through an approved secure process. Record roles, recovery ownership, remote-access approval, multi-factor status and the procedure for removing departing contractors. Do not place passwords in a public handover PDF or an unprotected email thread.

Provide training records for normal operation, alarms, isolation boundaries, emergency response, data export and escalation. Identify the person authorized to change PCS, BMS or EMS settings. Include maintenance intervals, consumables, inspection points, software-update rules and warranty contact routes.

The C&I ESS maintenance checklist can organize post-handover records. Maintenance responsibility should be explicit even when the seller offers remote support or a service agreement.

11. Use a controlled handover matrix

A short matrix makes it easier for the owner and supplier to see whether a document is present, approved and linked to the installed configuration.

Do not average a missing safety-critical record into an overall percentage. A handover is ready when the responsible parties accept the defined evidence and the remaining restrictions are visible and controlled.

12. Preserve the record for future changes

Store the final pack in a controlled location with a clear index. Keep the approved drawing, settings, firmware, meter configuration, test data, certificates, training records and exception close-outs linked by project revision. A future battery expansion, PCS replacement or firmware change should trigger a documented impact review rather than an informal file overwrite.

For a project review, send SolarStorageHub the installation country, connection boundary, equipment list, approved operating modes and outstanding utility comments. The Battery Storage Buyer Resources hub can help organize related procurement and commissioning questions.

Frequently asked questions

Does energizing a BESS mean the grid handover is complete?

No. Energization is one controlled milestone. Handover may also require approved drawings, protection evidence, meter verification, functional tests, utility conditions, training and a closed or accepted exception register.

Who owns the as-built single-line diagram?

The responsible design and project parties should define ownership and approval. The owner needs a controlled copy that reflects the installed configuration and the revisions used for testing and utility submission.

Can a supplier certificate replace utility approval?

Usually not. A supplier certificate may support the submission, but the local network operator, inspector or authority determines which documents and approvals are required for the actual connection.

Should passwords be included in the handover PDF?

No. Transfer credentials through an approved secure process. The handover record should describe roles, access ownership, recovery and removal procedures without exposing reusable passwords.