A remotely controlled BESS is part of the operational network. An EMS interface can change schedules, power limits or the emergency SOC reserve. Access requirements therefore belong in the purchase specification alongside PCS power.
Separate viewing from control
An operator, service engineer and financial analyst need different permissions. Request individual accounts, change logs and a way to revoke a contractor's access. A shared password makes it difficult to identify who changed a setting. Define who is allowed to approve remote changes as well as who can technically make them.
Remote access without exposing the controller
Agree network segmentation, a protected access route, time-limited service sessions and an update process. Modbus alone is not a security control. Identify required external services, behaviour after internet loss and the functions that remain locally available. The system should have a documented response to communications failure rather than relying on an unspecified cloud fallback.
Test recovery
A backup is useful only if it can restore the agreed configuration. Include configuration export, recovery, event logs and disabling a compromised account in acceptance checks. NIST OT guidance helps frame requirements but does not replace assessment of the actual network. Ask the supplier to state its support period and vulnerability-reporting channel in writing.
Draw the access map before discussing security features
Consider a routine service request: the supplier wants to connect to the EMS to investigate a charging alarm. Who authorises the session, which settings can be changed and who reviews the result? A password sent through a messaging app does not answer those questions. Procurement needs a data-flow diagram and named responsibilities, not just the name of an encrypted protocol.
Locate the BMS, PCS, EMS, meters, remote-support gateway, operator workstation and external services on the diagram. For each connection, identify its direction, purpose and ability to carry commands. Reading a measurement and changing a power setpoint have different consequences. A reporting service should not receive control privileges merely because that makes integration easier.
Specify accounts that the owner can manage
Individual accounts link actions to responsible people. Separate the roles of operator, administrator, service support and report reader. Check whether one employee’s access can be revoked without changing credentials throughout the system. Define emergency local access as well: it should remain controlled and accountable when an external authentication service is unavailable.
The handover package should list active accounts, the procedure for changing initial passwords and the rules for keeping keys. If the manufacturer retains a service account, the owner needs to know its privileges and permitted use. Undocumented permanent access should not be accepted as an unavoidable characteristic of industrial equipment.
Review ownership changes and contractor turnover. The business may replace its service provider long before it replaces the battery. Ask whether the account structure allows that transition without losing configuration, historical data or access to essential local functions. These are practical purchasing questions, not merely matters for a later IT audit.
Give every remote session a beginning and an end
Agree who initiates a session, who approves it and when permission expires. Important changes should record the previous and new values. At the end of service, the operator should receive a short account of the issue, actions, versions and unresolved points. This record supports the next shift, warranty review and analysis of subsequent behaviour even when no security incident has occurred.
The objective is not to ban every cloud connection. Establish which data leave the site, why they are needed and which functions depend on the service. Losing online reports is one situation; losing critical reserve or local control is another. The latter affects the equipment’s ability to perform its primary purchased duty.
Ask how remote access is separated from ordinary office browsing and unrelated business systems. The supplied diagram should identify the boundary, rather than assume that a shared internet connection makes every device part of the same trusted environment. The final arrangement must be agreed with the organisation responsible for the site network.
Do not make a live BESS the first update trial
Request supported versions and the compatibility procedure for BMS, PCS and EMS. Updating one component may alter communication or available settings. Before installation, agree the maintenance window, backup, checks after completion and route back to a working configuration. “Automatically updated” is not enough information to establish a suitable support arrangement.
The contract should identify a vulnerability-notification channel, support period and process for receiving fixes. Ask what happens after support ends: whether local operation remains possible, which components can be replaced and whether configuration can be exported. These obligations affect ownership cost just as much as a future power-module replacement.
Distinguish notification speed from restoration time. A support desk may acknowledge a ticket promptly while a compatible controller or approved software image remains unavailable. The commercial offer should make these different commitments understandable rather than combining them into one reassuring service-level phrase.
Prove that a backup can restore the required configuration
A settings file on an engineer’s laptop is not a complete recovery process. Establish whether it includes network settings, signal maps, users, schedules, limits and reserve rules. Secrets may require separate protected storage. The owner should know where the necessary material is held and who is entitled to use it.
Request a recovery demonstration on an agreed test environment or under a safe acceptance plan. Check more than whether the interface starts. Verify units, timestamps, power-flow signs and operating limits. Following a controller replacement, an incorrect measurement direction can be more consequential than a missing dashboard chart.
Useful acceptance scenarios
| Scenario | Evidence for the customer |
|---|---|
| Service access revoked | The former user can no longer sign in |
| External communication lost | Agreed local functions remain available |
| Power limit changed | User, time, previous value and new value are recorded |
| Configuration restored | Agreed rules and signal maps return correctly |
| Event history reaches retention limit | Retention and export behaviour are understood |
| Device clocks differ | Events can still be interpreted and the fault identified |
This is not an instruction to run aggressive tests on a working control network. Checks must be agreed with those responsible for operation; uncontrolled scanning can affect industrial-device availability. NIST SP 800-82 Rev. 3 is a useful reference for forming operational-technology security requirements. Citing it does not certify the offered BESS.
Put the requirements in the supply enquiry
Give USK Energy the IT team’s requirements for remote access, local operation, logging and support. Ask the manufacturer to answer each item for the offered model and version. Security then becomes part of a comparable specification rather than a promise that cannot be checked after payment.
Where an external integrator supplies part of the functionality, identify that responsibility explicitly. Purchasing an industrial router does not by itself create access and recovery procedures. The buyer needs compatible equipment, documentation and management rights that support the business’s agreed operating model throughout ownership.
Before requesting a quotation
Mark questions for which you already have a confirmed answer. Save the list and send unresolved points to the supplier.
How to check controls before ordering
Request an operating log for a specific load profile. It should expose the command, measured power, SOC, limits and reasons for stopping. A polished dashboard does not show what happens when communication fails or a forecast is wrong. Local protection takes priority over tariff optimisation; the minimum emergency reserve needs a separate setting.
Clarify data ownership, export options and the functions that remain available after a subscription ends. Remote access needs separated roles, an audit trail and a way to revoke access. Make failure-scenario tests an acceptance criterion rather than a promise of a future software update.
Further verification
From calculation to equipment
Preparing an equipment purchase? Send the load, backup duration or specification. USK Energy will clarify the configuration, compatibility and delivery terms.




