JP2008013262A - Traceability support system and database structure applied thereto - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To trace and track back products in a distribution process including a packing condition. <P>SOLUTION: This traceability support system of the present invention, for tracing and tracking back the status of the product A in each step in the distribution process, is provided with a trace object master 83 and a trace object container/contents map 91. The trace object master manages the departure date 83b and arrival date 83c in the distribution process of the product A by associating them with respective products A-1 to A-4, and also manages the departure date 83b and arrival date 83c of a container B distributed along the distribution process while storing the product A by associating them with respective containers B-1 to B-3. The trace object container/contents map manages containers O-5 to O-7 by associating them with products O-1 to O-4 stored therein, and also manages in association with containers O-5 to O-6 if the container O-7 stores the other containers O-5 to O-6. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention, for example, traceability support apparatus capable of tracking the current location, configuration, content, status, and the like of a product or product and tracing the past location, configuration, content, status, change, etc. , And a database structure applied thereto.

  As a technique for managing and grasping the distribution state of products and products, there is a traceability system as disclosed in Patent Document 1, for example.

  Traceability is a term used in a wide range of fields, and its original meaning means that it can be traced. That is, it means that the history, whereabouts, location, configuration, contents, history of changes and changes, etc. of management units of products and products can be confirmed later. The basic requirement for traceability is that, firstly, the management unit of goods and products, etc. can be clarified and individually identified and “tracked”, and secondly, the records can be traced back. It is possible to “trace back”.

