Cell tracking controller, battery manufacturing system comprising same, and battery manufacturing method

Abstract

According to exemplary embodiments, a cell tracking controller can be provided. The cell tracking controller may comprise: a cell ID collection unit for collecting a cell ID, which is identification information of a battery cell; a data collection unit for collecting at least one from among inspection data of the battery cell, measurement data of the battery cell, and equipment data collected from equipment of a battery cell manufacturing process or an equipment controller for controlling the equipment; and a cell ID mapping unit for mapping, to the cell ID, at least one from among the inspection data, the measurement data, and the equipment data corresponding to the cell ID, wherein the cell ID collection, the data collection and the data mapping can be performed in real time.

Description

Cell tracking controller, battery manufacturing system including the same, and battery manufacturing method

[0001] The present invention relates to a cell tracking controller, a battery manufacturing system including the same, and a battery manufacturing method.

[0002] This application claims the benefit of priority based on Korean Patent Application No. 10-2024-0195627 dated December 24, 2024 and Korean Patent Application No. 10-2024-0195946 dated December 24, 2024, and all contents disclosed in the documents of said Korean patent applications are incorporated herein as part of this specification.

[0003] Batteries are manufactured through electrode processes, assembly processes, activation processes, and module / pack manufacturing processes.

[0004] The electrode process may include a coating process, a roll press process, and a slitting process. In the coating process, an active material and an insulating material may be applied to the surface of a current collector (electrode sheet). In the roll press process, the electrode sheet may be pressed by pressure rolls. The roll press process can determine the density, performance, and surface quality of the electrode. In the slitting process, the electrode sheet may be cut into multiple electrode sheets according to the design of the battery cell.

[0005] In the assembly process, the electrode sheet can be cut to a predetermined size and manufactured into an electrode (unit electrode). The electrode can be laminated with a separator to form an electrode assembly such as a half-cell, monocell, bicell, or stack cell. The electrode assembly can be housed within a battery case and filled with an electrolyte to form a packaged cell.

[0006] A packaging cell can become a finished battery product through an activation process, etc. Electrode assemblies including electrodes and packaging cells, etc., before becoming a finished battery product, can be referred to as semi-finished battery products.

[0007] The above-mentioned finished battery product can become a battery module through a modularization process. Multiple battery modules can be assembled to form a battery pack. Battery modules and battery packs can also be forms of the finished battery product.

[0008] In a narrow sense, a finished battery product that has been endowed with characteristics as a battery after an activation process may be referred to as a battery cell. However, in the present invention, a part of an electrode sheet that can serve as an electrode, an actual cut electrode (unit electrode), a battery semi-finished product containing the electrode, and a finished battery product containing the electrode are all referred to as a battery cell. That is, the battery components (electrode sheet, electrode), semi-finished product, and finished product of the forms listed above all contain a part intended to be an 'electrode' or an 'electrode'. Therefore, by adding an ID (cell ID) indicating the identity of the electrode, it can be distinguished from other electrodes or battery semi-finished products or finished products containing other electrodes.

[0009] Accordingly, the battery cell mentioned in the present disclosure is a concept that encompasses all battery components, semi-finished products, and finished products that can be distinguished from other battery cells by a cell ID.

[0010] In each of the aforementioned battery manufacturing processes, a process controller may be provided for process control. The process controller is also referred to as an equipment controller in the sense that it controls each process equipment. In addition, an inspection device and a measuring device may be provided to inspect the battery cells of each process.

[0011] The above-mentioned equipment controller serves as a channel for collecting equipment data from sensors equipped in the equipment and transmitting it to an upper control system. In addition, inspection data and measurement data collected by the above-mentioned inspection and measuring instruments can also be transmitted to the upper control system.

[0012] The above-mentioned upper control system may include various subsystems (servers) for each purpose, such as operating and analyzing the battery manufacturing process and detecting process anomalies.

[0013] At the upper level of the above subsystem, a data warehouse may ultimately be provided to collect and store the data and provide a quality post-analysis environment.

[0014] However, the data provided to each subsystem is either mapped to time-series data or mapped to cell IDs, resulting in different data management standards for each subsystem. For example, time-series-based data is provided to FDC (Fault Detection & Classification) servers that detect equipment anomalies and APC (Advanced Process Control) servers that automatically calibrate equipment controllers. On the other hand, cell ID-based data is provided to SPC (Statistical Process Control) servers that statistically analyze data to monitor and regulate manufacturing processes.

[0015] For this reason, even if the data is the same (equipment data, inspection data, or measurement data), there is no link connecting the data acquired between each subsystem, making organic data linkage and analysis difficult.

[0016] Furthermore, even when quality is analyzed by generating monitoring data, such as roll maps, based on the aforementioned collected data, there were limitations in analyzing the cause in real time when issues regarding quality or equipment occurred.

[0017] For example, when data was provided to a data warehouse for cause analysis, the data loading cycle was relatively long, ranging from several hours to several days. Consequently, even if problems such as data omissions occurred in each process, it was difficult to detect or respond to the data omissions in real time.

[0018] Furthermore, when a data tracking function was added to an equipment controller, which is intended for the specific purpose of controlling equipment, it placed a load on the controller, making real-time data communication difficult. Moreover, since data resources were consumed for cell tracking, there were adverse effects, such as slowed operation or operational errors occurring in the equipment controller responsible for actual control.

[0019] For this reason, there is a challenge to establish a real-time data collection environment in the battery manufacturing system.

[0020] [Patent Literature]

[0021] Korean Published Patent No. 2023-0119607

[0022] The present invention aims to unify data management standards by mapping data using cell IDs as keys.

[0023] In addition, it is intended to provide a real-time data collection environment in the battery manufacturing system.

[0024] According to exemplary embodiments of the present invention for solving the above-mentioned problem, a cell tracking controller may be provided.

[0025] The above cell tracking controller is,

[0026] A cell ID collection unit configured to collect a cell ID, which is identification information of a battery cell;

[0027] A data collection unit configured to collect at least one of inspection data of a battery cell, measurement data of a battery cell, and equipment data collected from equipment of a battery cell manufacturing process or from an equipment controller controlling said equipment; and

[0028] It includes a cell ID mapping unit configured to map at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID, and

[0029] The above cell ID collection, data collection, and data mapping can be configured to be performed in real time.

[0030] The battery cell may be at least one of a part of an electrode sheet, an electrode formed by cutting the electrode sheet to a predetermined size, a battery semi-finished product including the electrode, and a battery finished product including the electrode.

[0031] The cell tracking controller is configured to transmit mapped data to at least one upper server and can be configured to perform cell ID collection, data collection, data mapping, and data transmission in real time.

[0032] The cell tracking controller may further include a data conversion unit that converts the mapped data into a form required by the upper server, and may be configured to perform cell ID collection, data collection, data mapping, data conversion, and data transmission in real time.

[0033] The above real-time may be the time required for one battery cell to move from a first process position where one battery cell is located to a second process position, which is the location of the next battery cell preceding the one battery cell.

[0034] The above cell ID collection unit is,

[0035] A cell ID detection unit that detects the cell ID of the above battery cell, and

[0036] It may include a cell ID tracking unit that tracks the cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit.

[0037] The above cell ID collection unit is,

[0038] A virtual cell ID generation unit that generates a virtual cell ID corresponding to the above battery cell, and

[0039] It may include a virtual cell ID tracking unit that tracks the virtual cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit.

[0040] The above cell ID collection unit is,

[0041] A virtual cell ID generation unit that generates a virtual cell ID corresponding to the above battery cell, and

[0042] A virtual cell ID tracking unit that tracks the virtual cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit, and

[0043] It may include a cell ID detection unit that detects the cell ID of the battery cell and reports the cell ID, or the cell ID and virtual cell ID, to the cell ID mapping unit.

[0044] The mapped data is,

[0045] A main key data set including cell IDs, and

[0046] It may include the source time at which the data signal was collected.

[0047] The above main key data set is,

[0048] It may include at least one of an equipment ID, a lot ID, a data collection unit ID, and location data indicating the location of the battery cell in the battery cell manufacturing process.

[0049] According to another aspect of the present disclosure, a battery manufacturing system may be provided.

[0050] The above system is,

[0051] A cell tracking controller configured to collect cell IDs, which are identification information of battery cells;

[0052] It includes at least one inspection device configured to collect inspection data of a battery cell, at least one measuring device configured to collect measurement data of a battery cell, and at least one equipment controller configured to collect equipment data from equipment of a battery cell manufacturing process.

[0053] The cell tracking controller may be configured to map at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID.

[0054] The above system further includes a T-branching module that branches the equipment data into equipment control data and monitoring data, and

[0055] The above T branch module can transmit the monitoring data directly to the cell tracking controller without passing through the facility controller.

[0056] The above equipment controller includes an equipment data address where equipment data is temporarily stored, and a cell tracking dedicated address.

[0057] The above equipment controller may be configured to extract equipment data from the equipment data to be transmitted to the cell tracking controller, collect it in the cell tracking dedicated address, and transmit the collected data to the cell tracking controller.

[0058] As another aspect of the present disclosure, a battery manufacturing system is,

[0059] A cell tracking controller configured to collect cell IDs, which are identification information of battery cells;

[0060] It includes at least one of the equipment for a battery cell manufacturing process, comprising at least one inspection device configured to collect inspection data of a battery cell, at least one measuring instrument configured to collect measurement data of a battery cell, and at least one sensor configured to collect equipment data.

[0061] The cell tracking controller may be configured to map at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID.

[0062] The above cell tracking controller is,

[0063] Mapped data can be transmitted to at least one upper server, and the cell ID collection, data collection, data mapping, and data transmission can be configured to be performed in real time.

[0064] The cell tracking controller further includes a data conversion unit that converts the mapped data into a form required by the upper server.

[0065] The cell tracking controller above may be configured to perform cell ID collection, data collection, data mapping, data conversion, and data transmission in real time.

[0066] The above battery manufacturing system may further include at least one upper server that performs at least one of the following operations.

[0067] 1) Generation of monitoring data based on mapped data

[0068] 2) At least one of anomaly detection and anomaly alarm generation based on mapped data

[0069] 3) Generation of correction values ​​for process conditions (Recipe Parameters) based on mapped data

[0070] According to another aspect of the present disclosure, a method for manufacturing a battery may be provided.

[0071] The above manufacturing method is,

[0072] A step of collecting a cell ID, which is identification information of a battery cell;

[0073] A step of collecting at least one of inspection data of the battery cell, measurement data of the battery cell, and equipment data collected from equipment of the battery cell manufacturing process or equipment controller controlling the equipment; and

[0074] The method includes the step of mapping at least one of inspection data, measurement data, and equipment data corresponding to the cell ID collected above to the cell ID, and

[0075] The above cell ID collection, data collection, and data mapping can be characterized by being performed in real time.

[0076] The above manufacturing method may further include the step of transmitting mapped data to at least one upper server.

[0077] The above manufacturing method further includes a data conversion step of converting the mapped data into a form required by the upper server, and

[0078] The above cell ID collection, data collection, data mapping, data conversion, and data transmission can be performed in real time.

[0079] The above manufacturing method is,

[0080] The above equipment data further includes a step of branching into equipment control data and monitoring data,

[0081] The above branched monitoring data can be mapped to the above cell ID.

[0082]

[0083] A cell tracking controller may be provided as an exemplary embodiment.

[0084] The above cell tracking controller is,

[0085] A cell ID collection unit configured to collect a cell ID, which is identification information of a battery cell;

[0086] A data collection unit configured to collect at least one of inspection data of a battery cell, measurement data of a battery cell, and equipment data of a battery cell manufacturing process;

[0087] A cell ID mapping unit configured to map at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID; and

[0088] The above data conversion unit may include a data conversion unit that converts binary data mapped to a cell ID into string data.

[0089] The above data conversion unit may be configured to transmit string data mapped to a cell ID to at least one upper server.

[0090] The above cell ID collection, data collection, data mapping, data conversion, and data transmission can be performed in real time.

[0091] The above real-time may be the time required for one battery cell to move from a first process position where one battery cell is located to a second process position, which is the location of the next battery cell preceding the one battery cell.

[0092] A battery manufacturing method may be provided as an exemplary embodiment.

[0093] The above manufacturing method is,

[0094] A step of collecting a cell ID, which is identification information of a battery cell;

[0095] A step of collecting at least one of inspection data of a battery cell, measurement data of a battery cell, and equipment data of a battery cell manufacturing process;

[0096] A step of mapping at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID; and

[0097] It may include a step of converting binary data mapped to the cell ID into string data.

[0098] The above manufacturing method may further include the step of transmitting string data mapped to a cell ID to at least one upper server.

[0099] An exemplary battery manufacturing system may be provided.

[0100] The above system is,

[0101] A cell tracking controller configured to collect cell IDs, which are identification information of battery cells; and

[0102] It includes an equipment controller configured to collect equipment data from equipment of a battery cell manufacturing process, and

[0103] The above cell tracking controller is,

[0104] Equipment data, which is binary data corresponding to the cell ID, is mapped to the cell ID, and

[0105] Convert the above mapped binary data into string data, and

[0106] It may be characterized by transmitting string data mapped to the cell ID above to at least one upper server.

[0107] An exemplary battery manufacturing system may be provided.

[0108] The above system is,

[0109] A cell tracking controller configured to collect cell IDs, which are identification information of battery cells; and

[0110] The battery cell manufacturing process equipment includes at least one sensor for sensing equipment data, and

[0111] The above cell tracking controller is,

[0112] Equipment data, which is binary data corresponding to the cell ID, is mapped to the cell ID, and

[0113] Convert the above mapped binary data into string data, and

[0114] It may be characterized by transmitting string data mapped to the cell ID above to at least one upper server.

[0115] An exemplary battery manufacturing system may be provided.

[0116] The above system is,

[0117] It further includes at least one of at least one inspector configured to collect inspection data of a battery cell and at least one measuring instrument configured to collect measurement data of a battery cell.

[0118] The above cell tracking controller is,

[0119] At least one of inspection data, measurement data, and equipment data, which are binary data corresponding to the cell ID, is mapped to the cell ID, and

[0120] Convert the above mapped binary data into string data, and

[0121] It may be characterized by transmitting string data mapped to the cell ID above to at least one upper server.

[0122] An exemplary battery manufacturing system is,

[0123] A cell tracking controller configured to collect cell IDs, which are identification information of battery cells; and

[0124] It further includes at least one of at least one inspector configured to collect inspection data of a battery cell and at least one measuring instrument configured to collect measurement data of a battery cell.

[0125] The above cell tracking controller is,

[0126] At least one of inspection data, measurement data, and equipment data, which are binary data corresponding to the cell ID, is mapped to the cell ID, and

[0127] Convert the above mapped binary data into string data, and

[0128] It may be characterized by transmitting string data mapped to the cell ID above to at least one upper server.

[0129]

[0130] According to one aspect of the present disclosure, a battery cell tester may be provided.

[0131] The above battery cell tester generates test data based on the test signal of the battery cell, and

[0132] Receive the cell ID of the above battery cell, and

[0133] Mapping data is generated by mapping inspection data corresponding to the cell ID to the cell ID, and

[0134] The above mapping data can be configured to be transmitted to at least one upper server.

[0135] The above battery cell tester is,

[0136] Receive the above cell ID from the cell tracking controller, and

[0137] The above mapping data can be configured to be transmitted to the cell tracking controller.

[0138] The above inspection device may include an inspection data generation unit configured to generate inspection data based on an inspection signal of a battery cell and to generate the mapping data.

[0139] The above inspector may further include an API configured to receive the cell ID from the cell tracking controller and transmit the mapping data to the cell tracking controller.

[0140] The above inspection device may further include a data collection unit configured to collect mapping data from the inspection data generation unit and transmit the collected mapping data to at least one upper server.

[0141] The above API may be configured to store a log file regarding at least one of the processes of receiving a cell ID through the API, transmitting mapping data to a controller for tracking battery cell IDs, and collecting the generated mapping data within the inspector.

[0142] The above API can be written based on the TCP / IP protocol.

[0143] According to another aspect of the present disclosure, a method for manufacturing a battery may be provided.

[0144] The above manufacturing method comprises the step of generating inspection data based on an inspection signal of a battery cell;

[0145] A step of receiving the cell ID of the battery cell; and

[0146] A step of generating mapping data by mapping inspection data corresponding to the cell ID to the cell ID; and

[0147] It may include the step of transmitting the above mapping data to at least one upper server.

[0148] The above manufacturing method may further include the step of transmitting the mapping data to a cell tracking controller.

[0149] The above manufacturing method may further include the step of the cell tracking controller transmitting the mapping data to at least one upper server.

[0150] The above cell ID is received from the cell tracking controller via API, and

[0151] The above API may be configured to transmit the above mapping data to the cell tracking controller.

[0152] The above manufacturing method may further include a step of collecting the mapping data before the step of transmitting the mapping data to an upper server.

[0153] The above API may be configured to store a log file regarding at least one of the processes of receiving a cell ID through the API, transmitting mapping data to a cell tracking controller through the API, and collecting mapping data.

[0154] According to one aspect of the present disclosure, a battery manufacturing system may be provided.

[0155] The above system is,

[0156] A cell tracking controller configured to collect cell IDs of battery cells; and

[0157] It includes an inspector configured to collect inspection data of battery cells, and

[0158] The cell tracking controller is configured to transmit a cell ID to the inspector, and

[0159] The above-described inspector may be configured to generate mapping data by mapping inspection data corresponding to the cell ID to the cell ID.

[0160] The above inspector may be configured to transmit the mapping data to at least one upper server and at least one of the cell tracking controller.

[0161] The above inspection device is,

[0162] It may further include an API configured to receive the cell ID from the cell tracking controller and transmit the mapping data to the cell tracking controller.

[0163] The above API may be configured to store a log file regarding at least one of the processes of receiving a cell ID through the API, transmitting mapping data to a controller for tracking battery cell IDs, and collecting mapping data within the inspector.

[0164] The cell tracking controller above transmits mapping data received from the inspector to the first server, and

[0165] The above inspector can transmit the above mapping data to a second server.

[0166]

[0167] According to one aspect of the present disclosure, a battery manufacturing system may be provided.

[0168] The above system includes a cell tracking controller configured to collect cell IDs, which are identification information of battery cells;

[0169] A data collection device configured to collect high-frequency data generated according to the progress of the process for the battery cell; and

[0170] It may include a mapping device configured to map high-frequency data corresponding to the cell ID to the cell ID.

[0171] The above high-frequency data may be time-series data that fluctuates at a frequency of kHz or MHz or higher for a period of time of 1 second or less.

[0172] The above high-frequency data may be at least one of vibration data of a driving device included in the battery manufacturing process equipment and data of the current flowing through the driving device.

[0173] The above data collection device is,

[0174] At least one high-frequency sensing sensor that detects a high-frequency signal, and

[0175] It includes data acquisition hardware configured to collect raw data of high-frequency data by conditioning, converting, and processing the high-frequency signal, and

[0176] The collected raw data can be configured to be transmitted to the mapping device.

[0177] The above mapping device may be configured to convert the raw data of the high-frequency data into high-frequency feature data by compressing and / or sampling it.

[0178] The above mapping device may be configured to transmit high-frequency feature data mapped to the cell ID to at least one upper server.

[0179] The above mapping device is,

[0180] High-frequency raw data for a first time period is collected from the above data collection device at every first period, and

[0181] It can be configured to transmit high-frequency feature data for a first time period to the upper server at each of the first cycles.

[0182] The above system may further include a fault detection and classification server that detects whether there is an abnormality in the battery cell manufacturing process based on mapping data between the cell ID and high-frequency data.

[0183] The above system further includes at least one of at least one inspector configured to collect inspection data of the battery cell and at least one measuring instrument configured to collect measurement data of the battery cell.

[0184] The cell tracking controller transmits the cell ID to at least one of the inspector and measuring instrument, and

[0185] At least one of the above-mentioned inspection device and measuring device may be configured to map at least one of the inspection data and measuring data corresponding to the cell ID to the cell ID.

[0186] The above system can perform at least one of the following operations based on at least one of the inspection data and measurement data mapped to the cell ID and comparison data of the high-frequency data mapped to the same cell ID as the cell ID.

[0187] 1) Generation of monitoring data based on comparison data

[0188] 2) At least one of process anomaly detection and anomaly alarm generation based on comparison data

[0189] 3) Generation of correction values ​​for cell manufacturing process-related parameters based on comparison data

[0190] According to one aspect of the present disclosure, a method for manufacturing a battery may be provided.

[0191] The above manufacturing method is,

[0192] A step of collecting a cell ID, which is identification information of a battery cell;

[0193] A step of collecting high-frequency data generated according to the progress of the process for the battery cell; and

[0194] It may include a step of mapping high-frequency data corresponding to the cell ID to the cell ID.

[0195] The mapping step may further include a step of converting the raw data of the high-frequency data into high-frequency feature data by compressing and / or sampling it.

[0196] The above manufacturing method may further include the step of transmitting high-frequency feature data mapped to the cell ID to at least one upper server.

[0197] In the above manufacturing method,

[0198] Collect high-frequency raw data for the first time period during each first cycle, and

[0199] High-frequency feature data for a first time period during each of the above first cycles can be transmitted to the upper server.

[0200] The above manufacturing method is,

[0201] The method may further include a step of detecting whether there is an abnormality in the battery cell manufacturing process based on the mapping data of the cell ID and high-frequency data.

[0202] The above manufacturing method is,

[0203] The method may further include the step of mapping at least one of the inspection data and measurement data of the battery cell corresponding to the cell ID to the cell ID.

[0204] The above manufacturing method is,

[0205] Based on at least one of the inspection data and measurement data mapped to the cell ID and comparison data of the high-frequency data mapped to the same cell ID as the cell ID, at least one of the following operations can be performed.

[0206] 1) Generation of monitoring data based on comparison data

[0207] 2) At least one of process anomaly detection and anomaly alarm generation based on comparison data

[0208] 3) Generation of correction values ​​for cell manufacturing process-related parameters based on comparison data

[0209]

[0210] According to one aspect of the present disclosure, a cell tracking controller may be provided.

[0211] The cell tracking controller above comprises a cell ID data collection unit configured to collect a cell ID, which is identification information of a battery cell;

[0212] Equipment data collection unit configured to collect equipment data from equipment of a battery cell manufacturing process or from an equipment controller that controls said equipment; and

[0213] It includes a cell ID mapping unit configured to map equipment data corresponding to the collected cell ID to the cell ID, and

[0214] The above data collection and data mapping can be configured to be performed in real time.

[0215] The cell tracking controller is configured to transmit mapped data to at least one upper server, and

[0216] The above data collection, data mapping, and data transmission can be configured to be performed in real time.

[0217] The cell tracking controller further includes a data conversion unit that converts the mapped data into a form required by the upper server.

[0218] The above data collection, data mapping, data conversion, and data transmission can be configured to be performed in real time.

[0219] The above cell ID data collection unit is,

[0220] A cell ID detection unit that detects the cell ID of the above battery cell, and

[0221] It may include a cell ID tracking unit that tracks the cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit.

[0222] The above cell ID data collection unit is,

[0223] A virtual cell ID generation unit that generates a virtual cell ID corresponding to the above battery cell, and

[0224] It may include a virtual cell ID tracking unit that tracks the virtual cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit.

[0225] The above cell ID data collection unit is,

[0226] A virtual cell ID generation unit that generates a virtual cell ID corresponding to the above battery cell, and

[0227] A virtual cell ID tracking unit that tracks the virtual cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit, and

