Battery Storage
Mirox monitors battery energy storage systems (BESS) as part of your plant, surfacing the full storage hierarchy and its state so you can track capacity, health, and faults from a single view.
Concept
When a battery system reports through one of your loggers, Mirox automatically discovers its structure and presents it as a four-level hierarchy. You do not enter components by hand — the platform builds the tree from the incoming data and keeps it in sync.
| Level | What it represents |
|---|---|
| Box | The battery container / cabinet (nameplate AC power and energy live here) |
| Storage | A storage unit within a box |
| Module | A module within a storage unit |
| Cell | An individual cell — the most granular monitored element |
Each level is read-only for structure: you can rename a component, hide it from counts and dashboards, mark it as manually verified, and link it to a datasheet, but the components themselves are created and updated from the live data feed.
Info
Battery components are discovered through the data feed, not entered manually. A component you cannot see has not yet been observed in the incoming metrics.
Monitored Parameters
For each component in the hierarchy, Mirox tracks the metrics the battery system reports:
Power and Energy
- Charge / discharge power — current rate (W)
- Energy throughput — charged and discharged energy over a period (Wh)
- State of Charge (SOC) — current stored capacity as a percentage
- State of Health (SOH) — degradation indicator
Electrical and Thermal Status
- Voltage — at module and cell level
- Current — charge and discharge currents
- Temperature — module and cell temperatures
- Cell health — the platform tracks how many cells are currently healthy
Capacity and Status Overview
Each park with a battery system exposes a battery KPI summary you can read directly:
- Component counts per level — boxes, storage units, modules, and cells (hidden components excluded)
- Healthy cell count — how many cells are currently reporting healthy
- Nominal AC power and energy — summed from the linked box datasheets (nameplate capacity)
- Verification status — how many boxes are manually verified versus still unverified
- Needs-attention count — boxes or modules flagged as requiring attention
Datasheets
You can attach reusable equipment datasheets — for battery storage, box, module, and cell — to your components. The nameplate AC power and energy in the capacity overview are read from the box datasheet, so keeping datasheets up to date keeps your capacity totals accurate.
Production Page
A plant whose main asset is the battery (park type Battery) opens on a Production page — the storage seen from its grid connection point rather than from its cells:
- Grid power and today's export / import energy from the plant's feed-in meter (positive = export to the grid)
- Battery power as the sum of the storage units' AC side (positive = charging), with today's charged / discharged energy from the units' own counters
- A chart of grid exchange beside battery power over the selected day, week, month or year, with the state of charge where the storage reports one
- A table of every storage unit on its AC side: signed power, reactive power, frequency, line voltages and phase currents where a feeder relay measures them, lifetime energies, the device's own status word and the age of its newest sample
The page reads the same shape for a storage behind a solar or wind plant, so a battery that is an add-on to another plant type is served by it as well — there it stays reachable next to the plant's own production page. The Battery page remains the technical view: state of charge, racks and cells.
Park Controller
Where the storage plant is run by a central park controller of the kind Battery plant, the Battery page shows its card above the graphs: the controller's operating state, its condition flags (running, standby, fault, state of charge high or low, switchgear open and the others the controller reports), the maker's own status text and code, the measurements it provides — state of charge, energy and health, the available charge and discharge power, units connected and running, converter and storage availability — and when it last reported. A plant without a controller shows no card. See Solar Trackers and Park Controllers — Park controllers.
Alarms and Notifications
Mirox judges every battery unit — the power converters (PCS) and the battery containers — from the status word it reports every minute, and notifies on the judged state rather than on each raw manufacturer code:
- Stopped by a fault — the status word says fault for 5 consecutive minutes. The unit's event opens then; the plant's single "components down" notification (High) follows after 15 minutes.
- Not communicating — one unit's data stops while the rest of its data source keeps delivering: an event after 15 minutes, the plant notification after 30 minutes. When the whole data source goes silent, one Source availability event speaks for it instead.
- Device fault while running (Normal) — the unit reports a fault of its own but keeps operating. Recorded as an event for service, not notified by default.
- Safety alarm (Critical) — a fire alarm, smoke or gas detection, thermal runaway, a released fire suppression or an arc. Checked every minute and sent at once. Errors of the fire-detection equipment itself are device faults, not safety alarms.
A park controller of the storage plant is judged as one unit for the whole storage: its fault notifies on its own (Critical) after two consecutive one-minute reads, a safety alarm it reports notifies at once, and its standby or an operator stop is recorded as Park controller stopped by command without notifying — see Alarm Levels — Solar trackers and park controllers.
Idle, standby and stops someone ordered are status, never faults. The manufacturer's own alarm and warning list stays visible on the battery pages as detail. In the event list it is filed under the Vendor alarms category, like that of inverters and wind turbines, and it does not notify.
Storage on solar and wind plants
These checks run wherever battery hardware is present — not only on plants of type Battery. A solar plant with a storage system gets the same battery alarms, and a hybrid site raises one "components down" notification that lists inverters and battery units together. On the Monitor page such a plant shows its battery units next to its inverters.
Battery events are filed in the event list under the same categories as those of every other plant type: faults, stops and safety alarms under Production, a unit that stops communicating under Availability, the manufacturer's own alarm list under Vendor alarms. Earlier records may still show the Battery category. They notify through the Production row of your notification settings — there is no separate battery row. The thresholds and the measurements behind them are explained in Alarm Levels — Battery storage.
Data Collection
Battery data reaches Mirox through a dedicated adapter for your storage system. The platform already supports FREQCON BESS systems, and we can build adapters for other battery and storage controllers on request — see the Data Scraper for how the edge agent collects and standardizes plant data.
Performance Analysis (Planned)
The Digital Twin analysis engine currently covers solar PV only. Automated battery analysis — round-trip efficiency tracking, degradation-rate analysis, cycle accounting, and loss attribution — is planned. Today you can monitor the live battery state and capacity described above and receive the fault and safety alarms described in Alarms and Notifications; automated performance findings for batteries are not yet generated.
The following capabilities are planned for battery storage:
- Round-trip efficiency and cycle-count tracking
- Degradation and remaining-useful-life estimation
- Charge / discharge optimization insight
- Financial analysis for arbitrage, frequency regulation, and capacity-market participation
Related Features
- Plant Types Overview — the full catalog of plant types Mirox supports
- Solar Plants — the fully analyzed PV vertical and its component model
- Digital Twin — the analysis engine (solar today, battery planned)
- Real-Time Monitoring — live metric collection and visualization
- Alarm Levels — battery alarms, their levels and timing
- Data Scraper — how edge adapters collect and standardize plant data