Processing history management device, processing history management method, and processing history management program

Abstract

To provide a processing history management device, a processing history management method, and a processing history management program that can visualize a processing history of processing from a base metal to a product.SOLUTION: A processing history management device according to this embodiment includes: processing input means which inputs processing put-out data, processing receipt data, commodity code of lot data, lot number, top level commodity code, top level lot number, master commodity code, master lot number, worker number and asset quantity according to the operation of an operator on an input screen displayed on a display unit when processing a base material or processing a processed commodity and registers them in a storage area; level update means that updates the level, the downward expansion flag, and the sequence of the lot data registered in the storage area; and history output means that creates and outputs an inventory history detail list showing the processing history from the base material to the product on the basis of the updated lot data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a manufacturing history management device, a manufacturing history management method, and a manufacturing history management program. [Background technology]

[0002] For example, in the steel industry, base materials are processed before being shipped as products. Conventionally, a system for managing the processing of base materials is disclosed in, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-61552 Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 does not describe anything about visualizing the processing history from the base material to the finished product.

[0005] The present invention has been made in consideration of the above, and aims to provide a processing history management device, a processing history management method, and a processing history management program that are capable of visualizing the processing history from the base material to the processing into a product. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a processing history management device having a control unit, wherein the control unit is configured to manage processing and releasing data including a processing number, a row, a product code, a lot number, a quantity, and an asset quantity; processing and receiving data including a releasing row which is a row of processing and releasing data of a product to be processed; product code, lot number, a top-level product code which is a product code of a base material that is the source of processing; a top-level lot number which is a lot number of a base material that is the source of processing; a parent product code which is a product code of a product that is the direct source of processing; a parent lot number which is a lot number of a product that is the direct source of processing; a quantity; an asset quantity; a level which indicates which hierarchical level of the processing is from the base material; a lower level expansion flag which indicates whether processing continues afterwards; an inventory history; and lot data including the order to be used as the sorting order of the specification table, and the control unit is characterized by comprising: processing input means for inputting processing release data, processing acceptance data, product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of the lot data in response to operator operations on an input screen displayed on the display unit when processing a base material or when further processing the processed product, and registering them in the storage area; level update means for updating the level, sub-expansion flag, and order of the lot data registered in the storage area; and history output means for creating and outputting an inventory history specification table that shows the processing history from the base material to the finished product based on the updated lot data.

[0007] Furthermore, according to one aspect of the present invention, the history output means may rearrange the lot data in the "order" in which the product code and lot number of the specified base material are the highest-level product code and highest-level lot number, and output the inventory history detail table with the rearranged order of the lot data as the row order, including a history detail table including a hierarchy according to the level, product, lot number, quantity, and asset quantity, and a header section including the product code, lot, quantity, asset quantity, and yield rate of the base material.

[0008] According to one aspect of the present invention, the storage area stores a product master in which product codes are associated with product categories indicating whether or not the product is scrap, and the inventory history detail table includes the yield rate of the base material. The history output means may extract, for the yield rate, records in which the lot data sub-expansion flag = "Do not expand," obtain the product category of the product master using the product code of the extracted record as a key to determine whether or not the product is scrap, and calculate the yield rate as follows: Yield rate = (total asset quantity - scrap asset quantity) / total asset quantity.

[0009] According to another aspect of the present invention, the inventory history detail table may include a hierarchical matrix display based on the level of each product code and product lot number of the lot data.

[0010] According to one aspect of the present invention, the storage area includes a main work for expanding data on the product code, lot number, level, sub-expansion flag, and order, and a parent-child work for expanding data on the parent product code, parent lot number, child product code, child lot number, level, and order, and the level update means (1) acquires data on the highest product code and highest lot number from the lot data in the storage area and expands it in the main work, (2) internally joins data on the product code and lot number of the lot data with the highest product code and highest lot number as the parent product in the main work, and then adds the data excluding itself to the parent work. When the child works are expanded, if the conditions that the product code of the main work = the parent product code of the lot data, the lot number of the main work = the parent lot number of the lot data, and the sub-expansion flag of the main work = no expansion are met, the parent product code and parent lot number of the parent-child works are combined with the main work, and for those that are combined, the sub-expansion flag is updated to "expansion present", the data of the child product code and child lot number of the parent-child works are added to the main work, and the process is repeated until (3) and (2) can no longer be obtained, and (4) the level, sub-expansion flag, and order of the lot data are updated with the values ​​of the main work.

[0011] According to another aspect of the present invention, the base material may include a coil, and the processing may include slitting, leveling, and shearing.

