Cargo and vehicle request system, server device, and program

Abstract

To increase the number of cargo delivery contracts accepted by a transportation business operator and to enable persuasive price negotiation by presenting a price with a clear basis to a shipper. [Solution] The system determines whether delivery is possible based on the current loading condition (ST102), and if delivery is not possible based on the current loading condition (No in ST102), determines whether delivery is possible based on the loading condition predicted based on the current delivery plan (ST105), and if delivery is not possible based on the loading condition predicted based on the current delivery plan (No in ST105), determines whether delivery is possible based on the loading condition predicted based on a revised proposal for the delivery plan (ST108), and if delivery is not possible based on the loading condition predicted based on the revised proposal for the delivery plan (No in ST108), creates an alternative plan in which the delivery conditions specified by the shipper are changed so that actual delivery is possible (ST109), and presents the alternative plan to the shipper.

Description

[Technical field]

[0001] The present invention relates to a cargo and vehicle request system, a server device, and a program for executing a process of examining the possibility of delivery of a cargo based on delivery conditions designated by a shipper and providing a response based on the result to the shipper. [Background technology]

[0002] A cargo and vehicle request system is known that compares the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the shipper with the availability (loading status) of trucks currently in operation by the transportation company, and matches the shipper's requests regarding trucks to deliver cargo with the transportation company's requests regarding cargo to be loaded onto the trucks (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-196479 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the cargo and vehicle request system, as in the conventional technology, the possibility of delivery of a cargo is determined based on information (vacant vehicle information) about trucks that can deliver the cargo under the delivery conditions specified by the shipper, but since the loading status of the truck changes during the delivery process, it is desirable to determine the possibility of delivery based on the loading status predicted based on the delivery plan. However, the conventional technology does not take such a perspective into consideration at all, and there is a problem that it is not possible to sufficiently increase the number of cargo delivery contracts accepted by the transportation company or to present a price with a clear basis to the shipper and conduct persuasive price negotiations.

[0005] Therefore, the main object of the present invention is to provide a cargo and vehicle request system, server device, and program that can increase the number of cargo delivery assignments accepted by a transportation company and also enable persuasive price negotiations by presenting prices with clearly-founded reasons to shippers. [Means for solving the problem]

[0006] The cargo and vehicle request system of the present invention is a cargo and vehicle request system in which one or more processors execute a process of examining the possibility of delivery of a cargo based on delivery conditions designated by a cargo owner and providing a response to the cargo owner based on the result, and the processor determines the possibility of delivery according to the loading condition predicted based on the delivery plan when the cargo cannot be delivered based on the delivery conditions designated by the cargo owner with the loading condition at the time of receiving an inquiry about cargo delivery from the cargo owner, Due to a change in the timing of collection of the above-mentioned packages If delivery is deemed possible, The change in collection timing will be reflected in the increase in handling work volume and travel distance. The price to be offered to the shipper is set.

[0007] The server device of the present invention is a server device in which one or more processors execute a process of examining the possibility of delivery of a package based on delivery conditions designated by a shipper and providing a response to the shipper based on the result of the examination, and the processor determines the possibility of delivery according to the loading condition predicted based on the delivery plan when the package cannot be delivered based on the delivery conditions designated by the shipper with the loading condition at the time of receiving an inquiry about package delivery from the shipper, and Due to a change in the timing of collection of the above-mentioned packages If delivery is deemed possible, The change in collection timing will be reflected in the increase in handling work volume and travel distance. The price to be offered to the shipper is set.

[0008] The program of the present invention is a program that causes one or more processors to execute a process of examining the possibility of delivery of a package based on delivery conditions designated by a shipper and providing a response to the shipper based on the result of the process, and in the case where the cargo condition at the time of receiving an inquiry about package delivery from the shipper does not allow delivery of the package based on the delivery conditions designated by the shipper, the program determines the possibility of delivery according to the cargo condition predicted based on the delivery plan, Due to a change in the timing of collection of the above-mentioned packages If delivery is deemed possible, The change in collection timing will be reflected in the increase in handling work volume and travel distance. The price to be offered to the shipper is set. Effect of the Invention

[0009] According to the present invention, the possibility of delivery is considered based on the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the shipper, and in particular, when the cargo cannot be delivered based on the current loading condition, the possibility of delivery is judged according to the loading condition predicted based on the delivery plan. This allows the number of cargo deliveries accepted by the transport company to be increased, and also allows the shipper to be presented with a price with a clear basis for persuasive price negotiations. [Brief description of the drawings]

[0010] [Figure 1] Overall configuration diagram of a freight and vehicle request system according to the present embodiment. [Diagram 2] An explanatory diagram showing the case classification performed in the delivery condition analysis process performed on the cargo and vehicle request server. [Diagram 3] FIG. 1 is an explanatory diagram showing an example of a truck loading state corresponding to the first case. [Figure 4] FIG. 11 is an explanatory diagram showing an example of a truck loading state corresponding to the second case. [Diagram 5] FIG. 11 is an explanatory diagram showing an example of a truck loading state corresponding to the third case. [Figure 6] Block diagram showing the schematic configuration of the cargo and vehicle request server and the delivery management server [Figure 7] An explanatory diagram showing the registered contents of the delivery information database and the cargo request information database. [Figure 8] A sequence diagram showing an overview of the processing performed by this system when presenting cargo request information to a shipper. [Figure 9] A sequence diagram showing an overview of the processing performed by this system when presenting cargo request information to a shipper. [Figure 10] A sequence diagram showing an overview of the processing performed by this system when cargo request information is not presented to the shipper [Figure 11]A sequence diagram showing an overview of the processing performed by this system when cargo request information is not presented to the shipper [Figure 12] Flow diagram showing the procedure of processing performed by the cargo and vehicle request server [Figure 13] Flow diagram showing the processing steps performed by the delivery management server DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The first invention made to solve the above problems is a cargo and vehicle request system in which one or more processors execute a process of examining the possibility of delivery of a cargo based on delivery conditions designated by a shipper and providing a response to the shipper based on the result, and the processor determines the possibility of delivery according to the loading condition predicted based on a delivery plan when the cargo cannot be delivered based on the delivery conditions designated by the shipper with the loading condition at the time of receiving an inquiry about cargo delivery from the shipper, Due to a change in the timing of collection of the above-mentioned packages If delivery is deemed possible, The change in collection timing will be reflected in the increase in handling work volume and travel distance. The price to be offered to the shipper is set.

[0012] According to this, the possibility of delivery is considered based on the delivery conditions specified by the shipper (delivery date, arrival time, delivery destination, etc.), and in particular, when the cargo cannot be delivered based on the current loading condition, the possibility of delivery is judged according to the loading condition predicted based on the delivery plan. This allows the transportation company to increase the number of cargo deliveries it accepts, and also allows it to present a price with a clear basis to the shipper and conduct persuasive price negotiations.

[0013] In addition, in a second invention, when the cargo cannot be delivered based on the delivery conditions designated by the shipper with the cargo state predicted based on the delivery plan, the processor determines whether delivery is possible according to the cargo state predicted based on a revised delivery plan obtained by changing the order of unloading, and when it is determined that delivery is possible, Reflecting the increase in handling volume and distance traveled The price to be offered to the shipper is set.

[0014] According to this, when a package cannot be delivered based on the loading status predicted based on the delivery plan, the possibility of delivery is judged according to the loading status predicted based on the revised delivery plan. This allows the transportation company to further increase the number of package deliveries it accepts, and also allows it to present a price with a clear basis to the shipper and conduct persuasive price negotiations.

[0016] This allows a price based on a clear basis to be presented to the shipper. The price may be set to reflect the amount of waiting time increase in addition to the amount of cargo handling work and the distance traveled. The price may also be set according to the number of cargo deliveries accepted on the day.

[0017] Also, 3 In the invention, when delivery is not possible with the loading status predicted based on the revised delivery plan proposal, the processor creates an alternative plan based on cargo request information, which is information about cargo desired by the transportation company, in which at least one or more of the delivery conditions specified by the shipper, including the delivery date, arrival time, collection time, and delivery destination of the cargo, is changed so as to make actual delivery possible, and presents the alternative plan to the shipper.

[0018] According to this, even if a shipper's cargo cannot be delivered even after revising the delivery plan, if the shipper accepts an alternative plan, the cargo delivery can be accepted, thereby preventing the transport company from losing the opportunity to accept the cargo delivery.

[0019] Also, 4 The invention is configured such that the processor updates cargo request information regarding deliverable cargo and its delivery conditions based on the latest information regarding cargo loaded onto transport vehicles, and considers the possibility of delivering the cargo based on the cargo request information.

[0020] This makes it possible to present the latest cargo request information to the shipper, and to respond to inquiries about cargo delivery from the shipper based on the latest cargo request information.

[0021] Also, 5The invention includes a first server device that manages cargo request information and a second server device that manages a delivery plan, wherein the processor provided in the second server device executes a loading status prediction process that predicts a loading status based on the delivery plan and a delivery plan review process that creates a revised proposal for the delivery plan, and the processor provided in the first server device executes a delivery condition analysis process that considers the possibility of delivering a cargo based on delivery conditions specified by a shipper, based on the results of the loading status prediction process and the delivery plan review process.

[0022] This allows the two server devices to work together to appropriately perform the required processing.

[0023] Also, 6 The invention is a server device in which one or more processors execute a process of examining the possibility of delivery of a package based on delivery conditions designated by a shipper and providing a response to the shipper based on the result of the process, and when the cargo condition at the time of receiving an inquiry about cargo delivery from the shipper makes it impossible to deliver the package based on the delivery conditions designated by the shipper, the processor determines the possibility of delivery according to the cargo condition predicted based on a delivery plan, Due to a change in the timing of collection of the above-mentioned packages If delivery is deemed possible, The change in collection timing will be reflected in the increase in handling work volume and travel distance. The price to be offered to the shipper is set.

[0024] Like the first invention, this enables the transportation company to increase the number of parcel deliveries it accepts, and also enables it to present prices with clearly-founded reasons to shippers, enabling persuasive price negotiations.

[0025] Also, 7 The invention is a program that causes one or more processors to execute a process of considering the possibility of delivery of a package based on delivery conditions designated by a shipper and providing a response to the shipper based on the result of the process. In the case where the cargo condition at the time of receiving an inquiry about cargo delivery from the shipper does not allow the cargo to be delivered based on the delivery conditions designated by the shipper, the program determines the possibility of delivery according to the cargo condition predicted based on the delivery plan, Due to a change in the timing of collection of the above-mentioned packages If delivery is deemed possible, The change in collection timing will be reflected in the increase in handling work volume and travel distance. The price to be offered to the shipper is set.

[0026] Like the first invention, this enables the transportation company to increase the number of parcel deliveries it accepts, and also enables it to present prices with clearly-founded reasons to shippers, enabling persuasive price negotiations.

[0027] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0028] FIG. 1 is an overall configuration diagram of a cargo and vehicle request system according to this embodiment.

