The global energy transition, especially the rapid rise of electric mobility, is driving an unprecedented surge in demand for battery cells. By 2030, around 200 new battery factories are expected to be built globally—equivalent to nearly 2.5 new plants every month [1]. To meet this growing demand efficiently and competitively, especially in Europe, battery cell manufacturing must become more digital, flexible, and adaptive.
Traditional battery cell plants and production lines, which rely heavily on fixed processes and turnkey solutions, are too rigid to accommodate fast innovation cycles or customized product variants. Instead, digitalization can enable future battery manufacturing that is highly automated using interconnected systems that can adapt quickly to new materials, formats, and technologies [2].
Innovative digital solutions such as digital twins, AI/ML-assisted optimization, and modular production architectures offer significant potential for reducing production costs and enhancing product quality. Data-driven optimization can reduce scrap rates and downtime, improve cell performance, and support traceability requirements such as those defined in the EU Battery Regulation.
However, realizing this potential depends on reliable data exchange between machines, systems, and actors across the value chain. A major obstacle to this is the lack of standardized, interoperable interfaces. Without a shared data language, integration efforts are time-consuming, error-prone, and costly. To overcome this, formalized and semantically consistent data descriptions must be established and aligned with industrial standards [3].
These descriptions can be based on existing domain knowledge and structured information models, which serve as the technical foundation for interoperable communication. Industrial communication standards such as OPC UA (Open Platform Communications Unified Architecture) provide a standardized framework for this, enabling the consistent and secure exchange of production data across heterogeneous systems.
In this context, the usability and practical implementability of the interface and underlying data model are critical to ensure broad adoption. This paper presents a requirements analysis for data standards in battery cell manufacturing, with a specific focus on these aspects. Based on the findings, a development procedure for domain-specific standards is derived.
Related work on information models and ontologies
A key element in achieving flexible and adaptive production is the creation of formalized data descriptions that make the semantics of data explicit and machine-readable. These descriptions provide the foundation for consistent interpretation across systems. To achieve this, semantically rich and context-aware data structures can be developed using ontologies. In the context of information science and data modeling, an ontology is a formal, explicit specification of a shared conceptualization. It defines a structured set of concepts, entities, and relationships relevant to a particular domain.
Ontologies can therefore help in making it possible to model production knowledge in a structured and meaningful way. These ontological models can then be translated into or embedded within formal information models, which define how data is organized, accessed, and communicated within and across systems. The information model complements the data model by adding contextual information, enabling consistent interpretation and use of the data.
In the domain of battery cell production, the development of ontologies has been part of numerous research projects. Many of these ontologies refer to authorities such as the IEC: IEC 60050, for example, defines terminology for batteries. However, they have an electrochemical or product-specific focus and lack definitions for production processes and systems. Moreover, these ontologies typically operate at a high level of abstraction and are not readily applicable for direct implementation in production environments.
Relevant previous work is listed below. The Battery Value Chain Ontology (BVCO) seeks to model processes along the entire battery value chain [4], while the Battery Interface Ontology (BattINFO) aims to provide a semantic basis for describing battery-related knowledge and for generating linked data [5]. The DigiBatMat project presents an ontology for structured data handling in lithium-ion battery cell production based on BVCO, BattINFO and others [6].
Zanotto et al. discuss data specifications for the digitalization of battery manufacturing and propose a data-driven modeling approach for cell production, based in part on the BattINFO ontology [7]. The DataBatt project has developed an ontology to enable semantic linking for the storage and evaluation of data and information [8]. In addition, the KIProBatt Ontology introduces a unified framework for the integration of a data space in battery production environments [9]. Haghi et al. propose a tailored digitalization approach based on the significance of specific process parameters [10].
While these approaches exist, definitions for production machines and processes are lacking. It thus remains obscure how to transfer these ontologies into a framework for interoperable data exchange within production environments.
The architecture of interoperable interfaces
While the content of a new standard is important, its acceptance and adoption also depend on the implementability and usability of the underlying technology. Interoperable interfaces that go beyond mere communication protocols serve as the technological foundation for standardized data exchange. In this context, a communication protocol defines the rules and formats for data exchange between devices or systems at various layers of a network. In contrast, an interoperable interface builds on lower-level protocols and provides a higher-level, structured framework.
A study by the VDMA involving over 600 companies found that, among those for whom interoperable interfaces are relevant, more than half consider such interfaces to be of high or very high importance. Of these, 90% have either already implemented the communication standard OPC UA (Open Platform Communications Unified Architecture) or plan to do so in the future [11].
OPC UA is a common industrial interoperable interface that enables secure and platform-independent data exchange [12].
This framework not only defines how data is transmitted but also how it is semantically described, enabling the meaningful interpretation of data across heterogeneous systems. Its architecture supports features such as encryption, scalability across device levels, and domain-specific data representation.
Based on a service-oriented architecture, OPC UA comprises logical layers, including a transport layer for protocol handling, a data model layer for publishing structured information, and basic services for client-server communication. Its information modeling framework not only allows the integration of existing and already defined standards—called OPC UA companion specifications—but also offers the possibility to model individual information models.
Methodology and requirements analysis
To derive an approach for developing implementable data standards for battery cell manufacturing, we conducted a systematic requirements analysis. In a first step, experts from industry—including machine manufacturers, automation engineers, and software developers—as well as from battery cell research, collected requirements for the standards. The collected requirements address various topics, including those necessary to realize the potential benefits of standardization, as well as challenges related to implementability.
Accordingly, they cover areas such as data acquisition and processing, requirements for the content of the information model, the modeling procedure and specific use cases relevant to battery cell manufacturing.
Following this, the requirements were systematically classified into three categories—data, process representation and use cases—as shown in Figure 1. Within each of these categories, the individual requirements were then refined and specified, and their priorities ranked by experts in the subject. This way, it is ensured that all important criteria are evaluated by experts from the field. A selection of requirements with highest priority is listed below.