[0012] In order to solve the above-mentioned problems and achieve the object, the present invention provides a processing history management method to be executed by an information processing device having a control unit, wherein the control unit receives processing and shipping data including processing number, row, product code, lot number, quantity, and asset quantity, processing receipt data including processing number, row, product code, lot number, quantity, asset quantity, and shipping rows which are rows of processing and shipping data of a product to be processed, product code, lot number, top-level product code which is the product code of a base material that is the source of processing, top-level lot number which is the lot number of a base material that is the source of processing, parent product code which is the product code of a product that is the direct source of processing, parent lot number which is the lot number of a product that is the direct source of processing, number of items, asset quantity, a level which indicates which hierarchical level of the processing is from the base material, and a lower level expansion flag which indicates whether processing continues or not. and lot data including the order to be used as the sorting order of the inventory history statement, and the control unit is configured to be able to access a memory area that stores the above-mentioned data, and the above-mentioned data includes lot data including the order to be used as the sorting order of the inventory history statement, and the control unit is characterized by including: a processing input process that, when processing a base material or when further processing a processed product, inputs processing release data, processing acceptance data, the product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of the lot data in accordance with operation by an operator on an input screen displayed on the display unit, and registers them in the memory area; a level update process that updates the level, sub-expansion flag, and order of the lot data registered in the memory area; and a history output process that creates and outputs an inventory history statement that shows the processing history from the base material to the product based on the updated lot data.

[0013] In order to solve the above-mentioned problems and achieve the object, the present invention provides a processing history management program to be executed by an information processing device having a control unit, the control unit being configured to process processing and releasing data including a processing number, a row, a product code, a lot number, a quantity, and an asset quantity; processing and receiving data including a releasing row which is a row of processing and releasing data of a product to be processed; product code, lot number, a top-level product code which is a product code of a base material that is the source of processing; a top-level lot number which is a lot number of a base material that is the source of processing; a parent product code which is a product code of a product that is the direct source of processing; a parent lot number which is a lot number of a product that is the direct source of processing; a quantity; an asset quantity; a level which indicates which hierarchical level of the processing is from the base material; a lower level expansion flag which indicates whether processing continues afterwards; an inventory history clearing flag; and lot data including an order to be used as the order of the detailed table, and the control unit executes a processing input step in which, when processing a base material or when further processing a processed product, the control unit inputs processing withdrawal data, processing acceptance data, product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of the lot data in accordance with operations by an operator on an input screen displayed on the display unit, and registers them in the storage area; a level update step in which the level, sub-expansion flag, and order of the lot data registered in the storage area are updated; and a history output step in which, based on the updated lot data, an inventory history statement is created and output that shows the processing history from the base material to the finished product. [Effects of the Invention]

[0014] According to the present invention, it is possible to visualize the processing history from the base material to the finished product. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a manufacturing history management device according to this embodiment. [Figure 2]FIG. 2 is a block diagram showing an example of the configuration of the product master. [Figure 3] FIG. 3 is a flowchart illustrating an outline of the overall processing of the control unit of the information processing device according to this embodiment. [Figure 4] FIG. 4 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 5] FIG. 5 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 6] FIG. 6 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 7] FIG. 7 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 8] FIG. 8 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 9] FIG. 9 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 10] FIG. 10 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 11] FIG. 11 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. [Figure 12] FIG. 12 is a diagram showing sample data for explaining a specific example of processing by the control unit of the information processing device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0017] [1. Overview] For example, in the steel industry, when processing a base material to create a product, the relationship between the material and the product is N:M, making it impossible to unfold (confirm) the processing history from the base material to the product. For example, at a coil center, the base material coil is slit into multiple pieces, and then the slit coils are leveled to create plates, after which the multiple plates are sheared, making it difficult to confirm the processing history from the base material to the final sheared plate.

[0018] Therefore, in this embodiment, a system is provided that can visualize the processing history from the base material to the finished product at once.

[0019] According to this embodiment, for example, by visualizing the process of processing (slitting, leveling, shearing, etc.) from a base material (e.g., a coil) using an inventory history statement, it becomes possible to check the overall yield from the base material perspective. The inventory history statement also makes it easy to trace from base material to finished products and from finished products to base material. Furthermore, when base material is received as a supply item from a customer for processing, the customer may be asked to present the processing status of the entire base material (proof of work), and presenting the inventory history statement makes it possible to improve work efficiency.

[0020] In the following explanation, we will use as an example the case of processing coils at a coil center, but the present invention is not limited to this and can be widely applied to industries that process base materials, and can be suitably used in, for example, the steel industry.

[0021] [2. Configuration] An example of the configuration of a manufacturing history management device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of a manufacturing history management device 100 according to this embodiment.

[0022] The manufacturing history management device 100 is, for example, a commercially available desktop personal computer. Note that the manufacturing history management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0023] The manufacturing history management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the manufacturing history management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0024] The communication interface unit 104 communicably connects the manufacturing history management device 100 to a network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the manufacturing history management device 100 and the server 200 to each other so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. Furthermore, "output" refers to outputting by the output device 114, and includes, for example, display output to the monitor 114, print output by the printer 114, and sending data to the outside.

[0026] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0027] The storage unit 106 includes a product master 106a, a data table 106b, and a work table 106c. Fig. 2 is a diagram showing an example of the configuration of the product master 106a.

[0028] The product master 106a can be configured as a table or the like that associates and registers product codes with grades (for example, Grade 1, Scrap) that indicate whether the product is scrap or not, as shown in Fig. 2. In the example shown in the figure, the grade "Grade 1" is set for product codes "1000" to "4000", and the grade "Scrap" is set for product code "4001".

[0029] The data table 106b is a table for storing various data such as processing and delivery data, processing and receipt data, and lot data.

[0030] The processing payment data may include a processing number, a line, a product code (product identification information), a lot number (lot identification information), a quantity, and an asset quantity.

