WO2017199558A1

WO2017199558A1 - Management system and management method for managing at least one of distribution container and goods

Info

Publication number: WO2017199558A1
Application number: PCT/JP2017/009976
Authority: WO
Inventors: 尚美加納; 好則村崎
Original assignee: 日本パレットレンタル株式会社
Priority date: 2016-05-18
Filing date: 2017-03-13
Publication date: 2017-11-23
Also published as: KR20170139495A; CN107636708A; JP2017206352A

Abstract

The present invention manages at least one of a distribution container and goods in consideration of a loading relationship. A server 10 is provided with: a database 11 for storing parent link information and child link information with respect to each of 30 entities which are either goods or distribution containers; an input unit 12 for inputting loading information that indicates a load for loading and a load object to be loaded, and inputting unpacking information that indicates a load and a load object to be unpacked; an association unit 13 for causing information that indicates a load object as parent link information pertaining to the load in the loading information and information that indicates a load as child link information pertaining to the load object to be stored in the database 11, and causing information that indicates a load object as parent link information pertaining to the load in the unpacking information and information that indicates a load as child link information pertaining to the load object to be removed from the database 11; and an output unit 14 for outputting information stored by the database 11.

Description

Management system and management method for managing at least one of physical distribution container and article

The present invention relates to a management system and a management method for managing at least one of a distribution container and an article.

Conventionally, in order to improve the efficiency of transportation, logistics containers such as pallets for collectively transporting articles to be transported have been used. In such a system for receiving and shipping logistics containers between bases, in order to accurately manage the number of incoming and outgoing logistics containers at each base, a physical distribution container management system configured by an information processing device is used (for example, , See Patent Document 1).

JP 2003-246456 A

As described above, a system for managing receipt / shipment of physical distribution containers is used, while a system for managing receipt / shipment of goods to be transported is also used. Usually, incoming and outgoing logistics containers and incoming and outgoing goods are managed by separate systems. In this way, when the distribution container and the article are managed by separate systems, it is impossible to grasp which distribution container the article is loaded on.

In addition, a distribution container loaded with products may be loaded in another distribution container. For example, a shipping case may be loaded on a pallet. In the conventional system, it is impossible to grasp the loading relationship between such distribution containers.

If the loading relationship cannot be grasped, for example, the following problems occur. When a problem occurs in a specific product individual in the food industry and a recall is made, in order to search for the product, it is necessary to take out and confirm all the products loaded in the distribution container. Even if there is a system that reads the tag attached to the product and issues a warning for the product to be recalled, it may be difficult to read it if it is packed and loaded in a physical distribution container. May not be performed. Therefore, a product that should not be shipped may be shipped by mistake. For this reason, in the food industry, conventionally, when a recall occurs, there is no method other than to deal with the whole amount recovery.

The present invention has been made in view of the above, and an object thereof is to provide a management system and a management method capable of managing at least one of a distribution container and an article in consideration of a loading relationship.

In order to achieve the above object, a management system according to an embodiment of the present invention provides parent link information indicating a link to a parent and a link to a child for each individual that is at least one of an article and a physical distribution container. The storage means for storing the child link information to be displayed, the loading information indicating the loaded object as the individual to be loaded, and the loaded object as the loaded individual, and the loaded object and the loaded object to be unpacked are indicated. Input means for inputting unpacking information, information indicating the load as parent link information for the load indicated by the load information input by the input means, and child links for the load indicated by the load information Information indicating the load as information is stored in the storage means, and the parent link for the load indicated by the unloading information input by the input means Information indicating the loaded object as information, and information indicating the loaded object as child link information for the loaded object indicated by the loading information are deleted from the storage means, and information indicating the individual is stored as parent link information For an individual that has not been performed, an association unit that stores in the storage unit location information indicating a location where the individual is located, and an output unit that performs output according to the information stored in the storage unit.

In the management system according to an embodiment of the present invention, the information on the loading relationship between the individuals is stored by the parent link information and the child link information for each individual, and the location information is stored for the highest individual in the loading relationship. It is associated. Therefore, according to the management system concerning one embodiment of the present invention, an individual can be managed in consideration of a loading relation.

The output means inputs detection information indicating the detection target individual and detection target information indicating the detection target individual, and obtains the individual obtained from the parent link information of the detection target individual and the detection target individual. It is good also as comparing and performing the output according to a comparison result. According to this configuration, it is possible to appropriately perform a warning of a recall target product based on the stored information on the loading relationship between individuals.

The association means may store the location information indicating the location where the individual is located and the history information indicating the history of loading and unpacking in the storage means for each individual. According to this configuration, it is possible to grasp a trace of what kind of transportation work has been performed on an individual.

By the way, the present invention can be described as the invention of the management system as follows, as well as the invention of the management system as described above. This is substantially the same invention only in different categories, and has the same operations and effects.

