JP2009009190A - Traceability management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a traceability management device for quickly retrieving components to be used for products in assembling and machining industry. <P>SOLUTION: A traceability management device 1 comprises a trace configuration generation unit 7 generating trace link data by associating a lot No. in its header data retrieved from a header database DB2 and including inputted event data, with a trace lot No. in actual achievement data retrieved from an actual achievement database DB3 and including the inputted event data; a trace database DB9 storing the trace link data; and a display data collection unit 10 retrieving, from the trace database DB9, the trace link data having the inputted lot No. and displaying a trace lot No. in the trace link data on a display. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a traceability management apparatus that performs traceability management in an assembly processing industry.

In the case of performing traceability management in the assembly processing industry, data indicating the parts used in the product is sequentially raised from the assembly processing line to the traceability management device. This data includes various information such as assembly processing start time and assembly processing end time. (For example, see Patent Document 1)
JP-A-10-320014

  However, in the existing traceability management apparatus, when searching for parts used in a product specified by the user using data obtained from the assembly processing line as it is, it takes time to search for those parts. is there. For example, when a plurality of parts used in a certain product are accumulated for each different assembly process, the database for accessing the product and the assembly process and accessing the assembly process is connected. After accessing, it is necessary to access a plurality of databases each time a part is searched, such as accessing a database in which an assembly process and a part are associated with each other. And if it takes time to search for parts in this way, the efficiency of traceability management is reduced.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a traceability management apparatus capable of quickly searching which part is used for which product in the assembly processing industry.

In order to solve the above problems, the present invention adopts the following configuration.
That is, the traceability management device of the present invention is a traceability management device that performs traceability management in the assembly processing industry, and among the data obtained from the assembly processing line, event data for identifying a predetermined unit assembly processing step, Header storage means for storing header data composed of assembly processed product data indicating an assembly processed product, and for assembling the event data and the assembly processed product among data obtained from the assembly processing line The result storage means for storing the result data composed of the part data indicating the parts necessary for the search, and the header data having the same data as the input event data are searched from the header storage means, and the header data in the searched header data The assembly work product data and the same data as the event data input Comprising a tracing configuration creating means for creating a trace link data actual data in association with the component data in the actual data retrieved by the search from the record storage means, and a trace memory means for storing the trace link data.

According to the traceability management apparatus configured as described above, it is only necessary to access the trace link data when searching for a part used in an assembly processed product, that is, a part used in the product. The assembly processed product data and the component data in the trace link data are associated by common event data, and are not limited to the assembly processing step. Therefore, the traceability management apparatus of the present invention can access the trace link data without accessing a database in which parts and assembly processes are associated, a database for connecting assembly processes, and the like. It is possible to quickly search for a part used for a product designated by, or a product for which a part designated by a user is used.

  Further, the traceability management device of the present invention retrieves trace link data having the same data as the input assembly work product data from the trace storage means, and causes the display means to display the component data in the retrieved trace link data. Alternatively, a display data collecting unit is provided for retrieving trace link data having the same data as the input component data from the trace storage unit and displaying the assembly product data in the retrieved trace link data on the display unit. It may be configured.

  According to the traceability management device configured as described above, it is possible to display to the user the parts used for the product specified by the user or the products used for the part specified by the user.

  The scope of the present invention extends to a program for managing product traceability in the assembly processing industry.

  According to the present invention, it is possible to quickly search which part is used for which finished product in the assembly processing industry.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing a traceability management apparatus according to an embodiment of the present invention.
The traceability management apparatus 1 shown in FIG. 1 includes an integrated DB 4 having a header DB 2 and a performance DB 3, a data item master 5, a data type master 6, a trace configuration creation unit 7, a link DB 8, a trace DB 9, and display data. And a collecting unit 10.

  Among the data obtained from the assembly processing line, the header DB 2 includes an event No (data for identifying a predetermined unit assembly processing step), a procedure ID (data indicating a set of event Nos), a start time (event No.). Data indicating the start time of the indicated assembly processing step), end time (data indicating the end time of the assembly processing step indicated by event No.), and data indicating a lot No (a certain product (assembly processed product, first part)) ) And batch data (data indicating a part (second part) necessary for assembling the product indicated by the lot number).

  The record DB 3 is composed of an event number, a data item ID, and a record value (data indicating parts used in the assembly process and work performed in the assembly process) among data obtained from the assembly process line. Memorized performance data.