[0031] The processing acceptance data may include a processing number, a line, a product code, a lot number, a quantity, an asset quantity, and a delivery line number, which is a line of processing delivery data for the product to be processed.

[0032] Lot data may include the product code, lot number, top-level product code, which is the product code of the base material used for processing, top-level lot number, which is the lot number of the base material used for processing, parent product code, which is the product code of the product directly used for processing, parent lot number, which is the lot number of the product directly used for processing, quantity, asset quantity, level, which indicates the level of processing from the base material, a sub-expansion flag indicating whether processing continues (e.g., "1: Sub-expansion available" or "0: Sub-expansion not available"), and a sequence (SEQ) used to sort the inventory history statement. The product code, lot number, top-level product code, top-level lot number, parent product code, parent lot number, quantity, and asset quantity are updated during the processing input process. The level, sub-expansion flag, and sequence are updated during the level update process.

[0033] The work table 106c is a work area used when the level update unit 102c updates the level, lower level development flag, and order of the lot data, and includes areas for a main work and parent-child work.

[0034] The control unit 102 is a CPU or the like that performs overall control of the machining history management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processes based on these stored programs.

[0035] The control unit 102 is configured to be able to access the product master 106a, the data table 106b, the work table 106c, etc. stored in the storage unit 106. The product master 106a, the data table 106b, and the work table 106c may be provided in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0036] The control unit 102 conceptually includes a purchase input unit 102a, a processing input unit 102b, a level update unit 102c, a history output unit 102d, a master maintenance unit 102e, and a screen display control unit 102f.

[0037] The purchase input unit 102a inputs the product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of lot data for the base material in response to, for example, an operator's operation on a purchase input screen (not shown) displayed on the monitor 114, and registers the input in the data table 106b.

[0038] When processing a base material or when further processing the processed product, the processing input unit 102b inputs and updates the processing release data, processing acceptance data, and lot data product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity in response to, for example, an operator's operation on a processing input screen (see FIG. 5, etc.) displayed on the monitor 114, and registers them in the data table 106b.

[0039] The level update unit 102c uses the main work and parent-child work of the work table 106c to update the level, the lower development flag, and the order of the lot data.

[0040] The level update unit 102c (1) acquires the data of the highest-level product code and the highest-level lot number from the lot data in the data table 106b and expands it into the main work, (2) internally joins the data of the product code and lot number of the lot data having the highest-level product code and the highest-level lot number as the parent product into the main work, and expands the data excluding itself into the parent-child work, and if the conditions that the product code of the main work = the parent product code of the lot data, the lot number of the main work = the parent lot number of the lot data, and the sub-expansion flag of the main work = no expansion are met, it joins the parent product code and parent lot number of the parent-child work with the main work, updates the sub-expansion flag of the joined items to "expansion enabled", adds the data of the child product code and child lot number of the parent-child work to the main work, and (3) repeats the process until (2) can no longer be acquired, and (4) updates the level, sub-expansion flag, and order of the lot data with the values ​​of the main work.

[0041] The history output unit 102d, for example, in response to an operator's operation on an inventory history statement output screen (not shown) displayed on the monitor 114, references lot data for the specified base material and displays an inventory history statement.

[0042] The history output unit 102d may rearrange the lot data in which the product code and lot number of the specified base material are the highest-level product code and highest-level lot number in that "order," and output the inventory history detail table with the rearranged lot data order as the row order, including a history detail table including a hierarchy according to the level, product, lot number, number of units, and asset quantity, and a header section including the product code, lot, number of units, asset quantity, and yield rate of the base material.

[0043] The history output unit 102d may extract records in which the lot data sub-expansion flag = "Do not expand" for the yield rate, obtain the product classification of the product master 106a using the product code of the extracted record as a key, determine whether or not the product is scrap, and calculate the yield rate as follows: (total asset quantity - scrap asset quantity) / total asset quantity.

[0044] The inventory history detail table may include a hierarchical matrix display based on the level of each product code and product lot number in the lot data.

[0045] The master maintenance section 102e is used to perform settings such as inputting, adding, changing, and updating data for the product master 106a in response to an operator's operation on a master maintenance screen (not shown).

[0046] The screen display control unit 102f controls the display of various input screens (for example, purchase input screen, processing input screen, inventory history statement output screen, etc.) displayed on the monitor 114 and the reception of inputs on the screens.

[0047] [3. Specific Examples] A specific example of the processing performed by the control unit 102 of the manufacturing history management device 100 according to this embodiment will be described with reference to FIGS.

[0048] (3-1. Overall processing) 3 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the manufacturing history management device 100 according to the present embodiment. With reference to FIG. 3, an outline of the overall processing of the control unit 102 of the manufacturing history management device 100 according to the present embodiment will be described.

[0049] 3, the purchase input unit 102a executes a purchase input process (step S1). Specifically, in the purchase input process, the purchase input unit 102a inputs the product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of lot data for the base material in response to, for example, an operator's operation on a purchase input screen (not shown) displayed on the monitor 114, and registers the input data in the data table 106b.

[0050] The processing input unit 102b executes the processing input process (step S2). The processing input process is executed as many times as the number of processing steps. Specifically, in the processing input process, when processing a base material or when further processing the processed product, the processing input unit 102b inputs and updates the processing release data, processing acceptance data, and lot data product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity in accordance with, for example, an operator's operation on the processing input screen displayed on the monitor 114, and registers them in the data table 106b.