That is, the management method according to an embodiment of the present invention stores parent link information indicating a link to a parent and child link information indicating a link to a child for each of at least one of an article and a physical distribution container. A management method, which is an operation method of a management system including a storage unit, and inputs load information indicating a load to be loaded and a load to be loaded as an individual to be loaded and unloads the load. And an input step for inputting unloading information indicating the load, and information indicating the load as parent link information for the load indicated by the load information input in the input step, and the load indicated by the load information. For the load, information indicating the load as child link information is stored in the storage means, respectively, and the unloading information input in the input step is used. Delete the information indicating the load as parent link information for the load indicated, and delete the information indicating the load as child link information for the load indicated by the load information from the storage means. For an individual in which information indicating an individual is not stored as link information, an associating step for storing in the storage means location information indicating the location where the individual is located, and an output for performing output in accordance with the information stored in the storage means Steps.

According to one embodiment of the present invention, individuals can be managed in consideration of the loading relationship.

It is a figure which shows the structure of the management system which concerns on embodiment of this invention. It is a figure which shows the table of the database of a server. It is a figure which shows packing loading schematically. It is a figure which shows unpacking typically. It is a figure which shows the work information at the time of packing up. It is a figure which shows the work information at the time of unpacking. It is a figure which shows the work information at the time of shipment and arrival. It is a figure which shows the table of the database at the time of packing up. It is a figure which shows the table of the database at the time of unpacking. It is a figure which shows the table of the database at the time of shipment and arrival. It is a figure which shows the table of a database, and the goods and container hierarchy reference information produced | generated according to it. It is a figure which shows the example of the screen display using goods and container hierarchy reference information. It is a figure which shows the table of a database, and the trace information produced | generated according to it. It is a sequence diagram which shows the process (management method) performed when the operation | work is performed in a base and information is registered into a database in the management system which concerns on embodiment of this invention. It is a sequence diagram which shows the process (management method) performed when the warning which concerns on recall goods is performed in the management system which concerns on embodiment of this invention.

Hereinafter, embodiments of a management system and a management method according to the present invention will be described in detail with reference to the drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted.

FIG. 1 shows a server (distribution product individual management server) 10 which is a management system according to the present embodiment. The server 10 is a device that manages the individual 30 related to logistics. The individual 30 to be managed includes a commodity that is an article to be transported and a physical distribution container that is used for transportation of the commodity. A logistics container is a loading platform or container that is loaded when goods are transported, and specifically corresponds to a pallet, a transporting cardboard, a folding container, a cart, a logistics crate, an international maritime cargo container, and the like. The goods are collected into a plurality or packed individually and loaded in a distribution container, and are received and shipped between bases. Further, the physical distribution container can be loaded on another physical distribution container. For example, containers such as containers for transporting logistics containers such as pallets together may be used. In this way, transportation can be carried out using several levels of logistics containers. In addition, at a base, transshipment to another physical distribution container may be performed depending on the transport scale. In addition, the distribution container can be received and shipped between the bases in a state where no goods are loaded.

The bases where the individual 30 is received and shipped are, for example, a factory that manufactures products, a warehouse that stores products, a distribution center, and a wholesale or retail store that sells products. A number that is information for uniquely identifying each base is assigned to the base in advance. The receipt / shipment of the individual 30 is performed based on, for example, an order for a product from a wholesale or retail store to a product manufacturer.

The server 10 holds information on the position of the individual 30 and the loading relationship between the individual 30. Specifically, the server 10 is realized by a computer such as a PC (Personal Computer) or a server device including hardware such as a CPU (Central Processing Unit), a memory, and a communication module. The functions of the server 10 to be described later are exhibited by operating these components by a program or the like.

Each individual 30 is previously assigned an individual number (individual identification number) that is information for uniquely identifying each individual 30. For example, an RFID (Radio Frequency IDentification) tag holding the individual number of the individual 30 is attached to the individual 30.

A reader (HHT: handheld terminal) 20 is provided at each base where the individual 30 is received and shipped. The reader 20 is a device that acquires an individual number of the individual 30 and transmits / receives information related to management of the individual 30 to / from the server 10. The reader 20 is used by an operator at each site. For example, the reader 20 reads an RFID tag attached to the individual 30 and acquires the individual number of the individual 30. The acquisition of the individual number may be performed not by reading the RFID tag but by reading a barcode attached to the individual 30 or the like. The server 10 and the reader 20 can exchange information with each other via a communication network such as the Internet.

Specifically, the reader 20 is configured by hardware such as a CPU, a memory, a reading module, and a communication module. The reader 20 also includes an input device for inputting information and an output device for outputting (for example, displaying) information. For example, the reader 20 includes a touch panel display. A conventional RFID reader may be used as the reader 20 device. The function of the reader 20 according to the present embodiment will be described together with the description of the function of the server 10. Note that the reader 20 may be included in the management system according to the present invention.

Subsequently, functions of the server 10 according to the present embodiment will be described. As illustrated in FIG. 1, the server 10 includes a database 11, an input unit 12, an association unit 13, and an output unit 14.