[0228] It may include a cell ID detection unit that detects the cell ID of the battery cell and reports the cell ID, or the cell ID and virtual cell ID, to the cell ID mapping unit.

[0229] According to one aspect of the present disclosure, a battery manufacturing system may be provided.

[0230] The above system is,

[0231] A cell tracking controller configured to collect cell IDs, which are identification information of battery cells; and

[0232] It includes an equipment controller configured to collect equipment data from equipment of a battery cell manufacturing process, and

[0233] The cell tracking controller above may be configured to map facility data corresponding to the cell ID to the cell ID.

[0234] The above equipment controller includes an equipment data address where equipment data is temporarily stored, and a cell tracking dedicated address.

[0235] The above equipment controller may be configured to extract equipment data from the equipment data to be transmitted to the cell tracking controller, collect it into the cell tracking dedicated address, and transmit the collected data to the cell tracking controller.

[0236] The above system may further include a T-branching module that branches the equipment data into equipment control data and monitoring data.

[0237] The above T branch module can transmit the monitoring data directly to the cell tracking controller without passing through the facility controller.

[0238] According to one aspect of the present disclosure, a battery manufacturing system may be provided.

[0239] The above system is,

[0240] A cell tracking controller configured to collect cell IDs, which are identification information of battery cells; and

[0241] The battery cell manufacturing process equipment includes at least one sensor for sensing equipment data, and

[0242] The cell tracking controller above may be configured to map the facility data to the cell ID.

[0243] The above cell tracking controller is,

[0244] Mapped data can be transmitted to at least one upper server, and the data collection, data mapping, and data transmission can be configured to be performed in real time.

[0245] The above system may further include at least one upper server that performs at least one of the following operations.

[0246] 1) Generation of monitoring data based on mapped data

[0247] 2) At least one of anomaly detection and anomaly alarm generation based on mapped data

[0248] 3) Generation of correction values ​​for battery cell manufacturing process-related parameters based on mapped data

[0249] According to one aspect of the present disclosure, a method for manufacturing a battery may be provided.

[0250] The above manufacturing method is,

[0251] A step of collecting a cell ID, which is identification information of a battery cell;

[0252] A step of collecting equipment data from a battery cell manufacturing process facility or an equipment controller that controls said facility; and

[0253] It includes the step of mapping equipment data corresponding to the collected cell ID to the cell ID, and

[0254] The above data collection and data mapping can be characterized by being performed in real time.

[0255] The above manufacturing method may further include the step of transmitting mapped data to at least one upper server.

[0256] The above manufacturing method further includes a data conversion step of converting the mapped data into a form required by the upper server, and

[0257] The above data collection, data mapping, data conversion, and data transmission may be characterized by being performed in real time.

[0258] The above manufacturing method further includes the step of branching the equipment data into equipment control data and monitoring data, and

[0259] It may be characterized by mapping the branched monitoring data above to the cell ID above.

[0260]

[0261] According to one aspect of the present invention, a data hub device may be provided.

[0262] The above data hub device is,

[0263] As a data hub device for mapping data acquired from multiple battery cell manufacturing processes between processes,

[0264] A first data collection unit configured to collect a first data set including at least one of location data and cell ID of a battery cell of each process in real time from the start of each process;

[0265] A data hub device comprising a second data collection unit configured to collect a second data set by correcting at least one of the location data and cell ID of the battery cell in the first data set so as to correspond to at least one of the location data and cell ID of the battery cell completed in the previous process of each process when one battery cell is completed in each process.

[0266] The above real-time may be the time required for one battery cell to move from a first process position where one battery cell is located to a second process position, which is the location of the next battery cell preceding the one battery cell.

[0267] The first data set and the second data set may include at least one of inspection data, measurement data, and equipment data mapped to at least one of the location data and cell ID of the battery cell.

[0268] The above data hub device may further include a data storage unit in which a second data set of each process is stored.

[0269] The above second data collection unit is,

[0270] By comparing the second data set of the previous process of each of the above processes with the first data set of each process,

[0271] It can be configured to generate a second data set for each process.

[0272] The above second data collection unit is,

[0273] By correcting the first data set of each process by reflecting the difference between the battery cell manufacturing performance of the previous process of each process and the battery cell manufacturing performance of each process,

[0274] It can be configured to generate a second data set for each process.

[0275] The above-mentioned first data collection unit is,

[0276] At least one of the location data and cell ID of the battery cell of each process, and

[0277] It may be configured to generate the first data set by performing a real-time mapping of at least one of inspection data, measurement data, and equipment data corresponding to at least one of the above location data and cell ID.

[0278] By means of a controller provided in each process, at least one of the location data and cell ID of the battery cell in each process and at least one of the inspection data, measurement data, and equipment data corresponding to at least one of the location data and cell ID are mapped in real time, and

[0279] The first data collection unit may be configured to generate the first data set based on real-time mapping data transmitted from the controller.

[0280] The above controller is,

[0281] It is configured to collect coordinate data as location data, and

[0282] It may be a roll map controller configured to collect at least one of inspection data and measurement data mapped to the above coordinate data.

[0283] The above controller is,

[0284] It is configured to collect cell IDs, and

[0285] It may be a cell tracking controller configured to map at least one of inspection data, measurement data, and equipment data to the above cell ID.

[0286] As one aspect of the present invention, a method for manufacturing a battery may be provided.

[0287] The above manufacturing method is,

[0288] A battery manufacturing method for mapping data acquired from multiple battery cell manufacturing processes between processes,

[0289] A step of collecting a first data set including at least one of location data and cell ID of a battery cell of each process in real time from the start of each process;

[0290] When one battery cell is completed in each process, the method may include the step of collecting a second data set by correcting at least one of the location data and cell ID of the battery cell in the first data set so as to correspond to at least one of the location data and cell ID of the battery cell completed in the previous process of each process.

[0291] The step of collecting the second data set above is,

[0292] By comparing the second data set of the previous process of each of the above processes with the first data set of each process,

[0293] It may include a step of generating a second data set for each process.

[0294] The step of collecting the second data set above is,

[0295] By correcting the first data set of each process by reflecting the difference between the battery cell manufacturing performance of the previous process of each process and the battery cell manufacturing performance of each process,

[0296] It may include a step of generating a second data set for each process.

[0297] The step of collecting the first data set above is,

[0298] At least one of the location data and cell ID of the battery cell of each process, and

[0299] The method may further include a step of performing a real-time mapping of at least one of inspection data, measurement data, and equipment data corresponding to at least one of the above location data and cell ID.

[0300] As one aspect of the present invention, a battery manufacturing system is,

[0301] A plurality of controllers configured to collect at least one of location data and cell ID of a battery cell in a plurality of processes; and

[0302] A first data set including at least one of the location data and cell ID of the battery cell of each process is collected in real time from the start of each process, and

[0303] A data hub device may be included that is configured to collect a second data set by correcting at least one of the location data and cell ID of the battery cell in the first data set so that, when one battery cell is completed in each process, at least one of the location data and cell ID of the battery cell completed in the previous process of each process corresponds to the first data set.

[0304] The above controller is,

[0305] It is configured to collect coordinate data as location data, and

[0306] It may be a roll map controller configured to collect at least one of inspection data and measurement data mapped to the above coordinate data.

[0307] The above controller is,

[0308] It is configured to collect cell IDs, and

[0309] It may be a cell tracking controller configured to map at least one of inspection data, measurement data, and equipment data to the above cell ID.

[0310] The above system is,

[0311] It may include at least one additional parent server that performs at least one of the following actions.

[0312] 1) Generation of monitoring data based on at least one of the first and second data sets

[0313] 2) At least one of anomaly detection and anomaly alarm generation based on at least one of the first and second data sets

[0314] 3) Generation of correction values ​​for process progress conditions (Recipe Parameters) of the equipment controller based on at least one of the first and second data sets

[0315] The above system is,

[0316] From the above-mentioned upper server,

[0317] It may include a top-level server configured to receive at least one of the first and second data sets and / or analysis data based on at least one of the first and second data sets.

[0318] According to the present invention, a cell tracking controller can collect individual data or all data based on a cell ID and provide them to upper-level servers. Accordingly, each server can compare individual data based on the cell ID, thereby enabling organic data analysis between systems.

[0319] Furthermore, a cell tracking controller utilizing data tracking is introduced instead of an equipment controller, and a data tracking foundation is established within the said cell tracking controller. Accordingly, the load on the equipment controller can be reduced, and an environment can be created to provide real-time cell ID-based data. Additionally, by transmitting real-time mapped data (data integrated into cell IDs) from the cell tracking controller to the upper server, the upper server can easily achieve its respective objectives based on the real-time data.

[0320] The effects obtainable from the exemplary embodiments of the present invention are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art to which the exemplary embodiments of the present disclosure belong from the following description. That is, unintended effects resulting from the implementation of the exemplary embodiments of the present disclosure can also be derived by those skilled in the art from the exemplary embodiments of the present disclosure.

[0321] Figure 1 is a schematic diagram showing an example of a data processing process in a battery manufacturing process.

[0322] Figure 2 is a schematic diagram showing another example of a data processing process in a battery manufacturing process.

[0323] FIGS. 3 to 7 show examples of battery semi-finished products including an electrode sheet, an electrode, and an electrode.

[0324] Figure 8 is a schematic diagram showing an example of a battery manufacturing system.

[0325] Figure 9 is a schematic diagram of an example of a cell tracking controller.

[0326] Figure 10 is an example of binary data and string data.

[0327] Figure 11 is a schematic diagram showing an example of a battery manufacturing system.

[0328] Figure 12 is a schematic diagram of an example of a cell tracking controller.

[0329] Figure 13 is a schematic diagram showing an example of a battery manufacturing system.

[0330] Figure 14 is a schematic diagram of an example of a cell tracking controller.

[0331] Figure 15 is an example of a data set mapped using cell IDs as keys.

[0332] FIG. 16 is an example of a battery manufacturing system including a T-branch module.

[0333] Figure 17 shows an example of a collection path for equipment data.

[0334] FIG. 18 is a flowchart showing an example of a battery manufacturing method.

[0335] Figure 19 is a flowchart showing another example of a battery manufacturing method.

[0336] Figure 20 is an example of a battery manufacturing system.

[0337] Figure 21 is an example of a battery manufacturing method.

[0338] Figure 22 is an example of a battery manufacturing system.

[0339] Figure 23 is an example of a battery manufacturing system.

[0340] Figure 24 is a schematic diagram showing the process of collecting high-frequency data.

[0341] Figure 25 is a schematic diagram showing the conversion process of high-frequency data.

[0342] Figure 26 is an example of a battery manufacturing method.

[0343] Figure 27 is an example of a battery manufacturing system.

[0344] Figure 28 is an example of a battery manufacturing system.

[0345] FIG. 29 is an example of a battery manufacturing method.

[0346] Figure 30 is an example of a battery manufacturing system.

[0347] Figure 31 is an example of a battery manufacturing system.

[0348] Figure 32 is an example of a battery manufacturing system.

[0349] Figure 33 illustrates the first data set and the second data set.

[0350] Figure 34 is a flowchart showing a battery manufacturing method.

[0351] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. Prior to this, terms and words used in this specification and claims should not be interpreted as being limited to their ordinary or dictionary meanings. Instead, based on the principle that the inventor can appropriately define the concepts of terms to best describe his invention, they should be interpreted in a meaning and concept consistent with the technical spirit of the present invention.

[0352] Therefore, the embodiments described in this specification and the configurations illustrated in the drawings are merely the most preferred embodiments of the present invention and do not represent all of the technical ideas of the present invention; thus, it should be understood that various equivalents and modifications that can replace them may exist at the time of filing this application.

[0353] In addition, in describing the present invention, if it is determined that a detailed description of related known components or functions may obscure the essence of the invention, such detailed description is omitted.

[0354] Since embodiments of the present invention are provided to more fully explain the invention to those skilled in the art, the shapes and sizes of the components in the drawings may be exaggerated, omitted, or schematically depicted for clearer explanation. Accordingly, the size or proportion of each component does not entirely reflect the actual size or proportion.

[0355]

[0356] Figure 1 is a schematic diagram showing an example of a data processing process in a battery manufacturing process.