[0051] The level update unit 102c executes a level update process (step S3). Specifically, in the level update process, the level update unit 102c uses the work table 106c to update the level, the lower expansion flag, and the order of the lot data stored in the data table 106b.

[0052] In this case, the level update unit 102c (1) acquires the data of the highest-level product code and highest-level lot number from the lot data in the data table 106b and expands it into the main work, (2) internally joins the data of the product code and lot number of the lot data having the highest-level product code and highest-level lot number as the parent product into the main work, and expands the data excluding itself into the parent-child work, and if the conditions that the product code of the main work = the parent product code of the lot data, the lot number of the main work = the parent lot number of the lot data, and the sub-expansion flag of the main work = no expansion are met, it joins the parent product code and parent lot number of the parent-child work with the main work, updates the sub-expansion flag of the joined items to "expansion enabled", adds the data of the child product code and child lot number of the parent-child work to the main work, and (3) repeats the process until (2) can no longer be acquired, and (4) updates the level, sub-expansion flag, and order of the lot data with the values ​​of the main work.

[0053] The history output unit 102d executes an inventory history statement output process (step S4). Specifically, in the inventory history statement output process, the history output unit 102d outputs and displays an inventory history statement based on the lot data stored in the data table 106b, in response to, for example, an operator's operation on an inventory history statement output screen (not shown) displayed on the monitor 114.

[0054] In this case, the history output unit 102d may rearrange the lot data in which the product code and lot number of the specified base material are the highest-level product code and highest-level lot number in that "order," and output the inventory history detail table with the rearranged lot data order as the row order, including a history detail table including a hierarchy according to the level, product, lot number, quantity, and asset quantity, and a header section including the product code, lot, quantity, asset quantity, and yield rate of the base material.

[0055] The history output unit 102d may extract records in which the lot data sub-expansion flag = "Do not expand" for the yield rate, obtain the product classification of the product master 106a using the product code of the extracted record as a key, determine whether or not the product is scrap, and calculate the yield rate as follows: (total asset quantity - scrap asset quantity) / total asset quantity.

[0056] The inventory history detail table may include a hierarchical matrix display based on the level of each product code and product lot number in the lot data.

[0057] (3-2. Sample data) 4 to 12 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the manufacturing history management device 100 according to the present embodiment. A specific example of the processing by the control unit 102 of the manufacturing history management device 100 according to the present embodiment will be explained with reference to FIGS.

[0058] (Example of base material processing process) Figure 4 is a diagram for explaining an example of a base material processing process. In the following explanation, we will explain the transition of processing withdrawal data, processing acceptance data, lot data, and inventory history statement when processing a base material as shown in Figure 4.

[0059] The example shown in Figure 4 shows a case where a coil, which is the base material, is purchased at a coil center, and the base material coil is slit in process K1, then slit and leveled in process K2, and finally sheared in process K3.

[0060] The base material coil has product code "1000," product category "base material," lot number "A," and weight "50 kg."

[0061] The base coil is slit in process K1 to create two slit coils. The two slit coils have product code "2000", product category "In-process", lot "B-1", and weight "25 kg", and the other has product code "2000", product category "In-process", lot "B-2", and weight "25 kg".

[0062] Next, in process K2, the slit coil from lot "B-2" is slit into five strips and then leveled into plates. One sheet has product code "3000," product category "product," lot "C-1," and weight "5 kg," while the other four have product code "3001," product category "work in progress," lot "C-2," and weight "5 kg."

[0063] Finally, in process K3, the board from lot "C-1" is sheared into five pieces, and each of the five boards will have the product code "4000," product category "product," lot "D-1," and weight "1 kg."Furthermore, the four boards from lot "C-2" are sheared into 18 pieces, and each of the 18 pieces will have the product code "4000," product category "product," lot "D-2," and weight "1 kg," with the remainder (scrap) having the product code "4001," product category "end board," lot "D-3," and weight "2 kg."

[0064] (Processing input processing: S2) The processing input process will be described in detail with reference to Figures 5 to 10. The processing input process is executed the same number of times as the number of processes. When processing a base material or when further processing the processed product, the processing input unit 102b inputs and updates the processing release data, processing acceptance data, and lot data product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity in response to, for example, an operator's operation on the processing input screen displayed on the monitor 114, and registers them in the data table 106b.

[0065] (Processing K1) Fig. 5 is a diagram for explaining processing K1. Fig. 5(A) is a diagram showing an example of the display of the processing input screen for processing K1. The processing input screen has a field for inputting the processing date, a sending out area for inputting processing sending out data, a receiving area for inputting processing receiving data, and a register button. In the sending out area, for the processing sending out object, the product code, lot number, quantity, and asset quantity (kg) are entered for each line number. In the receiving area, for the processing receiving object, the product code, sending out line number (number), lot number, quantity, and asset quantity (kg) are entered for each line number.

[0066] When data is entered for the processing date, unloading area, and receiving area and the registration button is pressed, the processed unloading data, processed receiving data, and lot data are registered in data table 106b. When data such as that shown in Figure 5(A) is entered and the registration button is pressed, the processed unloading data, processed receiving data, and lot data are registered as shown in Figures 5(B) to (D).