The database 11 is storage means for storing parent link information indicating a link to a parent and child link information indicating a link to a child for each individual 30. The parent link information and the child link information indicate the position of the individual 30 and the loading relationship between the individual 30. That is, the database 11 stores hierarchical management information for managing the hierarchical relationship between the individuals 30 and between the base and the individual 30. The database 11 holds information in the table shown in FIG. As shown in FIG. 2, the table stores information of “No.”, “Target”, “Parent No.”, “Child No.”, and “History” in association with each other. Each record (data in one row) of the table is information about one individual 30 (for example, a record such that “object” is “individual A”), or information about one base (location) (for example, “Object” corresponds to a record of “location X” and “location Y”).

“No.” is information for specifying a target related to the record. When the record relates to the individual 30, “No.” is the individual number of the individual 30. When the record relates to a base, “No.” is the number of the base. “Target” is the name of the target related to the record (for example, “location X”, “individual A”). “Parent No.” is information corresponding to the parent link information. When the individual 30 is loaded on another individual 30, “parent number” is the individual number of the other individual 30. When the individual 30 is not loaded on another individual 30, the “parent number” is the number of the base where the individual 30 is located. “Parent No.” of one record includes only one piece of information (individual number of individual 30 or base number). “Parent No.” is not set in the base record.

“Child No.” is information corresponding to the child link information. When the individual 30 carries another individual 30, “child No.” is the individual number of the other individual 30. When the individual 30 does not carry another individual 30, the “child No.” is not set. In the base record, the individual number of the individual 30 that is not loaded on another individual 30 among the individuals 30 located at the base. A plurality of pieces of information (individual numbers) may be included in the “child No.” of one record (for example, records of “location X” and “individual A”). “History” is information on the history of the individual 30. More details will be described later. “History” is not set in the base record.

As described above, the database 11 stores information indicating the loading relationship of the individual 30 over a plurality of hierarchies.

The input unit 12 is input means for inputting loading information related to loading of the individual 30 at the base and inputting unloading information related to unpacking of the individual 30 at the base. The loading information is information indicating a loaded object that is an individual 30 to be loaded and a loaded object that is an individual 30 to be loaded. The unpacking information is information indicating the load and the load to be unpacked. The loading information and the unloading information are transmitted as work information from the reader 20 at each site to the server 10.

For example, loading is performed as shown in FIG. 3, and unpacking is performed as shown in FIG. In each base, work information is generated in the reader 20 when work such as loading and unpacking is performed. When the work information is generated, first, information indicating the work classification is input to the reader 20 by the worker. The work classification is, for example, packing (loading) and unpacking. Subsequently, the individual number of the individual 30 is acquired from the individual 30 to be worked by the reader 20. The acquisition of the individual number is performed after setting the parent individual or the target individual. This setting is performed by an operation on the reader 20 by the operator. The parent individual is an individual to be loaded (loading object), and the target individual is an individual to be loaded (loading object). Further, the reader 20 has a time measuring function, and acquires the time when the work information is generated as the work date. In addition, the reader 20 stores in advance information on a base indicating a work place as a work place. The information on the work place stored in the reader 20 can be registered and changed by an operator or the like.

The reader 20 associates the above information with work information. For example, as shown in FIG. 3, when “product D” and “product E” are packed and loaded in “container A” at “place X”, the reader 20 displays the work information shown in FIG. Generate. Furthermore, when “container A” is packed in “container B” at “place X”, the reader 20 generates work information shown in FIG.

As shown in FIG. 4, when “container A” is unpacked from “container B” at “place Y”, the reader 20 generates work information shown in FIG. Furthermore, when “product D” and “product E” are unpacked from “container A” at “place Y”, the reader 20 generates work information shown in FIG.

Work information is also generated when work other than loading and unpacking is performed. For example, it is also generated when the individual 30 is shipped or received at the base. In this case, the parent information is not included in the work information, and the individual number of the individual 30 to be shipped or received is included as the target individual information. The individual 30 at this time is the highest individual (not loaded on another individual 30) in the hierarchical relationship. For example, when “container B” is shipped at “location X”, the reader 20 generates work information shown in FIG. When “container B” is received at “place Y”, the reader 20 generates work information shown in FIG. The reader 20 transmits the generated work information to the server 10.

The input unit 12 receives and inputs work information transmitted from the reader 20. The input unit 12 outputs the input work information to the association unit 13.

The association unit 13 is an association unit that registers information in the database 11, that is, associates (links) the individuals 30 based on the work information input from the input unit 12. The association between the individuals 30 during loading and unpacking and the cancellation thereof are performed one layer at a time as shown below. For the load (target individual) indicated by the load information input from the input unit 12, the associating unit 13 uses the individual number of the load (parent individual) as the parent link information and the load indicated by the load information. For the object (parent individual), the individual number of the load (target individual) is stored in the database 11 as child link information. Further, for each individual 30, the association unit 13 stores, in the database 11, location information indicating the location where the individual 30 is located, and history information indicating the history of loading and unpacking.