[0029] This cargo and vehicle request system includes a cargo and vehicle request server 1 (first server device), a delivery management server 2 (second server device), a shipper terminal 3, and a driver terminal 4. The cargo and vehicle request server 1, the delivery management server 2, the shipper terminal 3, and the driver terminal 4 are connected to a network such as the Internet.

[0030] The cargo vehicle request server 1 is operated by a company that mediates between the shipper and the transport company. The cargo vehicle request server 1 compares the delivery conditions specified by the shipper with the vacant status (load status) of the truck (transport vehicle) operated by the transport company, and performs processing to match the shipper's request for a truck to deliver the cargo with the transport company's request for the cargo to be loaded on the truck. Specifically, the cargo vehicle request server 1 generates cargo request information based on information provided by the delivery management server 2, and presents the cargo request information to the shipper using the shipper terminal 3. The cargo request information is information about the cargo required by the transport company, and is information that serves as a reference when the shipper decides whether or not to request the cargo delivery. In addition, in response to an inquiry about cargo delivery from the shipper, the cargo vehicle request server 1 considers whether delivery is possible (delivery possibility) under the delivery conditions specified by the shipper, and responds to the inquiry about cargo delivery from the shipper. The cargo vehicle request server 1 may be directly operated by the transport company.

[0031] The delivery management server 2 is operated by a transportation company. The delivery management server 2 performs a loading optimization process to obtain optimal loading, that is, the optimal arrangement of cargo loaded in the cargo compartment (bed) of a truck. The delivery management server 2 also manages cargo information and delivery plan information of all trucks managed by this system based on information provided from the driver terminal 4. The delivery management server 2 may be operated by one transportation company, or may be jointly operated by multiple transportation companies.

