JP7664302B2 - Management device and logistics information management method - Google Patents

Description

The present invention relates to an information processing system for managing logistics.

There is a distribution system in which a center centrally manages requests for delivery of cargo from shippers. For example, Patent Document 1 (JP Patent Publication 2002-207798A) describes a distribution management center for a distribution system in which a transport company dispatches a vehicle in response to a request from a shipper, and transports the cargo managed by a warehouse company by loading it, the distribution management center comprising: a means for receiving a delivery request from a shipper and notifying a terminal of the delivery company and a terminal of the warehouse company of information on the delivery request, respectively; a means for acquiring dispatch information indicating the content of dispatch based on the delivery request from a computer of the transport company; and a means for acquiring position information indicating the current position of the dispatched vehicle based on the dispatch information, calculating the estimated time of arrival of the vehicle at the warehouse company using the position information, and supplying the estimated time of arrival together with information on the delivery request assigned to the vehicle to a terminal of the warehouse company.

JP 2002-207798 A

When a consignee, who is the party placing an order, orders an item (e.g., a product) from a consignor, who is the party receiving the order, the item is delivered by a delivery company's delivery vehicle from a shipping base, which is the consignor's shipping origin, to a delivery base, which is the consignee's delivery destination. In such a logistics system, the consignee inspects each item or package (e.g., the cardboard box in which the item is packed) at the time of delivery. Since the inspection work is carried out when the vehicle arrives, it is difficult for the consignee to prepare and schedule the inspection work, and there is an issue of a large workload for the consignee.

In addition, because it is difficult to know the status of vehicle delays or the products loaded on arriving vehicles before the vehicles arrive, it is difficult to appropriately allocate delivery berths, which can result in excess staff at the recipient's facility and waste such as vehicle waiting times.

The object of the present invention is to provide a management device that can reduce the burden and waste of receiving operations and improve the efficiency of operations by sharing information held by each participant in the logistics system, such as the consignor, receiver, and delivery company.

A representative example of the invention disclosed in the present application is as follows: That is, a management device is configured by a computer having an arithmetic unit that executes a predetermined arithmetic process and a storage device connected to the arithmetic unit, the storage device stores account master data in which commodity codes and delivery styles are recorded in correspondence with each other , commodity classification master data in which commodity codes and commodity classifications are recorded in correspondence with each other, storage area master data in which commodity classifications and commodity storage areas are recorded in correspondence with each other, and receiving location master data in which commodity storage areas and berths at which vehicles arrive are recorded in correspondence with each other , the arithmetic unit stores order information including commodity codes and commodity quantities input by a consignee in the storage device, refers to the account master data to identify the delivery style corresponding to the commodity code included in the order information, refers to the commodity classification master data, the storage area master data, and the receiving location master data to identify a berth corresponding to the commodity code included in the order information, and outputs delivery information including the commodity codes, the commodity quantities , the delivery style , and the berth in response to a request from the consignee.

According to one aspect of the present invention, the burden of inspection work on the recipient can be reduced, and the inspection work can be made more efficient. Problems, configurations, and effects other than those described above will become clear from the following description of the embodiment of the invention.

FIG. 1 is a diagram illustrating an example of a configuration of an information processing system according to an embodiment of the present invention. FIG. 2 illustrates an example of the configuration of a management device according to the present embodiment. FIG. 2 is a diagram showing an example of a configuration of product classification master data in the present embodiment. FIG. 2 is a diagram showing an example of a configuration of storage area master data in the present embodiment. FIG. 2 is a diagram showing an example of the configuration of the account master data in this embodiment. FIG. 2 is a diagram showing an example of the configuration of delivery contract master data in the present embodiment. FIG. 2 is a diagram showing an example of a configuration of receiving location master data in the present embodiment. FIG. 2 is a diagram showing an example of a configuration of order information in the present embodiment. FIG. 2 is a diagram showing an example of the configuration of order information by shipping origin in the present embodiment. FIG. 2 is a diagram showing an example of the configuration of delivery request information according to the present embodiment. FIG. 2 is a diagram showing an example of the configuration of a delivery packing specification in the present embodiment. FIG. 2 is a diagram showing an example of a configuration of a packing slip according to the present embodiment. FIG. 11 is a diagram showing an example of a delivery schedule (dispatch result) in the present embodiment. FIG. 13 is a diagram showing an example of delivery records in the present embodiment. FIG. 13 is a diagram showing an example of delivery record (details) in the present embodiment. FIG. 2 is a diagram showing an example of operation results in the present embodiment. FIG. 13 is a diagram showing an example of delivery forecast/actual data in the present embodiment. FIG. 11 is a diagram showing an example of delivery statement data in the present embodiment. 11 is a flowchart showing an example of an order information/shipment-specific order information creation process according to the present embodiment. 13 is a flowchart showing an example of an operation record creation process according to the present embodiment. 11 is a flowchart showing an example of a delivery forecast/actual/delivery detail creation process according to the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a consignee in the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a consignee in the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a consignee in the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a shipper in the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a shipper in the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a delivery company in the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a delivery company in the present embodiment. FIG. 13 is a diagram showing an example of a delivery status reference screen referred to by a delivery company in the present embodiment.

Below, an embodiment of the present invention will be described with reference to the drawings. The embodiment is an example for explaining the present invention, and appropriate omissions and simplifications have been made to clarify the explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc., in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

As examples of various types of information, expressions such as "table", "list", and "queue" may be used, but the various types of information may be expressed in other data structures. For example, various types of information such as "XX table", "XX list", "XX queue", and "XX data" may be expressed as "XX information". When explaining identification information, expressions such as "identification information", "identifier", "name", "ID", "number", "code", and the like are used, but these are interchangeable.

When there are multiple components with the same or similar functions, they may be described using the same reference numerals with different subscripts. Also, when there is no need to distinguish between these multiple components, the subscripts may be omitted.

In the embodiments, the processing performed by executing a program may be described. Here, the computer executes the program using a processor (e.g., CPU, GPU), and performs the processing defined by the program using storage resources (e.g., memory) and interface devices (e.g., communication ports). Therefore, the subject of the processing performed by executing the program may be the processor. Similarly, the subject of the processing performed by executing the program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing the program may be a calculation unit, and may include a dedicated circuit that performs specific processing. Here, the dedicated circuit is, for example, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), a CPLD (Complex Programmable Logic Device), etc.

The program may be installed on the computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and a storage resource that stores the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In addition, in the embodiments, two or more programs may be realized as one program, and one program may be realized as two or more programs.

Figure 1 is a diagram showing an example of the configuration of an information processing system 6 according to an embodiment of the present invention.

The information processing system 6 of this embodiment includes a management device 1, an account reconciliation office terminal device 201, an account reconciliation office shipping base terminal device 202, an account reconciliation office terminal device 203, an account reconciliation shipping base terminal device 204, a delivery company office terminal device 301, a crew terminal device 302, a consignee office terminal device 401, and a delivery base terminal device 402. The management device 1 and each of the terminal devices 201 to 402 are connected to each other so as to be able to communicate with each other via a network 5. The network 5 may be a wired network or a wireless network. In particular, since the crew terminal device 302 is mounted on a delivery vehicle, using a 5G communication system may enable high-speed communication with little delay.

