Secondary battery manufacturing system

Abstract

According to an exemplary embodiment, a cell tracking data management method is provided. The method comprises the following steps that battery cell tracking data including unidentified roll core IDs and roll core IDs adjacent to the unidentified roll core IDs are loaded, the roll core IDs are used for distinguishing roll cores, and the roll cores are of a winding structure of a positive electrode, a negative electrode and a diaphragm; and recovering the unidentified roll core ID based on the roll core ID.

Description

TECHNICAL FIELD

[0001] This application claims the benefit of Korean Patent Application Nos. 2024-0005395, filed January 12, 2024, and 2024-0195585, filed December 24, 2024, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference.

[0002] Example embodiments of the present disclosure relate to a secondary battery manufacturing system. BACKGROUND

[0003] Unlike primary batteries, secondary batteries can be charged and discharged multiple times. Secondary batteries are widely used as energy sources for various wireless devices such as handheld devices, notebook computers, and wireless vacuum cleaners. Recently, as the manufacturing cost per unit capacity of secondary batteries is significantly reduced due to an increase in energy density and economies of scale, and the driving range of battery electric vehicles (BEVs) is improved to a level comparable to that of fuel vehicles, the main use of secondary batteries is shifting from mobile devices to the field of mobile travel.

[0004] Secondary batteries are manufactured through an electrode process, an assembly process, and an activation process. In order to improve the yield and reliability of the secondary battery manufacturing process, it is necessary to ensure traceability of the manufacturing process. Therefore, various studies are being conducted to ensure traceability of the secondary battery manufacturing process. SUMMARY

[0005] TECHNICAL PROBLEM

[0006] An object of the present disclosure is to provide a secondary battery manufacturing system with enhanced traceability.

[0007] TECHNICAL SOLUTION

[0008] According to an example embodiment of the present disclosure, an electrode tracking data management method is provided. The method includes loading electrode tracking data including an unidentified jelly-roll identification (ID) and a jelly-roll ID adjacent to the unidentified jelly-roll ID, wherein the jelly-roll ID is used to distinguish a jelly-roll that is a wound structure of a positive electrode, a negative electrode, and a separator, and recovering the unidentified jelly-roll ID based on the jelly-roll ID.

[0009] The jelly-roll ID can precede the unidentified jelly-roll ID.

[0010] The jelly-roll ID can follow the unidentified jelly-roll ID.

[0011] The core can be input into the assembly process of a secondary battery, and the core ID can include a symbol indicating the input order of the core, and the unrecognized core ID can be restored to a value in which the symbol indicating the input order of the core ID is changed.

[0012] The symbols can be changed to indicate the order of precedence.

[0013] The symbol can be changed to indicate a later order.

[0014] According to an example implementation, a cell tracking data management method is provided. The method includes: loading cell tracking data including an unidentified can ID and can IDs adjacent to the unidentified can ID, wherein the can IDs are used to distinguish cell housings for inserting cores, the cores being a wound structure of a positive electrode, a negative electrode, and a separator; and recovering the unidentified can IDs based on the can IDs, determining the can IDs by reading a data matrix of the cell housings, and the unidentified can IDs being determined by a failure to read the data matrix.

[0015] The can ID can precede the unidentified can ID.

[0016] The can ID can be after the unidentified can ID.

[0017] The cans can be input into the assembly process of secondary batteries, and the can ID can include a symbol representing the input order of the cell housing, and the unidentified can ID can be restored to a value in which the symbol representing the input order of the can ID is changed.

[0018] The symbols can be changed to indicate the order of precedence.

[0019] The symbol can be changed to indicate a later order.

[0020] According to an example implementation, a cell tracking data management method is provided. The method includes: loading a dataset for recovery, comprising first cell tracking data and second cell tracking data; recovering unidentified can IDs of the first cell tracking data based on the dataset for recovery; collecting the first cell tracking data from a first sub-device configured to perform a first sub-process of a battery cell assembly process; and collecting the second cell tracking data from a second sub-device configured to perform the battery cell assembly process, wherein the first and second cell tracking data include a plurality of can IDs, the can IDs being used to distinguish cell housings for inserting cores, the cores being a wound structure of a positive electrode, a negative electrode, and a separator; determining the can IDs by reading a data matrix of the cell housings; and determining unidentified can IDs by failure to read the data matrix.

[0021] The second sub-process can be performed after performing the first sub-process.

[0022] The second sub-process can be performed before performing the first sub-process.

[0023] The plurality of can IDs can include a first can ID before the unidentified can ID and a second can ID after the unidentified can ID, and the unidentified can ID can be recovered based on a portion of the second cell tracking data between the first can ID and the second can ID.

[0024] The unidentified can ID can be recovered as one of the plurality of can IDs of the second cell tracking data existing between the first can ID and the second can ID.

[0025] The unidentified can ID can be recovered based on one of the first can ID and the second can ID.

[0026] According to an example embodiment, an electric cell tracking data management method is provided. The method includes loading a data set for recovery including first electric cell tracking data and second electric cell tracking data, and recovering an unidentified can ID of the first electric cell tracking data and collecting the first electric cell tracking data from a first sub-device configured to perform a first sub-process of an assembly process of a battery cell, collecting the second electric cell tracking data from a second sub-device configured to perform a second sub-process of the assembly process of the battery cell, the first electric cell tracking data and the second electric cell tracking data including a plurality of can IDs used to distinguish a battery cell including a jelly-roll and a cell case, the jelly-roll being a wound structure of a positive electrode, a negative electrode, and a separator, the cell case being for insertion of the jelly-roll, the can ID being determined by reading a data matrix of the cell case, and the unidentified can ID being determined by a reading failure of the data matrix.

[0027] The second sub-process can be performed after performing the first sub-process.

[0028] The second sub-process can be performed before performing the first sub-process

[0029] According to an example embodiment, an electric cell tracking data management method is provided. The plurality of can IDs can include a first can ID before the unidentified can ID and a second can ID after the unidentified can ID, and the unidentified can ID can be recovered based on a portion of the second cell tracking data between the first can ID and the second can ID.

[0030] The unidentified can ID can be recovered as a batch ID existing between the first can ID and the second can ID among a plurality of batch IDs of the second cell tracking data.

[0031] According to an example embodiment, a cell tracking data management method is provided. The method includes configuring a first data window for recovery based on first cell tracking data and configuring a second data window for recovery based on second cell tracking data, and recovering an unidentified can ID of the first cell tracking data based on the second data window for recovery and collecting the first cell tracking data from a first sub-device configured to perform a first sub-process of an assembly process of a battery cell, collecting the second cell tracking data from a second sub-device configured to perform a second sub-process of the assembly process of the battery cell, the first cell tracking data and the second cell tracking data including a plurality of can IDs used to distinguish a battery cell including a jelly-roll and a cell case, the jelly-roll being a wound structure of a positive electrode, a negative electrode, and a separator, the cell case being for insertion of the jelly-roll, and generating the unidentified can ID when determination of the plurality of can IDs fails.

[0032] The second sub-process can be performed after the first sub-process is performed.

[0033] The second sub-process can be performed before the first sub-process is performed.

[0034] The first data window for recovery can include a first can ID and a second can ID, the first can ID being a first can ID among can IDs included in the first data window for recovery among the plurality of can IDs, the second can ID being a last can ID among can IDs included in the first data window for recovery among the plurality of can IDs, and the second data window for recovery can include can IDs among the plurality of can IDs between the first can ID and the second can ID.

[0035] The unidentified can ID of the first cell tracking data can be recovered based on matching the first cell tracking data with the can IDs among the plurality of can IDs included in the second data window for recovery.

[0036] The unidentified can ID of the first cell tracking data can be recovered based on a can ID not existing in the first cell tracking data among the can IDs among the plurality of can IDs included in the second data window for recovery.

[0037] Inventive Effects

[0038] The electric cell tracking data management method according to the example embodiment of the present disclosure can restore omitted electric cell tracking data. Accordingly, the manufacturing traceability of the secondary battery can be enhanced.

[0039] Effects obtainable from example embodiments of the present disclosure are not limited to what has been described herein above, and other effects which are not described herein will become apparent to those skilled in the art from the following description. In other words, example embodiments of the present disclosure are also capable of other effects and are obvious to those skilled in the art based on the following description. BRIEF DESCRIPTION OF DRAWINGS

[0040] Figure 1 is a flowchart illustrating a secondary battery manufacturing method according to an example embodiment.

[0041] Figure 2 is a block diagram illustrating a secondary battery manufacturing system according to an example embodiment.

[0042] Figures 3 to 12 is a diagram for explaining a secondary battery manufacturing method according to an example embodiment.

[0043] Figure 13 is a diagram for illustrating a method of managing data by a secondary battery manufacturing system according to an example embodiment.

[0044] Figure 14 is a diagram illustrating Figure 13 the roll diagram data.

[0045] Figure 15 is a flowchart illustrating an electric cell tracking data management method according to an example embodiment.

[0046] Figure 16 is a diagram illustrating an electric cell tracking data management method according to an example embodiment.

[0047] Figure 17 is a diagram illustrating an electric cell tracking data management method according to an example embodiment.

[0048] Figure 18 is a flowchart illustrating an electric cell tracking data management method according to an example embodiment.

[0049] Figure 19 is a diagram illustrating an electric cell tracking data management method according to an example embodiment.

[0050] Figure 20 is a diagram illustrating an electric cell tracking data management method according to an example embodiment.

[0051] Figure 21is a flowchart illustrating an electric chip tracking data management method according to an example embodiment.

[0052] Figure 22 is a diagram illustrating an electric chip tracking data management method according to an example embodiment.

[0053] Figure 23 is a flowchart illustrating an electric chip tracking data management method according to an example embodiment.

[0054] Figure 24 is a flowchart illustrating an electric chip tracking data management method according to an example embodiment.

[0055] Figure 25 is a flowchart illustrating an electric chip tracking data management method according to an example embodiment.

[0056] Figure 26 is a flowchart illustrating an electric chip tracking data management method according to an example embodiment.

[0057] Figure 27 is a flowchart illustrating an electric chip tracking data management method according to an example embodiment.

[0058] Figure 28 is a flowchart illustrating an electric chip tracking data management method according to an example embodiment. DETAILED DESCRIPTION

[0059] Hereinafter, example embodiments of the present disclosure are described in detail with reference to the accompanying drawings. Prior to this description, the words and terms used in the present disclosure should not be construed as being limited to common or dictionary meanings, but interpreted as meanings and concepts that are consistent with the principle of the present disclosure based on the concept that the inventor can properly define the terms to best explain the principle of the present disclosure.

[0060] Therefore, the example embodiments described in the present disclosure and the configurations shown in the accompanying drawings are only the most example embodiments of the present disclosure, and do not completely cover the technical idea of the present disclosure, and thus it should be understood that various equivalents and modified examples can exist as alternatives thereto at the time of filing the present application.

[0061] In addition, in describing the present disclosure, when it is determined that a detailed description of a related known configuration or function can obscure the gist of the present disclosure, a detailed description thereof will be omitted.

[0062] Since the example embodiments of the present disclosure are provided in order to more fully describe the present disclosure to those skilled in the art, for a clearer description, the shapes and sizes of the elements in the accompanying drawings can be exaggerated, omitted, or schematically shown. Therefore, the size or ratio of each element does not completely reflect the actual size or ratio.

[0063] (First and second examples)

[0064] Figure 1 FIG. 1 is a flowchart illustrating a secondary battery manufacturing method according to an example embodiment.

[0065] Figure 2 FIG. 2 is a block diagram illustrating a secondary battery manufacturing system 1000 according to an example embodiment.

[0066] Figures 3 to 12 FIG. 3 is a diagram for explaining a secondary battery manufacturing method according to an example embodiment.

[0067] Referring to Figure 1 and Figure 2 , the secondary battery manufacturing system 1000 can be configured to perform a secondary battery manufacturing process. Here, the secondary battery manufacturing process can include an electrode manufacturing process, an assembly process, and an activation process of a secondary battery. According to an example embodiment, the secondary battery manufacturing system 1000 can be configured to perform an assembly process of a secondary battery. For example, the secondary battery manufacturing system 1000 can be configured to perform an assembly process of a can-type battery (e.g., a prismatic battery or a cylindrical battery) or a pouch-type battery. The secondary battery manufacturing system 1000 can include a plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n, controllers 120a, 120b, 120c, and 120d, a processor 130, and a server 200. Figure 2 The number of the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n and the number of the controllers 120a, 120b, 120c, and 120d shown are for the purpose of explanation, and the present disclosure is not limited thereto.

[0068] The secondary battery manufacturing process can include a plurality of sub-processes, and each of the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n can be configured to perform one of the sub-processes (or one or more of the sub-processes).

[0069] The controllers 120a, 120b, 120c, and 120d can be configured to process the cell tracking data obtained from the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n. More specifically, the controller 120a can be configured to process the cell tracking data CTDa, CTDb, CTDc, and CTDd obtained from the controllers 113a, 113b, 113c, and 113d included in the plurality of sub-devices 110a, 110b, 110c, and 110d, respectively, and the controller 120b can be configured to process the cell tracking data CTDe, CTDf, and CTDg obtained from the controllers 113e, 113f, and 113g included in the plurality of sub-devices 110e, 110f, and 110g, respectively, and the controller 120c can be configured to process the cell tracking data CTDh, CTDi, and CTDj obtained from the controllers 113h, 113i, and 113j included in the plurality of sub-devices 110h, 110i, and 110j, respectively, and the controller 120d can be configured to process the cell tracking data CTDm and CTDn obtained from the controllers 113m and 113n included in the plurality of sub-devices 110m and 110n, respectively.

[0070] Figure 2 The number of the controllers 120a, 120b, 120c, and 120d and the allocation of the controllers 120a, 120b, 120c, and 120d to the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n shown in FIG. 1 are for illustrative purposes, and the present disclosure is not limited thereto. For example, the secondary battery manufacturing system 1000 can include a single controller that processes the cell tracking data obtained from the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n. In this case, the single controller can be configured to independently process the cell tracking data obtained from each of the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n.

[0071] The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to obtain a cell ID corresponding to the semi-finished cell based on the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn obtained from the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110l, 110m, and 110n. According to an example embodiment, the cell ID can be a virtual ID generated using data related to the semi-finished cell. For example, the controller (at least one of 120a, 120b, 120c, and 120d) can generate a virtual ID (e.g., a jelly-roll ID) of the semi-finished cell based on at least one of a tray ID, a tray coordinate, an electrode lot ID, and an electrode count of the tray loaded with the semi-finished cell (e.g., a jelly-roll). According to an example embodiment, the cell ID can be a representative ID for tracking the semi-finished cell in at least one sub-process before obtaining the holder ID in a sub-process to be described below. For example, when a carrier ID corresponding to the holder ID is obtained based on the process P40 of Figure 1 , the cell ID can be a jelly-roll ID generated based on the process P30 of Figure 1 . As another example, when a can ID corresponding to the holder ID is obtained based on the process P50 of Figure 1 , the cell ID can be a jelly-roll ID generated based on the process P30 of Figure 1 or a carrier ID obtained based on the process P40 of Figure 1 .

[0072] Here, the semi-finished cell can include various types of semi-finished cells manufactured during a manufacturing process performed on the secondary battery manufacturing system 1000. For example, in the case of a can-type battery manufacturing process, the semi-finished cell can be configured as a jelly-roll that is a wound structure of a positive electrode, a negative electrode, and a separator interposed therebetween, or a can-type battery cell in which the jelly-roll is inserted into a cell case. As another example, in the case of a pouch-type battery manufacturing process, the semi-finished cell can be configured as a unit cell composed of at least one electrode of a tape polarity (e.g., a positive electrode and / or a negative electrode) and a separator, a stacked electrode assembly formed by stacking a plurality of unit cells, a foldable electrode assembly formed by folding a plurality of unit cells, or a pouch-type battery cell in which the electrode assembly is inserted into a pouch. In this case, the unit cell can be configured as a half cell in which a positive electrode and a negative electrode are respectively located at both outermost unit cells, a double cell in which electrodes of the same polarity are located at both outermost sides, or a half cell in which a positive electrode or a negative electrode is located between separators at the outermost sides.