In the first category, “Data”, the clear definition and future viability of the data format is defined as very important. It is also recognized that both raw data, for example at sensor level, and result data, including from proprietary system software, must be captured to ensure comprehensive data collection. The aggregation of the recorded data should be carried out via the standard to be developed and not in advance by other systems. This will ensure that the format of the data conforms to the standard. Data visualization was identified as being less directly affected by the standard and was therefore assigned a lower priority. In terms of implementability, OPC UA was identified as the most relevant existing communication standard.
OPC UA is also addressed in the category of “Process Representation”. One requirement is to enable interoperability with existing standards such as OPC UA Machinery, for example for the handling of process values. In general, creating a consistent structure for the information model is found to be of high priority. For each data point, the relevant metadata (for example time and location), the SI unit, and a serial number must be considered in the information model. The modeling must be based on the typical process chain of battery cell production.
A hierarchical structure is needed in which processes can be divided into sub-processes. The individual sub-processes, but also entire processes, if possible, must have a modular structure so that they can be linked and exchanged. This will also ensure that the standard is open to future process technologies replacing outdated ones in the process chain.
The third category deals with three specific “Use Cases” and considers which requirements are particularly important for them in particular. The selection of these particular use cases—traceability, the battery passport and process optimization—was driven by their relevance in the battery cell production domain. They encompass a broad spectrum of applications, ranging from upstream and shopfloor-near use cases such as process optimization through downstream data usage in the case of the battery passport to overall data aggregation and linking for traceability purposes.
The first use case addresses traceability, which refers to the tracking and tracing of data across the process chain and its assignment to materials and intermediate products. For the standard to be suitable for traceability, the relationships between production data and their influencing variables must be defined and subsequent changes to the models must be possible. In addition, meta-information about the individual parts used must be assigned to the finished intermediate and final products. This meta-information includes, for example, serial and batch numbers or tools used.
The second use case deals with the creation of a battery passport based on upcoming EU regulations that define which information must be stored for a produced battery. For this, traceability is an enabler. It is required to collect and include all the data needed to implement the passport in accordance with the standard. In addition, the ability to query process data from external systems is identified as very important for the battery passport.
The third use case considered is process optimization. In this use case, real-time and historical data are utilized to improve the performance and efficiency of production equipment. For this to be successful, the data relevant for deriving recommendations for process improvement must be available in alignment with the standard. It must also be possible to generate timestamped data records. In this way, recommendations for adjustments to current process parameters can be made based on existing data.
Derived procedure for developing a standard
The result of the analysis is a categorized list of prioritized requirements which forms the basis for deriving a procedure for developing standards. A schematic visualization of the desired standardized data exchange is shown in Figure 2. Machines on the shop floor are connected via standardized interfaces, enabling the use of semantically rich information models. This structured approach to data acquisition and interpretation—based on conventions from standards—forms the basis for interoperability and supports the aforementioned key use cases.