This will be described using the example shown in FIG. In “place X”, there are “container A”, “container B”, “product D”, and “product E” as individuals 30. In this case, information shown in FIG. 8A is stored in the table of the database 11. Individual numbers of “container A”, “container B”, “product D”, and “product E” are stored in “child No.” of the record of “location X”. In the “parent No.” of each record of “container A”, “container B”, “product D”, and “product E”, the number of “location X” is stored. Nothing is stored. When a record of the individual 30 is newly registered in the server 10, as described above, the number of the base where the individual is located is stored in the “parent No.”, and the “child No.” is stored in the “child No.”. Nothing is stored.

When “product D” and “product E” are packed and loaded in “container A” at “location X”, the work information shown in FIG. 5A is input by the input unit 12 and is input to the association unit 13. Is output. For the work information whose work classification is packing (loading), the associating unit 13 sets “parent No.” to the individual number of the parent individual of the work information for the record of the individual 30 indicated by the individual number of the target individual of the work information. Change to (replace). In addition, for the record of the individual 30 indicated by the individual number of the parent individual of the work information, the individual number of the target individual of the work information is added to “child No.”. Further, the individual number of the target individual is deleted from the “child No.” of the record of the “parent No.” number before the change of the record of the individual 30 indicated by the individual number of the target individual of the work information. In this way, the hierarchical relationship between the individuals 30 is changed.

For the work information shown in FIG. 5A, the associating unit 13 sets “parent No.” from the number of “location X” for the records of “product D” and “product E” that are target individuals. The parent number is changed to the individual number of “container A”. Further, the associating unit 13 adds the individual numbers of “product D” and “product E” as target individuals to “child No.” for the record of “container A” as the parent individual. Further, the associating unit 13 records “location X” indicated by “parent No.” of “product D” and “product E”, which are target individuals, from “child No.” to “product D” and “ The individual number of “Product E” is deleted.

Also, the association unit 13 adds history information to the “history” for the record of the individual 30 indicated by the parent individual of the work information and the individual number of the target individual based on the work information. The history information includes information on the work date, work place, and work classification included in the work information. For the work information shown in FIG. 5A, the association unit 13 adds history information for “container A”, “product D”, and “product E”. The associating unit 13 adds the same history information to the “history” in all the records obtained by tracing the “child No.” from the record of the target individual. In the example of FIG. 8A, since there is no individual number of “child No.” of “product D” and “product E” as target individuals (no child), the addition is not performed. As a result of the processing by the associating unit 13 based on the work information shown in FIG. 5A, the table of the database 11 is in the state shown in FIG. The history information may include information of “parent No.” and “child No.” of each individual 30 at that time.

Subsequently, when “container A” is packed in “container B” at “place X”, the work information shown in FIG. 5B is input by the input unit 12 and output to the association unit 13. The For the work information shown in FIG. 5B, the associating unit 13 sets the “parent No.” as the parent individual from the “location X” number for the record of “container A” that is the target individual. Change to the individual number of “container B”. The association unit 13 adds the individual number of “container A” as the target individual to “child No.” for the record of “container B” as the parent individual. Further, the associating unit 13 deletes the individual number of “container A” from “child number” for the record of “location X” indicated by “parent number” of “container A” that is the target individual.

Also, the associating unit 13 adds history information for “container B” and “container A”. The associating unit 13 also has the same “history” for “product D” and “product E” that are all records obtained by tracing “child No.” from the record of “container A” that is the target individual. Add history information. As a result of the processing by the associating unit 13 based on the work information shown in FIG. 5B, the table of the database 11 is in the state shown in FIG. The above is the function of the associating unit 13 when the work classification is packing (loading).

For the load (target individual) indicated by the unloading information input from the input unit 12, the associating unit 13 displays information indicating the load (parent individual) as parent link information, and indicates the load indicated by the load information. For the load (parent individual), information indicating the load (target individual) is deleted from the database 11 as child link information. In addition, the association unit 13 causes the database 11 to store location information indicating a location where the individual 30 is located for the individual 30 in which information indicating the individual 30 is not stored as parent link information.

This will be described using the example shown in FIG. In “location Y”, there are “container A”, “container B”, “product D”, and “product E” as individuals 30. In “container B”, “container A” is packed and loaded, and in “container A”, “product D” and “product E” are packed and loaded. In this case, the information shown in FIG. 9A is stored in the table of the database 11. Normally, when the individual 30 is loaded, the “history” of the record of the individual 30 related to the loading includes the history information, but is omitted in FIG. The same applies to the following).

When “container A” is unpacked from “container B” at “location Y” (“container A” is taken out from “container B”), the work information shown in FIG. And output to the association unit 13. For the work information whose work classification is unpacking, the associating unit 13 deletes the individual number of the target individual of the work information from the “child No.” for the record of the individual 30 indicated by the individual number of the parent individual of the work information To do. Further, for the record of the individual 30 indicated by the individual number of the target individual of the work information, “parent No.” is changed (changed) to the number of the base obtained by following the “parent No.” at that time. “Parent No.” may be changed to the work place number in the work information. In addition, for the record of the base (the base number obtained by tracing the “parent No.” or the work place number of the work information), the individual number of the target individual of the work information is indicated in the “child No.”. Add