[0067] 5(B) is a diagram showing an example of processing and issuing data. The processing and issuing data has the following fields: processing number, line, product code, lot number, quantity, and asset quantity (e.g., kg). In the example shown in the figure, the first line contains processing number "KA001," line "1," product code "1000," lot number "A," quantity "1," and asset quantity "50."

[0068] 5(C) is a diagram showing an example of processing acceptance data. The processing acceptance data has the following fields: processing number, line, product code, lot number, quantity, asset quantity, and dispensing line number (number). In the example shown in the figure, the first line has processing number "KA001," line "1," product code "2000," lot number "B-1," quantity "1," asset quantity "25," and dispensing line number "1." The second line has processing number "KA001," line "2," product code "2000," lot number "B-2," quantity "1," asset quantity "25," and dispensing line number "1."

[0069] FIG. 5(D) is a diagram showing an example of lot data. The lot data includes the following items: product code, lot number, top-level product code, top-level lot number, parent product code, parent lot number, quantity, asset quantity, level, sub-expansion flag, and order. The level, sub-expansion flag, and order are updated in the level update process. The lot data is updated when the base material is purchased, when the base material is processed, or when the processed base material is further processed.

[0070] The top-level product code is the product code of the base material for the product with that product code (product accepted for processing). The top-level lot number is the lot number of the base material for the product with that product code (product accepted for processing). The parent product code is the product code of the product from which the product is processed (product to be shipped for processing) used when processing the product with that product code (product accepted for processing). The parent lot number is the lot number of the product from which the product is processed (product to be shipped for processing) used when processing the product with that product code (product accepted for processing).

[0071] The top-level product code and top-level lot number are copied from the product code and lot number of the base material. The parent product code and parent lot number are copied from the product code and lot number of the parent product. The base material is the top-level product, products processed from the base material are child products with the base material as the parent product, and products further processed from the processed product of that base material are child products with the processed product of that base material as the parent product.

[0072] In the example shown in the figure, the first line contains data about the base material, including product code "1000," lot number "A," top-level product code "1000," top-level lot number "A," parent product code "1000," parent lot number "A," quantity "1," and asset quantity "50." The lot data about the base material is registered by the purchase input process when the base material is purchased.

[0073] The second line contains product code "2000", lot number "B-1", top product code "1000", top lot number "A", parent product code "1000", parent lot number "A", quantity "1", and asset quantity "25". The third line contains product code "2000", lot number "B-2", top product code "1000", top lot number "A", parent product code "1000", parent lot number "A", quantity "1", and asset quantity "25", and these are registered by the processing input process.

[0074] For product code "2000" and lot number "B-1" and product code "2000" and lot number "B-2", the parent product and top-level product is product code "1000", so the top-level product code, top-level lot number, parent product code, and parent lot number are registered as product code "1000" and lot number "A".

[0075] (Processing K2) 6 and 7 are diagrams for explaining processing K2. Fig. 6 is a diagram showing a display example of a processing input screen for processing K2. When data as shown in Fig. 6 is entered and the registration button is pressed, processing delivery data, processing acceptance data, and lot data as shown in Figs. 7(B) to (D) are registered.

[0076] 7(B) is a diagram showing an example of processing and delivery data. In the example shown in the figure, the first line has registered the processing number "KA002", line "1", product code "2000", lot number "B-2", quantity "1", and asset quantity "25".

[0077] 7(C) is a diagram showing an example of processing receipt data. In the example shown in the figure, the first line has the processing number "KA002", line "1", product code "3000", lot number "C-1", quantity "1 piece", asset quantity "5", and delivery line number "1", and the second line has the processing number "KA002", line "2", product code "3001", lot number "C-2", quantity "4 pieces", asset quantity "20", and delivery line number "1".

[0078] 7(D) is a diagram showing an example of lot data. In the example shown in the drawing, the following are registered on the fourth line: product code "3000," lot number "C-1," top-level product code "1000," top-level lot number "A," parent product code "2000," parent lot number "B-2," quantity "1," and asset quantity "5." On the fifth line: product code "3001," lot number "C-1," top-level product code "1000," top-level lot number "A," parent product code "2000," parent lot number "B-2," quantity "4," and asset quantity "20."

[0079] (Processing K3) 8 and 9 are diagrams for explaining processing K3. Fig. 8 is a diagram showing an example of the display of the processing input screen for processing step K3. When data as shown in Fig. 8 is entered and the registration button is pressed, the processing delivery data, processing acceptance data, and lot data as shown in Figs. 9(B) to (D) are registered.

[0080] 9(B) is a diagram showing an example of processing and delivery data. In the example shown in the figure, the first line has the processing number "KA003", line "1", product code "3000", lot number "C-1", quantity "1", and asset quantity "5", and the second line has the processing number "KA003", line "2", product code "3001", lot number "C-2", quantity "4", and asset quantity "20".

