MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
    • VPN Services
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request an Integration
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
    • Raw Data Export for Excel
  • Remote Access
  • AI in Mirox
  • History Import
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
    • VPN Services
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request an Integration
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
    • Raw Data Export for Excel
  • Remote Access
  • AI in Mirox
  • History Import
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
    • Alarm System

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.

LevelWhat it represents
BoxThe battery container / cabinet (nameplate AC power and energy live here)
StorageA storage unit within a box
ModuleA module within a storage unit
CellAn 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.

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; automated health and 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
  • Data Scraper — how edge adapters collect and standardize plant data
Prev
Wind Plants
Next
Alarm System
MIT Licensed | Copyright 2026 Mirox Verwaltungs GmbH | Privacy