[0357] As illustrated in Fig. 1, data in the manufacturing process of a battery cell can go through the stages of generation, collection, processing, and analysis. The collected data regarding the battery cell can be mapped to a cell ID (#1) and finally analyzed on an integrated server such as a data warehouse.

[0358] In the data generation stage, equipment data may be generated in an equipment controller (e.g., an equipment PLC) that performs process control and equipment control. Additionally, inspection and measurement may be performed on battery cells in the battery manufacturing process, and inspection data and measurement data may be generated in the inspection device and the measurement device, respectively.

[0359] Referring to Fig. 1, for example, equipment data X1 of equipment 1 is generated in the equipment PLC, and inspection data y1 and z1 are generated in inspection device 1 and inspection device 2, respectively. Measurement data is not generated in measuring device 1, and omission occurs.

[0360] The generated data can be collected by each data collection server (SPC server, eIoT server, etc.) determined in the data flow.

[0361] Data collected from servers can be processed and analyzed on a top-level server, such as a data warehouse (DW). In the data warehouse (DW), the cell ID (#1) of the battery cell is mapped to each data point to identify process anomalies or missing data.

[0362] Therefore, in a data processing process like that of Fig. 1, it is not possible to detect anomalies or take measures to resolve them until the data is loaded into the data warehouse (DW), so the anomalies cannot be resolved early.

[0363] Furthermore, even if the cause of the data loss is identified and corrective measures are taken on the final server, data from the time the problem occurred until the corrective action is taken cannot be restored. This is because data may be lost if a response is not provided within the minimum processing time (scan time) required for data generation due to limitations in data processing algorithms or communication delays related to information processing time.

[0364] In a data processing process or data processing system as shown in Fig. 1, the data generating device (equipment PLC, inspection device, measuring instrument) and the data collection server each only focused on transmitting data, and since the structure made data analysis difficult, it was not possible to detect data omissions or data delays.

[0365]

[0366] FIG. 2 is a schematic diagram showing another example of a data processing process in a battery manufacturing process. FIG. 2 is intended to explain the concept of the invention according to the present disclosure.

[0367] In Figure 2, the data processing process is significantly simplified to data generation and data collection in order to detect data omissions, data delays, etc., in real time and generate an alarm. To this end, a separate device for data collection and mapping of cell IDs with collected data, namely a cell tracking controller (CTC), may be introduced.

[0368] As in Fig. 1, during the data generation step, equipment data X1 is generated in the equipment PLC, and inspection data y1 and z1 can be generated in Inspector 1 and Inspector 2, respectively. Measurement data was not generated in Measurement Instrument 1, and omission occurred.

[0369] The generated data is transmitted to the Cell Tracking Controller (CTC) before being collected by each data collection server (SPC or eIoT, etc.). The collected data can be mapped to the cell ID of the battery cell at the Cell Tracking Controller (CTC).

[0370] Accordingly, the Cell Tracking Controller (CTC) can immediately identify any missing measurement data for the corresponding cell ID. In other words, data omissions or delays can be identified during the data collection phase.

[0371] Therefore, the disadvantages of the data processing process as shown in Fig. 1 can be resolved.

[0372] The Cell Trace Controller (CTC) can map collected data using a cell ID, which identifies the battery cell being manufactured, as a key, thereby enabling the rapid identification of missing data or abnormal conditions. Additionally, the mapped data can be transmitted to multiple subsystems (servers) to promptly take corrective action regarding the anomalies. Consequently, the time required for data recovery to become impossible can also be reduced.

[0373] In practice, compared to the time taken to upload data to the data warehouse (DW), retrieve the data, and perform root cause analysis and action, the time taken to collect data and perform root cause analysis and action at the cell tracing controller (CTC) can be reduced significantly by more than half.

[0374] In addition, by introducing a Cell Tracking Controller (CTC) in each of the multiple battery manufacturing processes, a standardized data set mapped based on a standard key, the cell ID, can be provided.

[0375] Multiple subsystems receive standardized data sets from each Cell Tracking Controller (CTC) and can process the data according to common criteria (e.g., cell ID). Accordingly, organic data linkage and analysis can be performed between each battery manufacturing process and / or between each subsystem.

[0376] Furthermore, by introducing a dedicated controller for data tracking or battery cell tracking instead of the equipment controller, the load placed on the equipment controller or subsystem can be relieved. Accordingly, a real-time data collection environment can be provided that enables real-time cell ID collection, data collection, mapping, and transmission.

[0377] The cell ID can be a physical ID actually assigned to the battery cell.

[0378] The cell ID may be a virtual cell ID virtually assigned to a battery cell. In other words, the virtual cell ID is an identification mark virtually assigned to each corresponding battery cell.

[0379] A cell ID (CID) or virtual cell ID (VID) may include a symbol indicating the sequence number of a battery cell. The symbol may include Arabic numerals, but is not limited thereto. A cell ID (CID) or virtual cell ID (VID) may include any character capable of providing information regarding the sequence number of electrode tabs (TN). A physical cell ID may include a barcode or a QR code, but is not limited thereto.

[0380] FIG. 3 illustrates the movement of an electrode sheet (ES) unwound from an electrode roll (ER) in the electrode process of a roll-to-roll process. The electrode sheet (ES) can be cut to a predetermined size in a subsequent process (e.g., a notching or lamination process) to form an electrode. The dotted line in FIG. 3 represents a virtual line that is cut into an electrode. Accordingly, a virtual cell ID (VID) can be assigned to each portion of the electrode sheet scheduled for cutting as a future electrode. The portion of the electrode sheet (battery cell) to which the virtual cell ID (VID) is assigned can be distinguished from other battery cells by their respective virtual cell IDs (VIDs).

[0381] FIG. 4 discloses the movement of an electrode sheet (ES) unwound from an electrode roll (ER) during a notching process of a roll-to-roll process. The notching process may be performed on the electrode sheet (ES) unwound from the electrode roll (ER) by a rewinder. During the notching process, an electrode tab (ETN) may be formed on the electrode slurry non-coated portion of the electrode sheet (ES). During the notching process, a V-shaped groove may be formed on the electrode sheet (ES). A cell ID (CID) may be formed on the electrode tab (ETN). The electrode sheet (ES) with the cell ID (CID) formed thereon may be a negative electrode sheet, but is not limited thereto. The electrode sheet (ES) may also include an anode sheet.

[0382] The cell ID (CID) can be formed by methods such as laser printing and ink printing, but is not limited to these methods.

[0383] As shown in FIG. 4, before the electrode tab (ETN) is formed, a virtual cell ID (VID) may be assigned to identify the planned electrode portion. In this way, the virtual cell ID (VID) may be assigned to a battery cell including an electrode sheet or electrode, etc., before the actual cell ID (physical cell ID) is assigned. The virtual cell ID (VID) may be matched to the actual cell ID (CID) after the actual cell ID is generated. After the notching process, the electrode sheet (ES) may be individualized into unit electrodes including the electrode tab (ETN).

[0384] Referring to FIGS. 5 and 6, in the lamination process, individualized unit electrodes can be bonded to a separator. In the lamination process, to enhance the bonding strength between the separator and the unit electrode, the separator and the unit electrode may be heat-treated. A half cell (HC) or a mono cell (MC) may be provided by the lamination process. A bi-cell, etc., may also be provided by the lamination process. The half cell (HC) may include a separator and an anode, or a separator and a cathode. The half cell (HC) may include an electrode tab (ETN) including a cell ID (CID). The mono cell (MC) may include an anode, a first separator, a cathode, and a second separator stacked in order. The mono cell (MC) may include an electrode tab (ETN) including a cell ID (CID) and an electrode tab (ETP) having opposite polarity to the electrode tab (ETN).

[0385] Unlike in Fig. 6, the cell ID (CID) may be formed on each of the electrode tabs (ETP, ETN) or may be formed only on the electrode tab (ETP).

[0386] Referring to FIGS. 5 to 7, in the stacking process, a half cell (HC), a mono cell (MC), and

[0387] At least one of the bi-cells can be repeatedly stacked. An electrode assembly (EA) (so-called stack cell) can be provided by a stacking process. The electrode assembly (EA) may include a tape (TF) for securing the positive and negative electrodes. The electrode assembly (EA) may include an electrode tab (ETN) containing a cell ID (CID) and an electrode tab (ETP) of opposite polarity to the electrode tab (ETN). Unlike in FIG. 7, the cell ID (CID) may be formed on each of the electrode tabs (ETP, ETN) or may be formed only on the electrode tab (ETP).

[0388] In the folding process, half cells, mono cells, and bi cells can be wound by a separator. The packaging process may include inserting an electrode assembly into a case, injecting an electrolyte, and then sealing the case. A cell that has undergone the packaging process may be referred to as a packaged cell.

[0389] The battery semi-finished products of the above half-cell, monocell, bicell, electrode assembly, and packaging cell can all be identified by a cell ID (CID), so they can be referred to as a battery cell (BC).

[0390] In addition, a finished battery product (finished battery cell, battery module, battery pack) including the above electrode also includes a cell ID (CID), and since it can be identified by the cell ID, it can be included in the battery cell (BC).

[0391]

[0392] FIG. 8 is a schematic diagram showing an example of a battery manufacturing system, and FIG. 9 is a schematic diagram of an example of a cell tracking controller.

[0393] A battery manufacturing system (10) according to an exemplary embodiment may include a battery cell manufacturing process facility (EQ), a cell tracking controller (100), a facility controller (200), an inspector (300), and a measuring instrument (400).

[0394] The battery cell manufacturing process may refer to a process for manufacturing each battery cell, such as an electrode sheet, an electrode, a battery semi-finished product including an electrode, or a battery finished product including an electrode. For example, the battery cell manufacturing process may be each detailed process of the electrode process, such as a coating process, a roll press process, or a slitting process. The battery cell manufacturing process may be each detailed process of the assembly process, such as a notching process, a lamination process, a lamination and folding process, or a lamination and stacking process, or a winding process. The battery cell manufacturing process may be a packaging process, an activation process, a modularization process, a pack process, or a detailed process of each of these processes.

[0395] The battery cell manufacturing process equipment (EQ) may include a plurality of devices for performing each process. The equipment (EQ) may include a transfer device (TD) for transferring a battery cell (BC), a processing mechanism, and at least one equipment sensor.

[0396] The transfer device (TD) may be configured to transfer electrode sheets, electrodes, battery semi-finished products, or battery finished products. The transfer device (TD) may be a Linear Motion System (LMS). The transfer device (TD) may include a conveyor device or a roll-to-roll transfer device. The transfer device (TD) may include a driving device, such as a motor, for moving a battery cell (BC).

[0397] For example, a roll-to-roll transfer device may include an unwinder for unwinding an electrode roll, a rewinder for winding an electrode roll, and a motor for driving the unwinder and the rewinder.

[0398] The processing mechanism may be configured to process battery cells (BC). Battery cell manufacturing process equipment may be configured to perform different processes.

[0399] For example, in a coating process, the processing mechanism may include a coater that coats an electrode slurry onto an electrode sheet, a dryer that dries the electrode sheet, and a half-slitter that half-slits the electrode sheet.

[0400] In the roll press process, the processing mechanism may include a press roll that rolls the electrode sheet.

[0401] In the slitting process, the processing mechanism may include a slitter that slits the electrode sheet into a plurality of electrode lanes.

[0402] In the notching process, the processing mechanism may include a puncher that forms an electrode tab.

[0403] In the lamination process, the processing mechanism may include a cutter for cutting electrode tabs and a combiner for combining the cut electrodes.

[0404] In this way, there may be one or more processing mechanisms in each process.

[0405] Equipment sensors may refer to sensors installed at a transfer device (TD), processing mechanism, or other device or location to acquire data related to equipment (EQ), namely equipment data (ED).

[0406] Equipment data (ED) may include Process Value and Set Value. Process Value may be a quantity / value currently changing in the process. Set Value may be a value that has been set (target value).

[0407] Parameters that can have a significant impact on the process (CTP: Critical To Parameter) can also be included in the equipment data (ED).

[0408] Specifically, temperature, pressure, flow rate, etc., can be included in the equipment data (ED).

[0409] For example, in a coating process, the RPM of a pump connected to a coater, the temperature of the electrode slurry discharged from the coater, and the Die Gap, which is the distance between the coater and the electrode sheet, are also examples of equipment data (ED).

[0410] These facility data (ED) can be sensed by corresponding facility sensors (e.g., temperature sensors, distance measuring sensors, RPM sensors, etc.).

[0411] The equipment controller (200) may be configured to control the operation of the equipment. Since the process can be controlled by controlling the equipment (EQ), the equipment controller (200) is also referred to as a process controller. The equipment controller (200) may be an equipment PLC (Programmable Logic Controller). A PLC is a microprocessor-based controller that uses programmable memory to store commands and controls machines and processes by implementing functions such as logic, sequencing, timing, counting, and arithmetic. The PLC is easy to operate and program.

[0412] The equipment controller (200) can control a transfer device (TD), a processing mechanism, etc. The equipment controller (200) may be configured to generate signals for the operation and cessation of multiple equipment units, such as a transfer device (TD) and a processing mechanism, included in the equipment. The signals for the operation and cessation of multiple equipment units may be generated based on a body containing details of a manufacturing recipe.

[0413] The equipment controller (200) may be configured to collect equipment data (ED) from the equipment (EQ) of the battery cell manufacturing process. The equipment controller (200) may perform in operative communication with each equipment unit and each equipment sensor through a wired or wireless data network.

[0414] Equipment data (ED) acquired from each equipment sensor can be transmitted to the equipment controller (200). For example, a data storage such as a memory provided in the equipment controller (200) may have a location, i.e., an address, where the equipment data (ED) acquired by each sensor is stored. The equipment data (ED) acquired by each sensor can be stored at the address continuously or at predetermined time intervals.

[0415] The battery manufacturing system (10) may include a position measuring device (410) for measuring the position of a battery cell (BC) moving during the process.

[0416] The above position measuring device (410) can obtain position data of each battery cell (BC) by measuring the position value (PV: Position Value) of the battery cell (BC) moving during the process.

[0417] The above position data may be position data indicating the position of a battery cell (BC) that is part of an electrode sheet (ES) that moves during the process. Alternatively, it may be position data during the process of a battery cell (BC) that is an electrode cut to a predetermined standard size by the electrode sheet. Alternatively, it may be position data during the process of a battery cell that is a battery semi-finished product including the electrode, or a battery cell that is a battery finished product including the electrode. The above position data may be expressed in coordinates. In this case, the position data may be coordinate data. The above position data may be expressed in a manner other than coordinates. For example, it may be indicated as a displacement amount that moves during the process. However, the method of expressing the position of the battery cell in the present disclosure is not limited thereto, and it is possible to express it in other ways as long as the position of the battery cell during the process can be appropriately expressed.

[0418] For example, the position measuring device (410) may be a rotary encoder installed in an unwinder or rewinder that moves the electrode sheet in a roll-to-roll process. The rotary encoder can sense the unwinding amount signal or winding amount signal of the electrode sheet and indicate the position value (PV: Position Value) of each moving part of the electrode sheet. The unwinding amount signal and winding amount signal are transmitted to an equipment controller (200), an inspector (300), a measuring instrument (400), or a cell tracking controller (100) described later, and coordinate data (CD), which is the position of each moving battery cell (BC) (in this case, a part of the electrode sheet or a unit electrode), can be collected by the equipment controller (200), etc.

[0419] The above position measuring device (410) may be another position measuring sensor (e.g., a displacement amount sensing sensor, etc.) capable of detecting the movement of a battery cell (BC) in an LMS or conveyor device. Position values ​​in each process can also be obtained by the displacement amount sensing sensor, and based on these position values, the equipment controller (200), inspection device (300), measuring device (400), or cell tracking controller (100) of each process can collect position data.

[0420] The battery manufacturing system (10) may also include a cell recognition device (430) capable of recognizing a battery cell (BC) moving during the process, a cell ID recognition device (420) capable of recognizing a cell ID, or a cell ID marking device (421) capable of marking a cell ID.

[0421] The cell recognizer (430) may be configured to detect a battery cell (BC) and generate a cell detection signal (CDS). The cell recognizer (430) may be a vision camera, but is not limited thereto.

[0422] The cell ID recognizer (420) can detect the cell ID displayed on the battery cell (BC) and generate an ID recognition signal (IDS). The cell ID recognizer may be a barcode reader (BCR), but is not limited to this.

[0423] The cell detection signal (CDS) or cell ID recognition signal (IDS) can be transmitted to at least one of the facility controller (200) and the cell tracking controller (100).

[0424] The equipment controller (200) can control the equipment to perform a predetermined process on a corresponding battery cell (BC) based on a cell detection signal (CDS) or a cell ID recognition signal (IDS).

[0425] The cell tracking controller (100) can acquire the cell ID (CID) of each battery cell (BC) moving in the process based on the cell ID recognition signal (IDS).

[0426] The cell tracking controller (100) can assign a virtual cell ID (VID) to each battery cell (BC) moving in the process based on a cell recognition signal (CDS) as described below.

[0427] A cell ID marking machine (421) may be provided in a battery manufacturing system. The cell ID marking machine (421) may assign a cell ID to a battery cell (BC) at a predetermined interval, for example, every pitch. The cell ID may be assigned based on electrode specification information and position information. For example, the cell ID marking machine (421) may assign a cell ID to a battery cell (BC) at a coordinate position acquired by a position measuring device (410) (e.g., a rotary encoder), corresponding to a predetermined interval detected by an electrode spacing sensor or a tap sensor. The cell ID marking machine (421) may be an ink marking machine or a laser marking machine, but is not limited thereto.

[0428] The inspection device (300) may be configured to inspect a battery cell (BC) and collect inspection data (ID). The inspection data (ID) may include a judgment on the quality of the battery cell (BC) and process events. For example, the inspection data (ID) may include data on the appearance of the battery cell (BC) collected by an image-based inspection device such as a vision machine, data on the breakage and seams of the electrode sheet material (SM) that is the battery cell (BC), data on the part of the sheet material (SM) where sampling inspection was performed, data on the part of the sheet material (SM) scheduled for scrapping, data on the scrapped part of the sheet material (SM), data on the quality of the coating material and insulating material on the sheet material (SM), data on reference points indicating the location of the sheet material (SM), and defect data such as pinhole defects, crater defects, line defects, crack defects, side ring defects, island defects, folding defects, wrinkle defects, gouging defects, and dents. Reference points may be formed at predetermined intervals on the sheet material (SM), and the locations of other elements on the sheet material (SM) may be known based on the reference points. The inspection device (300) may be any one of a color sensor, a seam sensor, a reference point sensor, and a vision machine.

[0429] The measuring instrument (400) can be configured to collect measurement data (MD) of the battery cell (BC). The measuring instrument (400) can measure the battery cell (BC) by scanning.

[0430] Measurement data (MD) may include measurement results expressed in numerical form. For example, the measurement data (MD) may include dimensional data of a battery cell (BC), such as thickness and width; data on the loading amount of a coating material on a sheet material; dimensional data such as the width of an insulating material provided on the coating material and the overlap width between the coating material and the insulating material. By processing the measurement data (MD) according to a set method, the quality of the measured portion of the battery cell (BC) can be determined.

[0431] The measuring instrument (400) may be, for example, any one of the web gauge and thickness measuring instrument of Thermofisher Scientific, but is not limited thereto.

[0432] The inspection device (300) and the measuring device (400) may include a sensing unit and a processing unit (e.g., an inspection PC or a measuring PC). The sensing unit may be configured to detect physical quantities of a battery cell (BC) to generate an inspection signal (IS) or a measurement signal (MS). For example, the sensing unit may include a TDI (Time Delay and Integration) camera, a CMOS (Complementary Metal Oxide Semiconductor) image sensor, and a TOF (Time of Flight) sensor.

[0433] The processing unit may be configured to collect inspection signals (IS) or measurement signals (MS) sensed by the sensing unit to generate inspection data (ID) or measurement data (MD). The processing unit may be connected to the sensing unit via a wired or wireless connection.

[0434] As described above, based on the position value obtained from the position measuring device (410), the inspection device (300) and measuring device (400) of each process can collect position data (e.g., coordinate data) of each battery cell (BC).

[0435] A cell tracking controller (100) may be configured to collect a cell ID (CID), which is identification information of a battery cell (BC). The cell tracking controller (100) may be configured to map at least one of inspection data (ID), measurement data (MD), and equipment data (ED) corresponding to the cell ID (CID) to the cell ID (CID).

[0436]

[0437] Referring to FIG. 9, the cell tracking controller (100) may include a cell ID collection unit (110), a data collection unit (120), and a cell ID mapping unit (130).

[0438] The cell tracking controller (100) may be a PLC (Programmable Logic Controller). The cell tracking controller (100) may include a power supply, a CPU, an input interface, an output interface, a communication interface (TIF), and memory devices. The power supply may be configured to supply power to other elements of the controller, such as the CPU, input interface, output interface, communication interface (TIF), and memory devices, for the operation of the cell tracking controller (100). The memory devices may include ROM (Read Only Memory) configured to store system programs, such as an operating system, and RAM (Random Access Memory) configured to store data, such as user programs, status information of input and output devices, timers, counters, and values ​​of other internal devices. The CPU may be configured to control communication between modules that implement logic and convert input signals into output operation signals. The CPU may operate based on system programs and user programs stored in the memory devices. The CPU may be configured to write or read inspection data and measurement data to the data areas of the memory devices based on system programs and user programs. Conditions or data of industrial devices and production processes can be transmitted to the CPU through the input module. The results processed by the CPU can be transmitted to the actuator through the output module. The communication interface (TIF) can be configured to relay the transmission and reception of data between the cell tracking controller (100) and the inspection device (300), measuring instrument (400), equipment controller (200), etc.

[0439] The cell tracking controller (100) may include any one of a simple controller, a complex processor such as a microprocessor, CPU, GPU, etc., a processor configured by software, dedicated hardware, and firmware.

[0440] A cell tracking controller (100), such as a main control unit (CPU: Central Processing Unit) of a cell tracking controller, may be equipped with a cell ID collection unit (110), a data collection unit (120), and a cell ID mapping unit (130). The CPU, which is the main control unit, may include a control unit (CU), an arithmetic and logical unit (ALU), registers, and an internal bus connecting each component so as to perform the functions of each component.

[0441] The cell tracking controller (100) may further include a data conversion unit (140) that converts collected data into a form required by the upper server (500). The cell tracking controller (100) may be equipped with a communication interface (TIF) for transmitting and receiving data. For example, the cell tracking controller (100) may include an Ethernet communication interface (TIF) based on an Ethernet protocol that performs data transmission and reception through a LAN (local area network).

[0442] The cell ID collection unit (110) can be configured to collect the cell ID (CID), which is identification information of the battery cell (BC).

[0443] Referring to FIGS. 4 through 8, a cell ID recognizer (420) (e.g., BCR) may be configured to detect a barcode (e.g., data matrix) provided on a battery cell (BC) to generate a cell ID detection signal (IDS). The cell ID detection signal (IDS) generated based on the reading of the barcode may be transmitted to a cell tracking controller (100).

[0444] The cell ID collection unit (110) may include a cell ID detection unit (111) that detects a cell ID (CID) collected in a communication interface (TIF) and a cell ID tracking unit (112) that tracks the cell ID.

[0445] The cell ID detection unit (111) can sequentially detect cell IDs (CIDs) received from the cell ID recognizer (420).

[0446] The cell ID tracking unit (112) can track a moving battery cell as the battery cell manufacturing process progresses. A position measuring device (410) (e.g., a rotary encoder or a displacement sensor) may be provided to detect the position of the moving battery cell (BC). The cell ID tracking unit (112) can identify the cell ID (CID) of the moving battery cell (BC) based on the position value transmitted from the position measuring device (410). As described above, the position of the moving battery cell (BC) during the process is reported to the equipment controller (200), and the equipment controller (200) can perform a predetermined process on the battery cell (BC) based on this. Likewise, the position of the moving battery cell (BC) during the process is reported to the cell tracking controller (100), and the cell tracking controller (100) can detect and track the cell ID (CID) of the battery cell (BC) based on this.

[0447] The position measuring device (410) can transmit the position value of the battery cell (BC) during the process to the cell tracking controller (100). Based on this, the cell tracking controller (100) can collect position data (e.g., coordinate data) of the battery cell (BC). The cell tracking controller (100) can collect the cell ID (CID) and the position data of the battery cell (BC) corresponding to the cell ID (CID), and match the cell ID (CID) corresponding to a specific battery cell (BC) with the coordinate data.

[0448] The cell ID collection unit (110) can collect the cell ID (CID) of a battery cell (BC) moving in the battery cell manufacturing process and transmit it to the cell ID mapping unit (130). Specifically, the cell ID tracking unit (112) can track the cell ID (CID) of the battery cell (BC) moving according to the progress of the process for the battery cell (BC) and report it to the cell ID mapping unit (130).

[0449] The data collection unit (120) can collect at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) of the battery cell (BC).

[0450] Referring to FIGS. 4 to 8, at least one inspection device (300) or measuring device (400) may be provided during the process. The inspection device (300) may sense an inspection signal (IS) in a sensing unit and process the inspection signal (IS) by a predetermined inspection algorithm in a processing unit (e.g., an inspection PC) to generate inspection data (ID). The inspection data (ID) may be transmitted to a cell tracking controller (100).

[0451] The measuring instrument (400) can sense a measurement signal (MS) in a sensing unit and process the measurement signal (MS) by a predetermined algorithm in a processing unit (e.g., a measuring instrument PC) to generate measurement data (MD). The measurement data (MD) can be transmitted to a cell tracking controller (100).

[0452] Referring to FIGS. 4 through 8, equipment data (ED) generated in the process equipment (EQ) can be transmitted to an equipment controller (200) (e.g., an equipment PLC). The equipment data (ED) can be transmitted from the equipment controller (200) to a cell tracking controller (100). In some cases, the equipment data (ED) can be transmitted directly from the equipment to the cell tracking controller (100) without passing through the equipment controller (200).

[0453] A data collection unit (120) provided in a cell tracking controller (100) can collect at least one of inspection data (ID), measurement data, and equipment data (ED) through a communication interface (TIF). The data collection unit (120) may include an inspection / measurement data collection unit (121) that collects at least one of inspection data (ID) and measurement data, and an equipment data (ED) collection unit (122).

[0454] The data collection unit (120) can transmit at least one of the collected inspection data (ID), measurement data (ED), and equipment data (ED) to the cell ID mapping unit (130).

[0455] The cell ID mapping unit (130) may be configured to map at least one of the collected inspection data (ID), measurement data (ED), and equipment data (ED) to the cell ID (CID).

[0456] Referring to FIGS. 8 and 9, the cell ID mapping unit (130) can receive the cell ID (CID) of a battery cell (BC) from the cell ID collection unit (110). The cell ID mapping unit (130) can receive at least one of inspection data (ID), measurement data (MD), and equipment data (ED) from the data collection unit (120).

[0457] Mapping is a general term for the process of associating one value with another. In the field of programming, mapping refers to connecting data that acts as a key with data that acts as a value. The key is used to distinguish stored data, while the value refers to the data stored in connection with that key.

[0458] Meanwhile, in the present disclosure, matching refers to the process of finding a match among two or more elements. For example, an example can be given in the case of matching a Cell ID (CID) with a corresponding Virtual Cell ID (VID).

[0459] In other words, mapping is connecting two or more elements or defining relationships, while matching can be described as finding a match among two or more elements.

[0460] For example, the cell ID mapping unit (130) can map at least one of the cell ID (CID) collected at the same time based on time and the corresponding inspection data (ID), measurement data (MD), and equipment data (ED). However, if based on time, data collected at different locations at the same time may be mapped, which has the disadvantage of reduced data consistency. Therefore, it may be preferable to map at least one of the cell ID (CID) collected at the same location and the corresponding inspection data (ID), measurement data (MD), and equipment data (ED) based on location values. The cell ID collection unit (110) can detect the cell ID (CID) and track the cell ID (CID) based on the location value (coordinate value) of each battery cell (BC) by linking with the location measuring device (410). Similarly, each inspection device (300) and measuring device (400) can also acquire inspection data (ID) or measurement data (MD) based on the location value of each battery cell (BC) by linking with the location measuring device (410). Therefore, in a system like Fig. 8, the cell ID (CID), inspection data (ID), and measurement data (MD) can be mapped based on the same location data. Additionally, the equipment controller (200) also receives a location value (PV) from the location measuring device (410). Thus, the location value can also be mapped to the equipment data (ED) acquired by the equipment units included in the equipment (EQ) and the equipment sensors installed in each unit.

[0461] In this regard, in the present disclosure, inspection data (ID), measurement data (MD), and equipment data (ED) corresponding to the cell ID (CID) may refer to the cell ID (CID), inspection data (ID), measurement data (MD), and equipment data (ED) acquired for the same battery cell (BC) in the process.

[0462] As disclosed in FIG. 9, the cell ID mapping unit (130) can map collected data corresponding to the cell ID (CID) using the cell ID (CID) as a key.

[0463] The cell ID mapping unit (130) can store the mapped data in a predetermined memory device.

[0464] The above cell ID collection, data collection, and data mapping can be performed in real time.

[0465] In the present disclosure, a controller (100) dedicated to data tracking, i.e., dedicated to cell ID tracking, is provided separately from the equipment controller (200) (process controller). According to the present disclosure, since the equipment controller (200) does not perform cell tracking functions and controls only the process equipment, almost no load for data tracking is applied to the equipment controller (200). Therefore, problems such as delays in the operation of the equipment controller (200) or operational errors can be prevented.

[0466] In addition, since a separate controller dedicated to cell ID tracking, namely the cell tracking controller (100), is responsible for tracking battery cell data, data processing such as data transmission and reception and mapping can be performed quickly. For example, compared to the case where process equipment control and data tracking are performed simultaneously in the equipment controller (200), it is obvious that the data processing speed is much faster because the cell tracking controller (100) of the present disclosure performs only data tracking.

[0467] Therefore, the cell tracking controller (100) (e.g., cell tracking PLC) can perform cell ID collection, data collection, and data mapping in real time simply by applying a standard CPU, memory device, and interfaces.

[0468] Additionally, the cell tracking controller (100) may be configured to transmit mapped data to at least one upper server (500). The cell ID collection, data collection, data mapping, and data transmission may also be performed in real time.

[0469]

[0470] The cell tracking controller (100) may further include a data conversion unit (140) that converts collected data into a form required by the upper server (500).

[0471] The data conversion unit (140) may be configured as a separate module from the CPU, i.e., a data conversion module. In order to reduce the resources or time required to convert data, the data conversion unit (140) may be configured as a separate data conversion module and included in the cell tracking controller (100).

[0472] As illustrated in FIG. 10, data is typically displayed in the form of binary numbers (0 and 1) in controllers such as PLCs. Additionally, each subsystem (server), such as an FDC or MES, connects to the PLC to scan and retrieve the binary data. Each subsystem can convert the binary data into character data, specifically string data (text data). In this disclosure, a subsystem can be defined as an individual system for performing specific purposes or functions required for battery manufacturing, such as production management, anomaly detection, system correction, and recipe management. The subsystem may include a computing system for performing each function. Each subsystem may be a higher-level server for performing each function, or a device that includes a higher-level server. On the other hand, in this disclosure, an upstream server that receives data from the subsystem (higher-level server) may be referred to as an integrated system (integrated server or top-level server). The integrated system may be, for example, a data warehouse and may store the received data for a long period based on the product's warranty period, etc.

[0473] However, since the naming rule differs for each subsystem, even the same data may be displayed under different names, as shown in Fig. 10.

[0474] If this happens, identical data introduced into each subsystem may be regarded as different data, making comparative analysis of data between subsystems difficult. Furthermore, from the user's perspective, identical data may be judged as different data, potentially causing confusion in process execution.

[0475] Therefore, it is necessary to provide the same data item name to each subsystem by converting the data in the cell tracking controller (100) rather than converting the binary data into string data in the subsystem.

[0476] In this embodiment, the data conversion unit (140) of the cell tracking controller (100) converts binary data into string data in a form required by the subsystem.

[0477] Generally, the primary role of a PLC's CPU is not data conversion. Therefore, when data is converted by the CPU, the conversion time may be long (e.g., more than 2 seconds), making real-time data processing difficult.

[0478] In this embodiment, real-time data processing can be facilitated by adding (developing) a separate data conversion module to the CPU of the cell tracking controller (100). Binary-to-string data conversion can be performed by conversion software written in a specific programming language such as Python, or by hardware including said conversion software.

[0479] By the above data conversion module, cell ID collection, data collection, data mapping, data conversion, and data transmission in the cell tracking controller (100) can be performed in real time.

[0480] In the present disclosure, "real-time" may refer to the time required for a single battery cell to move from a first process location where the single battery cell is located to a second process location, which is the location of the next battery cell preceding the single battery cell. That is, it may refer to the tact time for moving (producing) one battery cell (BC) in each process. "Process location" may refer to the location of each battery cell in the process. For example, in the lamination process, the time for moving (producing) one mono cell is approximately 0.25 seconds. Alternatively, the time required for moving a battery cell (BC) may differ in other battery cell manufacturing processes. Importantly, cell ID collection, data collection, data mapping, data conversion, and data transmission can be performed within the short time (real-time) during which each battery cell (BC) moves in each battery cell manufacturing process.

[0481] That is, in the present disclosure, data collection and mapping are performed in a separate cell tracking controller (100) from the facility controller (200) to reduce communication and data processing resources and increase the data processing speed, and a module dedicated to data conversion is provided so that data conversion can also be performed quickly.

[0482] Accordingly, all data processing in the cell tracking controller (100) can be performed in real time. Therefore, a real-time data processing environment can be provided to the battery cell manufacturing process and manufacturing system.

[0483] Referring again to Fig. 9, a more detailed flow regarding data mapping and data transformation is explained.

[0484] In the cell ID mapping unit (130), binary data mapped to a cell ID (CID) as a key can be stored in memory. Data preprocessing for string conversion can be performed on the stored mapping data.

[0485] Data preprocessing refers to the process of transforming collected data into a suitable form. Through data preprocessing, the quality of data can be improved by removing unnecessary data and handling missing values ​​or outliers. Various commonly known data preprocessing techniques (handling missing values, handling outliers, data normalization, data encoding, data integration, data partitioning, data alignment, data pivoting, data sampling, etc.) can be performed for data preprocessing.

[0486] After data preprocessing, a string conversion request can be transmitted from the cell ID mapping unit (130) to the data conversion unit (140). In the data conversion unit (140), the binary data mapped to the cell ID (CID) can be converted into string data according to the conversion request. The data conversion unit (140) can store the converted data in a transmission area for transmitting to the upper server (500).

[0487] Afterwards, the data mapping unit may issue a transmission command to the upper server (500) to the data conversion unit (140). By means of the transmission command, the data conversion unit (140) may transmit string data mapped to a cell ID (CID) to the upper server (500).

[0488]

[0489] FIGS. 11 and 12 disclose a battery manufacturing system (10') and a cell tracking controller (100) to which a virtual cell ID (VID) is applied.

[0490] Except for the fact that a virtual cell ID (VID) is applied and the device configuration within the system is partially changed, it is identical to the battery manufacturing system (10) of FIG. 8 and the cell tracking controller (100) of FIG. 9. Therefore, redundant descriptions regarding parts identical to FIG. 8 and FIG. 9 will be omitted.

[0491] In FIG. 11, a physical cell ID (CID) is not assigned to the battery cell (BC), and a virtual cell ID is assigned to the battery cell (BC). That is, as in FIG. 3, a physical cell ID is not yet marked on the electrode sheet (ES) before it is cut into unit electrodes, so a virtual cell ID (VID) can be assigned. In addition, as in FIG. 4, a physical cell ID is not yet assigned to the electrode sheet (ES) before it is notched, so a virtual cell ID (VID) can be assigned.

[0492] Specifically, a virtual cell ID can be assigned in the following cases.

[0493] 1) Battery cell manufacturing process before physical cell ID is assigned (electrode process, the part of the process prior to notching in the notching process)

[0494] 2) Cases where it is difficult to assign a physical cell ID to the electrode during the process (e.g., cases where it is difficult to mark the cell ID on the anode)