The data item master 5 stores item data composed of a data item ID and a data type.
The data type master 6 stores type data composed of a data type and a data type name.

  Each time a new event number is added to the integrated DB 4, the trace configuration creation unit 7 generates link data and trace link data based on data stored in the header DB 2, the performance DB 3, and the data item master 5, respectively. create.

  The link DB 8 includes link data including a start time, an end time, a product number (data indicating the names of products and parts), and a tray slot No (data indicating a set (parts) of parts indicated by a batch No). Remember.

  The trace DB 9 is necessary for assembling and processing the lot number, batch number, serial number (data indicating the serial number for the lot number and batch number), tray slot number, and trace batch number (part indicated by the batch number). Trace link data including data (data indicating a component (third component)) is stored.

  The display data collection unit 10 accesses the trace link data, acquires the tray slot number or trace batch number corresponding to the lot number or batch number specified by the user, and acquires the acquired tray slot number or trace batch number. The data is sent to the terminal device 11 provided on the user side and displayed on the display of the terminal device 11.

FIG. 2 is a flowchart for explaining the operation of the trace configuration creation unit 7.
First, the trace configuration creation unit 7 acquires a new event number from the integrated DB 4 or the like. (S1)
Next, the trace configuration creation unit 7 acquires “data type”, “offset time (minutes)”, and “number of product number digits” in the INI file defined in advance by the user, the assembly processing plan creation device, or the like. (S2)
FIG. 3 is a diagram illustrating an example of the INI file.

In the INI file shown in FIG. 3, “9999” is defined as “data type”, “3” is defined as “offset time (minutes)”, and “4” is defined as “number of product part digits”.
Next, in FIG. 2, the trace configuration creation unit 7 uses “procedure ID”, “end time” from the header data having the same “event No.” as the “event No.” acquired in S1 among the header data in the header DB2. ”,“ Lot No ”, and“ Batch No ”are acquired. (S3)
FIG. 4 is a diagram illustrating an example of the header DB2.

  For example, if the “event No” acquired in S1 is “100”, the trace configuration creating unit 7 sets “PROC001” as the “procedure ID” and “PROC001” from the header data 40 of the header DB2 shown in FIG. “10:00”, “Lot No.” as “LOT0001”, and “Batch No” as “LOT00001” are acquired.

Next, in FIG. 2, the trace configuration creation unit 7 uses the “data type” acquired in S2 and the “procedure ID”, “end time”, “lot No”, and “batch No” acquired in S3 as conditions. , Header DB2, result DB3, data item master 5, and data type master 6, obtain "start time", "end time", and "actual value", create link data composed of these data, and create link DB8 To record. (S4)
An example of the operation of S4 is shown below.

  (1) In S3, the trace configuration creating unit 7 sets “PROC001” as “Procedure ID”, “10:00” as “End Time”, “LOT0001” as “Lot No”, and “LOT0001” as “Batch No”. If acquired, the header data 40 to 42 having the same data are acquired from the header DB 2 shown in FIG. Then, the trace configuration creation unit 7 acquires “100”, “102”, and “103” as the “event number” from the header data 40 to 42, and “9:00” and “9:30” as the “start time”. "," 9:45 "is acquired.

  (2) When “9999” is acquired as the “data type” in S <b> 2, the trace configuration creating unit 7 sets “data item ID” corresponding to “9999” stored as “data type” in the data type master 6. “DTI001” and “DTI002” are acquired from the item data 50 and 51 of the data item master 5 shown in FIG.

  (3) The trace configuration creating unit 7 sets “100”, “102”, “103” as “event No.” acquired in (1) above, and “data item ID” acquired in (2) above. The result data 60 to 64 having “DTI001” and “DTI002” are acquired from the result DB3 shown in FIG. Then, the trace configuration creating unit 7 acquires “A012LOT0011”, “B012LOT0014”, “A012LOT0012”, “B012LOT0015”, and “A012LOT0013” as “actual values” from the actual data 60 to 64.

  (4) The trace configuration creating unit 7 associates the “start time” and “end time” acquired in (1) with the “actual value” acquired in (3), as shown in FIG. Link data 70 to 74 composed of “start time”, “end time”, and “actual value” are created.

