Cloud monitoring: What we actually look for in your battery's data

An industrial BESS facility is an active, dynamic part of a company's energy infrastructure. Stable operation, sound economics, and a high level of safety all depend on closely following the system's condition. That is done through BESS cloud monitoring, where data from battery cells, inverters, and control systems are collected and analysed.

ZynexGroup emphasises operational reliability, savings, sustainability, and transparency as central values. Openness about which data are collected, and how they are used, builds a stronger foundation for collaboration than closed systems. This article explains exactly which data points are monitored in real time, how we distinguish between passive logs and critical alarms, and how data security is handled in practice.

Which data points are monitored in real time?

To understand the system's health and performance, a wide range of technical parameters are collected continuously. In an industrial BESS, operators typically look at battery state, temperature, voltage, current, and capacity signals. These data are sent from the facility's Battery Management System (BMS) and Power Conversion System (PCS) to a secured cloud platform.

The primary data points include:

State of Charge (SOC): This indicates the battery's current charge level as a percentage. It is essential for knowing how much energy is available to reduce peak load consumption or deliver system services (ancillary services that help keep the electricity grid in balance).

State of Health (SOH): This expresses the battery's overall health and remaining lifetime compared with a new system from the factory. SOH can be assessed from several operational data streams, including charge cycles and internal resistance over time.

Temperature: Battery cells operate most safely and effectively within a specific temperature range. Temperature is therefore monitored down to cell or module level.

Voltage and current: Monitoring electrical voltage (volts) and current (amperes) ensures that the system charges and discharges within its design limits.

System efficiency: Monitoring is not only about alarms. It also covers efficiency, standby losses, and the real energy state. By measuring the loss between energy sent into the battery and energy drawn out, the system's actual efficiency can be documented.

What triggers an alarm, and what is logged passively?

An industrial battery system generates large volumes of data every day. If every deviation triggered an alarm, it would create unnecessary noise for both operations staff and technicians. That is why a clear distinction is made between passive logging and actual alarms.

What triggers an alarm typically depends on the system, chemistry, supplier, and service agreement. In general, the logic is built around threshold values.

Passive logs: The large majority of collected data are used only for history and trend analysis. Minor voltage fluctuations during a fast discharge, or a marginal drop in efficiency on a very cold day, are recorded in the system. These data trigger no immediate action, but they are fundamental for calculating the system's long-term degradation and State of Health.

Warnings: If a parameter approaches a critical limit, a warning is generated. That might be a temperature rising slightly faster than expected under high load. The system continues to operate, but the event is flagged for review at the next scheduled maintenance.

Critical alarms: A critical alarm is triggered when a parameter exceeds absolute safety or operating limits. Examples include a sudden voltage drop in a specific cell, a fault in the inverter's communication with the grid, or a temperature above the permitted maximum. When critical alarms occur, the system's internal safety systems often intervene automatically by reducing power or disconnecting the facility from the grid entirely to protect the hardware.

Proactive anomaly detection in practice

The value of cloud monitoring is not only in reacting when something goes wrong. The main operational benefit is the ability to anticipate and limit downtime. Cloud monitoring makes it possible to spot deviations early and follow performance trends over time.

A classic example of proactive anomaly detection is monitoring of cell temperatures and internal resistance. If data over a period show that one battery module consistently runs slightly warmer than neighbouring modules during charging, that is an indicator of a potential future fault. Even when the temperature remains within permitted limits and does not trigger an acute alarm, the underlying trend can be picked up by the data analysis.

By identifying this imbalance early, technicians can plan an inspection or replacement of the specific component during a scheduled service stop. That avoids an unannounced failure that would otherwise have led to unplanned downtime and lost revenue from, for example, frequency regulation. It should still be noted that while early monitoring catches many deviations before they become operationally critical, it cannot guarantee that every internal fault is detected in advance.

What does the customer see in the dashboard, and what do we see?

Transparency does not mean that every party needs to look at the same raw data. Different users need different information to make the right decisions.

The customer's overview: The company's operations manager or CFO typically has access to a dashboard focused on business value and overall status. The customer can see whether the system is in normal operation and access reports on performance and operation over time. The interface is designed to give a quick, clear overview without unnecessary technical complexity.

ZynexGroup's overview: Our technical team has access to a deeper diagnostic layer. Here we can work with more detailed operational data and log information used for technical support and proactive maintenance. That makes it possible to follow developments in voltage differences and other deviations when they are relevant to operations.

Response time for a critical alarm

When a critical alarm is registered, fast and precise action matters. The subsequent process depends on the system's setup and the specific event.

First, the nature of the fault is assessed. If the fault poses a risk to system safety, the local Battery Management System typically responds by limiting or stopping operation locally, independently of the cloud connection.

A technical review of data and log files then begins. If the fault turns out to be a physical component failure, it is handled through the relevant service process. The goal is to return the system to normal, safe operation as quickly as possible.

Data security: Access and storage

As energy systems become more intelligent, data security becomes a central parameter. Increased digitalisation and network connections expand the potential attack surface, which places strict requirements on how data are handled.

Data from a BESS facility are transmitted and stored with appropriate access control and technical security measures.

When it comes to data access, we work from the principle of least privilege. That means only the technicians and systems that genuinely need to see the data to operate and maintain the facility have access. If operational data can be linked to a person or a specific customer, European data protection rules also apply. This includes requirements for data minimisation, purpose limitation, and appropriate technical security measures. Data are retained only as long as necessary to document the system's history and support operations.

ZynexGroup's approach to facility assessment

When we assess the potential for a new BESS facility, we build monitoring and data collection in from the start. A correctly sized system requires a solid data foundation, both before and after installation. We analyse the company's historical consumption data and grid connection to design a system that matches the real need.

After commissioning, our cloud monitoring helps ensure the system delivers the expected performance. This continuous data collection is also the foundation for our documentation. To follow the system's performance over time, it is essential that both we and the customer have full transparency around operation and efficiency throughout the period.

Overall perspective

BESS cloud monitoring is the link between the physical hardware and the business value. By monitoring parameters such as State of Charge, temperature, and voltage in real time, a detailed picture of the system's health is created.

Transparency around these data provides reassurance. The customer gets the overview needed for economics and operations, while technicians get the in-depth data required to prevent failures before they occur. At the same time, data are handled under strict requirements for security and access control. The result is a battery system that does not function as a black box, but as an integrated, monitored, and reliable part of the company's infrastructure.

Assess the potential for your facility

If you are considering whether industrial battery storage is the right solution for your business, we are happy to have a data-based conversation. By looking at your current grid connection and consumption profile, we can make an initial assessment of whether there is a match between your needs and what a BESS facility can offer.

You are welcome to contact us to learn more about how we design and monitor solutions tailored to Danish commercial and industrial companies.