Although the illustration shows the consignor divided into an accounting originating company and an accounting destination company, there may be only one consignor. The accounting originating company and the accounting destination company are companies that have a sales relationship for the goods. For example, the accounting originating company is a manufacturer of the goods and the accounting destination company is a wholesaler of the goods. In another example, the accounting originating company is a first wholesaler of the goods and the accounting destination company is a second wholesaler of the goods.

The accounting originator office terminal device 201 is a computer installed in the accounting originator company's office, and the accounting originator shipping base terminal device 202 is a computer installed in the accounting originator company's product shipping base (e.g., a logistics center). The accounting destination office terminal device 203 is a computer installed in the accounting destination company's office, and the accounting destination shipping base terminal device 204 is a computer installed in the accounting originator company's product shipping base (e.g., a logistics center). The delivery company office terminal device 301 is a computer installed in the delivery company's office, and the driver's terminal device 302 is a computer installed in the delivery company's vehicle and operated by the driver. The consignee office terminal device 401 is a computer installed in the consignee company's office, and the delivery base terminal device 402 is a computer installed in the consignee company's delivery base (e.g., a logistics center).

Each of the terminal devices 201 to 402 is a computer having a processor (CPU), memory, an input interface, an output interface, and a communication interface. The processor is an arithmetic device that executes programs stored in memory 2. The memory stores programs executed by processor 1 and data used when executing the programs. The communication interface is a network interface device that controls communication with other devices according to a specific protocol. The input interface is an input device such as a keyboard or touch panel. The output interface is an output device such as a display device or printer.

Figure 2 is a diagram showing an example of the configuration of the management device 1 in this embodiment.

The management device 1 is composed of a computer having a storage device 10, a processor (CPU) 11, a memory 12, an input interface 13, an output interface 14, and a communication device 15.

The processor 11 is a computing device that executes programs stored in the memory 12. The processor 11 executes various programs to realize the functions of each functional unit of the management device 1. Note that some of the processing performed by the processor 11 by executing the programs may be executed by another computing device (e.g., hardware such as an ASIC or FPGA).

The memory 12 includes a ROM, which is a non-volatile storage element, and a RAM, which is a volatile storage element. The ROM stores unchanging programs (e.g., BIOS) and the like. The RAM is a high-speed, volatile storage element such as a DRAM (Dynamic Random Access Memory), and temporarily stores programs executed by the processor 1 and data used when the programs are executed.

The storage device 10 is, for example, a large-capacity, non-volatile storage device such as a magnetic storage device (HDD) or a flash memory (SSD). The storage device 10 also stores data used by the processor 11 when executing a program, and the program executed by the processor 11. In other words, the program is read from the storage device 10, loaded into the memory 12, and executed by the processor 11 to realize each function of the management device 1.

Specifically, the storage device 10 stores a processing program 150, product classification master data 111 (see Figure 3), storage area master data 112 (see Figure 4), account master data 113 (see Figure 5), delivery contract master data 114 (see Figure 6), receiving location master data 115 (see Figure 7), order information 121 (see Figure 8), order information by shipper origin 122 (see Figure 9), delivery request information 123 (see Figure 10), delivery packaging details data 124 (see Figure 11), packing details data 125 (see Figure 12), delivery schedule (dispatch result) data 126 (see Figure 13), actual delivery data 127 (see Figure 14), operation details data 128 (see Figure 15), forecast/actual delivery data 129 (see Figure 16), and delivery details data 130 (see Figure 17). Product classification master data 111, storage area master data 112, account master data 113, delivery contract master data 114, and receiving location master data 115 are classified as allocation master data referenced during processing, and order information 121, order information by shipper 122, delivery request information 123, delivery packaging details data 124, packing details data 125, delivery schedule (dispatch results) data 126, delivery record data 127-1, 127-2, operation record data 128, delivery forecast/actual data 129, and delivery details data 130 are classified as transaction data generated during processing.

The communication device 15 is a network interface device that controls communication with other devices according to a specific protocol.

The input interface 13 is an interface to which input devices such as a keyboard and a mouse are connected and which receives input from an operator. The output interface 14 is an interface to which output devices such as a display device and a printer are connected and which outputs the results of program execution in a format that can be viewed by the user. Note that a user terminal connected to the management device 1 via a network may provide the input device and output device. In this case, the management device 1 may have the functionality of a web server, and the user terminal may access the management device 1 using a specified protocol (e.g., http).

The programs executed by the processor 1 are provided to the management device 1 via removable media (CD-ROM, flash memory, etc.) or a network, and are stored in a non-volatile storage device 10, which is a non-transient storage medium. For this reason, the management device 1 should have an interface for reading data from removable media.

The management device 1 is a computer system configured on one physical computer, or on multiple logically or physically configured computers, and may operate on a virtual computer constructed on multiple physical computer resources. For example, the multiple program blocks that make up the processing program 150 may each operate on separate physical or logical computers, or multiple blocks may be combined to operate on a single physical or logical computer.

Figure 3 shows an example of the configuration of product classification master data 111 in this embodiment.

The product classification master data 111 is information on the classification of products defined by the consignee who orders the products. The product classification master data 111 includes records in which product codes 111A, major product categories 111B, medium product categories 111C, and minor product categories 111D are associated. The product code 111A is identification information for uniquely identifying a product. The major product categories 111B, medium product categories 111C, and minor product categories 111D are classification items set according to the granularity at which products are divided and managed. The major product categories 111B, medium product categories 111C, and minor product categories 111D are defined hierarchically, and the product classification can be expressed by the product classification of the smallest granularity assigned to the product.

Figure 4 shows an example of the configuration of the storage area master data 112 in this embodiment.

The storage area master data 112 is information on storage areas for each product classification defined by the consignee who manages the warehouse. The storage area master data 112 includes records that associate product classification 112A, area level 1 (112B), area level 2 (112C), and area level 3 (112D). Product classification 112A is a product classification item, and the data with the smallest granularity for the product among product classifications 111B to 111D in the product classification master data 111 (Figure 3) is used. Area level 1 (112B), area level 2 (112C), and area level 3 (112D) are items that are set according to the granularity of the storage area in the warehouse where products are stored by product classification.

Figure 5 shows an example of the configuration of the account master data 113 in this embodiment.

The account master data 113 is information on the shipper and delivery style defined by the combination of the consignee, the ordered product, and the sender. The account master data 113 includes records in which the consignee 113A, the product code 113B, the sender 113C, the shipper 113D, and the delivery style 113E are associated. The consignee 113A is identification information for uniquely identifying the consignee who is the order source in the commercial flow. The product code 113B is identification information for the product, and the same data as the product code 111A in the product classification master data 111 (Figure 3) is used. The sender 113C is identification information for uniquely identifying the consignor who is the order source in the commercial flow. The shipper 113D is identification information for uniquely identifying the shipping base in the physical distribution, and is defined by the combination of the consignee 113A, the ordered product code 113B, and the sender 113C. Delivery packaging style 113E is identification information assigned to each type of packaging style, and is defined by the combination of the consignee 113A, the ordered product code 113B, and the sender 113C.