[0073] The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to obtain a holder ID corresponding to a holder in which a semi-finished battery cell is placed, based on cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn obtained from the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n.

[0074] Here, the holder can include various types of holders in which a semi-finished battery cell is placed during a manufacturing process performed on the secondary battery manufacturing system 1000. For example, in the case of a can-type battery manufacturing process, the holder can be configured as a carrier 115a or 115b on which a jelly-roll is placed or a cell case into which the jelly-roll is inserted. The carrier 115a or 115b can be a configuration for holding a jelly-roll in a specific sub-process P30, P40, and P50 for the jelly-roll. The cell case can be a configuration of a cylindrical battery cell, and can be a configuration in which a jelly-roll is inserted in a specific sub-process P50. As another example, in the case of a pouch-type battery manufacturing process, the holder can be configured as a box in which unit cells are stacked or a pouch into which a unit cell is inserted. The box can be a configuration that stacks and holds a plurality of unit cells to be stacked or folded before a stacking process or a folding process for forming an electrode assembly by stacking or folding a plurality of unit cells during an assembly process of a pouch-type battery, after a slotting process for forming an electrode tab on an electrode sheet of a unit cell and a lamination process for joining the unit cell to a separator. The pouch can be a configuration of a pouch-type battery cell, and can be a configuration in which a stacked cell or a folded cell is inserted in a packaging process.

[0075] The controller (at least one of 120a, 120b, 120c, and 120d) can obtain a cell ID and / or a holder ID by using various data included in the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn.

[0076] According to an example embodiment, the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn can include data for obtaining a cell ID and / or a holder ID. The cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn can include identification data identified by detecting a code object related to a semi-finished cell and / or a holder. For example, the identification data can include at least one of a tray ID identified by a code object on a tray on which a jelly-roll is placed, a carrier ID identified by a code object on a carrier on which the jelly-roll is loaded, and a can ID identified by a code object on a cell case into which the jelly-roll is inserted. Here, the code object can be a code image including information about an ID of a target detected and identified by a code reader (e.g., the matrix reader 111a, 111b, 111c, 111d, 111e, 111f, 111g, 111h, 111i, 111j, 111m, or 111n), and can be implemented as at least one of a data matrix, a QR code, and a bar code. Hereinafter, the present disclosure will be described focusing on an example embodiment in which a data matrix is used as a code object. However, this is for illustrative purposes, and the present disclosure is not limited thereto. In addition, the identification data can further include an electrode lot ID and an electrode count loaded by the plurality of sub-devices 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m, and 110n, in which the ID is identified as a trigger.

[0077] According to an example embodiment, the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn can include time data about a time at which the identification data is identified. The time data can be used for matching between a plurality of IDs.

[0078] The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match the obtained cell ID and the holder ID.

[0079] According to an example embodiment, the controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match a jelly-roll ID corresponding to a jelly-roll and a carrier ID corresponding to a carrier on which the jelly-roll is placed during a secondary battery manufacturing process. For example, the controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match the jelly-roll ID and the carrier ID based on jelly-roll tracking data JTDa obtained from the sub device 110a, the sub device 110a performing a sub-process of loading a jelly-roll to be placed on a tray onto the carrier 115a. Here, the jelly-roll tracking data JTDa can include time data about a time at which the jelly-roll ID is generated and a time at which the carrier ID is identified. The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match the jelly-roll ID and the carrier ID based on a time interval between the time at which the jelly-roll ID is generated and the time at which the carrier ID is identified.

[0080] According to an example embodiment, the controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match a plurality of carrier IDs corresponding to a plurality of carriers on which the same jelly-roll is loaded during a secondary battery manufacturing process. For example, the controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match a first carrier ID corresponding to the carrier 115a and a second carrier ID corresponding to the carrier 115b to each other based on jelly-roll tracking data JTDb obtained from the sub device 110b, the sub device 110b performing a sub-process of unloading a jelly-roll loaded onto the carrier 115a, loading the jelly-roll onto the carrier 115b, and coupling the jelly-roll loaded onto the carrier 115b to a lower insulator. Here, the jelly-roll tracking data JTDb can include time data about a first time at which the sub device 110b identifies the first carrier ID and a second time at which the sub device 110b identifies the second carrier ID. The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match the first carrier ID and the second carrier ID based on a time interval between the first time and the second time. The buffer (at least one of 120a, 120b, 120c, and 120d) of the controller can store a match between the jelly-roll ID based on the jelly-roll tracking data JTDa and the carrier ID corresponding to the carrier 115a. The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match the jelly-roll ID and the carrier ID corresponding to the carrier 115b based on the match stored in the buffer and the match between the first carrier ID and the second carrier ID based on the jelly-roll tracking data JTDb.

[0081] The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to obtain a can ID corresponding to a cell case in which a jelly-roll is inserted, based on the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn.

[0082] According to an example embodiment, the controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match a jelly-roll ID corresponding to a jelly-roll and a can ID corresponding to a cell case in which the jelly-roll is inserted during a secondary battery manufacturing process. For example, the controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match a carrier ID corresponding to a carrier 115b and a can ID based on the cell tracking data CTDc obtained from the sub device 110c that performs a sub-process of inserting a jelly-roll loaded on the carrier 115b into a cell case. Here, the cell tracking data CTDc can include time data about a third time at which the sub device 110c recognizes the carrier ID and a fourth time at which the sub device 110c recognizes the can ID. The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match the carrier ID and the can ID based on a time interval between the third time and the fourth time. The buffer of the controller (at least one of 120a, 120b, 120c, and 120d) can store a match between the jelly-roll ID based on the cell tracking data CTDa and CTDb and the carrier ID corresponding to the carrier 115b. The controller (at least one of 120a, 120b, 120c, and 120d) can be configured to match the jelly-roll ID and the can ID based on the match stored in the buffer and the match between the carrier ID and the can ID based on the cell tracking data CTDc.

[0083] According to an example embodiment, the controller (at least one of 120a, 120b, 120c, and 120d) can be configured to map IDs obtained from each sub-process with process data and / or inspection data obtained from a corresponding sub-process. Here, the process data can include information (e.g., a motor load value and a revolution per minute (RPM)) related to a device that performs a corresponding process and a time at which the corresponding process is performed. The inspection data can include measurement information obtained by scanning a size of a semi-finished product to be inspected, an image (e.g., an X-RAY image and a visual image) obtained by capturing the semi-finished product to be inspected, and state information of the semi-finished product inspected based on at least one of the measurement information and the image. The mapping can mean storing data linked to the ID so that the data serving as a value can be referenced by the ID serving as a key. In other words, when the ID is mapped with the process data and / or the inspection data, the process data and / or the inspection data can be referenced by the ID.

[0084] The manufacturing traceability of the secondary battery can be enhanced by the controller (at least one of 120a, 120b, 120c, and 120d) via the above-described operations to track the battery ID, process data, and inspection data of the semi-finished battery cell passing through each sub-process of the secondary battery manufacturing system 1000.

[0085] Hereinafter, a can-type battery manufacturing process is taken as an example of the secondary battery manufacturing process of the secondary battery manufacturing system 1000, and a method of matching at least two or more of the jelly-roll ID, the carrier ID, the can ID, and the lot ID and a method of mapping the ID with the process data in the plurality of sub-processes included in the can-type battery manufacturing process are specifically described. However, this is only an example for ease of description, and the cell tracking method of the present disclosure is not limited to the can-type battery manufacturing process and can also be applied to a pouch-type battery manufacturing process.

[0086] Reference Figures 1 to 3 In the process P10, the jelly-roll JR can be provided. The providing of the jelly-roll JR can include winding the positive electrode sheet PS, the negative electrode sheet NS, and the separator sheet SP, and cutting the positive electrode sheet PS, the negative electrode sheet NS, and the separator sheet SP so that the wound structure is separated. The positive electrode sheet PS can be unwound from the positive electrode roll by the unwinder 11, the negative electrode sheet NS can be unwound from the positive electrode roll by the unwinder 13, and the separator sheet SS can be unwound from the separator roll by the unwinders 15 and 17. The positive electrode sheet PS can include a positive electrode current collector and a positive electrode active material. The negative electrode sheet NS can include a negative electrode current collector and a negative electrode active material.

[0087] The thickness of the positive electrode current collector can be in the range of about 3 micrometers (㎛) to about 500㎛. The positive electrode current collector can not cause a chemical change in the finally manufactured secondary battery, and can have high electrical conductivity. The positive electrode current collector can include, for example, stainless steel, aluminum, nickel, titanium, calcined carbon, and aluminum. The positive electrode current collector can also include stainless steel surface-treated with carbon, nickel, titanium, or silver. The surface of the positive electrode current collector can include a fine uneven structure to increase the adhesion of the active material. The positive electrode current collector can have a shape such as a film, a sheet, a foil, a mesh, a porous material, a foam, or a nonwoven fabric.

[0088] The positive active material is a material that can cause an electrochemical reaction. The positive active material can be a lithium transition metal oxide. The positive active material can include, for example, a layered compound such as lithium cobalt oxide (LiCoO2) and lithium nickel oxide (LiNiO2) substituted with one or more transition metals, lithium manganese oxide substituted with one or more transition metals, lithium nickel-based oxide represented by the chemical formula LiNi1-yMyO2 (here, M is one of Co, Mn, Al, Cu, Fe, Mg, B, Cr, Zn, and Ga, and 0.01 ≤ y ≤ 0.7), lithium nickel cobalt manganese composite oxide represented by Li1+zNibMncCo1-(b+c+d)MdO(2-e)Ae (here, -0.5 ≤ z ≤ 0.5, 0.1 ≤ b ≤ 0.8, 0.1 ≤ c ≤ 0.8, 0 ≤ d ≤ 0.2, 0 ≤ e ≤ 0.2, and b + c + d < 1, M is one of Al, Mg, Cr, Ti, Si, and Y, and A is one of F, P, and Cl) (such as Li1+zNi1 / 3Co1 / 3Mn1 / 3O2 and Li1+zNi0.4Mn0.4Co0.2O2), and olivine-based lithium metal phosphate represented by the chemical formula Li1+xM1-yM'yPO4-zXz (here, M is a transition metal, more specifically, one of Fe, Mn, Co, and Ni, M' is one of Al, Mg, and Ti, X is one of F, S, and N, -0.5 ≤ x ≤ +0.5, 0 ≤ y ≤ 0.5, and 0 ≤ z ≤ 0.1).

[0089] The thickness of the negative current collector can be in the range of about 3㎛ to about 500㎛. The negative current collector can not cause a chemical change in the finally manufactured secondary battery, and can have high electrical conductivity. The negative current collector can include copper, stainless steel, aluminum, nickel, titanium, calcined carbon, and aluminum cadmium alloy. The negative current collector can also include stainless steel surface-treated with carbon, nickel, titanium, or silver. The surface of the negative current collector can include a fine uneven structure to increase the adhesion of the active material. The negative current collector can have a shape such as a film, a sheet, a foil, a mesh, a porous material, a foam, or a nonwoven fabric.

[0090] The negative active material can include, for example, carbon such as non-graphitizable carbon and graphite-based carbon. The negative active material can include, for example, metal complex oxides such as LixFe2O3(0≤x≤1), LixWO2(0≤x≤1), SnxMe1-xMe'yOz(where Me is one of Mn, Fe, Pb, and Ge, Me' is one of Al, B, P, Si, elements of Group 1, Group 2, or Group 3 of the periodic table, and halogen, 0

[0091] The positive tab PS, the negative tab NS, and the separator SP can be wound on the surface of the mandrel. The positive tab PS, the negative tab NS, and the separator SP can be wound by the rewinder 19. The jelly-roll JR can be provided such that the positive tab PS, the negative tab NS, and the separator SP are wound on the mandrel, are cut and are separated, and then the positive tab PT and the negative tab NT are welded to the separated wound structure. The positive tab PT can be welded to an uncoated portion of the positive electrode, and the negative tab NT can be welded to an uncoated portion of the negative electrode. The positive tab PT and the negative tab NT can be welded, for example, by ultrasonic welding, but are not limited thereto.

[0092] The processor 130 and / or the server 200 can be configured to obtain first process data and first inspection data corresponding to the process P10 for manufacturing the jelly-roll JR.

[0093] According to an example embodiment, the first process data can include at least one of information related to a device that performs the process P10 for manufacturing the jelly-roll JR (for example, tension information of the positive tab PS, the negative tab NS, and the separator SP and winding information of the rewinder 19) and a time at which the process P10 is performed.

[0094] According to an example embodiment, the first inspection data can include measurement information obtained by scanning measuring the size of the elements constituting the jelly-roll JR, images obtained by capturing the elements constituting the jelly-roll JR through a vision machine, and state information of the jelly-roll JR inspected based on at least one of the measurement information and the images. Here, the measurement information can include the size (e.g., thickness and width) of the positive electrode sheet PS, the negative electrode sheet NS, and the separator SP, the size (e.g., thickness and width) of the positive tab PT and the negative tab NT, the loading amount of the coating material on the electrode sheets PS and NS, the size (e.g., thickness and width) of the insulating material disposed on the coating material, the size (e.g., thickness and width) of the overlapping portion between the coating material and the insulating material, and information on the misalignment between the coating portion channel on the upper surface of the electrode sheets PS and NS and the coating portion channel on the lower surface of the electrode sheets PS and NS. The images can include appearance images of the positive electrode sheet PS, the negative electrode sheet NS, and the separator SP, and appearance images of the positive tab PT and the negative tab NT, which are captured and obtained through the vision machine. The state information can include the quality of the jelly-roll JR determined based on at least one of the measurement information and the images. For example, the state information can include at least one of information on whether there is a defect determined based on the size of the elements (e.g., the positive electrode sheet PS, the negative electrode sheet NS, the separator SP, the positive tab PT, the negative tab NT, the coating material, and the insulating material) constituting the jelly-roll JR and information on the defect type (e.g., pinhole defect, pit defect, line defect, crack defect, side ring defect, island defect, folding defect, wrinkle defect, indentation defect, and dent defect) determined based on the appearance images of the elements constituting the jelly-roll JR.

[0095] Subsequently, with reference to Figure 1 , Figure 2 and Figure 4 , in process P20, the jelly-roll JR can be loaded onto the tray 20. The jelly-roll JR can be placed on the tray 20 in rows and columns. Accordingly, the jelly-roll JR can be arranged in a matrix on the tray 20.

[0096] Subsequently, with reference to Figure 1 , Figure 2 , Figure 4 and Figure 5 , in process P30, the jelly-roll JR can be unloaded from the tray 20 and loaded onto the carrier 115a. The sub-device 110a can include a pick-and-place machine configured to move the jelly-roll JR on the tray 20 to the carrier 115a.

[0097] The sub-device 110a can include a data matrix reader 111a for reading the data matrix DM1 of the tray 20, a controller 113a, and the carrier 115a. The controller 113a can be configured to control the capturing of the data matrix reader 111a and the operation of the pick-and-place machine.

[0098] One of the data matrix readers 111a can be configured to detect the data matrix DM1 of the tray 20. When the reading of the data matrix DM1 is successful, the data matrix reader 111a can be configured to transmit a signal indicating the tray ID to the controller 113a. The tray ID can include a plurality of symbols for distinguishing and / or identifying the tray 20. The tray ID can be used to distinguish the tray 20. Here, the symbols can be collectively referred to as symbols, characters, and marks for representing a meaning.

[0099] The reading of the data matrix DM1 can include capturing an image including the data matrix DM1 and obtaining information included in the data matrix DM1 from the image. In addition, the reading of the data matrix DM1 can further include identifying the tray ID based on the information included in the data matrix DM1.

[0100] For example, the controller 113a can be configured to load the positive electrode batch ID and the positive electrode count from a server such as a manufacturing execution system (MES) as a trigger for the identification of the tray ID. As another example, the controller 113a can be configured to load the negative electrode batch ID and the negative electrode count from a server such as the MES as a trigger for the identification of the tray ID. Hereinafter, the present disclosure will be described focusing on an example embodiment of generating a jelly-roll ID using the positive electrode batch ID. However, this is for illustrative purposes and the present disclosure is not limited thereto in any sense. Here, the positive electrode count and the negative electrode count represent the order in which the jelly-roll is manufactured in the winding apparatus. The controller 113a can be configured to determine the coordinates of the jelly-roll JR on the tray based on the operation of the pick-and-place machine.