[0032] The consignor terminal 3 is operated by the consignor. The consignor terminal 3 may be configured as an information terminal such as a PC, a smartphone, or a tablet terminal. On the consignor terminal 3, under the control of the cargo request vehicle request server 1, a screen for presenting cargo request information to the consignor, a screen for the consignor to inquire about cargo delivery by specifying delivery conditions, a screen for displaying the response from the transport company to the inquiry about cargo delivery, and a screen for officially requesting cargo delivery are displayed.

[0033] The driver terminal 4 is operated by the truck driver. The driver terminal 4 may be configured as a portable information terminal such as a smartphone or a tablet terminal. The driver terminal 4 displays a screen that presents the driver with stowage information provided by the delivery management server 2, that is, information regarding the optimal arrangement of luggage in the luggage compartment of the truck. The driver can load luggage into the luggage compartment of the truck by referring to the stowage information. The driver terminal 4 also displays a screen that allows the driver to input information about luggage to be loaded and unloaded when the luggage is delivered and collected.

[0034] In this embodiment, the loading status of the truck is recognized by the driver inputting information on the luggage to be loaded and unloaded. Alternatively, the loading status of the truck may be recognized based on an image of a camera that photographs the luggage compartment of the truck or a detection result of a weight sensor that measures the weight of the luggage loaded in the luggage compartment.

[0035] Next, the delivery condition analysis process performed by the cargo vehicle request server 1 will be described. FIG. 2 is an explanatory diagram showing the case division performed in the delivery condition analysis process. FIG. 3 is an explanatory diagram showing an example of the loading state of a truck corresponding to the first case. FIG. 4 is an explanatory diagram showing an example of the loading state of a truck corresponding to the second case. FIG. 5 is an explanatory diagram showing an example of the loading state of a truck corresponding to the third case.

[0036] When the cargo request / vehicle request server 1 receives an inquiry about cargo delivery from a shipper, a process (delivery condition analysis process) is performed to consider the possibility of delivery based on the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the shipper. For example, it is determined whether the shipper's cargo can be collected on a specified date and delivered to a specified delivery destination by a specified time.

[0037] At this time, first, for trucks operating on that day, it is judged whether or not delivery is possible under the delivery conditions specified by the shipper with the current loaded state (delivery possibility). Specifically, it is judged whether or not there is currently free space to load the new cargo inquired about by the shipper.

[0038] The example shown in Figure 3 is the first case where delivery is possible under the delivery conditions specified by the shipper with the current loaded state (see Figure 2). In the example shown in Figure 3, packages #1 to #5 are currently loaded in the truck's cargo compartment. If the shipper inquires about the delivery of package #6, there is currently free space in the truck that can load package #6.

[0039] In this case, the cargo can be delivered according to the delivery conditions specified by the shipper, and a reply to that effect is sent to the shipper. In addition, a price is set to reflect the increase in the amount of cargo handling work and the distance traveled due to the addition of cargo #6, and this price is presented to the shipper. Note that cargo handling work includes loading and unloading of cargo when delivering and collecting the cargo, and reloading to rearrange the cargo in the cargo compartment.

[0040] In addition, there are cases where the current loading state makes it impossible to deliver the goods under the delivery conditions specified by the shipper. In this case, it is next determined whether or not the trucks operating on that day can deliver the goods under the delivery conditions specified by the shipper under the loading state predicted based on the current delivery plan (delivery possibility). Specifically, the loading state is predicted based on the delivery plan, and it is determined whether or not there is enough space to load the new goods inquired about by the shipper before the goods are collected from the shipper under the predicted loading state.

[0041] The example shown in Figure 4 is the second case where delivery is possible under the delivery conditions specified by the shipper in the loading state predicted based on the current delivery plan (see Figure 2). In the example shown in Figure 4, packages #1 to #6 are currently loaded in the truck's cargo bay. Packages #1 to #6 will be unloaded in the order specified based on the delivery plan.

[0042] Now, if the shipper inquires about the delivery of package #7, package #7 cannot be loaded at this time, as shown in FIG. 4(A).

[0043] On the other hand, as shown in Figures 4(B) and (C), when the unloading of packages #5 and #6 is performed in sequence, an empty space becomes available on the truck to load package #7, as shown in Figure 4(D). In other words, if the empty space becomes available on the truck to load package #7 before the collection of package #7, package #7 can be delivered.

[0044] In this case, the shipper is notified that the shipment can be delivered according to the shipping conditions specified by the shipper. The price is set to reflect the additional handling work and mileage due to the addition of the #7 shipment, and is presented to the shipper.

[0045] In addition, there are cases where delivery cannot be made under the delivery conditions specified by the shipper in the loading state predicted based on the current delivery plan. In this case, it is next determined whether or not delivery is possible (delivery possibility) under the delivery conditions specified by the shipper in the loading state predicted based on the revised delivery plan for trucks operating on that day. Specifically, a revised delivery plan is created in which the unloading order is changed, the loading state is predicted based on the revised delivery plan, and it is determined whether or not there is free space in the predicted loading state to load new cargo inquired about by the shipper before the timing of collection of the cargo from the shipper.

