Summary

BESS commissioning can stall when equipment is ready but the connections between suppliers, controls and the site remain unresolved. Define electrical boundaries, command authority, safety responses, auxiliary supplies and acceptance evidence before factory acceptance testing. A successful factory test supports site readiness; it does not establish it on its own.


Why can a tested BESS still be difficult to commission?

A battery energy storage system can pass factory acceptance testing (FAT) and still arrive at a site where nobody has agreed which controller authorizes charging, how an emergency stop propagates or who supplies power before the main circuit is energized. These are examples of interface gaps, not evidence that every commissioning delay has the same cause.


FAT verifies the equipment and functions included in an agreed factory test scope. Site commissioning verifies the installed system and its integration with actual site equipment. EPRI distinguishes commissioning, interconnection requirements and acceptance testing in its energy storage deployment guidance. Buyers should therefore define what the factory can prove and what remains for the site.


The following interface checks are practical procurement recommendations. Their detail should reflect the selected architecture, contract scope and local requirements.


Define the electrical boundary and energization sequence

Identify where the battery supplier's scope ends and where the power conversion system (PCS), transformer, switchgear and site contractor scopes begin. Record terminal locations, cable responsibilities, polarity, earthing arrangements and the agreed operating envelope. Confirm compatibility using the actual equipment documents.


Then write the energization sequence. Establish who checks insulation, authorizes switching and verifies that the required permissives are present. A drawing showing a cable connection does not explain which party is responsible for making that connection ready to energize.


Keep grid permission separate from equipment readiness. Any utility witnessing, protection settings or interconnection evidence needed for energization should have an owner and a place in the schedule.


Agree which controller has command authority

The battery management system (BMS), PCS, energy management system (EMS) and plant controller can each influence operation. Agree who issues the operating command, which limits constrain it and how local, remote and maintenance modes interact.


A protocol name alone is insufficient. An interface definition should identify the data points, units, scaling, charge and discharge sign convention, update expectations and response to invalid or stale data. Define how battery operating limits reach the PCS and how command rejection is reported.


Use a simple acceptance scenario: the plant requests discharge while the battery permits less power than requested. Agree the expected response and the evidence that will demonstrate it. This exposes a control assumption before the commissioning team has to resolve it offshore or on a remote site.


Translate safety functions into agreed responses

Prepare a cause-and-effect description showing how relevant alarms, trips and shutdown commands affect the battery, PCS and connected equipment. Distinguish an operator stop from a protective trip and from an emergency stop. Specify the restart conditions and the party authorized to reset each function.


The project safety design should determine the actions associated with fire detection, cooling failure and other applicable hazards. Avoid assuming that every alarm requires the same shutdown sequence. Factory testing should verify the agreed logic using safe simulations where appropriate, with outstanding site dependencies recorded.


The Sandia energy storage conformity assessment resources explain that assessment extends across components, complete systems and installation activities. A certificate for one item should be checked against its actual scope before it is used as evidence for the complete project.


Make auxiliary services available when they are needed

Cooling, controls, ventilation and safety equipment may need power before the main power path is available. Identify each required auxiliary service, its supply owner and the conditions under which it must operate.


Review normal operation, initial energization, shutdown and power loss. Confirm how controls retain or recover their state after an interruption. Where backup power is required by the design, define the supported loads and acceptance evidence rather than assuming that a generic UPS description covers them.


Use FAT to close interfaces and expose site dependencies

Before FAT, agree the test procedure, equipment configuration, software versions and pass criteria. Use the actual connected controls where practical. Where a simulator substitutes for a site device, record what it represents and what it cannot establish.


A useful FAT record identifies the test performed, observed result, supporting log and unresolved item. Assign each open item an owner and a closure stage. State which items prevent shipment, energization or final acceptance under the contract.


Define performance measurement boundaries separately. Any contracted energy, efficiency or power test needs agreed measurement points, treatment of auxiliary consumption and test conditions. Tie performance commitments to the agreed equipment configuration and test boundary.


What should buyers provide before requesting a quotation?

  • A single-line diagram and the proposed division of supply.
  • PCS, EMS and plant controller details, including available interface documents.
  • Site power, auxiliary supply and communications arrangements.
  • Applicable grid, safety and approval requirements identified for the project.
  • The intended FAT, site testing and handover responsibilities.


Frequently Asked Questions

Does passing FAT mean the BESS can immediately connect to the grid?

No. Installation checks, site integration, interconnection permission and any required witnessed tests remain separate activities. The agreed FAT scope determines what its result establishes.


Is a communications test enough to prove control integration?

No. A connection can be active while commands, units or failure responses are wrong. Test the operating scenarios and responses defined in the interface specification.


Who should coordinate interface closure?

The contract should name the party responsible for system integration. Individual suppliers can confirm their equipment, but someone must coordinate the functions that cross supply boundaries.


Discuss the integration scope with TLS Energy

Send TLS Energy your single-line diagram, intended delivery scope and PCS or EMS interface information. Ask for a project-specific review of supply boundaries, factory test coverage and site dependencies before finalizing the package. Contact TLS.


Further Reading