JP4175248B2 - Trace information conversion system - Google Patents

Description

  The present invention relates to a technique for collecting and using trace information indicating the distribution or manufacturing process of an article. In particular, the present invention relates to a technique for converting trace information in a plurality of data formats into a unified format.

  Conventionally, there is Patent Document 1 that grasps the distribution status of goods such as merchandise. Patent Document 1 discloses the following description as a configuration for properly grasping the status of physical distribution in real time. Traceability data is written to a non-contact single chip equipped with a tracking function-equipped package that wraps the article, and every time an article passes a control point, the traceability data stored in this non-contact single chip is read, and the read traceability data is It is transmitted and stored via a communication line. Then, the distribution status of the article is grasped using the stored traceability data.

JP 2000-233808 A

  Here, in the distribution of normal articles, a plurality of participants are involved. In other words, distributors, manufacturers (parts manufacturing, assembly), retailers, etc. are involved. These participants often have different forms of trace information indicating the distribution state of articles. Also, in each distributor, manufacturer, etc., the data format may be different if the supplier is different. Thus, the trace information is often handled in a plurality of data formats, and there is a problem that unified management is difficult.

  However, in Patent Document 1, it is an object to prevent a product received in a warehouse from being sold, and it is not considered at all that a plurality of data formats are mixed.

  The present invention employs the following configuration in order to solve the above problems. For the trace information transmitted from each participant, the identification information indicating the transmission source and the transmission destination is extracted from the trace information, and is converted into trace information in a predetermined data format by a conversion method according to the extracted identification information. . Here, extracting the identification information includes extracting information of a predetermined number of digits as identification information from the transmitted trace information. Moreover, extracting the information located in the predetermined position transmitted as identification information is included.

  According to the present invention, unified management can be executed even when there are a plurality of data formats in the trace information.