[0101] According to an example embodiment, the controller 113a can be configured to generate (or assign) the jelly-roll ID based on the positive electrode batch ID, the positive electrode count, the tray ID, and the tray coordinates. According to another example embodiment, the controller 113a can transmit cell tracking data CTDa including the positive electrode batch ID, the positive electrode count, the tray ID, and the tray coordinates to the controller 120a. The controller 120a can be configured to generate (or assign) the jelly-roll ID based on the transmitted cell tracking data CTDa. Here, the jelly-roll ID can correspond to a virtual ID generated based on required data, rather than being identified through data matrix detection.

[0102] Due to the characteristics of the semi-finished product, the jelly-roll JR can not include an actual data matrix. Accordingly, the jelly-roll ID assigned in the operation processed at the level of the jelly-roll JR can be generated and managed on a facility network or a factory automation network, and can be referred to as a virtual ID. According to an example embodiment, the jelly-roll ID can include the positive electrode batch ID, the positive electrode count, the tray ID, and the tray coordinates.

[0103] Here, when the roll core JR is input into the sub-device 110a according to the arrangement of the roll core JR on the tray 20, the symbol of the roll core ID representing the tray coordinates of the roll core ID can represent the input order of the roll core JR into the sub-device 110a. Since the sub-device 110a is the first stage of the assembly process, the input of the roll core JR into the sub-device 110a can also be referred to as the input of the roll core JR into the assembly process.

[0104] The controller 120a can transmit the roll core ID of the roll core JR to the processor 130 and / or the server 200. According to an example embodiment, the processor 130 and / or the server 200 can be configured to map the roll core ID obtained from the controller 120a with the first process data and the first inspection data of the roll core JR obtained in the process P10. For example, the processor 130 and / or the server 200 can be configured to map the electrode lot ID of the roll core JR with the first process data and the first inspection data, and map the roll core ID with the first process data and the first inspection data by the electrode lot ID used to generate the roll core ID. Another one of the data matrix readers 111a can be configured to detect the data matrix DM2a of the carrier 115a. Accordingly, the other data matrix reader can be configured to identify the carrier ID of the carrier 115a from the data matrix DM2a of the carrier 115a. The carrier ID of the carrier 115a can include a plurality of symbols for distinguishing and / or identifying the carrier 115a. The carrier ID can be used to distinguish the carrier 115a.

[0105] When the pick-and-place machine picks the roll core JR on the tray 20 and places the roll core JR on the carrier 115a, the data matrix DM1 of the tray 20 and the data matrix DM2a of the carrier 115a can be detected by the data matrix reader 111a of the sub-device 110a. The controller 113a can be configured to transmit the roll core ID to the controller 120a. The data matrix reader 111a can be configured to transmit the carrier ID of the carrier 115a to the controller 120a.

[0106] The controller 120a can be configured to collect cell tracking data CTDa of the sub device 110a. The cell tracking data CTDa can include data for obtaining a cell ID of a jelly roll JR. For example, the cell tracking data CTDa can include a jelly roll ID generated by the sub device 110a. In this case, the controller 120a can obtain the jelly roll ID by simply identifying the cell tracking data CTDa. As another example, the cell tracking data CTDa can include a positive electrode lot ID, a positive electrode count, a tray ID, and a tray coordinate for generating a jelly roll ID. In this case, the controller 120a can generate the jelly roll ID of the jelly roll JR based on the positive electrode lot ID, the positive electrode count, the tray ID, and the tray coordinate included in the cell tracking data CTDa. The cell tracking data CTDa of the sub device 110a can further include a carrier ID of the carrier 115a.

[0107] The cell tracking data CTDa can further include time data regarding a time of generating the jelly roll ID and a time of identifying the carrier ID from the data matrix DM1a of the carrier 115a. In addition, the cell tracking data CTDa can further include a time at which the carrier ID is matched with the jelly roll ID.

[0108] The controller 120a can be configured to match the carrier ID of the carrier 115a with the jelly roll ID of the jelly roll JR. According to an example embodiment, the controller 120a can be configured to match the jelly roll ID and the carrier ID by comparing a time of generating the jelly roll ID and a time of identifying the carrier ID based on the cell tracking data CTDa. For example, if a time interval between the time of generating the jelly roll ID and the time of identifying the carrier ID is within a preset threshold time value, the generated jelly roll ID and the identified carrier ID can be matched with each other. In contrast, if the time interval between the time of generating the jelly roll ID and the time of identifying the carrier ID exceeds the preset threshold time value, the generated jelly roll ID can be matched with another carrier ID whose time interval is within the threshold time value.

[0109] When reading of the data matrix DM1 fails, the data matrix reader 111a can be configured to generate an unidentified jelly roll ID. Accordingly, the cell tracking data CTDa can include the unidentified jelly roll ID. The unidentified jelly roll ID can be matched with the carrier ID of the carrier 115a.

[0110] The unidentified jelly roll ID can have a different generation rule (or format) from the jelly roll ID, such that the unidentified jelly roll ID can be easily distinguished from the jelly roll ID. As an example, a length of the unidentified jelly roll ID can be different from a length of the jelly roll ID.

[0111] Similarly, when reading of the data matrix DM2a fails, an unrecognized carrier ID can be matched with the roll core ID. The unrecognized carrier ID can have a different generation rule (or format) from the carrier ID, so that the unrecognized carrier ID can be easily distinguished from the carrier ID. As an example, the length of the unrecognized carrier ID can be different from the length of the carrier ID.

[0112] Subsequently, with reference to Figure 1 , Figure 2 , Figure 5 and Figure 6 , in the process P40, the lower insulator and the roll core JR can be coupled. The lower insulator can prevent an unwanted short circuit between the cell case CC (see Figure 6 described below and the roll core JR. The lower insulator and the roll core JR can be coupled by the sub device 110b.

[0113] The sub device 110b can include a data matrix reader 111b and a controller 113b. The controller 113b can be configured to control the capturing of the data matrix reader 111a and the operation of the device elements for coupling the lower insulator and the roll core JR.

[0114] The carrier 115a of the sub device 110a can be configured to transfer the roll core JR to the sub device 110b. The roll core JR can be moved from the carrier 115a of the sub device 110a to the carrier 115b of the sub device 110b, for example, by a pick-and-place machine.

[0115] The data matrix reader 111b can be configured to detect the data matrix DM2a of the carrier 115a and the data matrix DM2b of the carrier 115b. One of the data matrix readers 111b can be configured to detect the data matrix DM2a of the carrier 115a, and one of the data matrix readers 111b can be configured to detect the data matrix DM2b of the carrier 115b. When reading of the data matrices DM2a and DM2b is successful, the data matrix readers 111b can be configured to transmit a signal indicating the carrier IDs of the carriers 115a and 115b to the controller 120a. The controller 120a can identify the carrier IDs of the carriers 115a and 115b based on the transmitted signal. The carrier ID of the carrier 115b can include a plurality of symbols for distinguishing and / or identifying the carrier 115b. The carrier ID can be used to distinguish the carrier 115b.

[0116] The controller 120a can be configured to collect cell tracking data CTDb of the sub device 110b. The cell tracking data CTDb can include the vehicle IDs of the vehicles 115a and 115b. The cell tracking data CTDb can further include time data on a time at which the sub device 110b recognizes the vehicle ID of the vehicle 115a and a time at which the sub device 110b recognizes the vehicle ID of the vehicle 115b. In addition, the cell tracking data CTDb can further include a time at which the vehicle IDs of the vehicles 115a and 115b match each other. When reading of one of the data matrices DM2a and DM2b fails, the cell tracking data CTDb can include an unidentified cell ID.

[0117] The controller 120a can be configured to match the vehicle ID of the vehicle 115a and the vehicle ID of the vehicle 115b. According to an example embodiment, the controller 120a can be configured to match the vehicle IDs of the vehicles 115a and 115b to each other by comparing the recognition times of the vehicle IDs based on the cell tracking data CTDb. For example, if a time interval between the recognition times of the vehicle IDs is within a preset threshold time value, the recognized vehicle IDs can be matched to each other. In contrast, if the time interval between the recognition times of the vehicle IDs exceeds the preset threshold time value, each of the recognized vehicle IDs can be matched to another vehicle ID with which the time interval is within the threshold time value. Since the buffer of the controller 120a stores a match between the vehicle ID of the vehicle 115a and the cell ID of the cell JR, the controller 120a can be configured to match the cell ID of the cell JR to the vehicle ID of the vehicle 115b through the vehicle ID of the vehicle 115a.

[0118] The controller 120a can obtain second process data and second inspection data corresponding to the process P40 targeting the cell JR from the sub device 110b.

[0119] According to an example embodiment, the second process data can include at least one of information related to a device that performs the process P40 targeting the cell JR, a time at which the process P40 is performed, and information related to a lower insulator coupled to the cell JR.

[0120] According to an example embodiment, the second inspection data can include measurement information obtained by scanning to measure a size (e.g., thickness and width) of the lower insulator coupled to the cell JR, an image obtained by capturing the cell JR and the lower insulator with a vision machine, and state information of the cell JR and the lower insulator checked based on at least one of the measurement information and the image. Here, the state information can include at least one of information on whether the lower insulator is defective based on the size of the lower insulator and information on a defect type (e.g., a press-in defect in a lower portion of the cell JR and a defect in an inner or outer tab of an electrode of the cell JR) based on an appearance image of the cell JR and the lower insulator.

[0121] The controller 120a can be configured to map the obtained second process data and second inspection data with the carrier ID of the carrier 115b. Accordingly, the tracking of the second process data and the second inspection data can be provided based on the carrier ID and / or the jelly-roll ID mapped with the carrier ID.

[0122] Subsequently, referring to Figure 1 , Figure 2 and Figure 7 , in the process P50, the jelly-roll JR can be inserted into the cell case CC. The process P50 can also be referred to as a can insertion process. The jelly-roll JR can be inserted into the cell case CC by the sub device 110c. The battery case CC can be a metal can. The cell case CC can be, for example, one of a cylindrical can or a prismatic can. Hereinafter, the present disclosure is described focusing on an example embodiment in which the cell case CC is a cylindrical can. However, this is for illustrative purposes only, and the present disclosure is not limited to this in any sense. One of ordinary skill in the art can easily implement an example in which the cell case CC is a prismatic can based on what is described herein.

[0123] The carrier 115b of the sub device 110b can be configured to transfer the jelly-roll JR to the sub device 110c. The sub device 110c can include a data matrix reader 111c and a controller 113c. The controller 113c can be configured to control the capture of the data matrix reader 111c and the operation of the device elements for inserting the jelly-roll JR into the cell case CC.

[0124] The data matrix reader 111b can be configured to detect the data matrix DM2a of the carrier 115b and the data matrix DM3 of the cell case CC. When the reading of the data matrix DM2b is successful, the data matrix reader 111c can be configured to transmit a signal indicating the carrier ID of the carrier 115b to the controller 120a. The controller 120a can identify the carrier ID of the carrier 115b based on the transmitted signal. When the reading of the data matrix DM3 is successful, the data matrix reader 111c can be configured to transmit a signal indicating the can ID of the cell case CC to the controller 120a.

[0125] The can ID of the cell case CC can include a plurality of symbols for distinguishing and / or identifying the cell case CC. In other words, the can ID can include information for identifying the cell case CC. The can ID can be used to distinguish the cell case CC. The can ID can include symbols representing the coordinates of the cell case CC on the can tray. Accordingly, the can ID can include tray coordinates.

[0126] In general, the input order of the battery cell case CC can be determined based on the arrangement of the battery cell case CC on the can tray. In other words, when the battery cell case CC is input into the sub device 110c according to the arrangement of the battery cell case CC on the can tray, the symbol of the can ID representing the tray coordinates of the jelly roll ID can represent the input order of the jelly roll JR into the sub device 110a.

[0127] The controller 120a can be configured to collect battery cell tracking data CTDc of the sub device 100c. The battery cell tracking data CTDc can include a carrier ID of the carrier 115b and a can ID of the battery cell case CC. The battery cell tracking data CTDc can further include time data regarding a time at which the carrier ID of the carrier 115b is identified and a time at which the can ID of the battery cell case CC is identified by the sub device 110c. In addition, the battery cell tracking data CTDc can further include a time at which the jelly roll ID of the jelly roll JR and the can ID of the battery cell case CC are matched.

[0128] The controller 120a can be configured to match the carrier ID of the carrier 115b with the can ID of the battery cell case CC. According to an example embodiment, the controller 120a can be configured to match the carrier ID of the carrier 115b with the can ID of the battery cell case CC by comparing the identification times of the carrier ID and the can ID based on the battery cell tracking data CTDc. For example, if a time interval between the identification times of the carrier ID and the can ID is within a preset threshold time value, the identified carrier ID and the identified can ID can be matched with each other. In contrast, if the time interval between the identification times of the carrier ID and the can ID exceeds the preset threshold time value, the identified carrier ID can be matched with another can ID with which the time interval is within the threshold time value. When the buffer of the controller 120a stores a match between the carrier ID of the carrier 115a and the jelly roll ID of the jelly roll JR (or, a match between the carrier ID of the carrier 115b and the jelly roll ID of the jelly roll JR), the controller 120a can be configured to match the jelly roll ID of the jelly roll JR with the can ID of the battery cell case CC through the carrier ID of the carrier 115a (or the carrier ID of the carrier 115b).

[0129] The battery cell tracking data CTDc of the sub device 115c can further include the carrier ID of the carrier 115b matched with the jelly roll ID. When reading of the data matrix DM2b fails, the data matrix reader 111b can be configured to transmit an unidentified carrier ID to the controller 120a. The controller 120a can be configured to issue an unidentified jelly roll ID in response to receiving the unidentified carrier ID, and the battery cell tracking data CTDc can include the unidentified jelly roll ID.

[0130] When reading of the data matrix DM3 fails, the data matrix reader 111b can be configured to transmit an unidentified can ID to the controller 120a, and thus the cell tracking data CTDc can include the unidentified can ID.

[0131] Accordingly, some of the jelly-roll IDs of the jelly-roll JR can match the unidentified can ID, and some of the can IDs of the cell case CC can match the unidentified jelly-roll ID.

[0132] The controller 120a can obtain third process data and third inspection data corresponding to the process P50 targeting the jelly-roll JR from the sub-device 110c.

[0133] According to an example embodiment, the third process data can include at least one of information related to a device that performs the process P50 targeting the jelly-roll JR, a time at which the process P50 is performed, and information related to the cell case CC into which the jelly-roll JR is inserted.

[0134] According to an example embodiment, the third inspection data can include measurement information obtained by scanning to measure a size of the cell case CC, an image obtained by capturing the cell case CC with a vision machine, and state information of the cell case CC inspected based on at least one of the measurement information and the image. Here, the state information can include at least one of information on whether the cell case CC is defective based on the size of the cell case CC and information on a type of defect (e.g., an opening defect) based on an appearance image of the cell case CC.

[0135] The controller 120a can be configured to map the obtained third process data and third inspection data with the can ID of the cell case CC. Accordingly, tracking of the third process data and the third inspection data can be provided based on at least one of the can ID, the carrier ID mapped with the can ID, and the jelly-roll ID. Further, history data for providing a semi-finished product of the battery cell BC (see Figure 12 ) can be collected based on the data matrix on the cell case CC, and tracking of the secondary battery manufacturing process can be provided.

[0136] Hereinafter, processes P60 to P180 in which the cell case CC into which the jelly-roll JR is inserted is input in the secondary battery manufacturing process will be described.

[0137] Subsequently, in the process P60, a negative terminal of the jelly-roll JR (see Figure 3 ) and a negative terminal of the cell case CC can be welded. The process P50 can also be referred to as a negative tab welding process. The tab welding process can be resistance welding. The welding can be performed by applying a current to the negative tab NT (see Figure 3) and the negative terminal of the battery cell case CC, and applies voltage (or current) therebetween, and the negative tab NT (see Figure 3 ) of the jelly-roll JR can be fusion welded. The negative tab NT (see Figure 3 ) of the jelly-roll JR can be welded to the negative terminal of the battery cell case CC by the sub device 110d.

[0138] The sub device 110d can include a data matrix reader 111d and a controller 113d. The controller 113d can be configured to control the capturing of the data matrix reader 111d and the operation of the device element for welding the negative tab NT (see Figure 3 ) of the jelly-roll JR to the negative terminal of the battery cell case CC.

[0139] The data matrix reader 111d can be configured to detect the data matrix DM3 of the battery cell case CC. When the reading of the data matrix DM3 is successful, the data matrix reader 111d can be configured to transmit a signal indicating the can ID of the battery cell case CC to the controller 120a. The controller 120a can identify the can ID of the battery cell case CC based on the transmitted signal.

[0140] The controller 120a can be configured to collect the battery cell tracking data CTDd of the sub device 110d. The battery cell tracking data CTDd can include the can ID of the battery cell case CC. The battery cell tracking data CTDd can further include time data about the time at which the sub device 110d identifies the can ID of the battery cell case CC. In addition, the battery cell tracking data CTDd can further include the time matching the can ID of the battery cell case CC. When the reading of the data matrix DM3 fails, the battery cell tracking data CTDd of the sub device 110d can include the unidentified can ID of the battery cell case CC.

[0141] Subsequently, in the process P70, a swaging process can be performed on the battery cell case. The sub device 110d can further include a swaging tool configured to perform the swaging process on the battery cell case CC. In the swaging process, the upper portion of the battery cell case CC can be compression molded to reduce its outer diameter. Here, the upper portion of the battery cell case CC can include an opening into which the jelly-roll JR is inserted. A stepped portion can be formed on the battery cell case CC during the swaging process.

[0142] The controller 120a can obtain, from the sub device 110d, fourth process data and fourth inspection data corresponding to the processes P60 and P70 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted).

