JP2010092365A - System and method for acquiring trace information - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for acquiring trace information capable of acquiring trace information even in fields which do not share an infrastructure. <P>SOLUTION: The system for acquiring trace information for acquiring trace information regarding a product manufactured through multiple stages, includes: a storage means for storing event data regarding an event performed to the product; and an acquisition means for acquiring the trace information from the event data stored by the storage means. The event data 11 includes: thing data 12a regarding an event; person data 12b regarding the event; time point data 12c regarding the event; position data 12d regarding the event; and state data 12e regarding the event, and has a common data format in the multiple stages. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a trace information acquisition system and a trace information acquisition method, and more particularly to a trace information acquisition system and a trace information acquisition method for acquiring trace information of a product manufactured through a plurality of stages. .

  Recently, from the viewpoint of product quality maintenance and quality improvement, it is required to build a traceability system that can trace the manufacturing process of products manufactured through multiple stages, that is, to build a system for acquiring trace information for products. ing. Technologies relating to product traceability are disclosed in, for example, Japanese Patent Application Laid-Open No. 2007-249326 (Patent Document 1) and Japanese Patent Application Laid-Open No. 2005-346280 (Patent Document 2).

According to Patent Document 1, information relating the linkage between each process is stored between a plurality of adjacent processes, and trace information straddling between adjacent processes is acquired by using the stored inter-process relation information. It is said. According to Patent Document 2, in a process chain including a series of processes, a pointer indicating a storage destination of product trace information is stored, and product trace information is acquired using the stored pointer.
JP 2007-249326 A JP 2005-346280 A

  With respect to the traceability shown in Patent Document 1 and Patent Document 2 described above, it is necessary to store information relating to linkage between processes and a trace information pointer indicating a storage destination. That is, the trace information about the product cannot be obtained unless the stored link information between processes is used. Then, for example, in a field in an environment where infrastructure is not shared, such as different supply chains or ranges across supply chains, link information between processes may not be stored, and trace information cannot be obtained. That is, trace information cannot be acquired in a field that does not share infrastructure.

  An object of the present invention is to provide a trace information acquisition system that can acquire trace information even in a field that does not share infrastructure.

  Another object of the present invention is to provide a trace information acquisition method capable of acquiring trace information even in a field that does not share infrastructure.

  Still another object of the present invention is to provide a trace information acquisition apparatus that can acquire trace information even in a field that does not share infrastructure.

  Still another object of the present invention is to provide a trace information acquisition program capable of acquiring trace information even in a field that does not share infrastructure.

  Still another object of the present invention is to provide a storage medium storing a trace information acquisition program that can acquire trace information even in a field that does not share infrastructure.

  A trace information acquisition system according to the present invention is a trace information acquisition system for acquiring trace information relating to a product manufactured through a plurality of stages, and storing means for storing event data relating to an event performed on the product. Acquisition means for acquiring trace information from the event data stored by the storage means. Here, the event data has a common data format in a plurality of stages.

  As described above, since event data related to an event performed on a product has a common data format in a plurality of stages, trace information on the product can be acquired based on the stored event data. Then, it is possible to obtain trace information regarding a product manufactured through a plurality of stages regardless of the infrastructure, for example, without storing data relating a plurality of stages in a product manufactured through a plurality of stages. Trace information for the product can be acquired. Therefore, trace information can be acquired even in a field that does not share infrastructure.

  Preferably, the event data includes mono data related to the event, human data related to the event, time data related to the event, position data related to the event, and state data related to the event.

  More preferably, the storage means stores event activity data that is information of a business activity to be stored when an event occurs, and the acquisition means acquires trace information from the event activity data stored by the storage means.

  More preferably, the acquisition unit includes an extraction unit that extracts a plurality of event data associated with each other from a plurality of event data stored in the storage unit.

  Further, the extracting means may extract, as event data associated with each other, data having the same time in the time data related to the event among the plurality of event data.

  In a further preferred embodiment, the storage means stores event data using an RFID (Radio Frequency Identification) tag.

  In another aspect of the present invention, a trace information acquisition method is a trace information acquisition method for acquiring trace information relating to a product manufactured through a plurality of stages, and has a common data format in the plurality of stages. And a storage step for storing event data relating to the event performed on the memory, and an acquisition step for acquiring trace information from the event data stored in the storage step.

  In still another aspect of the present invention, the trace information acquisition device is a trace information acquisition device that acquires trace information about a product manufactured through a plurality of stages, and has a common data format in the plurality of stages. A storage unit that stores event data related to an event performed on the product, and an acquisition unit that acquires trace information from the event data stored in the storage unit.

  In still another aspect of the present invention, the trace information acquisition program has a common data format in a plurality of stages to acquire trace information related to a product manufactured through a plurality of stages. It is a trace information acquisition program for functioning as storage means for storing event data relating to an event performed on the event, and acquisition means for acquiring trace information from the event data stored by the storage means.

  In still another aspect of the present invention, the storage medium is a computer-readable storage medium that stores the above-described trace information acquisition program.

  According to such a trace information acquisition system, since event data related to an event performed on a product has a common data format in a plurality of stages, trace information on the product is acquired based on stored event data. can do. Then, it is possible to obtain trace information regarding a product manufactured through a plurality of stages regardless of the infrastructure, for example, without storing data relating a plurality of stages in a product manufactured through a plurality of stages. Trace information for the product can be acquired. Therefore, trace information can be acquired even in a field that does not share infrastructure.

  In addition, for such a trace information acquisition method, trace information acquisition device, trace information acquisition program and storage medium, it is possible to acquire trace information regarding a product manufactured through a plurality of stages regardless of the infrastructure, for example, In a product manufactured through a plurality of stages, trace information for the product can be obtained without storing data relating the plurality of stages. Therefore, trace information can be acquired even in a field that does not share infrastructure.

  Embodiments of the present invention will be described below with reference to the drawings. First, event data used in the trace information acquisition system according to an embodiment of the present invention will be described. FIG. 1 is a conceptual diagram showing a data format of event data. Referring to FIG. 1, event data 11 is data relating to an event performed on a product, and has a common data format in a plurality of stages when the product is manufactured. The event data 11 includes object data 12a that is information about a sensing object related to the event, person data 12b that is information about a person related to the event, time data 12c that is time information about the event, and position data that is information about a place related to the event. 12d, and status data 12e which is status information regarding the event. The mono data 12a, the person data 12b, the time point data 12c, and the position data 12d are concepts connected by the state data 12e.

  Next, the event activity data 13 will be described. The event activity data 13 refers to information on business activities to be stored when an event occurs, for example, data such as production quantity and parts consumption. The event activity data 13 is a data item according to the event attribute for each field. For example, in the production quantity data 14 a in the event activity data 13, “Product ID” is mono data, and “Time” is time data. The “container ID”, “number of non-defective products”, and “number of discarded items” are on-site input / acquisition information. In the carry-in / out data 14b, “gate ID” is position data, “container ID” is mono data, “time” is time data, and “carrier” is on-site input / acquisition information. Of the daily work report data 14c, “worker ID” is human data, “time” is time data, and “daily” is field input / acquisition information. Of the environmental data 14d, “facility ID” is position data, “time” is time data, “temperature”, and “humidity” are field input / acquisition information. Of the power amount data 14e, “wattmeter ID” is position data, “time” is time data, and “power” is field input / acquisition information. The event activity data and the event data are combined with a minimum item that can be correlated 1: 1. In FIG. 1, event activity data having the same items such as mono data are indicated by the same hatching.

  FIG. 2 is a system configuration diagram showing a hardware configuration of the trace information acquisition system according to the embodiment of the present invention. 1 and 2, the trace information acquisition system 21 can store various data such as event data, event activity data, an event data master that stores a plurality of event data and event activity data, and the like. An existing system, a server 23 storing production management data, process masters, BOM (Build Of Material) masters, computers 24a, 24b, 24c, 24d for inputting data such as event data, and event data Is provided as it is, a sensor device 25b that can input event data via the computer 24c, and a connection line 26 that connects the servers 22 and 23 and the computers 24a to 24d. The server 22 includes storage means for storing event data relating to an event performed on the product, and acquisition means for acquiring trace information from the event data stored by the storage means. Here, the computer 24c functions as a device setting interface for the sensor device 25b. The trace information acquisition system 21 includes an RFID tag system 27 that can input and output event data in a state separated from the product. The RFID tag system 27 includes a reader / writer 28a provided on the computer 24d side, and an RFID tag 28b attached to the product 29. The reader / writer 28a can read and write data, that is, input / output data. . Here, the computer 24 d functions as an external storage data interface with respect to the RFID tag system 27.

  The server 22 and the server 23 may be realized by a single server. The connection line 26 is not limited to a wired connection, and part or all of the connection line 26 may be realized wirelessly. Further, the number of computers 24a to 24d is not limited to four, and at least one computer may be used, and any number may be used. Further, the sensor devices 25a and 25b and the RFID tag system 27 may not be included, or two or more of each may be included.

  Here, a method for storing event data for product events will be described. FIG. 3 is a flowchart showing the flow of operations when storing event data. FIG. 4 is a block diagram of a trace information acquisition system according to an embodiment of the present invention. With reference to FIG. 1 to FIG. 4, a method for storing event sensing type event data by a device device will be described first. Note that the event sensing type event data storage method refers to a method of directly acquiring and storing event data by a sensor device such as the sensor device 25a or the sensor device 25b in the system configuration diagram shown in FIG.

  First, in the device setting interface of the computer 24c, data is read from the sensor device (device device) 25b (step S11 in FIG. 3, hereinafter, steps are omitted). Next, event data having the above-described configuration is created by the interface logic in the computer 24c (S12). Thereafter, event activity data having the above-described configuration is created by the interface logic in the computer 24c (S13). Next, the event data master database stored in the server 22 is updated (S14). Here, an event data master composed of a table master, a state master, a position master, a mono master, and a person master is updated. That is, new event data is stored in each master.

  Here, the event data master is a master for associating the data with the contents of each event data. For example, in the case of human data, the data itself is stored as simple symbols such as numbers and alphabets. A master in which this symbol is associated with information such as the name and affiliation of an actual worker is a person master in the event data master. The same applies to the status master, position master, and mono master. The table master is a master corresponding to various databases such as product event data and component event data. Note that the point-in-time data itself is date, date, and date / time data and does not need to be associated with other information, so there is no master.

  Next, a method of storing data transfer type event data by the existing system will be described. Note that the data transfer type event data storage method reads, for example, data stored in a storage device of an existing system such as the server 23 in the system configuration diagram shown in FIG. 2, converts it into event data, and stores it. It refers to a method and a method of reading data stored in an external storage medium such as the RFID tag 28b shown in the system configuration diagram, converting it into event data, and storing it.

  First, the server 22 reads data from the production management system server 23 that constructs the existing system (S21). Next, event data and event activity data are created by the interface logic in the existing system interface of the server 22 (S22, S23). Next, the event data master database stored in the server 22 is updated (S24).

  Next, a method for storing data transfer type event data using external storage data will be described. In the computer 24d, data is read by the RFID tag system 27 (S31). Specifically, the external system storage data is read by the reader / writer 28a from the RFID tag 28b attached to the product 29 and input to the computer 24d. Next, event data and event activity data are created by the interface logic in the external storage data interface of the computer 24d (S32, S33). Next, the event data master database stored in the server 22 is updated (S34).

  As described above, event data and event activity data of various data, specifically, event sensing type data by device equipment, data transfer type data by existing system, and data transfer type data by external storage data To update the database.

  In addition, as shown in FIG. 4, it is good also as constructing various databases beforehand based on event data. Specifically, in a plurality of stages, product event data and product event activity data related to stored products, part event data and part event activity data related to parts, loading event data related to loading and loading event activity data, and procurement events related to procurement Build data and procurement event activity data, shipment event data and shipment event activity data for shipments, vein event data and vein event activity data for veins. A vein event is an event related to collection, disassembly, reuse, and recycling, not a product production process. By doing so, the acquisition of trace information described later becomes more appropriate, and the acquisition of trace information becomes efficient.

  Next, a method for acquiring product trace information using event data will be described. FIG. 5 is a flowchart showing the flow of processing when acquiring product trace information. 1 to 5, when product information for which trace information is acquired as a tracing agent is input to the server 22 (S 41), first, an event of a product manufactured through a plurality of stages. Data is extracted (S42). Here, the acquisition unit included in the server 22 includes an extraction unit that extracts a plurality of event data associated with each other from a plurality of event data stored in the storage unit. The product event data referred to here is so-called product footprint information (footprint information), which is data indicating in what process the product is manufactured.

  Next, based on the event data of the extracted product, specifically, based on the time data and the position (location) data of the event data, the parts are generated at the same time, that is, the parts having the same time data and the same position data. An event is extracted (S43). Here, the extracting means extracts, as event data associated with each other, data having the same time in the time data related to the event among the plurality of event data. Similarly, a component container mounting event is extracted based on the extracted product event data (S44), and a component container event is further extracted from the extracted component container mounting event (S45). A part event is extracted (S46). Then, after examining the validity of the information from the BOM information by the process master and the BOM master by the component event extracted in S43 and the component container mounting event, the component container event, and the component event extracted in S44 to S46 (S47), The procurement event of the related event is extracted (S48). Note that the step of examining the validity of information by the process master and the BOM master is arbitrarily performed.

  In S42, after product event information is extracted, a package / shipping event is extracted together with a part event (S49), and a product shipping event is extracted (S50). Similarly, after extracting the product event information in S42, the decomposition event is extracted together with the extraction of the part event (S51), and further, the reuse event of the decomposition product is extracted (S52).

  In this way, trace information, specifically information related to parts related to a product, information about parts, information about containers, shipment, and reuse is acquired from the event data. According to such a trace information acquisition system, since event data related to an event performed on a product has a common data format in a plurality of stages, trace information on the product is acquired based on stored event data. can do. Then, it is possible to obtain trace information regarding a product manufactured through a plurality of stages regardless of the infrastructure, for example, without storing data relating a plurality of stages in a product manufactured through a plurality of stages. Trace information for the product can be acquired. Therefore, trace information can be acquired even in a field that does not share infrastructure.

  That is, the trace information acquisition system stores the process in the life cycle of the product to be traced as the start and end event data. At the same time, in the life cycle process of the product, the event data of parts, member consumption and packing / shipping which occurred at the same place at the same time are also stored. Correlation of parts and parts for the product used for production due to event simultaneity, and also related to parts used, parts receiving process and product shipping process, from parts and parts procurement to production and shipping trace information Can be obtained. Furthermore, not only the production process, but also venous events such as collection, disassembly, reuse, and recycling can be related by synchronization. In this case, since the event data has a common data format in a plurality of stages, such trace information can be acquired.