[0046] The example shown in Figure 5 is the third case where delivery is possible under the delivery conditions specified by the shipper in the loading state predicted based on the revised delivery plan (see Figure 2). In the example shown in Figure 5, as in the example shown in Figure 4, packages #1 to #6 are currently loaded in the truck compartment.

[0047] In this case, if the shipper inquires about the delivery of the #7 package, the #7 package cannot be loaded at this time, as shown in Fig. 5(A). Also, unlike the example shown in Fig. 4, if the timing of collection (loading) of the #7 package is before the timing of unloading the #6 package, the #7 package cannot be loaded into the luggage compartment at the time of collection.

[0048] On the other hand, if the delivery plan is changed to switch the unloading order of the #5 parcel and the #6 parcel as shown in Fig. 5(B), when the #6 parcel is unloaded as shown in Fig. 5(C), an empty space in which the #7 parcel can be loaded becomes available on the truck as shown in Fig. 5(D). In other words, if the empty space in which the #7 parcel can be loaded becomes available on the truck before the #7 parcel is picked up, the #7 parcel can be delivered.

[0049] In this case, the shipper is notified that the shipment can be delivered according to the delivery conditions specified by the shipper. The price is set to reflect the increase in the amount of work required for handling the shipment and the distance traveled due to the addition of the shipment #7 and the revised delivery plan, and the price is presented to the shipper.

[0050] On the other hand, there are cases (fourth case) where the cargo condition predicted based on the revised delivery plan makes it impossible to deliver the goods according to the delivery conditions specified by the shipper (see Figure 2).

[0051] In this case, an alternative plan is created by modifying the delivery conditions specified by the shipper so that actual delivery is possible. A response is sent to the shipper to inform him that the package cannot be delivered under the delivery conditions specified by the shipper, and an alternative plan is proposed to the shipper. A price is set based on the alternative plan and presented to the shipper. Note that fees for modifying the delivery plan may be reflected in the price.

[0052] In this embodiment, the delivery plan is changed so as to change the order of unloading a plurality of packages, but when the order of unloading the packages is changed, the loading positions of the packages may be changed at the same time. In this case, the loading is reviewed in the delivery management server 2. In addition, if the amount of handling work increases due to the change in the loading positions of the packages, the increase in the amount of handling work may be reflected in the price.

[0053] Next, a description will be given of the schematic configuration of the cargo vehicle request server 1 and the delivery management server 2. Fig. 6 is a block diagram showing the schematic configuration of the cargo vehicle request server 1 and the delivery management server 2. In this embodiment, the cargo vehicle request server 1 and the delivery management server 2 are configured separately, but they may be configured as one server.

[0054] The cargo and vehicle request server 1 includes a communication unit 11, a storage unit 12, and a processor 13.

[0055] The communication unit 11 communicates with the delivery management server 2 and the shipper terminal 3 .

[0056] The storage unit 12 stores programs and the like executed by the processor 13. The storage unit 12 also stores registration information of the cargo request information database, specifically, cargo request information managed by the processor 13 (see FIG. 7).

[0057] The processor 13 performs various processes by executing the programs stored in the storage unit 12. In this embodiment, the processor 13 performs a cargo request information management process, a cargo request information presentation process, a reception response process, a delivery condition analysis process, a price setting process, an alternative plan creation process, and the like.

[0058] In the cargo request information management process, the processor 13 updates the cargo request information based on the delivery plan information (including loading information) provided by the delivery management server 2. The cargo request information is information about the cargo requested by the transport business operator, and is information that serves as a reference when the shipper decides whether or not to request the delivery of the cargo (see FIG. 7). The cargo request information updated in the cargo request information management process is registered in the cargo request information database.

[0059] In the cargo request information presentation process, the processor 13 presents the latest cargo request information registered in the cargo request information database to the shipper. Specifically, the processor 13 causes the shipper terminal 3 to display a screen presenting the cargo request information to the shipper.

[0060] In the reception and response process, the processor 13 receives an inquiry about package delivery from the shipper, and responds to the inquiry about package delivery. When responding, the processor 13 also presents the price for package delivery (delivery fee) to the shipper. Specifically, the processor 13 causes the shipper terminal 3 to display a screen on which the shipper can specify delivery conditions and make an inquiry about package delivery, and a screen that displays the response from the transport company to the inquiry about package delivery.

[0061] In addition, in the reception / reply process, the processor 13 receives a formal request for package delivery from the shipper. Specifically, the processor 13 causes the shipper terminal 3 to display a screen for formally requesting package delivery. The shipper determines whether to formally request package delivery or to abandon the request for package delivery, and operates the screen accordingly.

[0062] In the delivery condition analysis process, the processor 13 considers the possibility of delivery of the package based on the delivery conditions specified by the shipper. The delivery possibility is examined for multiple trucks currently in operation. The delivery condition analysis process includes a first delivery possibility determination process, a second delivery possibility determination process, and a third delivery possibility determination process.

[0063] In the first delivery possibility determination process, the processor 13 determines whether or not delivery is possible under the delivery conditions specified by the shipper in the current loaded state (delivery possibility). Specifically, it is determined whether or not there is currently any free space to load a new package inquired about by the shipper. The processor 13 may determine the delivery possibility based on the loaded state at the time of collection of the package, based on the delivery plan information.

[0064] In the second delivery possibility determination process, the processor 13 determines whether or not delivery is possible under the delivery conditions specified by the shipper in the loading state predicted based on the current delivery plan (delivery possibility). Specifically, it is determined whether or not a vacant space for loading new cargo inquired by the shipper will be available before the timing of collection of the cargo from the shipper in the loading state predicted based on the delivery plan.

[0065] In the third delivery possibility determination process, the processor 13 determines whether or not delivery is possible under the delivery conditions specified by the shipper in the loading state predicted based on the revised delivery plan proposal (delivery possibility). Specifically, it is determined whether or not an available space for loading new cargo inquired by the shipper will be available before the timing of collection of the cargo from the shipper in the loading state predicted based on the revised delivery plan proposal in which the unloading order is changed.

