Introduction
This document outlines the data requirements for the TWAICE Energy Analytics platform. It specifies the supported BESS data model hierarchy, required sensor inputs and data resolution for best quality.
The customer’s cooperation and fulfillment of the outlined requirements are essential for the full delivery of TWAICE products and services.
Supported Battery Chemistries
TWAICE Energy Analytics platform is available for all common lithium-ion cell chemistries, listed below.
NMC/NCM (Lithium Nickel Manganese Cobalt Oxide)
NCA (Lithium Nickel Aluminium Cobalt Oxide)
LMO (Lithium Manganese Oxide)
LCO (Lithium Cobalt Oxide)
LNMO (Lithium Nickel Manganese Oxide)
LFP (Lithium Iron Phosphate)
BESS Data Model Components
Battery Energy Storage Systems (BESS) follow a hierarchical structure of components and sensors.
Below, a typical BESS data model components supported by TWAICE is given.
Name | Definition |
System (Site, Storage) | This identifies the BESS as one entity. Usually, one entity is defined by its operator. Multiple storage systems can be located at the same physical site. |
PCS (Inverter) | This component describes the physical inverter hardware component which performs the AC to DC conversion. |
Container (Cluster, BESS Enclosure) | Houses multiple battery strings (e.g., 8 strings per container). Equipped with a Container BMS for managing and monitoring all strings. Contains thermal management, electrical connections, and safety systems. |
String (Rack, Pack) | A string often refers to a series of connected components or units. A string could represent a series connection of modules or cells. It might be a way to organize and manage multiple components in a linear fashion. |
Module | A module is a standardized unit or component that can be easily integrated into a larger system. Modules refer to a self-contained unit of batteries with associated electronics for control and monitoring. It is usually the smallest component that can be replaced. |
Cell | A cell is the smallest unit within a battery, typically containing the active materials and electrolyte necessary for energy storage. In this hierarchy, a cell would represent the fundamental building block of the BESS. |
❗Notes:
Customers can customize naming of the component levels.
Customers may define additional hierarchy levels, any such custom additional levels are not included in TWAICE’s standard may not be reflected in the platform.
BESS Sensor Requirements
To enable the features of TWAICE Energy Analytics platform, a minimum set of sensor data should be provided by the customer. These sensors are essential to calculate key battery performance and health indicators such as SoC, SoH, and EFC.
We recommend the following minimum sensor inputs to be shared with TWAICE:
Sensor Data Resolution
While KPIs can be generated from a variety of data resolutions, higher fidelity data results in more precise calculations for battery performance and health.
The accuracy of performance and health KPIs may vary depending on the time and data resolution provided by the customer.
For optimal results, we require raw, high-resolution time series data (not down-sampled) from your BESS telematics system.
From battery time series data collected by your telematics system, we require the following parameters with the indicated resolution listed below.
Data Logging
Understanding your data logging method is critical for both accurate monitoring and diagnosis of any data inconsistencies.
❗This information should be shared with TWAICE before ingestion of data begins.
🔁 On-Change Logging
If the system logs data only when a value changes, please provide:
Heartbeat of those sensors ( TWAICE requires at least 10 minute heartbeat on all sensors)
Minimum expected value
Maximum expected value
Default value indicating invalid reading
📈 Continuous Logging
If data is logged at a fixed interval, please provide:
Native readings or aggregation (min/max/average)
Logging frequency
Minimum expected value
Maximum expected value
Default value indicating invalid reading
❗Note: Regardless of logging type, please inform TWAICE of any known or potential data gaps.
Additional Data Pattern Requirements
Time series data should reflect the following patterns for best quality of TWAICE KPIs provision.
Minimum of 30 full charge/discharge cycles required before SoC and SoH estimations can be generated.
Data should include all BESS operating states: charging, discharging, and resting.
BESS should be in regular operation (more than 200 Equivalent Full Cycles (EFC) annually).
Data gaps should be avoided, as they can affect KPI quality, particularly for EFC, throughput, SoC, and SoH.
Continuous data logging is recommended (see options above).
TWAICE Calculated KPIs
📘 For a complete list of KPIs calculated by TWAICE and delivered in Energy Analytics platform, please refer to the following article: Guide to TWAICE KPIs.