Next, in FIG. 2, the trace configuration creation unit 7 sets the “actual value” in the link data created in S4 to “product number” and “tray slot number” based on the “number of product number digits” acquired in S2. Divide into (S5)
For example, when the “item number digit” is “4”, the trace configuration creating unit 7 sets “A012LOT0011” as “actual value” of each link data of the link DB 8 created in S4, as shown in FIG. “Product number” is divided into “A012” and “Tray slot number” is divided into “LOT0011”.

Next, in FIG. 2, the trace configuration creation unit 7 rearranges the link data of S5 so that “tray slot numbers” are arranged in chronological order for each “product number”, and then “end time” in each link data. Correct each. (S6)
For example, as shown in FIG. 9, the trace configuration creation unit 7 rearranges the link data of S5 so that the “start time” is arranged in time series for each “product number”, and then, as shown in FIG. When the “end time” of the link data is later than the “start time” of the next link data, the “end time” of the certain link data is changed to the “start time” of the next link data.

Next, in FIG. 2, the trace configuration creation unit 7 creates the “data type” and “offset time (minutes)” acquired in S2, the “lot number” and “procedure ID” acquired in S3, and the S6. Based on the “start time” and “end time” of each link data, header data having a “batch No.” as a parent is extracted from the header DB 2. (S7)
For example, “offset time (minutes)” acquired in S2 is “3”, “lot No.” and “procedure ID” acquired in S3 are “LOT0001” and “PROC001”, and the link data shown in FIG. When the “start time” of 70 is “9:00” and the “end time” is “9:30”, the trace configuration creating unit 7 sets 9: 0 to 9: 30 + 3 minutes (offset time (minutes)), that is, 9 : Header data 43 to 46 (FIG. 4) having “start time” or “end time” falling within a period of 00 to 9:40 are extracted from the header DB2. Similarly, when the “start time” of the link data 72 shown in FIG. 10 created in S6 is “9:30” and the “end time” is “9:45”, 9:30 to 9: 45 + 3. (Offset time (minutes)), that is, header data 46 and 47 (FIG. 4) having “start time” or “end time” falling within a period of 9:30 to 9:50 are extracted from the header DB2. Further, when the “start time” of the link data 74 shown in FIG. 10 created in S6 is “9:45” and the “end time” is “10:00”, 9: 45 + 3 (offset time (minutes)) 10: 00 + 3 (offset time (minutes)), that is, header data 48 and 49 (FIG. 4) having “start time” or “end time” that falls within the period of 9:50 to 10:10 are extracted from the header DB2. The When the “start time” of the link data 71 shown in FIG. 10 created in S6 is “9:00” and the “end time” is “9:30”, the header data 43 to 46 (FIG. 4) are stored. Extracted from the header DB2. Further, when the “start time” of the link data 73 shown in FIG. 10 created in S6 is “9:30” and the “end time” is “10:00”, 9:30 to 10: 00 + 3 (offset time) (Minutes)) That is, header data 46 to 49 (FIG. 4) having “start time” or “end time” that falls within a period of 9:30 to 10:10 are extracted from the header DB2.

Next, in FIG. 2, the trace configuration creation unit 7 creates a “batch number” as a child from the header DB 2 based on the “data type” acquired in S 2 and the “tray slot No” in the link data created in S 6. Extract header data with. (S8)
For example, if the “tray slot number” of the link data 70 shown in FIG. 10 created in S6 is “LOT0011”, the trace configuration creation unit 7 has the header data 30 to 32 having the same “lot number” as that “LOT0011”. (FIG. 4) is extracted from the header DB2. When the “tray slot number” of the link data 72 shown in FIG. 10 created in S6 is “LOT0012”, the header data 33 and 34 (FIG. 4) having the same “lot number” as the “LOT0012” are the headers. Extracted from DB2. When the “tray slot number” of the link data 74 shown in FIG. 10 created in S6 is “LOT0013”, the header data 35 and 36 (FIG. 4) having the same “lot number” as the “LOT0013” are headers. Extracted from DB2. When the “tray slot number” of the link data 71 shown in FIG. 10 created in S6 is “LOT0014”, the header data 37 and 38 (FIG. 4) having the same “lot number” as the “LOT0014” are headers. Extracted from DB2. When the “tray slot number” of the link data 73 shown in FIG. 10 created in S6 is “LOT0015”, the header data 39 (FIG. 4) having the same “lot number” as the “LOT0015” is obtained from the header DB2. Extracted.