In this type of traceability system, a route such as when and where a target product or product came from is mainly registered and managed.
JP 2005-267625 A

  However, such a conventional traceability system has the following problems.

  That is, in the conventional traceability system, some products and products may be packed and distributed in trays, boxes, bags, etc. in an actual distribution process. Then, at a certain stage in the middle, the trays and boxes may be combined into another tray or box, and when the destination arrives, there may be a complicated state change in which the tray or box is removed from the packed tray or box. Therefore, when tracking the location, configuration, content, and state of a product or product after the middle stage or the end of distribution, management and grasping including the packing state in a tray or box may be required.

  However, in the conventional traceability system, only a predetermined target such as a product or a product itself is tracked, and management and grasping including a packing state is not performed. For this reason, in the distribution process, it is possible to grasp when and where a product or product has passed, but there is a problem that it is impossible to trace and trace back to what packaging state.

  The present invention has been made in view of such circumstances, and is applicable to a traceability support apparatus that enables tracking and retroactiveness in a distribution process including not only products and products but also their packaging states. It aims to provide a database structure.

  In order to achieve the above object, the present invention takes the following measures.

  That is, the invention of claim 1 is a traceability support apparatus that tracks and retroactively traces the state in each stage of the distribution process of an object, and includes first to third management means.

  The first management means manages the departure date of the object at the starting point in the distribution process and the arrival date at the arrival point in association with the object. Further, the second management means manages the departure date at the departure point and the arrival date at the arrival point of the storage means that stores the object that is distributed along the distribution process in association with the storage means. The third management means manages the storage means and the object stored in the storage means in association with each other. When the storage means stores other storage means, the third management means further includes other storage means. Are managed in association with each other.

  The invention of claim 2 is the traceability support apparatus of the invention of claim 1, wherein the first management means attaches a unique identifier to each object, and starts the object at the starting point in the distribution process. The date and the arrival date at the arrival point are managed using a first database associated with the identifier attached to the object. The second management means attaches a unique identifier to each storage means, and associates the departure date at the departure point and the arrival date at the arrival point of the storage means with the identifier attached to the storage means. To manage using the first database. Further, the third management means manages the associated storage means and the object, or the associated storage means, using the second database in which each identifier is associated.

  According to a third aspect of the present invention, in the traceability support apparatus according to the second aspect of the invention, the first and second management means include a registration means for registering a departure date and an arrival date in the first database, and a first database. A correction means for correcting the registered contents, a reference means for referring to the contents registered in the first database, and a deletion means for deleting any of the contents registered in the first database are provided. . The invention of claim 3 further includes a tracking means for tracking the state of the object or the storage means based on the first database.

  The invention according to claim 4 is the traceability support device according to any one of claims 1 to 3, wherein each of the identifier of the object or storage means to be retroactively, the time zone to be retroactively, and the distribution process An input unit that accepts an input of retroactive conditions including any one of the stages to be retrospectively acquired, and information corresponding to the retroactive conditions input to the input unit is acquired from the first database, and is output as retrospective information. And a retroactive means.

  The invention of claim 5 is a database structure applied to a traceability support apparatus that tracks and retroactively monitors the state in each stage of the distribution process of an object. Here, the database includes a first database and a second database. The first database associates the departure date at the starting point in the distribution process and the arrival date at the arrival point of the object with the identifier given to the object, and the starting point of the storage means. The departure date at and the arrival date at the arrival point are associated with the identifier attached to the storage means. Further, the second database associates the storage means and the object associated with each other in the first database, or the associated storage means with each identifier.

  ADVANTAGE OF THE INVENTION According to this invention, the traceability assistance apparatus which enabled the tracking and retroactiveness in a distribution process including not only goods and products, but also those packing states, and the database structure applied to it are realizable.

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

  FIG. 1 is a functional block diagram showing a configuration example of a traceability support apparatus according to an embodiment of the present invention. Here, tracking (tracking) and retroactive (trace back) are collectively referred to as a trace.

  That is, the traceability support apparatus according to the embodiment includes a control unit 3 in addition to an input unit 1 including an input device such as a mouse and a keyboard and an output unit 2 including an output device such as a display and a printer. A trace target management unit 4, a container / content management unit 5, a route information management unit 6, a route retroactive management unit 7, a trace target database 8, a container / content database 9, and a route database 10 are provided. Here, the container is a generic term for containers, bags, and the like that serve as storage means for storing products and products. A cart can also be considered as a container. The contents refer to products and products. The trace target database 8, the container / content database 9, and the path database 10 are held in a storage device such as a hard disk.

  In FIG. 1, the above-described parts are shown as being integrated. For example, the input unit 1 and the output unit 2 are configured by a client such as a personal computer, and the control unit 3, the trace target management unit 4, the container content. A management unit 5, a route information management unit 6, a route retrospective management unit 7, a trace target database 8, a container / content database 9, and a route database 10 are servers connected to clients via a communication network such as the Internet. Also good.

  The input unit 1 provides the user S with a screen for inputting information and a communication interface. On the other hand, the input information made by the user S is acquired, and the input information is output to the control unit 3. The input unit 1 further includes, for example, an input device such as a two-dimensional or three-dimensional barcode, an IC tag, an interface, a mobile phone, and an IC reader in addition to a mouse, a keyboard, and the like. May be entered. However, the present invention is not limited to these, and input may be made by any means.

  The output unit 2 acquires the information output from the control unit 3 and provides the acquired information to the user S via a screen or a communication interface.

  The control unit 3 acquires the input information output from the input unit 1, and uses the input information according to the type and condition of the information, the trace target management unit 4, the container / content management unit 5, and the route information management unit 6. , And distribute to any one of the route retrospective management unit 7. In addition, information output from the trace target management unit 4, the container / content management unit 5, the route information management unit 6, and the route retroactive management unit 7 is acquired, and this information is traced according to the type and condition of the information. The management unit 4, the container / content management unit 5, the route information management unit 6, and the route retroactive management unit 7 are allocated to the processing unit, and the processing is continued or output to the output unit 2.

  The trace target management unit 4 includes information on a target to be traced input by the user S, for example, trace target classification information (content or container type information), trace target classification specific information (content product name) , Information such as container name of the container), information according to the specification for each trace target category (content or container information including an identifier such as a product lot number) is acquired from the control unit 3. Then, a unique identifier is assigned according to the type and state of such information, and attribute information is registered, referred to, updated, and deleted from the trace target database 8. Then, a return value for displaying the registration in the trace target database 8 and the registration search result in the trace target database 8 to the user S is output to the control unit 3.

  The trace target management unit 4 executes such processing and obtains an output result, as shown in FIG. 2, the trace target registration management control unit 41, the trace target class registration management unit 42, the trace target class specific specification. A registration management unit 43, a trace target registration management unit 44, and a trace target database control unit 45 are provided.

  The trace target registration management control unit 41 receives the input information from the user S according to the type and state thereof, the trace target classification registration management unit 42, the trace target classification-specific detail registration management unit 43, and the trace target registration management unit 44. To any one of the above. On the other hand, the processing results output from the trace target category registration management unit 42, the trace target category-specific detail registration management unit 43, and the trace target registration management unit 44 are acquired and output to the control unit 3.

  Based on the processing result of the tracing object registration management control unit 41, the tracing object classification registration managing unit 42 performs any one of registration, reference, update, and deletion processing with respect to the tracing object database 8, and registers the processing result as the tracing object. Output to the management control unit 41. That is, in the case of registration, a unique identifier is assigned to the sorted trace target classification information and registered in the trace target database 8 via the trace target database control unit 45. In the case of reference, the trace target database 8 is searched through the trace target database control unit 45 using the unique identifier as a key, and the matching attribute information is referred to. In the case of update, the trace target database 8 is searched through the trace target database control unit 45 using the unique identifier of the sorted trace target classification information as a key, and the matching attribute information is transferred. Overwrite the traced classification information. In the case of deletion, the trace target database 8 is searched through the trace target database control unit 45 using the unique identifier of the sorted trace target classification information as a key, and the matching attribute information is obtained as the trace target database control unit. The data is deleted from the trace target database 8 via 45. The trace target classification registration management unit 42 outputs the processing result to the trace target registration management control unit 41 after the end of these processes.

  The trace target category detail registration management unit 43 replaces the part described as "trace target category information" with "trace target category specific information" in the description of the trace target category registration management unit 42. This is the same as the description of the processing of the trace target category registration management unit 42. However, in addition to the unique identifier of the trace target category given by the trace target category registration management unit 42, a unique identifier for the details detailing this category is defined.

  The trace target registration management unit 44 is a trace target class registration management unit in the case where the part described as “trace target classification information” is replaced with “trace target information” in the description of the trace target class registration management unit 42. This is the same as the description of the process 42. However, it refers to the unique identifier of the trace target classification details given by the trace target classification detail registration management unit 43, and indicates what kind of classification or detail the item registered as the trace target.

  The trace target database control unit 45 obtains the search conditions for the trace target database 8 from the trace target category registration management unit 42, the trace target classification detail registration management unit 43, and the trace target registration management unit 44, and trace target database 8 is accessed. Then, the result of the processing performed using the acquired search condition or the like is obtained as the search condition acquisition source of the trace target class registration management unit 42, the trace target class-specific detail registration management unit 43, and the trace target registration management unit 44. Return to site.

  Of the information output from the control unit 3, the container / content management unit 5 sets the container role setting information for the trace target, the content role setting information for the trace target, and the nesting relationship of the trace target (content storage for the container) Any of the information on the relationship) is set as input information. Then, in accordance with the type, state, and condition of the input information, the trace target database 8 or the container / content database 9 is accessed to perform registration, reference, editing, and deletion.

  Specifically, a unique identifier for identifying the role of the container is set for the trace target, the container / content database 9 is accessed, and attribute information is registered, referred to, edited, and deleted. Also, a unique identifier for identifying the role of the content is set for the trace target, the container / content database 9 is accessed, and the attribute information is registered, referenced, edited, and deleted. Also, a unique identifier for identifying the nesting relationship of the trace target is set, the container / content database 9 is accessed, and registration, reference, and editing of the combination of the target as the role of the container and the target as the role of the content , And delete. Then, a registration value in the container / content database 9 and a return value for displaying the registration search result in the container / content database 9 to the user S are output to the control unit 3.

  The container / content management unit 5 executes such processing and obtains an output result, as shown in FIG. 3, the container / content management control unit 51, the container setting management unit 52, the content setting management unit 53, A container / content mapping management unit 54 and a trace / container / content database control unit 55 are provided.

  The container / content management control unit 51 receives input information from the user S as one of the container setting management unit 52, the content setting management unit 53, and the container / content mapping management unit 54 according to the type and state of the input information. Sort out. Conversely, the processing results output from the container setting management unit 52, the content setting management unit 53, and the container / content mapping management unit 54 are acquired and output to the control unit 3.

  Based on the processing result of the container / content management control unit 51, the container setting management unit 52 performs any one of registration, reference, update, and deletion for the trace target database 8 or the container / content database 9. Is output to the container / content management control unit 51. That is, in the case of registration, a unique identifier is assigned to the distributed container information and registered in the container / content database 9 via the container / content database control unit 55. In the case of reference, the container / content database 9 or the trace target database 8 is searched through the container / content database control unit 55 using the unique identifier as a key, and the matching attribute information is referred to. In the case of updating, the container / content database 9 is searched through the container / content database control unit 55 using the unique identifier of the distributed container information as a key, and the distributed container is searched for the matching attribute information. Overwrite information. In the case of deletion, the container / content database 9 is searched through the container / content database control section 55 using the unique identifier of the distributed container information as a key, and the matching attribute information is obtained from the container / content database control section. It is deleted from the container / content database 9 via 55. The container setting management unit 52 outputs the processing result to the container / content management control unit 51 after the end of these processes.

  The content setting management unit 53 is the same as the description of the processing of the container setting management unit 52 when the portion described as “container information” in the description of the container setting management unit 52 is replaced with “content information”. .

  In the description of the container setting management unit 52, the container / content mapping management unit 54 explains the processing of the container setting management unit 52 when the portion described as “container information” is replaced with “container / content information”. It is the same.

  The trace target / container / content database control unit 55 acquires search conditions for the trace target database 8 or the container / content database 9 from the container setting management unit 52, the content setting management unit 53, and the container / content mapping management unit 54. Then, the trace object database 8 or the container content database 9 is accessed. Then, the result of the accessed processing is returned to the part from which the search condition is acquired in the container setting management unit 52, the content setting management unit 53, and the container / content mapping management unit 54.

  The route information management unit 6 selects one of the information output from the control unit 3 from the schedule of the route to be traced regarding the route to be traced, the history of the route to be traced and the inquiry about the current state of the target to be traced. Input information. Then, the trace target database 8 or the route database 10 is accessed according to the type, state, and condition of the input information, and registration, reference, editing, and deletion are performed.

  Specifically, a unique identifier for identifying the schedule of the transportation route to be traced is set, the route database 10 is accessed, registration and reference of attribute information (combination of departure / arrival date / time and location), reference, Edit and delete. Also, a unique identifier for identifying the actual track of the route to be traced is set, the route database 10 is accessed, and attribute information (combination of departure / arrival date / time and location) is registered in the route database 10. Browse, edit, and delete. In addition, the current position and the nesting state are generated from the track record information of the transportation route to be traced. Then, a return value for displaying the results of these processes to the user S is output to the control unit 3.

  The route information management unit 6 executes such processing and obtains an output result, as shown in FIG. 4, the route information management control unit 61, the planned route registration management unit 62, the actual route registration management unit 63, A current management unit 64 and a trace target and path database control unit 65 are provided.

  The route information management control unit 61 distributes the input information from the user S to any one of the planned route registration management unit 62, the actual route registration management unit 63, and the current management unit 64 according to the type and state. . Conversely, the processing results output from the planned route registration management unit 62, the actual route registration management unit 63, and the current management unit 64 are acquired and output to the control unit 3.

  Based on the processing result of the route information management control unit 61, the planned route registration management unit 62 performs any one of registration, reference, update, and deletion processing with respect to the trace target database 8 or the route database 10, and the processing result is routed. The information is output to the information management control unit 61. That is, in the case of registration, a unique identifier is assigned to the information on the scheduled transportation route, and the information is registered in the route database 10 via the trace target and route database control unit 65. In the case of reference, the trace target database 8 or the route database 10 is searched via the trace target and route database control unit 65 using the unique identifier as a key, and the information on the scheduled transportation route is output. In the case of update, the route database 10 is searched through the trace target and route database control unit 65 using the unique identifier of the sorted route information as a key, and the matching route information is searched for. , Overwrite the sorted route information. In the case of deletion, the route database 10 is searched through the trace target and route database control unit 65 using the unique identifier of the sorted route information as a key, and the information on the matched route route is traced. And deleted from the route database 10 via the route database control unit 65. The planned route registration management unit 62 outputs the processing result to the route information management control unit 61 after the completion of these processes.

  The actual route registration management unit 63 in the description of the planned route registration management unit 62 is the planned route registration management unit 62 when the portion described as “transport route plan information” is replaced with “transport route result information”. This is the same as the description of the process.

  Based on the processing result of the route information management control unit 61, the current management unit 64 searches the route database 10 via the trace target and route database control unit 65 for the distributed current date and time information, and sets the trace target. And the nesting relationship information between the container and the content are generated, and the generation result is output to the route information management control unit 61.

  The trace target and route database control unit 65 acquires the search conditions for the trace target database 8 or the route database 10 from the planned route registration management unit 62, the actual route registration management unit 63, and the current management unit 64, and the trace target database. 8 or the route database 10 is accessed. Then, the result of the processing performed by accessing is returned to the part of the planned route registration management unit 62, the actual route registration management unit 63, and the current management unit 64, which is the acquisition source of search conditions and the like.

  The route retrospective management unit 7 matches the retroactive condition by inputting the retroactive condition including the trace target, the period, the range, etc. regarding the nesting relation of the transport route and container etc. of the trace target among the information output from the control unit 3. Information to be extracted from the trace target database 8, the container content database 9, and the route database 10, and the route information matching the conditions and the information regarding the change in the nesting state of the container are generated, and the generated information is sent to the control unit 3. Output.

  In order to execute such processing, the route retroactive management unit 7 performs a route retroactive management control unit 71, a route retroactive condition setting management unit 72, a route retroactive management unit 73, and a route generation management unit 74 as shown in FIG. And a tracing target / container content / database control unit 75.

  The route retrospective management control unit 71 converts the input information from the user S to any one of the route retroactive condition setting management unit 72, the route retrospective management unit 73, and the route generation management unit 74 according to the type and state. Distribute. Conversely, the processing results output from the route retroactive condition setting management unit 72, the route retroactive management unit 73, and the route generation management unit 74 are acquired and output to the control unit 3.

  The route retroactive condition setting management unit 72 checks the retroactive condition input from the user S based on the processing result of the route retrospective management control unit 71, and sets the trace target / container content / database control unit 75 as necessary. Then, the condition is supplemented from the trace target database 8, and the result of whether the retroactive condition is appropriate is returned to the route retroactive management control unit 71.

  Based on the processing result of the route retrospective management control unit 71, the route retrospective management unit 73 receives a trace target transport route record that matches the retroactive conditions input from the user S and determined to be valid by the route retroactive condition setting management unit 72. Container nesting information is extracted from the container / content database 9 and the route database 10 via the trace target / container content / database control unit 75, and the result is returned to the route retrospective management control unit 71.

  The route generation management unit 74 matches the retroactive conditions input from the user S based on the processing result of the route retrospective management control unit 71, and information on the transportation route results and the container nesting relation extracted by the route retrospective management unit 73. To generate route information and return the result to the route retrospective management control unit 71.

  The trace target / container content / database control unit 75 includes the trace target database 8, the container content database 9, and the route database 10 from the route retroactive condition setting management unit 72, the route retrospective management unit 73, and the route generation management unit 74. Get the search condition for and access the corresponding database. Then, the result of the accessed processing is returned to the part from which the search condition is acquired, among the route retroactive condition setting management unit 72, the route retroactive management unit 73, and the route generation management unit 74.

  The trace target database 8 includes trace target classification information (type information such as contents and containers), detailed information for each trace target classification (information such as the product name and container name of the content), and trace target classification information. FIG. 12 is a database in which information according to details (product information including an identifier such as a product lot number of content) is stored. As an example, a master by type shown in FIG. 12 to be described later, a master details by type shown in FIG. The trace target master shown in FIG. 15, the trace target content shown in FIG. 15, and the trace target container shown in FIG. 16 are included.

  The container / content database 9 is a database in which trace target information to be regarded as a container, trace target information to be regarded as content, and container / content map information indicating a nesting relationship between the container and the content are stored. As an example, FIG. Contains the traced container / content map shown.

  The route database 10 is a database in which the combination information of the departure and arrival planned location and time to be traced and the combination information of the departure and arrival actual place and time are accumulated. As an example, the planned delivery data shown in FIG. 19, delivery schedule details shown in FIG. 19, delivery record data shown in FIG. 20, delivery record details shown in FIG. 21, and base master shown in FIG.

  Next, the operation of the traceability support apparatus according to the embodiment configured as described above will be described.

  FIG. 6 is a flowchart showing the distribution of the input information performed by the control unit 3 and the operation in which the processing result for the distributed input information is returned to the control unit 3.

  When input information is input to the input unit 1 by the user S (S1), the input information is output to the control unit 3. The control unit 3 traces the trace target management unit 4 according to the type and condition of the input information. , It is distributed to any one of the container / content management unit 5, the route information management unit 6, and the route retroactive management unit 7 (S2).

  For example, if the input information is related to the trace target registration, the input information is distributed to the trace target management unit 4, processed in the trace target management unit 4, and the processing result is returned to the control unit 3 (S3).

  If the input information is related to container / content management, the input information is distributed to the container / content management unit 5, processed in the container / content management unit 5, and the processing result is returned to the control unit 3 ( S4).

  If the input information is related to the route information management, the input information is distributed to the route information management unit 6, processed in the route information management unit 6, and the processing result is returned to the control unit 3 (S5).

  If the input information is related to the route retroactive management, the information is distributed to the route information management unit 6, processed in the route information management unit 6, and the processing result is returned to the control unit 3 (S6).

  The processing results (S7) returned to the control unit 3 in steps S3 to S6 are output from the control unit 3 to the output unit 2 and presented to the user S (S8).

  After that, if there is an input by the user S (S9: Yes), the process returns to step S1, and if there is no input (S9: No), the process ends.

  Next, details of the processing in step S3 will be described with reference to the flowchart shown in FIG.

  The input information related to the trace target registration distributed to the trace target management unit 4 is acquired by the trace target registration management control unit 41 (S301). Then, the trace target registration management control unit 41 distributes this information (S302). When this information is information related to the trace target classification, this information is processed by the trace target class registration management unit 42 (S303). If the information is related to the trace target category-specific details, the trace target category-specific details registration management unit 43 processes the information (S304). If the information is related to the trace target, this information is processed by the trace target registration management unit 44 (S305). Then, the processing results performed in steps S303 to S305 are output to the trace target database control unit 45 (S306).

  And when the processing result with the access to the trace object database 8 is output to the trace object database control unit 45 (S307: Yes), the process result is used by the trace object database control unit 45, Processing is performed on the trace target database 8 (S308), and thereafter, the process returns to any one of steps S303 to S305.

  On the other hand, when it is not a processing result with access to the trace target database 8 (S307: No), and there is output data to the trace target registration management unit 44 in the processing result output in step S305. In (S309: Yes), the trace target registration management unit 44 outputs data (S310), and then returns to any one of steps S303 to S305.

  In step S309, when there is no output data to the trace target registration management unit 44 (S309: No), and when the data acquisition by the trace target registration management unit 44 is continuously performed (S311: Yes), Returning to step S301, if the process is not continued (S311: No), the process ends.

  Next, details of the processing in step S4 will be described using the flowchart shown in FIG.

  The container / content management related input information distributed to the container / content management unit 5 is acquired by the container / content management control unit 51 (S401). The container / content management control unit 51 distributes the information (S402). When this information is information related to the container setting, this information is processed by the container setting management unit 52 (S403). If the information is related to content setting, it is processed by the content setting management unit 53 (S404). If the information is related to container / content mapping, this information is processed by the container / content mapping manager 54 (S405). The processing results obtained in steps S403 to S405 are output to the tracing target and container / content database control unit 55 (S406).

  When a processing result with access to the trace target database 8 is output to the trace target and container / content database control unit 55 (S407: Yes), the trace target and container / content database control unit 55 The processing result is used to perform processing on the trace target database 8 (S408), and then the process returns to any one of steps S403 to S405.

  On the other hand, when it is not a processing result with access to the trace target database 8 (S407: No) and a processing result with access to the container / content database 9 is output (S409: Yes), The processing result is used by the tracing target and container / content database control unit 55 to perform processing using the container / content database 9 (S410), and then any one of steps S403 to S405 is performed. Return to.

  In step S409, when there is no access to the container / content database 9 (S409: No) and there is output data to the container / content management control unit 51 (S411: Yes), the container Data is output by the content management control unit 51 (S412), and thereafter, the process returns to any one of steps S403 to S405.

  In step S411, there is no output data to the container / content management control unit 51 (S411: No), and data acquisition by the container / content management control unit 51 is continued (S413: Yes). ), The process returns to step S401, and if it is not continued (S413: No), the process ends.

  Next, details of the processing in step S5 will be described with reference to the flowchart shown in FIG.

  The route information management-related input information distributed to the route information management unit 6 is acquired by the route information management control unit 61 (S501). Then, the route information management control unit 61 distributes this information (S502). If this information is information related to the planned route, this information is processed by the planned route registration management unit 62 (S503). If the information is related to the actual route, the actual route registration management unit 63 processes the information (S504). If the information is related to the current state, this information is processed by the current management unit 64 (S505). Then, the processing results performed in steps S503 to S505 are output to the trace target and path database control unit 65 (S506).

  Then, when the processing result with access to the trace target database 8 is output to the trace target and route database control unit 65 (S507: Yes), the trace target and route database control unit 65 displays the processing result. The processing is performed on the trace target database 8 (S508), and thereafter, the process returns to any one of steps S503 to S505.

  On the other hand, if the processing result with access to the trace database 8 is not the result of processing (S507: No), and the processing result with access to the route database 10 is output (S509: Yes), the trace target Then, the route database control unit 65 uses this processing result to perform processing on the route database 10 (S510), and then returns to any one of steps S503 to S505.

  In step S509, when there is no access to the route database 10 (S509: No) and there is output data to the route information management control unit 61 (S511: Yes), the route information management control unit. 61 is output (S512), and thereafter, the process returns to any one of steps S503 to S505.

  In step S511, when there is no output data to the route information management control unit 61 (S511: No), and the data acquisition by the route information management control unit 61 is continuously performed (S513: Yes). Returns to step S501, and when it is not continued (S513: No), the process ends.

  Next, details of the processing in step S6 will be described using the flowchart shown in FIG.

  The route retrospective management related input information distributed to the route retroactive management unit 7 is acquired by the route retroactive management control unit 71 (S601). Then, the route retrospective management control unit 71 distributes this information (S602). When this information is information related to the route retroactive condition, this information is processed by the route retroactive condition setting management unit 72 (S603). If the information is related to the route retroactive, the route retroactive management unit 73 processes the information (S604). If the information is related to route generation, this information is processed by the route generation management unit 74 (S605). The processing results obtained in steps S603 to S605 are output to the trace target / container content / path database control unit 75 (S606).

  When the processing result with access to the trace target database 8 is output to the trace target / container content / route database control unit 75 (S607: Yes), the trace target / container content / route database control is performed. The processing result is used by the unit 75 to process the trace target database 8 (S608), and thereafter, the process returns to any one of steps S603 to S605.

  On the other hand, when the processing result with access to the database 8 to be traced is not a processing result (S607: No) and the processing result with access to the container / content database 9 is output (S609: Yes), The processing result is used by the tracing target / container content / route database control unit 75 to perform processing on the container content database 9 (S610), and then any one of steps S603 to S506 is performed. Return to.

  On the other hand, if the processing result with access to the container / content database 9 is not the processing result (S609: No), and the processing result with access to the route database 10 is output (S611: Yes), the trace is performed. The target / container content / route database controller 75 uses this processing result to perform processing on the route database 10 (S612), and then returns to any one of steps S603 to S605.

  In step S611, when there is no access to the route database 10 (S611: No) and there is output data to the route retrospective management control unit 71 (S613: Yes), the route retrospective management control unit. 71 is output (S614), and then the process returns to any one of steps S603 to S605.

  In step S613, when there is no output data to the route retrospective management control unit 71 (S613: No), and when the data acquisition by the route retrospective management control unit 71 is continuously performed (S615: Yes). Returns to step S601, and if not continued (S615: No), the process ends.

  Next, an example of specific data stored in the trace target database 8, the container / content database 9, and the route database 10 will be described.

  For example, consider a distribution process as shown in FIG. In this distribution process, the products A-1 to A-4 are transported from the point K, which is the starting point, to the point M, which is the arrival point, via the point L. At point K, the products A-1 and A-2 are stored in the container B-1, while the products A-3 and A-4 are stored in the container B-2 and are transported to the point L together. . At the point L, the container B-1 storing the products A-1 and A-2 and the container B-2 storing the products A-3 and A-4 are both stored in the container B-3. And from the point L to the point M, the products A-1 to A-4 are finally distributed to the point M by transporting the container B-3.

  12 to 16 are data stored in the trace target database 8, respectively. FIG. 12 is a master 81 by type, FIG. 13 is a master description 82 by type, FIG. 14 is a trace target master 83, and FIG. 15 is a trace target. Content 84 and FIG. 16 show examples of the data structure of the trace target container 85, respectively.

  As shown in FIG. 12, the type-specific master 81 includes a type-specific master ID 81a and a type-specific master name 81b. In the type-specific master 81, the product A and the container B are defined. Although not used in the distribution process of FIG. 11, the cart C and the bag D are also defined. Therefore, not only the container B but also the cart C and the bag D are used as storage means for the product A. It is possible to respond.

  As shown in FIG. 13, the type-specific master description 82 includes a type-specific master ID 82a, a type-specific master specification ID 82b, a type-specific master specification name 82c, a type-specific master start date 82d, and a type-specific master end date 82e. Consists of. The type-specific master ID 82a exists for each type-specific master specification ID 82b. The master-specific ID 82b for each type covers all items distributed including the product A and the container B. Therefore, in the case of a distribution process as shown in FIG. 11, the products A-1 to A-4 and the containers B-1 to B-3 are applicable. The master ID 82a for each type of the products A-1 to A-4 is A, and the master ID 82a for each type of the containers B-1 to B-3 is B. The master-specific name 82c by type is a name that can be arbitrarily set for the corresponding master-specific ID 82b by type. Here, “Product 1” is set as the type-specific master specification name 82c of the product A-1, and “S container 1” is set as the container B-1. The type-specific master start date 82d and the type-specific master end date 82e are a use start date and a use end date of the type-specific master details 82, respectively.

  As shown in FIG. 14, the trace target master 83 includes a trace target ID 83a, a start date 83b, an end date 83c, a type master 83d, and a type master detail ID 83e. The type-specific master 83d and the type-specific master specification ID 83e correspond to the type-specific master ID 82a and the type-specific master specification ID 82b. The trace target ID 83a is an identifier uniquely assigned to each type-specific master specification ID 83e. The start date 83b and the end date 83c are a use start date and a use end date of the trace target master 83, respectively.

  As shown in FIG. 15, the trace target content 84 includes a content ID 84a, a trace target ID 84b, a start date 84c, and an end date 84d. The trace target ID 84b corresponds to all the trace target IDs 83a stored. The containers B-1 and B-2 are stored in the container B-3, but the container B-3 is not stored in any container. Therefore, the tracing target ID 84b is O- corresponding to the products A-1 to A-4. 1 to O-4 and O-5 and O-6 corresponding to the containers B-1 and B-2 are targeted. The content ID 84a is an identifier uniquely assigned to each of the trace target IDs 84b. The start date 84c and the end date 84d are a use start date and a use end date of the trace target content 84, respectively.

  As shown in FIG. 16, the trace target container 85 includes a container ID 85a, a trace target ID 85b, a start date 85c, and an end date 85d. The trace target ID 85b corresponds to the trace target ID 83a whose type-specific master 83d is B. The container ID 85a is an identifier uniquely assigned to each trace target ID 85b. The start date 85c and the end date 85d are a use start date and a use end date of the trace target container 85, respectively.

  FIG. 17 shows an example of the data structure of a trace target container / content map 91 which is data stored in the container / content database 9. As shown in FIG. 17, the trace target container / content map 91 includes a container / content ID 91a, a trace target ID (# 1) 91b, a trace target ID (# 2) 91c, a start date 91d, and an end date 91e. It consists of. The trace target ID (# 1) 91b corresponds to the trace target ID 85b, and the trace target ID (# 2) 91c corresponds to the trace target ID 84b. The nesting relationship between the container B and the product A is defined by a combination of the trace target ID (# 1) 91b and the trace target ID (# 2) 91c. For example, the CCM-1 of the container content ID 91a that is an identifier uniquely assigned to the combination of the trace target ID (# 1) 91b and the trace target ID (# 2) 91c is the trace target ID (# 1). ) 91-1 indicates that O-1 of the trace target ID (# 2) 91c is stored in O-5 of 91b. The start date 91d and the end date 91e are a use start date and a use end date of the trace target container / content map 91, respectively.

  18 to 22 are data stored in the route database 10, respectively. FIG. 18 shows delivery schedule data 101, FIG. 19 shows delivery schedule details 102, FIG. 20 shows delivery record data 103, and FIG. FIG. 22 shows an example of the data structure of the site master 105.

  As shown in FIG. 18, the delivery schedule data 101 includes a delivery schedule ID 101a, a trace target ID 101b, a carry-out source ID 101c, a carry-out scheduled date 101d, a final arrival destination ID 101e, and an arrival completion scheduled date 101f. The trace target ID 101b corresponds to the trace target ID 84b, and the delivery schedule ID 101a is an identifier uniquely assigned to each of the trace target ID 101b. The carry-out source ID 101c indicates the point K that is the departure point, and the carry-out scheduled date 101d is the scheduled departure date of the point K. The final destination ID 101e indicates a point M that is an arrival point, and the arrival completion scheduled date 101f is a scheduled arrival date at the point M.

  As shown in FIG. 19, a delivery schedule detail 102 includes a delivery schedule detail ID 102a, a delivery schedule ID 102b, a trace target ID 102c, a carry-out source ID 102d, a carry-out planned date 102e, an arrival destination ID 102f, and a planned arrival date 102g. Consists of. The delivery schedule ID 102b corresponds to the delivery schedule ID 101a, and the trace target ID 102c corresponds to the trace target ID 101b. Further, the carry-out source ID 102d is the starting point K, and the carry-out scheduled date 102e may be configured to correspond to the planned carry-out date 101d in principle, but the information on the scheduled delivery details shown in FIG. Since it is necessary to show more detailed information than the delivery schedule shown in (2), the two do not have to correspond. The destination ID 102f is a point where the state changes next, and is not necessarily an arrival point. The product A-1 whose tracing target ID 102c is O-1 is stored in the container B-1 and leaves the point K. At the point L, the container B-1 becomes a larger container B-3 and others. The state changes by being stored together with the container B-2. Accordingly, the destination ID 102f is the point L, and the scheduled arrival date 102g is the scheduled date of arrival at the point L. Delivery schedule details ID102a from ED-1 to ED-4 are delivery schedule details from point K to point L, and ED-5 to ED-8 indicate delivery schedule details from point L to point M. ing.

  As shown in FIG. 20, the delivery record data 103 includes a delivery record ID 103a, a trace target ID 103b, a carry-out source ID 103c, a carry-out completion date 103d, a final arrival destination ID 103e, and an arrival completion date 103f. The trace target ID 103b corresponds to the trace target ID 101b, the carry-out source ID 103c corresponds to the carry-out source ID 101c, and the carry-out completion date 103d corresponds to the planned carry-out date 101d. The final destination ID 103e corresponds to the point M that is the arrival point to be traced. The arrival completion date 103f is written with the date when the corresponding trace target ID 103b arrives at the final destination. The delivery record ID 103a is an identifier that is uniquely assigned to each trace target ID 103b that has been delivered.

  As shown in FIG. 21, the delivery record details 104 include a delivery record detail ID 104a, a delivery record ID 104b, a trace target ID 104c, a carry-out source ID 104d, a carry-out completion date 104e, an arrival destination ID 104f, and an arrival date 104g. Become. The delivery record item 104 is also written when delivery to the final destination to be traced is completed. The delivery result ID 104b, the trace target ID 104c, the carry-out source ID 104d, and the carry-out completion date 104e may be configured to correspond to the principle delivery result ID 103a, the trace target ID 103b, the carry-out source ID 103c, and the carry-out completion date 103d, respectively. Since it is necessary for the information of the delivery record details shown in 21 to indicate more detailed information than the delivery record shown in FIG. 20, it is not necessary to correspond to each. The destination ID 104f is a point where the state changes next, and is not necessarily an arrival point. The product A-1 whose tracing target ID 102c is O-1 is stored in the container B-1 and leaves the point K. At the point L, the container B-1 becomes a larger container B-3 and others. The state changes by being stored together with the container B-2. Therefore, the destination ID 104f is the point L, and the arrival date 104g is the date of arrival at the point L. The delivery record detail ID 104a is an identifier uniquely assigned to each delivery record ID 104b.

  As shown in FIG. 22, the site master 105 includes a site ID 105a, a site name 105b, a site type 105c, a site address 105d, a site contact 105e, a site start date 105f, and a site end date 105g. . The base ID 105a corresponds to a starting point, an arriving point in the distribution process, and a point where the state of the product A changes, as in the points K, L, and M. The site name 105b is the name of each site, the site type 105c is additional information for each site, the site address 105d is the address of the site, the site contact 105e is a telephone number, the site start date 105f is the date when the site is valid, The base end date 105g is a date when the base is invalidated. TD-1 to TD-4 of the delivery record details ID 104a are scheduled delivery details from point K to point L, and TD-5 to TD-8 are scheduled delivery details from point L to point M. .

  By using such data, a route retroactive example in which the route through which the product A-1 has passed will be described. This retroactive processing is performed by the route retroactive management unit 7.

  First, from the trace target master 83 stored in the trace target database 8, O-1 having the type-specific master detail ID 83e of A-1 as the trace target ID 83a is acquired.

  Next, the trace target ID 104c corresponding to O-1 is referred to from the delivery record details 104 stored in the route database 10. The corresponding delivery record details ID 104a are TD-1 and TD-5. Thereby, the product A-1 departs from the point K on September 3, arrives at the point L on September 4, further departs from the point L on September 4, and the point M on September 5 You can see that it has arrived.

  Next, from the trace target container / content map 91 stored in the container / content database 9, all the container / content relationships in which the trace target ID is related to O-1 can be repeated. This process will be described with reference to FIG. The data written in FIG. 23 is the same as the data written in FIG. First, as shown in the container content ID 91a CCM-1, O-1 exists as the trace target ID (# 2) 91c. At this time, since the trace target ID (# 1) 91b is O-5 (1), it can be seen that O-1 was stored in O-5 from September 1 to September 5. Next, as indicated by the container content ID 91a CCM-5, O-5 exists as the trace target ID (# 2) 91c (2). At this time, since the tracing target ID (# 1) 91b is O-7 (3), it can be seen that O-5 was stored in O-7 from September 1 to September 5.

  From the tracing target master 83 and the type-specific master description 82 stored in the tracing target database 8, it can be seen that O-5 is the S container B-1 and O-7 is the L container B-3.

  From the above, the product A-1 is in the container B-1 from September 1 to September 5, and in particular, from September 3 to September 5, the container B- 3, it can be seen that it is in the container B-1. Summarizing the period overlap, product A-1 is in container B-1 from September 1 to September 3, and from September 3 to September 5. Although it is in container B-3, it turns out that it was in container B-1.

  As described above, in the traceability support apparatus according to the embodiment, the nesting relationship between the content and the container (the content is put into and taken out from the container) can be freely set by the above-described operation. In this way, since the nesting relationship between the content and the container is defined and the packaging state of the content and the information on the transportation route are registered and managed, the distribution route information and the packaging state information can be traced simultaneously. Therefore, it is possible not only to trace what packaging state is in the middle of distribution, but also to trace both the packaging state change and the route information change. Even if a container is specified, changes in packing status and route information can be traced.

  Furthermore, it is possible not only to cope with a change in packing or distribution form in the middle, but also to trace changes in the packing state and route information even when the content is decomposed in the middle. In addition, even when transporting in a complicated form, it is possible to cope with traceability by newly defining information to be managed as appropriate.

  As described above, the traceability support apparatus according to the embodiment can trace the product in the distribution process in a general-purpose manner including not only the product itself but also the packaging state thereof.

(Example)
Here, more specific examples of data structures of the trace target database 8, the container content database 9, and the route database 10 and examples of behavior in container content mapping performed by the container content management unit 5 will be described more specifically. explain.

  FIG. 24 is a diagram showing the interrelationship between the type-specific master 81, the type-specific master description 82, and the trace target master 83 stored in the trace target database 8. First, the trace target master 83 is defined so as to have a one-to-one relationship with the content, and then the type-specific master 81 is defined in anticipation that the type of the trace target is added to other than the content and the container. The type-specific master details 82 have attributes of only the type-specific master details name 82c, the type-specific master details start date 82d, and the type-specific master details end date 82e.

  FIG. 25 shows the mutual relationship between the trace target container / content map 91 stored in the container / content database 9, the trace target master 83, the trace target content 84, and the trace target container 85 stored in the trace target database 8. It is a figure which shows a relationship.

  FIG. 26 shows delivery schedule data 101, delivery schedule details 102, delivery record data 103, delivery record details 104 and site master 105 stored in the route database 10, and a trace target master stored in the trace target database 8. FIG.

  FIG. 27 is a diagram showing an example of the functional structure of the container / content mapping management unit 54 in the container / content management unit 5. Here, the structure of a program for realizing container / content mapping management is represented by a UML (Unified Modeling Language) class diagram, rectangles 270 to 274 represent classes, and relationships between classes are represented by straight lines. ing. The class is divided into two parts. The upper parts 270a, 271a, 273a, and 274a indicate class names and class types, and the lower parts 270b, 271b, 273b, and 274b indicate operations owned by the classes. The class type is enclosed in "<<" and describes the set name into which the class is classified according to the notation called stereotype in UML.

  FIG. 27 shows that there are two types of classes: << Kernel >> (basic part) and << Optional >> (variable part). A white triangle 275 indicates that an inheritance relationship is established from the triangle 275 to a plurality of related classes, with the class of the portion in contact with the triangle 275 as a parent. The inheritance relationship is that the class corresponding to the child inherits all the attributes and behavior of the class corresponding to the parent.

  In FIG. 27, the trace target content control class 272, the trace target container control class 273, and the container / content map control class 274 inherit all the properties of the trace target control class 270 that is the parent class. The white diamond 276 indicates that the class in which the diamond 276 is in contact holds the class associated with the diamond 276. In the example of FIG. 27, the container / content map control class 274 indicates that the trace target control class 270 is owned. The trace target control class 270 is a parent class of the trace target content control class 272, the trace target container control class 273, and the container / content map control class 274. The container / content map control class 274 is traced by a recursive nesting relationship. Indicates that the target content, the trace target container, and the content put in the container can be controlled recursively.

  FIG. 27 shows that the trace target control class 270 has behaviors (functions) for registration, search, update, deletion, content addition, content deletion, and content acquisition. The trace target content control class 272, the trace target container control class 273, and the container / content map control class 274 are provided with the above behavior inherited from the trace target control class 270 that is the parent class, and are specific to each of the classes 272 to 274. This behavior is implemented by adding to the behavior inherited from the parent class 270.

  FIG. 28 shows an example of the behavior when registering a container and content in the functional structure of the container / content mapping management unit 54. FIG. 28 shows an example of the interaction in the program structure for realizing the container / content mapping management shown in FIG. 27 by a UML sequence diagram. If the user S requests registration of the product (content) A-1, an A-1 object is generated and registered in the trace target database 8 via the entity 271 (S280). Thereafter, the registration result is returned to the user S side (S281). Similarly, when there is a request for registration of the product (content) A-2 from the user S, an A-2 object is generated and registered in the trace target database 8 via the entity 271 (S282). The result is returned to the user S side (S283). Similarly, when there is a request for registration of the container (container) B-1 from the user S, a B-1 object is generated and registered in the trace target database 8 via the entity 271 (S284). The result is returned to the user S side (S285).

  FIG. 29 shows an example of behavior when content is put in a container in the functional structure of the container / content mapping management unit 54.

  FIG. 30 shows an example of behavior when searching for content in the functional structure of the container / content mapping management unit 54. FIG. 30 shows an example of the interaction in the program structure for realizing the container / content mapping management shown in FIG. 27 by a UML sequence diagram.

  First, when the user S makes a request to acquire content (S300), this request is sent to the container / content management unit 5. Then, the content is searched from the trace target database 8 by the container / content management unit 5 via the entity 271 (S301). In response to this, content nesting relation information is returned from the trace target database 8 (S302). Here, when such behavior is executed after the execution result of FIG. 29 is completed, information containing the contents A-1 and A-2 is returned to the container B-1.

  Next, when the user S makes a request for searching for specific content, for example, the content A- 1 (S 303), the search request is sent to the container / content management unit 5. Then, the content A-1 is retrieved from the trace target database 8 by the container / content management unit 5 via the entity 271 (S304). In response to this, content nesting relation information is returned from the trace target database 8 (S305). Here, when such behavior is executed after the execution result of FIG. 29 is completed, information that the content A-1 is contained in the container B-1 is returned.

  The best mode for carrying out the present invention has been described above with reference to the accompanying drawings, but the present invention is not limited to such a configuration. Within the scope of the invented technical idea of the scope of claims, a person skilled in the art can conceive of various changes and modifications. The technical scope of the present invention is also applicable to these changes and modifications. It is understood that it belongs to.

The functional block diagram which shows the structural example of the traceability assistance apparatus which concerns on embodiment of this invention. The functional block diagram which shows the detailed structural example of a trace object management part. The functional block diagram which shows the detailed structural example of a container content management part. The functional block diagram which shows the detailed structural example of a route information management part. The functional block diagram which shows the detailed structural example of a route retroactive management part. The flowchart which shows the operation | movement which distributes the input information by a control part, and the process result made | formed with respect to input information is returned to a control part. The flowchart which shows the detail of a process of step S3. The flowchart which shows the detail of the process of step S4. The flowchart which shows the detail of a process of step S5. The flowchart which shows the detail of a process of step S6. The conceptual diagram which shows an example of a distribution process. The data structure figure which shows an example of the master classified by type. The data structure figure showing an example of master details classified by type. The data structure figure which shows an example of the master classified by trace. The data structure figure which shows an example of the content for a trace. The data structure figure which shows an example of a trace object container. The data structure figure which shows an example of a trace object container content map. The data structure figure which shows an example of delivery schedule data. The data structure figure which shows an example of a delivery schedule item. The data structure figure which shows an example of delivery performance data. The data structure figure which shows an example of a delivery track record. The data structure figure which shows an example of a base master. A container / content map to be traced for explaining an example of route retrospective. The figure which shows the mutual relationship of the master 81 classified by type stored in the trace object database 8, the master details 82 classified by type, and the trace object master 83. The figure which shows the correlation with the trace object container content map 91 stored in the container content database 9, and the trace object master 83, the trace object content 84, and the trace object container 85 stored in the trace object database 8. . The delivery schedule data 101, the delivery schedule details 102, the delivery record data 103, the delivery record details 104, and the site master 105 stored in the route database 10 and the trace target master 83 stored in the trace target database 8 are mutually connected. The figure which shows a relationship. The figure which shows the Example of the function structure of the container content mapping management part 54 in the container content management part 5. FIG. The figure which shows the Example of the behavior at the time of registering a container and a content in the functional structure of the container content mapping management part. The figure which shows the Example of the behavior at the time of putting a content in a container in the functional structure of the container content mapping management part 54. FIG. The figure which shows the Example of the behavior at the time of searching a content in the functional structure of the container content mapping management part.

Explanation of symbols

  A ... Product, B ... Container, C ... Dolly, D ... Bag, K ... Point, L ... Point, M ... Point, S ... User, 1 ... Input unit, 2 ... Output unit, 3 ... Control unit, 4 ... Trace Object management unit, 5 ... container / content management unit, 6 ... route information management unit, 7 ... route retroactive management unit, 8 ... trace target database, 9 ... container / content database, 10 ... route database, 41 ... trace target registration management Control unit 42 ... Trace target class registration management unit 43 ... Detail registration management unit by trace target category 44 ... Trace target registration management unit 45 ... Trace target database control unit 51 ... Container / content management control unit 52 ... Container setting management unit, 53 ... Content setting management unit, 54 ... Container / content mapping management unit, 55 ... Trace target and container / content database 61, route information management control unit, 62 ... planned route registration management unit, 63 ... actual route registration management unit, 64 ... current management unit, 65 ... trace target and route database control unit, 71 ... route retrospective management control 72: Route retroactive condition setting management unit, 73 ... Route retroactive management unit, 74 ... Route generation management unit, 75 ... Trace target / container content / route database control unit, 81 ... Master by type, 82 ... Master by type Detail, 83 ... Trace target master, 84 ... Trace target content, 85 ... Trace target container, 91 ... Trace target container / content map, 101 ... Delivery schedule data, 102 ... Delivery schedule details, 103 ... Delivery record data, 104 ... Delivery Actual result, 105 ... base master, 270 ... trace target control class, 271 ... entity 272 ... traced content control class, 273 ... traced container control class, 274 ... container content map control class

Claims (5)

A traceability support device that tracks and retroactively monitors the status of each stage of the distribution process of an object,
A first management means for managing a departure date of the object at a starting point in the distribution process and an arrival date at the arrival point in association with the object;
A second management unit that manages a departure date at the departure point and an arrival date at the arrival point of the storage unit that is distributed along the distribution process and stores the object in association with the storage unit; ,
The storage unit and the object stored in the storage unit are managed in association with each other, and when the storage unit stores another storage unit, the storage unit is further managed in association with the other storage unit. And a third management means. A traceability support apparatus comprising: The traceability support device according to claim 1,
The first management means attaches a unique identifier to each object, and attaches the departure date of the object at the starting point in the distribution process and the arrival date at the arrival point to the object. Using the first database associated with the identifier,
The second management means attaches a unique identifier to each storage means, and indicates the departure date of the storage means at the departure point and the arrival date at the arrival point of the storage means. In association with the first database,
The third management means manages the associated storage means and the object, or the associated storage means, using a second database associated with each identifier. Traceability support device. The traceability support apparatus according to claim 2,
The first and second management means are:
Registration means for registering the departure date and the arrival date in the first database;
Correction means for correcting the contents registered in the first database;
A reference means for referring to contents registered in the first database;
Deleting means for deleting any of the contents registered in the first database,
A traceability support apparatus, further comprising a tracking unit that tracks the state of the object or the storage unit based on the first database. The traceability support apparatus according to any one of claims 1 to 3,
An input means for receiving an input of a retroactive condition including any identifier of the object or storage means to be retroactive, a time zone to be retroactive, and any of the stages that are desired to be retroactive among the stages of the distribution process;
A traceability support apparatus further comprising: retroactive means for acquiring information corresponding to the retroactive condition input to the input means from the first database and outputting the information as retroactive information. The structure of a database applied to a traceability support device that tracks and retroactively monitors the status of each stage of the distribution process of an object,
The database includes first and second databases,
The first database associates the departure date of the object at the departure point in the distribution process and the arrival date at the arrival point with an identifier attached to the object, and the storage means The departure date at the departure point and the arrival date at the arrival point are associated with the identifier attached to the storage means,
The second database has a database structure in which storage units and objects associated with each other in the first database or storage units associated with each other are associated with each other using respective identifiers.

Images