Embodiments of the present invention will be described below with reference to the drawings.
The trace information in the present invention is information extracted when a product is traded among a plurality of participants, and is stored for managing the transaction history of the product and for the participants to view.
FIG. 1 is an overall configuration diagram of the trace information conversion system of this embodiment, and FIG. 2 shows a processing flow of this embodiment.

  First, an overall configuration diagram of the trace information conversion system shown in FIG. 1 will be described.

  The trace information management system 110 includes a trace information management server 111, a unified trace information management database 112, and a mapping information management database 113. The trace information management system 110 is connected to the trace information registration system 130 and the trace information search terminal 133 via the communication network 120. The trace information registration system 130 is composed of a business system 131 for acquiring article trace information and a trace information registration terminal 132, and a plurality of trace information registration systems may exist.

  Hereinafter, the processing flow of the embodiment of the present invention will be described with reference to FIG.

  (Step 201) The trace information management server 111 receives a trace information registration request. The registration request procedure will be described in each embodiment described later. The received trace information may be a format depending on the trace information registration system instead of a single format, but is a format including information that can identify the transmitted trace information registration system.

  (Step 202) The trace information management server 111 analyzes the received trace information. The received trace information includes information for determining the trace information registration system that transmitted the trace information, and the format, data length, and meaning of the data of the trace information are specified based on the information. Can do.

  (Step 203) The trace information management server 111 analyzes the trace information and determines whether or not the supplier information is included in the trace information. Here, the supplier information means the person to whom the item to be tracked is passed next, and there may not be a business transaction relationship between the persons, and the person is the sender. You can be yourself. If the supplier information is not included in the trace information, it cannot be registered as the trace information, so the data rejection process in step 211 is performed.

  (Step 204) The trace information management server 111 searches the mapping information management database 113 using the supplier information acquired in step 203.

  (Step 205) The trace information management server 111 analyzes the search result in step 204, and determines whether or not the trace information is specified for mapping. If mapping information is not specified, the determination in step 208 is executed without processing the trace information.

  (Step 206) If the mapping information is specified in Step 205, the mapping information is acquired from the mapping information management database.

  (Step 207) The trace information management server 111 uses the mapping information acquired in step 206 to convert the trace information into unified trace information.

  (Step 208) The trace information management server 111 verifies whether the trace information or the unified trace information calculated in Steps 205 and 207 conforms to the format of the unified trace information. If it does not conform to the format of the unified trace information, it cannot be registered as trace information, so the data non-acceptance process in step 211 is performed.

  (Step 209) In step 208, when the trace information and the unified trace information conform to the format of the unified trace information, the trace information management server 111 stores the unified trace information in the unified trace information management database 112. Store. By giving a serial number to the data to be stored, even trace information that handles the same ID can be registered as different trace information.

  (Step 211) The trace information determined not to be registered in the unified trace information management database in Step 203 and Step 208 cannot be received in the current process and is appropriately processed.

  (Step 212) The registration requester is notified of the results of the normal processing at Step 209 and the rejection processing at Step 211.

  Through the above common steps, the trace information management system 110 can register the trace information requested by the trace information registration system 130 in the unified trace information management system 112.

  The unified trace information data items registered here will be described with reference to FIG.

  FIG. 3 shows information constructed in the unified trace information database 112.

  The unified trace information is composed of items 301 (ID, USER, TIME, PLACE, CODE, ROLE, and NEXT) stored in the database 112, ID 3011 is an identifier for identifying an article to be tracked, and USER 3012 is a trace information management system. A member identifier that is unique as a whole, TIME 3013 is time information described in rules determined by the trace information management system, such as the time when this record is registered in the trace information management server or the time when the trace information is created, and PLACE 3014 Is the location information described in the rules determined by the trace information management system, such as the identifier of the company that registered the record or the data indicating the location where the ID 3011 actually exists in the record, and CODE 3015 indicates the detailed information of the article. A code indicating a product information number in accordance with a code system of a JAN code, ROLE 3016 is a status information when the record is registered, for example, a column describing business information of the record such as shipping, receiving, inspection, inventory, NEXT 3017 Is a code indicating the destination of the ID 3011, and the relationship between the record and the next unified trace information, such as the member identifier of the business partner who sent the ID 3011, the storage location of the item indicated by the ID 3011, and information on the stop of use of the ID 3011 Indicates information.

  Here, the use cancellation code used for the NEXT 3017 is a code when the reuse of the ID 3011 is assumed. When the use is canceled, by registering the unified trace information in which the use stop code is set in NEXT 3017, it is determined that the unified trace information in which the ID 3011 appearing after the record appears is the reused ID 3011. it can.

  Next, a processing flow for searching for unified trace information stored in the unified trace information management database 112 will be described with reference to FIG.

  (Step 901) The trace information management server 111 receives the trace information search request transmitted from the trace information search terminal 133. At this time, the received data includes information for confirming the user on this system and a search condition.

  (Step 902) The trace information management server 111 analyzes the trace information search request. At this time, information and search conditions that can identify the user are extracted from the search request.

  (Step 903) The trace information management server 111 verifies from the user information obtained in step 902 and the search condition whether the user has authority for the search. If the user does not have the authority to search, the data rejection process in step 911 is performed without permitting the search.

  (Step 904) The trace information management server 111 searches the unified trace information stored in the unified trace information management database 112 based on the search condition extracted in step 902. When a plurality of unified trace information is applicable, a plurality of records may be returned as a search result.

  (Step 905) Using the user information obtained in Step 902, the conversion information of the unified trace information is acquired from the mapping information management database 113.

  (Step 906) Using the conversion information obtained in Step 905, the unified trace information obtained by searching in Step 904 is converted into a format suitable for the user information. The suitable format is the unified trace information given to the unified dictionary with industry dictionary, standard code, and missing attribute information used by the user, and the format is converted according to the browsing on the trace information search terminal 133. .

  (Step 911) The trace information management server 111 uses the unified trace information converted into a suitable format obtained in step 906 and the result of the data rejection process obtained in step 911 as the trace information search terminal. To 133.

  In the following, a description will be given of a procedure for registering trace information, a procedure for searching, and data to be converted in tracking distribution information in the food and pharmaceutical fields.

  Hereinafter, as a first embodiment, a trace information management system for accumulating trace information for tracking food distribution information will be described.

  In the field of food distribution, it is assumed that the trace information registration system 130a is a food manufacturer, the trace information registration system 130b is a food processing manufacturer, and the trace information search terminal 133 is a consumer who consumes processed food.

  Regarding the basic data processing flow, the above-described processing flow is used.

  FIG. 4 shows data items of trace information registered using the trace information registration system 130b of the food processing manufacturer in this embodiment.

  The trace information 400 is transmitted to the trace information management system 110 in a data format set by the trace information registration system 131a, for example, CSV (Comma Separated Value) format or XML (Extensible Markup Language) format. The trace information 400 indicates the ID 401 associated with the food registered in the unified trace information management database 112, the user ID 402 indicating the food processing manufacturer, the transmission time 403 of the trace information 400, and the location of the ID 401 within the food processing manufacturer. Location code 404, for example, using a standard company code by DUNS (the Data Universal Numbering System), product code 405 indicating the product type of food indicated by ID 401, such as JAN code, common work used by food processing manufacturers in-house Information such as a code 406 and a destination code 407 designated as a destination for shipping the product and a destination between warehouses is included. The trace information 400 can be acquired by the business system 131b of the food processing manufacturer, and is generated by the trace information registration system 131a.

  FIG. 7 is a screen image for registering the trace information 400 in the trace information management system 110. The trace information registration screen 700 is roughly divided into a function for selecting the trace information registration 701 or the trace information search 702, a registration information selection function 703, an information confirmation button 708, an information transmission button 709, and a cancel button 710. Further, the registration information selection function 703 includes a supplier selection function 706 and its supplier list 707, an input box 704 for selecting a transaction information file, a file selection button 705, and the like.

  The user of the trace information registration terminal 132b uses the supplier selection function 706 to select a food company as a supplier, A food in this figure, and selects the trace information 400 to be registered using the file selection button 705. To do. At this time, the trace information 400 may be prepared as a file in advance, or may be output by the business system 131a when selecting the trace information 400 to be registered.

  The trace information management system 110 registers the trace information 400 in the unified trace information management database 112 by the procedure shown in FIG. The processing of step 203 to step 207 in the present embodiment will be described with reference to FIGS.

  FIG. 5 is information used when selecting a mapping table for converting the trace information 400 stored in the mapping information management table 113. In this embodiment, at the time of registering trace information, the supplier information determined using the supplier selection function 706 is used as a determination criterion for mapping table selection. That is, once the business partner is determined, the format of the trace information 400 is uniquely determined.

  (Step 203) The trace information management server 111 confirms the business partner selected by the business partner selection function 706 received together with the trace information 400.

  (Steps 204 and 205) The trace information management server 111 searches for applicable mapping tables using the business partners confirmed in Step 203. In this embodiment, since the A food is selected, it is confirmed that the A food is used as the determination criterion 501 and the mapping table 1 is designated as the mapping table 502 to be used. FIG. 6 shows one embodiment of the mapping table 1 and provides information necessary for converting items between the unified trace information and the trace information 400.

  (Step 206) The trace information management server 111 acquires the mapping table 1 shown in FIG. 6 from the mapping information management database 113.

  (Steps 207 and 208) The trace information management server 111 converts the received trace information 400 into a unified trace information format by using the item mapping 601 to 607. Further, it is confirmed that the definition of the unified trace information and the data format of the converted trace information 400 are consistent. After confirming the conversion to the unified trace information, it is stored in the unified trace information management database 112 according to the procedure of FIG.

  By the above procedure, the trace information registration system 130b of the food processing manufacturer can register the trace information 400 in the unified trace information management database 112.

  Next, a method for searching for trace information registered in the unified trace information registration system 110 using the trace information search terminal 133 will be described.

  FIG. 8 is a screen image for requesting the trace information management system 110 to search for trace information. The trace information search screen 800 is roughly divided into a function for selecting a trace information registration 801 and a trace information search 802, a search condition specifying function 803, a search condition transmission button 806, and a cancel button 807. Further, the search condition specifying function 803 includes a search condition list 804 and an input box 805 for specifying condition details.

  The user of the trace information search terminal 133 selects a search condition from the search condition list 804 and inputs the details of the condition in the input box 805. For example, the ID 401 attached to the food purchased by the user in the form of numbers, barcodes, and IC tags is visually recognized or read and input.

  The trace information management system 110 searches the unified trace information database 112 by the procedure of FIG. As in the present embodiment, a plurality of unified trace information is searched by searching with the ID 401, and the information is displayed as a list in a table format, an Excel format, a list format, or the like.

  The above is an embodiment relating to the accumulation and use of trace information for tracking food distribution information.

  In the following, as a second embodiment, a system for accumulating trace information in order to track distribution information of pharmaceuticals will be described.

  In the pharmaceutical distribution field, it is assumed that the trace information registration system 130a is a drug manufacturer, the trace information registration system 130b is a pharmaceutical wholesaler, and the trace information search terminal 133 is a hospital or a person in charge of each business.

  Regarding the basic data processing flow, the above-described processing flow is used.

  FIG. 10 shows a data format of trace information registered using the trace information registration system 130a of the drug manufacturer in this embodiment.

  In the present embodiment, it is assumed that the format of the trace information 400 to be transmitted conforms to a data format used in the pharmaceutical industry. The data fields 1011 to 1017 respectively include the transmission time of the trace information 400, the sender of the trace information 400, the business status in EDI, the receiver of the trace information 400, the product code of the medicine to be sent, and the ID associated with the medicine to be sent. Indicates a location code indicating the location of the medicine to be sent.

  The trace information management system 110 registers the trace information 400 in the unified trace information management database 112 by the procedure shown in FIG. The processing from step 203 to step 207 in the present embodiment will be described with reference to FIGS.

  FIG. 11 is information used when selecting a mapping table for converting the trace information 400 stored in the mapping information management table 113. In this embodiment, a case where the data conforms to the VAN data format used in the pharmaceutical industry will be described.

  (Step 203) The trace information management server 111 confirms that the format uses the VAN data format from the total data length of the trace information 400 and the like.

  (Steps 204 and 205) The trace information management server 111 searches for applicable mapping tables using the information in the VAN format confirmed in Step 203. In this embodiment, since the trace information 400 is received in the VAN format, it is confirmed that the mapping table a is designated as the mapping table 1102 to be used by using the pharmaceutical industry VAN as the determination criterion 1101. FIG. 12 shows one embodiment of the mapping table a, which provides information necessary for converting items between the unified trace information and the trace information 400.

  (Step 206) The trace information management server 111 acquires the mapping table a shown in FIG. 12 from the mapping information management database 113.

  (Steps 207 and 208) The trace information management server 111 uses the item mapping information 1200 to convert the received trace information 400 into a unified trace information format. Further, it is confirmed that the definition of the unified trace information and the data format of the converted trace information 400 are consistent. After confirming the conversion to the unified trace information, it is stored in the unified trace information management database 112 according to the procedure of FIG.

  By the above procedure, the trace information registration system 130a of the drug manufacturer can register the trace information 400 in the unified trace information management database 112.

  In the second embodiment, as a criterion for selecting the mapping table, it is determined whether or not the data is in the VAN format. However, the industry standard EDI data format may be used, and the drug manufacturer agrees. Other data formats may be used.

  INDUSTRIAL APPLICABILITY The present invention can appropriately grasp the distribution status of articles using a computer, and can be used for managing articles in the distribution industry.