[0495] 3) Even when a physical cell ID is assigned, if the cell ID recognizer (420) is located at the end of the process and the battery cell (BC) is located at the process location before the physical cell ID is recognized

[0496] In FIG. 8, a cell ID recognizer (420) is installed, whereas in FIG. 11, a cell recognizer (430), such as a vision camera, may be installed. The cell recognizer (430) can generate a battery cell detection signal (CDS) and transmit the signal to a cell tracking controller (100).

[0497] In FIG. 12, the cell ID collection unit (110') of the cell tracking controller (100) may include a virtual cell ID generation unit (111') that generates a virtual cell ID (VID) corresponding to the battery cell (BC), and a virtual cell ID tracking unit (112') that tracks the virtual cell ID.

[0498] The virtual cell ID generation unit (111') can assign a predetermined virtual cell ID (VID) to the detected battery cell (BC) based on the detection signal of the battery cell (BC). The virtual cell ID (VID) may include information regarding the sequence number of the battery cell (BC), etc. Alternatively, the virtual cell ID generation unit (111') can assign a virtual cell ID (VID) based on the predetermined specification information (pitch) of the battery cell (BC). For example, a cell ID can be assigned to each electrode sheet portion to be cut into a future electrode according to the electrode specification set in FIG. 3. Alternatively, the virtual cell ID generation unit (111') can assign a virtual cell ID (VID) based on the location information (coordinate information) of the battery cell (BC). For example, a cell ID can be assigned to each electrode sheet portion to be cut into a future electrode according to the electrode specification set in FIG. 11.

[0499] As described above, the virtual cell ID generation unit (111') can assign a virtual cell ID (VID) based on the detection signal of the battery cell (BC), the predetermined specification information of the battery cell (BC), and the location information of the battery cell (BC).

[0500] The virtual cell ID tracking unit (112') can track the virtual cell ID (VID) of the battery cell (BC) as it moves according to the progress of the process for the battery cell (BC) and report it to the cell ID mapping unit (130).

[0501] The virtual cell ID tracking unit (112') can track a moving battery cell (BC) as the battery cell manufacturing process progresses. A position measuring device (410) may be provided to detect the position of the moving battery cell (BC). The virtual cell ID tracking unit (112') can track the moving battery cell (BC) and its virtual ID based on a position value transmitted from the position measuring device (410) (e.g., a rotary encoder or a displacement sensor). The position of the moving battery cell (BC) during the process is reported to the cell tracking controller (100), and the cell tracking controller (100) can detect and track the virtual cell ID (VID) of the battery cell (BC) based on this.

[0502] The cell tracking controller (100) can collect location data of a virtual cell ID (VID) and a battery cell (BC) corresponding to the virtual cell ID (VID), and match coordinate data with a virtual cell ID (VID) corresponding to a specific battery cell (BC).

[0503] In the cell ID mapping unit (130), at least one of inspection data (ID), measurement data (MD), and equipment data (ED) can be mapped to a virtual cell ID (VID).

[0504] The data conversion unit (140) can convert binary data mapped to a virtual cell ID (VID) into string data.

[0505] In accordance with the upper transmission command of the cell ID mapping unit (130), the data conversion unit (140) can transmit string data mapped to a virtual cell ID (VID) to at least one upper server (500).

[0506]

[0507] FIGS. 13 and 14 disclose a battery manufacturing system (10) and a cell tracking controller (100) in which a virtual cell ID (VID) and a physical cell ID (CID) are applied together.

[0508] In this system (10) and cell tracking controller (100), redundant descriptions of parts identical to those in FIG. 8 and FIG. 9 will be omitted.

[0509] In the initial stage of the process of FIG. 13, a virtual cell ID (VID) is assigned to the battery cell (BC). Alternatively, even if a physical cell ID (CID) is assigned, a cell ID recognizer (420) may be provided at the end of the process so that the cell ID cannot be recognized before then. Before the physical cell ID is recognized, the cell tracking controller (100) assigns a virtual cell ID (VID) to each battery cell (BC) to manage and track data in the process.

[0510] In FIG. 13, the cell recognizer (430) can generate a battery cell detection signal (CDS) and transmit the signal to the cell tracking controller (100).

[0511] In FIG. 14, the cell ID collection unit (110) of the cell tracking controller (100) may include a virtual cell ID generation unit (111'), a virtual cell ID tracking unit (112'), and a cell ID detection unit (111).

[0512] As described above, the virtual cell ID generation unit (111') can assign a virtual cell ID (VID) based on a detection signal of a battery cell (BC), a predetermined specification information of a battery cell (BC), or location information of a battery cell (BC).

[0513] The virtual cell ID tracking unit (112') can track a moving battery cell (BC) and its virtual ID (VID) based on a position value transmitted from a position measuring device (410) (e.g., a rotary encoder or a displacement sensor). The position of the battery cell (BC) moving during the process is reported to the cell tracking controller (100), and the cell tracking controller (100) can detect and track the virtual cell ID (VID) of the battery cell (BC) based on this.

[0514] The virtual cell ID tracking unit (112') can report the tracked cell ID to the cell ID mapping unit (130).

[0515] A cell ID marking device (421) installed at the end of the process of FIG. 13 can mark a cell ID on a battery cell (BC).

[0516] As a process end of FIG. 13, a cell ID recognizer (420) installed behind the cell ID marking machine (421) can generate an ID recognition signal (IDS) and transmit this signal to the cell ID detection unit (111) of the cell tracking controller (100).

[0517] The cell ID detection unit (111) may report the detected physical cell ID to the cell ID mapping unit (130). Alternatively, the cell ID detection unit (111) may match the detected physical cell ID with the virtual cell ID (VID). The matched physical cell ID (CID) and virtual cell ID (VID) may be reported from the cell ID detection unit (111) to the cell ID mapping unit (130).

[0518] The cell tracking controller (100) collects a virtual cell ID (VID) and location data of a battery cell (BC) corresponding to the virtual cell ID (VID), and location data of a battery cell (BC) corresponding to a physical cell ID (CID), and can match coordinate data with a virtual cell ID (VID) and a physical cell ID (CID) corresponding to a specific battery cell (BC).

[0519] In the cell ID mapping unit (130), at least one of inspection data (ID), measurement data, and equipment data (ED) can be mapped to at least one of a physical cell ID (CID) and a virtual cell ID (VID).

[0520] The data conversion unit (140) can convert binary data mapped to at least one of a cell ID (CID) and a virtual cell ID (VID) into string data.

[0521] In accordance with the upper transmission command of the cell ID mapping unit (130), the data conversion unit (140) can transmit string data (CID / ED / ID / MD) mapped to at least one of the cell ID (CID) and virtual cell ID (VID) to at least one upper server (500).

[0522]

[0523] Figure 15 is an example of a data set mapped using a cell ID (CID) as a key.

[0524] Data mapped to a cell ID (CID) may include a main key data set containing the cell ID (CID) and the source time at which the data signal was collected.

[0525] The main key data set may include at least one of a facility ID, a lot ID, a data collection unit ID, and location data indicating the location of the battery cell (BC) in the battery cell manufacturing process.

[0526] The facility ID may include information regarding factories, buildings, processes, manufacturing machinery, etc.

[0527] The lot ID may include the project name, product ID, process name, lot number of the electrode roll, etc.

[0528] The data collection unit ID may mean the ID of a data collection unit such as at least one equipment unit included in the inspection device (300), measuring instrument (400), and equipment (EQ).

[0529] The main key data set may further include data collection items. Data collection items may represent, for example, one or more data types or codes collected by each data collection unit.

[0530] The position data is data regarding the position of a battery cell (BC) in the battery manufacturing process. For example, coordinate data regarding the position of an electrode sheet moving in the electrode process can be used. The position data can be obtained by a position measuring device (410) as described above.

[0531] Depending on the electrode specifications, a single electrode may include multiple electrode lanes in the electrode process. For example, by a stripe coating process, an electrode sheet in which coated and uncoated portions are repeated on a single current collector may be manufactured. Accordingly, multiple electrode lanes may be formed on a single current collector. The main key data set may also include information regarding the electrode lanes.

[0532] The main key data set must include a Cell ID (CID). The Cell ID (CID) may be a Physical Cell ID (CID), a Virtual Cell ID (VID), or both.

[0533] A data value can be mapped to a main key dataset containing a cell ID (CID). The data value may be an inspection value, a measurement value, or an equipment sensor value.

[0534] Mapping data may include the source time at which the data signal was collected.

[0535] At least one of the above cell ID (CID), inspection data (ID), measurement data, and equipment data (ED) may be time series data. Time series data may refer to data observed in chronological order. That is, each data point may be aligned chronologically. Each data point may be indexed by time. Each data point may be matched to the source time at which each data signal was collected.

[0536] Accordingly, at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) can be mapped using the cell ID (CID) as the primary key and the source time as the sub-key.

[0537] At least one of the inspection data (ID), measurement data (MD), and equipment data (ED) is mapped using a standardized parameter called a cell ID (CID) as a key. Accordingly, the data set disclosed in FIG. 15 can be referred to as a standardized data set.

[0538] When a data set standardized by a cell ID (CID) is transmitted to multiple subsystems (upper server (500)), the data standards of each subsystem can be unified based on the cell ID (CID). Therefore, data analysis between each subsystem can be performed in an organically linked manner.

[0539] As illustrated in FIGS. 8 to 14, the standardized data set can be transmitted to at least one upper server (500).

[0540] The battery manufacturing system illustrated in the drawings above may include at least one upper server (500).

[0541] The above upper server (500) can perform at least one of the following operations.

[0542] 1) Generation of monitoring data based on mapped data

[0543] 2) At least one of anomaly detection and anomaly alarm generation based on mapped data

[0544] 3) Generation of a correction value (CV) for the process progress condition (Recipe Parameter) of the equipment controller (200) based on the mapped data

[0545] For example, if the upper server (500) or subsystem is a manufacturing execution system (MES: 530)) or a statistical process control (SPC: 540)) it can generate monitoring data regarding the battery cell manufacturing process based on mapped standardized data (set). For example, when a standardized data set is transmitted from the cell tracking controller (100) of each process to the MES (530) or SPC (540), each upper server (500) can generate manufacturing-related monitoring data based on the standardized data set of each process.

[0546] Alternatively, for example, in the case of an FDC (Fault Detection & Classification) server (520), it may receive a standardized data set of each process from the cell tracking controller (100) of each process, detect anomalies from this data set, or issue an alarm for the detected anomalies. Anomalies may include data omissions, data delays, or cases where the value of each data falls outside a set range.

[0547] Alternatively, for example, an APC (Advanced Process Control) server (510) may receive a standardized data set of each process from a cell tracking controller (100) of each process. In this case, the APC may generate a correction value (CV) for the process progress condition (Recipe Parameter) of the equipment controller (200) based on the mapped data. The APC server transmits the correction value (CV) to the equipment controller (200) so that the equipment controller (200) can control the process based on the correction value (CV).

[0548] For example, when data values ​​regarding processing mechanisms such as the motor of the transfer device (TD), the coater, or the roll press are corrected, the corrected value (CV) can be transmitted to the equipment controller (200) for the coating process, etc., to enable feedback control and feedforward control of each process. Accordingly, the quality of the battery cell (BC) produced in each process can be made uniform or improved, or the yield can be improved.

[0549] The standardized data set can also be transmitted to other subsystems other than the server exemplified above.

[0550] In addition, since each upper server (500) receives a standardized data set in real time, in process management, monitoring, anomaly detection, alarm generation, and correction value (CV) generation can be performed based on real-time data. Therefore, a real-time data collection and processing environment can be established throughout the entire battery manufacturing system by the cell tracking controller (100) of the present disclosure.

[0551] FIG. 16 is an example of a battery manufacturing system (10''') including a T branch module (210), and FIG. 17 shows an example of a collection path for equipment data (ED).

[0552] In the above-described embodiment, the equipment data (ED) is collected in the equipment controller (200).

[0553] However, various types of equipment data (ED1, ED2, ED3) generated from the equipment can be classified into equipment control data for controlling the equipment (e.g., line speed data of a servo motor) and monitoring data (e.g., data regarding the pressure filter of a coating pump).

[0554] As shown in FIG. 17(a), when all data collected from the equipment controller (200) is transmitted to the cell tracking controller (100), a large load is applied to the equipment controller (200). Furthermore, since data is transmitted from the equipment controller (200), which has a large data load, back to the cell tracking controller (100), the transmission speed may be reduced. In addition, among the equipment data (ED), data other than that for equipment control does not need to be directly collected by the equipment controller (200). Also, data for equipment control does not need to be collected by the cell tracking controller (100).

[0555] Accordingly, as shown in FIGS. 16 and FIGS. 17(b), it may be reasonable to split the equipment data (ED) into equipment control data and monitoring data, and to transmit only the monitoring data to the cell tracking controller (100). In this case, since only the monitoring data is transmitted directly to the cell tracking controller (100), the load applied to each controller can be reduced and the data transmission speed can be increased.

[0556] A T branch module (210) can be applied for data branching.

[0557] Referring to FIG. 16, among the various equipment data (ED1, ED2, ED3) transmitted to the equipment controller (200), monitoring data can be branched at the T-branch module (210) and transmitted to the cell tracking controller (100). The monitoring data can be transmitted directly to the cell tracking controller (100) without passing through the equipment controller (200).

[0558] The branched monitoring data can be mapped to a cell ID (CID) in the cell tracking controller (100) and transmitted to at least one upper server (500).

[0559] Referring to FIG. 17(b), the data replication and branching process in the T-branch module (210) is shown. The T-branch module (210) may include a source equipment data receiving area (211), an equipment control data area (212), a monitoring data area (213), and a data replication unit (214).

[0560] The source equipment data receiving area (211), the equipment control data area (212), and the monitoring data area (213) may be pre-configured memory areas of the T-branch module (210). Data branching may be performed by replicating monitoring data among the equipment data from the data replication unit (214) using a so-called data mirroring technique, but is not limited thereto.

[0561] Data mirroring is the redundant storage of data in one or more devices to prevent data loss when an accident occurs in which equipment fails. This technique can be implemented by hardware or software. The T-branch module (210) may include a data replication unit (214) that performs data mirroring by copying monitoring data among the data transmitted from the source equipment data receiving area (211) to the equipment control data area (211). The copied data is transferred (stored) to the monitoring data area (213) and can be transmitted directly to the cell tracking controller (100) via a communication interface without passing through the equipment controller (200).

[0562] The embodiments of FIGS. 16 and 17 can be described as a battery manufacturing system in which equipment data (monitoring data) is transmitted directly from the equipment to a cell tracking controller (100).

[0563] That is, the battery manufacturing system of the above embodiment is,

[0564] A cell tracking controller (100) configured to collect cell IDs (CID);

[0565] It may include at least one inspection device (300) configured to collect inspection data (ID) of a battery cell (BC); at least one measuring device (400) configured to collect at least one of measurement data (MD) of a battery cell (BC); and at least one sensor for sensing equipment data (ED) of a battery cell manufacturing process (EQ).

[0566] The cell tracking controller (100) may be configured to map at least one of inspection data (ID), measurement data (MD), and equipment data (ED) corresponding to the cell ID (CID) to the cell ID (CID).

[0567] The cell tracking controller (100) above is,

[0568] Mapped data can be transmitted to at least one upper server (500), and the data collection, data mapping, and data transmission can be configured to be performed in real time.

[0569] Additionally, the cell tracking controller (100) further includes a data conversion unit (140) that converts the mapped data into a form required by the upper server (500).

[0570] The cell tracking controller (100) may be configured to perform cell ID collection, data collection, data mapping, data conversion, and data transmission in real time.

[0571]

[0572] FIG. 18 is a flowchart showing an example of a battery manufacturing method.

[0573] The battery manufacturing method of the present disclosure includes the step (P10) of collecting a cell ID (CID), which is identification information of a battery cell (BC);

[0574] A step (P20) of collecting at least one of inspection data (ID) of the battery cell (BC), measurement data (MD) of the battery cell, and equipment data (ED) from the battery cell manufacturing process equipment or the equipment controller (200) that controls the equipment; and

[0575] It may include a step (P30) of mapping at least one of inspection data (ID), measurement data (MD), and equipment data (ED) corresponding to the cell ID (CID) to the cell ID (CID).

[0576] In the cell ID collection step (P10), the cell tracking controller (100) may collect a physical cell ID (CID) or a virtual cell ID (VID) of the battery cell manufacturing process, or both. To collect the cell ID, the cell tracking controller (100) may include a cell ID collection unit (110). The cell ID collection unit (110) may include a cell ID detection unit (111) and a cell ID tracking unit (112) for cell ID detection and tracking. Alternatively, the cell ID collection unit (110) may include a virtual cell ID generation unit (111') and a virtual cell ID tracking unit (112') for virtual cell ID generation and tracking. Alternatively, the cell ID collection unit (110) may include a virtual cell ID generation unit (111'), a virtual cell ID tracking unit (112'), and a physical cell ID detection unit (111).

[0577] At least one of the cell ID and virtual cell ID (VID) collected by the cell ID collection unit (110) can be reported to the cell ID mapping unit (130).

[0578] In the data collection step (P20), at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) of the battery cell (BC) may be collected.

[0579] Inspection data (ID) can be collected by an inspector (300), and measurement data can be collected by a measuring instrument (400). At least one inspector (300) or measuring instrument (400) may be provided in the battery cell manufacturing process.

[0580] Additionally, equipment data (ED) may be collected from a battery cell manufacturing process facility or an equipment controller (200) that controls the facility. The battery manufacturing method of the present embodiment may further include a step of branching the equipment data (ED) into equipment control data and monitoring data. For example, monitoring data may be branched from the equipment data (ED) by a T-branching module (210) and transmitted directly to the cell tracking controller (100) without passing through the equipment controller (200).

[0581] In the cell ID mapping step (P30), at least one of the collected inspection data (ID), measurement data, and equipment data (ED) can be mapped to a corresponding cell ID (CID).

[0582] Each collected data can be mapped to a cell ID (CID) based on the time at which the data was acquired or the location data of the battery cell (BC) from which the data was acquired. The cell ID (CID) corresponding to each collected data may be a cell ID (CID) acquired at the same time or at the same location as the time at which each data was collected.

[0583] The cell ID mapping unit (130) of the cell tracking controller (100) can map collected data to the cell ID and configure a standardized data set using the cell ID (CID) as a key.

[0584] The above cell ID collection, data collection, and data mapping can be performed in real time. Real time may be the time it takes for one battery cell (BC) to move in each battery manufacturing process.

[0585] The above manufacturing method may further include the step (P50) of transmitting mapped data to at least one upper server (500).

[0586] The above manufacturing method may further include a data conversion step (P40) prior to the data transmission step (P50), in which the mapped data is converted into data of a required form at the upper server (500).

[0587] In the data conversion step (P40), binary data mapped to the cell ID (CID) can be converted into string data. A dedicated module for data conversion may be provided in the cell tracking controller (100). By having the dedicated module perform the data conversion, the load applied to the CPU of the cell tracking controller (100) can be reduced, and the conversion operation can be performed quickly.

[0588] The above cell ID collection, data collection, data mapping, data conversion, and data transmission can be performed in real time.

[0589] A real-time data processing and transmission / reception environment can be implemented by the battery manufacturing method of this embodiment.

[0590] Since the battery manufacturing method of the present embodiment allows for easy tracking of a battery cell and data related to the battery cell, the battery manufacturing method may be described as a battery cell tracking method, or as a battery manufacturing method including the battery cell tracking method.

[0591]

[0592] Figure 19 is a flowchart showing another example of a battery cell manufacturing method.

[0593] According to FIG. 19, a battery manufacturing method of one embodiment may be provided.

[0594] The above battery manufacturing method is,

[0595] A step (P10) of collecting a cell ID (CID), which is identification information of a battery cell;

[0596] A step (P20) of collecting at least one of the battery cell inspection data (ID), the battery cell measurement data, and the battery cell manufacturing process equipment data (ED);

[0597] A step (P30') of mapping at least one of inspection data (ID), measurement data, and equipment data (ED) corresponding to the collected cell ID (CID) to the cell ID (CID); and

[0598] It may include a step (P40') of converting binary data mapped to the cell ID (CID) into string data.

[0599] The above battery manufacturing method may further include the step (P50') of transmitting string data mapped to a cell ID (CID) to at least one upper server (500).

[0600] The cell ID collection step (P10) is the same as in Fig. 18.

[0601] The step (P20) of collecting at least one of inspection data (ID), measurement data and equipment data (ED) is also the same as in FIG. 18.

[0602] The data collected by the PLC is binary data represented by 0s and 1s. In the cell ID mapping step (P30'), the collected binary data can be mapped to a cell ID (CID).

[0603] In the data conversion step (P40'), binary data can be converted into string data. A data conversion module separate from the CPU may be provided for data conversion.

[0604] String data mapped to a cell ID (CID) can be transmitted to an upper server (500).

[0605] The above cell ID collection, data collection, data mapping, data conversion, and data transmission can be performed in real time.

[0606] Since the battery manufacturing method of the present embodiment allows for easy tracking of a battery cell and data related to the battery cell, the battery manufacturing method may be described as a battery cell tracking method, or as a battery manufacturing method including the battery cell tracking method.

[0607]

[0608] The present disclosure may also provide a battery manufacturing system that converts binary data into string data and provides it to an upper server (500).

[0609] The above battery manufacturing system is,

[0610] A cell tracking controller (100) configured to collect cell ID (CID), which is identification information of a battery cell (BC); and

[0611] It may include an equipment controller (200) configured to collect equipment data (ED) from equipment of a battery cell manufacturing process.

[0612] The cell tracking controller (100) above is,

[0613] Equipment data (ED), which is binary data corresponding to the above cell ID (CID), is mapped to the above cell ID (CID), and

[0614] Convert the above mapped binary data into string data, and

[0615] String data mapped to the cell ID (CID) can be transmitted to at least one upper server (500).

[0616] A similar battery manufacturing system may be provided.

[0617] The above battery manufacturing system is,

[0618] A cell tracking controller (100) configured to collect cell ID (CID), which is identification information of a battery cell (BC); and

[0619] The battery cell manufacturing process equipment includes at least one sensor for sensing equipment data (ED), and

[0620] The cell tracking controller (100) above is,

[0621] Equipment data (ED), which is binary data corresponding to the above cell ID (CID), is mapped to the above cell ID (CID), and

[0622] Convert the above mapped binary data into string data, and

[0623] String data mapped to the cell ID (CID) can be transmitted to at least one upper server (500).

[0624] The above battery manufacturing systems are,

[0625] It may further include at least one of at least one inspector (300) configured to collect inspection data (ID) of a battery cell (BC) and at least one measuring instrument (400) configured to collect inspection data (ID) of a battery cell (BC).

[0626] The cell tracking controller (100) above is,

[0627] At least one of the inspection data (ID), measurement data, and equipment data (ED), which are binary data corresponding to the cell ID (CID), is mapped to the cell ID (CID), and

[0628] Convert the above mapped binary data into string data, and

[0629] String data mapped to the cell ID (CID) can be transmitted to at least one upper server (500).

[0630] Other similar battery manufacturing systems may be provided.

[0631] The above battery manufacturing system is,

[0632] A cell tracking controller (100) configured to collect cell ID (CID), which is identification information of a battery cell (BC); and

[0633] It includes at least one of at least one inspector (300) configured to collect inspection data (ID) of a battery cell (BC) and at least one measuring instrument (400) configured to collect measurement data (MD) of a battery cell (BC).

[0634] The cell tracking controller (100) above is,

[0635] At least one of the inspection data (ID) and measurement data, which are binary data corresponding to the cell ID (CID), is mapped to the cell ID (CID), and

[0636] Convert the above mapped binary data into string data, and

[0637] String data mapped to the cell ID (CID) can be transmitted to at least one upper server (500).

[0638]

[0639]

[0640] Figure 20 is an example of a battery manufacturing system (20).

[0641] As described above, a real-time data collection and processing environment can be established in the battery manufacturing system by introducing a cell tracking controller (100). Additionally, a standardized data set mapped using a cell ID (CID) as a key can be obtained from the cell tracking controller (100). Since the functions of each subsystem can be performed based on the standardized data set, organic and unified data processing and analysis are possible among multiple subsystems.

[0642] For the above data analysis, it is necessary to map the inspection data (ID) and the cell ID (CID) without omission. In other words, consistency in the mapping between the inspection data (ID) and the cell ID (CID) must be ensured.

[0643] As shown in FIG. 9, the mapping of cell ID (CID) and inspection data (ID) may be performed at the cell tracking controller (100), but it may also be performed at the inspector (300). The inspector (300) can receive the cell ID (CID) from the cell tracking controller (100) and map it to the inspection data (ID). The inspector (300) can transmit the mapped data to a server for generating monitoring data. Additionally, the inspector (300) can transmit the mapped data to the cell tracking controller (100). Since the cell tracking controller (100) receives the pre-mapped data from the inspector (300), the data processing resources in the controller can be reduced, and the data processing speed in the controller can be improved. The cell tracking controller (100) can transmit the mapped data to another server, such as an anomaly detection server. In this case, the mapped data may include equipment data (ED) in addition to the inspection data (ID) (see FIG. 9).

[0644] Meanwhile, when the cell tracking controller (100) transmits the cell ID (CID) to the inspector (300) and the inspector (300) maps the cell ID (CID) to the inspection data (ID), data omission may occur.

[0645] If missing data occurs, it may be difficult to analyze the cause, such as whether the cell tracking controller (100) did not transmit the cell ID (CID) to the inspector (300), or whether the inspector (300) received the cell ID (CID) but did not add the cell ID (CID) and only transmitted the inspection data (ID) to the upper server (500).

[0646] Therefore, it is necessary to improve the inspection data collection system in the inspection device (300) so that it can be determined at which communication stage the omission occurred when the above data is omitted.

[0647] FIG. 20 shows a battery manufacturing system (20) including an inspector (300) with an improved inspection data collection system.

[0648] The above system (20) may include a cell tracking controller (100) and an inspector (300).

[0649] As described with reference to FIGS. 8 to 15, the cell tracking controller (100) may be configured to collect a cell ID (CID), which is identification information of a battery cell (BC).

[0650] As described above, the cell tracking controller (100) can map at least one of inspection data (ID), measurement data (MD), and equipment data (ED) to a cell ID (CID). The binary data mapped to the cell ID (CID) can be converted into string data by the data conversion unit (140). The string data mapped to the cell ID (CID) can be transmitted to an upper server (500) by the data conversion unit (140).

[0651] In this embodiment, the mapping of inspection data (ID) and cell ID (CID) may be performed in advance at the inspection device (300) rather than at the cell tracking controller (100). When data mapped in advance at the inspection device (300) is transmitted to the cell tracking controller (100), the data mapping unit of the controller may build a standardized data set by additionally mapping equipment data (ED) or measurement data (MD) to the inspection data (ID) mapped to the cell ID (CID).

[0652] In order to enable mapping between the cell ID (CID) and inspection data (ID) in the inspection device (300), the cell tracking controller (100) can transmit the collected cell ID (CID) to the inspection device (300).

[0653] The above-mentioned inspector (300) generates inspection data (ID) based on an inspection signal (IS) of a battery cell (BC), and

[0654] Receive the cell ID (CID) of the above battery cell (BC), and

[0655] Mapping data is generated by mapping inspection data (ID) corresponding to the cell ID (CID) to the cell ID (CID), and

[0656] The above mapping data can be configured to be transmitted to at least one upper server (500).

[0657] The inspection device (300) may include a sensing unit (310) and a processing unit (320) (e.g., an inspection device PC). The sensing unit (310) may be configured to detect the physical quantity of a battery cell (BC) to generate an inspection signal (IS).

[0658] The processing unit (320) can generate inspection data (ID) based on the inspection signal (IS) sensed by the sensing unit. The processing unit (320) may include a processor (CPU) capable of performing operations such as generating inspection data, mapping the cell ID (CID) to the inspection data (ID), and collecting the mapped data. The processing unit (320) may be connected to the sensing unit (310) via a wired or wireless connection.

[0659] The above-mentioned inspector (300) may be configured to receive the cell ID (CID) from the cell tracking controller (100) and transmit the mapping data (CID / ID) to the cell tracking controller (100).

[0660] The above processing unit (320) may include an inspection data generation unit (321), an inspection data collection unit (322), and an API (Application Programming Interface).

[0661] The inspection data generation unit (321) can analyze an inspection signal (IS) based on a predetermined inspection algorithm or make a determination regarding the quality of the battery cell (BC) by comparing it with a normal signal, etc. That is, the inspection data generation unit (321) can generate an inspection result file by inputting an inspection signal into the inspection algorithm. The inspection result file may include results such as good quality or poor quality of the battery cell (BC). The inspection result file may constitute inspection data (ID).

[0662] The inspection data generation unit (321) may also be configured to generate mapping data by mapping inspection data (ID) corresponding to the cell ID (CID) to the cell ID (CID). The inspection algorithm may further include mapping data generation logic or a program. For example, cell IDs (CID) and inspection data (ID) acquired at the same time or at the same location in a battery cell manufacturing process may be associated (mapped) with each other. The inspection device (300) may receive data acquisition time values ​​or data acquisition location values ​​from, for example, the equipment controller (200).

[0663] Mapping data including inspection data (ID) (inspection result file) and cell ID (CID) can be collected by an inspection data collection unit (322). The inspection data collection unit (322) may be configured to collect mapping data from an inspection data generation unit (321). The inspection data collection unit (322) may be configured to transmit the collected mapping data to at least one upper server (500) (e.g., SPC (540)). The inspection data collection unit (322) may be a software agent configured to automatically and repeatedly perform data collection, or hardware including said software agent. The agent may be autonomous process software that performs tasks on behalf of a user for a specific purpose.

[0664] The above-described inspector (300) may further include an API configured to receive the cell ID (CID) from the cell tracking controller (100) and transmit the mapping data to the cell tracking controller (100). An API is a type of software interface. Unlike a user interface that connects a computer and a human, an API connects computers or software to each other. Additionally, an API may be composed of different parts and serves as a tool or service that can be used by a programmer or program. When a program or programmer uses one of these parts, it can be said that the corresponding part of the API is called.

[0665] The applicant has developed an API by adding a function to transmit mapping data of the cell ID (CID) and inspection data (ID) from the inspection device (300) to the cell tracking controller (100), in addition to the function of simply transmitting the cell ID (CID) from the cell tracking controller (100) to the inspection device (300). For example, the cell tracking controller (100) transmitting the cell ID (CID) to the inspection device (300) may be an API request or an API call. The API may be configured to provide a service of transmitting mapping data from the inspection data (ID) generation unit to the cell tracking controller (100) upon receipt of the cell ID (CID).

[0666] The above API can be written based on the TCP / IP protocol. For example, in the case of data transmission based on the commonly used MC protocol, the transmission of the cell ID (CID) cannot be performed quickly. The applicant has developed a dedicated API suitable for a checker (300) capable of implementing the above-described data transmission and reception based on the TCP / IP protocol.

[0667] Meanwhile, as described above, data omission may occur during data transmission and reception between the cell tracking controller (100) and the inspector (300). If data is omitted, it is difficult to analyze the cause, such as whether the cell tracking controller (100) did not transmit the cell ID (CID) to the inspector (300), or whether the inspector (300) received the cell ID (CID) but transmitted only the inspection data (ID) to the upper server (500) without adding the cell ID (CID).

[0668] To analyze the cause of data omission, a data logger function can be added to the above API.

[0669] A log file is a file that records events occurring during the execution of a processor's operating system or other software, or messages between different software programs of the processor (e.g., communication software).

[0670] According to the present embodiment, the API may be configured to store a log file regarding at least one of the processes of receiving a cell ID (CID) through the API, transmitting mapping data to a cell tracking controller (100), and collecting generated mapping data within an inspector (300). Specifically, the API may generate and store a log file regarding the process of transmitting a cell ID (CID) from the cell tracking controller (100) to an inspection data generation unit (321). Additionally, the API may generate and store a log file regarding the process of transmitting mapping data from the inspection data generation unit (321) to the cell tracking controller (100). Furthermore, the API may generate and store a log file regarding the process of transmitting (collecting) mapping data from the inspection data generation unit (321) to an inspection data collection unit (322).

[0671] By analyzing the above log file, it is easy to identify, for example, at which communication stage data omission occurs.

[0672] When a trigger event occurs, such as data omission or data duplication, a user device (UD) can send a log file request (LR) command to the API. Alternatively, a top-level server (500) can send a log file request (LR) command to the API. The API can transmit the stored log file to the user device (UD) or the top-level server (500) in accordance with the command. The server or user can analyze the message transmission records included in the log file to easily identify at which stage the data omission or duplication occurred.

[0673] The cell tracking controller (100) can transmit mapping data of the cell ID (CID) and inspection data (ID) received from the inspector (300) to at least one upper server (500) (first server). Of course, the mapping data may additionally include measurement data (MD) and equipment data (ED). When the mapping data is transmitted to the APC (510), the APC can generate a correction value (CV) for the process progress condition (Recipe Parameter) of the equipment controller (200) based on the mapping data. When the mapping data is transmitted to the FDC (520), the FDC can detect an anomaly based on the mapping data or issue an alarm for the detected anomaly.

[0674] The inspector (300) can transmit mapping data of cell ID (CID) and inspection data (ID) to at least one upper server (500) (second server).

[0675] When mapping data is transmitted to SPC (540), SPC can generate monitoring data (e.g., roll map data) regarding the battery cell manufacturing process based on the mapping data.

[0676]

[0677] Figure 21 is a flowchart regarding a battery manufacturing method.

[0678] According to an exemplary embodiment, a method for manufacturing a battery may be provided.

[0679] The above manufacturing method comprises the step (P110) of generating inspection data (ID) based on an inspection signal (IS) of a battery cell (BC);

[0680] Step (P120) of receiving the cell ID (CID) of the battery cell (BC); and

[0681] A step (P130) of generating mapping data by mapping inspection data (ID) corresponding to the cell ID (CID) to the cell ID (CID); and

[0682] The method may include the step (P150) of transmitting the above mapping data to at least one upper server (500).

[0683] The sensing unit (310) (sensor) of the inspection device (300) can sense the physical quantity of the battery cell (BC) in the battery cell manufacturing process and generate an inspection signal (IS). The inspection signal (IS) can be input into a predetermined inspection algorithm of the processing unit (320) to generate inspection data (ID) (inspection result file). The inspection data generation unit (321) of the inspection device (300) can generate inspection data (ID) based on the inspection signal.

[0684] The inspector (300) can receive the cell ID (CID) of the battery cell (BC). The cell ID (CID) can be received, for example, from the cell tracking controller (100).

[0685] The above cell ID (CID) can be mapped to inspection data (ID) corresponding to the cell ID (CID). The inspection data generation unit (321) can generate inspection data (ID) and map the generated inspection data (ID) to the cell ID (CID) to generate mapping data.

[0686] The above mapping data (CID / ID) can be transmitted to at least one upper server (500) (P150).

[0687] The above mapping data can be transmitted to the cell tracking controller (100) (P142).

[0688] The cell tracking controller (100) can map the mapping data or additional data to the mapping data and transmit it to at least one upper server (500) (P150).

[0689] The upper server (500) to which the inspector (300) transmits mapping data and the upper server (500) to which the cell tracking controller (100) transmits mapping data may be different.

[0690] The above cell ID (CID) can be received from the cell tracking controller (100) via an API. The inspector (300) may include an API for transmitting and receiving data. The API may be configured to transmit the mapping data to the cell tracking controller (100).

[0691] The method may further include a step (P141) of collecting the mapping data before the step of transmitting the mapping data to the upper server (500). The inspector (300) may further include an inspection data collection unit (322) that collects mapping data from the inspection data generation unit (321). The inspection data collection unit (322) may transmit the mapping data to the upper server (P150).

[0692] A data logger function may be provided to the above API.

[0693] The above API may be configured to store a log file regarding at least one process among receiving a cell ID through the API, transmitting mapping data to a cell tracking controller (100) through the API, and collecting mapping data. By analyzing the message transmission records of the log file, it is possible to determine which communication stage data omission occurred.

[0694] Since inspection data can be efficiently processed by the battery manufacturing method of the present embodiment, the battery manufacturing method may also be referred to as an inspection data processing method or as a battery manufacturing method including the same.

[0695] FIG. 22 is an example of a battery manufacturing system (30).

[0696] FIG. 22 discloses a system (30) that collects high-frequency data (HFD) generated as the process of a battery cell (BC) progresses and transmits it to an anomaly detection server, FDC (520).

[0697] High frequency data (HFD) may refer to data that fluctuates at high frequency during the process of a battery cell (BC). For example, time series data that fluctuates at a frequency of kHz or higher or MHz or higher for a period of time of 1 second or less may be referred to as high frequency data (HFD).

[0698] Time series data may refer to data observed in chronological order. High-frequency data (HFD) is data that fluctuates over time at a high frequency of kHz or MHz or higher for a period of time less than 1 second. For example, at least one of the vibration of a drive device included in battery manufacturing process equipment and the current flowing through the drive device fluctuates at a high frequency for a short period of time of 1 second or less. In particular, alternating current fluctuates at a high frequency of 100 kHz or higher, and such current can be referred to as high-frequency current. High-frequency data (HFD) is not limited to vibration data or current data. In addition to vibration and current, other parameters exhibiting significant changes at kHz or MHz or higher for a period of time less than 1 second during the process for battery cells (BC) may also be included in high-frequency data (HFD).

[0699] Since high-frequency data (HFD) exhibits many changes (frequencies) over a short period of time, a sensor with high resolution is required to detect high-frequency data (HFD). In this sense, high-frequency data (HFD) can be referred to as high-resolution data or high-resolution data. Additionally, a high-frequency data detection sensor (HFS) can be referred to as a high-resolution sensor or high-resolution sensor.

[0700] In the present disclosure, high-frequency data (HFD) in the range of 4 kHz to 50 kHz per second generated according to the process progress can be collected according to the embodiments.

[0701] In order to collect high frequency data (HFD), a dedicated data acquisition device including a high-resolution sensor may be required as described above. For example, a DAQ (Data Acquisition) device / system capable of measuring and recording electrical and physical quantities such as voltage, current, temperature, strain, pressure, shock, vibration, distance, displacement, RPM, angle, and weight may be applied as the data acquisition device (250).

[0702] Since high-frequency data (HFD) contains a large amount of data over a short period of time, it is not transmitted to the equipment controller (200) even when it occurs in the equipment normally. Since the equipment controller (200) performs its original purpose of controlling the equipment, if it processes large-capacity data such as high-frequency data (HFD), the original operation of the equipment controller (200) may be difficult. Referring to FIG. 22, high-frequency data (HFD) is detected by a high-frequency detection sensor (251) and transmitted to an edge PC (260) through DAQ hardware (252). At the edge PC (260), the raw high-frequency data (HFD) can be compressed and / or sampled to be converted into so-called feature data. The high-frequency feature data converted from the edge PC (260) can be transmitted to an anomaly detection server (FDC) (520). The anomaly detection server (FDC) can detect anomalies by analyzing the high-frequency feature data generated in the process.

[0703] Meanwhile, at least one of the inspection data (ID) and measurement data (MD) acquired in the process can be mapped to the cell ID (CID) by receiving the cell ID (CID) from the cell tracking controller (100) as shown in FIG. 22. At least one of the inspection data (ID) and measurement data (MD) mapped to the cell ID (CID) can be transmitted to a server (e.g., SPC (540)) for generating monitoring data.

[0704] However, the high-frequency data (HFD) collected in the FDC (520) is time-series data, and at least one of the inspection data (ID) and measurement data (MD) collected in the SPC (540) is mapped to a cell ID (CID). That is, the data collected from each subsystem (FDC, SPC) is managed by different management standards (i.e., time and cell ID (CID)). Because of this, even if the data is generated in the same process, it is difficult to perform linked analysis because there is no common management standard.

[0705] In order to perform linked analysis of high-frequency data (HFD) and other data based on the same criteria, the battery manufacturing system (40) of FIG. 23 may be presented.

[0706] The system (40) of FIG. 23 may include a cell tracking controller (100), a data collection device (250), and a mapper (270).

[0707] A cell tracking controller (100) may be configured to collect a cell ID (CID), which is identification information of a battery cell (BC). The cell tracking controller (100) may include a cell ID collection unit (110), a data collection unit (120) that collects at least one of inspection data (ID), measurement data (MD), and equipment data (ED), and a cell ID mapping unit (130) configured to map at least one of inspection data (ID), measurement data (MD), and equipment data (ED) corresponding to the cell ID (CID) to the cell ID (CID) (see FIG. 9). The cell ID collection unit (110) may detect and track the cell ID (CID) of a battery cell (BC) moving in the process based on a cell ID detection signal (IDS) transmitted by a cell ID recognizer (420). The cell tracking controller (100) may transmit the collected cell ID (CID) to a mapping unit (270). Alternatively, the cell tracking controller (100) can transmit data mapped to a cell ID (CID) to a mapper (270).

[0708] The data collection device (250) may be configured to collect high-frequency data (HFD) generated as the process of the battery cell (BC) progresses. As the data collection device (250), for example, a DAQ device / system from NI (National Instruments) may be used.

[0709] The data collection device (250) may include at least one high-frequency detection sensor (251) that detects a high-frequency signal and data collection hardware (252).

[0710] Figures 23 and 24 are schematic diagrams illustrating the process of collecting high-frequency data.

[0711] A plurality of high-frequency detection sensors (251) may be installed in the process for the battery cell (BC). Each high-frequency detection sensor (251) can detect high-frequency data (HFD) when each battery cell (BC) moves. Accordingly, each high-frequency data (HFD) can be associated with the battery cell (BC) or the cell ID (CID) of the battery cell (BC) based on the time of detection. The sensor (251) may be a transducer. A transducer can convert a physical quantity into an electrical signal. For example, the high-frequency detection sensor (251) can detect an alternating current flowing through a motor for driving the equipment of the process. The detected alternating current signal can be transmitted to data collection hardware (252).

[0712] Data acquisition hardware (252) can convert an analog high-frequency signal that is conditioned and input into a digital signal. To this end, the hardware may include an analog-to-digital converter (ADC). The converted digital signal can be processed through a computer bus (bua) and stored as raw data of high-frequency data (HFD). For processing and storing high-frequency raw data, the hardware (252) may include a computer equipped with certain driver software and application software.

[0713] The data collection device (250) can transmit raw data (time series data) of high-frequency data (HFD) to the mapper (270).

[0714] A mapping device (270) may be configured to map high-frequency data (HFD) corresponding to a cell ID (CID) to the cell ID (CID). The mapping device may be an Embedded Computer System (ECS), but is not limited thereto. An ECS is a software system integrated into computer hardware and may form a separate system for operating various applications. An ECS includes hardware and software, and these may operate on a microprocessor or microcontroller, which is an integrated circuit that provides data for computation.

[0715] For example, high-frequency data (HFD) and cell IDs (CID) collected at the same time or location in a process can be associated (mapped) with each other.

[0716] The mapping unit (270) can convert raw data of high-frequency data (HFD) mapped to a cell ID (CID) into feature data. FIG. 25 is a schematic diagram showing the conversion process of high-frequency data in the mapping unit (270).

[0717] High frequency data (HFD) collected from the data collection device (250) can be called raw data or raw data in the sense that it has not been processed into feature data.

[0718] Feature data can refer to data to which characteristics have been assigned by processing raw data. The process of processing raw data to represent data characteristics can be called featuring. Feature data is data generated by featuring raw data. Raw data can be converted into feature data by compressing and / or sampling.

[0719] The compressed and / or sampled data may include representative values ​​of the raw data of the high-frequency data (HFD). For example, at least one of the mean, standard deviation, median, maximum, and minimum values ​​of the digital raw data collected per second may be used as a representative value. The mean, mean, standard deviation, median, maximum, and minimum values ​​may each represent statistical characteristics or other characteristics. In this sense, the values ​​become feature data having characteristics.

[0720] The mapping device (270) may include a predetermined conversion algorithm or conversion software for converting raw data into feature data. The algorithm or software may be implemented, for example, by the Python programming language.

[0721] The converted feature data can be mapped to a cell ID (CID) in the mapper (270). The high-frequency feature data mapped to the cell ID (CID) can be transmitted to at least one upper server (500) (e.g., FDC (520)).

[0722] The mapping device (270) can collect high-frequency raw data for a first period of time from the data collection device (250) at a first period. The data collection period can be determined by considering data capacity, data processing and conversion speed, and the processing speed of the data transmission and reception line. For example, the first period may be any one of 3 minutes, 4 minutes, or 5 minutes, but is not limited thereto. In addition, the raw data collected at each period may be data collected during the first period of time. The first period of time may be one time selected from 1 to 20 seconds, but is not limited thereto. The mapping device (270) can collect raw data collected for several seconds from the data collection device (250) for example every 5 minutes.

[0723] The mapping device (270) can convert the raw data of the collected high-frequency data (HFD) into high-frequency feature data. The mapping device (270) may be configured to transmit the high-frequency feature data to the upper server (500) at the first cycle. The high-frequency feature data may be the feature data of the raw data collected during the first time period.

[0724] The mapping device (270) of the present disclosure can detect mechanical defects occurring in the motor (M) or drive unit at an early stage by periodically diagnosing high-frequency feature data.

[0725] The above system (40) may further include a fault detection and classification server (520) that detects whether there is an abnormality in the battery cell manufacturing process based on mapping data of cell ID (CID) and high frequency data (HFD).

[0726] The abnormality detection server (520) can detect whether there is an abnormality in the battery cell manufacturing process or issue an abnormality alarm based on high-frequency feature data received at predetermined intervals.

[0727] The above system (40) may further include at least one of at least one inspector (300) configured to collect inspection data (ID) of the battery cell and at least one measuring instrument (400) configured to collect measurement data (MD) of the battery cell.

[0728] As illustrated in FIG. 23, the cell tracking controller (100) can transmit the cell ID (CID) to the inspector (300) or measuring instrument (400).

[0729] The above inspection device (300) or measuring device (400) may be configured to map the cell ID (CID) to inspection data (ID) or measurement data corresponding to the cell ID (CID).

[0730] The generated mapping data can be transmitted to an upper server (500) (e.g., SPC). The SPC (540) can generate process monitoring data based on the mapping data.

[0731] In the FDC (520), high-frequency data (HFD) (feature data) mapped to the cell ID (CID) can be collected. In the SPC (540), inspection data (ID) or measurement data (MD) mapped to the cell ID (CID) can be collected.

[0732] Data collected in each subsystem (FDC, SPC) is mapped according to the same data collection standard (Cell ID (CID)). Therefore, by comparing at least one of the high-frequency data (HFD), inspection data (ID), and measurement data (MD) each mapped to the same Cell ID (CID), the impact of the high-frequency data (HFD) on the process can be determined. Specifically, the battery manufacturing system of the present disclosure can perform at least one of the following operations based on comparison data among at least one of the high-frequency data (HFD), inspection data (ID), and measurement data (MD) each mapped to the same Cell ID (CID).

[0733] 1) Generation of monitoring data based on comparison data

[0734] 2) At least one of process anomaly detection and anomaly alarm generation based on comparison data

[0735] 3) Generation of Correction Values ​​(CV) for Cell Manufacturing Process Related Parameters Based on Comparative Data

[0736] For the operations of 1) to 3) above, appropriate subsystems (e.g., FDC, SPC, APC, etc.) may be provided. For the operations of 1) to 3) above, data transmission and reception between subsystems may be possible wirelessly or via wired connection. For the operations of 1) to 3) above, a data warehouse (DW) capable of collecting and comprehensively analyzing data from the subsystems may be additionally provided.

[0737]

[0738] Figure 26 is an example of a battery manufacturing method.

[0739] The above manufacturing method includes the step (P210) of collecting a cell ID (CID), which is identification information of a battery cell (BC);

[0740] A step (P220) of collecting high-frequency data (HFD) generated as the process progresses for the battery cell (BC); and

[0741] It may include a step (P230) of mapping high-frequency data (HFD) corresponding to the cell ID (CID) to the cell ID (CID).

[0742] In the cell ID (CID) collection step (P210), the cell tracking controller (100) can collect the cell ID (CID) of a battery cell (BC) moving in the process. The cell tracking controller (100) can transmit the collected cell ID (CID) to a mapper (270).

[0743] In the high-frequency data collection step (P220), the data collection device (250) can collect high-frequency data (HFD) based on signals that fluctuate at high frequencies, such as vibrations or currents that occur as the process progresses. The data collection device (250) may include at least one high-frequency detection sensor (251) that detects high-frequency signals, and data collection hardware (252) that collects raw data of high-frequency data (HFD) by conditioning, converting, and processing the high-frequency signals. The data collection device (250) can transmit the raw data of high-frequency data (HFD) to a mapper (270).

[0744] In the cell ID mapping step (P230), data collected at the same time and / or same location in the process can be mapped to each other. For example, the mapper (270) can map cell IDs (CID) and high-frequency data (HFD) collected at the same time and / or same location.

[0745] The method may further include a step (P240) of compressing and / or sampling the raw data of the high-frequency data (HFD) to convert it into high-frequency feature data. The mapping device (270) may convert the raw data into feature data based on a predetermined conversion algorithm.

[0746] The above manufacturing method may further include the step (P250) of transmitting high-frequency feature data mapped to the cell ID (CID) to at least one upper server (500).

[0747] The mapping device (270) may be configured to collect high-frequency raw data for a first period during a first period and to transmit high-frequency feature data for a first period during a first period to an upper server (500). In this way, by periodically diagnosing the high-frequency feature data, mechanical defects occurring in the motor or drive unit can be detected early.

[0748] The above manufacturing method may further include a step (P260) of detecting whether there is an abnormality in the battery cell manufacturing process based on mapping data of the cell ID (CID) and high frequency data (HFD).

[0749] The upper server (500) that receives the mapping data can detect an abnormality in the battery manufacturing process or generate an abnormality detection signal based on the high-frequency feature data.

[0750] The above manufacturing method may further include the step of mapping at least one of the inspection data (ID) and measurement data of a battery cell (BC) corresponding to the cell ID (CID) to the cell ID (CID). A cell tracking controller (100) may collect the cell ID (CID) and transmit it to an inspector (300) or a measuring instrument (400). The inspector (300) or the measuring instrument (400) may map the cell ID (CID) to the collected inspection data (ID) or measurement data (MD). The inspector (300) or the measuring instrument (400) may transmit the mapped data to at least one upper server (500).

[0751] The above manufacturing method may further include the step of performing at least one of the following operations based on the high-frequency data (HFD) mapped to the cell ID (CID) and the comparison data of the inspection data (ID) or measurement data mapped to the same cell ID (CID) as the cell ID (CID).

[0752] 1) Generation of monitoring data based on comparison data

[0753] 2) At least one of process anomaly detection and anomaly alarm generation based on comparison data

[0754] 3) Generation of Correction Values ​​(CV) for Cell Manufacturing Process Related Parameters Based on Comparative Data

[0755]

[0756] FIGS. 27 and 28 are examples of a battery manufacturing system, and FIG. 29 is an example of a battery manufacturing method.

[0757] A battery manufacturing system (50) according to an exemplary embodiment may include a battery cell manufacturing process facility (EQ), a cell tracking controller (100), and a facility controller (200).

[0758] The equipment controller (200) may be configured to control the operation of the equipment. Since the process can be controlled by controlling the equipment, the equipment controller (200) is also referred to as a process controller. The equipment controller (200) may be an equipment PLC (Programmable Logic Controller).

[0759] The equipment controller (200) can control the transfer device (TD), processing mechanism, etc. The equipment controller (200) may be configured to generate signals for the operation and interruption of multiple equipment units, such as the transfer device (TD) and processing mechanism included in the equipment.

[0760] The equipment controller (200) may be configured to collect equipment data (ED) from the equipment of the battery cell manufacturing process. The equipment controller (200) may perform in operative communication with each equipment unit and each equipment sensor through a wired or wireless data network.

[0761] Equipment data (ED) acquired from each equipment sensor can be transmitted to the equipment controller (200). For example, a data storage such as a memory provided in the equipment controller (200) may have a location, i.e., an address, where the equipment data (ED) acquired by each sensor is stored. The equipment data (ED) acquired by each sensor can be stored at the address continuously or at predetermined time intervals.

[0762] The battery manufacturing system may include a position measuring device (410) for measuring the position of a battery cell (BC) moving during the process.

[0763] For example, the position measuring device (410) may be a rotary encoder installed in an unwinder or rewinder that moves the electrode sheet in a roll-to-roll process. The rotary encoder can sense the unwinding amount signal or winding amount signal of the electrode sheet and indicate the position value of each moving part of the electrode sheet. The unwinding amount signal and winding amount signal, or coordinate data which is the position of each moving battery cell (BC) (in this case, a part of the electrode sheet or a unit electrode) that is transmitted to the cell tracking controller (100), may be collected by the equipment controller (200), etc.

[0764] The above position measuring device (410) may be another position measuring sensor (e.g., a displacement amount sensing sensor, etc.) capable of detecting the movement of a battery cell (BC) in an LMS or conveyor device. Position values ​​in each process can also be obtained by the displacement amount sensing sensor, and based on these position values, the equipment controller (200) or cell tracking controller (100) of each process can collect position data.

[0765] The battery manufacturing system may also include a cell recognition device (430) capable of recognizing a battery cell (BC) moving during the process, a cell ID recognition device (420) capable of recognizing a cell ID (CID), or a cell ID marking device (421) capable of marking a cell ID.

[0766] The cell recognizer (430) may be configured to detect a battery cell (BC) and generate a cell detection signal (CDS). The cell recognizer (430) may be a vision camera, but is not limited thereto.

[0767] The cell ID recognizer (420) can detect the cell ID (CID) displayed on the battery cell (BC) and generate an ID recognition signal (IDS). The cell ID recognizer (420) may be a barcode reader (BCR), but is not limited thereto.

[0768] The cell detection signal (CDS) and / or cell ID recognition signal (IDS) can be transmitted to at least one of the facility controller (200) and the cell tracking controller (100).

[0769] The equipment controller (200) can control the equipment to perform a predetermined process on the corresponding battery cell (BC) based on a cell detection signal or a cell ID recognition signal.

[0770] The cell tracking controller (100) can acquire the cell ID (CID) of each battery cell (BC) moving in the process based on a cell ID recognition signal.

[0771] The cell tracking controller (100) can assign a virtual cell ID (VID) to each battery cell (BC) moving in the process based on a cell recognition signal.

[0772] A cell ID marking device (421) may be provided in a battery manufacturing system. The cell ID marking device (421) may assign a cell ID to a battery cell (BC) at a predetermined interval, for example, every pitch. A cell ID (CID) may be assigned based on electrode specification information and position information. For example, the cell ID marking device may assign a cell ID (CID) to a battery cell (BC) at a coordinate position acquired by a position measuring device (410) (e.g., a rotary encoder), corresponding to a predetermined interval detected by an electrode spacing sensor or a tap sensor.

[0773] The cell tracking controller (100) may be configured to collect a cell ID (CID), which is identification information of a battery cell (BC). The cell tracking controller (100) may be configured to map facility data (ED) corresponding to the cell ID (CID) to the cell ID (CID).

[0774] Referring to FIG. 28, the cell tracking controller (100) may include a cell ID collection unit (110), an equipment data collection unit (120'), and a cell ID mapping unit (130).

[0775] The cell tracking controller (100) may be a PLC (Programmable Logic Controller).

[0776] The cell tracking controller (100) may include any one of a simple controller, a complex processor such as a microprocessor, CPU, GPU, etc., a processor configured by software, dedicated hardware, and firmware.

[0777] The main control unit (CPU) of the cell tracking controller (100) may be equipped with a cell ID collection unit (110), an equipment data collection unit (120'), and a cell ID mapping unit (130). The cell tracking controller (100) may further include a data conversion unit (140) that converts the collected data into a form required by the upper server (500). The cell tracking controller (100) may be equipped with a communication interface (TIF) for transmitting and receiving data. For example, the cell tracking controller (100) may include an Ethernet communication interface (TIF) based on an Ethernet protocol that performs data transmission and reception through a LAN (local area network).

[0778] The cell ID collection unit (110) can be configured to collect the cell ID (CID), which is identification information of the battery cell (BC).

[0779] A cell ID recognizer (420) (e.g., BCR) may be configured to detect a barcode (e.g., data matrix) provided on a battery cell (BC) to generate a cell ID detection signal (IDS). The cell ID detection signal (IDS) generated based on the reading of the barcode may be transmitted to a cell tracking controller (100).

[0780] The cell ID collection unit (110) may include a cell ID detection unit that detects a cell ID (CID) collected in a communication interface (TIF) and a cell ID tracking unit that tracks the cell ID.

[0781] The cell ID detection unit can sequentially detect cell IDs received from the cell ID recognizer (420).

[0782] The cell ID tracking unit can track a moving battery cell (BC) as the battery cell manufacturing process progresses. A position measuring device (410) (e.g., a rotary encoder or a displacement sensor) may be provided to detect the position of the moving battery cell (BC). The cell ID tracking unit can identify the cell ID (CID) of the moving battery cell (BC) based on the position value transmitted from the position measuring device (410). As described above, the position of the moving battery cell (BC) during the process is reported to the equipment controller (200), and the equipment controller (200) can perform a predetermined process on the battery cell (BC) based on this. Likewise, the position of the moving battery cell (BC) during the process is reported to the cell tracking controller (100), and the cell tracking controller (100) can detect and track the cell ID (CID) of the battery cell (BC) based on this.

[0783] The position measuring device (410) can transmit the position value of the battery cell (BC) during the process to the cell tracking controller (100). Based on this, the cell tracking controller (100) can collect position data (e.g., coordinate data) of the battery cell (BC). The cell tracking controller (100) can collect the cell ID (CID) and the position data of the battery cell (BC) corresponding to the cell ID (CID), and match the cell ID (CID) corresponding to a specific battery cell (BC) with the coordinate data.

[0784] The cell ID collection unit (110) can collect the cell ID (CID) of a battery cell (BC) moving in the battery cell manufacturing process and transmit it to the cell ID mapping unit (130). Specifically, the cell ID tracking unit can track the cell ID (CID) of the battery cell (BC) moving according to the progress of the process for the battery cell (BC) and report it to the cell ID mapping unit (130).

[0785] The equipment data collection unit (120') can collect equipment data.

[0786] Equipment data (ED) generated from the process equipment (EQ) can be transmitted to an equipment controller (200) (e.g., an equipment PLC). The equipment data (ED) can be transmitted from the equipment controller (200) to a cell tracking controller (100). In some cases, the equipment data (ED) can be transmitted directly from the equipment to the cell tracking controller (100) without passing through the equipment controller (200).

[0787] The equipment data collection unit (120') provided in the cell tracking controller (100) can collect equipment data (ED) through a communication interface (TIF). The equipment data collection unit (120') can transmit the collected equipment data (ED) to the cell ID mapping unit (130).

[0788] The cell ID mapping unit (130) may be configured to map the collected equipment data (ED) to the cell ID (CID).

[0789] Referring to FIG. 28, the cell ID mapping unit (130) can receive the cell ID (CID) of the battery cell (BC) from the cell ID collection unit (110). The cell ID mapping unit (130) can receive equipment data (ED) from the equipment data collection unit (120').

[0790] For example, the cell ID mapping unit (130) can map cell IDs (CIDs) collected at the same time based on time and corresponding equipment data (EDs). However, if based on time, data collected at different locations at the same time may be mapped, which has the disadvantage of reduced data consistency. Therefore, it may be desirable to map cell IDs (CIDs) collected at the same location and corresponding equipment data (EDs) based on location values. The cell ID collection unit (110) can detect cell IDs (CIDs) and track cell IDs (CIDs) based on location values ​​(coordinate values) of each battery cell (BC) by linking with a location measuring device (410). The equipment controller (200) receives location values ​​(PVs) from the location measuring device (410). Therefore, the above location values ​​can be mapped to equipment data (EDs) acquired by multiple equipment units included in the equipment and equipment sensors installed in each unit.

[0791] In the present disclosure, the facility data (ED) corresponding to the cell ID (CID) may mean the cell ID (CID) and facility data (ED) acquired for the same battery cell (BC) in the process.

[0792] As disclosed in FIG. 28, the cell ID mapping unit (130) can map equipment data (ED) corresponding to the cell ID (CID) using the cell ID (CID) as a key.

[0793] The cell ID mapping unit (130) can store the mapped data in a predetermined memory device.

[0794] The above cell ID collection, data collection, and data mapping can be performed in real time. In the present disclosure, a controller (100) dedicated to data tracking, i.e., dedicated to cell ID tracking, is provided separately from the equipment controller (200) (process controller). According to the present disclosure, since the equipment controller (200) does not perform cell tracking functions and controls only the process equipment, almost no load for data tracking is applied to the equipment controller (200). Therefore, problems such as delays in the operation of the equipment controller (200) or operational errors can be prevented.

[0795] In addition, since data tracking is handled exclusively by a separate controller dedicated to cell ID tracking, namely the cell tracking controller (100), data processing such as data transmission and reception and mapping can be performed quickly. For example, compared to the case where process equipment control and data tracking are performed simultaneously by the equipment controller (200), it is evident that the data processing speed is much faster because the cell tracking controller (100) of the present disclosure performs only data tracking.

[0796] Therefore, the cell tracking controller (100) (e.g., cell tracking PLC) can perform cell ID collection, data collection, and data mapping in real time simply by applying a standard CPU, memory device, and interfaces.

[0797] Additionally, the cell tracking controller (100) may be configured to transmit mapped data to at least one upper server (500). The cell ID collection, data collection, data mapping, and data transmission may also be performed in real time.

[0798] The cell tracking controller (100) may further include a data conversion unit (140) that converts collected data into a form required by the upper server (500).

[0799] The data conversion unit (140) may be configured as a separate module from the CPU, i.e., a data conversion module. In order to reduce the resources or time required to convert data, the data conversion unit (140) may be configured as a separate data conversion module and included in the cell tracking controller (100).

[0800] As illustrated in FIG. 28, in a typical controller such as a PLC, data is displayed in the form of binary numbers of 0 and 1. Additionally, each subsystem (server), such as an FDC or MES, connects to the PLC and scans and retrieves the binary data. Each subsystem can convert the binary data into character data, specifically string data (text data).

[0801] However, since each subsystem has a different naming rule, the same data may be displayed with a different name.

[0802] If this happens, identical data introduced into each subsystem may be regarded as different data, making comparative analysis of data between subsystems difficult. Furthermore, from the user's perspective, identical data may be judged as different data, potentially causing confusion in process execution.

[0803] Therefore, instead of converting binary data into string data in the subsystem, it is necessary to convert the data in the cell tracking controller (100) so that the same data item name is provided to each subsystem.

[0804] In this embodiment, the data conversion unit (140) of the cell tracking controller (100) converts binary data into string data in a form required by the subsystem.

[0805] Generally, the primary role of a PLC's CPU is not data conversion. Therefore, when data is converted by the CPU, the conversion time may be long (e.g., more than 2 seconds), making real-time data processing difficult.

[0806] In this embodiment, a separate data conversion module from the CPU of the cell tracking controller (100) can be developed to facilitate real-time data processing. Binary-to-string data conversion can be performed by conversion software written in a specific programming language such as Python, or by hardware including conversion software.

[0807] By the above data conversion module, cell ID collection, data collection, data mapping, data conversion, and data transmission in the cell tracking controller (100) can be performed in real time.

[0808] In the present disclosure, data collection and mapping are performed in a separate cell tracking controller (100) from the facility controller (200) to reduce communication and data processing resources and increase the data processing speed, and a module dedicated to data conversion is provided so that data conversion can also be performed quickly.

[0809] Accordingly, all data processing in the cell tracking controller (100) can be performed in real time. Therefore, a real-time data processing environment can be provided to the battery cell manufacturing process and manufacturing system.

[0810] Referring to Fig. 28, a more detailed flow regarding data mapping and data transformation is described.

[0811] In the cell ID mapping unit (130), binary data mapped to a cell ID (CID) as a key can be stored in memory. Data preprocessing for string conversion can be performed on the stored mapping data.

[0812] After data preprocessing, a string conversion request can be transmitted from the cell ID mapping unit (130) to the data conversion unit (140). In the data conversion unit (140), the binary data mapped to the cell ID (CID) can be converted into string data according to the conversion request. The data conversion unit (140) can store the converted data in a transmission area for transmitting to the upper server (500).

[0813] Afterwards, the data mapping unit may issue a transmission command to the upper server (500) to the data conversion unit (140). By means of the transmission command, the data conversion unit (140) may transmit string data (CID / ED) mapped to a cell ID (CID) to the upper server (500).

[0814] The cell tracking controller (100) can collect location data of a virtual cell ID (VID) and a battery cell (BC) corresponding to the virtual cell ID (VID), and match coordinate data with a virtual cell ID (VID) corresponding to a specific battery cell (BC).

[0815] In the cell ID mapping unit (130), equipment data (ED) can be mapped to a virtual cell ID (VID).

[0816] The data conversion unit (140) can convert binary data mapped to a virtual cell ID (VID) into string data.

[0817] In accordance with the upper transmission command of the cell ID mapping unit (130), the data conversion unit (140) can transmit string data mapped to a virtual cell ID (VID) to at least one upper server (500).

[0818] The cell tracking controller (100) collects a virtual cell ID (VID) and location data of a battery cell (BC) corresponding to the virtual cell ID (VID), and location data of a battery cell (BC) corresponding to a physical cell ID, and can match coordinate data with a virtual cell ID (VID) and a physical cell ID (CID) corresponding to a specific battery cell (BC).

[0819] In the cell ID mapping unit (130), facility data (ED) can be mapped to at least one of the physical cell ID (CID) and the virtual cell ID (VID).

[0820] The data conversion unit (140) can convert binary data mapped to a cell ID (CID) into string data.

[0821] In accordance with the upper transmission command of the cell ID mapping unit (130), the data conversion unit (140) can transmit string data mapped to the cell ID to at least one upper server (500).

[0822] Data mapped to a cell ID (CID) may include a main key data set containing the cell ID (CID) and the source time at which the data signal was collected.

[0823] The main key data set may include at least one of a facility ID, a lot ID, a data collection unit ID, and location data indicating the location of the battery cell (BC) in the battery cell (BC) manufacturing process.

[0824] The facility ID may include information regarding factories, buildings, processes, manufacturing machinery, etc.

[0825] The lot ID may include the project name, product ID, process name, lot number of the electrode roll, etc.

[0826] The data collection unit ID may mean the ID of a data collection unit such as at least one equipment unit included in the inspection device (300), measuring instrument (400), and equipment (EQ).

[0827] The main key data set may further include data collection items. Data collection items may represent, for example, one or more data types or codes collected by each data collection unit.

[0828] The position data is data regarding the position of a battery cell (BC) in the battery manufacturing process. For example, coordinate data regarding the position of an electrode sheet moving in the electrode process can be used. The position data can be obtained by a position measuring device (410) as described above.

[0829] Multiple electrode lanes may be formed on a single current collector. The main key data set may also include information regarding the electrode lanes.

[0830] The main key data set must include a Cell ID (CID). The Cell ID (CID) may be a Physical Cell ID (CID), a Virtual Cell ID (VID), or both.

[0831] A data value can be mapped to a main key dataset containing a cell ID (CID). The data value may be an inspection value, a measurement value, or an equipment sensor value.

[0832] Mapping data may include the source time at which the data signal was collected.

[0833] The above Cell ID (CID) or Equipment Data (ED) may be time-series data. Time-series data may refer to data observed in chronological order. That is, each data point may be aligned chronologically. Each data point may be indexed by time. Each data point may be matched to the source time at which each data signal was collected.

[0834] Therefore, facility data (ED) can be mapped using the cell ID (CID) as the primary key and the source time as the sub-key.

[0835] Equipment data (ED) is mapped using a standardized parameter called the Cell ID (CID) as a key.

[0836] When a data set standardized by a cell ID (CID) is transmitted to multiple subsystems (upper server (500)), the data standards of each subsystem can be unified based on the cell ID (CID). Therefore, data analysis between each subsystem can be performed in an organically linked manner.

[0837] The standardized data set can be transmitted to at least one upper server (500).

[0838] As illustrated in FIG. 27, the battery manufacturing system may include at least one upper server (500).

[0839] The above upper server (500) can perform at least one of the following operations.

[0840] 1) Generation of monitoring data based on mapped data

[0841] 2) At least one of anomaly detection and anomaly alarm generation based on mapped data

[0842] 3) Generation of a correction value (CV) for the process progress condition (Recipe Parameter) of the equipment controller (200) based on the mapped data

[0843] For example, if the upper server (500) or subsystem is a Manufacturing Execution System (MES) (530) or a Statistical Process Control (SPC) (540), monitoring data regarding the battery cell manufacturing process can be generated based on mapped standardized data (set). For example, when a standardized data set is transmitted from the cell tracking controller (100) of each process to the MES or SPC, each upper server (500) can generate manufacturing-related monitoring data based on the standardized data set of each process.

[0844] Alternatively, for example, in the case of an FDC (Fault Detection & Classification) server (520), it may receive a standardized data set of each process from the cell tracking controller (100) of each process, detect anomalies from this data set, or issue an alarm for the detected anomalies. Anomalies may include data omissions, data delays, or cases where the value of each data falls outside a set range.

[0845] Alternatively, for example, an APC (Advanced Process Control) server (510) may receive a standardized data set of each process from a cell tracking controller (100) of each process. In this case, the APC may generate a correction value (CV) for the process progress condition (Recipe Parameter) of the equipment controller (200) based on the mapped data. The APC server transmits the correction value (CV) to the equipment controller (200) so that the equipment controller (200) can control the process based on the correction value (CV).

[0846] The standardized data set can also be transmitted to other subsystems other than the server exemplified above.

[0847] In addition, since each upper server (500) receives a standardized data set in real time, in process management, monitoring, anomaly detection, alarm generation, and correction value (CV) generation can be performed based on real-time data. Therefore, a real-time data collection and processing environment can be established throughout the entire battery manufacturing system by the cell tracking controller (100) of the present disclosure.

[0848] Referring again to FIG. 28, the equipment controller (200) may include an equipment data address (AD1) where equipment data (ED) is temporarily stored, and a cell tracking dedicated address (AD2). For example, the addresses may be provided in a register, which is a memory device that temporarily stores data necessary for the CPU of the equipment controller (200) to process a request.

[0849] The above equipment controller (200), specifically a processor such as a CPU equipped by the equipment controller (200), can execute a command to extract equipment data from the equipment data (ED) to be transmitted to the cell tracking controller (100). Additionally, the processor can execute a command to collect the equipment data extracted from the equipment data address (AD1) into the cell tracking dedicated address (AD2). Upon a request from the cell tracking controller (100), the processor can issue a command to transmit the extracted data collected in the cell tracking dedicated address (AD2) to the cell tracking controller (100). In this way, the equipment controller (200) can be configured to extract only the equipment data necessary for cell tracking. For example, it can be configured to collect only the equipment data necessary for generating a correction value (CV) in the APC (510) into the cell tracking dedicated address (A2). That is, if the extraction algorithm of the equipment controller is set to extract only the equipment data required for a specific purpose subsystem (server), data processing for cell tracking can be performed more efficiently.

[0850] Equipment data (ED) can be divided into equipment control data for controlling equipment (e.g., line speed data of a servo motor) and monitoring data (e.g., data regarding the pressure filter of a coating pump).

[0851] It may be reasonable to split the equipment data (ED) into equipment control data and monitoring data, and to transmit only the monitoring data to the cell tracking controller (100). In this case, since only the monitoring data is transmitted directly to the cell tracking controller (100), the load applied to each controller can be reduced and the data transmission speed can be increased.

[0852] A T branch module (210) can be applied for data branching.

[0853] Among the various equipment data (ED) transmitted to the equipment controller (200), monitoring data can be branched at the T-branch module (210) and transmitted to the cell tracking controller (100). The monitoring data can be transmitted directly to the cell tracking controller (100) without passing through the equipment controller (200).

[0854] The branched monitoring data can be mapped to a cell ID (CID) in the cell tracking controller (100) and transmitted to at least one upper server (500).

[0855] Data branching in the T branch module (210) can be performed using the so-called data mirroring technique, but is not limited thereto.

[0856] An example of a case where the T branch module (210) is applied can be a battery manufacturing system in which equipment data (ED) (monitoring data) is directly transmitted from the equipment to the cell tracking controller (100).

[0857] That is, the battery manufacturing system of the above embodiment is,

[0858] A cell tracking controller (100) configured to collect cell IDs (CID);

[0859] It may include equipment (EQ) of a battery cell manufacturing process equipped with at least one sensor that senses equipment data (ED).

[0860] The cell tracking controller (100) above may be configured to map facility data (ED) corresponding to the cell ID (CID) to the cell ID (CID).

[0861] FIG. 29 is a flowchart showing an example of a battery manufacturing method.

[0862] The battery manufacturing method of the present disclosure includes the step (P310) of collecting a cell ID (CID), which is identification information of a battery cell;

[0863] A step (P320) of collecting equipment data (ED) from a battery cell manufacturing process facility or an equipment controller (200) that controls the facility; and

[0864] It may include a step (P330) of mapping facility data (ED) corresponding to the collected cell ID (CID) to the cell ID (CID).

[0865] In the cell ID collection step (P310), the cell tracking controller (100) can collect a physical cell ID (CID) or a virtual cell ID (VID) of the battery cell manufacturing process. To collect the cell ID, the cell tracking controller (100) may include a cell ID collection unit (110). The cell ID collection unit (110) may include a cell ID detection unit and a cell ID tracking unit for detecting and tracking the cell ID. Alternatively, the cell ID collection unit (110) may include a virtual cell ID generation unit and a virtual cell ID tracking unit for generating and tracking the virtual cell ID (VID). Alternatively, the cell ID collection unit (110) may include a virtual cell ID generation unit, a virtual cell ID tracking unit, and a physical cell ID detection unit.

[0866] At least one of the cell ID and virtual cell ID (VID) collected by the cell ID collection unit (110) can be reported to the cell ID mapping unit (130).

[0867] In the equipment data collection step (P320), the equipment data (ED) of the battery cell (BC) can be collected.

[0868] Equipment data (ED) may be collected from a battery cell manufacturing process facility or an equipment controller (200) that controls the facility. The battery manufacturing method of the present embodiment may further include a step of branching the equipment data (ED) into equipment control data and monitoring data. For example, monitoring data may be branched from the equipment data (ED) by a T-branching module (210) and transmitted directly to a cell tracking controller (100) without passing through the equipment controller (200).

[0869] In the cell ID mapping step (P330), the equipment data (ED) can be mapped to the corresponding cell ID (CID).

[0870] Equipment data (ED) can be mapped to a Cell ID (CID) based on the time the data was acquired or the location data of the battery cell from which the data was acquired. The Cell ID (CID) corresponding to the collected data may be a Cell ID (CID) acquired at the same time or at the same location as the time the data was collected.

[0871] The cell ID mapping unit (130) of the cell tracking controller (100) can map equipment data to a cell ID (CID) and configure a standardized data set using the cell ID (CID) as a key.

[0872] The above cell ID (CID) collection, data collection, and data mapping can be performed in real time. Real time may be the time required for a battery cell to move from a first process location where a battery cell is located to a second process location, which is the location of the next battery cell preceding the battery cell.

[0873] The above manufacturing method may further include the step (P350) of transmitting mapped data to at least one upper server (500).

[0874] The above manufacturing method may further include a data conversion step (P340) prior to the data transmission step (P350), in which the mapped data is converted into data of a required form at the upper server (500).

[0875] In the data conversion step (P340), binary data mapped to the cell ID (CID) can be converted into string data. A dedicated module for data conversion may be provided in the cell tracking controller (100). By having the dedicated module perform the data conversion, the load applied to the CPU of the cell tracking controller (100) can be reduced, and the conversion operation can be performed quickly.

[0876] The above cell ID collection, data collection, data mapping, data conversion, and data transmission can be performed in real time.

[0877] A real-time data processing and transmission / reception environment can be implemented by the battery manufacturing method of this embodiment.

[0878] Since the battery manufacturing method of the present embodiment allows for easy tracking of a battery cell and data related to the battery cell, the battery manufacturing method may be described as a battery cell tracking method, or as a battery manufacturing method including the battery cell tracking method.

[0879]

[0880] Figure 30 is an example of a battery manufacturing system.

[0881] A roll map is a visual tool for efficiently representing an electrode sheet or electrode proposed by the applicant. The roll map can represent the electrode sheet (ES) based on coordinate values ​​representing a position on the electrode sheet (ES). The roll map may represent the history of processes performed on the electrode sheet (ES) and include data associated with the coordinates. Accordingly, the roll map enables the feedback control, feedforward control, and traceability of the manufacturing process of a secondary battery, as described below.

[0882] The electrode manufacturing process for secondary batteries involves a series of roll-to-roll processes. For feed-forward control, time-series data needs to be associated with the locations on real-world workpieces, parts, semi-finished products, and finished products. A roll map can associate time-series data with coordinate data containing coordinate values ​​representing the locations on real-world workpieces, parts, semi-finished products, and finished products. Based on the coordinate data, the roll map can provide a matching between the time-series data and the real-world workpieces, parts, semi-finished products, and finished products. Accordingly, the creation of a roll map and feed-forward control based on the roll map can improve productivity and quality by quantifying and objectifying process phases that previously relied on the operator's discretion. Furthermore, the roll map of a preceding lot can be used to improve the process for a subsequent lot, and this operation can be referred to as process feedback. Process feedback using a roll map may include identifying process conditions and process parameters that caused problems and defects based on the data contained in the roll map.

[0883] Furthermore, the roll map is generated cumulatively for the workpieces, parts, semi-finished products, and finished products of the above processes, thereby enabling the tracking of the process history for shipped products (e.g., battery cells (BC), battery modules, or battery packs). For example, a battery cell may include a Cell ID (CID) provided in a semi-finished product containing an electrode, such as a part of an electrode sheet, an electrode, or an electrode assembly, or a finished battery product containing an electrode. The Cell ID (CID) may include lot number and coordinate information of the electrodes and separators included in the battery cell. In other words, the Cell ID (CID) may be associated with the roll map of the electrodes and separators included in the battery cell. Accordingly, if an event such as a quality issue occurs in a battery cell that has already been shipped, the historical data of the manufacturing of the battery cell can be retrieved based on the Cell ID (CID).

[0884] Roll map data (roll map coordinates, inspection data (ID) or measurement data (MD) mapped to the roll map coordinates, etc.) was collected in the production management system (MES) via the equipment controller (200) of each process of the electrode process to generate a roll map. In addition, cell IDs (CID) generated in the notching process, etc., were mapped with other data in the equipment controller (200) of the notching process, etc., and collected in the cell ID management server (EDC) (550). The above roll map data and cell ID mapping data were finally linked (mapped) to each other at the top-level server (600).

[0885] However, in this battery manufacturing system, data is transferred through an equipment controller (200) for process management, and roll maps are generated in the production management system (530) of each process. As a result, a load is applied to the equipment controller (200) or the production management system (530) for process control, slowing down the data processing speed and causing delays in the control process of each process. In addition, since the data for process control and the data for battery cell tracking are processed in a single controller (equipment controller (200)) or system (MES) (530), it was difficult to perform the data processing for battery cell tracking quickly.

[0886] In addition, since coordinate correction was performed retrospectively only after the roll map data acquired from each process was uploaded to the subsystem (upper server), real-time data linkage and processing between multiple subsystems was difficult. In particular, the linkage between roll map data and cell ID (CID) was performed at the top-level server (600) (e.g., a data warehouse). At the top-level server (600), the collected data can be linked to track the cause of the problem retrospectively. However, the data loading cycle to the top-level server (600) is very long (e.g., several hours to several days), so problem response using data could not be performed quickly until the data was loaded into the top-level server (600).

[0887] The present disclosure is intended to provide a real-time data collection and processing environment in a battery manufacturing system.

[0888] The present disclosure is intended to provide a data hub device (350) between a plurality of process facilities and a plurality of upper servers (500). The data hub device (350) can acquire data generated in each process in real time and map the data acquired in each process between processes. The data hub device (350) can sort and / or integrate data from each process in real time, or collect sorted and / or integrated data in real time.

[0889] For example, the roll map data for each process generated by the MES (530) can be generated in the data hub device (350). Additionally, the cell ID mapping data collected by the EDC (550) can be generated in the data hub device (350). Accordingly, the MES, etc., can focus solely on the original process management, thereby improving the speed of process progress. Furthermore, real-time data of multiple processes and linkage data between each process can be generated in advance in the data hub device (350) before the data is loaded into the upper server (500) or the top server (600). Therefore, data can be processed quickly without waiting for the data to be loaded into the upper server (500) or the top server (600), thereby providing a real-time data collection and processing environment.

[0890] Referring to FIG. 30, the battery manufacturing system (60) of the present disclosure may include a plurality of equipment controllers (200: 201, 202, 203)) (e.g., equipment PLC), a data hub device (350), a plurality of upper servers (510, 520, 540) and a top server (500).

[0891] Although not shown in FIG. 30, at least one of an inspector (300) and a measuring instrument (400) may be provided for each process. A position measuring device (410) (LMS, conveyor, encoder, etc.) may be provided for each process.

[0892] At least one of the above-mentioned inspection device (300) and measuring device (400) can be linked with a position measuring device (410) to acquire at least one of inspection data (ID) and measurement data (MD) mapped to position data.

[0893] The above position data may be position data indicating the position of a battery cell (BC) that is part of an electrode sheet (ES) that moves during the process. Alternatively, it may be position data during the process of a battery cell (BC) that is an electrode cut to a predetermined standard size by the electrode sheet. Alternatively, it may be position data during the process of a battery cell that is a battery semi-finished product including the electrode, or a battery cell that is a battery finished product including the electrode. The above position data may be expressed in coordinates. In this case, the position data may be coordinate data (e.g., roll map coordinate data). The above position data may be expressed in a manner other than coordinates. For example, it may be indicated as a displacement amount that moves during the process. However, the method of expressing the position of the battery cell in the present disclosure is not limited thereto, and it is possible to express it in other ways as long as the position of the battery cell during the process can be appropriately expressed.

[0894] Inspection data (ID) or measurement data (MD) mapped to location data can be transmitted to the equipment PLC. In some cases, part of the inspection data (ID) or measurement data can be transmitted directly to the data hub device (350) without passing through the equipment PLC.

[0895] The equipment controller (200) can receive equipment data (ED) from the equipment. The equipment controller (200) can transmit the equipment data (ED) to the data hub device (350). The equipment controller (200) can acquire location data of a battery cell (BC) moving during the process from the location measuring device (410).

[0896] The facility controller (200) can obtain a physical cell ID (CID) from the cell ID recognizer (420). Alternatively, the facility controller (200) can assign a virtual cell ID (VID) to each battery cell (BC) based on the specifications (pitch) of the battery cell (BC).

[0897] In short, data generated from equipment (EQ), measuring instrument (400), and inspection device (300) can be transmitted to a data hub device (350) through an equipment controller (200) along with at least one of location data and a cell ID (CID). Since the data hub device (350) is located between the equipment controller (200) of the equipment unit and the subsystem (upper server (500)), it can be referred to as an intermediate hub device. Additionally, it can be referred to as an intermediate data hub device (350) in the sense that it links and maps data between multiple processes.

[0898] Based on data collected through the equipment PLC (201, 202, 203) of each process, the data hub device (350) can generate or collect a first data set (DS1) and a second data set (DS2).

[0899] The data hub device (350) is a data platform that integrates various data, processes it, and systematically manages it to create necessary information. The data hub device (350) can perform the functions of data collection and integration, data storage, data management, and data analysis. To perform the above functions, the data hub device (350) may include a database management system (DBMS), an ETL (Extract, Transform, Load) tool, a data lake, a data management solution, an analysis platform, an API, etc.

[0900] The data hub device (350) may be a physical server or a virtual server, or may include such a server. A virtual server is a server that operates like a physical server but can share hardware and software resources with other virtual servers through virtualization software. To virtualize a physical server, a software application must be added to a host system that divides server resources into multiple virtual servers. Each virtual server is isolated from other servers on the same host and can access memory, computing, and other resources while running its own OS (operating system). When a server is virtualized, server capacity can be utilized at a higher rate, and efficiency can be increased.

[0901]

[0902] FIG. 30 provides a data hub device (350) for mapping data acquired from a plurality of battery cell manufacturing processes between processes. The data hub device (350) may include a data collection unit (351, 352, 353) for each process.

[0903] Additionally, the data collection unit (351, 352, 353) of each process may each include a first data collection unit (351a, 352a, 353a) and a second data collection unit (351b, 352b, 353b). For convenience of illustration, the first data collection unit (352a) and the second data collection unit (352b) in the second process are shown in detail. However, the first data collection unit (351a) and the second data collection unit (351b) may also be provided in the first process. The first data collection unit (353a) and the second data collection unit (353b) may also be provided in the third process.

[0904] Although only three processes are illustrated as examples in FIG. 30, the data hub device (350) of the present disclosure can be applied to two, four, or more processes.

[0905] The above plurality of processes may each be a detailed process of the same system. For example, the first, second, and third processes may each be a detailed process of the electrode process. For example, the first, second, and third processes may each be a detailed process of the assembly process. For example, the first, second, and third processes may each be a detailed process of the packaging process. For example, the first, second, and third processes may each be a detailed process of the activation process. For example, the first, second, and third processes may each be a detailed process of the modularization process or the pack process.

[0906] The above multiple processes may include detailed processes of different systems.

[0907] For example, the first process may be a slitting process of the electrode process, and the second process may be a notching process of the assembly process.

[0908] In this embodiment, the data collection process will be explained focusing on the second process.

[0909] The first data collection unit (351a, 352a, 353a) of each process is configured to collect a first data set (1DS1, 2DS1, 3DS1) including at least one of the location data and cell ID (CID) of the battery cell (BC) of each process in real time from the start of each process. The present disclosure enables the real-time collection of data for each process by providing a dedicated data hub device (350) for data integration and tracking.

[0910] The first data set (1DS1, 2DS1, 3DS1) may include at least one of the location data and cell ID (CID) of each process, and process data of each process mapped to at least one of the location data and cell ID (CID). Specifically, the first data set (1DS1, 2DS1, 3DS1) may include at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) of each process mapped to at least one of the location data and cell ID (CID) of each process.

[0911] Specifically, the first data set (1DS1) of the first process may include at least one of the location data and cell ID of the first process, and at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) of each process that is mapped to at least one of the location data and cell ID (CID) of the first process.

[0912] The first data set (2DS1) of the second process may include at least one of the location data and cell ID of the second process, and at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) of each process that are mapped to the location data and cell ID (CID) of the second process.

[0913] The first data set (3DS1) of the third process may include at least one of the location data and cell ID of the third process, and at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) of each process that is mapped to at least one of the location data and cell ID (CID) of the third process.

[0914] Real-time may refer to the time required for a single battery cell to move from a first process location where a single battery cell is located, as described above, to a second process location, which is the location of the next battery cell preceding the single battery cell. That is, it may be the time (Tact Time) for one battery cell (BC) to move in each process. Whenever one battery cell (BC) moves (or is produced while moving) in each process, at least one of the location data and cell ID (CID) of that battery cell (BC) and data corresponding to at least one of the location data and cell ID (CID) may be matched. As the process progresses, one or more inspection data (ID) may sequentially correspond to at least one of the location data and cell ID (CID). As the process progresses, one or more measurement data (MD) may sequentially correspond to at least one of the location data and cell ID (CID). As the process progresses, one or more equipment data (ED) may sequentially correspond to at least one of the location data and cell ID (CID).

[0915] The mapping of at least one of the location data and cell ID (CID) with other data to configure the first data set (1DS1, 2DS1, 3DS1) can be performed by the equipment PLC. However, since the original purpose of the equipment PLC is process control, the data processing speed may be significantly slowed if the mapping of cell tracking data is also performed. For the same reason, it may be difficult to map at least one of the location data and cell ID (CID) with other data in real time by the equipment PLC. To perform real-time data mapping, a controller other than the equipment PLC may be provided, as described below.

[0916] Taking these points into consideration, as disclosed in the system (60) of FIG. 30, the equipment PLC is utilized only as a passage for each data, and real-time mapping of at least one of the location data and cell ID (CID) with other data can be performed in the first data collection unit (351a, 352a, 353a). The first data collection unit (351a, 352a, 353a) can collect a first data set (1DS1, 2DS1, 3DS1) by mapping the process data (inspection data (ID), measurement data, equipment data (ED)) corresponding to each battery cell (BC) to at least one of the location data and cell ID (CID) of each process whenever at least one of the location data and cell ID (CID) is transmitted from the equipment PLC (201, 202, 203) of each process.

[0917] The collection of the first data set (1DS1, 2DS1, 3DS1) can be performed based on a trigger event. When a trigger event occurs, for example, an API provided in the data hub device (350) can send a request to collect the first data set (DS1) to the first data collection unit (351a, 352a, 353a) of each process.

[0918] The trigger event for collecting the first data set (1DS1, 2DS1, 3DS1) may be the start of each process or the real-time elapsed time after the start of the process. The equipment PLC (201, 202, 203) of each process may transmit the signal for the start of each process or the signal for the real-time elapsed time after the start of the process to the data hub device (350).

[0919] According to the above trigger event, the first data collection unit (351a, 352a, 353a) of each process can collect real-time data at each time when, for example, one battery cell (BC) moves, and form a first data set (1DS1, 2DS1, 3DS1) which is a real-time data set of each process.

[0920]

[0921] The second data collection unit (351b, 352b, 353b) of each process is configured to collect the second data set (1DS2, 2DS2, 3DS2) of each process upon the completion of one battery cell in each process. In this case, the trigger event may be the completion of one battery cell in each process. When the trigger event occurs, for example, an API provided in the data hub device (350) may request the second data collection unit (120) to collect the second data set (DS2).

[0922] The second data collection unit (351b, 352b, 353b) of each process can collect a second data set (1DS2, 2DS2, 3DS2) by correcting at least one of the location data and cell ID (CID) of the battery cell (BC) in the first data set (1DS1, 2DS1, 3DS1) so as to correspond to at least one of the location data and cell ID (CID) of the battery cell (BC) completed in the previous process of each process. Since the second data set (1DS2, 2DS2, 3DS2) is also based on the first data set (1DS1, 2DS1, 3DS1), it may include at least one of the location data and cell ID (CID) of the battery cell (BC) and at least one of the inspection data (ID), measurement data, and equipment data (ED) mapped thereto.

[0923] The above data hub device (350) may further include a data storage unit in which the second data set (1DS2, 2DS2, 3DS2) of each process is stored.

[0924] The above second data collection unit (351b, 352b, 353b) is,

[0925] It can be configured to generate a second data set of each process by comparing a second data set of a previous process of each process with a first data set of each process.

[0926] For example, the second data collection unit (352b) of the second process can generate the second data set (2DS2) of the second process by comparing the second data set (1DS2) of the first process prior to the second process with the first data set (2DS1) of the second process.

[0927] The second data set (1DS2) of the first process can be obtained from the second data collection unit (351b) or data storage unit of the first process.

[0928] Due to the removal of an electrode sheet or electrode, or the removal of a battery semi-finished product or a battery finished product between the first and second processes, at least one of the location data and cell ID (CID) of a battery cell (BC) in the first process and at least one of the location data and cell ID (CID) of a battery cell (BC) identical to the battery cell (BC) in the second process may differ. For example, in the first process, cell IDs (CID) from #1 to #100 and the corresponding coordinate data of the battery cell (BC) can be acquired, and a second data set (1DS2) of the first process including the cell IDs (CID) and coordinate data can be obtained. However, if a battery cell (BC) with cell IDs (CID) of, for example, #1 to #5 is removed between the first and second processes, the cell IDs (CID) of the battery cell (BC) included in the first data set (2DS1) acquired sequentially in real time in the second process are recorded as #1 to #95. However, based on the second data set (1DS2) of the first process, the cell ID (CID) of the battery cell (BC) of the second process should actually be #6 to #100. When the second data collection unit (352b) of the second process receives a signal indicating the completion of the second process, it corrects at least one of the location data and cell ID (CID) of the battery cell (BC) in the first data set (2DS1) of the second process to correspond to at least one of the location data and cell ID (CID) of the battery cell (BC) included in the second data set (1DS2) of the first process. According to the correction, the cell ID (CID) of the battery cell (BC) included in the second data set (2DS2) of the second process is corrected to #6 to #100. Additionally, the location data of the battery cell (BC) can also be corrected to a value corresponding to the location data of the cell IDs #6 to #100.

[0929] Correction of the first data set (2DS1) of the second process may be performed by receiving correction information from the controller of the second process. For example, the performance of the battery cell (BC) completed in the first process (number of battery cells, length of electrode sheet, etc.) reported to the equipment PLC (201) of the first process may differ from the performance of the battery cell (BC) completed in the second process reported to the equipment PLC (202) of the second process. The controller of the second process (202) may derive the difference in performance of the battery cell (BC) between the first and second processes by referring to the performance information of the controller of the first process (201). The said difference in performance may correspond to correction information. The second data collection unit (352b) of the second process can correct at least one of the location data and cell ID (CID) of the battery cell (BC) of the first data set (2DS1) of the second process to correspond to at least one of the location data and cell ID (CID) of the battery cell (BC) of the first process by reflecting the correction information.

[0930] Meanwhile, if at least one of the position data and cell ID (CID) in the first process is reversed in the second process, at least one of the position data and cell ID (CID) of the first data set (DS1) in the second process can be corrected by referring to correction information related to the reversed position data. For example, if the first process and the second process are roll-to-roll processes, the positions of the starting and ending parts of the battery cell (BC) (e.g., electrode sheet) in the first process may be reversed in the second process. Alternatively, the corresponding surface of the electrode sheet may be reversed between processes depending on the winding direction of the electrode sheet in the first process and the unwinding direction of the electrode sheet in the second process. The second data collection unit (352b) of the second process above can correct at least one of the location data and cell ID (CID) of the battery cell (BC) in the first data set (2DS1) of the second process to correspond to at least one of the location data and cell ID (CID) of the battery cell (BC) included in the second data set (1DS2) of the first process by reflecting correction information regarding such start-end inversion and surface inversion. By comparing at least one of the location data and cell ID (CID) of the battery cell (BC) included in the second data set (1DS2) of the first process with at least one of the location data and cell ID (CID) of the battery cell (BC) included in the first data set (2DS1) of the second process, it is possible to determine whether the start-end inversion and surface inversion occurred between the first and second processes. That is, the second data collection unit (352b) of the second process can generate and collect the second data set (2DS2) of the second process by comparing the second data set of the first process with the first data set of the second process, thereby reflecting at least one change among the position data and cell ID (CID) due to battery cell removal, start-end inversion, and surface inversion.

[0931] The mechanism for correcting the first data set and generating the second data set described above can also be applied between the second process and the third process. That is, at the start of the third process, the first data collection unit (353a) of the third process can collect the first data set (3DS1) of the third process in real time. At the completion of one battery cell in the third process, the second data collection unit (353b) of the third process can correct the first data set (3DS1) of the third process to correspond to at least one of the location data and cell ID of the one battery cell completed in the second process, and collect the second data set (3DS2) of the third process. In this case, the second data collection unit (353b) of the third process can generate the second data set (3DS2) of the third process by comparing the second data set (2DS2) of the second process prior to the third process with the first data set (3DS1) of the third process.

[0932] Correction of the first data set (3DS1) of the third process may be performed by receiving correction information from the controller of the third process. For example, the performance of the battery cell (BC) completed in the second process reported to the equipment PLC (202) of the second process and the performance of the battery cell (BC) completed in the third process reported to the equipment PLC (203) of the third process may differ. The controller of the third process (203) may derive the difference in performance of the battery cell (BC) between the second and third processes by referring to the performance information of the controller (202) of the second process. The said difference in performance may correspond to correction information. The second data collection unit (353b) of the third process may correct at least one of the location data and cell ID (CID) of the battery cell (BC) in the first data set (3DS1) of the third process to correspond to at least one of the location data and cell ID (CID) of the battery cell (BC) in the second process by reflecting the said correction information.

[0933] The mechanism for collecting the first data set and generating the second data set by correcting the first data set is not limited to two consecutive processes. At the completion of each process, the first data set of each process can be corrected to correspond to at least one of the location data and cell ID from at least one of the multiple processes prior to each process, thereby generating / collecting the second data set. For example, the second data set of the third process can be generated to correspond to at least one of the location data and cell ID of the battery cell completed in at least one of the first and second processes. In this case, to generate the second data set of the third process, the second data set (1DS2, 2DS2) of the previous process, the first process or the second process, and the first data set (3DS1) of the third process can be compared. Alternatively, as described above, the second data set of the third process can be generated by reflecting the difference in performance between the previous process (the first process or the second process) and the current process (the third process) reported to the controller of the third process.

[0934] Referring to FIG. 30, the battery manufacturing system may further include at least one upper server (500). For example, an APC (510), FDC (520), and SPC (530) may be applied as the upper server (500), but are not limited thereto. For example, a VM (virtual machine) for performing other purposes / functions may also be an upper server.

[0935] The first data set (1DS1, 2DS1, 3DS1) (real-time data) of each process collected from the data hub device (350) can be transmitted to at least one upper server (500). Since the first data set (1DS1, 2DS1, 3DS1) represents data regarding battery cells (BC) collected in real time from each process, it can be used to generate a correction value (CV) for the process progress conditions of the equipment controllers (201, 202, 203) of each process based on the real-time data, for example, by an APC server (510), which is an upper server (500). Alternatively, it can be used by an FDC server (520) to detect process abnormalities or generate an abnormality alarm based on the real-time data. Alternatively, an MES or SPC (540) can generate monitoring data based on the real-time data.

[0936] The first data set (1DS1, 2DS1, 3DS1) of each process can be deleted after the second data set (1DS2, 2DS2, 3DS2) of each process is generated. The second data set (1DS2, 2DS2, 3DS2) is a final result data set mapped to the previous process after the completion of the battery cell in each process, allowing for an intuitive understanding of data changes between processes.

[0937] The second data set (1DS2, 2DS2, 3DS2) of each process collected from the data hub device (350) (data linked to or mapped with the previous process) can also be transmitted to at least one upper server (500).

[0938] The upper server (500) can generate monitoring data, detect anomalies and / or generate anomaly alarms, or generate a correction value (CV) for the process progress condition (Recipe Parameter) of the equipment controller (200) of each process based on the second data set (1DS2, 2DS2, 3DS2). Compared to the first data set (1DS1, 2DS1, 3DS1) (DS1) which reflects only real-time data of each process, the second data set (1DS2, 2DS2, 3DS2) can easily identify data changes between processes, so it may be more suitable for post-process data analysis by the upper server (500).

[0939] FIG. 31 is an example of a battery manufacturing system (70), and FIG. 32 is another example of a battery manufacturing system (80).

[0940] As described above, if the equipment controller (201, 202, 203) maps other data corresponding to at least one of the location data and cell ID (CID) as in FIG. 30, or collects data through the equipment controller (201, 202, 203), it may have an adverse effect on the control of each process and may be difficult to track the data of the battery cell (BC) in real time.

[0941] FIG. 31 shows a system provided with a roll map controller (205, 207, 209) for collecting location data and mapping the location data with other data.

[0942] A roll map controller (205, 207, 209) (e.g., a roll map PLC) may be configured to collect coordinate data of an electrode sheet or an electrode. For example, a roll map PLC may be provided for collecting coordinate data in a roll-to-roll process such as an electrode process, a notching process, or a lamination process. The roll map PLC may collect winding amount data or unwinding amount data based on a sensing signal from a rotary encoder that senses the amount of electrode sheet unwound by an unwinder or the amount of electrode sheet wound by a rewinder. The roll map PLC may be configured to collect coordinate data (position within the electrode sheet) of the electrode sheet (CD) based on either of the winding amount data or the unwinding amount data.

[0943] Additionally, the inspection device (300) or measuring device (400) of the roll-to-roll process can receive coordinate data from the roll map PLC and map at least one of the inspection data (ID) and the measuring data to the corresponding coordinate data. The mapped data can be transmitted to the roll map PLC. The roll map PLC can transmit the coordinate data and at least one of the mapping data among the inspection data (ID) and the measuring data to the data hub device (350). However, it may be difficult to transmit large-capacity equipment data (ED) through the roll map PLC. The equipment data (ED) can be transmitted to the data hub device (350) through the equipment PLC of each process or another relay server.

[0944] In the data hub device (350), the equipment data (ED) can be additionally mapped to at least one mapping data among the coordinate data, inspection data (ID), and measurement data to generate / collect a first data set (1DS1, 2DS1, 3DS1) and a second data set (1DS2, 2DS2, 3DS2). In this embodiment, since the roll map controller (205, 207, 209) provides at least one mapping data among the coordinate data, inspection data (ID), and measurement data (MD), the load on the equipment controller can be reduced. Additionally, since some data is introduced into the data hub device (350) in a mapped state, real-time mapping in the data hub device (350) becomes easier.

[0945] The system of Fig. 31 is characterized by providing a real-time data collection and processing environment by reducing the load of mapping operations based on at least location data.

[0946]

[0947] FIG. 32 illustrates a system in which data pre-mapped in a cell tracking controller (100) is collected in a data hub device (350).

[0948] As illustrated in FIGS. 8 to 14, the cell tracking controller (100:101,102,103) is a controller configured to collect at least one of inspection data (ID) and measurement data (MD) from at least one of an inspector (300) and a measuring instrument (400), collect equipment data (ED) from an equipment controller (201,202,203), and map the collected data to a cell ID (CID) in real time. The cell tracking controller (100:101,102,103) of each process can map at least one of the inspection data (ID), measurement data (MD), and equipment data (ED) to the cell ID (CID) of a battery cell (BC) moving in each process and transmit it to a data hub device (350). Additionally, the cell tracking controller (100:101,102,103) can add a position value (coordinate value or displacement amount) to the mapping data in conjunction with a position measuring device (410). The cell tracking controller (100:101,102,103) of each process can implement a main key set including a cell ID (CID) and a standardized data set including the source time at which the data signal was collected (see FIG. 15).

[0949] When data is fed into the data hub device in real time with the cell ID (CID) and location information mapped by the cell tracking controller (100:101,102,103) of each process, the data processing resources of the equipment PLC and the data hub device (350) can be significantly reduced. In addition, since the first data set (1DS1,2DS1,3DS1) can be collected in real time from the data hub device (350) in addition to real-time data collection, mapping, conversion, and transmission from the cell tracking controller (100:101,102,103) of each process, the real-time data collection and processing environment can be implemented more efficiently.

[0950] When a standardized data set is transmitted from the cell tracking controller (100:101,102,103) of each process to the data hub device (350), the first data collection unit (351a,352a,353a) of each process can generate and collect a first data set (1DS1,2DS1,3DS1) based on the standardized data set in real time.

[0951] The second data collection unit (351b, 352b, 353b) of each process can generate and collect a second data set (1DS2, 2DS2, 3DS2) by correcting at least one of the location data and cell ID (CID) of the battery cell (BC) of the first data set (1DS1, 2DS1, 3DS1) so as to correspond to at least one of the location data and cell ID (CID) of the battery cell (BC) completed in the previous process of each process when the battery cell is completed in each process.

[0952] In FIGS. 31 and 32, the transmission of the first and second data sets to the upper server (500) is the same as described in FIG. 30, so redundant descriptions are omitted.

[0953] The system of Fig. 32 is characterized by reducing the load of mapping operations based on at least one of cell ID (CID) and location data, thereby providing a real-time data collection and processing environment.

[0954]

[0955] FIG. 33 illustrates an example of a first data set (1DS1, 2DS1, 3DS1) and a second data set (1DS2, 2DS2, 3DS2).

[0956] FIG. 33(a) is an example of a first data set (1DS1, 2DS1, 3DS1) collected in real time by a first data collection unit (351a, 352a, 353a) based on trigger events of commencement of construction and real-time progress after commencement of construction.

[0957] The first data set (1DS1, 2DS1, 3DS1) may necessarily include the cell ID (CID) and coordinates (roll map coordinates) of each battery cell (BC) in each process. The first data set (1DS1, 2DS1, 3DS1) may include data values ​​(VALUE: equipment sensor value, inspection value, measurement value) mapped to the cell ID (CID) and coordinate values. The first data set (1DS1, 2DS1, 3DS1) may additionally include various data such as process site, process, equipment ID, ID of equipment unit included in the equipment, and ID of measuring instrument (400) / inspection instrument (300). The data in the first data set (1DS1, 2DS1, 3DS1) does not need to match 100% with the data in the standardized data set introduced from the cell tracking controller (100). However, at least one of the location data and the cell ID (CID) needs to be included in both data sets.

[0958] FIG. 33(b) is an example of a second data set (1DS2, 2DS2, 3DS2) that shows the second data collection unit (351b, 352b, 353b) correcting the first data set (1DS1, 2DS1, 3DS1) based on a trigger event of completion of a battery cell in each process.

[0959] For security reasons, the values ​​of each item in the first and second data sets have been left blank. However, a person skilled in the art would easily understand that the roll map coordinate values ​​and cell IDs (CIDs) of the first data set (1DS1, 2DS1, 3DS1) differ from the roll map coordinate values ​​and cell IDs (CIDs) of the corrected second data set (1DS2, 2DS2, 3DS2).

[0960]

[0961] Figure 34 is a flowchart showing a battery manufacturing method.

[0962] The above manufacturing method is intended to map data acquired from a plurality of battery cell manufacturing processes between processes.

[0963] The above manufacturing method may include a step (S420) of collecting a first data set (1DS1, 2DS1, 3DS1) containing at least one of the location data and cell ID (CID) of the battery cell (BC) of each process in real time from the start of each process.

[0964] The first data set (1DS1, 2DS1, 3DS1) may include at least one of inspection data (ID), measurement data, and equipment data (ED) mapped to at least one of location data and cell ID (CID). A data hub device (350) for collecting the first data set (1DS1, 2DS1, 3DS1) for data mapping may be provided. Mapping of at least one of location data and cell ID (CID) with other data may be performed at the data hub device (350) or may be performed in advance before the data hub device (350).

[0965] The roll map controller of each process can collect mapping data of location data and other data, and the cell tracking controller (100) of each process can provide mapping data of at least one of the cell ID (CID) and location data and other data in advance. In this case, a step (S410) of mapping at least one of inspection data (ID), measurement data, and equipment data (ED) in real time to at least one of the location data and cell ID (CID) of each process may be performed prior to the first data set (1DS1, 2DS1, 3DS1) collection step.

[0966] The operation of mapping at least one of inspection data (ID), measurement data, and equipment data (ED) in real time to at least one of the location data and cell ID (CID) of each process can be performed by the first data collection unit (351a, 352a, 353a) of the data hub device (350). The first data collection unit (351a, 352a, 353a) can collect data of each process and map the collected data in real time.

[0967] The first data collection unit (351a, 352a, 353a) can collect the first data set (DS1) based on the mapped data.

[0968] The above manufacturing method may include a step (S430) of collecting a second data set (1DS2, 2DS2, 3DS2) by correcting at least one of the location data and cell ID (CID) of the battery cell (BC) of the first data set (1DS1, 2DS1, 3DS1) so as to correspond to at least one of the location data and cell ID (CID) of the battery cell (BC) completed in the previous process of each process.

[0969] For collecting the second data set (1DS2, 2DS2, 3DS2), the data hub device (350) may include a second data collection unit (351b, 352b, 353b) that collects the second data set (1DS2, 2DS2, 3DS2) of each process.

[0970] In the step of collecting the second data set (1DS2, 2DS2, 3DS2), by comparing the second data set (1DS2, 2DS2, 3DS2) of the previous process of each process with the first data set (1DS1, 2DS1, 3DS1) of each process,

[0971] A second data set (1DS2, 2DS2, 3DS2) for each process can be generated.

[0972] Alternatively, in the step of collecting the second data set (1DS2, 2DS2, 3DS2), the second data set (1DS2, 2DS2, 3DS2) of each process can be generated by correcting the first data set (1DS1, 2DS1, 3DS1) of each process by reflecting the difference between the battery cell manufacturing performance of the previous process of each process and the battery cell manufacturing performance of each process.

[0973] Since the battery manufacturing method of the present embodiment maps data acquired from a plurality of battery cell manufacturing processes between processes, it can be described as a data mapping method, or as a battery manufacturing method including the data mapping method.

[0974]

[0975] The present invention has been described in more detail above through drawings and embodiments. However, the configurations described in the drawings or embodiments described in this specification are merely one embodiment of the present invention and do not represent all technical concepts of the present invention; therefore, it should be understood that various equivalents and modifications that can replace them may exist at the time of filing this application.

[0976] [Explanation of the symbol]

[0977] 10,10',10",10''': Battery manufacturing system

[0978] 20,30,40,50,60,70: Battery manufacturing system

[0979] BC: Battery cell

[0980] 100: Cell tracing controller

[0981] 200: Equipment Controller

[0982] 300: Checker

[0983] 400: Measuring instrument

[0984] 410: Positioning device

[0985] 420: Cell ID Recognizer

[0986] 421: Cell ID Marker

[0987] 430: Cell Recognizer

[0988] 500: Top Server

[0989] 510: APC

[0990] 520: FDC

[0991] 530: MES

[0992] 540: SPC

[0993] 550: EDC

[0994] 600: Top server

[0995] EQ: Equipment

[0996] TD: Transfer device

Claims

1. A cell ID collection unit configured to collect a cell ID, which is identification information of a battery cell; A data collection unit configured to collect at least one of inspection data of a battery cell, measurement data of a battery cell, and equipment data collected from equipment of a battery cell manufacturing process or from an equipment controller controlling said equipment; and It includes a cell ID mapping unit configured to map at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID, and A cell tracking controller configured to perform the above cell ID collection, data collection, and data mapping in real time.

2. In Paragraph 1, A cell tracking controller characterized in that the above battery cell comprises at least one of a part of an electrode sheet, an electrode formed by cutting the electrode sheet to a predetermined size, a battery semi-finished product including the electrode, and a battery finished product including the electrode.

3. In Paragraph 1, It is configured to transmit mapped data to at least one upper server, and A cell tracking controller configured to perform the above cell ID collection, data collection, data mapping, and data transmission in real time.

4. In Paragraph 3, It further includes a data conversion unit that converts the mapped data into a form required by the upper server, and A cell tracking controller configured to perform the above cell ID collection, data collection, data mapping, data conversion, and data transmission in real time.

5. In any one of paragraphs 1 through 4, A cell tracking controller characterized in that the above real-time is the time required for a battery cell to move from a first process position where a battery cell is located to a second process position, which is the location of the next battery cell preceding the battery cell.

6. In Paragraph 1, The above cell ID collection unit is, A cell ID detection unit that detects the cell ID of the above battery cell, and A cell tracking controller characterized by including a cell ID tracking unit that tracks the cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit.

7. In Paragraph 1, The above cell ID collection unit is, A virtual cell ID generation unit that generates a virtual cell ID corresponding to the above battery cell, and A cell tracking controller characterized by including a virtual cell ID tracking unit that tracks a virtual cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit.

8. In Paragraph 1, The above cell ID collection unit is, A virtual cell ID generation unit that generates a virtual cell ID corresponding to the above battery cell, and A virtual cell ID tracking unit that tracks the virtual cell ID of the battery cell moving according to the progress of the process for the battery cell and reports it to the cell ID mapping unit, and A cell tracking controller characterized by including a cell ID detection unit that detects the cell ID of the battery cell and reports the cell ID, or the cell ID and a virtual cell ID, to the cell ID mapping unit.

9. In Paragraph 1, The mapped data is, A main key data set including cell IDs, and A cell tracking controller characterized by including the source time at which the data signal was collected.

10. In Paragraph 9, The above main key data set is, A cell tracking controller characterized by including at least one of an equipment ID, a lot ID, a data collection unit ID, and location data indicating the location of a battery cell in a battery cell manufacturing process.

11. A cell tracking controller configured to collect cell IDs, which are identification information of battery cells; It includes at least one inspection device configured to collect inspection data of a battery cell, at least one measuring device configured to collect measurement data of a battery cell, and at least one equipment controller configured to collect equipment data from equipment of a battery cell manufacturing process. The above cell tracking controller is a battery manufacturing system configured to map at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID.

12. In Paragraph 11, It further includes a T-branching module that branches the above equipment data into equipment control data and monitoring data, and The above T branch module is a battery manufacturing system that transmits the above monitoring data directly to the cell tracking controller without passing through the above facility controller.

13. In Paragraph 11, The above equipment controller includes an equipment data address where equipment data is temporarily stored, and a cell tracking dedicated address. A battery manufacturing system configured such that the above-mentioned equipment controller extracts equipment data to be transmitted to a cell tracking controller from the above-mentioned equipment data, collects it in the above-mentioned cell tracking dedicated address, and transmits the collected data to the above-mentioned cell tracking controller.

14. A cell tracking controller configured to collect cell IDs, which are identification information of battery cells; It includes at least one of the equipment for a battery cell manufacturing process, comprising at least one inspection device configured to collect inspection data of a battery cell, at least one measuring device configured to collect measurement data of a battery cell, and at least one sensor configured to collect equipment data. The above cell tracking controller is a battery manufacturing system configured to map at least one of inspection data, measurement data, and equipment data corresponding to the cell ID to the cell ID.

15. In any one of paragraphs 11 through 14, The above cell tracking controller is, A battery manufacturing system characterized by transmitting mapped data to at least one upper server and being configured to perform cell ID collection, data collection, data mapping, and data transmission in real time.

16. In Paragraph 15, The cell tracking controller further includes a data conversion unit that converts the mapped data into a form required by the upper server. A battery manufacturing system characterized in that the cell tracking controller is configured to perform cell ID collection, data collection, data mapping, data conversion, and data transmission in real time.

17. In any one of paragraphs 11 through 14, A battery manufacturing system comprising at least one additional upper server that performs at least one of the following operations. 1) Generation of monitoring data based on mapped data 2) At least one of anomaly detection and anomaly alarm generation based on mapped data 3) Generation of correction values ​​for process conditions (Recipe Parameters) based on mapped data 18. A step of collecting a cell ID, which is identification information of a battery cell; A step of collecting at least one of inspection data of the battery cell, measurement data of the battery cell, and equipment data collected from equipment of the battery cell manufacturing process or equipment controller controlling the equipment; and The method includes the step of mapping at least one of inspection data, measurement data, and equipment data corresponding to the cell ID collected above to the cell ID, and A battery manufacturing method characterized by performing the above cell ID collection, data collection, and data mapping in real time.

19. In Paragraph 18, A battery manufacturing method further comprising the step of transmitting mapped data to at least one upper server.

20. In Paragraph 19, It further includes a data conversion step for converting the mapped data into a form required by the upper server, and A battery manufacturing method characterized by performing the above cell ID collection, data collection, data mapping, data conversion, and data transmission in real time.

21. In Paragraph 18, The above equipment data further includes a step of branching into equipment control data and monitoring data, A battery manufacturing method characterized by mapping the branched monitoring data above to the cell ID.

Images