For the work information shown in FIG. 6A, the associating unit 13 assigns the individual number of “container A” as the target individual from “child No.” for the record of “container B” as the parent individual. delete. Further, the associating unit 13 traces “parent No.” from the individual number of “container B” and “parent No.” from the record of “container B” for the record of “container A” as the target individual. Change to the number of “location Y” which is the base obtained in this way. In addition, for the record of “location Y”, the individual number of “container A” that is the target individual is added to “child No.”.

Also, the associating unit 13 adds history information for “container A” and “container B”. The associating unit 13 also has the same “history” for “product D” and “product E” that are all records obtained by tracing “child No.” from the record of “container A” that is the target individual. Add history information. As a result of the processing by the associating unit 13 based on the work information shown in FIG. 6A, the table of the database 11 is in the state shown in FIG. 9B.

Subsequently, when “product D” and “product E” are unpacked from “container A” at “place Y”, the work information shown in FIG. 6B is input by the input unit 12 and associated. Is output to the unit 13. For the work information shown in FIG. 6B, the associating unit 13 sets “product D” and “product E” as the target individuals from “child No.” for the record of “container A” as the parent individual. ”Is deleted. Further, the associating unit 13 sets “parent No.” from the individual number of “container A” and “parent” from the record of “container A” for the records of “product D” and “product E” as target individuals. "No." is changed to the number of "location Y" which is the base obtained by tracing. In addition, for the record of “location Y”, the individual numbers of “product D” and “product E” as target individuals are added to “child No.”.

Also, the associating unit 13 adds history information for “product D”, “product E”, and “container A”. In the example of FIG. 9B, since there is no individual number of “child No.” of “product D” and “product E” as target individuals (having no children), history to records other than the above is recorded. No information is added. As a result of the processing by the associating unit 13 based on the work information shown in FIG. 5B, the table of the database 11 is in the state shown in FIG.

When all the individuals 30 are unpacked from the parent individual (when all the individuals 30 of the parent individual “child No.” are the target individuals), the information on the target individual of the work information may not be set. . In that case (when there is no information on the target individual of the work information), the above processing is performed assuming that all the individuals 30 of the parent individual “child No.” are target individuals. The above is the function of the association unit 13 when the work classification is unpacking.

When the work information output from the input unit 12 relates to shipment or arrival, the association unit 13 has the following functions. This will be described using the example shown in FIGS. From “location X”, “container A”, “container B”, “product D”, and “product E” are shipped as individual 30. In “container B”, “container A” is packed and loaded, and in “container A”, “product D” and “product E” are packed and loaded. In this case, information shown in FIG. 10A is stored in the table of the database 11.

When each individual 30 (“container B” as the packing form) is shipped at “place X”, the work information shown in FIG. 7A is input by the input unit 12 to the association unit 13. Is output. In addition, a package form shows the form to be transported, and here shows the highest individual 30 in a hierarchical relationship. The associating unit 13 adds history information for “container B” for work information whose work classification is shipment. In addition, the associating unit 13 also records “container A”, “product D”, and “product E” that are all records obtained by tracing “child No.” from the record of “container B” that is the target individual. , Add the same history information to “History”. Note that the “parent number” and “child number” are not changed for the work information whose work classification is shipment. As a result of the processing by the associating unit 13 based on the work information shown in FIG. 7A, the table of the database 11 is in the state shown in FIG.

Subsequently, when each individual 30 shipped from “place X” is received at “place Y”, the work information shown in FIG. 7B is input by the input unit 12 to the association unit 13. Is output. For the work information whose work classification is arrival, the associating unit 13 sets the “parent No.” for the record of “container B” that is the individual 30 indicated by the individual number of the target individual of the work information, Change (change) the location number. Further, “container B” as the target individual is deleted from “child No.” for the record of “location X” indicated by “parent number” before the change of the record of “container B” as the target individual. For the record of “place Y” indicated by the work place number in the work information (“place Y” indicated by “parent No.” after the record of “container B” that is the individual 30 is changed) “ “Container B” as the target individual is added to “Child No.”. Further, the associating unit 13 adds history information for “container B”. In addition, the associating unit 13 also records “container A”, “product D”, and “product E” that are all records obtained by tracing “child No.” from the record of “container B” that is the target individual. , Add the same history information to “History”. As a result of the processing by the associating unit 13 based on the work information shown in FIG. 7B, the table of the database 11 is in the state shown in FIG. The above is the function of the associating unit 13 when the work classification is shipment or arrival.

In addition, although the work classification mentioned above was only packing (loading), unpacking, shipping, and receiving goods, if it is the work concerning the individual | organism | solid 30, arbitrary work divisions can be provided. Moreover, it is good also as changing the information stored in the database 11 according to the said operation | work.