Next, in FIG. 2, the trace configuration creation unit 7 sets the “batch No” of the header data extracted in S <b> 8 to “Trace Batch No” and has a parent-child relationship with the “batch No” of the header data extracted in S <b> 7. In addition, the “lot No.” of the header data extracted in S8 is set to “tray slot No.”, and trace link data is created in association with the “lot No” of the header data extracted in S7 so as to have a parent-child relationship. Store in the trace DB 9. (S9)
For example, the trace configuration creation unit 7 sets “SYN0011” that is “Batch No” of the header data 30 to 32 extracted in S8 to “SYN0001” that is “Batch No” of the header data 43 extracted in S7. ”,“ SYN0012 ”, and“ SYN0013 ”. Further, the trace configuration creating unit 7 associates “LOT0001” that is “lot No” of the extracted header data 43 with “LOT0011” that is “lot No” of each of the extracted header data 30 to 32. Thereby, the trace link data 80 to 82 are created as shown in FIG. By repeating this operation, trace link data 80 to 111 are created. That is, based on the link data 70 created in S6, the header data 43 to 46 extracted in S7 and the header data 30 to 32 extracted in S8 are associated with each other, whereby the trace link data 80 to 91 are associated. Is created. Also, based on the link data 72 created in S6, the header data 46 to 47 extracted in S7 and the header data 33 to 34 extracted in S8 are associated with each other, so that the trace link data 92 to 95 is associated. Is created. In addition, based on the link data 74 created in S6, the header data 48 to 49 extracted in S7 and the header data 35 to 36 extracted in S8 are associated with each other, whereby the trace link data 96 to 99 are associated. Is created. Further, based on the link data 71 created in S6, the header data 43 to 46 extracted in S7 and the header data 37 to 38 extracted in S8 are associated with each other, so that the trace link data 100 to 107 is associated. Is created. In addition, based on the link data 73 created in S6, the header data 46 ~ extracted in S7.
49 and the header data 39 extracted in S8 are associated with each other, thereby creating the trace link data 108 to 111.

Next, in FIG. 2, when the trace link data created in S <b> 9 does not already exist in the trace DB 9, the trace configuration creation unit 7 sets “lot No” or “batch No” in the trace link data. A serial number is assigned to the trace DB 9 to record it. (S10)
For example, as in the case of the trace link data shown in FIG. 12, when the “lot numbers” are all the same, serial numbers are assigned to the “batch numbers”.

  In S10, if the trace link data created in S9 already exists in the trace DB 9, the trace configuration creating unit 7 deletes the trace link data already existing in the trace DB 9, and newly creates the trace link data. Store in the trace DB 9.

  According to the traceability management device 1 of the present embodiment configured as described above, when searching for a tray slot No or a trace batch No that is a child of a lot No or a batch No, that is, a part used in a product, tracing is performed. It is only necessary to access the link data. The lot number or batch number and the tray slot number or trace batch number in the trace link data are associated with each other by a common event number and are not limited to the assembly process. Therefore, the traceability management device 1 of the present embodiment only accesses the trace link data, without accessing a database in which parts and assembly processes are associated with each other, or a database for connecting the assembly processes. A tray slot number or trace batch number that is a child of a lot number or batch number specified by the user, or a lot number or batch number that is a parent of the tray slot number or trace batch number specified by the user is searched at high speed. be able to.