[0143] According to an exemplary embodiment, the fourth process data can include at least one of information related to equipment performing processes P60 and P70 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted), a time at which the processes P60 and P70 are performed, and information related to set values used in the processes P60 and P70 (e.g., a pressure applied to the negative terminal of the battery cell case CC, an applied voltage (or current), a welding position, a welding pass, and swaging die information).

[0144] According to an exemplary embodiment, the fourth inspection data can include measurement information obtained by scanning to measure the size of the battery cell case CC, an image obtained by capturing the battery cell case CC with a vision machine, and state information of the battery cell case CC inspected based on at least one of the measurement information and the image. Here, the image can include at least one of an appearance image of the jelly-roll JR captured and obtained with the vision machine before the negative tab NT process is performed, an appearance image of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) captured and obtained with the vision machine after the negative tab NT process is performed, and an appearance image of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) captured and obtained with the vision machine after the swaging process is performed. The state information can include at least one of information on whether the battery cell case CC is defective based on the size of the battery cell case CC and information on a type of defect (e.g., a hole coverage defect in the jelly-roll JR, a press-in defect in the jelly-roll JR, and a defect in the negative tab NT) based on the appearance image of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted).

[0145] The controller 120a can be configured to map the obtained fourth process data and fourth inspection data to the can ID of the battery cell case CC. Accordingly, tracking of the fourth process data and the fourth inspection data can be provided based on at least one of the can ID, the carrier ID mapped to the can ID, and the jelly-roll ID.

[0146] Subsequently, in the process P80, an upper insulator can be inserted into the battery cell case CC. The upper insulator can prevent an undesired short circuit between the cap assembly CA (see Figure 9 ) described below and the jelly-roll JR.

[0147] The sub-equipment 110e can include a data matrix reader 111e and a controller 113e. The controller 113e can be configured to control capturing of the data matrix reader 111e and operation of an element of equipment for insertion of the upper insulator.

[0148] The data matrix reader 111e can be configured to detect the data matrix DM3 of the battery cell case CC. When the reading of the data matrix DM3 is successful, the data matrix reader 111e can be configured to transmit a signal indicating the can ID of the battery cell case CC to the controller 120b. The controller 120b can identify the can ID of the battery cell case CC based on the transmitted signal.

[0149] The controller 120b can be configured to collect battery cell tracking data CTDe of the sub device 110e. The battery cell tracking data CTDe can further include time data regarding a time at which the sub device 110e identifies the can ID of the battery cell case CC. In addition, the battery cell tracking data CTDe can include the can ID of the battery cell case CC. The battery cell tracking data CTDe can further include a time matching the can ID of the battery cell case CC. When the reading of the data matrix DM3 fails, the battery cell tracking data CTDe can include an unidentified can ID of the battery cell case CC.

[0150] The controller 120b can obtain, from the sub device 110e, fifth process data and fifth inspection data corresponding to the process P80 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted).

[0151] According to an example embodiment, the fifth process data can include at least one of information related to a device that performs the process P80 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted), a time at which the process P80 is performed, and information related to the upper insulation coupled to the jelly-roll JR.

[0152] According to an example embodiment, the fifth inspection data can include measurement information obtained by scanning a size (e.g., thickness and width) of the upper insulation inserted into the battery cell case CC, an image obtained by capturing the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) and the upper insulation with a vision machine, and state information of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) and the upper insulation checked based on at least one of the measurement information and the image. Here, the state information can include at least one of information regarding whether the upper insulation is defective based on a size of the upper insulation and information regarding a type of defect based on an appearance image of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) and the upper insulation.

[0153] The controller 120b can be configured to map the obtained fifth process data and fifth inspection data with the can ID of the battery cell case CC. Accordingly, tracking of the fifth process data and the fifth inspection data can be provided based on the carrier ID and / or the jelly-roll ID mapped with the carrier ID.

[0154] Subsequently, in process P90, a recess can be formed in the cell case CC. The recess can be used to seat a grommet to be described below. Process P90 can be referred to as crimping. The recess of the cell case CC can be formed by sub device 110f.

[0155] Sub device 110f can include data matrix reader 111f and controller 113f. Controller 113f can be configured to control the operation of data matrix reader 111f and a recess forming tool on cell case CC.

[0156] Data matrix reader 111f can be configured to detect data matrix DM3 of cell case CC. When reading of data matrix DM3 is successful, data matrix reader 111f can be configured to send a signal indicating the can ID of cell case CC to controller 120b. Controller 120b can identify the can ID of cell case CC based on the sent signal.

[0157] Controller 120b can be configured to collect cell tracking data CTDf of sub device 110f. Cell tracking data CTDf can further include time data on the time at which sub device 110f identifies the can ID of cell case CC. In addition, cell tracking data CTDf can include the can ID of cell case CC. Cell tracking data CTDf can further include the time matching the can ID of cell case CC. When reading of data matrix DM3 fails, cell tracking data CTDf can include an unidentified can ID of cell case CC.

[0158] Controller 120b can obtain, from sub device 110f, sixth process data and sixth inspection data corresponding to process P90 targeting the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted).

[0159] According to an example embodiment, the sixth process data can include at least one of information related to a device that performs process P90 targeting the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted), a time at which process P90 is performed, and information related to the recess formed in the cell case CC (e.g., a target shape and size of the recess and a number of recesses).

[0160] According to an example embodiment, the sixth inspection data can include an image obtained by capturing the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted) by a vision machine and state information of the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted) inspected based on the image. Here, the state information can include information on a defect type (e.g., a recess defect) determined based on an appearance image of the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted).

[0161] The controller 120b can be configured to map the obtained sixth process data and sixth inspection data with the can ID of the battery cell case CC. Accordingly, tracking of the sixth process data and the sixth inspection data can be provided based on the carrier ID and / or the jelly-roll ID mapped with the carrier ID.

[0162] Subsequently, in the process P100, an X-RAY inspection can be performed on the battery cell case CC. The X-RAY inspection can be performed by the sub device 110g. The arrangement of the electrode and defects can be checked by the X-RAY inspection.

[0163] The sub device 110g can include a data matrix reader 111g and a controller 113g. The controller 113g can be configured to control the capturing of the data matrix reader 111g and the operation of the X-RAY based inspection machine.

[0164] The data matrix reader 111g can be configured to detect the data matrix DM3 of the battery cell case CC. When the reading of the data matrix DM3 is successful, the data matrix reader 111g can be configured to transmit a signal indicating the can ID of the battery cell case CC to the controller 120b. The controller 120b can identify the can ID of the battery cell case CC based on the transmitted signal.

[0165] The controller 120b can be configured to collect battery cell tracking data CTDg of the sub device 110g. The battery cell tracking data CTDg can further include time data regarding the time at which the sub device 110g identifies the can ID of the battery cell case CC. In addition, the battery cell tracking data CTDg can include the can ID of the battery cell case CC. The battery cell tracking data CTDg can further include the time matching the can ID of the battery cell case CC. When the reading of the data matrix DM3 fails, the battery cell tracking data CTDg can include an unidentified can ID of the battery cell case CC.

[0166] The controller 120b can obtain, from the sub device 110g, seventh process data and seventh inspection data corresponding to the process P100 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted).

[0167] According to an example embodiment, the seventh process data can include at least one of information related to a device performing the process P100 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) and a time at which the process P100 is performed.

[0168] According to an example embodiment, the seventh inspection data can include an X-RAY image of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) and state information of the electrode checked based on the X-RAY image. Here, the state information can include a defect type (e.g., electrode arrangement defect, size defect, and electrode tab misalignment) determined based on the X-RAY image of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted).

[0169] The controller 120b can be configured to map the obtained seventh process data and seventh inspection data with the can ID of the battery cell case CC. Accordingly, tracking of the seventh process data and the seventh inspection data can be provided based on at least one of the can ID, the carrier ID mapped with the can ID, and the jelly-roll ID.

[0170] Subsequently, with reference to Figure 1 , Figure 2 and Figure 8 , in the process P110, an electrolyte can be injected into the battery cell case. The process P110 can also be referred to as an electrolyte injection process. The electrolyte can be formed by the sub device 110h.

[0171] The sub device 110h can include a data matrix reader 111h, a controller 113h, and an electrolyte injector 117h. The controller 113h can be configured to control the capturing of the data matrix reader 111h and the operation of the electrolyte injector 117h. The electrolyte injector 117h can be configured to inject the electrolyte into the battery cell case CC by using a vacuum, a capillary phenomenon, and a wetting phenomenon.

[0172] The data matrix reader 111h can be configured to detect the data matrix DM3 of the battery cell case CC. When the reading of the data matrix DM3 is successful, the data matrix reader 111h can be configured to transmit a signal indicating the can ID of the battery cell case CC to the controller 120c. The controller 120c can identify the can ID of the battery cell case CC based on the transmitted signal.

[0173] The controller 120c can be configured to collect battery cell tracking data CTDh of the sub device 110h. The battery cell tracking data CTDh can further include time data regarding the time at which the sub device 110h identifies the can ID of the battery cell case CC. In addition, the battery cell tracking data CTDh can include the can ID of the battery cell case CC. The battery cell tracking data CTDh can further include the time matching the can ID of the battery cell case CC. When the reading of the data matrix DM3 fails, the battery cell tracking data CTDh can include an unidentified can ID of the battery cell case CC.

[0174] The controller 120c can obtain eighth process data and eighth inspection data corresponding to the process P110 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) from the sub device 110h.

[0175] According to an example embodiment, the eighth process data can include at least one of information related to a device that performs the process P110 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted), a time at which the process P110 is performed, and information related to an electrolyte (e.g., electrolyte components and an injection amount).

[0176] According to an example embodiment, the eighth inspection data can include an image obtained by capturing the battery cell case CC by a vision machine and state information of the battery cell case CC based on the image. Here, the state information can include an electrolyte impregnation degree determined based on an appearance image of the battery cell case CC.

[0177] The controller 120c can be configured to map the obtained eighth process data and eighth inspection data to the can ID of the battery cell case CC. Accordingly, tracking of the eighth process data and the eighth inspection data can be provided based on at least one of the can ID, the carrier ID mapped to the can ID, and the jelly-roll ID.

[0178] Subsequently, with reference to Figure 1 , Figure 2 and Figure 9 , in the process P120, the positive tab PT (see Figure 3 ) of the jelly-roll JR and the positive terminal of the cap assembly case CA can be welded. The process P120 can also be referred to as a positive tab welding process. The positive tab PT (see Figure 3 ) of the jelly-roll JR can be welded to the positive terminal of the cap assembly by the sub device 110i.

[0179] The sub device 110i can include a data matrix reader 111i and a controller 113i. The controller 113i can be configured to control capturing of the data matrix reader 111i and operation of a welding tool.

[0180] The data matrix reader 111i can be configured to detect the data matrix DM3 of the battery cell case CC. When reading of the data matrix DM3 is successful, the data matrix reader 111i can be configured to transmit a signal indicating the can ID of the battery cell case CC to the controller 120c. The controller 120c can identify the can ID of the battery cell case CC based on the transmitted signal.

[0181] The controller 120c can be configured to collect cell tracking data CTDi of the sub device 110i. The cell tracking data CTDi can further include time data on a time at which the sub device 110i recognizes the can ID of the cell case CC. In addition, the cell tracking data CTDi can include the can ID of the cell case CC. The cell tracking data CTDi can further include a time matching the can ID of the cell case CC. When reading of the data matrix DM3 fails, the cell tracking data CTDi can include an un-recognized can ID of the cell case CC.

[0182] The controller 120c can obtain, from the sub device 110i, ninth process data and ninth inspection data corresponding to the process P120 targeting the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted).

[0183] According to an example embodiment, the ninth process data can include at least one of information related to a device performing the process P120 targeting the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted), a time at which the process P120 is performed, and information related to a set value used in the process P120 (e.g., a pressure applied to a positive electrode terminal of the cell case CC, an applied voltage (or current), a welding position, a welding pass number).

[0184] According to an example embodiment, the ninth inspection data can include measurement information obtained by scanning a dimension of the cap assembly case CA, an image obtained by capturing the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted) with a vision machine, and state information of the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted) and the cap assembly case CA checked based on at least one of the measurement information and the image. Here, the state information can include at least one of information on whether the cap assembly case CA is defective based on a dimension of the cap assembly case CA and information on a type of defect determined based on an appearance image of the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted) and the cap assembly case CA.

[0185] The controller 120c can be configured to map the obtained ninth process data and ninth inspection data with the can ID of the cell case CC. Accordingly, tracking of the ninth process data and the ninth inspection data can be provided based on at least one of the can ID, the carrier ID, and the jelly roll ID mapped with the can ID.

[0186] Subsequently, reference is made to Figure 1 , Figure 2 and Figure 10In the process P130, the battery cell can be sealed. The process P130 can also be referred to as a press process. In the press process, the battery cell BC can be sealed by applying pressure to the upper portion of the battery cell BC including the gasket and various safety devices (a positive temperature coefficient (PTC) device, a safety vent, and a current interrupter). Here, the upper portion of the battery cell BC can be a portion of the cell case CC in which the groove is formed in the crimping process.

[0187] The sub device 110j can include a data matrix reader 111j, a controller 113j, and a press tool 117j. The controller 113j can be configured to control the capturing of the data matrix reader 111j and the operation of the press tool 117j.

[0188] The data matrix reader 111j can be configured to detect the data matrix DM3 of the cell case CC. When the reading of the data matrix DM3 is successful, the data matrix reader 111j can be configured to transmit a signal indicating the can ID of the cell case CC to the controller 120c. The controller 120c can identify the can ID of the cell case CC based on the transmitted signal.

[0189] Subsequently, in the process P140, the size of the battery cell can be determined. By applying pressure to the battery cell BC in the axial direction (or the height direction), the total height of the battery cell BC can be adjusted (or reduced). The size determination of the battery cell can be performed by the sub device 110j.

[0190] The controller 120c can be configured to collect the cell tracking data CTDj of the sub device 110j. The cell tracking data CTDj can also include time data about the time at which the sub device 110j identifies the can ID of the cell case CC. In addition, the cell tracking data CTDj can include the can ID of the cell case CC. The cell tracking data CTDj can also include the time matching the can ID of the cell case CC. When the reading of the data matrix DM3 fails, the cell tracking data CTDj can include the unidentified can ID of the cell case CC.