There are two types of trace information: product life cycle footprint and carbon footprint. A product has a trace of its existence across procurement, production, use, recovery, disassembly, reuse, and recycling, and that trace and trajectory is called the product life cycle footprint. Furthermore, by memorizing the amount of CO ₂ (carbon dioxide) emitted in each trace, the CO ₂ emission trajectory in the product life cycle footprint is drawn, which is called the carbon footprint.

  The trace information acquisition method according to the present invention is a trace information acquisition method for acquiring trace information relating to a product manufactured through a plurality of stages, and has a common data format in the plurality of stages, A storage step for storing event data relating to the event performed in this manner, and an acquisition step for acquiring trace information from the event data stored in the storage step.

  Further, the trace information acquisition device according to the present invention is a trace information acquisition device for acquiring trace information related to a product manufactured through a plurality of stages, and has a common data format in the plurality of stages, A storage unit that stores event data related to the event that is performed, and an acquisition unit that acquires trace information from the event data stored in the storage unit. Here, the server 22 in FIG. 2 described above corresponds to the trace information acquisition apparatus.

  Further, the trace information acquisition program according to the present invention has a common data format in a plurality of stages and is performed on the product in order to acquire trace information on the product manufactured through the plurality of stages. A trace information acquisition program for functioning as storage means for storing event data relating to the event and the acquisition means for acquiring trace information from the event data stored in the storage means.

  The storage medium according to the present invention is a computer-readable storage medium that stores the above-described trace information acquisition program.

  Here, an embodiment of the trace information acquisition system according to the present invention will be described. FIG. 6 is a diagram illustrating an example of event data when a product mounting operation is performed using a component mounter on which an assembly component reel is mounted. FIG. 7 is a diagram showing association of event data in the case shown in FIG. Referring to FIGS. 6 and 7, regarding reel replacement, a reel setting event that sets the trigger to “set completed”, that is, an event that “sets a component tape to the reel”, and a trigger that is “installation completed”. Reel attachment / detachment events, that is, an event “removal / removal of the reel to / from the component mounter” and a reel attachment / detachment event having the trigger “removal completion” occur. Event data as shown in FIG. 6 is stored for these events. Specifically, for the event “reel set” whose trigger is “set completed”, “part lot 3” as mono data, “worker B” as human data, and position (equipment) data as “Reel 2”, “8:50” as time data, and “normal end” as status data are stored. This means that the worker B has normally set the parts lot 3 on the reel 2 at time 8:50. Similarly, for the event “reel attachment / detachment” with the trigger set to “installation complete”, “mounting reel 2” as mono data, “worker C” as human data, and “mounting as position (equipment) data” Machine 4 ”,“ 8:55 ”as time data, and“ normally mounted ”as status data are stored. This means that the worker C has normally mounted the reel 2 on the mounting machine 4 at time 8:55. Similarly, in response to an event “reel attachment / detachment” whose trigger is “removal completed”, “mounting reel 2” as mono data, “worker C” as human data, and position (equipment) data “Mounting machine 4”, “10:00” as time data, and “normal mounting” as status data are stored. This means that the worker C has successfully removed the reel 2 from the mounting machine 4 at time 10:00.

  On the other hand, regarding implementation, a “mounter” event having a trigger “work start” and a “mounter” event having a trigger “work completion” are generated. Then, as shown in FIG. 6, for the event “mounting machine”, a trigger “work start”, “product order 1” as mono data, “worker D” as human data, position ( Equipment) “Mounting machine 4” as data, “9:00” as time data, and “normal start” as status data are stored. This means that the worker D has successfully started the mounting operation of the product order 1 with the mounting machine 4 at time 9:00. Also, for the event “Mounting machine”, the trigger “Work complete”, “Product order 1” as mono data, “Worker D” as human data, “Mounting” as position (equipment) data Machine 4 ”,“ 9:45 ”as time data, and“ normal end ”as status data are stored. This means that the worker D has successfully completed the mounting operation of the product order 1 with the mounting machine 4 at time 9:45.

  Then, by acquiring the trace information, the trace information indicated by the dotted line in FIG. 7 is associated. That is, in the event data related to the mounting machine 4, the mono data is “product order 1”. In the event data related to reel attachment / detachment, the position data is “mounting machine 4”. Further, in the event data relating to the attachment / detachment of the reel, the mono data is “mounted reel 2”, and in the reel set event, the position data is “reel 2”.

  Then, as shown in FIG. 7, even if the association between the part lot 3 and the product order 1 is not directly stored, the part lot 3 and the product order 1 can be obtained from the event data via the mounting machine 4 and the mounting reel 2. The trace information can be associated.

  Here, event data in the manufacturing process will be further described as another embodiment. FIG. 8 is a diagram illustrating an example of event data in a manufacturing process from product order to shipment. Referring to FIG. 8, in the manufacturing process, a picking process for selecting parts from inventory corresponding to a product order, a kitting process for arranging the picked parts so that an assembly worker can easily perform the work, a reel replacement process, There are a dividend process, a mounting process, an inspection process, and a loading process. As an event that occurs before the picking process, there is an order registration event that sets the trigger to be completed. Event data, that is, mono data, human data, position data, time data, and status data are stored for each event generated in each of these processes. Then, the trace information is acquired from the stored event data.

  As described above, according to such a trace information acquisition system, it is possible to acquire trace information related to a product manufactured through a plurality of stages irrespective of the infrastructure. For example, in a product manufactured through a plurality of stages, Trace information for a product can be obtained without storing data relating multiple stages. Therefore, trace information can be acquired even in a field that does not share infrastructure.

  In addition, for such a trace information acquisition method, trace information acquisition device, trace information acquisition program and storage medium, it is possible to acquire trace information regarding a product manufactured through a plurality of stages regardless of the infrastructure, for example, In a product manufactured through a plurality of stages, trace information for the product can be obtained without storing data relating the plurality of stages. Therefore, trace information can be acquired even in a field that does not share infrastructure.

  In the above embodiment, the trace information is acquired from the event data and the event activity data. However, the present invention is not limited to this. Only the event data is stored, and the trace information is acquired from the stored event data. It may be configured.

  As mentioned above, although embodiment of this invention was described with reference to drawings, this invention is not limited to the thing of embodiment shown in figure. Various modifications and variations can be made to the illustrated embodiment within the same range or equivalent range as the present invention.

  The trace information acquisition system, trace information acquisition method, trace information acquisition device, trace information acquisition program, and storage medium according to the present invention are effective when it is necessary to appropriately acquire trace information in an environment that does not share infrastructure. Used.

