JP4949968B2 - Trace information management device, trace information management method, program, and trace information management system - Google Patents

Description

  The present invention relates to a technique for managing trace information for tracking a product.

  There is a system that implements a traceability function that tracks products over the course of manufacturing, distribution, and sales. Such a system stores information for tracking products and the like (hereinafter referred to as “trace information”) and manages the trace information. For example, Patent Document 1 describes a technique for realizing a traceability function.

JP 2005-267625 A

  The trace information may include public information that can be viewed from a plurality of companies and non-public information that each company does not want to disclose to other companies. For example, the public information is information such as the shipping status and processing status of the product, and the non-public information is information related to the raw materials and suppliers of the product.

  In order to manage such trace information including public information and non-public information, a server that manages public information and a server that manages non-public information are provided, and the public information and the non-public information are separately provided. It is desirable to manage. However, in order for the users of each company to browse the tracking information using both the public information server and the private information server, the information stored in both servers is browsed alternately. This is inconvenient for the user.

  An object of the present invention is to provide a technique for improving the convenience of a user by efficiently managing public information and non-public information included in trace information in a system for managing trace information.

In order to solve the above-mentioned problem, the present invention is a trace information management device for accumulating trace information relating to an article, the input receiving unit receiving input of trace information having a unique data structure, and the input receiving unit A data conversion processing unit that converts the trace information into public trace information having a standardized data structure when the information to be kept private is not included in the trace information , and a public trace converted by the data conversion processing unit transmit information to published server, the transmission and reception unit which receives the public trace information from the public server, a public trace information the transceiver unit receives said input and trace information accepting unit accepts, integrated information storage unit A data integration processing unit to be stored in the transmission / reception unit, wherein the transmission / reception unit corresponds to the public trace information transmitted to the public server The data conversion processing unit converts the public trace information received by the transmission / reception unit into trace information, and the data integration processing unit converts the data conversion processing unit stores the trace information converted into the integrated information storage unit, and wherein a call.

  According to the trace information management device of the present invention, it is possible to efficiently manage public information and non-public information included in trace information, and improve user convenience.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

  As shown in FIG. 1, the trace information management system 50 applied to the embodiment of the present invention includes a trace information management device 100 and a public server 200. As illustrated, the trace information management apparatus 100 and the public server 200 are connected to each other via a network 150. Although not shown, a plurality of trace information management devices 100 are connected to the network 150. In this case, the trace information management device 100 is installed in each company (for example, company A, company B, company C). . Note that the network 150 is, for example, the Internet.

  The trace information management apparatus 100 manages trace information for tracking products and the like. Specifically, the trace information management apparatus 100 shares public trace information with other companies (other trace information management apparatuses 100) by providing (uploading) public information included in the trace information to the public server 200. can do. Further, the trace information management apparatus 100 acquires (downloads) public trace information provided by the other trace information management apparatus 100 to the public server 200, and enables the user to view this information. Furthermore, the trace information management apparatus 100 accumulates the private information included in the trace information without providing it to the public server 200. At this time, the public trace information acquired from the public server 200 is integrated and accumulated.

  The trace information management apparatus 100 as described above includes a control unit 110, a storage unit 120, and an interface unit 130 as illustrated.

  The interface unit 130 is an interface for transmitting and receiving communication data via the network 150.

  The storage unit 120 includes a local information database (hereinafter abbreviated as “DB”) 121, a conversion rule DB 122, and an integrated information DB 123.

  The local information DB 121 accumulates (registers) the trace information generated by the trace information management apparatus 100 with a unique specification (data structure) in the company. Note that the trace information is generated for each work related to the trace target article (for example, manufacture, shipment, arrival, incorporation, sale, etc. of the article (product)). At the same time, the local information DB 121 stores transition information for specifying the order of each work. Specifically, the local information DB 121 stores a local information table 1210 and a transition information table 1240.

  As shown in FIG. 2, the local information table 1210 includes a trace ID column 1211, a target ID column 1212, a date / time column 1213, a location column 1214, a work information column 1215, a person in charge column 1216, and a transmission flag column. 1217. Note that data stored in association with the same row (hereinafter referred to as “record 1218”) in each column (1211-1217) is collectively referred to as “trace information”.

  The trace ID column 1211 stores a code (trace ID) for identifying trace information generated by the trace information management apparatus 100 (inside the company). For example, in the present embodiment, a non-overlapping number string such as “1000001” is stored.

  The target ID column 1212 stores a code (target ID) for identifying the product to be traced. For example, in the present embodiment, a numeric string such as “001” is stored. The target ID stored in the target ID column 1212 includes header information including information specifying a specification such as RFID (Radio Frequency IDentification), company information specifying a company, a serial code specifying a product, It may be information that is synthesized.

  The date / time column 1213 stores data (date / time information) for specifying the date and time when the trace information is generated. For example, in the present embodiment, a character string such as “2009/1/1 12:00” is stored.

  The location column 1214 stores data (location information) for specifying a location where a predetermined work has been performed on the product to be traced. For example, in this embodiment, a character string such as “company A factory A” is stored. Here, for example, identification information for specifying the company name and the factory name is included at the head of each information of “company A” and “factory A”.

  The work information column 1215 stores data (work information) for specifying work performed on the trace target product. For example, in this embodiment, character strings such as “shipment”, “arrival”, “built-in”, and “sales” are stored.

  The person-in-charge column 1216 stores data (person-in-charge information) that identifies a person in charge who has performed a predetermined work on the product to be traced. For example, in this embodiment, a character string such as “factory A shipping charge Sato” is stored. Here, for example, identification information for specifying the factory name, the work name, and the person in charge name is included at the head of each information of “factory A”, “shipment”, and “person in charge Sato”.

  The transmission flag column 1217 stores a flag (transmission flag) that identifies whether the trace information is information that has already been transmitted to the public server 200. For example, in this embodiment, a character string “sent” is stored. The transmission flag stored in the transmission flag column 1217 is also a flag for identifying whether or not the trace information that is non-public information has already been registered in the integrated information DB 123, and is a character string such as “registered”, for example. .

  As illustrated in FIG. 3, the transition information table 1240 includes a transition source column 1241 and a transition destination column 1242. The data stored in association with the same row (hereinafter referred to as “record 1243”) in each column (1241, 1242) is collectively referred to as “transition information”.

  The transition source column 1241 stores transition source information that identifies the task that is the transition source, and the transition destination column 1242 stores transition destination information that identifies the task that is the transition destination. Specifically, the transition source column 1241 and the transition destination column 1242 store data (transition source information and transition destination information) indicating the trace ID stored in the trace ID column 1211 of the local information table 1210. For example, in the present embodiment, the same trace ID as the trace ID 1211 of the local information table 1210 is stored.

  If the local information table 1210 is referenced, the work (work information) included in the trace information can be specified by the trace ID. Therefore, in the transition information table 1240, the transition ID column 1241 stores the trace ID that identifies the work performed first, and the transition destination column 1242 stores the trace ID that specifies the work performed later. . Thereby, by referring to the transition information stored in the transition information table 1240, it is possible to specify the order of work (performed on the article (product)) regarding the article to be traced.

  The transition information will be described with reference to a specific example shown in FIG. For example, after the product (part 001) is shipped to the factory C (401) at the factory A and the product (part 002) is shipped (402) to the factory C at the factory B, the product (part 001, In some cases, the parts 002) are received (403, 404) and the product 003 is assembled (405). In this case, trace information (record 1218) is generated by assigning a trace ID to each of the operations (401 to 405). At this time, if the trace IDs assigned to the operations (401 to 405) are “1000001”, “1000002”, “2000011”, “2000012”, and “2000013”, respectively, As shown in FIG. 3, transition information (record) that associates a trace ID (transition source column 1241) that identifies the work performed earlier with a trace ID (transition destination column 1242) that identifies the work performed later. 1243) is generated. In addition, the arrow shown in FIG. 4 has its start point written at the work position specified by the trace ID in the transition source column 1241, and its end point written at the work position specified by the trace ID in the transition destination column 1242. ing.

  Returning to FIG. 1, the rule conversion DB 122 stores data conversion rules for ensuring consistency of trace information between the public server 200 and the trace information management apparatus 100. Specifically, the rule conversion DB 122 stores a conversion rule table 1220.

  The conversion rule table 1220 includes a conversion rule ID column 1221 and a data conversion rule column 1242, as shown in FIG. The data stored in association with the same row (hereinafter referred to as “record 1223”) in each column (1221, 1222) is collectively referred to as “conversion rule information”.

  The conversion rule ID column 1221 stores a code (conversion rule ID) for identifying a data conversion rule registered in the trace information management apparatus 100 (inside the company). For example, in the present embodiment, non-overlapping number strings such as “1” and “2” are stored. For example, numbers are assigned to the conversion rule IDs in ascending order downward in the conversion rule table 1220.

  The data conversion rule column 1222 stores an instruction code or a program (which may be a path or a file name specifying a program storage location) describing a rule for converting trace information. Hereinafter, this instruction code or program is referred to as a “data conversion rule”. Data conversion rules include, for example, “Extract company name from location information and fill in the person in charge”, “Convert standard specification code to internal code”, “Delete public information of non-trade company (trading company Z)”, It includes a conversion rule such as “Check and check consistency of trace ID”. The data conversion rule is applied to data received from the public server 200 and data transmitted to the public server 200.

  Returning to FIG. 1, the integrated information DB 123 stores integrated information obtained by integrating the trace information generated by the trace information management apparatus 100 and the public trace information received from the public server 200. Specifically, the integrated information DB 123 stores an integrated information table 1230.

  As shown in FIG. 6, the integrated information table 1230 includes a trace ID column 1231, a target ID column 1232, a date / time column 1233, a location column 1234, a work information column 1235, and a person in charge column 1236. . The data stored in association with the same row (hereinafter referred to as “record 1237”) in each column (1231 to 1236) is collectively referred to as “integrated trace information”.

  In the trace ID column 1231, the target ID column 1232, the date / time column 1233, the location column 1234, the work information column 1235, and the person-in-charge column 1236, the trace ID, target ID, date / time information stored in the local information table 1210, respectively. Codes or data corresponding to location information, work information, and person-in-charge information are stored. For example, in the present embodiment, the same code or data stored in the local information table 1210 is stored. In addition, a code or data stored in the local information table 1210 converted according to the data conversion rule in the data conversion rule column 1222 is also stored. Furthermore, the code or data received from the public server 200 is also converted according to the data conversion rule in the data conversion rule column 1222 is stored.

  However, the data structure of the integrated information table 1230 is not limited to this, and may be based on specifications unique to each company.

  Returning to FIG. 1, the control unit 110 performs various processes in the trace information management apparatus 100. Therefore, the control unit 110 includes an input reception unit 111, a data registration unit 112, a data conversion processing unit 113, a data integration processing unit 114, a data transmission / reception unit 115, and a display processing unit 116.

  The input receiving unit 111 performs a process of receiving an input for registering trace information and data conversion rules. Specifically, the input receiving unit 111 receives data input from an input device such as a keyboard, data read from an IC tag attached to a product by an IC tag reader, and the like. Then, the input reception unit 111 notifies the data registration unit 112 of the received input data.

  The data registration unit 112 performs processing for storing the trace information and the data conversion rule notified from the input receiving unit 111 in the local information DB 121 and the conversion rule DB 122, respectively. When registering the trace information in the local information DB 121, the data registration unit 112 adds the trace ID to each input data notified from the input reception unit 111 to generate trace information (record 1218). Further, the data registration unit 112 registers transition information corresponding to the registered trace information in the local information DB 121. Specifically, the data registration unit 112 receives an instruction from the user and registers the transition information in the transition information table 1240. However, the data registration unit 112 changes the transition information according to a predetermined rule from the date / time information (date / time column 1213), location information (location column 1214), and work information (work information column 1215) included in each trace information of the local information table 1210. And the generated transition information may be registered. In this case, the predetermined rule is stored in the storage unit 120 in advance.

  The data conversion processing unit 113 performs data conversion between the public server 200 and the trace information management apparatus 100 for ensuring consistency of trace information.

  Specifically, the data conversion processing unit 113 performs processing for converting the trace information according to the data conversion rule stored in the data conversion table 1220. For example, the data conversion processing unit 113 refers to the data conversion table 1220 and acquires the data conversion rule 1222 of each record 1223 when the data transmission / reception unit 115 described later acquires public trace information from the public server 200. Applies to trace information. After the application, the data conversion processing unit 113 notifies the data integration processing unit 114 of the converted integrated trace information.

  On the other hand, the data conversion processing unit 113 also applies the data conversion rule 1222 to the provided trace information even when the data transmitting / receiving unit 115 provides the trace information to the public server 200. After the application, the data conversion processing unit 113 notifies the data transmission / reception unit 115 of the converted public trace information.