[0191] The controller 120c can obtain the tenth process data and the tenth inspection data corresponding to the processes P130 and P140 targeting the jelly roll JR (or the cell case CC into which the jelly roll JR is inserted) from the sub device 110j.

[0192] According to an example embodiment, the tenth process data can include at least one of information related to equipment performing processes P130 and P140 targeting the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted), a time of performing the processes P130 and P140, information about the gasket located in the groove, and information related to set values used in the processes P130 and P140 (e.g., a pressure applied to the upper portion of the battery cell BC and a number of pressurization times during sealing and a target total height of the battery cell BC during sizing).

[0193] According to an example embodiment, the tenth inspection data can include an image obtained by capturing the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) by a vision machine and state information of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted) inspected based on the image. Here, the state information can include information about a defect type determined based on an appearance image of the jelly-roll JR (or the battery cell case CC into which the jelly-roll JR is inserted).

[0194] The controller 120c can be configured to map the obtained tenth process data and tenth inspection data with the can ID of the battery cell case CC. Accordingly, tracking of the tenth process data and the tenth inspection data can be provided based on the carrier ID and / or the jelly-roll ID mapped with the carrier ID.

[0195] Subsequently, with reference to Figure 1 , Figure 2 and Figure 11 , in the process P150, the battery cell BC can be cleaned. The cleaning of the battery cell BC can be performed by the sub-equipment 110k. The sub-equipment 110k can include a cleaning solution sprayer 117k configured to spray a cleaning solution.

[0196] Subsequently, in the process P160, the battery cell BC can be inspected. The inspection of the battery cell BC can include appearance inspection and three-dimensional scanning of the battery cell BC, for example, by a vision machine. The battery cell BC can be inspected by the sub-equipment 110l.

[0197] The processor 130 and / or the server 200 can obtain, from the sub-equipment 110l, eleventh process data and eleventh inspection data corresponding to the process P160 targeting the battery cell BC.

[0198] According to an example embodiment, the eleventh process data can include at least one of information related to equipment performing the process P160 targeting the battery cell BC and a time of performing the process P160.

[0199] According to an example embodiment, the eleventh inspection data can include at least one of measurement information obtained by scanning to measure a size of the battery cell BC, an image obtained by visually capturing the battery cell BC, and state information of the battery cell BC inspected based on at least one of the measurement information and the image. Here, the state information can include at least one of information on whether the battery cell BC is defective based on the size of the battery cell BC and information on a type of defect (e.g., an upper and / or lower tilt defect and a side defect) based on an appearance image of the battery cell BC.

[0200] The processor 130 and / or the server 200 can be configured to map the obtained eleventh process data and the eleventh inspection data with the can ID of the cell case CC. Accordingly, tracking of the eleventh process data and the eleventh inspection data can be provided based on at least one of the can ID, the carrier ID mapped with the can ID, and the roll cell ID.

[0201] Subsequently, with reference to Figure 1 , Figure 2 and Figure 12 , in the process P170, a data matrix DM4 can be formed in the battery cell BC. For example, the data matrix DM4 can be formed by a method such as laser marking and inkjet marking. The data matrix DM4 can be formed by the marking machine 117m. The data matrix DM4 can include information on a batch ID of the battery cell BC. In other words, when the data matrix reader reads the data matrix DM4, a signal indicating the batch ID of the battery cell BC can be generated.

[0202] The batch ID of the battery cell BC can include a plurality of symbols for distinguishing and / or identifying the battery cell BC. In other words, the batch ID can include information for identifying the battery cell BC. The batch ID can be used to distinguish the battery cell BC.

[0203] The sub device 110m can include a data matrix reader 111m, a controller 113m, and a marking machine 117m. The controller 113m can be configured to control capturing of the data matrix reader 111m and operation of the marking machine 117m.

[0204] One of the data matrix readers 111m can be configured to detect the data matrix DM3 of the cell case CC. When reading of the data matrix DM3 is successful, the data matrix reader 111m can be configured to transmit a signal indicating the can ID of the cell case CC to the controller 120d. The controller 120d can identify the can ID of the cell case CC based on the transmitted signal.

[0205] Another one of the data matrix readers 111m can be configured to detect the data matrix DM4 formed by the marking machine 117m. When the reading of the data matrix DM3 is successful, the data matrix reader 111m can be configured to send a signal indicating the lot ID of the battery cell BC to the controller 113m. The controller 113m can be configured to send a signal indicating the lot ID of the battery cell BC to the controller 120d. The controller 120d can identify the lot ID of the battery cell BC based on the sent signal.

[0206] The controller 120d can be configured to collect the cell tracking data CTDm of the sub- device 110m. The cell tracking data CTDm can include the can ID of the cell case CC and the lot ID of the battery cell BC. The cell tracking data CTDm can further include time data about a time of identifying the can ID of the cell case CC and a time of identifying the lot ID of the battery cell BC.

[0207] The controller 120d can be configured to match the can ID of the cell case CC with the lot ID of the battery cell BC. According to an example embodiment, the controller 120d can be configured to match the can ID of the cell case CC with the lot ID of the battery cell BC by comparing the time of identifying the can ID and the time of identifying the lot ID based on the cell tracking data CTDm. For example, if a time interval between the times of identifying the can ID and the lot ID is within a preset threshold time value, the identified can ID and the identified lot ID can be matched with each other. In contrast, if the time interval between the times of identifying the can ID and the lot ID exceeds the preset threshold time value, the identified can ID can be matched with another lot ID whose time interval is within the threshold time value.

[0208] The cell tracking data CTDm can further include a time matched with the can ID of the cell case CC. When the reading of the data matrix DM3 fails, the cell tracking data CTDm can include an unidentified can ID of the cell case CC. When the reading of the data matrix DM4 fails, the cell tracking data CTDm can include an unidentified lot ID of the cell case CC.

[0209] Subsequently, in the process P180, the internal resistance of the battery cell BC can be measured. The internal resistance of the battery cell BC can be determined based on the open circuit voltage of the battery cell BC. The internal resistance of the battery cell BC can be measured by the sub-device 110n.

[0210] The sub-device 110n can include a data matrix reader 111n and a controller 113n. The controller 113n can be configured to control the capturing of the data matrix reader 111n and the operation of the holder and the measuring device for measuring the internal resistance of the battery cell BC.

[0211] The data matrix reader 111n can be configured to detect the data matrix DM3 of the cell case CC. When the reading of the data matrix DM3 is successful, the data matrix reader 111n can be configured to transmit a signal indicating the can ID of the battery cell BC to the controller 120d. The controller 120d can identify the can ID of the cell case CC based on the transmitted signal.

[0212] The controller 120d can be configured to collect cell tracking data CTDn of the sub device 110n. The cell tracking data CTDn can include the can ID of the battery cell BC. The cell tracking data CTDn can further include a time matching the can ID of the battery cell BC. When the reading of the data matrix DM3 fails, the cell tracking data CTDn can include an unidentified can ID of the cell case CC.

[0213] The controller 120d can obtain twelfth inspection data corresponding to the process P180 targeting the battery cell BC from the sub device 110n. Here, the twelfth inspection data can include information related to a result of an internal resistance measurement targeting the battery cell BC. For example, the twelfth inspection data can include a state measurement value (e.g., open circuit voltage and internal resistance) of the battery cell BC and information related to whether the battery cell BC is abnormally inspected based on the state measurement value.

[0214] The controller 120d can be configured to match the obtained twelfth inspection data with the can ID of the cell case CC. Accordingly, tracking of the twelfth inspection data can be provided based on at least one of the can ID, the carrier ID matching the can ID, and the cell ID.

[0215] As described above, the assembly process of the battery cell can be tracked by the cell ID, the carrier ID, the can ID, and the lot ID. In other words, the battery cell BC after shipment can provide the lot ID based on the reading of the data matrix DM4, and tracking of the history data of the sub-processes of the assembly process can be provided based on the lot ID.

[0216] More specifically, the sub-processes performed by the sub devices 110a, 110b, and 110c can be tracked by the cell ID, and the cell ID can be matched with the can ID by the cell tracking data CTDc of the sub device 110c. The sub-processes performed by the plurality of sub devices 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110m, and 110n can be tracked by the can ID, and the can ID can be matched with the lot ID by the cell tracking data of the sub device 110n.

[0217] Controllers 120a, 120b, 120c, and 120d can be configured to collect cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn from controllers 113a, 113b, 113c, 113d, 113e, 113g, 113h, 113j, 113m, and 113n. More specifically, controller 120a can be configured to collect cell tracking data CTDa, CTDb, CTDc, and CTDd collected from controllers 113a, 113b, 113c, and 113d, and controller 120b can be configured to collect cell tracking data CTDe, CTDf, and CTDg collected from controllers 113e, 113f, and 113g, and controller 120c can be configured to collect cell tracking data CTDh, CTDi, and CTDj collected from controllers 113h, 113i, and 113j, and controller 120d can be configured to collect cell tracking data CTDm and CTDn collected from controllers 113m and 113n.

[0218] Controllers 120a, 120b, 120c, and 120d can perform the functions of a network hub. From Figure 2 The allocation of cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn collected from controllers 113a, 113b, 113c, 113d, 113e, 113f, 113g, 113h, 113i, 113j, 113m, and 113n shown is for illustrative purposes and the present disclosure is not limited in any sense thereto.

[0219] Each of controllers 113a, 113b, 113c, 113d, 113e, 113f, 113g, 113h, 113i, 113j, 113m, and 113n and controllers 120a, 120b, 120c, and 120d can be a programmable logic controller (PLC). A PLC is a special type of microprocessor-based controller that uses programmable memory for storing instructions and implements functions such as logic, sequencing, timing, counting, and arithmetic for controlling machines and processes. PLCs are easy to operate and program.

[0220] Each of the controllers 113a, 113b, 113c, 113d, 113e, 113f, 113g, 113h, 113i, 113j, 113m, and 113n and the controllers 120a, 120b, 120c, and 120d can include a power supply, a central processing unit (CPU), an input interface, an output interface, a communication interface, and a memory device. The power supply can be configured to supply power to other elements of the controller, such as the CPU, the input interface, the output interface, the communication interface, and the memory device, for operation of the controller. The memory device can include a read-only memory (ROM) configured to store a system program, such as an operating system, and a random access memory (RAM) configured to store a user program and data, such as state information of input and output devices and values of timers, counters, and other internal devices. The CPU can be configured to control communication between modules that implement logic and convert input signals into output operation signals. The CPU can operate based on the system program and the user program stored in the memory device. The CPU can be configured to write check data and measurement data to or read check data and measurement data from a data area of the memory device based on the system program and the user program. Conditions or data of the industrial apparatus and the production process can be transmitted to the CPU through the input module. Results processed by the CPU can be transmitted to the actuator through the output module. The communication interface can be configured to relay data transmission and reception between the controller and other network elements.

[0221] However, the present disclosure is not limited thereto, and each of the controllers 113a, 113b, 113c, 113d, 113e, 113f, 113g, 113h, 113i, 113j, 113m, and 113n and the controllers 120a, 120b, 120c, and 120d can include one of a simple controller, a complex processor such as a microprocessor, a CPU and a graphic processing unit (GPU), a processor configured by software, a dedicated hardware, and a firmware. The controller can be implemented by, for example, a general-purpose computer or a dedicated hardware such as a digital signal processor (DSP), a field programmable gate array (FPGA), and an application specific integrated circuit (ASIC).

[0222] The processor 130 can be configured to receive the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn from the controllers 120a, 120b, 120c, and 120d. The processor 130 can be configured to collect the cell tracking data from the controllers 120a, 120b, 120c, and 120d.

[0223] The processor 130 can be configured to store log files including at least one of the cell ID, the carrier ID, the can ID, and the lot ID. The log files including at least one of the cell ID, the carrier ID, the can ID, and the lot ID can include, for example, log files of the data matrix readers 111a, 111b, 111c, 111d, 111e, 111f, 111g, 111h, 111i, 111j, 111m, and 111n, trigger log files of the controllers 120a, 120b, 120c, and 120d, NG code log files, and device data log files.

[0224] The processor 130 can be configured to generate log files for a server based on the log files including at least one of the cell ID, the carrier ID, the can ID, and the lot ID. The log files for the server can include logs of the data matrix readers 111a, 111b, 111c, 111d, 111e, 111f, 111g, 111h, 111i, 111j, 111m, and 111n, trigger logs of the controllers 120a, 120b, 120c, and 120d, NG code logs, and device data logs.

[0225] The log files for the server can have a format accessible from the server 200. The log files for the server can comply with a hypertext transfer protocol (HTTP). The log files for the server can have, for example, a hypertext markup language (HTML) format.

[0226] The processor 130 can be configured to transmit the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn to the server 200. The server 200 can be configured to store the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn. The server 200 can be configured to store a match between different IDs used in each stage of the assembly process, such as the cell ID, the carrier ID, the can ID, and the lot ID, and thus, can provide tracking of historical data of the assembly process of the secondary battery of the product during manufacturing or after shipment.

[0227] The server 200 can include a physical server or a cloud server. The server 200 can be implemented as a virtual server, but is not limited thereto. The server 200 can provide data and analysis results to an operator through various frameworks. The framework can include a protocol supporting data transmission so that a client device can visualize data through a user interface and provide an updated visualization when data is calculated by the server 200. The protocol supporting data transmission can use HTML, JavaScript, and / or JavaScript Object Notation (JSON).

[0228] The server 200 can include various application programming interfaces (APIs) for storing data in a database and other data management tools. The API can also be used to retrieve data from the databases of various data management systems. The data management system can provide access to the database, extract data from the database, or retrieve data, and generate metrics. Here, the metrics are tools for visualizing data. The metrics include measurement results generated in a time series, and can be used to monitor an application and generate a status alert.

[0229] According to an example embodiment, the server 200 can be configured to obtain a roll map of the jelly-roll JR from an electrode manufacturing system (not shown) that performs an electrode manufacturing process before a secondary battery assembly process.

[0230] Here, the electrode manufacturing process can be a process of manufacturing the jelly-roll JR through a mixing process of mixing various raw materials for electrode manufacturing, a coating process of applying an active material and a predetermined insulating material to a surface of a metal electrode plate as a current collector to form a positive electrode and a negative electrode, a roll pressing process of roll pressing the coated electrode, and a slitting process of cutting the roll pressed electrode into a specification of the jelly-roll JR. In the mixing process, the coating process, the roll pressing process, and the slitting process, the electrode can be wound between an unwinder and a rewinder, and can be performed in a roll-to-roll state. The roll map can be represented in the form of a bar simulating an electrode process in each of a plurality of sub-processes included in the electrode manufacturing process. On the roll map, a longitudinal dimension of the electrode can be shown as a coordinate, and information on a quality of the electrode can be shown together with the corresponding coordinate. For example, electrode appearance information obtained by an image-based inspection device such as a vision machine, information on a short circuit and a joint of the electrode, information on an electrode portion for which a sampling inspection is performed, information on an electrode portion planned to be scrapped, information on a scrapped electrode portion, information on whether a coating material and an insulating material on the electrode are defective, and information on a defect type of the electrode (for example, a pinhole defect, a dent defect, a line defect, a crack defect, a side ring defect, an island defect, a folding defect, a wrinkle defect, a indentation defect, and a embossing defect) can be displayed on the roll map together with the corresponding coordinate.

[0231] The server 200 can be configured to map the cell ID corresponding to the semi-finished cell with the roll map. According to an example embodiment, the server 200 can be configured to map the cell ID of the roll cell JR with the roll map using the roll map.

[0232] For example, the server 200 can be configured to map the cell ID with the roll map based on the electrode lot ID of the roll cell JR. The server 200 can be configured to obtain the electrode lot ID of the roll cell JR from an electrode manufacturing system (not shown). Also, the server 200 can be configured to further obtain the mapping between the electrode lot ID of the roll cell JR and the roll map from the electrode manufacturing system (not shown). The electrode manufacturing system (not shown) can be configured to generate the electrode lot ID of the roll cell JR, and generate the roll map based on the electrode progress of the roll cell JR in the electrode manufacturing process. Also, the electrode manufacturing system (not shown) can be configured to map the electrode lot ID and the roll map of the roll cell JR to each other, and transmit the mapping between the electrode lot ID and the roll map to the server 200.