[0066] In the pricing process, the processor 13 sets a price (transportation fee) to be presented to the shipper as a reference when responding to an inquiry from the shipper. In the pricing process, a pricing method that varies the price depending on the status of the truck and the cargo, known as dynamic pricing, is adopted. If delivery is possible under the delivery conditions specified by the shipper, the price is set based on the contents of the delivery conditions specified by the shipper. Also, if delivery is not possible under the delivery conditions specified by the shipper and an alternative is proposed to the shipper, the price is set based on the contents of the alternative. Note that when a formal delivery request is accepted from the shipper, the price to be charged to the shipper at that time is set again.

[0067] For example, when the number of parcel deliveries accepted is low, it is desirable to increase new delivery requests, so the price is set based on the number of parcel deliveries accepted on that day. Specifically, if the number of parcel deliveries accepted on that day is low, the price is set low, and if the number of parcel deliveries accepted on that day is high, the price is set high. Note that the number of parcel deliveries accepted may be based on all of the multiple trucks operating on that day. The price may also be set based on the loading rate of the truck.

[0068] Furthermore, since the amount of cargo handling work increases when cargo is added due to a new delivery request, the price is set based on the amount of cargo handling work. Furthermore, if the delivery plan is revised to meet the delivery conditions specified by the shipper, the amount of cargo handling work increases due to a change in the unloading order, so the price is set based on the amount of cargo handling work. The amount of cargo handling work may be set based on the time required for loading and unloading, the weight and size of the cargo, and the loading conditions of the cargo (designated top and bottom, no stacking, fragile items, precision machinery, temperature designation), etc. A fee for reviewing the delivery plan may be reflected in the price.

[0069] In addition, when a new delivery request adds cargo, the truck's travel distance (delivery route length) is extended, so the price is set based on the increased travel distance. Furthermore, when the delivery plan is revised to meet the delivery conditions specified by the shipper, the revised delivery plan extends the travel distance, so the price is set based on the increased travel distance.

[0070] In addition, when a new delivery request is made and cargo is added, waiting time may occur due to the need to adjust the time for loading and unloading the cargo, so the price is set based on the increase in waiting time. Furthermore, when a delivery plan is revised to meet delivery conditions specified by the shipper, waiting time may occur due to the revision of the delivery plan, so the price is set based on the increase in waiting time.

[0071] In the alternative plan creation process, when delivery based on the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the shipper is impossible, the processor 13 creates an alternative plan by modifying the delivery conditions specified by the shipper so that actual delivery is possible. The alternative plan is created based on the latest cargo request information registered in the cargo request information database. The created alternative plan is proposed to the shipper when responding to an inquiry about package delivery.

[0072] In the alternative plan, for example, a delivery date different from the delivery date specified by the shipper is proposed. Specifically, when delivery cannot be made on the delivery date specified by the shipper, if delivery is possible on another day (for example, the next day), the other day is proposed as the new delivery date. In this case, in addition to proposing only one delivery date, delivery dates may be proposed over multiple days (periods). In addition, in the alternative plan, for example, an arrival time different from the arrival time specified by the shipper is proposed. Specifically, when delivery cannot be made at the arrival time specified by the shipper, if delivery is possible if the arrival time is delayed, that time is proposed as the new arrival time. In addition, in the alternative plan, for example, a collection time different from the collection time specified by the shipper is proposed. Specifically, when collection cannot be made at the collection time specified by the shipper, if collection is possible if the collection time is delayed or advanced, that time is proposed as the new collection time. In addition, in the alternative plan, for example, a delivery destination different from the delivery destination specified by the shipper is proposed. Specifically, if the delivery destination specified by the shipper cannot be delivered, but a delivery base near the destination can be delivered, that delivery base will be suggested as the new delivery destination.

[0073] The delivery management server 2 includes a communication unit 21, a storage unit 22, and a processor 23.

[0074] The communication unit 21 communicates between the cargo and vehicle request server 1 and the driver terminal 4.

[0075] The storage unit 22 stores programs executed by the processor 23, etc. The storage unit 22 stores registration information of the delivery information database, specifically, package information, loading information, and delivery plan information managed by the processor 23 (see FIG. 7).

[0076] The processor 23 performs various processes by executing the programs stored in the storage unit 22. In this embodiment, the processor 23 performs a stowage optimization process, a loading information management process, a delivery plan management process, a cargo status prediction process, and the like.

[0077] In the stowage optimization process, the processor 23 determines optimal stowage, that is, the optimal arrangement of cargo to be loaded in the cargo compartment of the truck, based on loading information related to the cargo compartment of the truck and the cargo to be loaded.

[0078] In the loading information management process, the processor 23 updates the loading information based on the baggage information acquired from the driver terminal 4. The loading information is information related to the loading status of the baggage in the truck (see FIG. 7).

[0079] In the delivery plan management process, the processor 23 manages delivery plan information. The delivery plan information is information related to a schedule for delivering packages by driving trucks (see FIG. 7). In addition, in the delivery plan management process, the processor 23 creates a revised delivery plan (delivery plan review process). At this time, for example, a revised plan is created in which the order of delivery (unloading) of multiple packages is changed.

[0080] In the loading status prediction process, the processor 23 predicts the loading status of the truck, i.e., the status of the luggage loaded in the luggage compartment of the truck (the availability of the luggage compartment) based on the delivery plan information. Specifically, the processor 23 predicts the situation in which the loading status of the truck (the availability of the luggage compartment) changes as the luggage is delivered and collected in sequence according to the delivery schedule.

[0081] Next, the registered contents of the delivery information database and the cargo request information database will be described. Fig. 7 is an explanatory diagram showing the registered contents of the delivery information database and the cargo request information database.

[0082] The delivery information database manages package information, loading information, and delivery plan information.