Figure 6 shows an example of the configuration of the delivery contract master data 114 in this embodiment.

The delivery contract master data 114 is delivery contract information including the shipper, the receiver, and the delivery company, which are defined by the combination of the sender, the receiver, and the delivery company, and includes the shipper, the delivery destination base, the designated time, and the delivery style. The delivery contract master data 114 includes records in which the sender 114A, the receiver 114B, the delivery company 114C, the shipper 114D, the designated loading time 114E, the delivery destination 114F, the designated unloading time 114G, and the delivery style 114H are associated. The sender 114A is the identification information of the sender who is the order source in the commercial flow, and the same data as the sender 113C in the account master data 113 (Figure 5) is used. The receiver 114B is the identification information of the receiver who is the order source in the commercial flow, and the same data as the receiver 113A in the account master data 113 (Figure 5) is used. The delivery company 114C is the identification information for uniquely identifying the delivery company. Shipment origin 114D is identification information of a shipping base in logistics, and uses the same data as shipment origin 113D in the account master data 113 (Figure 5). Loading designation time 114E is a time window of loading time at the logistics center, and is designated by the sender within the range from start time (Fromo) to end time (To). Delivery destination 114F is identification information for uniquely identifying a delivery base in logistics. Unloading designation time 114G is a time window of unloading time at the logistics center, and is designated by the receiver within the range from start time (From) to end time (To). Delivery packaging style 114H is identification information of the packaging style of the delivery, and uses the same data as delivery packaging style 113E in the account master data 113 (Figure 5).

Figure 7 shows an example of the configuration of the receiving location master data 115 in this embodiment.

The receiving location master data 115 is information on recommended berth locations for each storage area defined by the consignee. The receiving location master data 115 includes records in which storage area 115A, recommended berth 1 (115B), recommended berth 2 (115C), and recommended berth 3 (115D) are associated. Storage area 115A is identification information for uniquely identifying a storage area in the consignee's warehouse. Recommended berth 1 (115B), recommended berth 2 (115C), and recommended berth 3 (115D) are identification information for the recommended berths corresponding to the storage area 115A, and the order of priority for use is recommended: recommended berth 1 (115B), recommended berth 2 (115C), and recommended berth 3 (115D).

Figure 8 shows an example of the configuration of order information 121 in this embodiment.

Order information 121 is information placed by a consignee, who is the order source in the commercial flow, to a consignor, who is the order recipient in the commercial flow. Order information 121 includes records that associate a specified delivery date 121A, consignor 121B, consignee 121C, delivery destination 121D, slip number 121E, line number 121F, product code 121G, product quantity 121H, product classification 121I, and storage area 121J, with one record representing one order. Specified delivery date 121A is the delivery date of the product and is specified by the consignee. Consignor 121B is identification information of the consignor, who is the order source in the commercial flow, and uses the same data as consignor 113C in the account master data 113 (Figure 5). The consignee 121C is identification information of the consignee who is the orderer in the commercial flow, and the same data as the consignee 113A in the account master data 113 (FIG. 5) is used. The delivery destination 121D is identification information of the delivery base in the physical distribution, and the same data as the delivery destination 114F in the delivery contract master data 114 (FIG. 6) is used. The slip number 121E is identification information for uniquely identifying the order. The row number 121F is identification information for uniquely identifying the breakdown of one order. The product code 121G is identification information of the product ordered in the row, and the same data as the product code 111A in the product classification master data 111 (FIG. 3) is used. The product quantity 121H is the quantity of the product ordered. The product classification 121I is the classification item of the product ordered, and the smallest granularity data of the product is used among the product classifications 111B to 111D in the product classification master data 111 (FIG. 3). Storage area 121J is identification information for the storage area in which the product is stored within the consignee's warehouse.

Figure 9 shows an example of the configuration of order information by shipping origin 122 in this embodiment.

Order information by shipper 122 is information shared by the shipper, who is the account source, with the shipper, including the account recipient. Order information by shipper 122 includes records that associate the specified delivery date 122A, shipper 122B, shipper 123C, consignee 122D, delivery destination 122E, slip number 122F, line number 122G, product code 122H, product quantity 122I, product classification 122J, storage area 122K, and delivery packaging 122L. The specified delivery date 122A is the delivery date of the product, and the same data as the specified delivery date 121A in the order information 121 (Figure 8) is used. The shipper 122B is identification information of the shipper, who is the order source in the commercial flow, and the same data as the shipper 113C in the account master data 113 (Figure 5) is used. The sender 123C is identification information of a shipping base in terms of logistics, and the same data as the shipper 113D in the account master data 113 (FIG. 5) is used. The receiver 122D is identification information of a receiver who is an order source in terms of commercial flow, and the same data as the receiver 113A in the account master data 113 (FIG. 5) is used. The delivery destination 122E is identification information of a delivery base in terms of logistics, and the same data as the delivery destination 114F in the delivery contract master data 114 (FIG. 6) is used. The slip number 122F is identification information of an order, and the same data as the slip number 121E in the order information 121 (FIG. 8) is used. The row number 122G is identification information of the breakdown of one order, and the same data as the row number 121F in the order information 121 (FIG. 8) is used. The product code 122H is identification information of a product ordered in the row, and the same data as the product code 121G in the order information 121 (FIG. 8) is used. Product quantity 122I is the quantity of the product being ordered, and uses the same data as product quantity 121H in order information 121 (Figure 8). Product classification 122J is the classification item of the product being ordered, and uses the same data as product classification 121I in order information 121 (Figure 8). Storage area 122K is identification information for the storage area in which the product is stored in the receiver's warehouse, and uses the same data as storage area 121J in order information 121 (Figure 8). Delivery packaging style 122L is identification information for the packaging style in which the product is delivered, and uses the same data as delivery packaging style 114H in delivery contract master data 114 (Figure 6).

Figure 10 shows an example of the configuration of delivery request information 123 in this embodiment.

