Applications & Engineering

BESS EMS Integration: Agree the Interface Before Ordering

An EMS interface needs more than a protocol name. Agree the point list, control authority, failure behavior and integration responsibilities before comparing BESS quotations.

By HUA-X · Published October 7, 2026 · Updated October 20, 2026

Control-room window overlooking a closed PowerFac-5M battery container — A control-room view toward a battery storage yard.

Before ordering a battery energy storage system (BESS), ask the supplier and site controls integrator to agree a versioned interface document: what each signal means, who may issue commands, what happens when communication is lost, and who proves the connection works. A protocol name alone does not settle these questions. For procurement, the useful deliverable is an agreed interface and test scope attached to the proposed equipment configuration.

1. Separate the protocol from the information it carries

MESA’s overview of IEEE 1815.2-2025 describes a mapping between DNP3 communications and the IEC 61850-7-420 data model for distributed energy resources. Its scope includes monitored information, control commands and configuration management. This illustrates why exchanging messages and agreeing their meaning are separate parts of an interface. See the MESA standard overview.

At the equipment level, the MESA-Device specifications address communications involving the power conversion system, battery and meters. They also identify model definitions and vendor-specific extensions. Use this as a reason to request the actual interface document and supported functions. Ask which protocols and functions the offered HUA-X configuration supports.

Two unplugged network cable connectors on a laboratory bench — Communication connectors on an integration workbench.

2. Request a point list that both teams can interpret

A point list describes the measurements, status information and commands exchanged across a control interface. Ask the equipment supplier and integrator to review the same revision against the actual controller and firmware. Use the fields below to agree the interface requirements with both teams.

Suggested fields for a project-specific EMS interface agreement.
Interface item	What to agree	Why it affects the quotation
Connection and document revision	Protocol and version, physical connection, gateway needs, controller and firmware scope.	Identifies supplied hardware and integration work.
Measurements	Signal name, measurement location, unit, scaling and charge/discharge sign convention.	Prevents different interpretations of the same reading.
Status and alarms	Meaning of each state, alarm priority, data-quality indication and reset responsibility.	Defines monitoring and operator handover.
Timing	Timestamp source, time zone, update interval and when data is treated as stale.	Makes data freshness and logging reviewable.
Commands	Read/write permissions, allowed modes, limits, acknowledgement and rejection reasons.	Defines which controls are actually available.
Loss and recovery	Expected response to lost communications or stale data, reconnection and restart permission.	Defines the behavior to review and demonstrate.

Keep these definitions with the quotation rather than accepting a generic protocol brochure as the entire integration scope. If an item is unavailable, record who will supply it and whether the offer depends on that assumption. Request the applicable response times, register addresses and command limits from the responsible supplier.

3. Agree who controls the system in each operating state

List the parties that can request operation: the site energy management system (EMS), supervisory control and data acquisition system (SCADA), local operator, or another project controller. Ask which party has authority in each agreed mode and how a command is accepted, rejected or superseded. Distinguish monitoring access from permission to change operating settings.

Bring the approved operating brief into this discussion. If the project needs both peak shaving and backup reserve, ask how a dispatch request interacts with the reserve requirement and equipment limits. Do not assume a communications interface establishes islanding, black-start or backup capability. The electrical architecture and applicable engineering approvals still govern what the installation can do. See backup reserve and peak shaving for the operating brief and grid-connection data for the electrical boundary.

For communication loss, ask the responsible engineering teams to specify the permitted response and recovery conditions. Holding a setpoint, stopping dispatch or changing mode can have different consequences at different sites. Obtain a project-specific decision before writing it into the acceptance procedure.

A controls engineer seated at a bench with a monitor and an instrument case — An engineer at an integration workbench.

4. Put the integration test and its owner in the scope

MESA treats testing as a separate part of achieving predictable interoperability; its testing overview describes different testing and certification programs. For a purchase, request evidence that matches the offered implementation and ask what still needs demonstration with the site controller. Do not treat a reference to a standard as a project acceptance record.

Agree which supplier provides the point list and test environment, which integrator maps the signals, and who witnesses and accepts the results.
Plan checks for measurement meaning, command permission and acknowledgement, relevant operating limits, stale data, communication loss and recovery.
Record the tested controller and firmware revisions, unresolved items and the change process if the delivered configuration differs.
Have qualified engineering teams choose safe test conditions. A simulated or bench result should be identified separately from a site demonstration.

Resolve responsibility for gateways, software configuration, network access, commissioning support and ongoing changes before comparing prices. A quotation with an unspecified integration owner leaves a commercial question open even when the equipment itself is clearly described. Use the FAT and SAT acceptance guide to agree which results support shipment release, site acceptance and handover.

5. Confirm the owner can retrieve usable operating records

Ask the supplier and integrator to demonstrate a data export using the owner’s agreed access before handover. Review an agreed recording period alongside the current point list. A working control-room display does not by itself show that the owner can retrieve the records needed to investigate an operating problem.

DOE’s Battery Energy Storage System Evaluation Method reports problems with data availability and incomplete charge/discharge records. It also explains that zero energy flow alone cannot distinguish a battery that was not dispatched from one that was unavailable. See the report’s data and availability discussion, page 10.

Suggested operating-record checks to agree with the supplier and integrator.
Handover item	What to request	What to check in the sample
Owner access	Name the party providing access and demonstrate the agreed download method.	The owner can retrieve and open the file using the agreed access.
Measurement meaning	Include units, measurement location, time zone and charge/discharge definitions.	The exported fields match the agreed point-list revision.
Missing or estimated records	Agree how gaps and estimates are identified.	A missing record is distinguishable from a measured zero.
Operating context	Provide relevant status and alarm records for the same period.	The records can be aligned by time to investigate unexplained zero flow.

Agree the recording interval, export format, retention period and any cloud access or subscription conditions in the quotation. If charging and discharging can occur within one interval, ask how the records preserve both energy quantities instead of only their net value. Use available commissioning records for the demonstration and record any missing deliverable with its responsible party. Before comparing an efficiency figure, use the round-trip efficiency measurement guide to check the measurement boundary and the charging and discharging records.

6. Apply the right boundary to the HUA-X enquiry

For PowerFac-261, confirm the external point list and compatibility with the proposed site controller. Review the PowerFac-261 product information and procurement brief, then request its applicable interface documents.

PowerFac-5M is presented as a DC-side battery platform. Confirm the proposed PCS, EMS/SCADA, communications and related responsibilities separately. Review the PowerFac-5M scope and procurement brief and request documents for the proposed configuration. An included controller or gateway should be identified in the quotation, not inferred from the battery-container rating.

Start an EMS integration enquiry with the site country, operating objective, proposed battery configuration, existing controller and revision, available interface documents, and the party responsible for integration. State whether you need monitoring, dispatch control or both. You can begin with incomplete records: mark the missing inputs and ask which ones affect the next quotation. Use the BESS RFQ guide for the wider project brief.