[0083] The baggage information is individual information about the baggage loaded on the truck. The baggage information includes information about the delivery destination (such as the name of the delivery destination, the arrival time, etc.), information about the size of the baggage (such as information about the three sides: length, width, and height), information about the weight of the baggage, information about the loading conditions of the baggage (such as information about the top and bottom of the baggage, no stacking, etc.), and other information about the baggage (fragile, precision machinery, temperature conditions, etc.). The baggage information is updated in response to the driver's operation to input information about the baggage to be loaded and unloaded when the baggage is delivered or collected in the driver's terminal 4. The baggage information also includes identification information individually assigned to the baggage.

[0084] The loading information is information about the loading status of the cargo in the truck. The loading information includes information about the cargo compartment of the truck (such as the size of the cargo compartment) and information about the cargo loaded (such as cargo information). The loading information is updated in the delivery management server 2 based on the cargo information provided from the driver terminal 4.

[0085] The delivery plan information is information related to a schedule for driving trucks to deliver packages, etc. The delivery plan information includes information related to the delivery area (the range in which the truck drives for delivery), information related to the delivery route (the names of the delivery destinations, the order of delivery (unloading), and the route of travel between the delivery destinations), loading information, and other information related to delivery (information related to the driver's attributes (gender, etc.)).

[0086] The cargo request information database manages cargo request information. The cargo request information is information about cargo requested by a transport business operator, and serves as a reference when a shipper decides whether or not to request cargo delivery. The cargo request information includes information about delivery areas and collection areas (such as the names of areas), information about time periods when delivery is possible, information about the size of cargo that can be delivered, and reference prices. The cargo request information is updated based on the latest delivery plan information (including loading information) provided by the delivery management server 2.

[0087] The reference price is a price that is presented to the shipper when responding to an inquiry about package delivery from the shipper, so that the shipper can use it as a guide for deciding whether or not to formally request package delivery. The reference price may be set with a price range. When a formal package delivery request is received from the shipper, the regular price is set again based on the situation at that time.

[0088] Next, the processing performed by this system will be described. Figures 8 and 9 are sequence diagrams showing an overview of the processing performed by this system when cargo request information is presented to the shipper. Figures 10 and 11 are sequence diagrams showing an overview of the processing performed by this system when cargo request information is not presented to the shipper.

[0089] First, a case where cargo request information is presented to a shipper will be described. In this case, as shown in FIG. 8, the driver first inputs information about the cargo when the cargo is delivered and collected in the driver terminal 4. Next, the driver terminal 4 performs an update process to reflect the loading and unloading of the cargo at the time of delivery and collection in the cargo information of the truck based on the information input by the driver. Next, the updated cargo information is transmitted from the driver terminal 4 to the delivery management server 2.

[0090] The delivery management server 2 first receives the updated baggage information from the driver terminal 4. Next, the delivery management server 2 performs an update process to reflect the updated baggage information in the loading information of the truck. Also, the delivery management server 2 performs an update process to reflect the updated loading information in the delivery plan information of the truck. Next, the delivery management server 2 performs an update process to reflect the updated baggage information, loading information, and delivery plan information in the delivery information database. Also, the updated delivery plan information (including loading information) is transmitted from the delivery management server 2 to the cargo request vehicle request server 1.

[0091] The cargo request vehicle request server 1 first receives updated delivery plan information (including loading information) from the delivery management server 2. Next, the cargo request vehicle request server 1 performs an update process to review information on each item included in the cargo request information (information on the size of deliverable cargo, reference price, etc.) based on the updated delivery plan information (including loading information). Next, the cargo request vehicle request server 1 performs an update process to reflect the updated cargo request information in the cargo request information database. Furthermore, the cargo request vehicle request server 1 transmits the latest cargo request information to the shipper terminal 3 in response to a viewing request from the shipper terminal 3. The shipper terminal 3 displays the received cargo request information on a screen, thereby presenting the latest cargo request information to the shipper.

[0092] The above process is repeatedly executed every time the driver performs an input operation on the driver terminal 4 during delivery of the luggage. As a result, every time the driver loads or unloads luggage, the driver inputs information about the unloaded luggage, thereby updating the loading information of the truck, and the loading information of the truck is kept up to date. Note that the loading information may be updated by detecting a change in the luggage in the luggage compartment based on an image of a camera that photographs the luggage compartment of the truck or a detection result of a weight sensor that measures the weight of the luggage loaded in the luggage compartment.

[0093] 9, when the consignor inquires of the transport company about the delivery of the cargo at the consignor terminal 3, the inquiry about the cargo delivery is transmitted to the cargo vehicle request server 1. This inquiry about the cargo delivery includes the delivery conditions (delivery date, arrival time, delivery destination, etc.) designated by the consignor.

[0094] When the cargo request vehicle request server 1 receives an inquiry about cargo delivery from the shipper terminal 3, a process (delivery condition analysis process) is performed to consider whether or not delivery is possible under the delivery conditions specified by the shipper, based on the delivery conditions and cargo request information specified by the shipper. At this time, first to third delivery possibility determination processes are performed, and the case is divided into first to fourth cases (see FIG. 2).

[0095] At this time, the delivery management server 2 executes, as necessary, a loading status prediction process for predicting a loading status based on a delivery plan and a delivery plan review process for creating a revised proposal for the delivery plan in response to an instruction from the cargo vehicle request server 1. Meanwhile, the cargo vehicle request server 1 executes a delivery condition analysis process based on the results of the loading status prediction process and the delivery plan review process.

[0096] Next, the cargo and vehicle request server 1 sets a price according to the result of the delivery condition analysis process. Next, the cargo and vehicle request server 1 transmits a response to the inquiry about the cargo delivery to the shipper terminal 3.

[0097] Next, a case where the cargo request information is not presented to the shipper will be described. In this case, as shown in FIG. 10, the process performed in the driver terminal 4 is the same as that in the case where the cargo request information is presented to the shipper (see FIG. 8). The process performed in the delivery management server 2 is also substantially the same as that in the case where the cargo request information is presented to the shipper (see FIG. 8), but the updated delivery plan information (including loading information) is not transmitted from the delivery management server 2 to the cargo request vehicle request server 1. In addition, the cargo request vehicle request server 1 does not perform a process of updating the cargo request information and a process of updating the cargo request information database.

[0098] 11, when the consignor inquires of the transport company about the delivery of the cargo at the consignor terminal 3, the inquiry about the cargo delivery is transmitted to the cargo vehicle request server 1. This inquiry about the cargo delivery includes the delivery conditions (delivery date, arrival time, delivery destination, etc.) designated by the consignor.

[0099] When the cargo request vehicle request server 1 receives an inquiry about cargo delivery from the shipper terminal 3, it requests the delivery management server 2 to transmit the latest delivery plan information (including loading information), and in response receives the latest delivery plan information (including loading information) from the delivery management server 2. Next, the cargo request vehicle request server 1 performs an update process to review the information of each item (reference price, etc.) included in the cargo request information based on the latest delivery plan information (including loading information). Next, the cargo request vehicle request server 1 performs an update process to reflect the updated cargo request information in the cargo request information database.

[0100] Next, the cargo vehicle request server 1 performs a process (delivery condition analysis process) to consider whether or not delivery is possible under the delivery conditions specified by the shipper based on the delivery conditions and cargo request information specified by the shipper. At this time, first to third delivery possibility determination processes are performed and the cases are divided into first to fourth cases (see FIG. 2). Next, the cargo vehicle request server 1 sets a price according to the results of the delivery condition analysis process. Next, the cargo vehicle request server 1 transmits a response to the inquiry about baggage delivery to the shipper terminal 3.

[0101] Next, the process performed by the cargo vehicle request server 1 and the delivery management server 2 when there is an inquiry about cargo delivery from a shipper will be described. Fig. 12 is a flow diagram showing the procedure of the process performed by the cargo vehicle request server 1. Fig. 13 is a flow diagram showing the procedure of the process performed by the delivery management server 2.

[0102] In the cargo request vehicle request server 1, the processor 13 first accepts an inquiry about baggage delivery from a shipper (ST101). At this time, the processor 13 displays a screen on the shipper terminal 3 for performing operations related to the inquiry about baggage delivery. On the screen, the shipper can perform operations such as making an inquiry about baggage delivery and inputting baggage delivery conditions.

[0103] Next, the processor 13 determines whether or not delivery is possible under the delivery conditions designated by the shipper in the current loaded state (delivery possibility) (first delivery possibility determination process) (ST102).

[0104] If the current state of the load allows delivery under the delivery conditions specified by the shipper (Yes in ST102), the processor 13 sets a price for delivery of the cargo based on the delivery conditions specified by the shipper (ST110). At this time, the price is set to reflect the increase in the amount of handling work and the travel distance due to the addition of the cargo.

[0105] Next, the processor 13 responds to the inquiry about the package delivery from the consignor (ST111). At this time, the processor 13 displays a screen presenting the response to the consignor on the consignor terminal 3. By viewing the screen of the consignor terminal 3, the consignor can decide whether to formally request the package delivery or to abandon the request for package delivery.

[0106] It should be noted that a cheaper price may be set by changing the delivery terms from those specified by the shipper. For example, if there is more vacancy (loading status) in a truck in operation on a day other than the delivery date specified by the shipper (e.g. the next day), a cheaper price may be set by changing the delivery date and time to that day and time. In this case, in addition to the answer corresponding to the shipper's delivery terms, in ST111, delivery terms different from the shipper's delivery terms and the price in that case may be presented. This may have the effect of reducing opportunity loss by distributing the delivery load.

[0107] Here, when the shipper formally requests baggage delivery, the shipper performs an operation to formally request baggage delivery on the shipper terminal 3. At this time, the cargo vehicle request server 1 displays a screen on the shipper terminal 3 for performing operations related to the formal request for baggage delivery. On the screen, the shipper can perform operations to formally request baggage delivery and operations to input delivery conditions. In the cargo vehicle request server 1, a process of accepting the formal request for baggage delivery from the shipper is performed in response to the screen operations on the shipper terminal 3.

[0108] On the other hand, if the current loading status makes it impossible to deliver the goods under the delivery conditions specified by the shipper (No in ST102), then, under the control of the processor 13, the communication unit 11 sends an instruction to the delivery management server 2 to execute the loading status prediction process (ST103).

[0109] 13(A), in the delivery management server 2, when the communication unit 21 receives an instruction to execute the loading state prediction process transmitted from the cargo vehicle request server 1 (ST201), the processor 23 predicts the loading state of the truck on the day based on the delivery plan for the day (loading state prediction process) (ST202). Next, based on the control of the processor 23, the communication unit 21 transmits the result of the loading state prediction process to the cargo vehicle request server 1 (ST203).

[0110] As shown in FIG. 12, in the cargo vehicle request server 1, when the communication unit 11 receives the results of the loading status prediction process transmitted from the delivery management server 2 (ST104), the processor 13 determines whether or not delivery is possible (delivery possibility) under the delivery conditions specified by the shipper in the loading status predicted based on the current delivery plan (second delivery possibility determination process) (ST105).

[0111] Here, if delivery is possible under the delivery conditions specified by the shipper in the cargo state predicted based on the current delivery plan (Yes in ST105), the process proceeds to ST110 and ST111.

[0112] On the other hand, if delivery cannot be made under the delivery conditions specified by the shipper with the loading status predicted based on the current delivery plan (No in ST105), then, under the control of the processor 13, the communication unit 11 sends an instruction to the delivery management server 2 to execute a delivery plan review process (ST106).

[0113] As shown in FIG. 13(B), in the delivery management server 2, when the communication unit 21 receives an execution instruction for the delivery plan review process transmitted from the cargo vehicle request server 1 (ST211), the processor 23 creates a delivery plan review proposal (delivery plan review process) (ST212). Next, the processor 23 predicts the loading status of the truck based on the delivery plan review proposal (loading status prediction process) (ST213). Next, based on the control of the processor 23, the communication unit 21 transmits the result of the loading status prediction process based on the delivery plan review proposal to the cargo vehicle request server 1 (ST214).

[0114] As shown in FIG. 12, in the cargo vehicle request server 1, when the communication unit 11 receives the result of the loading status prediction process based on the revised delivery plan sent from the delivery management server 2 (ST107), the processor 13 determines whether or not delivery is possible (delivery possibility) under the delivery conditions specified by the shipper in the loading status predicted based on the revised delivery plan (third delivery possibility determination process) (ST108).

[0115] Here, if delivery is possible under the delivery conditions specified by the shipper in the cargo state predicted based on the revised delivery plan (Yes in ST108), the process proceeds to ST110. At this time, a price is set based on the revised delivery plan.

[0116] On the other hand, if the cargo condition predicted based on the revised delivery plan proposal makes it impossible to deliver the goods under the delivery conditions specified by the shipper (No in ST108), then processor 13 creates an alternative plan in which the delivery conditions specified by the shipper are modified so that actual delivery is possible (alternative plan creation process) (ST109). Next, the process proceeds to ST110 and ST111. At this time, a price is set based on the alternative plan (ST110), and a response is made to the inquiry about parcel delivery (ST111). If the shipper can accept the delivery conditions and price of the alternative plan, he or she performs an operation to formally request parcel delivery.

[0117] If an alternative plan cannot be created, the shipper will be informed that delivery of the package cannot be accepted.

[0118] Incidentally, there are cases where multiple revision plans for a delivery plan can be created. In this case, the process of creating an alternative plan for each revision plan may be repeated. In addition, all of the multiple alternative plans created may be presented to the shipper, or a process of evaluating the alternative plans may be performed, and one or a predetermined number of alternative plans based on the highest evaluation may be presented to the shipper.

[0119] As described above, the embodiments have been described as examples of the technology disclosed in this application. However, the technology in this disclosure is not limited to these, and can be applied to embodiments in which modifications, substitutions, additions, omissions, etc. are made. In addition, it is also possible to combine the components described in the above embodiments to create new embodiments. [Industrial Applicability]

[0120] The cargo and vehicle request system, server device, and program of the present invention have the effect of increasing the number of cargo delivery assignments accepted by a transportation company, and also enabling persuasive price negotiations to be conducted by presenting a price with a clear basis to a shipper, and are useful as a cargo and vehicle request system, server device, and program that executes a process of considering the possibility of delivering a cargo based on delivery conditions specified by the shipper and providing a response to the shipper based on the results of the process. [Explanation of symbols]

[0121] 1: Cargo and vehicle request server (first server device) 2: Delivery management server (second server device) 3: Shipper terminal 4: Driver terminal 13: Processor 23: Processor

Claims

1. A cargo and vehicle request system in which one or more processors execute a process of examining the possibility of delivery of a cargo based on delivery conditions designated by a shipper and providing a response based on the result to the shipper, The processor, If the cargo condition at the time of receiving an inquiry about cargo delivery from the shipper makes it impossible to deliver the cargo according to the delivery conditions specified by the shipper, Determine the feasibility of delivery according to the cargo status predicted based on the delivery plan; A cargo and vehicle request system characterized in that, when it is determined that delivery is possible by changing the timing of collection of the cargo, a price to be offered to the shipper is set so as to reflect an increase in the amount of cargo handling work and the travel distance due to the change in the timing of collection.

2. The processor, If the cargo condition predicted based on the delivery plan does not allow the cargo to be delivered based on the delivery conditions specified by the shipper, determining whether delivery is possible according to a predicted loading state based on a revised delivery plan obtained by changing the unloading order; The cargo and vehicle request system according to claim 1, characterized in that, when it is determined that delivery is possible, a price to be offered to the shipper is set so as to reflect an increase in the amount of cargo handling work and the travel distance based on the revised proposal for the delivery plan.

3. The processor, If delivery cannot be made based on the predicted loading status based on the revised delivery plan, Based on cargo request information, which is information about cargo required by the transportation business operator, an alternative plan is created in which at least one of the delivery conditions specified by the shipper, including the delivery date, arrival time, collection time, and delivery destination, is changed so that actual delivery is possible; 3. The cargo and vehicle request system according to claim 2, wherein the alternative plan is presented to the shipper.

4. The processor, Update cargo information regarding deliverable cargo and its delivery conditions based on the latest information regarding cargo loaded on the transportation vehicle; 2. The cargo and vehicle request system according to claim 1, further comprising: examining the possibility of cargo delivery based on the cargo request information.

5. The system includes a first server device that manages cargo request information and a second server device that manages a delivery plan, The processor provided in the second server device, A cargo status prediction process for predicting a cargo status based on a delivery plan; A delivery plan review process for creating a revised proposal for the delivery plan is executed; The processor provided in the first server device, The cargo and vehicle request system according to claim 2, characterized in that a delivery condition analysis process is executed based on the results of the loading status prediction process and the delivery plan review process, to consider the possibility of delivering cargo based on delivery conditions specified by a shipper.

6. A server device in which one or more processors execute a process of examining the possibility of delivery of a package based on delivery conditions designated by a shipper and providing a response based on the result to the shipper, The processor, If the cargo condition at the time of receiving an inquiry about cargo delivery from the shipper makes it impossible to deliver the cargo according to the delivery conditions specified by the shipper, Determine the feasibility of delivery according to the cargo status predicted based on the delivery plan; A server device characterized in that, when it is determined that delivery is possible by changing the timing of collection of the package, the price offered to the shipper is set so as to reflect the increase in the amount of handling work and the distance traveled due to the change in the timing of collection.

7. A program that causes one or more processors to execute a process of examining the possibility of delivery of a package based on delivery conditions designated by a shipper and providing a response to the shipper based on the result of the examination, If the cargo condition at the time of receiving an inquiry about cargo delivery from the shipper makes it impossible to deliver the cargo according to the delivery conditions specified by the shipper, Determine the feasibility of delivery according to the cargo status predicted based on the delivery plan; When it is determined that delivery is possible by changing the timing of collection of the cargo, the program sets a price to be offered to the shipper so as to reflect the increase in the amount of cargo handling work and the distance traveled due to the change in the timing of collection.

Images