The output unit 14 is an output unit that performs output according to information stored in the database 11. As described above, the database 11 holds information indicating the hierarchical relationship between the individuals 30 and between the base and the individuals 30. Therefore, information can be output based on the hierarchical relationship.

Specifically, the output unit 14 acquires information about another individual 30 loaded on the specific individual 30 and information about the individual 30 located at the specific base from the database 11 and outputs the information. For example, the reader 20 transmits the individual number of the specific individual 30 or the number of the specific base to the server 10. This transmission is performed by, for example, an operator's operation on the reader 20. The output unit 14 receives and inputs the individual number of the specific individual 30 or the number of the specific base transmitted from the reader 20. The output unit 14 specifies the record of the individual number of the specific individual 30 or the number of the specific base from the information stored in the database 11. The output unit 14 records all the records obtained by tracing the “child No.” from the record, information on another individual 30 loaded on the specific individual 30, and an individual located at a specific base. 30 information is specified. The output unit 14 outputs the specified record information by transmitting it to the reader 20 as product / container hierarchy inquiry information.

For example, when the table of the database 11 is in the state shown in FIG. 11A and the specific individual 30 is “container B”, “container A” is recorded from “child No.” in the record of “container B”. “Product D” and “product E” are specified from “child No.” of the record of “container A”. Therefore, the product / container hierarchy inquiry information output from the output unit 14 is information shown in the table of FIG.

The above information can be used, for example, for inspection when goods are received at the base. Specifically, the leader 20 of the received base receives the product / container hierarchy inquiry information about the received physical distribution container from the server 10. At this time, the information on the target individual included in the work information related to arrival may be the information on the specific individual 30 described above. The reader 20 performs inspection by comparing (collating) the number of products indicated by the product / container hierarchy inquiry information with the number of products scheduled to be received in advance in the reader 20 by an operator or the like. If the numbers match, it is assumed that the goods are correctly received, and if they do not match, the goods are not correctly received. If the numbers do not match, the reader 20 is made to read the individual number from the received product (after unpacking), the read individual number, and the individual number of the product indicated by the product / container hierarchy inquiry information May be compared (collated).

Further, as shown in the screen image of FIG. 12, the hierarchical relationship between the bases and the individuals 30 may be displayed in a tree shape using the product / container hierarchy inquiry information.

Also, the output unit 14 acquires information about another individual 30 carrying the specific individual 30 from the database 11 and outputs the information. For example, the reader 20 transmits the individual number of the specific individual 30 to the server 10. This transmission is performed by, for example, an operator's operation on the reader 20. The output unit 14 receives and inputs the individual number of the specific individual 30 transmitted from the reader 20. The output unit 14 specifies the record of the individual number of the specific individual 30 from the information stored in the database 11. The output unit 14 specifies all records other than the base obtained by tracing the “parent No.” from the record as information on another individual 30 carrying the specific individual 30. The output unit 14 outputs the specified record information by transmitting it to the reader 20 as product / container hierarchy inquiry information. The merchandise / container hierarchy query information may also include information on the base record obtained by tracing the “parent number”.

For example, if the table of the database 11 is in the state shown in FIG. 11A and the specific individual 30 is “product E”, “container A” from “parent No.” in the record of “product E”. Is identified, and “container B” is identified from “parent number” of the record of “container A”. Therefore, the product / container hierarchy inquiry information output from the output unit 14 is information shown in the table of FIG.

The above information can be used, for example, to specify a physical distribution container loaded with a recall product, which is a product to be recalled, and issue a warning (alert) at the base. Specifically, the specific individual 30 is set as an individual 30 to be detected as a recall product. That is, the output unit 14 inputs the individual number of the specific individual 30 as alert individual input information. In addition, when there are a plurality of recalled products, the output unit 14 inputs a plurality of individual numbers.

The base reader 20 receives the product / container hierarchy inquiry information about the individual 30 from the server 10 as alert information. The reader 20 reads the individual number from the individual 30 to be detected at the base. The reading of the individual number may be performed only for warning related to the recalled product, or may be performed for generating the above-described work information. The reader 20 compares the individual 30 indicated by the alert information with the individual 30 associated with the read individual number, and whether any of the individuals 30 indicated by the alert information matches the individual 30 associated with the read individual number. Judge whether or not. If they match, the individual 30 associated with the read individual number is the individual 30 loaded with the recall product or the recall product itself. Accordingly, in that case, the reader 20 issues a warning to that effect (for example, a display such as “A recall target product has been detected! A recall target product is loaded in a work target container”).

In the above example, the output unit 14 inputs detection information indicating the individual 30 to be detected, and outputs alert information obtained from the parent link information of the individual 30 to be detected to the reader 20. Further, the reader 20 inputs the alert information and the detected information indicating the individual 30 to be detected, compares the individual 30 indicated in the alert information with the individual 30 to be detected, and produces a comparison result. Output according to In the above aspect, the reader 20 is included in the management system according to the present embodiment and has one function of output means.