A typical example of the data conversion process performed by the data conversion processing unit 113 by applying the data conversion rule (data conversion rule 1222) to the trace information is shown below.
When the data conversion rule to be applied to the trace information is “Extract company name from location information and fill in the person in charge column” The data conversion processing unit 113 has the company name in the person in charge column 1216 of the local information table 1210 When there is no data having identification information for specifying this, the company name in the location column 1214 is extracted, and the extracted company name is entered in the person in charge column 1236 of the integrated information table 1236. When the public trace information is acquired from the public server 200, the company name extracted from the location column 2304 of the acquired public trace information is entered in the person in charge column 1236 of the integrated information table 1236.
When the data conversion rule is “convert standard specification code to in-house code” When the data conversion processing unit 113 acquires the public trace information from the public server 200, each data included in the public trace information (public information described later) Data in each column (2301 to 2305) of the table 2300 is converted so as to conform to the in-house specifications (in-house unique data structure) (for example, header information included in the target ID (target ID column 2302)) , Delete company information, etc.). Further, although not shown in FIG. 5, “conversion of in-house specification code to standard specification code” may be provided in the data conversion rule. In this case, when the data conversion processing unit 113 provides public trace information to the public server 200, the trace information of the internal specification (internal data structure) included in the local information DB 121 is converted into the standard specification (standard data structure). Data structure).
When the data conversion rule is “delete public information of non-trade company (trading company Z)” The data conversion processing unit 113 registers in the storage unit 120 in advance in the location column 2304 of the public trace information acquired from the public server 200. The public trace information having the company name that matches the non-trade company name (for example, trading company Z) is deleted (not notified to the data integration processing unit 114).
When the data conversion rule is “conversion after checking the consistency of the trace ID” When the data conversion processing unit 113 converts the trace information in the local information table 1210, the trace ID (trace ID column 1211) of the company specification is used. ) Is converted to a standard trace ID. Further, when public trace information is acquired from the public server 200, it is determined whether or not the trace ID (trace ID field 2301) included in the acquired public trace information is the same specification as the in-house specification. Convert to in-house specifications. Here, for example, the header portion of the trace ID includes information specifying whether the specification is in-house specification or standard specification, and the data conversion processing unit 113 stores data stored in the storage unit 120 in advance. Compared with, the specification of the trace ID can be specified.

  The data conversion performed by the data conversion processing unit 113 is not limited to these processes.

  The data integration processing unit 114 includes the trace information (local information) registered by the data registration unit 112 of the trace information management apparatus 100 (in-house) and the public trace provided to the public server 200 by another trace information management apparatus 100 (other company). Processing to integrate information (shared information).

  Specifically, the data integration processing unit 114 acquires the trace information (local information) stored in the local information table 1230 at a predetermined time interval (for example, every 2 hours). At this time, all trace information (record 1218) having a transmission flag (transmission flag column 1217) that is not “transmitted” and “registered” is sequentially stored as integrated trace information in the integrated information table 1230. At this time, the data integration processing unit 114 determines whether the trace information stored in the local information table 1230 is public information or non-public information. If it is public information, the data integration processing unit 114 notifies the data conversion processing unit 113 of the trace information, and stores the trace information in the integrated information table 1230 as integrated trace information. On the other hand, if it is non-public information, the data integration processing unit 114 stores the trace information as it is in the integrated information table 1230 as the integrated trace information without notifying the data conversion processing unit 113 of the trace information. Then, the local information table 1210 is accessed, and the transmission flag 1217 of the trace information (record 1218) corresponding to the integrated trace information stored in the integrated information table 1230 is changed to “registered”. Here, whether the trace information is public information or non-public information is determined with reference to the location 1214 and the work information 1215 of the local information table 1210. For example, when the place 1214 is “company C (company that does not want to be disclosed)” and the work information 1215 is “arrival”, the trace information having such information is determined as non-public information. Note that the data for determining whether to open or close in this way is registered in the storage unit 120 in advance.

  In addition, the data integration processing unit 114 sequentially stores the public trace information (shared information) notified from the data conversion processing unit 113 from the public server 200 in the integrated information table 1230 as integrated trace information. Note that the data integration processing unit 114 updates the transition information table 1240 stored in the local information DB 1210 when storing the public trace information (shared information) from the public server 200 in the integrated information table 1230. Specifically, the data integration processing unit 114 adds the transition information acquired from the public server 200 together with the public trace information to the transition information table 1240.

  The data transmission / reception unit 115 performs a process of providing the public trace information to the public server 200 and a process of acquiring the public trace information from the public server 200.

  Specifically, when acquiring the public trace information, the data transmitting / receiving unit 115 transmits a request for acquiring the public trace information to the public server 200 via the interface unit 130 to acquire the public trace information. . Then, the data transmitting / receiving unit 115 includes the public trace information corresponding to the trace information whose transmission flag 1217 of the local information table 1210 is “transmitted” among the trace information acquired from the public server 200 (trace information published by the company). Other than the above, the data conversion processing unit 113 is notified of the public trace information. The data transmission / reception unit 115 acquires the public trace information from the public server 200 at a predetermined time interval (for example, every two hours).

  On the other hand, when providing the public trace information to the public server 200, the data transmission / reception unit 115 provides the public trace information to the public server 200 via the interface unit 130. Specifically, when the data transmission / reception unit 115 is notified of the public trace information from the data conversion processing unit 113, the data transmission / reception unit 115 provides the trace information to the public server 200 via the interface unit 130. At this time, the data transmitting / receiving unit 115 accesses the local information table 1210 and changes the transmission flag (transmission flag column 1217) of the trace information (record 1218) corresponding to the provided public trace information to “transmitted”. Further, the data transmission / reception unit 115 may acquire transition information having transition source information or transition destination information corresponding to the trace ID of the provided public trace information from the local information DB 210 and provide the information to the public server 200.

  The display processing unit 116 performs processing for displaying the integrated information integrated by the data integration processing unit 114 on an output device such as a display. Specifically, the display processing unit 116 displays a list of integrated trace information stored in the integrated information table 1230 when the input receiving unit 111 receives an instruction to display integrated information from the user. In this case, for example, the display processing unit 116 may convert the list of integrated trace information in the integrated information table 1230 illustrated in FIG. 6 into image data.

  In addition, the display processing unit 116 may display a list of trace information, and may display a transition diagram of work performed on the product to be traced as shown in FIG. In this case, the display processing unit 116 refers to the integrated information table 1230 and the transition information table 1240 of the local information DB 121 to generate a transition diagram screen. Specifically, a display column for displaying the location information stored in the location column 1234 of the integrated information table 1230 is provided. However, duplicate location information is not displayed. At this time, a rectangular thick frame is provided in the vicinity of each display field (for example, a thick frame is provided for each of factory A, factory B, factory C, and store D). The display processing unit 116 is specified by the target ID (target ID column 1232) and work information (work information column 1235) included in the record 1237 having the location information for specifying the thick frame in each thick frame. A display field for displaying data is provided. At this time, an ellipse is provided in the vicinity of each display field (for example, shipment 401 of component 001, shipment 402 of component 002, receipt 403 of component 001, etc.). Further, the display processing unit 116 displays an ellipse surrounding the data specified by the transition source information (transition source column 1241) or the transition destination information (transition destination column 1242) associated with the same record 1243 of the transition information table 1240. Provide arrows to connect. For example, when the transition source information is “1000001” and the transition destination information is “1000002”, “1000001” is identified by the target ID and work information associated with the record 1237 in the trace ID column 1231 of the integrated information table 1230. The arrow to the ellipse specified by the work ID and the target ID associated with the record 1237 having “1000001” in the trace ID column 1231 is provided.

  The trace information management apparatus 100 configured as described above can manage public information and private information in an integrated manner. In addition, since the trace information management apparatus 100 gives a transmission flag indicating transmission to the public information transmitted (provided) to the public server 200, the trace information management apparatus 100 does not receive the provided public information from the public server 200, and Double management can be prevented. Further, when transmitting / receiving public trace information, the trace information management apparatus 100 performs mutual exchange of local (in-house) specifications (in-house unique data structure) and standard specifications (standard data structure) with respect to the public trace information. Because of the conversion, the user (each company) can browse the integrated trace information in the integrated information DB 123 without being conscious of the specifications and standard specifications of other companies.

  The public server 200 includes an interface unit 210, a public information management unit 220, and a public information DB 230, as illustrated.

  The interface unit 210 is an interface for transmitting and receiving communication data via the network 150.

  The public information DB 230 stores public information (trace information) provided from each trace information management device 100. Specifically, the public information DB 230 stores a public information table 2300. Further, transition information corresponding to the trace information is stored together with the public information table 2300.

  As shown in FIG. 7, the public information table 2300 includes a trace ID column 2301, a target ID column 2302, a date / time column 2303, a location column 2304, and a work information column 2305. Note that data stored in association with the same row (hereinafter referred to as “record 2306”) in each column (2301 to 2305) is collectively referred to as “public trace information”.

  In the trace ID column 2301, the target ID column 2302, the date / time column 2303, the location column 2304, and the work information column 2305, codes or data provided from the respective trace information management devices 100 are stored. For example, in the present embodiment, the code or data stored in the local information table 1210 is a code or data converted into a standard specification (standard data structure).

  The public information management unit 220 registers public information and publicizes the registered public information in response to a request. Specifically, the public information management unit 220 stores the public trace information provided from each trace management device 100 in the public information DB 230, and requests from the trace management device 100 (company) that requires the public trace information. In response to this, a process of providing public trace information stored in the public information DB 230 is performed. When providing public trace information, transition information having transition source information or transition destination information corresponding to the trace ID of the public trace information is acquired from the public information DB 230 and provided.

  The trace information management device 100 and the public server 200 configured as described above include, for example, a CPU 601, a main storage unit 602, an external storage device 603 such as an HDD, a CD-ROM or a DVD as shown in FIG. A reading device 605 for reading information from a portable storage medium 607 having portability such as a ROM, an input / output device 606 such as a display, a keyboard, a mouse, an IC tag reader, and a NIC (Network And a communication device 604 such as an interface card).

  For example, the storage unit 120 and the public information DB 230 illustrated in FIG. 1 can be realized by the external storage device 603, and the control unit 110 and the public information management unit 220 mainly store a predetermined program stored in the external storage device 603. This can be realized by loading the storage device 602 and executing it by the CPU 601.

  The predetermined program is downloaded from the portable storage medium 607 via the reading device 605 or from the network via the communication device 604 to the external storage device 603, and then loaded onto the main storage device 602 and loaded on the CPU 601. May also be executed. Alternatively, the program may be directly loaded on the main storage device 602 from the portable storage medium 607 via the reading device 605 or from the network via the communication device 604 and executed by the CPU 601.

  FIG. 9 is a flowchart showing processing at the time of obtaining public information performed by the trace information management apparatus 100.

  The data transmission / reception unit 115 of the trace information management apparatus 100 starts a process for obtaining public information when a predetermined timing comes. Here, the predetermined timing may be, for example, a time when a predetermined time (for example, 2 hours) elapses by measuring with an internal timer included in the data transmission / reception unit 115.

  First, the data transmission / reception unit 115 acquires public trace information (public information) from the public server 200 (step S101). Specifically, the data transmission / reception unit 115 acquires public trace information from the public server 200 via the interface unit 130, and temporarily stores the acquired public trace information. The public trace information acquired at this time is all the public trace information stored in the public information DB 230 by the public server 200. Further, the data transmitting / receiving unit 115 obtains transition information corresponding to the public trace information from the public server 200 together with the public trace information.

  Next, the data transmission / reception unit 115 determines whether or not the public trace information acquired in step S101 is public trace information that the trace information management apparatus 100 (in-house) has provided to the public server 200 in the past (step). S102). Specifically, first, the data transmission / reception unit 115 refers to a trace ID (trace ID column 2301) included in one public trace information among all the public trace information acquired from the public server 200. Then, the trace information having the trace ID (trace ID column 1211) corresponding to the trace ID is extracted from the local information table 1210 (at this time, if the trace ID in the trace ID column 2301 is not in-house specification, The data conversion processing unit 113 may convert the trace ID into in-house specifications). Further, when the transmission flag (transmission flag field 1217) of the extracted trace information is “transmitted”, it is determined that the acquired public trace information is public trace information provided in the past, and “transmitted” is determined. If it is other than (for example, blank), it is determined that it is public trace information that has not been provided in the past.

  In step S102, when the data transmission / reception unit 115 determines that the public trace information has been provided to the public server 200 in the past (step S102; Yes), the data transmission / reception unit 115 deletes the public trace information from the data transmission / reception unit 115 (step S103). . By the processing in step S103, the data transmitting / receiving unit 115 excludes the public trace information published by the company from the public trace information acquired from the public server 200, and notifies the data conversion processing unit 113 of other public trace information. To do. Thereafter, the data transmitter / receiver 115 shifts the processing to step S104.

  On the other hand, when the data transmitting / receiving unit 115 determines in step S102 that the trace information is not public trace information provided to the public server 200 in the past (step S102; No), the process proceeds to step S104.

  In step S104, the data transmission / reception unit 115 determines whether or not the processing in steps S102 and S103 has been performed on all the public trace information acquired in step S101 (step S104). For example, the data transmission / reception unit 115 performs this determination with reference to a memory address storing the public trace information.

  If it is determined in step S104 that the processes of steps S102 and S103 have not been performed for all the public trace information (step S104; No), the data transmitting / receiving unit 115 shifts the process to step S102. On the other hand, when it is determined that the processing of step S102 and step S103 has been performed for all the public trace information (step S104; Yes), the data transmission / reception unit 115 stores the public trace information (or storage) remaining in the data transmission / reception unit 115. Is notified to the data conversion processing unit 113.

  When the trace information is notified, the data conversion processing unit 113 performs data conversion for consistency between the public server 200 and the trace information management apparatus 100 on the notified public trace information (step) S105). Specifically, the data conversion processing unit 113 sets the data conversion rule (data conversion rule column 1222) corresponding to the conversion rule ID in ascending order of the conversion rule ID (conversion rule ID column 1221) of the conversion rule table 1220. This is applied to the public trace information notified from the data transmitting / receiving unit 115 (or the public trace information remaining in the data transmitting / receiving unit 115). Data conversion rules that cannot be applied at this time are not applied. After the application, the data conversion processing unit 113 notifies the data integration processing unit 114 of the integrated trace information that has been converted into in-house specifications (local information format).

  When the integrated trace information after data conversion is notified, the data integration processing unit 114 sequentially registers (stores) the integrated trace information (shared (public) information) in the integrated information table 1230 (step S106). At the same time, the data integration processing unit 114 performs processing for adding the transition information stored in the data transmission / reception unit 115 to the transition information table 1240.

  Thereafter, the data integration processing unit 114 ends the process at the time of obtaining public information.

  FIG. 10 is a timing chart of processing when providing the public information performed by the trace information management apparatus 100 and the public server 200.

  The data integration processing unit 114 of the trace information management apparatus 100 starts a process for providing public information when a predetermined timing comes. Here, the predetermined timing may be, for example, a time when a predetermined time (for example, 2 hours) elapses by measuring with an internal timer included in the data integration processing unit 114.

  First, the data integration processing unit 114 acquires trace information (public information / private information) from the local information table 1210 (step S201). Specifically, the data integration processing unit 114 acquires trace information from the local information table 1210 and temporarily stores the acquired trace information. The trace information acquired at this time is all the trace information whose transmission flag (transmission flag column 1217) is not “transmitted” or “registered” among the trace information stored in the local information table 1210. .

  Subsequently, the data integration processing unit 114 determines whether the stored trace information is public information or private information (step S202). If it is public information, the data integration processing unit 114 notifies the data conversion processing unit 113 of the trace information.

  On the other hand, if it is non-public information, the data integration processing unit 114 stores the trace information in the integrated information table 1230 as integrated trace information (step S203). At this time, the data integration processing unit 114 changes the transmission flag (transmission flag column 1217) of the local information table 1210 to “registered”.

  Receiving the notification of the trace information (public information) from the data integration processing unit 114, the data conversion processing unit 113 converts the trace information into a data format (for example, standard specification) that can be processed by the public server 200 (step S1) S204). Specifically, the data conversion processing unit 113 sets the data conversion rule (data conversion rule column 1222) corresponding to the conversion rule ID in ascending order of the conversion rule ID (conversion rule ID column 1221) of the conversion rule table 1220. This is applied to the trace information notified from the data integration processing unit 114. Data conversion rules that cannot be applied at this time are not applied. After the application, the data conversion processing unit 113 notifies the data transmission / reception unit 115 of the public trace information converted into the standard specification.

  Upon receiving the notification of the public trace information, the data transmitting / receiving unit 115 provides (transmits) the public trace information to the public server 200 via the interface unit 130 (step S205). At this time, the data transmitting / receiving unit 115 may provide the public server 200 with transition information corresponding to the provided public trace information. Thereafter, the data transmitter / receiver 115 shifts the processing to step S206.

  At this time, the public server 200 receives the public trace information provided from the trace information management apparatus 100 (step S301). Specifically, the public information management unit 220 of the public server 200 receives the public trace information via the interface unit 210.

  The public information management unit 220 registers (stores) the public trace information provided from the trace management apparatus 100 in the public information table 2300 of the public information DB 230 (step S302). The public information management apparatus 220 can return the public trace information registered (stored) in the public information table 2300 when requested by another trace management apparatus 100. The public information management unit 220 stores the transition information corresponding to the public trace information in the public information DB 230 together with the public trace information.

  On the other hand, in step S206, the data transmitting / receiving unit 115 of the trace information management apparatus 100 registers a trace information transmission flag (transmission flag column 1217) corresponding to the public trace information provided to the public server 200 (step S206). Specifically, the data transmission / reception unit 115 accesses the local information table 1210 and changes the transmission flag (transmission flag column 1217) of the provided trace information (record 1218) to “transmitted”.

  Subsequently, the data integration processing unit 114, among the trace information temporarily stored in the data integration processing unit 114, the trace information determined to be public information in step S202 (data not converted by the data conversion processing unit 113) Are registered (stored) in the integrated information table 1230 as integrated trace information (step S207).

  Thereafter, the data integration processing unit 114 ends the process when providing public information.

  In addition, this invention is not limited to the said embodiment, A various deformation | transformation and application are possible.

  For example, in the above-described embodiment, the data transmission / reception unit 115 starts processing for obtaining public information when a predetermined timing comes. However, the present invention is not limited to this. For example, when a user instruction is received from the input receiving unit 111, a process for obtaining public information may be started.

  In the above-described embodiment, the data integration processing unit 114 starts processing when providing public information when a predetermined timing comes. However, the present invention is not limited to this. For example, when receiving an instruction from the user of the input receiving unit 111, the process at the time of providing public information may be started.

  Further, the target ID (target ID column 2302) of the public information table 2300 is, for example, a JAN code or UPC code that defines a system such as a barcode, or an EPC code that defines an ID system such as RFID. It may be numbered.

  In the above embodiment, the transition information table 1240 is stored in the local information DB 121. However, the present invention is not limited to this, and may be stored in the integrated information DB 123, for example.

  Furthermore, in the above embodiment, the transmission flag column 1217 is provided in the local information table 1210. However, the present invention is not limited to this, and for example, a transmission flag column may be provided in the integrated information table 1230.