Delivery request information 123 is information provided by the sender to the delivery company to which the sender is requesting delivery. Delivery request information 123 includes records that associate a delivery request number 123A, delivery company 123B, sender 123C, shipper 123D, designated shipping date 123E, designated loading time 123F, receiver 123G, delivery destination 123H, designated delivery date 123I, designated unloading time 123J, delivery packaging style 123K, and packaging quantity 123L. Delivery request number 123A is identification information for uniquely identifying a delivery request. Delivery company 123B is identification information for the delivery company, and the same data as delivery company 114C in the delivery contract master data 114 (Figure 6) is used. The consignor 123C is identification information of the consignor who is the order source in the commercial flow of the delivery request, and the same data as the consignor 121B in the order information 121 (FIG. 8) is used. The shipper 123D is identification information of the shipping base in the physical distribution, and the same data as the shipper 114D in the distribution contract master data 114 (FIG. 6) is used. The designated shipping date 123E is the shipping date of the product, and is designated by the consignor so as to comply with the designated delivery date. The designated loading time 123F is the time window for loading time at the physical distribution center, and the same data as the designated loading time 114E in the distribution contract master data 114 (FIG. 6) is used. The receiver 123G is identification information of the receiver who is the order source in the commercial flow, and the same data as the receiver 121C in the order information 121 (FIG. 8) is used. The delivery destination 123H is identification information of a delivery base in terms of logistics, and uses the same data as the delivery destination 121D in the order information 121 (FIG. 8). The designated delivery date 123I is the delivery date of the product, and uses the same data as the designated delivery date 121A in the order information 121 (FIG. 8). The designated unloading time 123J is the time window for unloading time at the logistics center, and uses the same data as the designated unloading time 114G in the delivery contract master data 114 (FIG. 6). The delivery packaging style 123K is identification information of the packaging style in which the product is delivered, and uses the same data as the delivery packaging style 114H in the delivery contract master data 114 (FIG. 6). The packaging quantity 123L is the total amount of the delivery packaging style in the delivery. If a record associated with the delivery request number 123A is recorded in the delivery package detail data 124 (Figure 11), the number of delivery packages for that delivery request number (the number of delivery package numbers 124B excluding duplicates of the same delivery package number) should be recorded in the package quantity 123L.

Figure 11 shows an example of the configuration of delivery packaging details data 124 in this embodiment.

The delivery packaging details data 124 is information that indicates the relationship between delivery, packaging, and packaging, and is created as a result of the sender's sorting, packaging, and arrangement. The delivery packaging details data 124 includes records that associate a delivery request number 124A, a delivery packaging number 124B, and a delivery packaging number 124C. The delivery request number 124A is identification information for the delivery request, and uses the same data as the delivery request number 123A in the delivery request information 123 (Figure 10). The delivery packaging number 124B is identification information for uniquely identifying the delivery packaging (pallet, basket cart, etc.) included in the delivery request. The delivery packaging number 124C is identification information for uniquely identifying the packaging (cardboard box, etc.) included in the delivery packaging.

Figure 12 shows an example of the configuration of packing details data 125 in this embodiment.

Packing details data 125 is information that indicates the relationship between packaging and products, created as a result of sorting and packaging by the sender. Packing details data 125 includes records that associate delivery packaging number 125A, slip number 125B, line number 125C, product code 125D, and product quantity 125E. Delivery packaging number 125A is packaging identification information, and the same data as delivery packaging number 124C in delivery packaging details data 124 (Figure 11) is used. Slip number 125B is order identification information, and the same data as slip number 122F in order information by shipper 122 (Figure 9) is used. Line number 125C is identification information for the breakdown of one order, and the same data as line number 122G in order information by shipper 122 (Figure 9) is used. Product code 125D is identification information for the product ordered in the row, and uses the same data as product code 122H in order information by shipper 122 (Figure 9). Product quantity 125E is the quantity of the product ordered, and uses the same data as product quantity 122I in order information by shipper 122 (Figure 9).

Figure 13 shows an example of delivery schedule (dispatch result) data 126 in this embodiment.

The delivery schedule (dispatch result) data 126 is information on the scheduled vehicle, loading time, and unloading time for a delivery request, which is created based on an operation plan created by the delivery company based on the delivery request information 123 received. The delivery schedule (dispatch result) data 126 includes records in which a delivery request number 126A, a delivery company 126B, a scheduled vehicle 126C, a scheduled loading time 126D, and a designated unloading time 126E are associated. The delivery request number 126A is identification information for the delivery request, and the same data as the delivery request number 123A in the delivery request information 123 (Figure 10) is used. The delivery company 126B is identification information for the delivery company, and the same data as the delivery company 114C in the delivery contract master data 114 (Figure 6) is used. The scheduled vehicle 126C is identification information for uniquely identifying the vehicle used for the delivery. The planned loading time 126D is the time window for loading at the logistics center, and is input by the delivery company within the range from the start time (Fromo) to the end time (To). The designated unloading time 126E is the time window for unloading at the logistics center, and is input by the delivery company within the range from the start time (From) to the end time (To).

Figure 14A is a diagram showing an example of delivery record data 127-1 in this embodiment, and Figure 14B is a diagram showing an example of delivery record (details) 127-2 in this embodiment.

The delivery record data 127-1 and the delivery record (details) 127-2 are information created as a result of the delivery work performed by the delivery company. The delivery record data 127-1 is work record information corresponding to the delivery request information 123 and the delivery schedule (dispatch result) data 126, and the delivery record (details) 127-2 is work record information corresponding to the delivery packaging details data 124.

The delivery record data 127-1 includes records in which a delivery request number 127A, actual vehicle 127B, actual shipping date 127C, actual delivery date 127D, delivery packaging 127E, and actual quantity 127F are associated. The delivery request number 127A is identification information for the delivery request, and the same data as the delivery request number 123A in the delivery request information 123 (Figure 10) is used. The actual vehicle 127B is identification information for the vehicle used for the delivery, and the same data as the scheduled vehicle 126C in the delivery schedule (dispatch result) data 126 (Figure 13) is used. The actual shipping date 127C is the date on which the shipping work was performed, and is input by the delivery company. The actual delivery date 127D is the date on which the delivery work was performed, and is input by the delivery company. Delivery packaging style 127E is identification information for the packaging style in which the product will be delivered, and uses the same data as delivery packaging style 122L in order information by shipper 122 (FIG. 9). Actual quantity 127F is the quantity of the delivery packaging style in the delivery, and uses the same data as packaging style quantity 123L in delivery request information 120 (FIG. 10).

The delivery record (details) 127-2 includes records in which a delivery request number 127G, a delivery packaging number 127H, a loading operation time 127I, and an unloading operation time 127J are associated. The delivery request number 127G is identification information for the delivery request, and the same data as the delivery request number 123A in the delivery request information 123 (Figure 10) is used. The delivery request number 127G and the delivery request number 127A associate the delivery record (details) 127-2 with the delivery record data 127-1. The delivery packaging number 127H is identification information for the delivery packaging included in the delivery request, and the same data as the delivery packaging number 124C in the delivery packaging details data 124 (Figure 11) is used. The loading operation time 127I is the time when the loading operation was performed, and is input by the delivery company. The unloading operation time 127J is the time when the unloading operation was performed, and is input by the delivery company.

Figure 15 shows an example of operation performance data 128 in this embodiment.