Further, the output unit 14 may acquire and output information on another individual 30 included in the same packaging as the specific individual 30 from the database 11. For example, the reader 20 transmits the individual number of the specific individual 30 to the server 10. This transmission is performed by, for example, an operator's operation on the reader 20. The output unit 14 receives and inputs the individual number of the specific individual 30 transmitted from the reader 20. The output unit 14 specifies the record of the individual number of the specific individual 30 from the information stored in the database 11. The output unit 14 specifies all records other than the base obtained by tracing the “parent No.” from the record as information on another individual 30 included in the same package as the specific individual 30. Further, among those records, the record whose “parent number” is the base number, that is, all the records obtained by tracing “child number” from the record of the highest individual 30 in the hierarchical relationship. Is also specified as information on another individual 30 included in the same package as the specific individual 30. The output unit 14 outputs the specified record information by transmitting it to the reader 20 as product / container hierarchy inquiry information.

Also, the output unit 14 outputs the history information stored in the database 11. For example, the reader 20 transmits the individual number of the individual 30 to the server 10. This transmission is performed by, for example, an operator's operation on the reader 20. The output unit 14 receives and inputs the individual number of the individual 30 transmitted from the reader 20. The output unit 14 specifies the record of the individual number of the individual 30 from the information stored in the database 11. The output unit 14 outputs the “history” information of the record by sending it to the reader 20 as trace information.

For example, when the table of the database 11 is in the state shown in FIG. 13A and the individual 30 to which the trace information is output is “container B”, the record of “container B” shown in FIG. The “history” information of this becomes trace information. The trace information is displayed on the reader 20, for example. By referring to the trace information, it is possible to grasp a trace of what kind of transportation work has been performed on the individual 30. The above is the configuration of the server 10 according to the present embodiment.

Subsequently, a management method that is a process executed by the server 10 and the reader 20 (the operation method of each of the server 10 and the reader 20) according to the present embodiment will be described with reference to the sequence diagrams of FIGS. First, using the sequence diagram of FIG. 14, processing when work is performed at a base and information is registered in the database 11 of the server 10 will be described.

In the site leader 20, the work classification is input according to the work to be performed (S01). Subsequently, the reader 20 reads the individual number from the individual 30 according to the work to be performed (S02). At the base, work (packing loading, unpacking, shipping, receiving, etc.) is performed by an operator or the like. Subsequently, the reader 20 generates work information from the inputted work classification, the read individual number, and the like (S03). The generated work information is transmitted from the reader 20 to the server 10 (S04).

In the server 10, work information is received and input by the input unit 12 (S04, input step). Subsequently, the association unit 13 registers information in the database 11 based on the work information input from the input unit 12 (S05, association step). Specifically, the registration of information in the database 11 is registration of information in “parent No.” that is parent link information and “child No.” that is child link information as described above. The above is the processing when information is registered in the database 11 of the server 10.

Next, processing when a warning related to the recalled product is performed at the base will be described with reference to the sequence diagram of FIG. In the reader 20 at the base, the individual number of the individual 30 to be alerted is input (S11). The input individual number is transmitted from the reader 20 to the server 10 (S12).

In the server 10, the individual number of the individual 30 to be alerted is received and input as the alert individual input information by the output unit 14 (S12, output step). Note that the individual number of the individual 30 to be alerted does not necessarily have to be received from the reader 20 at the site where the alert is performed, and may be received from the reader 20 at another site. Further, the information may be input to the server 10 from other than the reader 20. Subsequently, the server 10 generates alert information including information on another individual 30 loaded with the individual 30 to be alerted from the database 11 based on the input individual number (S13, output step). The generated alert information is transmitted from the output unit 14 to the reader 20 (S14). This transmission may be performed, for example, with respect to the readers 20 at all bases.

The alert information is received by the reader 20 (S14). Subsequently, the reader 20 reads the individual number from the individual 30 to be detected (S15, output step). The reading of the individual number from the individual 30 may be common to the process of S02 described with reference to FIG. Subsequently, the reader 20 collates (determines) whether any of the individuals 30 indicated by the alert information matches the individual 30 associated with the read individual number (S16, output step). Subsequently, the reader 20 performs output according to the collation result (S17, output step). For example, if they match as a result of collation, a warning such as a display to that effect is given. Note that the information output from the server 10 is not limited to the warning related to the recalled product as described above, but can be used for the above-described inspection, tracing, and the like. In that case, the information corresponding to the inspection and the grasp of the trace as described above is output from the server 10. The above is the processing executed by the server 10 and the reader 20 according to the present embodiment.

According to the present embodiment, the information on the loading relationship between the individuals 30 is stored by the parent link information and the child link information for each individual 30, and the location information is associated with the highest individual in the loading relationship. . Therefore, according to the present embodiment, the individual 30 can be managed in consideration of the loading relationship. For example, by specifying an individual number, it is possible to grasp (search) where (location) it is and what state (loading state) it is. Further, since the goods contained in the outer distribution container and the information on the distribution containers can be extracted from the information on the outer distribution container, it is possible to know the loaded goods only by reading the outer container, thereby simplifying the incoming inspection work. In addition, according to the configuration as in the present embodiment, since there is no limit on the number of layers, it is possible to deal with an arbitrary number of layers.