It is a functional block diagram of the trace information management system which concerns on embodiment of this invention. It is the figure which showed notionally the data structure of a local information table. It is the figure which showed notionally the data structure of the transition information table. It is explanatory drawing which shows the transition of the operation | work performed with respect to the goods for trace. It is the figure which showed notionally the data structure of the conversion rule table. It is the figure which showed notionally the data structure of the integrated information table. It is the figure which showed notionally the data structure of the public information table. It is the figure which showed an example of the hardware constitutions of a trace information management apparatus and a public server. It is a figure which shows the flowchart of the process at the time of the public information acquisition performed with a trace information management apparatus. It is a figure which shows the timing chart of the process at the time of the provision of public information performed with a trace information management apparatus and a public server.

Explanation of symbols

50 ... Trace information management system 100 ... Trace information management device 110 ... Control unit 120 ... Storage unit 130 ... Interface unit 111 ... Input accepting unit 112 ... Data registration unit 113 ... Data conversion processing unit 114 Data integration processing unit 115 Data transmission / reception unit 116 Display processing unit 121 Local information DB 122 Conversion rule DB 123 Integration information DB 150 ..Network 200 200 Public server 220 Public information management unit 230 Public information DB 401 401 Parts 001 shipment 601 CPU 602 Main storage 603 External storage 604 ..Communication device 605 ..Reading device 606 ..Input / output device 607 ..Portable storage medium 1210 ..Local information table 1220 · conversion rule table, 1230 ... integrated information table, 1240 ... transition information table, 2300 ... public information table.