Next, the operation of the display data collection unit 10 will be described.
FIG. 13 is a flowchart for explaining the operation of the display data collection unit 10.
First, the display data collection unit 10 determines whether or not the traceback process is selected by the user. (S11)
Here, FIG. 14 is a diagram illustrating an example of a search screen displayed on the display of the terminal device 11. The search screen shown in FIG. 14 is provided with a selection field 12 in which a trace back process or a trace forward process can be selected from a pull-down menu. In addition, the search screen shown in FIG. 14 is provided with an input field 13 in which a lot number or batch number as a starting point can be specified. When a lot number is to be input, the lot number radio button beside the input field 13 is checked. When inputting a batch number, check the radio button for batch number next to the input field 13. Further, the search screen shown in FIG. 14 is provided with a designation column 14 in which a hierarchy can be designated by a pull-down menu. For example, when selection or input by the user is completed in the selection column 12, the input column 13, and the designation column 14, and the search button 15 is pressed by the user, the display data collection unit 10 executes the operation of the flowchart shown in FIG. To do.

Next, when it is determined in FIG. 13 that the traceback process has been selected (S11: Y), the display data collection unit 10 performs a lotback that is a lot number or a child of the batch No specified by the user as the traceback process. No or batch No is acquired from the trace DB 9. (S12)
Here, FIG. 15 is a diagram showing an acquisition image of the lot No when the lot No. for three layers is trace back processed. In the example shown in FIG. 15, starting from “LOT0001”, “LOT0011” in the next lower layer and “LOT0111” in the next lower layer.
"Is an image to collect.

  For example, when “LOT0001” is designated as the “lot number” of the starting point by the user, the display data collection unit 10 has “LOT0001” as the “lot number” of the child one layer below “LOT0001”. “LOT0011” which is “tray slot No” in the trace link data is acquired.

Next, in FIG. 13, the display data collection unit 10 determines whether there are lot numbers or batch numbers acquired up to now for the hierarchy designated by the user. (S13)
When it is determined that there is no hierarchy specified by the user (S13: N), the display data collection unit 10 acquires the lot number or batch number acquired in S12 as a parent, and further acquires the child lot number or batch number. Then (S14), the process returns to S13.

  For example, in FIG. 15, when acquiring “Lot No.” of a child of “LOT0011”, the display data collecting unit 10 sets “LOT0011” as “Lot No.” of a child one level lower than “LOT0011”. “LOT0111” that is “tray slot number” in the trace link data having “lot number” is acquired.

  In FIG. 13, when it is determined that there is a hierarchy specified by the user (S 13: Y), the display data collection unit 10 ends the data acquisition and displays the data acquired up to now on the display of the terminal device 11. To display.

  In the display field 16 of the search screen shown in FIG. 14, the parent-child relationship of the lot numbers or batch numbers acquired by the display data collection unit 10 is displayed in a tree structure, and the display field 17 is selected in the display field 17 of the search screen. The lot number or the actual value corresponding to the batch No. is displayed.

In FIG. 13, when it is determined that the traceback process is not selected (S11: N), the display data collection unit 10 is the parent of the lot number or batch number designated by the user as the trace forward process. A lot number or batch number is acquired. (S15)
Next, the display data collection unit 10 determines whether there are lot numbers or batch numbers acquired up to now for the hierarchy designated by the user. (S16)
When it is determined that the hierarchy is not specified by the user (S16: N), the display data collection unit 10 sets the lot No or batch No acquired in S15 as a child, and further sets the parent lot No or batch No. Obtain (S17) and return to S16.

  On the other hand, if it is determined that there is a hierarchy specified by the user (S16: Y), the display data collection unit 10 ends the data acquisition and displays the lot number or batch number acquired up to now on the display of the terminal device 11. To display.

Note that the starting lot number or batch number may be a lot number or batch number in the middle of the assembly process.
According to the traceability management apparatus 1 of the present embodiment configured as described above, a lot number or batch number that is a child of a lot number or batch number specified by the user, or a lot number or batch number specified by the user. Can be displayed on the display of the terminal device 11 in an arbitrary hierarchy.

