The Battery Data Alliance is a Linux Foundation Energy project. We build open source software and standards for the battery industry — data formats, cycler interfaces, analysis tooling — so that researchers, manufacturers, and engineers can spend their time on batteries instead of fighting incompatible data pipelines.
Battery data comes from everywhere: lab cyclers, field deployments, simulations, published research. None of it works well together. Different equipment vendors, different file formats, different assumptions about what a “cycle” means or how to label a voltage column. Every organization ends up writing the same conversion scripts, the same ingestion code, the same validation logic. BDA exists to solve that problem once, in the open.
Our current work spans two areas:
Data specification — the Battery Data Format defines a canonical schema for cycler time-series data, backed by an ontology aligned with BattINFO/EMMO. The batterydf Python package reads vendor exports, normalizes them to BDF, and validates the result. The BDF datastore hosts contributed datasets from organizations like SINTEF and Microsoft.
Cycler control — open source Python interfaces for communicating with battery test equipment, including PyMacNet (Maccor) and PyCTIArbin (Arbin).
This forum is where the community discusses the spec, coordinates on tooling, and works through the practical problems of making battery data interoperable. If you’re here, you probably already know why this matters — take a look at the pinned summary of where BDF stands and jump into any thread that’s relevant to your work.