It is a conceptual diagram which shows event data. It is a system configuration figure showing the hardware configuration of the trace information acquisition system concerning one embodiment of this invention. It is a flowchart which shows the flow of operation | movement in the case of memorize | storing event data. It is a block diagram of the trace information acquisition system concerning one embodiment of this invention. It is a flowchart which shows the flow of a process in the case of acquiring the trace information of a product. It is a figure which shows an example of the event data in the case of performing product mounting operation | work using the component mounting machine which mounted | wore the assembly | attachment component reel. FIG. 7 is a diagram showing association of event data in the case shown in FIG. 6. It is a figure which shows an example of the event data in the manufacturing process from a product order to shipment.

Explanation of symbols

  11 Event data, 12a Mono data, 12b Person data, 12c Time data, 12d Position data, 12e Status data, 13 Event activity data, 14a Production quantity data, 14b Carry-in / out data, 14c Work daily report data, 14d Environmental data, 14e Electric power Quantity data, 21 trace information acquisition system, 22, 23 server, 24a, 24b, 24c, 24d computer, 25a, 25b sensor device, 26 connection line, 27 RFID tag system, 28a reader / writer, 28b RFID tag, 29 products.

Claims (10)

A trace information acquisition system for acquiring trace information on a product manufactured through a plurality of stages,
Storage means for storing event data relating to events performed on the product;
Obtaining means for obtaining trace information from the event data stored by the storage means,
The trace information acquisition system, wherein the event data has a common data format in the plurality of stages. The trace information acquisition system according to claim 1, wherein the event data includes mono data related to the event, human data related to the event, time data related to the event, position data related to the event, and state data related to the event. The storage means stores event activity data which is information on business activities to be stored when an event occurs,
The trace information acquisition system according to claim 1, wherein the acquisition unit acquires trace information from the event activity data stored by the storage unit. The trace according to claim 1, wherein the acquisition unit includes an extraction unit that extracts a plurality of the event data associated with each other from the plurality of event data stored by the storage unit. Information acquisition system. 5. The trace information acquisition system according to claim 4, wherein the extraction unit extracts, as event data associated with each other, data having the same time in the time data related to the event among the plurality of event data. The trace information acquisition system according to claim 1, wherein the storage unit stores the event data using an RFID tag. A trace information acquisition method for acquiring trace information about a product manufactured through a plurality of stages,
A storage step for storing event data relating to an event performed on a product having a common data format in the plurality of stages;
A trace information acquisition method comprising: an acquisition step of acquiring trace information from the event data stored in the storage step. A trace information acquisition device that acquires trace information about a product manufactured through a plurality of stages,
A storage unit having a common data format in the plurality of stages and storing event data relating to an event performed on a product;
A trace information acquisition apparatus comprising: an acquisition unit that acquires trace information from the event data stored by the storage unit. Computer
Storage means for storing event data relating to events performed on a product having a common data format in the plurality of stages in order to obtain trace information relating to a product manufactured through a plurality of stages;
And a trace information acquisition program for functioning as acquisition means for acquiring trace information from the event data stored by the storage means. A computer-readable storage medium storing the trace information acquisition program according to claim 9.

Images