In addition, only by accessing the trace link data composed of only the lot number or batch number of the parent-child relationship, the trace back process or the trace forward process can be performed from any lot number or batch number without being bound to the assembly process. In either of these processes, the lot number or batch number can be easily obtained up to the level designated by the user, and can be displayed on the display of the terminal device 11 at high speed.

  In addition, by accessing the trace link data consisting only of the lot number or batch number of the parent-child relationship, even if the hierarchy specified by the user becomes deeper, the lot number or batch number of the parent-child relationship in the trace link data The desired lot No. or batch No. can be easily acquired by following the above.

  In addition, by accessing the trace link data that consists of only the lot number or batch number of the parent-child relationship, it is possible to display the lot number or batch number of only the hierarchy specified by the user. The lot number or batch number can be prevented from being displayed.

  In the above embodiment, the trace link data indicating the parent-child relationship of the lot No and the parent-child relationship of the batch No. is created. However, the trace link indicating only the parent-child relationship of the lot No or only the parent-child relationship of the batch No. You may comprise so that data may be produced. The configuration for creating the trace link data indicating the parent-child relationship of the lot No and the parent-child relationship of the batch No is compared with the configuration of creating the trace link data indicating only the parent-child relationship of the batch No or only the parent-child relationship of the batch No. When a failure occurs in a part constituting a certain product, it is possible to specify in more detail the location where the failure has occurred.

It is a figure which shows the traceability management apparatus of embodiment of this invention. It is a flowchart for demonstrating operation | movement of a trace structure preparation part. It is a figure which shows an example of an INI file. It is a figure which shows an example of header data. It is a figure which shows an example of item data. It is a figure which shows an example of performance data. It is a figure which shows an example of link data. It is a figure which shows an example of link data. It is a figure which shows an example of link data. It is a figure which shows an example of link data. It is a figure which shows an example of trace link data. It is a figure which shows an example of trace link data. It is a flowchart for demonstrating operation | movement of a display data collection part. It is a figure which shows an example of a search screen. It is a figure which shows the collection image of lot No at the time of carrying out the trace back process of lot No. for 3 layers.

Explanation of symbols

1 Traceability management device 2 Header DB
3 results DB
4 Integrated DB
5 Data item master 6 Data type master 7 Trace configuration creation unit 8 Link DB
9 Trace DB
10 Display Data Collection Unit 11 Terminal Device 12 Selection Field 13 Input Field 14 Designation Field 15 Search Button 16 Display Field 17 Display Field

Claims (8)