[0233] Since the cell ID of the roll cell JR is generated based on the electrode lot ID loaded from the server 200 by the controller 113a as described above, the server 200 can be configured to map the cell ID and the roll map through the electrode lot ID. Subsequently, the server 200 can be configured to map the roll map using at least one of the carrier ID, the can ID, and the lot ID matching the cell ID. Accordingly, the tracking of the roll map can be provided based on at least one of the cell ID, the carrier ID, the can ID, and the lot ID mapped with the roll map.

[0234] According to an example embodiment, the server 200 can be configured to obtain activation data of the battery cell BC from an activation system (not shown) performing an activation process after the secondary battery assembly process.

[0235] Here, the activation process can be a process of stabilizing a battery structure and imparting battery characteristics to the battery cell BC manufactured through the assembly process through a plurality of sub-processes such as aging, charging, and discharging. The activation data can include setting data related to a set value (for example, an aging temperature and a charge / discharge state of charge (SOC) used in a plurality of sub-processes included in the activation process), state data related to a state (for example, a voltage, a current, a temperature, and an SOC) of the battery cell BC obtained during the activation process, and diagnosis data for diagnosing an abnormality (for example, a low voltage and an internal short circuit) of the battery cell BC based on the state data.

[0236] According to an example embodiment, the server 200 can be configured to obtain the activation data from an activation system (not shown). Further, the server 200 can be configured to further obtain a mapping between the activation data and the can ID and / or lot ID of the battery cell BC from the activation system (not shown). The activation system (not shown) can be configured to identify the can ID and / or lot ID of the battery cell BC targeted for the activation process and generate the activation data of the battery cell BC for the activation process. Further, the activation system (not shown) can be configured to map the can ID and / or lot ID of the battery cell BC with the activation data and transmit the mapping between the can ID and / or lot ID and the activation data to the server 200. Since the can ID and / or lot ID of the battery cell BC is identified by the secondary battery manufacturing system 1000 and mapped with the process data and IDs (e.g., the jelly-roll ID and the carrier ID) of the previous processes as described above, the tracking of the activation data of the battery cell BC can be provided based on at least one of the jelly-roll ID, the carrier ID, the can ID, and the lot ID.

[0237] The processor 130 and the server 200 can be implemented with hardware, firmware, software, and a combination thereof. For example, the processor 130 and the server 200 can include a computing device such as a workstation computer, a desktop computer, a laptop computer, and a tablet computer. The processor 130 and the server 200 can include one of a simple controller, a microprocessor, a complex processor such as a central processing unit (CPU) and a graphics processing unit (GPU), a processor configured by software, a dedicated hardware, and firmware. The processor 130 and the server 200 can be implemented by, for example, a general-purpose computer or a dedicated hardware such as a digital signal processor (DSP), a field programmable gate array (FPGA), and an application specific integrated circuit (ASIC).

[0238] The operations of the processor 130 and the server 200 can be implemented by instructions stored in a machine-readable medium that can be read and executed by one or more processors. Here, the machine-readable medium can include any mechanism for storing and / or transmitting information in a form readable by a machine (e.g., a computing device). For example, the machine-readable medium can include read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, and digital signals), and any other suitable type of storage medium. The processor 130 and the server 200 can be configured with firmware, software, routines, and instructions for performing the above-described operations or any of the processes described below. For example, the processor 130 and the server 200 can be instantiated in memory.

[0239] The secondary battery manufacturing system 1000 can implement a plug-in architecture having an API for data acquisition to provide plug-and-play connectivity of sensors, measuring instruments, and inspection machines. Accordingly, resources at a specific process operation and a specific station can be easily transferred to other processes and other stations, or new resources can be easily introduced to each process operation and station.

[0240] In some example embodiments, the secondary battery manufacturing system 1000 can further include a manual input system that allows an operator to input manufacturing data. The secondary battery manufacturing system 1000 can allow the operator to input data using an input tool and computer-based input of manufacturing data such as grabbing an Excel file. The manual input system can be, for example, a human-machine interface (HMI) of a supervisory control and data acquisition (SCADA). The SCADA can generally include a combination of software and hardware such as a remote terminal unit (RTU) and a PLC. The HMI is a screen that supports communication between an operator and the SCADA system and is a main element of the SCADA system. For example, the manual input of the HMI can include selecting a defect type and reflecting performance upon completion.

[0241] Figure 13 FIG. 1 is a diagram for illustrating a method of managing data by a secondary battery manufacturing system 1000 according to an example embodiment. Figure 14 is a diagram illustrating Figure 13 the roll map data shown in FIG. 1.

[0242] Referring to Figure 13 and Figure 14 , the secondary battery manufacturing system 1000 can be configured to map and manage roll map data 1030 collected based on the electrode manufacturing process 1010 and data 1060a, 1060b, 1060c, 1060d, 1060e, 1070a, 1070b, 1070c, 1070d, 1070e, 1080a, 1080b, 1080c, 1080d, and 1080e collected based on the assembly process 1040.

[0243] According to an example embodiment, the secondary battery manufacturing system 1000 can be configured to obtain roll map data 1030 based on the electrode manufacturing process 1010. The roll map data 1030 can be data expressed in the form of a roll by simulating electrode processes included in the mixing process 1020a, the coating process 1020b, the roll-pressing process 1020c, and the slitting process 1020d of the electrode manufacturing process 1010.

[0244] According to an example implementation, the secondary battery manufacturing system 1000 can be configured to obtain identification data 1060a, 1060b, 1060c, 1060d and 1060e, process data 1070a, 1070b, 1070c, 1070d and 1070e, and inspection data 1080a, 1080b, 1080c, 1080d and 1080e of semi-finished products based on assembly process 1040.