Claims (8)

A trace information management device for accumulating trace information about an article,
An input receiving unit for receiving input of trace information having a unique data structure;
A data conversion processing unit for converting the trace information into public trace information having a standardized data structure when the information to be kept private is not included in the trace information received by the input reception unit;
A transceiver for the data conversion processing unit transmits the public trace information converted into published server, receives the public trace information from the public server,
A data integration processing unit that stores the public trace information received by the transmission / reception unit and the trace information received by the input reception unit in an integrated information storage unit;
The transmission / reception unit adds a flag indicating that transmission has been completed to the trace information corresponding to the public trace information transmitted to the public server,
The data conversion processing unit converts the public trace information received by the transmission / reception unit into trace information,
The data integration processing unit stores the trace information converted by the data conversion processing unit in the integrated information storage unit,
Trace information management apparatus according to claim and this. The trace information management device according to claim 1 ,
The data integration processing unit stores the trace information excluding trace information corresponding to the public trace information transmitted to the public server in the integrated information storage unit;
A trace information management device. The trace information management device according to claim 1 ,
The data conversion processing unit converts the public trace information into trace information when the transmission / reception unit determines that the flag is not added to the trace information corresponding to the public trace information received from the public server.
A trace information management device. The trace information management device according to claim 1 ,
A conversion rule storage unit for storing a conversion rule for specifying a rule of conversion processing performed by the data conversion processing unit;
When converting the trace information received by the input receiving unit into public trace information, the data conversion processing unit applies the conversion rule to the trace information, and converts the public trace information received by the transmitting / receiving unit into the trace information. When converting to, apply the conversion rule to the public trace information,
A trace information management device. The trace information management device according to any one of claims 1 to 4 ,
The data conversion processing unit includes information to be made private in the trace information when the location information including the work information and the company name relating to the item corresponding to the trace information does not include predetermined information to be kept secret. It is determined that
A trace information management device.   A trace information management method in a trace information management device for accumulating trace information about an article,
  The trace information management device includes a control unit,
  The control unit accepting input of trace information having a unique data structure;
  The control unit storing the received trace information in an integrated information storage unit;
  When the control unit does not include information to be disclosed in the received trace information, converting the trace information into public trace information having a standardized data structure;
  The control unit transmitting the converted public trace information to a public server;
  Adding a flag indicating that transmission has been completed to the trace information corresponding to the public trace information transmitted to the public server by the control unit;
  The control unit receiving public trace information from the public server;
  The control unit converting the received public trace information into trace information;
  The control unit storing the converted trace information in the integrated information storage unit;