A traceability management device that performs traceability management in the assembly processing industry,
Header storage means for storing header data composed of event data for identifying an assembly processing step of a predetermined unit among data obtained from an assembly processing line, and assembly processing product data indicating a certain assembly processing product;
Of the data obtained from the assembly processing line, performance storage means for storing performance data composed of the event data and parts data indicating parts necessary for assembling the assembly processed product;
The header data having the same data as the input event data is retrieved from the header storage means, and the assembly processed product data in the retrieved header data and the actual data having the same data as the input event data are stored in the actual data. A trace configuration creating means for creating trace link data by associating with the part data in the retrieved result data and searching from the means;
Trace storage means for storing the trace link data;
A traceability management device comprising: The traceability management device according to claim 1,
Trace trace data having the same data as the inputted assembly processed product data is retrieved from the trace storage means, and the part data in the retrieved trace link data is displayed on the display means, or the same data as the inputted part data And display data collecting means for retrieving the trace link data from the trace storage means, and displaying the assembly work product data in the retrieved trace link data on the display means,
Traceability management device characterized by that. A traceability management device that performs traceability management in the assembly processing industry,
Of the data obtained from the assembly processing line, event data for identifying a predetermined unit assembly processing step, lot data indicating the first component, and second data necessary for assembling the first component. A header composed of batch data indicating parts, start time data indicating the start time of the assembly process indicated by the event data, and end time data indicating an end time of the assembly process indicated by the event data Header storage means for storing data;
Of the data obtained from the assembly processing line, a record storage means for storing record data composed of the event data and tray slot data indicating a set of the second parts;
Header data having the same data as the input event data is retrieved from the header storage means, and the header data having the same data as the lot data, batch data, and end time data in the retrieved header data is retrieved from the header storage means. Search and search for header data having the same data as the input event data and start time data and end time data in the searched header data, and lot data and batches in the searched header data Data and header data having the same data as the end time data are retrieved from the header storage means, and the actual data having the same data as the event data in the retrieved header data is retrieved from the actual result storage means and the retrieved actual data Link with the tray slot data in Create a data,
The header data having the same lot data as the tray slot data in the predetermined link data is retrieved from the header storage means, and the batch data in the retrieved header data is assembled to process the second part. The header storage means is searched for header data having start time data and end time data that fall within the period indicated by the start time data and end time data in the predetermined link data. The batch data in the retrieved header data is associated with a parent-child relationship, and among the associated batch data and trace batch data, lot data in header data having trace batch data is used as the tray slot data, and Associated batch data and trace batch And association with trace configuration creating means for creating a trace link data so that the lot data and parent-child relationship in the header data with the batch data of the over data,
Trace storage means for storing the link data and the trace link data;
A traceability management device comprising: The traceability management device according to claim 3,
Trace link data having the same data as the lot data or batch data to be input is retrieved from the trace storage means, and the tray slot data or trace batch data in the retrieved trace link data is displayed on the display means or input. Display data collecting means for retrieving trace link data having the same data as the trace slot data or trace batch data from the trace storage means and displaying the lot data or batch data in the retrieved trace link data on the display means,
Traceability management device characterized by that. A program for managing the traceability of products in the assembly processing industry.
Header storage means for storing header data composed of event data for identifying a predetermined unit of the assembly processing step among data obtained from the assembly processing line and assembly processing product data indicating a certain assembly processing product;
Of the data obtained from the assembly processing line, performance storage means for storing performance data composed of the event data and part data indicating parts necessary for assembling the assembly processed product;
The header data having the same data as the input event data is retrieved from the header storage means, and the assembly processed product data in the retrieved header data and the actual data having the same data as the input event data are stored in the actual data. Trace configuration creating means for creating trace link data by associating with the component data in the retrieved result data by searching from the means,
Trace storage means for storing the trace link data;
Program to function as. The program according to claim 5,
Trace trace data having the same data as the inputted assembly processed product data is retrieved from the trace storage means, and the part data in the retrieved trace link data is displayed on the display means, or the same data as the inputted part data Display data collection means for retrieving the trace link data having the following from the trace storage means and displaying the assembly work product data in the retrieved trace link data on the display means,
Program to function as. A program for managing the traceability of products in the assembly processing industry.
Of the data obtained from the assembly processing line, event data for identifying a predetermined unit assembly processing step, lot data indicating the first component, and second data necessary for assembling the first component. A header composed of batch data indicating parts, start time data indicating the start time of the assembly process indicated by the event data, and end time data indicating an end time of the assembly process indicated by the event data Header storage means for storing data;
Of the data obtained from the assembly processing line, record storage means for storing record data composed of the event data and tray slot data indicating a set of the second parts;
Header data having the same data as the input event data is retrieved from the header storage means, and the header data having the same data as the lot data, batch data, and end time data in the retrieved header data is retrieved from the header storage means. Search and search for header data having the same data as the input event data and start time data and end time data in the searched header data, and lot data and batches in the searched header data Data and header data having the same data as the end time data are retrieved from the header storage means, and the actual data having the same data as the event data in the retrieved header data is retrieved from the actual result storage means and the retrieved actual data Link with the tray slot data in Create a data,
The header data having the same lot data as the tray slot data in the predetermined link data is retrieved from the header storage means, and the batch data in the retrieved header data is assembled to process the second part. The header storage means is searched for header data having start time data and end time data that fall within the period indicated by the start time data and end time data in the predetermined link data. The batch data in the retrieved header data is associated with a parent-child relationship, and among the associated batch data and trace batch data, lot data in header data having trace batch data is used as the tray slot data, and Associated batch data and trace batch Over the lot data and association with trace configuration creating means for creating a trace link data so that the parent-child relationship in the header data with the batch data of the data,
Trace storage means for storing the link data and the trace link data;
Program to function as. The program according to claim 7,
Trace link data having the same data as the lot data or batch data to be input is retrieved from the trace storage means, and the tray slot data or trace batch data in the retrieved trace link data is displayed on the display means or input. Display data collection means for retrieving trace link data having the same data as the trace slot data or trace batch data from the trace storage means and displaying the lot data or batch data in the retrieved trace link data on the display means;
Program to function as.

Images