JP5047760B2 - History management server and history management system - Google Patents

Description

  The present invention relates to a technique for managing a history indicating the production and distribution processes of individual articles.

  2. Description of the Related Art There is known a technique for accumulating history information indicating an article manufacturing process and distribution process in a database and tracking the accumulated history information for each article along the manufacturing process and distribution process. For example, it is possible to guarantee the quality and safety of an article by providing the consumer with the production history and distribution history of the article. Further, when the final article is out of the standard, history information can be used as one of means for investigating the cause.

  As a management method of such history information, for example, in Patent Document 1, information indicating what work is performed in which process for which article is set as history information for each process, and a history ID is assigned to each history information. The correspondence between the allocation, history ID, and history information is recorded in the history table (see FIG. 7 of Patent Document 1), and information indicating the order of the history information is stored in the history relationship table (see FIG. 8 of Patent Document 1). ) Is recorded. By referring to the history table and the history relationship table, history information for each article can be tracked.

JP 2007-11851 A

By the way, in the technique disclosed in Patent Document 1, tracking of history information is performed in the following procedure.
(1) A record of history information for starting tracking is acquired from the history table, and a history ID is acquired from the record.
(2) Next, the history relation table is searched using the acquired history ID as a key, and the history ID corresponding to the history information before or after the history ID is searched.
(3) Next, the history table is searched using the history ID obtained in (2) as a key, and history information of the previous or next step is acquired.
(4) Check the contents of the history information acquired in (3).
(5) The above (2) to (4) are repeated until the history information to be acquired is found.

  An enormous number of history information is registered in the history table, and information indicating the order of all history information registered in the history table is registered in the history relationship table. Therefore, it takes time to search for a desired record in each table. In the history tracking process in Patent Document 1, the processes shown in the above (2) to (4) are repeated until the actual history information to be acquired is found. The process of searching for a desired record from the table needs to be executed many times, and the time required for the history tracking process to end is further increased.

  Although it is possible to speed up the search by associating each record in the history table and each record in the history relationship table with an index, even if the search speed of each table is slightly improved, the history table Since it is necessary to repeatedly execute the process of searching for a desired record from the process and the process of searching for a desired record from the history relation table, it takes time to finish the history tracking process.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to shorten the time required for tracking history information.

  In order to solve the above-mentioned problem, in the present invention, in association with the event ID of the event applied to the article, information indicating the contents of the event and the order of the event is stored in the group file, and for each event ID, The contents of the corresponding event and the group ID of the group file in which the event ID is stored are stored as history information, and when information specifying the event that is the starting point is received, the event ID of the event that is the starting point is supported The group ID to be extracted is extracted from the history information, and the contents of the group file corresponding to the extracted group ID are output.

  For example, the first aspect of the present invention is a history management server that manages the history of individual articles, and associates an event ID that identifies each of a series of events applied to the article with the contents of the event. A group file storing means for storing information indicating at least a part of the information and a group file storing the order information indicating the order of the event in association with a group ID for identifying the group of the series of events, and an event ID History information storing the article ID of the article on which the event identified by the event ID has been performed, the content of the event identified by the event ID, and the group ID of the group file in which the event ID is stored Storage means, input means for receiving information indicating the contents of the event as the starting point, and history information storage means Group ID extraction means for sequentially reading stored information, specifying an event ID corresponding to the content of the event as a starting point, and extracting a group ID associated with the specified event ID; and group file storage means The information stored in is sequentially read out, the group file corresponding to the group ID extracted by the group ID extracting means is extracted, and the information stored in the extracted group file is processed into a predetermined format and output There is provided a history management server comprising a group information output means.

  The second aspect of the present invention is a history management system for managing the history of individual articles, comprising a terminal provided at each site and a history management server, wherein the terminal is attached to the article. ID acquisition means for acquiring the article ID and the event ID from the tag that holds the article ID for identifying the article and the event ID for identifying the event applied to the article, and the article ID read by the ID acquisition means, and When the event ID is received from the history management server and the ID transmission means for transmitting the event ID to the history management server together with the information indicating the content of the event applied to the article ID, ID rewriting means for rewriting the event ID in the tag, and the history management server corresponds to the event ID in association with the event ID. A group file that stores information indicating at least a part of the contents of an event and a group file that stores order information indicating the order of the event in association with a group ID that identifies a group of a series of events applied to the article. For each event ID, the storage means, the article ID of the article for which the event identified by the event ID has been performed, the content of the event identified by the event ID, and the group of the group file in which the event ID is stored A history information storage means for storing an ID, an input means for receiving information indicating the contents of the event as the starting point, and an event corresponding to the contents of the event as the starting point by sequentially reading the information stored in the history information storing means ID is specified, and the group ID associated with the specified event ID is The group ID extraction means to be issued and the information stored in the group file storage means are sequentially read out, the group file corresponding to the group ID extracted by the group ID extraction means is extracted, and stored in the extracted group file. Information that is processed into a predetermined format and output from the group information output means and information indicating the item ID, event ID, and event content from the terminal, the event indicated by the event content Event ID assigning means for newly assigning an event ID to the terminal, and event received from an external terminal when the event ID assigning means is newly assigned by the event ID assigning means. Group stored in the history information storage means in association with the ID The ID is specified, and the article ID received from the external terminal, the content of the event received from the external terminal, and the specified group ID are associated with the event ID newly assigned by the event ID assigning means. When an event ID is newly assigned by the history information registering means registered in the storage means and the event ID assigning means, the event ID received from the terminal corresponds to the event ID newly assigned by the event ID assigning means. Create the order information as the event ID of the event executed before the event, refer to the history information storage means, extract the group ID associated with the event ID received from the terminal, and to the extracted group ID Newly assigned to the corresponding group file by event ID assigning means The group file is updated by the event information registering means for storing information indicating at least part of the contents of the event received from the terminal and the created order information, and the event information registering means in association with the event ID. If the event ID newly assigned by the event ID assigning unit is the event ID of the event executed next to the event corresponding to the event ID received from the external terminal, the event received from the external terminal The event order information corresponding to the event ID corresponding to the event ID received from the external terminal stored in the group file updated by the event information registration means is created by creating the order information of the event corresponding to the ID. Having an order information updating means for updating To provide a management system.

  According to the present invention, the time required for tracking history information can be shortened.

  First, a first embodiment of the present invention will be described.

  FIG. 1 is a system configuration diagram showing a configuration of a history management system 10 in the first embodiment. The history management system 10 includes a history management server 20 and a terminal 30 provided for each base 12. The history management server 20 and each terminal 30 are connected to the communication line 11 and transmit / receive communication data via the communication line 11.

  The article 15 is, for example, an agricultural product, a processed product, or a manufactured product. A tag 16 in which an article ID for identifying the article 15 is recorded is attached to the article 15. In the present embodiment, the tag 16 is an RFID (Radio Frequency IDentification). As another form, the tag 16 may be a recording medium on which a barcode is printed, a recording medium on which information is recorded by magnetism, a recording medium on which characters, symbols, or the like are printed.

  In each base 12, a gate 13 to which a sensor 14 is attached is provided at a place where an event (for example, production, arrival, shipment, etc.) is performed on the article 15. In the present embodiment, the sensor 14 is a tag reader. As another form, the sensor 14 is a barcode reader, a device that reads information recorded by magnetism, or an imaging device that reads characters, symbols, etc. from a recording medium on which characters, symbols, etc. are printed. Also good.

  The terminal 30 of each base 12 acquires the article ID recorded on the tag 16 attached to the article 15 via the sensor 14, and the acquired article ID and the gate 13 to which the sensor 14 is attached. Create event information that includes the details of the event. Then, the terminal 30 transmits the created event information to the history management server 20 via the communication line 11.

  The history management server 20 accumulates event information transmitted from the terminal 30 at each site 12 as history information. Then, the history management server 20 supports the tracking of the history information of the article 15 by the user by displaying the history information for each article 15 in accordance with an instruction from the user.

  FIG. 2 is a block diagram illustrating an example of a detailed functional configuration of the terminal 30 according to the first embodiment. The terminal 30 includes an ID transmission unit 31 and an ID acquisition unit 32.

  The ID acquisition unit 32 holds, for each gate 13, information indicating the content of an event (action, location, person in charge, etc.) given to the article 15 at the place where the gate 13 is provided. When the article ID is received, the content of the event performed at the gate 13 to which the sensor 14 is attached includes the date and time when the article ID is received, and the ID is transmitted to the ID transmitter 31 together with the article ID. The ID transmission unit 31 creates event information including the item ID and event content received from the ID acquisition unit 32, and transmits the created event information to the history management server 20 via the communication line 11.

  FIG. 3 is a block diagram illustrating an example of a detailed functional configuration of the history management server 20 in the first embodiment. The history management server 20 includes an input unit 200, a group ID extraction unit 201, a history information storage unit 202, a history information registration unit 203, a group information output unit 204, a group file storage unit 205, a detailed information output unit 206, and an event information registration unit. 207, an order information update unit 208, a deletion unit 209, and a temporary storage unit 210.

  The history information storage unit 202 stores a plurality of records 2028 as shown in FIG. 4, for example. Each record 2028 includes a field 2020 for storing an event ID for identifying an event, a field 2021 for storing an article ID, a field 2022 for storing the contents of the event, and a field 2023 for storing a group ID. The group ID is information for identifying a group file that stores a series of history information such as production, manufacture, and distribution for each article.

  The field 2022 for storing the contents of the event further includes a field 2024 for storing information indicating an action performed on the article, a field 2025 for storing information indicating a place where the action has been performed, and the action being performed. A field 2026 for storing information indicating the date and time, a field 2027 for storing information for identifying a person in charge who has performed the action, and the like are included. By referring to the history information storage unit 202, the group ID of the group file that stores the contents of the event applied to the article and a series of history information of the article for each article is specified. Can do.

  The group file storage unit 205 stores a plurality of group files 2050, for example, as shown in FIG. Each group file 2050 stores a field 2051 for storing a group ID and a plurality of records 2059. In each record 2059, a field 2052 for storing an event ID, a field 2053 for storing an event ID of an event executed before the event corresponding to the event ID stored in the field 2052, and a field 2052 are stored. A field 2054 that stores an event ID of an event that is executed after an event corresponding to the event ID that is stored, and a field 2055 that stores information indicating at least a part of the event corresponding to the event ID stored in the field 2052 are stored. Is done. The event IDs stored in the field 2053 and the field 2054 constitute event order information corresponding to the event ID stored in the field 2052, respectively.

  In the present embodiment, the field 2055 stores a field 2056 for storing information indicating an action performed on the article, a field 2057 for storing information indicating a place where the action is performed, and a date and time when the action is performed. A field 2058 for storing information to be shown is included. As another form, the field 2055 may include information corresponding to all items stored in the field 2022 of the history information storage unit 202. By referring to the group file storage unit 205, for each article, the event IDs of a plurality of events applied to the article, the order in which the plurality of events are applied, and the outline of each event can be acquired. .

  As another form, the field 2053 includes a physical file in the group file storage unit 205 in which an event ID of an event executed before the event corresponding to the event ID stored in the field 2052 is stored. Address information may be stored. Similarly, the field 2054 stores the physical address information in the group file storage unit 205 in which the event ID of the event executed after the event corresponding to the event ID stored in the field 2052 is stored. May be. Thus, even when a large number of fields 2058 exist in the group file 2050, it is possible to quickly trace an event executed before or an event executed later.

  The temporary storage unit 210 stores a plurality of records 2108, for example, as shown in FIG. Each record 2108 stores a field 2100 for storing an event ID, a field 2101 for storing an article ID, a field 2102 for storing event contents, and a field 2103 for storing a group ID. In the field 2102 for storing the contents of the event, a field 2104 for storing information indicating an action performed on the article, a field 2105 for storing information indicating a place where the action is performed, and the action are performed. A field 2106 for storing information indicating the date and time, a field 2107 for storing information for identifying a person in charge who has performed the action on the article, and the like are stored.

  The data structure in the temporary storage unit 210 is the same as the data structure in the history information storage unit 202, but only the record 2108 for storing the latest event information is stored in the temporary storage unit 210 for each article. The point is different from the history information storage unit 202. Further, the record 2108 including information on the event executed last in the predetermined business flow is deleted from the temporary storage unit 210.

  For example, as illustrated in FIG. 7, the input unit 200 displays an input screen 40 for inputting a condition for specifying a record 2028 stored in the history information storage unit 202 on the display device 18. When the content of the corresponding item is input to each input box 400 by the user and the search button 401 is selected, the input unit 200 transmits the content input for each item to the group ID extraction unit 201. .

  Also, the input unit 200 displays the selected event ID in the detailed information output unit 206 when an event ID is selected in a state where the group information screen 41 as shown in FIG. Send to. When the end button 415 is selected in a state where the group information screen 41 as shown in FIG. 8 is displayed on the display device 18, the input unit 200 displays the input screen 40 shown in FIG. To display. The input unit 200 outputs the group information screen 41 when the return button 421 is selected in a state where the detailed information screen 42 as shown in FIG. 9 is displayed on the display device 18, for example. The unit 204 is instructed.

  The group ID extraction unit 201 refers to the history information storage unit 202 based on the information received from the input unit 200, identifies a record including information specified by the user as a starting record, and sets the identified record as The included group ID and article ID are transmitted to the group information output unit 204. In the example shown in FIG. 7, when an event ID is specified, the group ID extraction unit 201 searches the history information storage unit 202 using the event ID as a key, and sets a record 2028 including the event ID as 1 Identify one. When an item other than the event ID is designated, the group ID extraction unit 201 identifies records corresponding to all input information. When a plurality of records are specified, the group ID extraction unit 201 transmits the group ID and the article ID included in each record to the group information output unit 204.

  The group information output unit 204 searches the group file storage unit 205 using the group ID received from the group ID extraction unit 201 as a key, acquires a group file corresponding to the group ID, and stores the article ID together with the article ID of the history management server 20. Expand on RAM. Then, the group information output unit 204 refers to the expanded group file and sorts a plurality of records included in the group file in the order in which the events are executed, for example, a group information screen as shown in FIG. 41 is displayed on the display device 18.

  As shown in FIG. 8, the group information screen 41 displays a plurality of records 414 together with a field 410 for displaying an article ID and a field 411 for displaying a group ID. Each record 414 includes a field 413 that displays at least a part of the content of the event corresponding to the event ID displayed in the field 412. On the group information screen 41, the respective records 414 are displayed in order from the top in the order in which the events are executed.

  By referring to the group information screen 41, the user can trace the history information of the article corresponding to the specified information. For example, when tracking the history of non-standard products, if the final event of the article displayed on the group information screen 41 is the arrival at the wholesale store A, the user is still at the wholesale store A. It can be seen that the article can be collected from the wholesale store A. Further, by referring to the production place and processing place of the article displayed on the group information screen 41, the user can know which farmer has produced the article and at which factory.

  The group information output unit 204 keeps the group file acquired from the group file storage unit 205 and expanded on the RAM on the RAM, and next time, the same group ID and article ID are received from the group ID extraction unit 201. When received, necessary information is extracted from the group file on the RAM. It is preferable that the group file on the RAM is controlled so that the higher the access frequency is, the higher the priority is left, by the LRU (Least Recently Used) method or the like. Thereby, the group information output unit 204 can acquire the contents of the group file more quickly. Further, if more group files are expanded and left on the RAM, the search speed of the group file can be expected to improve. Therefore, the data amount of each group file is preferably small. Therefore, it is preferable to store a part of the contents of the event in the history information storage unit 202 (in this embodiment, “action”, “location”, and “date / time”) in the group file 2050.

  When receiving the event ID from the input unit 200, the detailed information output unit 206 searches the history information storage unit 202 using the event ID as a key, and specifies a record including the event ID. Then, for example, as illustrated in FIG. 9, the detailed information output unit 206 displays a detailed information screen 42 indicating information included in the specified record on the display device 18. On the detailed information screen 42, a field 420 for displaying information of each item and a return button 421 are displayed.

  Here, there are various kinds of articles, and the article ID for identifying each article is different in each kind. For example, the number of types of crops produced by a plurality of farmers is several hundreds or more including varieties and the like, and when each crop is identified as an individual item, the number of items is several million or more. In addition, an event given to each article may be several tens or more times such as production, washing, processing, bagging, packing, shipping, and the like. Furthermore, since the history information collected and stored in the history information storage unit 202 may be stored for a long time, the number of records in the history information storage unit 202 may reach several hundred million records.

  Further, if a history relationship table that stores information indicating the history relationship between history information as described in Patent Document 1 is used, the number of records in the history relationship table is also the same as the history information storage unit 202. May reach 100 million records. Also, depending on the article, there are cases where events of several tens of times or more are performed. Therefore, in the technique of Patent Document 1, when tracing the history information of a certain article, the search in the history information storage unit 202 and the history Each search in the relation table is repeated several tens of times.

  On the other hand, in this embodiment, after the group ID extraction unit 201 searches the history information storage unit 202 for a record corresponding to the information received from the input unit 200, the group information output unit 204 is included in the record. The group file corresponding to the group ID being searched is searched, and the information of the searched group file is displayed so that the order of events can be understood. The group file stores at least a part of the contents of the event. If the information necessary for tracing the history information can be acquired from the contents of the group file displayed by the group information output unit 204, the user can History information can be traced at that stage. Therefore, the search in the history information storage unit 202 and the search in the group file storage unit 205 need only be performed once, and information necessary for tracing the history information can be displayed more quickly than the method described in Patent Document 1. can do.

  In addition, when the contents of the group file displayed by the group information output unit 204 are insufficient to trace the history information, the detailed information output unit 206 displays several hundred million records each time an individual event ID is selected. The history information storage unit 202 consisting of is searched. However, even in this case, in the present embodiment, the group information screen 41 displayed by the group information output unit 204 follows the order in which the events are executed with respect to a group of events applied to the article. Since the event IDs are displayed in the arrangement, it is not necessary to search the history relation table consisting of several hundreds of millions of records more than tens of times in order to specify the order in which the events are executed. Therefore, even if the content of the group file displayed by the group information output unit 204 is insufficient as information necessary to trace the history information, the history information is more than the method described in Patent Document 1. Information necessary for tracing can be quickly displayed.

  In FIG. 5, each field 2058 in the group file 2050 contains the physical address information in the history information storage unit 202 in which the same event ID as the event ID stored in the field 2052 is stored. It may be stored. In this case, the input unit 200 displays the selected event ID and the event ID when the group ID screen 41 shown in FIG. 8 is displayed on the display device 18 and an event ID is selected. The group ID is transmitted to the detailed information output unit 206. As a result, the detailed information output unit 206 identifies the group file corresponding to the group ID received from the input unit 200 in the group file storage unit 205, and the event ID received from the input unit 200 from the identified group file. Address information can be acquired, and a target record in the history information storage unit 202 can be acquired more quickly based on the acquired address information.

  Returning to FIG. 3, the description will be continued. When the history information registration unit 203 receives event information including information indicating the article ID and the content of the event from the terminal 30 via the communication line 11, the history information registration unit 203 assigns an event ID to the event indicated by the content of the event. Assign a new one. Then, the history information registration unit 203 refers to the temporary storage unit 210 and acquires a group ID associated with the same product ID as the product ID included in the event information received from the terminal 30.

  Then, the history information registration unit 203 associates the item ID received from the terminal 30, the content of the event received from the terminal 30, and the group ID acquired from the temporary storage unit 210 with the newly assigned event ID. Registration is performed in the history information storage unit 202 and the temporary storage unit 210. When the group ID associated with the same article ID as the article ID received from the terminal 30 does not exist in the temporary storage unit 210, the history information registration unit 203 assigns a new group ID and newly assigns it. The article ID, event ID, and event content are registered in the history information storage unit 202 and the temporary storage unit 210 in association with the group ID.

  When a new record is registered in the temporary storage unit 210, the event information registration unit 207 selects another event ID associated with the same product ID as the product ID included in the newly registered record. It is specified in the temporary storage unit 210. Then, the event information registration unit 207 creates the order information as the event ID of the event that is executed before the event corresponding to the event ID newly registered in the temporary storage unit 210 with the other identified event ID. Then, the event information registration unit 207 refers to the group file storage unit 205 and identifies a group file corresponding to the group ID included in the record newly registered in the temporary storage unit 210.

  The event information registration unit 207 is included in the newly registered record in the temporary storage unit 210 in association with the event ID included in the record newly registered in the temporary storage unit 210 in the identified group file. Information indicating at least part of the contents of the event and the created order information are stored. When the group file corresponding to the group ID included in the record newly registered in the temporary storage unit 210 does not exist in the group file storage unit 205, the event information registration unit 207 creates a new group file, Information indicating at least a part of the contents of the event is stored in the created group file in association with the event ID.

  The order information update unit 208 is associated with the same product ID as the product ID included in the record newly registered in the temporary storage unit 210 when the group file is updated by the event information registration unit 207. Are specified in the temporary storage unit 210. Then, the order information update unit 208 uses the event ID included in the record newly registered in the temporary storage unit 210 as the event ID of the event executed next to the event corresponding to the other specified event ID. Event order information corresponding to other event IDs is created. Then, the order information update unit 208 updates the order information of the event corresponding to the other event ID stored in the group file updated by the event information registration unit 207 with the created order information. Is notified to the deletion unit 209.

  The deletion unit 209, when notified from the order information update unit 208 of the end of update of the order information, deletes another record including the same item ID as the item ID included in the record newly registered in the temporary storage unit 210. Identify. Then, the deletion unit 209 deletes, from the temporary storage unit 210, a record including information related to an event that is not the latest for the article corresponding to the article ID by deleting the identified record from the temporary storage unit 210. The deletion unit 209 holds information indicating an action and a location included in the last event of the business, and refers to the temporary storage unit 210 to determine a combination of the action and the location included in the last event of the business. The record to be included is deleted from the temporary storage unit 210.

  As described above, the deletion unit 209 deletes, from the temporary storage unit 210, a record including information related to an event that is not the latest and a record including information related to the last event of the job from the temporary storage unit 210 for each item ID. The information registered in can be reduced. Accordingly, when the history information registration unit 203 receives event information from the terminal 30, the temporary storage unit 210 searches for a group ID associated with the same item ID as the item ID included in the event information. In this case, the number of data in the temporary storage unit 210 can be reduced, and the history information registration unit 203 can search for the group ID more quickly.

  Here, the history information registration processing executed by the history information registration unit 203, the event information registration unit 207, the order information update unit 208, and the deletion unit 209 will be described with reference to FIGS. For example, in the state where the data shown in FIGS. 10A to 10C are stored in the history information storage unit 202, the temporary storage unit 210, and the group file 2050, respectively, the event shown in FIG. When the information 43 is received, the history information registration unit 203 assigns “ID-3” as a new event ID to the event indicated by the event information 43.

  Next, the history information registration unit 203 refers to the temporary storage unit 210 and acquires “GR-1” as the group ID associated with the same product ID as the product ID included in the event information 43. . Then, as shown in FIGS. 11A and 11B, the history information registration unit 203 uses the article ID included in the event information 43 in association with the newly assigned event ID “ID-3”. “P001”, “arrival”, “wholesale store”, “2007-07-22 09:30”, and “C” which are the contents of the event received from the terminal 30, and the group acquired from the temporary storage unit 210 The ID “GR-1” is registered in the history information storage unit 202 and the temporary storage unit 210.

  In FIG. 11B, since the contents of the temporary storage unit 210 after the record with the event ID “ID-2” is deleted by the deletion unit 209 are shown, the event ID is “ID-2”. However, at this stage, the record with the event ID “ID-2” is stored in the temporary storage unit 210.

  Next, the event information registration unit 207 has an event ID “ID-2” as another event ID associated with the same product ID as the product ID included in the record newly registered in the temporary storage unit 210. "Is specified in the temporary storage unit 210. Then, the event information registration unit 207 sets “ID-2”, which is the other identified event ID, before the event corresponding to “ID-3”, which is the event ID newly registered in the temporary storage unit 210. Order information is created as the event ID of the event to be executed. In the order information created here, the previous event ID is “ID-2” as indicated by a field 2068 in FIG.

  Next, the event information registration unit 207 refers to the group file storage unit 205 and refers to the group file corresponding to “GR-1” that is the group ID included in the record newly registered in the temporary storage unit 210 (see FIG. 10 (c)). Then, the event information registration unit 207 newly associates the identified group file with the event ID “ID-3” included in the record newly registered in the temporary storage unit 210 in the temporary storage unit 210. Information indicating at least a part of the contents of the event included in the registered record (“action”, “location”, and “date / time” in the example of FIG. 10C) and the created order information are stored.

  Next, the order information update unit 208 sets “ID− as another event ID associated with the same product ID as“ P001 ”which is the product ID included in the record newly registered in the temporary storage unit 210. 2 ”is specified in the temporary storage unit 210. Then, the order information update unit 208 corresponds to “ID-2”, which is another identified event ID, of “ID-3” that is the event ID included in the record newly registered in the temporary storage unit 210. As the event ID of the event executed next to the event, event order information corresponding to “ID-2” which is the other event ID is created. In the order information created here, the post-event ID is “ID-3” as indicated by a field 2069 in FIG.

  Next, the order information update unit 208 updates the order information of the event corresponding to the other event ID stored in the group file updated by the event information registration unit 207 with the created order information. As a result, the group file updated by the event information registration unit 207 has contents as shown in FIG.

  Next, the deletion unit 209 includes another record (“ID-2”) that includes the same product ID as “P001” that is the product ID included in the record newly registered in the temporary storage unit 210 as an event ID. Record). Then, the deletion unit 209 deletes the specified record from the temporary storage unit 210, so that the data in the temporary storage unit 210 has the contents as shown in FIG.

  Next, the operation of the history management server 20 when searching for history information in the present embodiment will be described with reference to FIG. When the user inputs data to the input screen 40 described with reference to FIG. 7 and selects the search button 401, the history management server 20 starts the operation shown in this flowchart.

  First, the input unit 200 transmits information input via the input device 17 to the group ID extraction unit 201 for each item. The group ID extraction unit 201 uses the information received from the input unit 200 as a key to specify a starting record in the history information storage unit 202 (S100). Then, the group ID extraction unit 201 extracts the group ID and article ID included in the identified record (S101), and transmits the extracted group ID and article ID to the group information output unit 204.

  Next, the group information output unit 204 refers to the group file storage unit 205 using the group ID received from the group ID extraction unit 201 as a key, and acquires a group file corresponding to the group ID (S102). Then, the group information output unit 204 creates a group information screen 41 (see FIG. 8) in which a plurality of records included in the acquired group file are sorted in the order in which events are executed, and displays the group information screen 41 on the display device 18 ( S103).

  Next, the input unit 200 determines whether an event ID has been selected (S104). When the event ID is selected (S104: Yes), the input unit 200 transmits the selected event ID to the detailed information output unit 206. Then, using the event ID as a key, the detailed information output unit 206 searches the history information storage unit 202 to identify the record including the event ID, and the detailed information screen 42 (showing the content included in the identified record) 9) is displayed on the display device 18.

  Next, the input unit 200 determines whether or not a return button has been selected (S106). When the return button is selected (S106: Yes), the input unit 200 instructs the group information output unit 204 to display the group information screen 41, and executes the process shown in step S104 again.

  When the event ID is not selected (S104: No), the input unit 200 determines whether an end button is selected (S107). If the end button has not been selected (S107: No), the input unit 200 executes the process shown in step S104 again. When the end button is selected (S107: Yes), the history management server 20 ends the operation at the time of searching the history information shown in this flowchart.

  Next, the operation of the history management server 20 when registering history information in the present embodiment will be described with reference to FIG. When event information is received from the terminal 30 via the communication line 11, the history management server 20 starts the operation shown in this flowchart.

  First, the history information registration unit 203 assigns a new event ID to the event indicated by the received event information (S200). Then, the history information registration unit 203 refers to the temporary storage unit 210 and acquires a group ID associated with the same product ID as the product ID included in the event information received from the terminal 30 (S201).

  Next, the history information registration unit 203 associates the item ID received from the terminal 30, the content of the event received from the terminal 30, and the group ID acquired from the temporary storage unit 210 in association with the newly assigned event ID. The history information storage unit 202 and the temporary storage unit 210 are registered (S202).

  Next, the event information registration unit 207 identifies another event ID associated with the same product ID as the product ID included in the record newly registered in the temporary storage unit 210 in the temporary storage unit 210. . Then, the event information registration unit 207 creates the order information as the event ID of the event executed before the event corresponding to the event ID newly registered in the temporary storage unit 210 with the other identified event ID ( S203).

  Next, the event information registration unit 207 refers to the group file storage unit 205 and identifies a group file corresponding to the group ID included in the record newly registered in the temporary storage unit 210. The event information registration unit 207 is included in the newly registered record in the temporary storage unit 210 in association with the event ID included in the record newly registered in the temporary storage unit 210 in the identified group file. Information indicating at least a part of the contents of the event and the created order information are stored (S204).

  Next, the order information update unit 208 identifies another event ID associated with the same product ID as the product ID included in the record newly registered in the temporary storage unit 210 in the temporary storage unit 210. . Then, the order information update unit 208 uses the event ID included in the record newly registered in the temporary storage unit 210 as the event ID of the event executed next to the event corresponding to the other specified event ID. Event order information corresponding to other event IDs is created. Then, the order information update unit 208 updates the order information of the event corresponding to the other event ID stored in the group file updated by the event information registration unit 207 with the created order information (S205). The deletion unit 209 is notified of the end of update of the order information.

  Next, the deletion unit 209 specifies another record including the same product ID as the product ID included in the record newly registered in the temporary storage unit 210. Then, the deletion unit 209 deletes the specified record from the temporary storage unit 210 (S206), and the history management server 20 ends the operation at the time of registering the history information shown in this flowchart.

  The first embodiment of the present invention has been described above.

  As is clear from the above description, according to the history management system 10 of the present embodiment, the time required for tracking history information can be shortened.

  Next, a second embodiment of the present invention will be described.

  FIG. 14 is a block diagram illustrating an example of a detailed functional configuration of the terminal 30 according to the second embodiment. The terminal 30 includes an ID transmission unit 31, an ID acquisition unit 32, and an ID rewriting unit 33. In the present embodiment, a tag 16 capable of rewriting information is attached to the article 15. In the present embodiment, an RFID having a rewritable memory is assumed as the tag 16 capable of rewriting information. As another form, the rewritable tag 16 may be a rewritable paper or an IC card.

  The ID acquisition unit 32 holds, for each gate 13, the contents of an event (action, location, person in charge, etc.) given to the article 15 at the place where the gate 13 is provided. When the event ID is received, the content of the event that is performed at the gate 13 to which the sensor 14 is attached includes the date and time when the product ID is received, and is transmitted to the ID transmission unit 31 together with the product ID and the event ID. . The event information recorded in the tag 16 is an event ID for identifying the previous event written in the tag 16 in the previous event. The ID transmission unit 31 creates event information including the article ID, the event ID, and the event content received from the ID acquisition unit 32, and transmits the created event information to the history management server 20 via the communication line 11.

  In addition, when information (for example, null data) indicating that the event ID is not set is received together with the article ID from the sensor 14, that is, when information in the tag 16 is read in the first step of the history, The ID acquisition unit 32 includes information indicating that the product ID and the event ID are not set, including the date and time when the product ID is received in the content of the event performed at the gate 13 to which the sensor 14 is attached. At the same time, the data is transmitted to the ID transmitter 31. In this case, the ID transmission unit 31 creates event information including information indicating that the article ID, the content of the event, and the event ID are not set, and the created event information is transmitted to the history management server via the communication line 11. 20 is transmitted.

  When the event ID is received from the history management server 20 via the communication line 11, the ID rewriting unit 33 is recorded in the tag 16 with the event ID received from the history management server 20 via the sensor 14. Rewrite the event ID. Since the event ID assigned to the current event is transmitted from the history management server 20, the event ID corresponding to the current event is stored in the tag 16 of the article 15 that has passed through the gate 13. become.

  FIG. 15 is a block diagram illustrating an example of a detailed functional configuration of the history management server 20 according to the second embodiment. The history management server 20 includes an input unit 200, a group ID extraction unit 201, a history information storage unit 202, a history information registration unit 203, a group information output unit 204, a group file storage unit 205, a detailed information output unit 206, and an event information registration unit. 207, an order information update unit 208, and an event ID assignment unit 211. Except for the points described below, in FIG. 15, the components denoted by the same reference numerals as those in FIG. 3 have the same or similar functions as those in FIG.

  When event information including event ID, event ID, and information indicating the content of the event is received from the terminal 30 via the communication line 11, the event ID assigning unit 211 receives an event corresponding to the event information. A new event ID is assigned. Then, the event ID assigning unit 211 transmits the newly assigned event ID to the terminal 30 via the communication line 11. In addition, the event ID assigning unit 211 transmits the event information received from the terminal 30 together with the newly assigned event ID to the history information registering unit 203, the event information registering unit 207, and the order information updating unit 208.

  When the event information is received from the event ID assignment unit 211 together with the newly assigned event ID, the history information registration unit 203 stores the history information using the event ID of the previous event included in the event information as a key. By searching the part 202, the record corresponding to the previous event is specified. Then, the history information registration unit 203 acquires the group ID included in the identified record from the history information storage unit 202. Then, the history information registration unit 203 associates the event ID newly assigned by the event ID assignment unit 211 with the group ID acquired from the history information storage unit 202, with the article ID and event content included in the event information. At the same time, it is registered in the history information storage unit 202.

  When the event information registration unit 207 receives event information together with a newly allocated event ID from the event ID allocation unit 211, the event ID allocation unit 211 newly allocates an event ID included in the event information. Order information is created as an event ID of an event executed before the event corresponding to the event ID. Then, the event information registration unit 207 refers to the history information storage unit 202 and searches the history information storage unit 202 using the event ID included in the event information received from the event ID assignment unit 211 as a key, thereby The record including the ID is specified.

  Then, the event information registration unit 207 extracts the group ID included in the identified record, and identifies the group file corresponding to the extracted group ID in the group file storage unit 205. Then, the event information registration unit 207 associates the event ID newly assigned by the event ID assignment unit 211 with the event information received from the event ID assignment unit 211 in the identified group file. The information which shows at least one part and the produced order information are stored. Then, the event information registration unit 207 notifies the order information update unit 208 of the group ID of the updated group file.

  The order information update unit 208 receives the event ID newly allocated by the event ID allocation unit 211 from the event ID allocation unit 211 when the group ID of the updated group file is notified from the event information registration unit 207. The event order information corresponding to the event ID included in the event information received from the event ID assignment unit 211 is created as the event ID of the event executed next to the event corresponding to the event ID included in the event information. Then, the order information update unit 208 includes the created order information and is included in the event information received from the event ID assignment unit 211 stored in the group file corresponding to the group file notified from the event information registration unit 207. Update the order information of the event corresponding to the event ID.

  Here, the history information registration processing executed by the history information registration unit 203, the event information registration unit 207, the order information update unit 208, and the event ID assignment unit 211 will be described with reference to FIGS. For example, when the event information 44 shown in FIG. 16C is received with the data shown in FIGS. 16A and 16B stored in the history information storage unit 202 and the group file 2050, respectively. The event ID assigning unit 211 assigns “ID-3” as a new event ID to the event indicated by the event information 44.

  Then, the event ID assignment unit 211 transmits “ID-3”, which is the newly assigned event ID, to the terminal 30 via the communication line 11. Further, the event ID assigning unit 211 transmits the event information 44 together with the newly assigned event ID “ID-3” to the history information registering unit 203, the event information registering unit 207, and the order information updating unit 208. .

  Next, the history information registration unit 203 searches the history information storage unit 202 using “ID-2”, which is the event ID of the previous event, included in the event information received from the event ID assignment unit 211 as a key. The record corresponding to the previous event is specified. Then, the history information registration unit 203 acquires “GR-1”, which is a group ID included in the specified record, from the history information storage unit 202. Then, the history information registration unit 203 associates the item ID and event content included in the event information 44 with the history information in association with “ID-3” which is the event ID newly assigned by the event ID assignment unit 211. It is registered in the history information storage unit 202 together with “GR-1” which is the group ID acquired from the storage unit 202. As a result, the data in the history information storage unit 202 has the contents as shown in FIG.

  Next, the event information registration unit 207 is an event ID newly assigned by the event ID assignment unit 211 as “ID-2” that is an event ID included in the event information received from the event ID assignment unit 211. Order information is created as an event ID of an event executed before the event corresponding to “ID-3”. In the order information created here, the previous event ID is “ID-2” as indicated by a field 2070 in FIG.

  Next, the event information registration unit 207 refers to the history information storage unit 202, and uses the event ID “ID-2” included in the event information received from the event ID assignment unit 211 as a key. To identify the record containing the event ID. Then, the event information registration unit 207 extracts “GR-1” that is the group ID included in the specified record, and stores the group file (FIG. 16B) corresponding to the extracted group ID in the group file. It specifies in the part 205.

  Next, the event information registration unit 207 receives from the event ID assignment unit 211 in association with “ID-3” which is the event ID newly assigned by the event ID assignment unit 211 in the identified group file. Information indicating at least a part of the contents of the event included in the event information (in the example of FIG. 17B, “action”, “location”, and “date / time”) and the created order information are stored. Then, the event information registration unit 207 notifies the order information update unit 208 of “GR-1” that is the group ID of the updated group file.

  Next, the order information update unit 208 receives “ID-3”, which is the event ID newly assigned by the event ID assigning unit 211, as the event ID included in the event information received from the event ID assigning unit 211 “ Order information is created as the event ID of the event executed next to the event corresponding to “ID-2”. In the order information created here, the post-event ID is “ID-3” as indicated by the field 2071 in FIG. Then, the order information update unit 208 includes the created order information and is included in the event information received from the event ID assignment unit 211 stored in the group file corresponding to the group file notified from the event information registration unit 207. The order information of the event corresponding to the event ID “ID-2” is updated. As a result, the data in the group file updated by the event information registration unit 207 has the contents as shown in FIG.

  Next, the operation of the history management server 20 when registering history information in the present embodiment will be described with reference to FIG. When event information is received from the terminal 30 via the communication line 11, the history management server 20 starts the operation shown in this flowchart.

  First, the event ID assigning unit 211 assigns a new event ID to an event corresponding to the event information received from the terminal 30 (S300), and assigns the newly assigned event ID to the terminal 30 via the communication line 11. Send. Then, the event ID assignment unit 211 transmits the event information received from the terminal 30 together with the newly assigned event ID to the history information registration unit 203, the event information registration unit 207, and the order information update unit 208.

  Next, the history information registration unit 203 specifies the record corresponding to the event ID by searching the history information storage unit 202 using the event ID included in the event information received from the event ID assignment unit 211 as a key. The history information registration unit 203 acquires the group ID included in the identified record from the history information storage unit 202 (S301). Then, the history information registration unit 203 associates the event ID newly assigned by the event ID assignment unit 211 with the group ID acquired from the history information storage unit 202, with the article ID and event content included in the event information. At the same time, it is registered in the history information storage unit 202 (S302).

  Next, the event information registration unit 207 executes the event ID included in the event information received from the event ID assignment unit 211 before the event corresponding to the event ID newly assigned by the event ID assignment unit 211. Order information is created as the event ID of the event (S303). Then, the event information registration unit 207 refers to the history information storage unit 202 and searches the history information storage unit 202 using the event ID included in the event information received from the event ID assignment unit 211 as a key, thereby The record including the ID is specified.

  Then, the event information registration unit 207 extracts the group ID included in the identified record, and identifies the group file corresponding to the extracted group ID in the group file storage unit 205. Then, the event information registration unit 207 associates the event ID newly assigned by the event ID assignment unit 211 with the event information received from the event ID assignment unit 211 in the identified group file. The information indicating at least a part of the information and the created order information are stored (S304). Then, the event information registration unit 207 notifies the order information update unit 208 of the group ID of the updated group file.

  Next, the order information update unit 208 executes the event ID newly assigned by the event ID assignment unit 211 next to the event corresponding to the event ID included in the event information received from the event ID assignment unit 211. As the event ID of the event, event order information corresponding to the event ID included in the event information received from the event ID assigning unit 211 is created. Then, the order information update unit 208 includes the created order information and is included in the event information received from the event ID assignment unit 211 stored in the group file corresponding to the group file notified from the event information registration unit 207. The event order information corresponding to the event ID is updated (S305), and the history management server 20 ends the operation at the time of registering the history information shown in this flowchart.

  The second embodiment of the present invention has been described above.

  As is clear from the above description, also in the history management system 10 of the present embodiment, the time required for tracking history information can be shortened. Further, in the history management server 20 of the present embodiment, the temporary storage unit 210 is unnecessary, so that the storage capacity in the history management server 20 can be saved.

  Next, a third embodiment of the present invention will be described.

  The history management system 10 according to the present embodiment performs a history information search process and a registration process for a product that is produced from a raw material in a flow manner, such as mixed production in a chemical plant. The system configuration of the history management system 10 in the present embodiment is similar to the system configuration of the history management system 10 in the first embodiment described with reference to FIG. 1, and each terminal 30 is installed in various places in the factory. This is different from the history management system 10 in the first embodiment. Since the collected event information occurs in the factory, the history management server 20 is installed in the factory. However, as another form, the history management server 20 may be installed in a management center or the like outside the factory. Good. Each terminal 30 is the same as the terminal 30 in the first embodiment described in FIG.

  FIG. 19 shows the contents of data in the history information storage unit 202 of the history management server 20 after the production process described in this embodiment is executed. In the production process of the present embodiment, after four types of raw materials having article IDs “P001” to “P004” arrive at factory A (corresponding to records 2028 having event IDs “ID-1” to “ID-4”). ), 3 types of raw materials with article IDs “P001” to “P003” are put into device B in factory A 10 liters each (corresponding to record 2028 with event IDs “ID-5” to “ID-7”) ), The product with the product ID “P010” is produced (corresponding to the record 2028 with the vent ID “ID-8”), and 10 liters of the raw material with the product ID “P004” is put into the apparatus B in the factory A After that, the product with the product ID “P011” is produced (corresponding to the record 2028 with the event ID “ID-10”).

  In the production process of the present embodiment, after the four types of raw materials having the article IDs “P001” to “P004” are input, the product having the article ID “P010” and the product “P011” are not produced. The product with the product ID “P010” is produced after the three types of raw materials with the product IDs “P001” to “P003” are input, and the product with the product ID “P011” is further provided with the product ID “ It is produced after the raw material “P004” is introduced. That is, the production process in the present embodiment is a production method in which the input of raw materials and the production of products are performed in a flow manner, and the correspondence between the raw materials and the products is a many-to-many relationship.

  In this way, when a certain product is produced from a plurality of raw materials, it is possible to define as a degree of correlation whether or not the proportion of each raw material included in a certain product is high. For example, when a mixer in a factory produces a product by mixing raw materials, the correlation between the raw material and the product increases immediately after the input of a certain raw material, and as other raw materials are input, It is thought that the correlation between the raw material first input and the product to be produced is lowered.

  An example of the correlation graph 45 showing the relationship between the input amount of raw material and the correlation is shown in FIG. The correlation graph 45 shows that the correlation is the highest immediately after the raw materials are added, and the correlation between the first input raw material and the product to be produced decreases each time another raw material is added. Is shown. For example, when 10 liters of other raw materials are added, the degree of correlation between the target raw material and the product is reduced to 0.5, 0.3, 0.1, and the input amount of other raw materials is 25 liters. If it exceeds, the degree of correlation becomes zero. The shape of the correlation degree graph 45 does not necessarily have to be the one shown in FIG. 20, and an optimal one may be used according to the production method. For example, if the raw material immediately after being put is put in the buffer and the product is not produced from the raw material immediately, the shape of the correlation graph increases as the input amount increases and decreases from a certain point. become.

  Further, in the present embodiment, as the information that associates the articles having the correlation as described above, such as the raw materials and the products produced therefrom, but in the group file of each article. Further, information for specifying a group file of other related articles and information indicating a degree of correlation with the related other articles are further registered. Thereby, by referring to each group file, the user can acquire information specifying the group file of other related articles and information indicating the degree of correlation with the related other articles.

  FIG. 21 is a block diagram illustrating an example of a detailed functional configuration of the history management server 20 according to the third embodiment. The history management server 20 includes an input unit 200, a group ID extraction unit 201, a history information storage unit 202, a history information registration unit 203, a group information output unit 204, a group file storage unit 205, a detailed information output unit 206, and an event information registration unit. 207, an order information update unit 208, a deletion unit 209, a temporary storage unit 210, and a business flow storage unit 212. Except for the points described below, in FIG. 21, the components denoted by the same reference numerals as those in FIG. 3 have the same or similar functions as those in FIG.

  The business flow storage unit 212 stores a plurality of records 2124 as shown in FIG. 22, for example. Each record 2124 includes a field 2120 for storing information indicating the order of events, a field 2121 for storing information indicating an action corresponding to the event, a field 2122 for storing information indicating a place where the action is executed, In addition, a field 2123 for storing information indicating processing that needs to be performed when the action is executed is stored.

  In the field 2123, for example, for an event in which the action is “input” and the place where the action is executed is “apparatus B”, processing for updating the correlation of the input raw material is required. Information indicating this is stored. Further, for example, for an event in which the action is “production” and the place where the action is executed is “device B”, in the respective group files of the input raw material and the produced product, the related information Is stored in the field 2123 indicating that it is necessary to set the value. Further, for example, for an event in which the action is “shipment” and the place where the action is executed is “factory A”, the corresponding record is deleted from the temporary storage unit 210 because it is the end of the business. Information indicating that it is necessary is stored.

  For example, as shown in FIG. 23, the group file storage unit 205 stores a field 2051 for storing a group ID and a plurality of records 2059 for each group file 2050. Each record 2059 is stored in a field 2052 for storing an event ID, a field 2053 for storing an event ID of a previously executed event, a field 2054 for storing an event ID of an event to be executed later, and a field 2052. A field 2055 for storing information indicating at least a part of the event corresponding to the event ID is stored.

  In the field 2055, in addition to the information in the field 2055 in the first embodiment described with reference to FIG. 5, information related to the event executed before the event shown in the own group file is executed is also displayed. Information on other group files to be stored, a field 2060 for storing information on other group files related in the production process, and an event executed after the event shown in the own group file is executed A field 2061 for storing information on other group files related to the production process is stored.

  The field 2060 further includes an event ID of an event executed before the event corresponding to the event ID stored in the field 2062 and the field ID stored in the field 2052 for storing the group ID of another related group file. A field 2063 for storing an event ID in the group file corresponding to the group ID stored in 2062, an event corresponding to the event ID stored in the field 2052, and an event ID stored in the field 2063. A field 2064 for storing the degree of correlation with the event is stored.

  The field 2061 further includes an event ID of an event to be executed after an event corresponding to the event ID stored in the field 2065 and the field ID stored in the field 2052 for storing group IDs of other related group files. Corresponding to the event 2066 storing the event ID in the group file corresponding to the group ID stored in the field 2065, the event corresponding to the event ID stored in the field 2052, and the event ID stored in the field 2066. A field 2067 for storing the degree of correlation with the event to be stored is stored.

  If there is no related group file, the field 2055 may not include the field 2060 and the field 2061. When there are a plurality of related group files, a plurality of fields 2060 and 2061 are stored in the field 2055.

  The temporary storage unit 210 stores a plurality of records 2108, for example, as shown in FIG. In addition to the information in the record 2108 in the first embodiment described with reference to FIG. 6, each record 2108 further includes a field 2109 for storing the correlation degree of raw materials applied when the product is produced. Is done.

  For example, the input unit 200 displays the input screen 40 shown in FIG. 7 on the display device 18, and when receiving information for each item via the input device 17, transmits the received information to the group ID extraction unit 201. . Further, the input unit 200 displays the selected group ID in the group information output unit 204 when a group ID is selected in a state where the correlation information screen 46 as shown in FIG. 25 is displayed on the display device 18, for example. Send to. When the end button 461 is selected while the correlation information screen 46 as shown in FIG. 25 is displayed on the display device 18, the input unit 200 displays the input screen 40 shown in FIG. To display. When the end button 415 is selected while the group information screen 41 as shown in FIG. 8 is being displayed on the display device 18, the input unit 200 instructs the group information output unit 204 to display FIG. The displayed input screen 40 is displayed on the display device 18.

  The group ID extraction unit 201 refers to the history information storage unit 202 based on the information received from the input unit 200, identifies a record including information specified by the user as a starting record, and sets the identified record as The included group ID and article ID are transmitted to the group information output unit 204. The group information output unit 204 searches the group file storage unit 205 using the group ID received from the group ID extraction unit 201 as a key, acquires a group file corresponding to the group ID, and stores the article ID together with the article ID of the history management server 20. Expand on RAM.

  When related information specifying another group file is not registered in the expanded group file, the group information output unit 204 creates a group information screen 41 (see FIG. 8) showing the contents of the expanded group file. It is displayed on the display device 18. On the other hand, when related information specifying another group file is registered in the expanded group file, the group information output unit 204 acquires the group ID and the degree of correlation of the other group file, as shown in FIG. The correlation information screen 46 is created and displayed on the display device 18.

  When the group ID is received from the input unit 200, the group information output unit 204 indicates the group information indicating the contents of the group file expanded on the RAM if the group file corresponding to the group ID exists on the RAM. A screen 41 is created and displayed on the display device 18. On the other hand, when the group file corresponding to the group ID received from the input unit 200 does not exist in the RAM, the group information output unit 204 searches the group file storage unit 205 using the group ID as a key and corresponds to the group ID. After the group file to be acquired is acquired and expanded on the RAM of the history management server 20, a group information screen 41 showing the contents of the group file is created and displayed on the display device 18.

  When a new record including information other than the degree of correlation is registered in the temporary storage unit 210, the event information registration unit 207 is based on the action and location information included in the newly registered record. With reference to the storage unit 212, it is determined whether or not it is necessary to update the correlation or set related information. When it is not necessary to update the degree of correlation and set related information, the event information registration unit 207 executes the processing described in the first embodiment.

  On the other hand, when the correlation degree needs to be updated, the event information registration unit 207 includes a record newly registered in the temporary storage unit 210 and a record in the record in which the correlation degree is set in the temporary storage unit 210. From the information, the correlation degree is calculated using the correlation information screen 46 shown in FIG. 20, and the correlation degree is set for a record newly registered in the temporary storage unit 210, and the correlation degree is set in the temporary storage unit 210. Update the correlation in the set record. Details of the calculation method of the correlation degree will be described later.

  In addition, when the related information needs to be set, the event information registration unit 207 refers to the record in which the degree of correlation is set in the temporary storage unit 210, and determines the group ID and event ID included in the record. Get each. Then, the event information registration unit 207 refers to the group file storage unit 205 and updates the field 2061 corresponding to the acquired event ID in the group file corresponding to the acquired group ID. Then, the event information registration unit 207 creates a group file included in the record newly registered in the temporary storage unit 210 in the group file storage unit 205, and in the record stored in the created group file, the field information 2060 is updated. Details of these update procedures will be described later.

  The deletion unit 209, when notified from the order information update unit 208 of the end of update of the order information, deletes another record including the same item ID as the item ID included in the record newly registered in the temporary storage unit 210. Delete from the temporary storage unit 210. In addition, the deletion unit 209 refers to the business flow storage unit 212 and deletes the record including the combination of the action and the location corresponding to the last event of the business from the temporary storage unit 210. In addition, the deletion unit 209 deletes from the temporary storage unit 210 a record in which a degree of correlation equal to or less than a predetermined value (for example, 0 or less) is set.

  Here, the history information registration processing executed by the history information registration unit 203, the event information registration unit 207, the order information update unit 208, and the deletion unit 209 will be described with reference to FIGS. For example, when the data shown in FIGS. 26A to 26C are stored in the history information storage unit 202, the temporary storage unit 210, and the group file 2050, respectively, the event shown in FIG. When the information 47 is received, the history information registration unit 203 assigns “ID-8” as a new event ID to the event indicated by the event information 43.

  Next, the history information registration unit 203 searches the temporary storage unit 210 for a group ID associated with the same product ID as “P010” that is the product ID included in the event information 47. Since “P010” is not registered in the history information storage unit 202, the history information registration unit 203 newly generates “GR-5” as the group ID associated with the article ID. Then, as shown in FIGS. 27A and 27B, the history information registration unit 203 associates the newly assigned event ID “ID-8” with the article ID included in the event information 47. “P010”, “Production”, “Apparatus B”, “2007-07-23 12:00”, and “D” which are the contents of the event received from the terminal 30, and the newly generated group ID “GR-5” is registered in the history information storage unit 202 and the temporary storage unit 210. At this point, the correlation field in the record newly registered in the temporary storage unit 210 is blank.

  Next, the event information registration unit 207 refers to the business flow storage unit 212 based on the action and location information included in the record newly registered in the temporary storage unit 210, and updates the correlation or sets related information. Whether or not is necessary. In the example of FIG. 27B, the event information registration unit 207 executes the setting of related information because a record with the action “production” and the location “device B” is newly registered in the temporary storage unit 210. Will do.

  First, the event information registration unit 207 has a record in which the degree of correlation is set in the temporary storage unit 210 (a record including an event ID of “ID-5”, “ID-6”, or “ID-7”). , The event ID and group ID ("GR-1", "GR-2", and "GR-3") included in the record are acquired, respectively. Then, the event information registration unit 207 refers to the group file storage unit 205 and identifies a record corresponding to the acquired event ID in the group file corresponding to the acquired group ID. Then, the event information registration unit 207 provides a field 2061 for storing information regarding a group file including an event ID of an event to be executed later in the specified record, and the field 2061 includes “GR-5” and “ID Register "-8" and "0.1". As a result, the data in the group file with the group ID “GR-1” has the contents as shown in FIG.

  Next, the event information registration unit 207 creates a group file corresponding to the group ID included in the record newly registered in the temporary storage unit 210 in the group file storage unit 205, and stores the group file in the created group file. Is provided with a field 2060 for storing information related to the group file including the event ID of the event to be executed, and “GR-1”, “ID-5”, and “0.1” are registered in the field 2060. As a result, the data in the group file with the group ID “GR-5” has the contents as shown in FIG.

  Next, when the event information 48 illustrated in FIG. 29A is received, the history information registration unit 203 assigns “ID-9” as a new event ID to the event indicated by the event information 48. Then, the history information registration unit 203 refers to the temporary storage unit 210 and sets “GR-4” as the group ID associated with the same product ID as “P004” that is the product ID included in the event information 48. To get. Then, as shown in FIGS. 29B and 29C, the history information registration unit 203 associates the newly assigned event ID “ID-9” with the article ID included in the event information 48. From the “P004”, the contents of the event received from the terminal 30 “Throw (10L)”, “Apparatus B”, “2007-07-23 13:30”, “C”, and the temporary storage unit 210 The acquired group ID “GR-4” is registered in the history information storage unit 202 and the temporary storage unit 210. At this point, the correlation field in the record newly registered in the temporary storage unit 210 is blank.

  Next, the event information registration unit 207 refers to the business flow storage unit 212 based on the action and location information included in the record newly registered in the temporary storage unit 210, and updates the correlation or sets related information. Whether or not is necessary. In the example of FIG. 29C, since the record with the action “input (10L)” and the location “device B” is newly registered in the temporary storage unit 210, the event information registration unit 207 displays the correlation degree. Updates will be performed.

  The event information registration unit 207 records the event ID of “ID-5”, “ID-6”, or “ID-7” in FIG. 27B in which the degree of correlation is set in the temporary storage unit 210. For each record), the degree of correlation with the product that has changed due to the input of the raw material corresponding to the article ID included in the record newly registered in the temporary storage unit 210 is calculated. For example, since the raw material with the article ID “P004” does not exist in the apparatus before the raw material is newly input into the apparatus B, the input amount becomes 0 in FIG. 20, and the event information registration unit 207 The correlation degree of the raw material is calculated as “0.5”.

  For raw materials that have already been input before the raw materials are newly input, the degree of correlation decreases according to the input amount each time new raw materials are input. The correlation of the raw material with the product ID “P003” was “0.5” before the raw material with the product ID “P004” was added, but the raw material with the product ID “P004” was newly set to 10 liters. As a result, the event information registration unit 207 uses the correlation degree graph 45 of FIG. 20 to calculate the correlation degree of the raw material with the article ID “P003” after the raw material is newly input, using “0.3”. Is calculated. Similarly, the event information registration unit 207 calculates the correlation degree of the raw material with the article ID “P002” as “0.1” and the correlation degree of the raw material with the article ID “P001” as “0”. Then, the event information registration unit 207 registers the calculated correlation degree for the record newly registered in the temporary storage unit 210, and calculates the record for which the correlation degree is set in the temporary storage unit 210. The correlation degree set with the correlation degree is updated.

  Next, the deletion unit 209 refers to the temporary storage unit 210 and records (corresponding to the correlation degree by the event information registration unit 207) in which a correlation level equal to or less than a predetermined value (0 or less in this embodiment) is set. The record including the event ID “ID-5” after the update is performed is deleted from the temporary storage unit 210. As a result, the data in the temporary storage unit 210 has the contents as shown in FIG. Note that the update of the group file corresponding to the record newly registered in the temporary storage unit 210 is the same as the process described in the first embodiment, and thus the description thereof is omitted, but after the process is executed. The data in the group file is as shown in FIG.

  Next, the operation of the history management server 20 when registering history information in the present embodiment will be described with reference to FIG. When event information is received from the terminal 30 via the communication line 11, the history management server 20 starts the operation shown in this flowchart. In this flowchart, the processing from step S400 to S405 is the same as the processing from step S200 to S205 described in FIG.

  After the order information update unit 208 updates the order information (S405), the event information registration unit 207, based on the action and location information included in the record newly registered in the temporary storage unit 210, the business flow storage unit 212. To determine whether or not the degree of correlation needs to be updated (S406). When the correlation degree needs to be updated (S406: Yes), the event information registration unit 207 has a record newly registered in the temporary storage unit 210, and the correlation degree is set in the temporary storage unit 210. The correlation degree is calculated from the information in the record using the correlation information screen 46 shown in FIG. 20, and the correlation degree is set for the record newly registered in the temporary storage unit 210. The correlation degree in the record in which the correlation degree is set is updated (S407). Then, the deletion unit 209 deletes from the temporary storage unit 210 a record in which a degree of correlation equal to or less than a predetermined value is set (S408).

  Next, the deletion unit 209 refers to the business flow storage unit 212 and deletes the record including the combination of the action and the location corresponding to the last event of the business from the temporary storage unit 210 (S409). Then, the deletion unit 209 deletes from the temporary storage unit 210 another record including the same item ID as the item ID included in the record newly registered in the temporary storage unit 210 (S410), and the history management server 20 Then, the operation at the time of registering the history information shown in this flowchart is terminated.

  When the correlation degree does not need to be updated (S406: No), the event information registration unit 207 sets the business flow storage unit 212 based on the action and location information included in the record newly registered in the temporary storage unit 210. It is referred and it is determined whether the setting of related information is necessary (S411). When the setting of the related information is unnecessary (S411: No), the deletion unit 209 executes the process shown in step S409.

  When the related information needs to be set (S411: Yes), the event information registration unit 207 refers to the record in which the degree of correlation is set in the temporary storage unit 210, and includes the group ID and the information included in the record. Each event ID is acquired. Then, the event information registration unit 207 refers to the group file storage unit 205 and updates the field 2061 corresponding to the acquired event ID in the group file corresponding to the acquired group ID. Then, the event information registration unit 207 creates a group file included in the record newly registered in the temporary storage unit 210 in the group file storage unit 205. Then, the event information registration unit 207 updates the field 2060 in the record stored in the created group file (S412), and the deletion unit 209 executes the process shown in step S409.

  Heretofore, the third embodiment of the present invention has been described.

  As is clear from the above description, also in the history management system 10 of the present embodiment, the time required for tracking history information can be shortened. Further, in the history management system 10 of the present embodiment, when a plurality of articles are related, information indicating the relationship between articles is stored in the group file for each article, and the group file including information on the target article is stored. By displaying other related group IDs and the degree of correlation together with the group ID, the user can track the history information from a more relevant group file first, so the cause investigation can be performed more efficiently. It can be carried out.

  Note that the history management server 20 in the first embodiment, the second embodiment, or the third embodiment described above is realized by a computer 50 configured as shown in FIG. 31, for example. The computer 50 includes a central processing unit (CPU) 51, a random access memory (RAM) 52, a read only memory (ROM) 53, a hard disk drive (HDD) 54, a communication interface (I / F) 55, an input / output interface ( I / F) 56 and media interface (I / F) 57.

  The CPU 51 operates based on a program stored in the ROM 53 or the HDD 54 and controls each unit. The ROM 53 stores a boot program executed by the CPU 51 when the computer 50 is started up, a program depending on the hardware of the computer 50, and the like. The communication interface 55 receives data from other devices via the communication line 11 and transmits the data to the CPU 51, and transmits data generated by the CPU 51 to other devices via the communication line 11.

  The CPU 51 controls the input device 17 and the display device 18 via the input / output interface 56. The CPU 51 acquires data from the input device 17 via the input / output interface 56. Further, the CPU 51 outputs the generated data to the display device 18 via the input / output interface 56.

  The media interface 57 reads a program or data stored in the recording medium 58 and provides it to the RAM 52. A program provided to the CPU 51 via the RAM 52 is stored in the recording medium 58. The program is read from the recording medium 58, installed in the computer 50 via the RAM 52, and executed by the CPU 51. The recording medium 58 is, for example, an optical recording medium such as a DVD (Digital Versatile Disk) or PD (Phase change rewritable disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. Etc.

  When the computer 50 functions as the history management server 20 in the first embodiment, a program installed and executed on the computer 50 includes the input unit 200, the group ID extraction unit 201, the history information storage unit 202, The history information registration unit 203, group information output unit 204, group file storage unit 205, detailed information output unit 206, event information registration unit 207, order information update unit 208, deletion unit 209, and temporary storage unit 210 are caused to function. The ROM 53 or the HDD 54 stores data in the history information storage unit 202, the group file storage unit 205, and the temporary storage unit 210.

  When the computer 50 functions as the history management server 20 in the second embodiment, the program installed in the computer 50 and executed is the input unit 200, the group ID extraction unit 201, the history information storage unit. 202, a history information registration unit 203, a group information output unit 204, a group file storage unit 205, a detailed information output unit 206, an event information registration unit 207, an order information update unit 208, and an event ID assignment unit 211. The ROM 53 or the HDD 54 stores data in the history information storage unit 202 and the group file storage unit 205.

  When the computer 50 functions as the history management server 20 in the third embodiment, a program installed on the computer 50 and executed is the computer 50, the input unit 200, the group ID extraction unit 201, the history information storage unit. 202, history information registration unit 203, group information output unit 204, group file storage unit 205, detailed information output unit 206, event information registration unit 207, order information update unit 208, deletion unit 209, temporary storage unit 210, and business flow It functions as the storage unit 212. The ROM 53 or the HDD 54 stores data in the history information storage unit 202, the group file storage unit 205, the temporary storage unit 210, and the business flow storage unit 212.

  The computer 50 reads these programs from the recording medium 58 and executes them, but as another example, these programs may be acquired from other devices via a communication medium. The communication medium refers to the communication line 11 or a digital signal or carrier wave that propagates through the communication line 11.

  In addition, this invention is not limited to each above-mentioned embodiment, Many deformation | transformation are possible within the range of the summary.

  For example, in the above-described third embodiment, when the group ID extraction unit 201 extracts a plurality of group IDs based on information input from the user, and a plurality of related information is set in each group file, The group information output unit 204 may total the correlations for other related group IDs, and display a correlation information screen 46 as shown in FIG. 32 on the display device 18, for example. For example, the degree of correlation with the group file whose group ID is “GR-5” is 0.5, the degree of correlation with the group file whose group ID is “GR-6” is 0.3, and the group ID is “ For the group file “GR-2”, the event information registration unit 207 calculates 0.8 as the sum of the correlation degrees. As a result, when a plurality of articles are out of specification and each of the articles is related to a plurality of articles, the user can obtain information on the article most strongly related to the plurality of out-of-standard articles. The history information can be tracked first from the group file storing the information, and the cause investigation efficiency can be further improved.

In the third embodiment described above, the history management server 20 expresses the degree of relevance between the raw material and the product using the “correlation degree”, but the present invention is not limited to this. For example, the history management server 20 may express the degree of relevance between the raw material and the product using “remaining ratio” instead of “correlation degree”. The “remaining ratio” is information indicating the ratio of the input raw material remaining in the apparatus, and is set only for the record whose “action” is “input”. When a new raw material is introduced, the event information registration unit 207 calculates the “remaining amount ratio” of the new record registered in the temporary storage unit 210 using, for example, Equation 1 below.
α = [input amount] ÷ ([input amount] + [amount of raw material present in the apparatus]) Equation 1

  Here, the “amount of raw material present in the apparatus” is the amount of the raw material immediately before the raw material input, measured by a sensor provided in the apparatus. Further, when a new record is registered in the temporary storage unit 210, the event information registration unit 207 multiplies the “remaining ratio” of the record already registered in the temporary storage unit 210 by (1−α). This corrects the degree of influence of the raw materials already input on the product. In this method, since the “remaining ratio” does not become 0 forever, the deletion unit 209 deletes a record whose “remaining ratio” is less than 0.01, for example.

  Further, in each of the above-described embodiments, the order information stored in the group file is information indicating the event ID of the previously executed event and the event ID of the next executed event. However, the order information may be a numerical value as long as the order in which the events are executed is indicated.

  In each of the above-described embodiments, the history information storage unit 202, the group file storage unit 205, the temporary storage unit 210, and the business flow storage unit 212 are provided in the history management server 20, but as other forms, these databases May be provided in another apparatus such as a database server, and the history management server 20 may communicate with the apparatus via the communication line 11 to acquire necessary data.

  In each of the above-described embodiments, the user directly operates the history management server 20 to acquire the history information of the desired article. However, the present invention is not limited to this, and the history management server 20 includes the communication line 11. The history information of the article may be provided in response to a request from a predetermined terminal that has undergone authentication or the like. Thereby, the history management server 20 can provide article history information to general consumers and related businesses.

It is a system configuration figure showing the composition of history management system 10 in a 1st embodiment. It is a block diagram showing an example of detailed functional composition of terminal 30 in a 1st embodiment. It is a block diagram which shows an example of the detailed function structure of the log | history management server 20 in 1st Embodiment. It is a figure which shows an example of the structure of the data stored in the log | history information storage part. It is a figure which shows an example of the structure of the data stored in the group file storage part 205 in 1st Embodiment. It is a figure which shows an example of the structure of the data stored in the temporary storage part 210 in 1st Embodiment. 4 is a conceptual diagram illustrating an example of an input screen 40 displayed on the display device 18. FIG. 4 is a conceptual diagram illustrating an example of a group information screen 41 displayed on the display device 18. FIG. 4 is a conceptual diagram illustrating an example of a detailed information screen 42 displayed on the display device 18. FIG. 6 is a diagram illustrating an example of data in a history information storage unit 202, a temporary storage unit 210, and a group file 2050 before event information 43 is transmitted in the first embodiment. FIG. 6 is a diagram illustrating an example of data in a history information storage unit 202, a temporary storage unit 210, and a group file 2050 after the contents of event information 43 are reflected in the first embodiment. FIG. It is a flowchart which shows an example of the operation | movement of the log | history management server 20 at the time of log | history information search in 1st Embodiment. It is a flowchart which shows an example of operation | movement of the log | history management server 20 at the time of log | history information registration in 1st Embodiment. It is a block diagram which shows an example of the detailed functional structure of the terminal 30 in 2nd Embodiment. It is a block diagram which shows an example of the detailed function structure of the log | history management server 20 in 2nd Embodiment. In 2nd Embodiment, it is a figure which shows an example of the data in the history information storage part 202 and the group file 2050 before the event information 44 is transmitted. In 2nd Embodiment, it is a figure which shows an example of the data in the history information storage part 202 and the group file 2050 after the content of the event information 44 was reflected. It is a flowchart which shows an example of operation | movement of the log | history management server 20 at the time of log | history information registration in 2nd Embodiment. It is a figure which shows an example of the data stored in the log | history information storage part 202 in 3rd Embodiment. It is a figure which shows an example of the correlation graph 45 used for calculation of a correlation. It is a block diagram which shows an example of the detailed function structure of the log | history management server 20 in 3rd Embodiment. 4 is a diagram illustrating an example of a structure of data stored in a business flow storage unit 212. FIG. It is a figure which shows an example of the structure of the data stored in the group file storage part 205 in 3rd Embodiment. It is a figure which shows an example of the structure of the data stored in the temporary memory part 210 in 3rd Embodiment. It is a conceptual diagram which shows an example of the correlation information screen 45 displayed on the display apparatus 18 in 3rd Embodiment. FIG. 20 is a diagram illustrating an example of data in a history information storage unit 202, a temporary storage unit 210, and a group file 2050 before event information 47 is transmitted in the third embodiment. In 3rd Embodiment, it is a figure which shows an example of the data in the history information storage part 202 and the temporary memory part 210 after the content of the event information 47 was reflected. FIG. 20 is a diagram illustrating an example of data in a group file 2050 after the contents of event information 47 are reflected in the third embodiment. FIG. 20 is a diagram illustrating an example of data in a history information storage unit 202, a temporary storage unit 210, and a group file 2050 after the contents of event information 48 are reflected in the third embodiment. It is a flowchart which shows an example of the operation | movement of the log | history management server 20 at the time of log | history information registration in 3rd Embodiment. 2 is a hardware configuration diagram illustrating an example of a configuration of a computer 50 that realizes a function of a history management server 20. FIG. It is a conceptual diagram which shows the other example of the correlation information screen 45 displayed on the display apparatus 18 in 3rd Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... History management system, 11 ... Communication line, 12 ... Base, 13 ... Gate, 14 ... Sensor, 15 ... Article, 16 ... Tag, 17 ... Input Device: 18 ... Display device, 20 ... History management server, 200 ... Input unit, 201 ... Group ID extraction unit, 202 ... History information storage unit, 203 ... History information registration unit 204 ... Group information output unit 205 ... Group file storage unit 2050 ... Group file 206 ... Detailed information output unit 207 ... Event information registration unit 208 ... Order information Update unit, 209 ... Deletion unit, 210 ... Temporary storage unit, 211 ... Event ID allocation unit, 212 ... Business flow storage unit, 30 ... Terminal, 31 ... ID transmission unit, 32... ID acquisition unit, 33 ID rewriting unit, 40 ... input screen, 41 ... group information screen, 42 ... detailed information screen, 43 ... event information, 44 ... event information, 45 ... correlation degree graph, 46 ... correlation information screen, 47 ... event information, 48 ... event information, 50 ... computer, 51 ... CPU, 52 ... RAM, 53 ... ROM, 54 ... HDD, 55 ... communication interface, 56 ... input / output interface, 57 ... media interface, 58 ... recording medium

Claims (7)

A history management server that manages the history of individual articles,
A group file storing information indicating at least a part of the contents of the event and order information indicating the order of the event in association with an event ID for identifying each of a series of events applied to the article, A group file storage means for storing in association with a group ID for identifying a group of a series of events;
For each event ID, the article ID of the article subjected to the event identified by the event ID, the content of the event identified by the event ID, and the group ID of the group file storing the event ID are stored. History information storage means;
Input means for receiving information indicating the content of the event as a starting point;
Group ID extraction for sequentially reading information stored in the history information storage means, identifying an event ID corresponding to the content of the event as the starting point, and extracting a group ID associated with the identified event ID Means,
The information stored in the group file storage means is sequentially read, the group file corresponding to the group ID extracted by the group ID extraction means is extracted, and the information stored in the extracted group file A history management server comprising group information output means for processing into a format and outputting the information. The history management server according to claim 1,
In the group file, physical address information in the history information storage means in which the event ID and content of the event are stored is stored as information indicating at least a part of the content of the event,
The input means includes
Further accepting designation of an event ID in the group file output by the group information output means;
The history management server
When an event ID in the group file is designated via the input means, information stored in the history information storage means is sequentially read out and stored in the group file in association with the event ID. A history management server, further comprising detailed information output means for acquiring and outputting the contents of an event corresponding to the event ID from a position on a memory indicated by address information. The history management server according to claim 1 or 2,
In the group file, as order information, an event ID of an event executed before the event and an event ID of an event executed after the event are stored,
The group information output means includes
A history management server that outputs an event ID and information indicating at least part of the content of the event in an array according to the order of events when outputting the content indicated by the group file. The history management server according to claim 3,
Temporary storage means for storing the article ID of the article, the contents of the event, and the group ID of the group file including the event ID in association with the event ID of the latest event applied to each article;
When information indicating the item ID and the content of the event is received from an external terminal, an event ID is newly assigned to the event indicated by the content of the event, and the external terminal is referred to by referring to the temporary storage unit The group ID associated with the same article ID as the article ID received from is acquired, the article ID received from the external terminal is associated with the newly assigned event ID, and the event received from the external terminal History information registration means for registering the contents and the group ID acquired from the temporary storage means in the history information storage means and the temporary storage means;
In the temporary storage means, another event ID associated with the same item ID as the newly registered item ID is set to an event executed before the event corresponding to the newly registered event ID. Order information is created as an event ID, and the group file corresponding to the group ID newly registered in the temporary storage unit is associated with the event ID newly registered in the temporary storage unit, and stored in the temporary storage unit. Information indicating at least part of the contents of the newly registered event, and event information registration means for storing the created order information;
When the group file is updated by the event information registration unit, another event ID associated with the same item ID as the item ID newly registered in the temporary storage unit is specified in the temporary storage unit. Then, the event ID newly registered in the temporary storage means is used as the event ID of the event executed next to the event corresponding to the other event ID, and the order information of the event corresponding to the other event ID is used. Order information updating means for updating the order information of the event corresponding to the other event ID stored in the group file updated by the event information registration means with the created order information;
When the order information is updated by the order information updating means, the temporary storage means is referred to, the same article ID as the newly registered article ID, the event ID associated with the same article ID, A history management server further comprising: deletion means for deleting the contents of the event corresponding to the event ID and the group ID associated with the same article ID from the temporary storage means. The history management server according to claim 4,
The deleting means is
When the content of the event registered in the temporary storage means indicates the content of a predetermined event, the content of the event, the event ID associated with the content of the event, the article ID, And a history management server further deleting the group ID from the temporary storage means. The history management server according to claim 3,
When receiving information indicating an article ID, an event ID, and an event content from an external terminal, a new event ID is assigned to the event indicated by the event content, and the newly assigned event ID is assigned to the event ID. An event ID assigning means for transmitting to an external terminal;
When a new event ID is assigned by the event ID assigning means, a group ID stored in the history information storing means in association with an event ID received from an external terminal is specified, and the event ID assignment History information for registering in the history information storage means the article ID received from the external terminal, the content of the event received from the external terminal, and the specified group ID in association with the event ID newly assigned by the means Registration means;
When a new event ID is assigned by the event ID assigning means, the event ID received from the external terminal is executed before the event corresponding to the event ID newly assigned by the event ID assigning means. Creates order information as an event ID of an event, refers to the history information storage means, extracts a group ID associated with an event ID received from an external terminal, and a group file corresponding to the extracted group ID Event information registration for storing information indicating at least a part of the contents of the event received from the external terminal and the created order information in association with the event ID newly assigned by the event ID assigning means Means,
When a group file is updated by the event information registration unit, an event ID newly allocated by the event ID allocation unit is changed to an event to be executed next to an event corresponding to the event ID received from the external terminal. As the event ID, event order information corresponding to the event ID received from the external terminal is created, and the created order information is stored in the group file updated by the event information registration unit. A history management server, further comprising: order information updating means for updating order information of events corresponding to event IDs received from a terminal. A history management system for managing the history of individual articles,
A terminal at each location;
With a history management server,
The terminal
ID acquisition means for acquiring an article ID and an event ID from an tag attached to the article and holding an article ID for identifying the article and an event ID for identifying an event applied to the article;
ID transmission means for transmitting the article ID and event ID read by the ID acquisition means to the history management server together with information indicating the contents of the event applied to the article ID;
An ID rewriting means for rewriting the event ID in the tag with the received event ID when the event ID is received from the history management server;
The history management server
A group file that stores information indicating at least a part of the contents of the event corresponding to the event ID in association with the event ID and order information indicating the order of the event, and a group of a series of events applied to the article Group file storage means for storing in association with the group ID to be identified;
For each event ID, the article ID of the article subjected to the event identified by the event ID, the content of the event identified by the event ID, and the group ID of the group file storing the event ID are stored. History information storage means;
Input means for receiving information indicating the content of the event as a starting point;
Group ID extraction for sequentially reading information stored in the history information storage means, identifying an event ID corresponding to the content of the event as the starting point, and extracting a group ID associated with the identified event ID Means,
The information stored in the group file storage means is sequentially read, the group file corresponding to the group ID extracted by the group ID extraction means is extracted, and the information stored in the extracted group file Group information output means for processing into a format and outputting;
When information indicating an article ID, an event ID, and an event content is received from the terminal, an event ID is newly assigned to the event indicated by the event content, and the newly assigned event ID is assigned to the terminal. Event ID assigning means for transmitting to
When a new event ID is assigned by the event ID assigning means, a group ID stored in the history information storing means in association with an event ID received from an external terminal is specified, and the event ID assignment History information for registering in the history information storage means the article ID received from the external terminal, the content of the event received from the external terminal, and the specified group ID in association with the event ID newly assigned by the means Registration means;
When an event ID is newly assigned by the event ID assigning unit, the event ID received from the terminal is executed before the event corresponding to the event ID newly assigned by the event ID assigning unit. The order information is created as the event ID, and the history information storage unit is referred to, the group ID associated with the event ID received from the terminal is extracted, and the group file corresponding to the extracted group ID is extracted. Event information registration means for storing information indicating at least part of the contents of the event received from the terminal in association with the event ID newly assigned by the event ID assignment means, and the created order information;
When a group file is updated by the event information registration unit, an event ID newly allocated by the event ID allocation unit is changed to an event to be executed next to an event corresponding to the event ID received from the external terminal. As the event ID, event order information corresponding to the event ID received from the external terminal is created, and the created order information is stored in the group file updated by the event information registration unit. A history management system comprising: order information update means for updating order information of events corresponding to event IDs received from a terminal.

Images