It is a figure which shows an example of the whole structure of the trace information management system in this Embodiment. It is a figure which shows the processing flow converted into unified trace information. It is a figure which shows an example of the data item of unified trace information. It is a figure which shows an example of the data item of the trace information which a food processing maker registers in a 1st Example. It is a figure which shows an example of the list | wrist for selecting the mapping table converted into unified trace information in a 1st Example. It is a figure which shows an example of the mapping table in a 1st Example. It is a figure which shows an example of the screen which registers trace information in a 1st Example. It is a figure which shows an example of the screen which searches trace information in 1st Example. It is a figure which shows the processing flow which searches unified trace information. It is a figure which shows an example of the data item of the trace information which a chemical | medical agent manufacturer registers in a 2nd Example. It is a figure which shows an example of the list | wrist for selecting the mapping table converted into unified trace information in a 2nd Example. It is a figure which shows an example of the mapping table in a 2nd Example.

Explanation of symbols

DESCRIPTION OF SYMBOLS 110 ... Trace information management system, 111 ... Trace information management server, 112 ... Unified trace information management database, 113 ... Mapping information management database, 130 ... Trace information registration system, 131 ... Existing business system, 132 ... Trace information registration terminal, 133 ... Trace information search terminal

Claims (8)

The trace information of two or more data formats received via the network is connected to a plurality of information transmission devices that transmit the trace information indicating the distribution or manufacturing process of the articles via the network. In the trace information conversion system that converts to unified trace information,
Each of the information transmitting devices is installed at each base of the distribution or manufacturing process of the article,
Storage means for storing in advance a conversion method that is determined according to the information transmission device and converts the trace data transmitted from the client device into the unified trace data;
Receiving means for connecting to the network and receiving trace information of the two or more data formats;
Determining means for determining whether the trace information received by the receiving means includes supplier information indicating a supplier to whom the article is next delivered from a base of the information transmitting device;
If it is determined that includes the client information by the determination unit, from the trace information received by the receiving means, an extraction means for extracting the client information,
Search means for searching the storage means for a conversion method corresponding to the supplier information extracted by the extraction means;
According to the conversion method searched by the search means, conversion means for converting the trace information received by the receiving means into the unified trace information;
A trace information conversion system comprising: registration means for registering the unified trace information converted by the conversion means. The trace information conversion system according to claim 1,
If the determination means determines that the supplier information is not included as a result of the determination, the determination means executes a non-acceptance process for the trace information. The trace information conversion system according to claim 1,
Furthermore, the trace information conversion system characterized by having a consistency confirmation means which confirms whether the converted said unified trace information matches with a predetermined format . In the trace information conversion system according to claim 3,
The trace information conversion system according to claim 1, wherein when it is determined that the consistency does not match, the consistency confirmation unit executes a non-acceptance process on the changed unified trace data . The trace information of two or more data formats received via the network is connected to a plurality of information transmission devices that transmit the trace information indicating the distribution or manufacturing process of the articles via the network. In a trace information conversion method using a trace information conversion system for converting to unified trace information,
Each of the information transmitting devices is installed at each base of the distribution or manufacturing process of the article,
A conversion method that is determined according to the information transmission device and converts the trace data transmitted from the client device into the unified trace data is stored in a storage device in advance.
Using the receiving device connected to the network, receiving the trace information of the two or more data formats,
Determine then the article from the station of the information transmission apparatus to the received trace information contains client information indicating a partner passed by the receiving unit,
When it is determined that the supplier information is included in the determination , the supplier information is extracted from the trace information received by the receiving device,
Search the storage device for a conversion method corresponding to the extracted supplier information,
According to the converted conversion method, the trace information received by the receiving device is converted into the unified trace information,
A trace information conversion method comprising: registering the converted unified trace information in a registration device. In the trace information conversion method according to claim 5,
As a result of the determination, if it is determined that the supplier information is not included, a non-acceptance process for the trace information is executed . In the trace information conversion method according to claim 5,
Furthermore, it is confirmed whether the converted said unified trace information matches with a predetermined format, The trace information conversion method characterized by the above-mentioned . In the trace information conversion method according to claim 7,
A trace information conversion method characterized in that, in the confirmation of consistency, if it is determined that there is no consistency, a non-acceptance process is performed on the changed unified trace data .

Images