[0245] According to an example implementation, based on the winding process 1050a included in the assembly process 1040m (e.g., Figure 1 The secondary battery manufacturing system 1000 can be configured to obtain the core ID 1060a of the core JR, as well as the process data 1070a and inspection data 1080a of the winding process 1050a. In this case, the process data 1070a and inspection data 1080a can be mapped to the core ID 1060a.

[0246] According to an example implementation, the secondary battery manufacturing system 1000 can be configured to map the core ID 1060a using roll pattern data 1030. Therefore, tracking of the roll pattern data 1030, process data 1070a, and inspection data 1080a can be provided based on the core ID 1060a.

[0247] According to the example implementation, based on the vehicle movement process 1050b included in the assembly process 1040 (e.g., Figure 1 The secondary battery manufacturing system 1000 can be configured to obtain the carrier ID 1060b of the carrier and the process data 1070b and inspection data 1080b of the carrier movement process 1050b. In this case, the process data 1070b and inspection data 1080b can be mapped to the carrier ID 1060b.

[0248] According to an example implementation, the secondary battery manufacturing system 1000 can be configured to match carrier ID 1060b with core ID 1060a. Therefore, tracking of roll pattern data 1030, process data 1070a and 1070b, and inspection data 1080a and 1080b can be provided based on at least one of core ID 1060a and carrier ID 1060b.

[0249] According to an example implementation, based on can insertion process 1050c (e.g., included in assembly process 1040), Figure 1According to an example embodiment, the secondary battery manufacturing system 1000 can be configured to obtain the can ID 1060c of the cell case CC and process data 1070c and inspection data 1080c of the can insertion process 1050c. In this case, the process data 1070c and the inspection data 1080c can be mapped with the can ID 1060c.

[0250] According to an example embodiment, the secondary battery manufacturing system 1000 can be configured to match the can ID 1060c with the carrier ID 1060b. Accordingly, tracking of the roll map data 1030, the process data 1070a, 1070b, and 1070c, and the inspection data 1080a, 1080b, and 1080c can be provided based on at least one of the roll core ID 1060a, the carrier ID 1060b, and the can ID 1060c.

[0251] According to an example embodiment, based on a can molding process 1050d (e.g., processes P60 to P140) included in the assembly process 1040, Figure 1 According to an example embodiment, the secondary battery manufacturing system 1000 can be configured to obtain the can ID 1060d of the cell case CC and process data 1070d and inspection data 1080d of the can molding process 1050d. In this case, the process data 1070d and the inspection data 1080d can be mapped with the can ID 1060d.

[0252] Meanwhile, since the can ID 1060c and the can ID 1060d are identical to each other, tracking of the roll map data 1030, the process data 1070a, 1070b, 1070c, and 1070d, and the inspection data 1080a, 1080b, 1080c, and 1080d can be provided based on at least one of the roll core ID 1060a, the carrier ID 1060b, and the can ID 1060c without a separate ID matching.

[0253] According to an example embodiment, based on a cleaning / inspection process 1050e (e.g., processes P150 to P180) included in the assembly process 1040, Figure 1 According to an example embodiment, the secondary battery manufacturing system 1000 can be configured to obtain the battery cell ID 1060e (e.g., a lot ID) of the battery cell BC and process data 1070e and inspection data 1080e of the cleaning / inspection process 1050e. In this case, the process data 1070e and the inspection data 1080e can be mapped with the battery cell ID 1060e.

[0254] According to an example embodiment, the secondary battery manufacturing system 1000 can be configured to match the battery cell ID 1060e with the can ID 1060c. Accordingly, the tracking of the roll map data 1030, the process data 1070a, 1070b, 1070c, 1070d, and 1070e, and the inspection data 1080a, 1080b, 1080c, 1080d, and 1080e can be provided based on at least one of the roll core ID 1060a, the carrier ID 1060b, the can ID 1060c, and the battery cell ID 1060e.

[0255] (Third and fourth examples)

[0256] Figure 15 is a flowchart illustrating a method of managing cell tracking data CTDc according to an example embodiment.

[0257] Figure 16 is a diagram illustrating a method of managing cell tracking data CTDc according to an example embodiment. More specifically, Figure 16 a portion of the cell tracking data CTDc including the roll core ID is illustrated.

[0258] Figure 17 is a diagram illustrating a method of managing cell tracking data CTDc according to an example embodiment. More specifically, Figure 17 a portion of the cell tracking data CTDc including the can ID is illustrated.

[0259] Referring to Figure 1 , Figure 2 and Figure 5 and Figures 15 to 17 , the unidentified roll core ID and the unidentified can ID can be recovered by the server 200. The server 200 can include logic for recovering the unidentified roll core ID and the unidentified can ID. The logic can operate based on a pre-set management period of the cell tracking data CTDc.

[0260] In operation P210, the cell tracking data CTDc can be loaded. The unidentified ID recovery logic can include a query for retrieving and / or loading a portion of the cell tracking data CTDc including the unidentified roll core ID or the unidentified can ID from a database of the server 200.

[0261] Subsequently, the cell tracking data CTDc can be recovered in operation P220. Recovering the cell tracking data can include recovering the unidentified roll core ID of the cell tracking data CTDc collected in the process P50 or recovering the unidentified can ID of the cell tracking data CTDc collected in the process P50.

[0262] Referring to Figure 1 , Figure 2 ,Figure 5 、 Figure 15 and Figure 16 The unidentified cell ID of the cell tracking data CTDc can be recovered based on the cell ID adjacent in time to the unidentified ID. According to an example embodiment, the unidentified cell ID can be recovered based on the cell ID before the unidentified cell ID. According to an example embodiment, the unidentified cell ID can be recovered based on the cell ID after the unidentified cell ID. According to an example embodiment, the unidentified cell ID can be recovered based on the cell ID before the unidentified cell ID and the cell ID after the unidentified cell ID.

[0263] Here, the unidentified cell ID and the cell ID adjacent in time to each other can indicate that there is no cell ID matching a third time between a first time matching the unidentified cell ID and a second time matching the cell ID in the cell tracking data CTDc. In other words, when the cell ID is arranged next to the unidentified cell ID at the time alignment of the cell tracking data CTDc, the cell ID of the unidentified cell ID can be referred to as adjacent in time thereto.

[0264] As described above, the cell ID can be generated based on the positive electrode batch ID, the positive electrode count, the tray ID, and the tray coordinates. The last four symbols of the cell ID can represent the row coordinates and the column coordinates on the tray 20. The other symbols of the cell ID can represent the positive electrode batch ID, the positive electrode count, and the tray ID. In the table of Figure 14 “A396Nca0003CC1D” highlighted in shadow in the table of

[0265] Since the cells JR are arranged in a matrix on the tray 20 and sequentially input into the sub device 110a, the cell IDs adjacent in time can be derived from the cells JR adjacently arranged on the tray 20. Accordingly, the unidentified cell ID “A396Nca0003CC1D” can be recovered based on the previous cell ID “WCCHJ71123JTM2AA06110117” and / or the subsequent cell ID “WCCHJ71123JTM2AA06110401”.

[0266] In this example, the cores JR on tray 20 can be arranged in an 18×18 matrix. The last four symbols in core IDs “WCCHJ71123JTM2AA06110117” and “WCCHJ71123JTM2AA06110401” represent the coordinates of the cores JR on tray 20. More specifically, the last four symbols “0117” in core ID “WCCHJ71123JTM2AA06110117” indicate that the core ID is derived from the core JR located in the seventeenth column of the first row of tray 20, and the last four symbols “0401” in core ID “WCCHJ71123JTM2AA06110401” indicate that the core ID is derived from the core JR located in the first column of the fourth row of tray 20. Meanwhile, since the cores JR are arranged in an 18×18 matrix on tray 20, as... Figure 16 As shown, it can be understood that there is no core ID derived from core JR in the eighteenth column of the first row of tray 20. Therefore, it can be understood that the core ID of core JR in the seventeenth column of the first row of tray 20 is adjacent to the core ID of core JR in the eighteenth column of the first row of tray 20.

[0267] Therefore, since the unidentified reel ID "A396Nca0003CC1D" can be recovered based on reel IDs that are temporally adjacent, such as... Figure 16 As shown, it can be identified that the roll core JR corresponding to the roll core ID "WCCHJ71123JTM2AA06110401" and the roll core JR corresponding to the unidentified roll core ID "A396Nca0003CC1D" are arranged in different rows on tray 20, and the roll core JR corresponding to the roll core ID "WCCHJ71123JTM2AA06110117" and the roll core JR corresponding to the unidentified roll core ID "A396Nca0003CC1D" are arranged in the same row on tray 20. Therefore, the unidentified roll core ID "A396Nca0003CC1D" can be recovered as "WCCHJ71123JTM2AA06110118".

[0268] In other words, recovering an unrecognized core ID may include changing the sign (or input order in the assembly process) of the coordinates representing the tray 20 in adjacent core IDs to the adjacent coordinates. According to an example implementation, recovering an unrecognized core ID may include changing the sign (or input order in the assembly process) of the coordinates representing the tray 20 in adjacent core IDs to the preceding coordinate (or order). According to an example implementation, recovering an unrecognized core ID may include changing the sign (or input order in the assembly process) of the coordinates representing the tray 20 in adjacent core IDs to the following coordinate (or order).

[0269] Although the recovery of the unidentified cell core ID derived from the example embodiment in which the cell cores JR are placed on the tray 20 in an 18x18 arrangement is described above, this is merely an example, and the present disclosure is not limited thereto in any sense. The unidentified cell core ID derived from the example embodiment in which the cell cores JR are arranged in any matrix on the tray 20 can be easily recovered by those skilled in the art.

[0270] Referring to Figure 1 , Figure 2 , Figure 7 , Figure 15 and Figure 17 , the recovery of the unidentified tank ID of the cell tracking data CTDc can include the recovery of the unidentified tank ID based on the tank ID adjacent in time to the unidentified tank ID. According to an example embodiment, the unidentified tank ID can be recovered based on the tank ID before the unidentified tank ID. According to an example embodiment, the unidentified tank ID can be recovered based on the tank ID after the unidentified tank ID. According to an example embodiment, the unidentified tank ID can be recovered based on the tank ID before the unidentified tank ID and the tank ID after the unidentified tank ID. In the table of Figure 17 "AD8Wo600005RQX" highlighted in shadow can have a different format from the tank ID, and can be an unidentified tank ID.

[0271] Since the cell case CC is arranged in a matrix on the tank tray and sequentially input into the sub device 110c, the tank ID adjacent in time can be derived from the cell core JR to be arranged adjacent on the tray 20. In other words, the adjacent tank ID in the cell tracking data CTDc can include a sequentially changed symbol. Therefore, at least one symbol of the tank ID in the cell tracking data CTDc can indicate the order in which the cell case CC is input into the sub device 110c.

[0272] For example, the tank ID "L1D8P030330T04" can be after the tank ID "L1D8P030330T03", the tank ID "L1D8P030330T05" can be after the tank ID "L1D8P030330T04", and the tank ID "L1D8P030330T06" can be after the tank ID "L1D8P030330T05". Therefore, some symbols of the tank ID can indicate the input order of the cell case CC from which the tank ID is derived. For example, the last two symbols of the tank ID can indicate the column coordinates on the tank tray. For example, the cell cases CC on the tank tray can be arranged in a 17x18 matrix. Referring to Figure 17Since the last two symbols of the can ID are consecutive from 03 to 09 and from 0A to 0J, these can be understood as the can ID derived from the battery cell case CC arranged in seventeen columns in a row, and the subsequent seventeen can IDs can be similarly understood as the can ID derived from the battery cell case CC arranged in seventeen columns in a row.

[0273] The unidentified can ID "AD8Wo600005RQX" can be recovered based on the preceding can ID "L1D8P030330T0J" and / or the following can ID "L1D8P030330T1L". In this example, the battery cell cases CC on the can tray can be arranged in a 17x18 matrix, in which seventeen battery cell cases CC can be input into the sub device 110c at a time. Accordingly, the can ID "L1D8P030330T0J" is derived from a different row than the unidentified can ID "AD8Wo600005RQX", and the can ID "L1D8P030330T1L" is derived from the same row as the unidentified can ID "AD8Wo600005RQX". Accordingly, the unidentified can ID "AD8Wo600005RQX" can be recovered as "L1D8P030330T1K".

[0274] Although the example in which seventeen battery cell cases CC are input into the sub device 110c at a time and seventeen can IDs sequentially change is described above, this is merely an example, and the present disclosure is not limited thereto in any sense. A person skilled in the art can easily implement an example embodiment in which less than seventeen or more than seventeen battery cell cases CC are simultaneously input into the sub device 110c.

[0275] The battery cell tracking data CTDc of the process P50 includes a match between the coil ID and the can ID, and thus can be used to connect the preceding history data and the following history data. According to an example embodiment, the unidentified coil ID and the unidentified can ID can be recovered based on a rule of the coil ID and the can ID of the battery cell tracking data CTDc, and a traceability break can be prevented, and thus the reliability of the secondary battery manufacturing can be enhanced.

[0276] (Fifth and sixth examples)

[0277] Figure 18 is a flowchart illustrating a battery cell tracking data management method according to an example embodiment.

[0278] Figure 19 is a diagram illustrating a battery cell tracking data management method according to an example embodiment.

[0279] Figure 20 is a diagram illustrating a battery cell tracking data management method according to an example embodiment.

[0280] Referring toFigure 1 、 Figure 2 and Figure 8 and Figures 18 to 20 A data set for recovery can be configured in operation P310. In Figure 19 , in the cell tracking data CTDc of the sub device 100c collected from the controller 113c, the consecutive can ID can be less than the expected number. For example, although the sub device 110c is designed to allow seventeen cell cases CC to be input thereto at the same time, the number of cell cases CC input to the sub device 110c at the same time can be different from seventeen. In this case, the can ID to be used for recovery of the unidentified can ID can not be selected from the can ID after the unidentified can ID and the can ID before the unidentified can ID.

[0281] Therefore, when the unidentified can ID cannot be recovered by the method of Figure 15 , a data set for recovery can be configured in operation P310. More specifically, in order to recover the unidentified can ID of the cell tracking data, a recovery data set including the cell tracking data of the current sub process and the cell tracking data of the adjacent sub process can be configured.

[0282] As an example, the recovery data set for recovering the unidentified can ID of the cell tracking data collected from the controller 113c can include the cell tracking data CTDc of the sub device 110c (in other words, the roll core insertion device) collected from the controller 113c and the cell tracking data CTDd of the sub device 110c (in other words, the tab welding device) collected from the controller 113d. Figure 19 The recovery data set for recovering the unidentified can ID of the cell tracking data CTDc collected from the controller 113c is illustrated.

[0283] For example, since the unidentified ID "AD5Go600007nsZ" of the cell tracking data of the device 110c exists between the can ID "D1D4K0201204AB" and the can ID "D1D4K020120D1H", a portion between the can ID "D1D4K0201204AB" and the can ID "D1D4K020120D1H" in the cell tracking data of the sub device 110c (in other words, the tab welding device) collected from the controller 113d can be included in the recovery data set.

[0284] As another example, the recovery data set for recovering the unidentified can ID of the cell tracking data collected from the controller 113n can include the cell tracking data CTDn of the sub device 110n (in other words, the internal resistance measurement device) collected from the controller 113n and the cell tracking data CTDm of the sub device 110m (in other words, the batch marking device) collected from the controller 113m. Figure 19The recovery dataset for recovering the unidentified can ID of the cell tracking data CTDn collected from the controller 113n is shown in FIG. 12.

[0285] Subsequently, the cell tracking data can be recovered in operation P320. Recovering the cell tracking data can include recovering the unidentified can ID of the cell tracking data CTDc or recovering the unidentified can ID of the cell tracking data CTDn collected in the process P180.

[0286] For example, the unidentified ID "AD5Go600007nsZ" of the cell tracking data CTDc of the device 110c exists between the can ID "D1D4K0201204AB" and the can ID "D1D4K020120D1H", and thus can be recovered as one of "D1D4K0201204AC" after the can ID "D1D4K0201204AB" or "D1D4K020120D1G" before the can ID "D1D4K020120D1H". The can ID "D1D4K0201204AC" exists between the can ID "D1D4K0201204AB" and the can ID "D1D4K020120D1H" in the cell tracking data CTDd collected by the controller 113d from the sub device 110d (in other words, the joint welding device), and is not included in the cell tracking data of the device 110c. Accordingly, the unidentified ID "AD5Go600007nsZ" of the cell tracking data CTDc of the device 110c can be recovered as the can ID "D1D4K0201204AC".

[0287] As another example, the can IDs having the preceding order in the cell tracking data CTDn of the device 110n (in other words, the internal resistance measurement device) can match the preceding order in the cell tracking data CTDm of the device 110m (in other words, the batch ID marking device), and the can IDs having the following order in the cell tracking data CTDn of the device 110n can match the following order in the cell tracking data CTDm of the device 110m. In other words, even if the order of each can ID in the cell tracking data CTDn of the device 110n and the order of each can ID in the cell tracking data CTDm of the device 110m do not correspond to each other, the order is maintained.

[0288] The un-identified ID "AT16Of00008k17" of the cell tracking data CTDn of the device 110n exists between the tank ID "D1D2K020120B1F" and the tank ID "D1D2K020120AOL", and thus, can be recovered to the tank ID "D1D2K020120B0F" which exists between the tank ID "D1D2K020120B1F" and the tank ID "D1D2K020120AOL" in the cell tracking data of the device 110m.

[0289] (Sixth Example)

[0290] Figure 21 FIG. 1 is a flowchart illustrating a cell tracking data management method according to an example embodiment.

[0291] Figure 22 FIG. 1 is a flowchart illustrating a cell tracking data management method according to an example embodiment.

[0292] Reference Figure 21 and Figure 22 The first data window W1 and the second data window W2 for recovery can be configured in operation P410. The first data window W1 for recovery can be provided from the cell tracking data including the un-identified tank ID.

[0293] As in the method of Figure 18 , when the un-identified tank ID of the cell tracking data can not be recovered based on the data set for recovery, the method of Figure 21 can be used. More specifically, the cell tracking data CTDiof a preceding process such as the sub-process P130 can be used to recover the un-identified tank ID of the cell tracking data CTDn. In this case, the order of the tank ID of the cell tracking data CTDnand the order of the cell tracking data CTDimay be different. Accordingly, the first data window W1 and the second data window W2 for recovery based on the un-identified tank ID can be configured.

[0294] In the example of Figure 22 , the first data window W1 for recovery can be configured based on the un-identified tank ID "AD6SoF00000uTK". The first data window W1 for recovery can include the tank IDs adjacent in time to the un-identified tank ID "AD6SoF00000uTK". The first data window W1 for recovery can include a preset number (e.g., ten) of preceding tank IDs from the un-identified tank ID "AD6SoF00000uTK". The first data window W1 for recovery can include a preset number (e.g., ten) of subsequent tank IDs from the un-identified tank ID "AD6SoF00000uTK".

[0295] According to the first data window W1 for recovery, it can be determined that "D1D5U0402209GX" is the first tank ID of the first recovery data window W1 and "1D5U0402209FQ" is the last tank ID thereof. "D1D5U0402209GX" which is the first tank ID of the first recovery data window W1 and "1D5U0402209FQ" which is the last tank ID thereof can be used to configure the second data window W2 for recovery. The second data window W2 for recovery can include a portion between the tank ID "D1D5U0402209GX" and the tank ID "1D5U0402209FQ" in the cell tracking data of the device 110i collected by the controller 117i.

[0296] Subsequently, in operation P420, the cell tracking data can be recovered. Recovering the cell tracking data can include matching each tank ID included in the second data window W2 for recovery with the tank ID from which the cell tracking data of the first data window W1 for recovery is derived. In Figure 22 In the example of FIG. 21, among the tank IDs of the second data window W2 for recovery, the tank ID "D1D5U0402209H6" can not be matched with the tank ID from which the cell tracking data of the first data window W1 for recovery is derived. When only a single tank ID is not matched with the tank ID from which the cell tracking data of the first data window W1 for recovery is derived as described above, the unidentified tank ID can be recovered as the corresponding tank ID. Accordingly, the unidentified tank ID "AD6SoF00000uTK" of the first window can be recovered as "D1D5U0402209H6".

[0297] Hereinafter, referring to Figures 23 to 28 a cell tracking method performed by the secondary battery manufacturing system 1000 is described. More specifically, referring to Figures 23 to 28 a method of tracking a cell by matching an ID in a secondary battery manufacturing process of the secondary battery manufacturing system 1000 is described.

[0298] Figure 23 is a flowchart illustrating a cell tracking data management method according to an example embodiment.

[0299] Since Figure 23 the method can be performed by Figure 2 the secondary battery manufacturing system 1000, any description overlapping with the above can be omitted, and the method can be described using the configuration of Figure 2 .

[0300] Figure 23 The example embodiments illustrated in the drawings are merely example embodiments, and the order of operations according to various example embodiments of the disclosure can differ from that of Figure 23The order shown can be omitted. Figure 23 Some of the operations shown can change the order of operations or can be combined.

[0301] Reference Figure 23 In operation P510, the secondary battery manufacturing system 1000 can obtain the cell ID corresponding to the semi-finished battery cell. According to the example implementation, the secondary battery manufacturing system 1000 can obtain the cell ID based on the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn.

[0302] Here, the semi-finished battery cell can include various types of semi-finished battery cells manufactured during the manufacturing process performed on the secondary battery manufacturing system 1000. For example, in the case of a can-type battery manufacturing process, the semi-finished battery cell can be configured as a wound core, which is a wound structure of a positive electrode, a negative electrode, and a separator inserted between the positive and negative electrodes, or configured as a can-type battery cell in which the wound core is inserted into the cell housing. As another example, in the case of a pouch-type battery manufacturing process, the semi-finished battery cell can be configured as a unit cell consisting of at least one polarized electrode (e.g., a positive and / or negative electrode) and a separator, a stacked electrode assembly formed by stacking multiple unit cells, a foldable electrode assembly formed by folding multiple unit cells, or a pouch-type battery cell in which the electrode assembly is inserted into a pouch. In this case, the unit cell can be configured as a single cell in which the positive and negative electrodes are located on the two outermost sides, a double cell in which electrodes of the same polarity are located on the two outermost sides, or a half cell in which the positive or negative electrode is located between the outermost separators.

[0303] In operation P520, the secondary battery manufacturing system 1000 can obtain a retainer ID corresponding to the retainer on which the semi-finished battery cell is placed. According to the example embodiment, the secondary battery manufacturing system 1000 can obtain the retainer ID based on the cell tracking data CTDa, CTDb, CTDc, CTDd, CTDe, CTDf, CTDg, CTDh, CTDi, CTDj, CTDm, and CTDn.

[0304] Here, the holder can include various types of holders in which a semi-finished battery cell is placed during a manufacturing process performed on the secondary battery manufacturing system 1000. For example, in the case of a can-type battery manufacturing process, the holder can be configured as a carrier 115a or 115b on which a jelly-roll is placed or a cell case into which the jelly-roll is inserted. The carrier 115a or 115b can be a configuration for holding a jelly-roll in a specific sub-process targeting the jelly-roll. The cell case can be a configuration of a cylindrical battery cell, and can be a configuration into which a jelly-roll is inserted in a specific sub-process. As another example, in the case of a pouch-type battery manufacturing process, the holder can be configured as a box in which unit cells are stacked or a pouch into which a unit cell is inserted. The box can be a configuration that stacks and holds a plurality of unit cells to be stacked or folded before a stacking process or a folding process for forming an electrode assembly by stacking or folding a plurality of unit cells during an assembly process of a pouch-type battery, after a slotting process for forming an electrode tab on an electrode sheet of a unit cell and a lamination process for joining the unit cell to a separator. The pouch can be a configuration of a pouch-type battery cell, and can be a configuration into which a stacked cell or a folded cell is inserted in an encapsulation process.

[0305] In operation P530, the secondary battery manufacturing system 1000 can match the cell ID obtained in operation P510 with the holder ID obtained in operation P520.

[0306] The method of Figures 24 to 28 is a flowchart for describing a method of matching at least two of a jelly-roll ID, a carrier ID, and a can ID in each of a plurality of sub-processes included in a can-type battery manufacturing process by a secondary battery manufacturing process performed by the secondary battery manufacturing system 1000, with the case in which the secondary battery manufacturing process is a can-type battery manufacturing process as an example. However, this is merely an example for ease of description, and the cell tracking method of the disclosure is not limited to the can-type battery manufacturing process, and can also be applied to a pouch-type battery manufacturing process.

[0307] Figure 24 is a flowchart illustrating a cell tracking data management method according to an example embodiment.

[0308] Since the method of Figure 24 can be performed by the secondary battery manufacturing system 1000 of Figure 2 , any description overlapping with the above can be omitted, and the method can be described using the configuration of Figure 2 .

[0309] Figure 24 The example embodiments illustrated are merely example embodiments, and the order of operations according to various example embodiments of the disclosure can differ from the order illustrated in Figure 24 , and Figure 24Some of the operations illustrated can change order, or can be combined, between operations.

[0310] Referring to Figure 24 In operation P610, the secondary battery manufacturing system 1000 can obtain a jelly-roll ID corresponding to a jelly-roll based on a first sub-process. For example, in a manufacturing process performed by the secondary battery manufacturing system 1000, the first sub-process can be a process P30 of Figure 1

[0311] In operation P620, the secondary battery manufacturing system 1000 can obtain a carrier ID corresponding to a carrier based on a second sub-process. Here, the carrier can be a configuration that loads a jelly-roll having the jelly-roll ID obtained in operation P610 in the second sub-process. For example, in a manufacturing process performed by the secondary battery manufacturing system 1000, the second sub-process can be a process P40 of Figure 1

[0312] In operation P630, the secondary battery manufacturing system 1000 can match the jelly-roll ID obtained in operation P610 and the carrier ID obtained in operation P620. The operation P630 in which the secondary battery manufacturing system 1000 matches the jelly-roll ID and the carrier ID can be described in more detail by Figure 25 and Figure 26

[0313] Figure 25 is a flowchart illustrating a jelly-roll tracking data management method according to an example embodiment. More specifically, Figure 25 is a flowchart for describing a jelly-roll tracking data management method by the secondary battery manufacturing system 1000 in a first sub-process described in Figure 23

[0314] Since the method of Figure 25 can be performed by the secondary battery manufacturing system 1000 of Figure 2 , any description overlapping with the above can be omitted, and the method can be described using the configuration of Figure 2

[0315] Figure 25 The example embodiments illustrated are merely example embodiments, and the order of operations according to various example embodiments of the disclosure can differ from the order illustrated in Figure 25 , some of the operations illustrated can change order between operations, or can be combined. Figure 25

[0316] Referring to Figure 25 ​​​​​​In operation P710, the secondary battery manufacturing system 1000 can identify a tray ID by detecting a code object of a tray on which a jelly-roll is loaded. Here, the code object can be a code image including information about an ID of a target detected and identified by a code reader (e.g., the matrix reader 111a, 111b, 111c, 111d, 111e, 111f, 111g, 111h, 111i, 111j, 111m, or 111n), and can be implemented as at least one of a data matrix, a QR code, and a bar code.

[0317] In operation P720, the secondary battery manufacturing system 1000 can load an electrode batch ID and an electrode count of the jelly-roll. Here, the electrode count can indicate an order in which the jelly-roll is manufactured in a winding apparatus.

[0318] According to an example embodiment, the secondary battery manufacturing system 1000 can load the electrode batch ID and the electrode count of the jelly-roll with the identification of the tray ID in operation P710 as a trigger. For example, the secondary battery manufacturing system 1000 can load a positive electrode batch ID and a positive electrode count from a server such as an MES. As another example, the secondary battery manufacturing system 1000 can also load a negative electrode batch ID and a negative electrode count from a server such as an MES.

[0319] In operation P730, the secondary battery manufacturing system 1000 can determine tray coordinates of the jelly-roll on the tray. According to an example embodiment, the secondary battery manufacturing system 1000 can determine the tray coordinates of the jelly-roll on the tray based on an operation of a pick-and-place machine that moves the jelly-roll loaded on the tray to the first carrier 115a in the first sub-process.

[0320] In operation P740, the secondary battery manufacturing system 1000 can generate a jelly-roll ID corresponding to the jelly-roll. For example, the jelly-roll ID can be a virtual ID generated using data related to the jelly-roll.

[0321] According to an example embodiment, the secondary battery manufacturing system 1000 can generate the jelly-roll ID based on the tray ID identified in operation P710. According to an example embodiment, the secondary battery manufacturing system 1000 can generate the jelly-roll ID based on at least one of the electrode batch ID and the electrode count loaded in operation P720 and the tray coordinates determined in operation P730, in addition to the tray ID identified in operation P710.

[0322] In operation P750, the secondary battery manufacturing system 1000 can identify a first carrier ID by detecting a code object of the first carrier 115a on which the jelly-roll is loaded.

[0323] In operation P760, the secondary battery manufacturing system 1000 can match the jelly-roll ID generated in operation P740 and the first carrier ID identified in operation P750. According to an example embodiment, the secondary battery manufacturing system 1000 can match the jelly-roll ID and the first carrier ID by comparing a time at which the jelly-roll ID is generated in operation P740 and a time at which the first carrier ID is identified in operation P750. For example, if a time interval between the time at which the jelly-roll ID is generated and the time at which the carrier ID is identified is within a preset threshold time value, the generated jelly-roll ID and the identified carrier ID can be matched to each other. In contrast, if the time interval between the time at which the jelly-roll ID is generated and the time at which the carrier ID is identified exceeds the preset threshold time value, the generated jelly-roll ID can be matched to another carrier ID with which the time interval is within the threshold time value.

[0324] Figure 26 FIG. 10 is a flowchart illustrating a jelly-roll tracking data management method according to an example embodiment. More specifically, Figure 26 FIG. 11 is a flowchart for describing a jelly-roll tracking data management method by the secondary battery manufacturing system 1000 in a second sub-process described in Figure 23 FIG. 12 is a flowchart for describing a jelly-roll tracking data management method by the secondary battery manufacturing system 1000 in a second sub-process described in

[0325] Since the method of Figure 26 can be performed by the secondary battery manufacturing system 1000 of Figure 2 , any description overlapping the above can be omitted, and the method can be described using the configuration of Figure 2 .

[0326] Figure 26 The example embodiments illustrated in Figure 26 may be different from the order illustrated in Figure 26 , some operations illustrated in may be omitted, the order between operations can be changed, or operations can be merged.

[0327] Figure 26 Referring to Figure 24 , in operation P810, the secondary battery manufacturing system 1000 can identify the first carrier ID by detecting a code object of the first carrier 115a. Operation P810 described herein can be an operation different from operation P750 of Figure 23 . Specifically, operation P750 of

[0328] may be an operation of identifying the first carrier ID during the first sub-process, and operation P810 can be an operation of identifying the first carrier ID during the second sub-process.

[0329] In operation P830, the secondary battery manufacturing system 1000 can match the first carrier ID identified in operation P810 and the second carrier ID identified in operation P820. According to an example embodiment, the secondary battery manufacturing system 1000 can match the first carrier ID and the second carrier ID by comparing a time at which the first carrier ID is identified in operation P810 and a time at which the second carrier ID is identified in operation P820. For example, if a time interval between the identification times of the first carrier ID and the second carrier ID is within a preset threshold time value, the identified first carrier ID and the second carrier ID can be matched to each other. In contrast, if the time interval between the identification times of the first carrier ID and the second carrier ID exceeds the preset threshold time value, the identified first carrier ID can be matched to another second carrier ID whose time interval is within the threshold time value.

[0330] According to an example embodiment, the secondary battery manufacturing system 1000 can store a match between the jelly-roll ID and the first carrier ID of operation P760. Figure 25 Accordingly, as in operation P630 of FIG. 6, Figure 24 Accordingly, as in operation P630 of FIG. 6,

[0331] Figure 27 is a flowchart illustrating a jelly-roll tracking data management method according to an example embodiment.

[0332] Since the method of Figure 27 can be performed by the secondary battery manufacturing system 1000 of Figure 2 , any description overlapping with the above can be omitted, and the method can be described using the configuration of Figure 2 .

[0333] Figure 27 The example embodiments illustrated in Figure 27 may be different from the order illustrated in Figure 27 may be omitted, the order between operations can be changed, or operations can be merged.

[0334] Referring to Figure 27 , in operation P910, the secondary battery manufacturing system 1000 can obtain a jelly-roll ID corresponding to a jelly-roll based on a first sub-process. Operation P910 can be the same operation as operation P610 of FIG. 6. Figure 24

[0335] ​In operation P920, the secondary battery manufacturing system 1000 can obtain a can ID corresponding to the cell case into which the jelly-roll is inserted, based on the third sub-process. For example, the third sub-process can be a process P50 of the manufacturing processes performed by the secondary battery manufacturing system 1000. Figure 1

[0336] In operation P930, the secondary battery manufacturing system 1000 can match the jelly-roll ID obtained in operation P910 and the can ID obtained in operation P920. The operation P930 of the secondary battery manufacturing system 1000 to match the jelly-roll ID and the can ID can be described in more detail below. Figure 28

[0337] Figure 28 is a flowchart illustrating a cell tracking data management method according to an example embodiment. More specifically, Figure 28 is a flowchart for describing a cell tracking data management method in the third sub-process described in Figure 27 by the secondary battery manufacturing system 1000.

[0338] Since the method of Figure 28 can be performed by the secondary battery manufacturing system 1000 of Figure 2 , any description overlapping with the above can be omitted, and the method can be described using the configuration of Figure 2 .

[0339] Figure 28 The example embodiments illustrated in Figure 28 may be different from the order illustrated in Figure 28 , some operations illustrated in may be omitted, the order between operations can be changed, or operations can be merged.

[0340] Figure 28 Referring to Figure 26 , in operation P1010, the secondary battery manufacturing system 1000 can identify a second carrier ID by detecting a code object of the second carrier 115b. The operation P1010 described herein can be an operation different from the operation P830 of Figure 26 . Specifically, the operation P830 of

[0341] may be an operation to identify a second carrier ID during a second sub-process, and the operation P1010 can be an operation to identify a second carrier ID during a third sub-process.

[0342] ​In operation P1030, the secondary battery manufacturing system 1000 can match the second carrier ID identified in operation P1010 and the can ID identified in operation P1020. According to an example embodiment, the secondary battery manufacturing system 1000 can match the second carrier ID and the can ID by comparing the time at which the second carrier ID is identified in operation P1010 and the time at which the can ID is identified in operation P1020. For example, if the time interval between the identification time of the second carrier ID and the identification time of the can ID is within a preset threshold time value, the identified second carrier ID and the identified can ID can be matched to each other. In contrast, if the time interval between the identification time of the second carrier ID and the identification time of the can ID exceeds the preset threshold time value, the identified second carrier ID can be matched to another can ID with which the time interval is within the threshold time value.

[0343] According to an example embodiment, the secondary battery manufacturing system 1000 can store the match between the jelly-roll ID and the first carrier ID in operation P760 of Figure 25 and store the match between the first carrier ID and the second carrier ID in operation P830 of Figure 26 Accordingly, the secondary battery manufacturing system 1000 can match the jelly-roll ID based on the first sub-process and the can ID obtained based on the third sub-process through the second carrier ID as in operation P930 of Figure 27

[0344] As described above, the present disclosure is described in more detail through the drawings and example embodiments. However, the example embodiments described in the present disclosure and the configurations shown in the drawings are only example embodiments of the present disclosure and do not completely cover the technical idea of the present disclosure, and thus it should be understood that various equivalents and modified examples can exist as alternatives thereto at the time of filing the present application.​

Claims

1. A method for managing battery cell tracking data, the method comprising the following steps: Loading cell tracking data, the cell tracking data including an unidentified core identifier (ID) and core IDs adjacent to the unidentified core ID, wherein the core ID is used to distinguish cores, and the core is a wound structure of positive electrode, negative electrode, and separator; and The unrecognized core ID is recovered based on the core ID.

2. The cell tracking data management method according to claim 1, in, The core ID precedes the unrecognized core ID.

3. The cell tracking data management method according to claim 1, in, The core ID follows the unrecognized core ID.

4. The cell tracking data management method according to claim 1, in, The winding core is fed into the assembly process of the secondary battery, and Wherein, the core ID includes a symbol representing the input order of the core, and The unidentified cartridge ID is restored to a value in which the symbol representing the input order of the cartridge ID is changed.

5. The cell tracking data management method according to claim 4, in, The symbols were changed to indicate the order of precedence.

6. The cell tracking data management method according to claim 4, in, The symbol was changed to indicate the subsequent order.

7. A method for managing battery cell tracking data, the method comprising the following steps: Loading cell tracking data including an unidentified can ID and can IDs adjacent to the unidentified can ID, wherein the can ID is used to distinguish cell housings for inserting cores, the cores being a wound structure of positive electrode, negative electrode, and separator; and The unidentified tank ID is recovered based on the tank ID. Specifically, the can ID is determined by reading the data matrix of the battery cell casing, and The unidentified tank ID is determined by the failure to read the data matrix.

8. The cell tracking data management method according to claim 7, in, The can ID is mentioned before the unidentified can ID.

9. The cell tracking data management method according to claim 7, in, The can ID follows the unidentified can ID.

10. The cell tracking data management method according to claim 7, in, The can is fed into the assembly process of the secondary battery, and Wherein, the can ID includes a symbol representing the input order of the cell casing, and The unidentified can ID is restored to a value in which the symbol representing the input order of the can ID is changed.

11. The cell tracking data management method according to claim 10, in, The symbols were changed to indicate the order of precedence.

12. The cell tracking data management method according to claim 10, in, The symbol was changed to indicate a later order.

13. A method for managing battery cell tracking data, the method comprising the following steps: Load the dataset for recovery, which includes the first cell tracking data and the second cell tracking data; as well as The unidentified tank ID of the first cell tracking data is recovered based on the dataset used for recovery. Specifically, the first cell tracking data is collected from a first sub-equipment of a first sub-process configured to perform the assembly process of the battery cell. Specifically, the second cell tracking data is collected from a second sub-device of a second sub-process configured to perform the assembly process of the battery cell. The first cell tracking data and the second cell tracking data include multiple tank IDs. The can ID is used to distinguish the cell housing into which the core is inserted. The core is a wound structure consisting of a positive electrode, a negative electrode, and a separator. Specifically, the can ID is determined by reading the data matrix of the battery cell casing, and The unidentified tank ID is determined by the failure to read the data matrix.

14. The cell tracking data management method according to claim 13, in, The second sub-process is executed after the first sub-process is executed.

15. The cell tracking data management method according to claim 13, in, The second sub-process is executed before the first sub-process is executed.

16. The cell tracking data management method according to claim 13, in, The plurality of can IDs includes a first can ID preceding the unidentified can ID and a second can ID following the unidentified can ID, and The unidentified tank ID is recovered based on the portion of the second cell tracking data between the first tank ID and the second tank ID.

17. The cell tracking data management method according to claim 16, in, The unidentified can ID is recovered to one of the can IDs in the second cell tracking data that exists between the first can ID and the second can ID.

18. The cell tracking data management method according to claim 16, in, The unidentified tank ID is recovered based on either the first tank ID or the second tank ID.

19. A method for managing battery cell tracking data, the method comprising the following steps: Load the dataset for recovery, which includes the first cell tracking data and the second cell tracking data; as well as Recover the unidentified tank ID from the first cell tracking data. Specifically, the first cell tracking data is collected from a first sub-equipment of a first sub-process configured to perform the assembly process of the battery cell. Specifically, the second cell tracking data is collected from a second sub-device of a second sub-process configured to perform the assembly process of the battery cell. The first cell tracking data and the second cell tracking data include multiple tank IDs. The can ID is used to distinguish battery cells, which include a core and a cell casing. The core is a wound structure consisting of a positive electrode, a negative electrode, and a separator. The cell casing is for inserting the core. Specifically, the can ID is determined by reading the data matrix of the battery cell casing, and The unidentified tank ID is determined by the failure to read the data matrix.

20. The cell tracking data management method according to claim 19, in, The second sub-process is executed after the first sub-process is executed.

21. The cell tracking data management method according to claim 19, in, The second sub-process is executed before the first sub-process is executed.

22. The cell tracking data management method according to claim 19, in, The plurality of can IDs includes a first can ID preceding the unidentified can ID and a second can ID following the unidentified can ID, and The unidentified tank ID is recovered based on the portion of the second cell tracking data between the first tank ID and the second tank ID.

23. The cell tracking data management method according to claim 22, in, The unidentified tank ID is recovered to the batch ID that exists between the first tank ID and the second tank ID among the plurality of batch IDs in the second cell tracking data.

24. A method for managing battery cell tracking data, the method comprising the following steps: A first data window for recovery is configured based on the first cell tracking data, and a second data window for recovery is configured based on the second cell tracking data; as well as The unidentified tank ID of the first cell tracking data is recovered based on the second data window used for recovery. Specifically, the first cell tracking data is collected from a first sub-equipment of a first sub-process configured to perform the assembly process of the battery cell. Specifically, the second cell tracking data is collected from a second sub-device of a second sub-process configured to perform the assembly process of the battery cell. The first cell tracking data and the second cell tracking data include multiple tank IDs. The can ID is used to distinguish battery cells, which include a winding core and a cell casing. The winding core is a wound structure consisting of a positive electrode, a negative electrode, and a separator. The cell casing is for inserting the winding core. When the determination of the multiple tank IDs fails, the unidentified tank ID is generated.

25. The cell tracking data management method according to claim 24, in, The second sub-process is executed after the first sub-process is executed.

26. The cell tracking data management method according to claim 24, in, The second sub-process is executed before the first sub-process is executed.

27. The cell tracking data management method according to claim 24, in, The first data window for recovery includes a first tank ID and a second tank ID, wherein the first tank ID is the first tank ID included in the plurality of tank IDs in the first data window for recovery, and the second tank ID is the last tank ID included in the plurality of tank IDs in the first data window for recovery. The second data window used for recovery includes the tank IDs between the first tank ID and the second tank ID among the plurality of tank IDs.

28. The cell tracking data management method according to claim 27, in, The unidentified tank ID of the first cell tracking data is recovered by matching the first cell tracking data with the tank IDs included in the second data window for recovery from the plurality of tank IDs.

29. The cell tracking data management method according to claim 27, in, The unidentified tank IDs in the first cell tracking data are recovered based on tank IDs that are not present in the first cell tracking data and are included in the second data window for recovery from among the plurality of tank IDs.

Images