The operation record data 128 is information created as a result of delivery work by the delivery company's crew, and includes records that associate operation date 128A, delivery company 128B, actual vehicle 128C, destination 128D, departure time 128E, and arrival time 128F. Operation date 128A is the date on which the vehicle performed the operation. Delivery company 128B is identification information of the delivery company, and the same data as delivery company 114C in delivery contract master data 114 (Figure 6) is used. Actual vehicle 128C is identification information of the vehicle used in the operation, and the same data as scheduled vehicle 126C in delivery schedule (dispatch result) data 126 (Figure 13) is used. Destination 128D is identification information of the delivery base in terms of logistics. Departure time 128E is the time when the operation started. Arrival time 128F is the time when the operation ended.

Figure 16 shows an example of delivery forecast/actual data 129 in this embodiment.

The delivery forecast/actual data 129 is information that compiles information entered by the sender and the delivery company's work schedule and work results. As the delivery work progresses, the less accurate planned information is replaced with more accurate actual information.

The delivery forecast/actual data 129 includes records that associate a delivery request number 129A, a delivery company 129B, a delivery vehicle 129C, a consignor 129D, a shipper 129E, a shipping date 129F, a loading time 129G, a consignee 129H, a delivery destination (a logistics delivery base) 129I, a delivery date 129J, a loading time 129K, a delivery package 129L, and a package quantity 129M.

Delivery request number 129A is identification information of the delivery request, and before the delivery company starts operating, the same data as delivery request number 123A in delivery request information 123 (Fig. 10) is used, or after the delivery company starts operating, the same data as delivery request number 123A in delivery record data 127-1 (Fig. 14A) is used. Delivery company 129B is identification information of the delivery company, and the same data as delivery company 126B in delivery schedule (dispatch result) data 126 (Fig. 13) is used. Delivery vehicle 129C is a vehicle number. Before the delivery company starts operating, the same data as scheduled vehicle 126C in delivery schedule (dispatch result) data 126 (Fig. 13) associated with delivery request number 129A is used, or after the delivery company starts operating, the same data as actual vehicle 127B in delivery record data 127-1 (Fig. 14A) associated with delivery request number 129A is used.

Shipper 129D is identification information of the shipper who is the order source in the commercial flow of the delivery request, and the same data as that of shipper 123C in delivery request information 123 (Figure 10) is used. Shipper 129E is identification information of the shipping base in terms of logistics, and the same data as that of shipper 123D in delivery request information 123 (Figure 10) is used. Shipping date 129F is the date of shipping, and before the delivery company begins operating, the same data as that of designated shipping date 123E in delivery request information 123 (Figure 10) associated with delivery request number 129A, or after the delivery company begins operating, the same data as that of actual shipping date 127C in delivery performance data 127-1 (Figure 14A) associated with delivery request number 129A is used. Loading time 129G is the time window for loading at the logistics center, and before the delivery company begins operation, the same data as the minimum and maximum of loading designated time 123F in delivery request information 123 (FIG. 10) associated with delivery request number 129A, or when the delivery company is dispatched, loading schedule time 126D in delivery schedule (dispatch result) data 126 (FIG. 13) associated with delivery request number 129A, or when the delivery company is working, loading operation time 127I in delivery record (details) 127-2 (FIG. 14B) associated with delivery request number 129A is used.

The consignee 129H is identification information of the consignee who is the orderer in the commercial flow, and uses the same data as the consignee 123G in the delivery request information 123 (Fig. 10). The delivery destination 129I is identification information of the delivery base in the physical distribution, and uses the same data as the delivery destination 123H in the delivery request information 123 (Fig. 10). The delivery date 129J is the date of delivery, and uses the same data as the designated delivery date 123I in the delivery request information 123 (Fig. 10) associated with the delivery request number 129A when the sender makes a delivery request, or the same data as the actual delivery date 127D in the delivery record data 127-1 (Fig. 14A) associated with the delivery request number 129A when the delivery company is working.

The unloading time 129K is the time window for unloading time at the logistics center, and uses the same data as the minimum and maximum of the unloading designated time 123J in the delivery request information 123 (Figure 10) associated with the delivery request number 129A when the shipper makes a delivery request, the designated unloading time 126E in the delivery schedule (dispatch result) data 126 (Figure 13) associated with the delivery request number 129A when the delivery company is dispatched, or the predicted arrival time calculated based on the delivery record data 127-1 (Figure 14A) and operation record data 128 (Figure 15) associated with the delivery vehicle 129C when the delivery company is loading, or the minimum and maximum of the unloading work time 127J in the delivery record (details) 127-2 (Figure 14B) associated with the delivery request number 129A when the delivery company is completed. Delivery style 129L is identification information of the style of delivery in which the product is delivered, and uses the same data as delivery style 127E in delivery record data 127-1 (Fig. 14A). Packaging quantity 129M is the quantity of delivery styles in the delivery, and after the sender's delivery request, uses the same data as packaging quantity 123L in delivery request information 123 (Fig. 10) associated with delivery request number 129A, or during delivery company work, uses the same data as actual quantity 127F in delivery record data 127-1 (Fig. 14A) associated with delivery request number 129A.

Figure 17 shows an example of delivery details data 130 in this embodiment.

The delivery details data 130 includes product details corresponding to the delivery package numbers of the products loaded and unloaded by the delivery company, as well as information on the product classification, storage area, and recommended berth for each product.

The delivery details data 130 includes records associated with a delivery request number 130A, a delivery package number 130B, loading time 130C, unloading time 130D, a delivery packaging number 130E, a slip number 130F, a line number 130G, a product code 130H, a product quantity 130I, a product classification 130J, a storage area 130K, and a recommended berth 130L.

Delivery request number 130A is identification information for the delivery request, and uses the same data as delivery request number 129A in delivery forecast/actual data 129 (Figure 16). Delivery packaging number 130B is identification information for the delivery packaging, and uses the same data as delivery packaging number 127H in delivery record (details) 127-24 (Figure 14B), and is left blank if the items have not yet been sorted. Loading operation time 130C is the time of loading at the logistics center, and uses the same data as loading operation time 127I in delivery record (details) 127-2 (Figure 14B) that is associated with delivery request number 130A and delivery packaging number 130B. Unloading time 130D is the time of unloading at the logistics center, and uses the same data as unloading time 127J in delivery record (details) 127-2 (FIG. 14B) associated with delivery request number 130A and delivery packaging number 130B. Delivery packaging number 130E is identification information of the delivery packaging included in the delivery request, and uses the same data as delivery packaging number 127H in delivery record (details) 127-2 (FIG. 14B) associated with delivery request number 130A and delivery packaging number 130B, and is left blank if the product is not packaged.

The slip number 130F is the identification information of the order, and the same data as the slip number 125B in the packing details data 125 (Fig. 12) is used. The row number 130G is the identification information of the breakdown of one order, and the same data as the row number 125C in the packing details data 125 (Fig. 12) is used. The product code 130H is the identification information of the product ordered in the row, and the same data as the product code 125D in the packing details data 125 (Fig. 12) is used. The product quantity 130I is the quantity of the product ordered, and the same data as the product quantity 125E in the packing details data 125 (Fig. 12) associated with the delivery package number 130E, the slip number 130F, the row number 130G, and the product code 130H is used. The product classification 130J is an item set for each product. The product classification 122J is the classification item of the product ordered, and the same data as the product classification 122J in the order information by shipper 122 (Fig. 9) is used. Storage area 130K is identification information for the storage area in which the product is stored in the consignee's warehouse, and uses the same data as storage area 122K in order information by shipper 122 (Figure 9). Recommended berth 130L is identification information for the recommended berth that corresponds to storage area 130K, and uses the same data as recommended berths 115B to 115D in receiving location master data 115 (Figure 7).