A trace information management method characterized by:   A program that causes a computer to function as a trace information management device that accumulates trace information about an article,
  The computer functions as a control means,
  The control means includes
  A process of accepting input of trace information having a unique data structure;
  A process of storing the received trace information in an integrated information storage unit;
  A data conversion process for converting the trace information into public trace information having a standardized data structure when the received trace information does not include information to be disclosed;
  A transmission process for transmitting the converted public trace information to a public server;
  Processing for adding a flag indicating that transmission has been completed to the trace information corresponding to the public trace information transmitted to the public server;
  Processing to receive public trace information from the public server;
  A process of converting the received public trace information into trace information;
  A process of storing the converted trace information in the integrated information storage unit;
The program characterized by performing.   A trace information management system comprising a trace information management device for accumulating trace information relating to articles, and a public server for accumulating public trace information provided by other trace information management devices,
  The trace information management device
  An input receiving unit for receiving input of trace information having a unique data structure;
  A data conversion processing unit for converting the trace information into public trace information having a standardized data structure when the information to be kept private is not included in the trace information received by the input reception unit;
  A transmitting / receiving unit that transmits the public trace information converted by the data conversion processing unit to a public server, and receives the public trace information from the public server;
  A data integration processing unit for storing the public trace information received by the transmitting / receiving unit and the trace information received by the input receiving unit in an integrated information storage unit;
  With
  The public server is
  A public information management unit that stores the public trace information transmitted from the trace information management device in a public information storage unit,
  The transmission / reception unit of the trace information management device adds a flag indicating that transmission has been completed to the trace information corresponding to the public trace information transmitted to the public server,
  The data conversion processing unit of the trace information management device converts the public trace information received by the transmission / reception unit into trace information,
  The data integration processing unit of the trace information management device stores the trace information converted by the data conversion processing unit in the integrated information storage unit.
Trace information management system characterized by that.

Images