[0081] 9(C) is a diagram showing an example of processing receipt data. In the example shown in the figure, the first line is registered with processing number "KA003", line "1", product code "4000", lot number "D-1", quantity "5", asset quantity "5", and dispensing line number "1". The second line is registered with processing number "KA003", line "2", product code "4000", lot number "D-2", quantity "18", asset quantity "18", and dispensing line number "2". The third line is registered with processing number "KA003", line "3", product code "4001", lot number "D-3", quantity "2", asset quantity "2", and dispensing line number "2".

[0082] 9(D) is a diagram showing an example of lot data. In the example shown in the drawing, the following are registered on the sixth line: product code "4000," lot number "D-1," top-level product code "1000," top-level lot number "A," parent product code "3000," parent lot number "C-1," quantity "5," and asset quantity "5." On the seventh line: product code "4000," lot number "D-2," top-level product code "1000," top-level lot number "A," parent product code "3001," parent lot number "C-2," quantity "18," and asset quantity "18." On the eighth line: product code "4001," lot number "D-3," top-level product code "1000," top-level lot number "A," parent product code "3001," parent lot number "C-2," quantity "2," and asset quantity "2."

[0083] (Level Update: S3) The level update process will be described in detail with reference to Fig. 11. The level update unit 102c uses the main work and parent-child work of the work table 106c to update the level, the lower expansion flag, and the order of the lot data stored in the data table 106b.

[0084] "Level" indicates the number of times (layers) processing occurs from the base material. "Subordinate expansion flag" is a flag that indicates whether processing continues (1 if it continues, 0 otherwise). "Sequence (SEQ)" is a number assigned to visualize inventory tracing, and is used as the sorting order of the inventory history details table.

[0085] The logic of the level update process will be explained.

[0086] (1) Aggregate the top-level product code and top-level lot number data from the lot data and expand it to the main work.

[0087] Figure 11(A) shows an example of data to be expanded in the main work. The main work has areas to store data for the product code, lot number, level, sub-expansion flag, and SEQ. The initial value of the level (variable) is 0.

[0088] In the example shown in the figure, the product code is "1000," the lot number is "A," the level is "0," the sub-expansion flag is "0," and the SEQ is "001." For the product (base material) with the highest product code and highest lot number, the initial settings are level (variable) = "0," sub-expansion flag = "0," and SEQ = "001."

[0089] (2) The parent product code and parent lot number of the lot data are internally joined to the main work, and the records excluding themselves are expanded to the parent-child work.

[0090] Figure 11(B) shows an example of data to be expanded into a parent-child work. The parent-child work has areas for storing data on the parent product code, parent lot number, child product code, child lot number, level, and SEQ. The product code and lot number of the lot data are set as the child product code and child lot number of the parent-child work, respectively. The level (variable) is incremented by 1, as follows: level (variable) = level (variable) + 1. SEQ is the row number within the main work's SEQ + child product lot number (child product > child lot in ascending order, 3 digits filled with 0s).

[0091] In the example shown in the figure, the first line has parent product code "1000," parent lot number "A," child product code "2000," child lot number "B-1," level "1," and SEQ "001001." The SEQ is "001001" by adding the line number "001 (3 digits)" in the child product lot number below the main work SEQ "001."

[0092] The second line will have parent product code "1000", parent lot number "A", child product code "2000", child lot number "B-2", level "1", and SEQ "001002". The SEQ will be "001002" by adding the line number "002 (3 digits)" in the child product lot number to the lower side of the main work SEQ "001".

[0093] The join conditions for the main work and parent work are as follows: Join condition: Main work product code = parent product code of lot data :Main work lot number = parent lot number of lot data : Main work sub-expansion flag = 0 (no expansion)

[0094] (2)-1 Combine the parent product / parent lot of the parent-child work with the main work, and update the sub-expansion flag of the combined work to "1: Expansion". In other words, if there is a parent-child work, set it to "1: Expansion". As shown in FIG. 11(C), the sub-deployment flag for the product code "1000" and lot number "A" is updated to "1."

[0095] (2)-2 Add the child products and child lots of the parent-child work to the main work. As shown in Figure 11(C), records with product code "2000", lot number "B-1", level "1", sub-expansion flag "0", and SEQ "001001" and product code "2000", lot number "B-2", level "1", sub-expansion flag "0", and SEQ "001002" are added.

[0096] (3) Repeat (2) until no more data can be acquired. Here, sample data up to product code "2000" is shown. Product codes "3000" to "4000" are not explained here, but are processed in the same way.

[0097] (4) Update the lot data level, sub-deployment flag, and sequence (SEQ) with the values ​​of the main work. Figure 11(D) shows an example of updating the level, sub-expansion flag, and sequence (SEQ) for product codes "1000" and "2000." For product codes "3000" to "4000," the level, sub-expansion flag, and sequence (SEQ) are updated using the same process, although not shown.

[0098] (Inventory history detail table output process: S4) A specific example of the inventory history statement output process will be described with reference to Fig. 12. The history output unit 102d outputs and displays an inventory history statement for a specified base material based on the lot data stored in the data table 106b, for example, in response to an operator's operation on an inventory history statement output screen (not shown) displayed on the monitor 114. Specifically, the unit sorts the lot data in which the product code and lot number of the specified base material are the highest-level product code and highest-level lot number in their "order," and outputs an inventory history statement with the order of the sorted lot data as the row order, including a hierarchy corresponding to the level, product, lot number, quantity, and asset quantity, and a header section including the product code, lot, quantity, asset quantity, and yield rate of the base material, thereby visualizing the tracing of the base material product lot.