Figure 18 is a flowchart showing an example of the order information/shipment-specific order information creation process executed by the processing program 150 of the management device 1 in this embodiment.

The order information and shipment-specific order information creation process is executed, for example, when the consignee places an order, and creates order information 121 based on the consignee's order, and creates order information 122 by shipper from the order information 121.

First, the processing program 150 records the specified delivery date 121A, sender (order recipient in the commercial flow) 121B, receiver (order recipient in the commercial flow) 121C, delivery destination (delivery base in the physical distribution) 121D, slip number 121E, line number 121F, product code 121G, and product quantity 121H of the order information 121 based on the order information received from the receiver's office terminal device 401 (step S101).

Next, the processing program 150 refers to the product classification master data 111 to identify the product code 111A that is the same as the product code 121G in the order information 121, obtains the product classifications 111B to 111D that correspond to the product code 111A, and records the obtained product classification in the product classification 121I in the order information 121 (step S102).

The recorded product classification 121I may be all or some of the major product classification 111B, the medium product classification 111C, and the minor product classification 111D. In the example shown in FIG. 8, the recorded product classification is the minor product classification 111D when all of the major product classification 111B, the medium product classification 111C, and the minor product classification 111D are assigned, the medium product classification 111C when the minor product classification 111D is not assigned and the major product classification 111B and the medium product classification are assigned, and the major product classification 111B when only the major product classification 111B is assigned, but the product classification may be recorded in another format.

Next, the processing program 150 refers to the storage area master data 112 to identify the product classification 112A that is the same as the product classification 121I of the order information 121, obtains a storage area from the area levels 112B to 112D that correspond to the product classification 112A, and records the obtained storage area in the storage area 121J of the order information 121 (step S103).

The recorded storage area may be all or some of area level 1 (112B), area level 2 (112C), and area level 3 (112D). In the example shown in FIG. 8, the recorded storage area is area level 3 (112D) if all of area level 1 (112B), area level 2 (112C), and area level 3 (112D) are assigned; area level 2 (112C) if area level 3 (112D) is not assigned and area level 1 (112B) and area level 2 (112C) are assigned; and area level 3 (112D) if only area level 3 (112D) is assigned; however, the storage area may be recorded in another format.

Next, the processing program 150 refers to the accounting master data 113 to identify the combination of consignee 113A, product code 113B, and consignee 113C that is the same as the combination of consignee 121C, product code 121G, and consignee 121B in the order information 121, and obtains the shipping origin 113D and delivery packaging style 113E that correspond to the combination of consignee 113A, product code 113B, and consignee 113C (step S104).

Next, the processing program 150 records the specified delivery date 121A, sender 121B, receiver 121C, delivery destination 121D, invoice number 121E, line number 121F, product code 121G, product quantity 121H, product classification 121I and storage area 121J of the order information 121 in the specified delivery date 122A, sender 122B, receiver 122D, delivery destination 122E, invoice number 122F, line number 122G, product code 122H, product quantity 122I, product classification 122J and storage area 122K of the order information by shipper 122, respectively. Furthermore, the processing program 150 records the acquired shipping origin 113D and delivery packaging style 113E in the consignor 123C and delivery packaging style 122L of the corresponding record in the order information by shipping origin 122, and creates the order information by shipping origin 122 (step S105).

Figure 19 is a flowchart showing an example of an operation record creation process executed by the processing program 150 of the management device 1 of this embodiment, which creates various data such as operation records from the order information by shipper 122. Specifically, the operation record creation process creates delivery request information 123, delivery packing details data 124, packing details data 125, delivery schedule (dispatch result) data 126, delivery record data 127-1, delivery record (details) 127-2, and operation record data 128 from the order information by shipper 122.

First, the processing program 150 refers to the delivery contract master data 114 to identify a record corresponding to the combination of the sender 122B, the sender 123C, the receiver 122D, and the delivery destination 122E in the order information by shipper 122, and obtains the delivery company 114C, the designated loading time 114E, and the designated unloading time 114G of the identified record (step S201).

Next, the processing program 150 records the designated delivery date 122A, sender 122B, sender 123C, receiver 122D, delivery destination 122E, and delivery style 122L of the order information by shipper 122 in the designated delivery date 123I, sender 123C, shipper 123D, receiver 123G, delivery destination 123H, and delivery style 123K of the delivery request information 123. The processing program 150 also records the delivery company 114C, designated loading time 114E, and designated unloading time 114G in the delivery company 123B, designated loading time 123F, and designated unloading time 123J of the delivery request information 123. Furthermore, the processing program 150 records the delivery request number, which is identification information assigned by the processing program 150 to each delivery request, the designated shipping date specified by the consignor when making the delivery request, and the planned or confirmed package quantity in the delivery request number 123A, designated shipping date 123E, and package quantity 123L of the delivery request information 123, respectively. In this way, the delivery request information 123 is created (step S202). Steps S201 and S202 are executed, for example, when the consignor makes a delivery request.

Then, the processing program 150 records the delivery packaging style and packaging information associated with the delivery request number 123A of the delivery request information 123, which is created as a result of the shipper's sorting and shipment arrangement, in the delivery packaging style number 124B and delivery packaging number 124C of the delivery packaging style detail data 124, respectively, to create the delivery packaging style detail data 124. In addition, the processing program 150 records the product information associated with the delivery request number 123A of the delivery request information 123 in the product code 125D and product quantity 125E of the packing detail data 125 to create the packing detail data 125 (step S203).

Then, the processing program 150 records the delivery company, scheduled vehicle, scheduled loading time, and scheduled unloading time created as a result of the delivery company's dispatch planning work in the delivery company 126B, scheduled vehicle 126C, scheduled loading time 126D, and designated unloading time 126E of the corresponding delivery request number 126A in the delivery schedule (dispatch result) data 126, and creates the delivery schedule (dispatch result) data 126 (step S204).

Note that steps S203 and S204 may be executed in the order described above, simultaneously, or in the order of steps S204 and S203.