In addition, as in the warning related to the recall product of the present embodiment, the individual 30 obtained by tracing the parent link information of the individual 30 to be detected is compared with the individual 30 to be detected and output is performed. Also good. According to this configuration, it is possible to appropriately perform a warning of a recall target product based on the stored information on the loading relationship between individuals. Thereby, the erroneous shipment of goods can be prevented.

Further, history information may be stored in the database 11 as in the present embodiment. According to this configuration, it is possible to grasp a trace of what type of transportation work has been performed on the individual 30. That is, it is possible to grasp (search) what route the individual 30 has passed through the base. In the present embodiment, as described above, history information is also added to all records obtained by tracing the “child No.” of the target individual. Thereby, it is possible to correctly trace the individual 30 (individual 30 that does not become the target individual) that is loaded on another individual 30 (distribution container) and is not directly the work target.

Especially in the food industry, there is a need for greater safety and security, so depending on the product, prompt recall and strict traceability are required. In this embodiment, quick recall handling and strict traceability can be realized.

In the above-described embodiment, the individual 30 to be managed by the server 10 includes both a commodity that is an article to be transported and a physical distribution container that is used for transportation of the commodity. Only one of them may be managed by the server 10.

Further, in the present embodiment, the location information indicating the location where the individual 30 is located is not hierarchical, but the location information may be hierarchical as well as the information of the individual 30. For example, the location information may be two layers of a warehouse and a storage location in the warehouse. Thereby, more detailed management becomes possible. In addition, information other than the base may be included in the location information. For example, location information related to a truck being transported may be defined. Thereby, the moving individual 30 can be easily managed.

Further, information indicating the state of the individual 30 may be added to the information of each individual 30 in the database 11. The state of the individual 30 includes, for example, a state in which the individual is usable, damaged, needs to be cleaned, is a product, or is a non-product. According to this configuration, the state of the individual 30 can also be managed. In addition, the number of stocks by state can be easily grasped.

In addition, the history information may include the packing form and shipping destination information. As a result, it is possible to manage information more in line with the actual transportation mode. Further, by adding information on the shipping destination, it is possible to grasp the planned arrival destination (shipping destination) by the search.

Further, in this embodiment, the apparatus that exchanges information with the server 10 at the base is the reader 20, but information may be exchanged with the server 10 by a terminal other than the reader 20. In that case, information about the individual 30 may be transmitted and received between the terminal and the reader 20. In particular, browsing of information such as trace information and registration of a recall target product may be performed by a terminal other than the reader 20 such as a PC instead of the reader 20.

10 ... server, 11 ... database, 12 ... input unit, 13 ... association unit, 14 ... output unit, 20 ... reader, 30 ... individual.

Claims

Storage means for storing parent link information indicating a link to a parent and child link information indicating a link to a child, for each of the individual that is at least one of an article and a physical distribution container;
An input means for inputting loading information indicating a loaded object that is an individual to be loaded and a loaded object that is an individual to be loaded, and inputting unloading information indicating a loaded object to be unpacked and a loaded object,
For the load indicated by the load information input by the input means, information indicating the load as parent link information, for the load indicated by the load information, information indicating the load as child link information, Each of the storage means stores the information indicating the load as parent link information for the load indicated by the unloading information input by the input means, and the child link for the load indicated by the load information. Information indicating the load as information is deleted from the storage unit, and for the individual in which information indicating the individual is not stored as parent link information, location information indicating the location where the individual is located is stored in the storage unit. Association means for causing,
Output means for performing output according to the information stored by the storage means;
A management system comprising:
The output means inputs detection information indicating an individual to be detected and detected information indicating an individual to be detected, and an individual obtained from parent link information of the individual to be detected; an individual to be detected; The management system according to claim 1, wherein an output corresponding to the comparison result is performed.
3. The management system according to claim 1, wherein the association means stores, in the storage means, location information indicating a location where the individual is located and history information indicating a loading / unpacking history for each individual.
A management method that is an operation method of a management system including storage means for storing parent link information indicating a link to a parent and child link information indicating a link to a child for each of at least one of an article and a physical distribution container There,
An input step of inputting loading information indicating a loaded object that is an individual to be loaded and a loaded object that is an individual to be loaded, and inputting unloading information indicating a loaded object to be unpacked and a loaded object, and
For the load indicated by the load information input in the input step, information indicating the load as parent link information, for the load indicated by the load information, information indicating the load as child link information, Each of the storage means stores the information indicating the loaded object as parent link information for the load indicated by the unloading information input in the input step, and the child link for the load indicated by the loading information. Information indicating the load as information is deleted from the storage unit, and for the individual in which information indicating the individual is not stored as parent link information, location information indicating the location where the individual is located is stored in the storage unit. An associated step to
An output step of performing output according to the information stored by the storage means;
Management method including.