[0099] Visibility is improved by displaying a matrix of rows and layers and identifying the relevant layer in the matrix. The yield rate is calculated by extracting records where the lot data sub-expansion flag is "0: Do not expand" and calculating the yield rate as follows: Yield rate = (total asset quantity - scrap asset quantity) / total asset quantity. In this case, the product code of the extracted record is used as a key to obtain the product category from the product master 106a and determine whether it is scrap or not.

[0100] Figure 12(A) shows the lot data sorted in that order. Sorting by order is generally in ascending order, and when there are data with the same number of digits, their sizes are compared, and if there is data that includes the smaller one, it is ranked higher, and if there is data that further includes the data that includes the smaller one, it is ranked higher, and this process is repeated. For example, in the example shown in Figure 12(A), between the orders "001002001" and "001002002", "001002001" is smaller, and "001002001001" which includes it is ranked higher than "001002002".

[0101] Figure 12(B) shows an example of an output of an inventory history detail table. The inventory history detail table displays a header section including the base material's product code, lot, number of units, asset quantity, and yield rate, and a history detail table including the hierarchy from the base material, product code, lot number, number of units, and asset quantity for products processed from the base material and base.

[0102] In the example shown in the figure, the history detail table displays the hierarchical level, product, lot number, quantity, and asset quantity in row order for the lot data sorted by "order." For the hierarchical levels, the rows and levels are displayed in a matrix format, and the corresponding hierarchical levels are displayed with a "○" in this matrix to improve visibility.

[0103] In addition, the header section displays the base material product code "1000", lot number "A", quantity "1", asset quantity "50 kg", and yield rate "96%".

[0104] 12(C) is a diagram for explaining the method of calculating the yield rate. The yield rate is calculated by extracting records where the lot data sub-expansion flag is "0: Do not expand" and calculating the yield rate as follows: Yield rate = (total asset quantity - scrap asset quantity) / total asset quantity. Scrap is determined by obtaining the product category from the product master 106a using the product code as a key and determining whether it is scrap or not.

[0105] The lot data sub-expansion flag in Figure 12(A) = "0: Do not expand" is product code "2000", lot number "B-1", product code "4000", lot number "D-1", product code "4000", lot number "D-2", product code "4001", and lot number "D-3". However, when product master 106a is referenced, product code "4001" is in the product category "scrap", so the scrap asset quantity is "2 kg", which is the asset quantity for product code "4001" and lot number "D-3" in the lot data.

[0106] As a result, the yield rate = {(total asset quantity "50 kg" - scrap asset quantity "2") / total asset quantity "50 kg"} x 100 = 96%.

[0107] As described above, according to this embodiment, when processing a base material or when further processing a processed product, the system is provided with: a processing input unit 102b that inputs processing release data, processing acceptance data, and the product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of the lot data in accordance with operations by the operator on the input screen displayed on the display unit, and registers these in data table 106b; a level update unit 102c that updates the level, sub-expansion flag, and order of the lot data registered in data table 106b; and a history output unit 102d that creates and outputs an inventory history statement that shows the processing history from the base material to the product based on the updated lot data, making it possible to visualize the processing history from the base material to the product.

[0108] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0109] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0110] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to Goal 16 of the SDGs.

[0111] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0112] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0113] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0114] Furthermore, with regard to the manufacturing history management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0115] For example, all or any part of the processing functions of the manufacturing history management device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing an information processing device to execute the processes described in this embodiment, and is mechanically read by the manufacturing history management device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with an OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM and constitutes the control unit in cooperation with the CPU.

[0116] This computer program may be stored in an application program server connected to the manufacturing history management device 100 via any network, and all or part of it may be downloaded as needed.

[0117] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0118] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0119] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0120] The manufacturing history management device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device connected to any peripheral device. The manufacturing history management device 100 may be realized by installing software (including programs, data, etc.) that causes the device to perform the processes described in this embodiment.

[0121] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0122] 100 Processing history management device 102 Control section 102a Purchase Input Section 102b Processing input section 102c Level Update Section 102d History output section 102e Master Maintenance Department 102f Screen display control unit 104 Communication interface unit 106 Storage section 106a Product Master 106b Data Table 106c Work Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A processing history management device equipped with a control unit, The control unit Processing and issuing data including processing number, line, product code, lot number, quantity, and asset quantity; Processing receipt data including a processing number, a line, a product code, a lot number, a quantity, an asset quantity, and a withdrawal line which is a line of processing withdrawal data for the product from which the processing is made; Lot data including product code, lot number, top-level product code which is the product code of the base material that is the source of processing, top-level lot number which is the lot number of the base material that is the source of processing, parent product code which is the product code of the product that is the direct source of processing, parent lot number which is the lot number of the product that is the direct source of processing, number of items, asset quantity, level which indicates which hierarchical level the processing is at from the base material, lower level expansion flag which indicates whether processing continues or not, and order to be used as the sorting order of the inventory history detail table; The storage area storing the The control unit a processing input means for inputting processing delivery data, processing acceptance data, product code, lot number, top product code, top lot number, parent product code, parent lot number, number of items, and asset quantity of lot data in response to an operator's operation on an input screen displayed on a display unit when processing a base material or when further processing a processed product, and registering the input data in the storage area; a level updating means for updating the level, the lower level development flag, and the order of the lot data registered in the storage area; a history output means for creating and outputting an inventory history statement showing the processing history from the base material to the finished product based on the updated lot data; A processing history management device comprising:

2. 2. The processing history management device according to claim 1, wherein the history output means sorts the lot data in which the product code and lot number of the specified base material are the highest product code and highest lot number in their "order," and outputs the inventory history statement with the order of the sorted lot data as the row order, the history statement including a hierarchy according to the level, product, lot number, number of items, and asset quantity, and a header portion including the product code, lot, number of items, asset quantity, and yield rate of the base material.

3. The storage area includes: The product master is stored in which the product code and the product classification indicating whether or not the product is scrap are associated with each other. The inventory history statement includes a yield rate of a base material, The processing history management device according to claim 1, characterized in that the history output means extracts records of the lot data whose sub-expansion flag is "do not expand" for the yield rate, obtains the product classification of the product master using the product code of the extracted record as a key to determine whether it is scrap or not, and calculates the yield rate as follows: Yield rate = (total asset quantity - scrap asset quantity) / total asset quantity.

4. 2. The manufacturing history management device according to claim 1, wherein the inventory history detail table includes a hierarchical matrix display based on the level of each product code and product lot number of the lot data.

5. The storage area includes: The main work is to expand the data of product code, lot number, level, sub-expansion flag, and order. Parent-child work for expanding data on parent product code, parent lot number, child product code, child lot number, level, and sequence, Equipped with The level update means (1) Obtaining the data of the highest-level product code and the highest-level lot number from the lot data in the storage area and expanding it to the main work; (2) The main work is internally linked with the data of the product code and lot number of the lot data with the top-level product code and top-level lot number as parent products, and the data excluding itself is expanded to the parent-child work. If the conditions that the product code of the main work = the parent product code of the lot data, the lot number of the main work = the parent lot number of the lot data, and the sub-expansion flag of the main work = no expansion are met, the parent product code and parent lot number of the parent-child work are linked with the main work, and the sub-expansion flag of the main work is updated to "expansion enabled" for those that were successfully linked, and the data of the child product code and child lot number of the parent-child work are added to the main work. (3) Repeat the process until (2) can no longer be obtained. (4) The manufacturing history management device according to claim 1, wherein the level, the sub-deployment flag, and the order of the lot data are updated with the value of the main work.

6. 6. The processing history management device according to claim 1, wherein the base material includes a coil, and the processing includes slitting, leveling, and shearing.

7. A processing history management method to be executed by an information processing device having a control unit, The control unit Processing and issuing data including processing number, line, product code, lot number, quantity, and asset quantity; Processing receipt data including a processing number, a line, a product code, a lot number, a quantity, an asset quantity, and a withdrawal line which is a line of processing withdrawal data for the product from which the processing is made; Lot data including product code, lot number, top-level product code which is the product code of the base material that is the source of processing, top-level lot number which is the lot number of the base material that is the source of processing, parent product code which is the product code of the product that is the direct source of processing, parent lot number which is the lot number of the product that is the direct source of processing, number of items, asset quantity, level which indicates which hierarchical level the processing is at from the base material, lower level expansion flag which indicates whether processing continues or not, and order to be used as the sorting order of the inventory history detail table; The storage area storing the Executed in the control unit: a processing input step of inputting processing delivery data, processing acceptance data, product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of lot data in response to an operator's operation on an input screen displayed on a display unit when processing a base material or when further processing a processed product, and registering the input data in the storage area; a level updating step of updating the level, the lower level development flag, and the order of the lot data registered in the storage area; a history output process for creating and outputting an inventory history statement showing the processing history from the base material to the finished product based on the updated lot data; A processing history management method comprising:

8. A processing history management program to be executed by an information processing device having a control unit, The control unit Processing and issuing data including processing number, line, product code, lot number, quantity, and asset quantity; Processing receipt data including a processing number, a line, a product code, a lot number, a quantity, an asset quantity, and a withdrawal line which is a line of processing withdrawal data for the product from which the processing is made; Lot data including product code, lot number, top-level product code which is the product code of the base material that is the source of processing, top-level lot number which is the lot number of the base material that is the source of processing, parent product code which is the product code of the product that is the direct source of processing, parent lot number which is the lot number of the product that is the direct source of processing, number of items, asset quantity, level which indicates which hierarchical level the processing is at from the base material, lower level expansion flag which indicates whether processing continues or not, and order to be used as the sorting order of the inventory history detail table; The storage area storing the In the control unit, a processing input step of inputting processing delivery data, processing acceptance data, product code, lot number, top product code, top lot number, parent product code, parent lot number, quantity, and asset quantity of lot data in response to an operator's operation on an input screen displayed on a display unit when processing a base material or when further processing a processed product, and registering the input data in the storage area; a level updating step of updating the level, the lower level development flag, and the order of the lot data registered in the storage area; a history output process for creating and outputting an inventory history statement showing the processing history from the base material to the finished product based on the updated lot data; A processing history management program for executing the above.

Images