Then, the processing program 150 records the delivery record created in conjunction with the delivery work of the delivery company (for example, at the time of the delivery work by the delivery company's crew) in the actual vehicle 127B, actual shipping date 127C, actual delivery date 127D, delivery packaging style 127E and actual quantity 127F of the corresponding delivery request number 127A in the delivery record data 127-1, and the delivery request number 127G, delivery packaging style number 127H, loading work time 127I and unloading work time 127J of the delivery record (details) 127-2, and creates the delivery record data 127-1 and the delivery record (details) 127-2. Furthermore, the processing program 150 records the operation history created in association with the delivery work of the delivery company in the operation date 128A, delivery company 128B, actual vehicle 128C, destination 128D, departure time 128E, and arrival time 128F of the operation history data 128, and creates the operation history data 128 (step S205).

Figure 20 is a flowchart showing an example of the delivery forecast/actual/delivery detail creation process executed by the processing program 150 of the management device 1 in this embodiment.

First, the processing program 150 obtains data corresponding to the delivery request number from the delivery request information 123, delivery packing details data 124, packing details data 125, delivery schedule (dispatch result) data 126, delivery performance data 127, and operation performance data 128, as described above (explanation of Figures 16 and 17), and obtains the delivery request number 129A, delivery company 129B, delivery vehicle 129C, consignor 129D, shipper 129E, shipping date 129F, loading time 129G, consignee 129H, The processing program 150 records the information in the delivery destination 129I, delivery date 129J, unloading time 129K, delivery package style 129L and package quantity 129M, and records the information in the delivery request number 130A, delivery package style number 130B, loading time 130C, unloading time 130D, delivery packaging number 130E, slip number 130F, line number 130G, product code 130H, product quantity 130I, product classification 130J and storage area 130K of the delivery detail data 130, thereby generating delivery forecast/actual data 129 and delivery detail data 130. Furthermore, the processing program 150 refers to the receiving location master data 115 to obtain a recommended berth corresponding to the same storage area 115A as the storage area 130K of the delivery detail data 130. The processing program 150 then records the obtained recommended berth in the recommended berth 130L of the delivery detail data 130 (step S301). The processing of step S301 is executed when the sender, the delivery company, and the receiver refer to the information, and the delivery forecast/actual data 129 and the delivery detail data 130 are updated with the latest data.

The processing program 150 references the delivery packaging number 130B in the delivery detail data 130 to determine whether the items have not yet been sorted (step S302). Then, in response to a request from the sender, the processing program 150 outputs information on the product classification 130J and storage area 130K (see, for example, Figures 22A to 22B) for each delivery request number 130A at the timing before sorting (step S303).

The processing program 150 also references the arrival time 128F in the operation history data 128 to determine whether a delivery operation is in progress (step S304). Then, in response to a request from the receiver, the processing program 150 outputs information on the product-specific recommended berth 130L for each delivery vehicle 129C during the delivery operation (step S305). In addition, in response to a request from the receiver, the processing program 150 outputs the unloading time 129K for each delivery vehicle 129C during the delivery operation as scheduled delivery time information (e.g., see Figures 21A to 21C) (step S306).

The processing program 150 also references the arrival time 128F in the operation record data 128 and the unloading operation time 130D in the delivery detail data 130 to determine whether the time has passed since the vehicle arrived but before acceptance (step S307). Then, in response to a request from the recipient, the processing program 150 outputs the product code 130H, product quantity 130I, product classification 130J, and storage area 130K for each delivery vehicle 129C after the vehicle has arrived but before acceptance as loaded product information (see, for example, Figures 21A to 21C) (step S308).

The processing program 150 also references the unloading time 130D in the delivery details data 130 to determine whether the unloading has occurred (step S309). Then, in response to a request from the recipient, the processing program 150 outputs the delivery details data 130 as delivery information (e.g., see Figures 21A to 21C) after the unloading has occurred (step S310).

The processing program 150 also references the unloading operation time 130D in the delivery details data 130 to determine whether the delivery operation has been completed (step S311). If the delivery operation has been completed, the delivery forecast/actual and delivery details creation process is terminated, and if the delivery operation has not been completed, the process returns to step S301 and continues.

In addition, the information output at each step of the delivery forecast/actual/delivery detail creation process may be displayed on a display or output to another system (e.g., a warehouse management system).

Figures 21A to 21C show examples of delivery status reference screens that can be viewed by the recipient.

On the delivery status reference screen shown in FIG. 21A, when search conditions are entered by operating the search condition button on the left side of the screen corresponding to the item to be searched, at least some of the items (items that the consignee should refer to) of the data stored in the delivery forecast/actual data 129 and the delivery detail data 130 that match the search conditions are displayed. For example, the scheduled delivery time displays the unloading time 129K of the delivery forecast/actual data 129 (FIG. 16); that is, when the sender makes a delivery request, the designated unloading time 123J of the delivery request information 123 (FIG. 10) associated with the delivery request number 129A is displayed; when the delivery company is dispatched, the designated unloading time 126E of the delivery schedule (dispatch result) data 126 (FIG. 13) associated with the delivery request number 129A is displayed; when the delivery company is loading, the predicted arrival time calculated based on the delivery performance data 127-1 (FIG. 14A) and operation performance data 128 (FIG. 15) associated with the delivery vehicle 129C is displayed; or when the delivery company is finished with its work, the minimum and maximum values of the unloading work time 127J of the delivery performance (details) 127-2 (FIG. 14B) associated with the delivery request number 129A are displayed.

When a row on the screen is selected, the delivery status reference screen (details 1) shown in FIG. 21B or the delivery status reference screen (details 2) shown in FIG. 21C is displayed. The delivery status reference screen (details 1) shown in FIG. 21B displays basic items of the delivery status (delivery date, supplier, shipping base, vehicle number, etc.), while the delivery status reference screen (details 2) shown in FIG. 21C displays detailed information for each product (storage area level, delivery packing style, packing style quantity, total number of products, recommended berth, etc.) corresponding to one record of the delivery detail data 130.

By presenting the delivery status reference screen to the recipient, the recipient can learn when, what, and how many items the delivery vehicle will be carrying before it arrives based on the number of vehicles scheduled to enter, the scheduled vehicle number, and the number of packages by arrival area (product classification).

More specifically, delivery information including product code, product quantity, and delivery packaging is output in response to the request of the recipient, so that the recipient can inspect each package without having to check whether the product is present or not, by matching the delivery packaging (e.g., a basket cart), packaging information within the delivery packaging (e.g., a cardboard box), and the product code of the packaged product, thereby making warehousing operations more efficient. In addition, the workload of inspection and shelving can be known before the delivery vehicle arrives, allowing for efficient planning of receiving and inspection operations.

In addition, delivery information including product codes and berths is output in response to requests from the recipient, so the recommended berth for the products contained in the packages loaded on the vehicle can be known before delivery, and a berth close to the storage area for the products that are frequently contained in the packages to be delivered can be selected, allowing for efficient berth allocation planning and streamlining of warehousing operations.

In addition, delivery information including the product code and the scheduled unloading time is output in response to the request of the recipient, so that the loading berth, personnel deployment, and material handling equipment deployment such as forklifts can be changed in advance according to the expected arrival date of the product, making warehousing operations more efficient.

In addition, delivery information including the product code and the planned vehicle is output upon request from the recipient, so the loaded product can be identified from the vehicle number without the need for reception work on the premises, eliminating the need for reception work and berth guidance, and streamlining the warehousing process.

Figures 22A and 22B show examples of delivery status reference screens that can be viewed by shippers.

On the delivery status reference screen shown in FIG. 22A, when search conditions are entered by operating the search condition button on the left side of the screen corresponding to the item to be searched, at least some of the items of data that match the search conditions (items that the shipper should refer to) stored in delivery forecast/actual data 129 and delivery detail data 130 are displayed. Then, when a row on the screen is selected, the delivery status reference screen (details) shown in FIG. 22B is displayed. The delivery status reference screen (details) shown in FIG. 22B displays details of the delivery status (product code, product name, row number, quantity, storage area, product classification, etc.).

By presenting the sender with a delivery status reference screen, they can refer to the issuance and progress of transportation requests based on delivery requirements, based on information on scheduled pickup and delivery (vehicle number and time) and actual pickup and delivery results (delivery completion).

More specifically, delivery information including product code and storage area is output in response to the sender's request, so products in the same storage area can be packed in the same packaging, improving the sender's service level. Products in the same storage area can be packed in the same packaging, making the receiver's warehousing process more efficient.

Figures 23A to 23C show examples of delivery status reference screens that delivery companies can view.

In the delivery status reference screen shown in FIG. 23A, when search conditions are entered by operating the search condition button on the left side of the screen corresponding to the item to be searched, at least some of the items (items that the delivery company should refer to) of the data that matches the search conditions among the data stored in delivery forecast/actual data 129 and delivery detail data 130 are displayed.

When a row on the screen is selected, the delivery status reference screen (details 1) shown in FIG. 23B or the delivery status reference screen (details 2) shown in FIG. 23C is displayed. The delivery status reference screen (details 1) shown in FIG. 23B displays basic items of the delivery status (delivery date, supplier, shipping base, vehicle number, etc.), while the delivery status reference screen (details 2) shown in FIG. 23C displays detailed information for each product (storage area level, delivery packing style, packing style quantity, total number of products, recommended berth, etc.) corresponding to one record of the delivery detail data 130.

By showing the delivery status reference screen to the delivery company, the vehicle driver can share the information registered by the delivery company, such as the package quantity, package quantity, product quantity corresponding to the delivery package, and recommended berth, and can know the details of the cargo corresponding to the transportation request. In addition, the delivery berth can be reserved early.

The present invention is not limited to the above-described embodiments, but includes various modified examples and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to having all of the configurations described. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added, deleted, or replaced with other configurations.

Furthermore, each of the configurations, functions, processing units, processing means, etc. described above may be realized in part or in whole in hardware, for example by designing them as integrated circuits, or may be realized in software by a processor interpreting and executing a program that realizes each function.

Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, hard disk, or SSD (Solid State Drive), or in a recording medium such as an IC card, SD card, or DVD.

In addition, the control lines and information lines shown are those considered necessary for explanation, and do not necessarily represent all control lines and information lines necessary for implementation. In reality, it is safe to assume that almost all components are interconnected.

1 Management device 5 Network 6 Information processing system 10 Storage device 11 Processor 12 Memory 13 Input interface 14 Output interface 15 Communication device 111 Product classification master data 112 Storage area master data 113 Accounting master data 114 Delivery contract master data 115 Receiving location master data 120 Delivery request information 121 Order information 122 Shipment origin order information 123 Delivery request information 124 Delivery packing style details data 125 Packing details data 126 Data 127 Delivery record data 128 Operation record data 129 Delivery forecast actual data 130 Delivery details data 150 Processing program 201 Accounting origin office terminal device 202 Accounting origin shipping base terminal device 203 Accounting destination office terminal device 204 Accounting destination shipping base terminal device 301 Delivery company office terminal device 302 Driver terminal device 401 Consignee office terminal device 402 Delivery base terminal device

Claims (5)

A management device,
The computer includes a computing device that executes a predetermined calculation process and a storage device that is connected to the computing device,
The storage device stores account master data in which product codes and delivery forms are recorded in correspondence with each other, product classification master data in which product codes and product classifications are recorded in correspondence with each other, storage area master data in which product classifications and product storage areas are recorded in correspondence with each other, and receiving location master data in which product storage areas and vehicle arrival berths are recorded in correspondence with each other ,
The computing device includes:
storing order information including the product code and the product quantity input by the recipient in the storage device;
By referring to the account master data, a delivery form corresponding to the product code included in the order information is identified;
Identifying a berth corresponding to the product code included in the order information by referring to the product classification master data, the storage area master data, and the receiving location master data;
A management device which outputs delivery information including the product code, the product quantity , the delivery packaging style , and the berth in response to a request from a consignee. The management device according to claim 1 ,
The computing device includes:
By referring to the product classification master data and the storage area master data, a storage area corresponding to the product code included in the order information is identified;
A management device which outputs delivery information including the product code and the storage area in response to a request from a shipper. The management device according to claim 1 ,
The storage device includes:
Delivery information recorded by matching a delivery request number for uniquely identifying the delivery with the scheduled unloading time;
Delivery package detail data in which the delivery request number and the delivery package number for uniquely identifying the delivery package are recorded in correspondence with each other;
Store the packing details data that records the delivery packing number and product code in correspondence with each other,
The computing device includes:
By referring to the packing details data, the delivery package details data, and the delivery information, a planned unloading time corresponding to the product code included in the order information is identified;
A management device which outputs the delivery information including the product code and the scheduled unloading time in response to a request from a recipient. The management device according to claim 1 ,
The storage device includes:
Delivery information recorded by matching a delivery request number for uniquely identifying a delivery with a scheduled vehicle;
Delivery package detail data in which the delivery request number and the delivery package number for uniquely identifying the delivery package are recorded in correspondence with each other;
Store the packing details data that records the delivery packing number and product code in correspondence with each other,
The computing device includes:
By referring to the packing details data, the delivery package details data, and the delivery information, a planned vehicle corresponding to a product code included in the order information is identified;
A management device which outputs the delivery information including the product code and the scheduled vehicle in response to a request from a consignee. A logistics information management method executed by a management device, comprising:
the management device is configured by a computer having a calculation device that executes a predetermined calculation process and a storage device connected to the calculation device;
The storage device stores account master data in which product codes and delivery forms are recorded in correspondence with each other, product classification master data in which product codes and product classifications are recorded in correspondence with each other, storage area master data in which product classifications and product storage areas are recorded in correspondence with each other, and receiving location master data in which product storage areas and vehicle arrival berths are recorded in correspondence with each other,
The logistics information management method includes:
The arithmetic unit stores the order information including the product code and the product quantity input by the consignee in the storage unit,
The computing device refers to the account master data and identifies a delivery form corresponding to the product code included in the order information,
The computing device refers to the commodity classification master data, the storage area master data, and the receiving location master data, and identifies a berth corresponding to the commodity code included in the order information;
The logistics information management method according to the present invention, characterized in that the computing device outputs delivery information including the product code, the product quantity, the delivery packaging form, and the berth in response to a request from a consignee.

Images