The following procedure for the creation of standards was derived based on the aforementioned requirements analysis, the prior and related work and the basic characteristics of interoperable interfaces such as OPC UA. The initial step is a systematic analysis of the battery cell production process chain, which enables the clear definition of all process steps and associated machinery. For this purpose, we recommend the use of ISA-88 or similar standardized procedures [13].
The analysis is then used to determine the number of distinct information models to be developed. Dividing the system into further subcomponents will support the integration of existing information models from related domains. Subsequent to this, a parameter list must be created for each process step.
As demonstrated by the requirements analysis, the selection of relevant parameters must be based on expert assessments, such as those from cell manufacturers and production machinery manufacturers, as well as existing literature and research and should be supported by relevant use cases (like those outlined above).
After identification, a clear and structured way of naming the parameters is crucial. The naming must consider prior work on ontologies and additional expert assessments to establish unambiguous designations. Combined with explanatory descriptions, the parameters must be assigned to machines and their subcomponents within structured system descriptions. These parameter definitions must be formulated in terms concrete enough to enable process experts to perform data mapping for their respective systems.
Altogether, this forms the basis for the development of the information model. In the case of OPC UA, types and subtypes are first to be defined, after which it will be checked whether existing variants of these (sub)-types can be integrated in order to build on existing standards. This implies that only the essential components of the model must be developed from the ground up.
The result is an information model built on a communication standard like OPC UA that is technically mature and readily deployable. The integrity of the modeling is assured by the provision of clear parameter descriptions.
The validation of the information model is to be conducted by subject experts, thereby ensuring its continuous enhancement. The actual development, integration and validation of the standard under discussion is not within the scope of this paper.
Challenges to an established data standard
The presented approach to developing a battery cell manufacturing standard offers a structured method that considers both technical and organizational requirements. Nevertheless, there are still some challenges involved in developing and establishing such a standard. One major challenge is determining an appropriate level of detail for the standard. All relevant parameters and requirements must be covered, particularly with regard to interoperability, traceability, and adaptability for future developments.
At the same time, however, the standard should not be overly complex or overdeveloped, as this would hinder its implementation and acceptance within the industry. Therefore, it is essential to achieve an optimal balance between comprehensiveness and practical feasibility. To achieve this, it is recommended that the standard provides users with the capability to independently extend the information model by adding specific proprietary properties, such as components or parameters, within its structure.
Consequently, the standard must include clear guidelines and instructions on how to model these extensions to ensure that it remain accessible and user-friendly. Only by keeping the standard adaptable and flexible can it be ensured that the standard stays compact while still accommodating special cases. Nevertheless, it should also be continuously validated against industry-relevant use cases in terms of its complexity and completeness. Furthermore, additional research focused on simplifying the implementation of such standards is essential. The objective should be to facilitate the adoption and integration of these standards across both new and legacy systems.
Such efforts will help to reduce barriers to implementation and broaden both applicability and acceptance. At this juncture, it is imperative to reiterate the necessity for the parameter descriptions and assignments to system components, as previously outlined, to be meticulously detailed and precise. This level of detail is essential to enable comprehensive data mapping. At the same time, research is being conducted into automated data mapping based on large language models, for example, in order to simplify and speed up future implementation [14].
Another challenge during standard development lies in the incorporation of parallel developments and preliminary work. As described in this article, many attempts have already been made to establish ontologies. Leveraging existing foundational work enables the consolidation of prior knowledge, minimizes duplication, and promotes interoperability across systems. However, realizing the full benefits of this approach requires sustained interdisciplinary collaboration and continuous stakeholder engagement throughout the development process. To ensure effective collaboration, it is crucial that the organizations responsible for the underlying technologies participate in the process of translating the developed models into standards. In the case of OPC UA, this role is fulfilled by the OPC Foundation which oversees the transformation of information models into standards known as OPC UA companion specifications.
For the standard to be successful following its technical implementation, it must be effectively disseminated and widely adopted within the industry. To engage relevant stakeholders in a unified manner, collaboration with corporate networks must be pursued. As part of the ENLARGE project, this effective collaboration with relevant industry partners is essential to advance the development of standards in battery cell manufacturing [15]. In general, platforms for collaboration, industry feedback, and ongoing development play a critical role in the path toward a standardized battery production chain.
Bibliography
[1] Grandl, G.; Duffner, F.; Baum, M.; Möhrke, M.; Wu, X.; et al.: Battery Manufacturing 2030: Collaborating at Warp Speed: What it takes for equipment manufacturers to ride the coming wave of breakneck growth, 2024. URL: https://www.porsche-consulting.com/sites/default/files/2024-02/battery_manufacturing_2030_porsche_consulting_2024.pdf, accessed 07.05.2025.[2] Michaelis, S.; Schütrumpf, J.; Kampker, A.; et al.: Roadmap Batterie-Produktionsmittel 2030: Update 2023, Frankfurt, 2023. URL: https://vdma.org/documents/34570/35405938/VDMA+Batterieproduktion_Roadmap_2023.pdf/ee2452cd-ed44-93bf-4762-6a09ce29b4b7?t=1683038844317, accessed 14.05.2025.
[3] Ayerbe, E.; Berecibar, M.; Clark; et al.: Digitalization of battery manufacturing: current status, challenges, and opportunities. In Advanced Energy Materials (2022), 12(17), 2102696.
[4] Stier, S.; Gold, L.; Fraunhofer ISC: Battery Value Chain Ontology. URL: https://github.com/Battery-Value-Chain-Ontology/ontology, accessed 13.05.2025.
[5] Clark, S.; Friis, J.; Bleken, F. L.; et al.: Battery Interface Ontology. URL: https://github.com/BIG-MAP/BattINFO, accessed 10.05.2025.
[6] Mutz, M.; Perovic, M.; Gümbel, P.; et al.: Toward a Li-Ion Battery Ontology Covering Production and Material Structure. In Energy Technology 11 (2023) 5.
[7] Zanotto, F. M.; Dominguez, D. Z.; Ayerbe, E.; et al.: Data specifications for battery manufacturing digitalization: current status, challenges, and opportunities. In Batteries & Supercaps 5 (2022) 9, e202200224.
[8] Stier, S.; Gannouni, A.: DataBatt 4.0 Ontology. URL: https://github.com/DataBatt-4-0/ontology, accessed 13.05.2025.
[9] Stier, S. P.; Xu, X.; Gold, L.; Möckel, M.: Ontology-Based Battery Production Dataspace and Its Interweaving with Artificial Intelligence-Empowered Data Analytics. In Energy Technology 12 (2024) 4: 2301305.
[10] Haghi, S.; Summer, A.; Bauerschmidt, P.; Daub, R.: Tailored digitalization in electrode manufacturing: the backbone of smart lithium‐ion battery cell production. In Energy Technology 10 (2022) 10, 2200657.
[11] VDMA: Studie zur Interoperabilität im Maschinen- und Anlagenbau, 2021. URL: www.vdma.org/documents/34570/0/Studie%20„Interoperabilität%20im%20Maschinen-%20und%20Anlagenbau“_Expertenseite%20OPC%20UA.pdf/0083b153-a3c0-501f-08ce-e93c82627eb0, accessed 14.05.2025.
[12] OPC Foundation: Unified Architecture. URL: https://opcfoundation.org/about/opc-technologies/opc-ua/, accessed 14.05.2025.
[13] International Society of Automation. ANSI/ISA-88.00.01-2010 Batch Control Part 1: Models and Terminology, 2010 (88.00.01-2010). URL: https://www.isa.org/products/ansi-isa-88-00-01-2010-batch-control-part-1-models, accessed 04.07.2025.
[14] Jaspers, W.; Schmetz, A.; Roth, D.; Becker, B.; Kampker, A.: Identification of machine parameters in battery cell production: A comparison of different methods and approaches for mapping parameters. In Procedia CIRP 134 (2025).
[15] ENLARGE consortium: SynBatt Batteriezellproduktion ENLARGE. URL: www.enlarge-projekt.de, accessed 14.05.2025.
Potentials: Globalization
Solutions: Safety
