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 negotiations by presenting prices with clear grounds to shippers. [Solution] Determine 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), determine 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), determine whether delivery is possible based on the loading condition predicted based on a revised delivery plan (ST108), and if delivery is not possible based on the loading condition predicted based on the revised delivery plan (No in ST108), create an alternative plan by changing the delivery conditions specified by the shipper so that actual delivery is possible (ST109), and present 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 that executes a process of examining the possibility of delivery of cargo based on delivery conditions specified by a shipper and providing a response based on the results 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 (load status) of trucks currently in operation by the transportation company, and matches the shipper's requests for trucks to deliver cargo with the transportation company's requests for cargo to be loaded onto the trucks (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-196479 Summary of the Invention [Problem to be solved by the invention]

[0004] In a cargo and vehicle request system, as in conventional technology, the possibility of delivering 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 because 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, conventional technology does not take this perspective into consideration at all, and there are problems in that it is not possible to sufficiently increase the number of cargo deliveries that a transportation company can accept, 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 transportation companies and that can present prices with clear grounds to shippers and conduct persuasive price negotiations. [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 cargo based on delivery conditions specified by the shipper and providing a response to the shipper based on the results, and the processor is configured to determine the possibility of delivery in accordance with the loading condition predicted based on the delivery plan when the cargo cannot be delivered based on the delivery conditions specified by the shipper with the current loading condition, and to set a price to be offered to the shipper based on the result of the determination of the possibility of delivery.

[0007] In addition, the server device of the present invention is a server device in which one or more processors execute a process of considering the delivery possibility of a package based on the delivery conditions specified by the shipper and providing the shipper with a response based on the results, and the processor is configured to determine the delivery possibility in accordance with the loading condition predicted based on the delivery plan when the package cannot be delivered based on the delivery conditions specified by the shipper with the current loading condition, and to set the price to be offered to the shipper based on the delivery possibility determination result.

[0008] In addition, the program of the present invention is a program that causes one or more processors to execute a process that considers the delivery possibility of a cargo based on the delivery conditions specified by the shipper and provides the shipper with a response based on the results.If the current loading condition makes it impossible to deliver the cargo based on the delivery conditions specified by the shipper, the program determines the delivery possibility according to the loading condition predicted based on the delivery plan, and sets the price to be offered to the shipper based on the results of the delivery possibility determination. [Effects 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 cargo condition, the possibility of delivery is determined according to the cargo 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 persuasive price negotiations to be conducted by presenting prices with clear grounds to the shipper. [Brief explanation of the drawings]

[0010] [Figure 1] Overall configuration diagram of a freight and vehicle request system according to this embodiment. [Figure 2] An explanatory diagram showing the situation of case division performed in the delivery condition analysis process performed on the cargo and vehicle request server. [Figure 3] FIG. 1 is an explanatory diagram showing an example of a truck loading state corresponding to the first case. [Figure 4] FIG. 10 is an explanatory diagram showing an example of a truck loading state corresponding to the second case. [Figure 5] FIG. 10 is an explanatory diagram showing an example of a truck loading state corresponding to the third case. [Figure 6] Block diagram showing the general configuration of the cargo and vehicle request server and 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 the outline of the processing performed by this system when presenting cargo request information to a shipper. [Figure 9] A sequence diagram showing the outline 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 processing steps 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 INVENTION

[0011] The first invention made to solve the above problem is a cargo and vehicle request system in which one or more processors execute a process to consider the possibility of delivery of a cargo based on delivery conditions specified by the shipper and provide a response to the shipper based on the results, and the processor is configured to determine the possibility of delivery in accordance with the loading condition predicted based on the delivery plan when the cargo cannot be delivered based on the delivery conditions specified by the shipper with the current loading condition, and to set a price to be offered to the shipper based on the result of the determination of the possibility of delivery.

[0012] According to this system, delivery possibility is considered based on the delivery conditions specified by the shipper (delivery date, arrival time, delivery destination, etc.), and in particular, if the cargo cannot be delivered based on the current loading condition, delivery possibility is determined based on the loading condition predicted based on the delivery plan. This allows transportation companies to increase the number of cargo deliveries they accept, and also allows them to present prices with clear grounds to shippers, enabling persuasive price negotiations.

[0013] In addition, the second invention is configured such that, when the cargo cannot be delivered based on the delivery conditions specified by the shipper with the cargo condition predicted based on the delivery plan, the processor determines the possibility of delivery according to the cargo condition predicted based on the revised delivery plan, and sets the price to be offered to the shipper based on the result of the delivery possibility determination.

[0014] According to this system, if a package cannot be delivered due to the load condition predicted based on the delivery plan, the possibility of delivery is determined according to the load condition predicted based on a revised delivery plan. This will further increase the number of package deliveries that a transport company can undertake, and will also enable persuasive price negotiations by presenting a price with a clear basis to the shipper.

[0015] In addition, a third invention is configured such that, when delivery is possible with the loading condition predicted based on the revised delivery plan, the processor sets the price to be offered to the shipper so as to reflect the increase in handling work volume and driving distance based on the revised delivery plan.

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

[0017] In addition, a fourth invention is configured such that, when delivery is not possible due to the loading status predicted based on the revised delivery plan proposal, the processor creates an alternative plan by modifying the delivery conditions specified by the shipper so that actual delivery is 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 transportation company from losing the opportunity to accept the cargo delivery.

[0019] In addition, the fifth 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 on the transportation vehicle, and considers the possibility of delivering the cargo based on the cargo request information.

[0020] This allows the latest cargo request information to be presented to the shipper, and also allows responses to inquiries about cargo delivery from the shipper based on the latest cargo request information.

[0021] In addition, a sixth 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 cargo status prediction process that predicts the cargo 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 the cargo based on the delivery conditions specified by the shipper, based on the results of the cargo 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] Furthermore, a seventh 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 specified by the shipper and providing the shipper with a response based on the results, and the processor is configured to determine the possibility of delivery in accordance with the predicted loading condition based on the delivery plan when the package cannot be delivered based on the delivery conditions specified by the shipper with the current loading condition, and to set a price to be offered to the shipper based on the result of the determination of the possibility of delivery.

[0024] As with the first invention, this allows the transportation company to increase the number of parcel deliveries it accepts, and also allows it to present prices with clear grounds to shippers, enabling persuasive price negotiations.

[0025] In addition, the eighth invention is a program that causes one or more processors to execute a process of considering the delivery possibility of a package based on delivery conditions specified by the shipper and providing the shipper with a response based on the results.If the current loading condition does not allow the package to be delivered based on the delivery conditions specified by the shipper, the program determines the delivery possibility according to the loading condition predicted based on the delivery plan, and sets the price to be offered to the shipper based on the delivery possibility determination result.

[0026] As with the first invention, this allows the transportation company to increase the number of parcel deliveries it accepts, and also allows it to present prices with clear grounds to shippers, enabling persuasive price negotiations.

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

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

[0029] This freight and vehicle request system includes a freight 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 freight 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 freight vehicle request server 1 is operated by a company that acts as an intermediary between a shipper and a transportation company. The freight vehicle request server 1 compares the delivery conditions specified by the shipper with the availability (load status) of trucks (transport vehicles) currently operated by the transportation company, and performs processing to match the shipper's request for trucks to deliver cargo with the transportation company's request for cargo to be loaded onto the truck. Specifically, the freight vehicle request server 1 generates freight request information based on information provided by the delivery management server 2, and presents the freight request information to the shipper using the shipper terminal 3. The freight request information is information about cargo desired by the transportation company, and serves as reference when the shipper decides whether or not to request cargo delivery. In addition, in response to an inquiry about cargo delivery from a shipper, the freight vehicle request server 1 considers whether delivery is possible (delivery possibility) under the delivery conditions specified by the shipper, and then responds to the inquiry about cargo delivery from the shipper. The freight vehicle request server 1 may also be operated directly by the transportation 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, i.e., the optimal arrangement of cargo to be loaded in the cargo compartment (bed) of a truck. The delivery management server 2 also manages cargo information and delivery plan information for 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 shipper terminal 3 is operated by the shipper. The shipper terminal 3 may be configured as an information terminal such as a PC, a smartphone, or a tablet terminal. Based on the control of the cargo and vehicle request server 1, the shipper terminal 3 displays a screen that presents cargo request information to the shipper, a screen on which the shipper specifies delivery conditions and makes an inquiry about cargo delivery, a screen that displays the response from the transport company to the inquiry about cargo delivery, and a screen on which the shipper can officially request cargo delivery.

[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 tablet terminal. The driver terminal 4 displays a screen that presents the driver with stowage information provided by the delivery management server 2, i.e., information regarding the optimal arrangement of cargo in the cargo compartment of the truck. The driver can refer to the stowage information to load cargo into the cargo compartment of the truck. The driver terminal 4 also displays a screen that allows the driver to input information about cargo to be loaded and unloaded when delivering and collecting cargo.

[0034] In this embodiment, the loading status of the truck is recognized by the driver inputting information about 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 the 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 situation of 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, it performs a process (delivery condition analysis process) to consider the possibility of delivery, that is, whether or not delivery is possible under the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the shipper. For example, it determines whether or not 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, it is determined whether or not the trucks operating on that day can deliver the goods under the delivery conditions specified by the shipper with the current state of the cargo (delivery possibility). Specifically, it is determined whether or not there is currently any free space available to load the new goods 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 given the current loading status (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 delivery of package #6, there is currently free space in the truck that can accommodate package #6.

[0039] 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 additional handling work and mileage due to the addition of shipment #6, and this price is presented to the shipper. Handling work includes loading and unloading of shipments when delivering and collecting them, and reloading to rearrange the shipments in the cargo compartment.

[0040] In addition, there are cases where the current loading status makes it impossible to deliver the goods under the delivery conditions specified by the shipper. In this case, a determination is made as to whether or not delivery is possible (delivery possibility) under the delivery conditions specified by the shipper for the trucks operating on that day under the loading status predicted based on the current delivery plan. Specifically, the loading status is predicted based on the delivery plan, and a determination is made as to whether or not there will be free space available to load the new goods inquired about by the shipper before the time of collection of the goods from the shipper.

[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 status 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] 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 #5 and #6 packages are unloaded in sequence, space becomes available on the truck to load the #7 package, as shown in Figure 4(D). In other words, if the timing at which space becomes available on the truck to load the #7 package is before the #7 package is picked up, the #7 package can be delivered.

[0044] 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 additional handling work and mileage due to the addition of shipment #7, and this price 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 condition predicted based on the current delivery plan. In this case, a determination is then made as to whether delivery is possible (delivery possibility) under the delivery conditions specified by the shipper in the loading condition predicted based on the revised delivery plan for trucks operating on that day. Specifically, a revised delivery plan is created that changes the unloading order, and the loading condition is predicted based on the revised delivery plan. It is then determined whether, in the predicted loading condition, there will be free space available to load the new cargo inquired about by the shipper before the time to collect 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 cargo 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] Here, when the shipper inquires about the delivery of package #7, package #7 cannot be loaded at this time, as shown in Figure 5(A). Also, unlike the example shown in Figure 4, if the timing of collection (loading) of package #7 is before the timing of unloading package #6, package #7 cannot be loaded into the luggage compartment at the time of collection.

[0048] On the other hand, if the delivery plan is changed so that the unloading order of #5 and #6 packages is swapped as shown in Figure 5(B), when #6 package is unloaded as shown in Figure 5(C), space becomes available on the truck to load #7 package as shown in Figure 5(D). In other words, if space becomes available on the truck to load #7 package before the collection of #7 package, #7 package 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 handling work and the mileage due to the addition of shipment #7 and the revised delivery plan, and this price is presented to the shipper.

[0050] On the other hand, there are cases (fourth case) where delivery cannot be made according to the delivery conditions specified by the shipper based on the predicted loading status based on the revised delivery plan (see Figure 2).

[0051] In this case, an alternative plan is created by changing the delivery conditions specified by the shipper so that actual delivery is possible. Also, a response is sent to the shipper to inform them that the package cannot be delivered according to the delivery conditions specified by the shipper, and an alternative plan is proposed to the shipper. Also, a price is set based on the alternative plan and presented to the shipper. Note that fees related to changes to the delivery plan may be reflected in the price.

[0052] In this embodiment, the delivery plan is changed so as to change the order in which multiple packages are unloaded. However, when the order in which packages are unloaded 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. Furthermore, if the amount of handling work increases due to a change in the loading positions of the packages, the increase in the amount of handling work may be reflected in the price.

[0053] Next, we will explain the schematic configuration of the freight vehicle request server 1 and the delivery management server 2. Fig. 6 is a block diagram showing the schematic configuration of the freight vehicle request server 1 and the delivery management server 2. In this embodiment, the freight vehicle request server 1 and the delivery management server 2 are configured separately, but they may also be configured as a single 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 registered information in 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 cargo requested by a transport business operator, and is information that serves as a reference when a shipper decides whether or not to request cargo delivery (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, processor 13 receives an inquiry about package delivery from a shipper and responds to the inquiry about package delivery. When responding, processor 13 also presents the price for package delivery (delivery fee) to the shipper. Specifically, processor 13 causes 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 / response process, the processor 13 receives a formal request for package delivery from the shipper. Specifically, the processor 13 displays a screen for formally requesting package delivery on the shipper terminal 3. The shipper determines whether to formally request package delivery or to abandon the package delivery request, 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 determined 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, processor 13 determines whether delivery is possible (delivery possibility) under the delivery conditions specified by the shipper in the current loaded state. Specifically, it is determined whether there is currently available space to load a new package inquired about by the shipper. Note that processor 13 may determine delivery possibility based on the loaded state at the time of package collection, based on delivery plan information.

[0064] In the second delivery possibility determination process, processor 13 determines whether delivery is possible under the delivery conditions specified by the shipper in the loaded state predicted based on the current delivery plan (delivery possibility). Specifically, it is determined whether there is enough space to load the new cargo inquired about by the shipper before the time to collect the cargo from the shipper in the loaded state predicted based on the delivery plan.

[0065] In the third delivery possibility determination process, processor 13 determines whether 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 there is free space to load the new cargo inquired about by the shipper 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 has been changed.

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

[0067] For example, when the number of parcel deliveries accepted is low, it is desirable to increase new delivery requests, so prices are 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. Prices may also be set based on the loading rate of the trucks.

[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 that increases. 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 that increases. 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 also be reflected in the price.

[0069] In addition, when a new delivery request adds cargo, the truck's driving distance (length of delivery route) is extended, so the price is set based on this increase in driving distance. Furthermore, if the delivery plan is revised to meet the delivery conditions specified by the shipper, the driving distance will be extended as a result of the revision of the delivery plan, so the price is set based on this increase in driving distance.

[0070] In addition, when a new delivery request adds cargo, waiting time may occur 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 the 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 is not possible based on the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the shipper, 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 proposal, for example, a delivery date different from the delivery date specified by the shipper is proposed. Specifically, if delivery is not possible on the delivery date specified by the shipper and delivery is possible on another day (for example, the next day), that 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). Furthermore, in the alternative proposal, for example, an arrival time different from the arrival time specified by the shipper is proposed. Specifically, if delivery is not possible at the arrival time specified by the shipper and delivery is possible if the arrival time is delayed, that time is proposed as the new arrival time. Furthermore, in the alternative proposal, for example, a collection time different from the collection time specified by the shipper is proposed. Specifically, if collection is not possible at the collection time specified by the shipper and collection is possible if the collection time is delayed or advanced, that time is proposed as the new collection time. Furthermore, in the alternative proposal, 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 delivery to a delivery center near the destination is possible, that delivery center will be suggested as a 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 with the cargo and vehicle request server 1 and the driver terminal 4.

[0075] The storage unit 22 stores programs executed by the processor 23. It 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 programs stored in the storage unit 22. In this embodiment, the processor 23 performs stowage optimization processing, loading information management processing, delivery plan management processing, and cargo status prediction processing.

[0077] In the stowage optimization process, the processor 23 determines the optimal stowage, that is, the optimal arrangement of the cargo to be loaded in the cargo compartment of the truck, based on loading information relating 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 luggage information acquired from the driver terminal 4. The loading information is information relating to the loading status of luggage on 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 relating to schedules 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 delivery plan is created in which the order of delivery (unloading) of multiple packages is changed.

[0080] In the loading status prediction process, processor 23 predicts the loading status of the truck, i.e., the status of the cargo loaded in the cargo compartment of the truck (the availability of the cargo compartment) based on the delivery plan information. Specifically, the process predicts how the loading status of the truck (the availability of the cargo compartment) will change as the cargo 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 explained. 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 luggage information is individual information about luggage loaded onto a truck. The luggage information includes information about the delivery destination (such as the name of the destination place and arrival time), information about the size of the luggage (such as information about the three dimensions: length, width, and height), information about the weight of the luggage, information about the luggage loading conditions (such as information about the top and bottom of the luggage (upside down information), no stacking), and other information about the luggage (such as fragile items, precision machinery, temperature conditions). The luggage information is updated in response to the driver's operation to input information about the luggage to be loaded and unloaded at the time of delivery and collection of the luggage on the driver terminal 4. The luggage information also includes identification information individually assigned to each luggage.

[0084] The loading information is information relating to the loading status of cargo on the truck. The loading information includes information relating to the cargo compartment of the truck (such as the size of the cargo compartment) and information relating to the loaded cargo (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] Delivery plan information is information related to schedules for delivering packages by driving trucks, etc. Delivery plan information includes information related to delivery areas (areas that trucks will drive for delivery), information related to delivery routes (place names of delivery destinations, order of delivery (unloading), and travel routes between delivery destinations), loading information, and other information related to delivery (information related to driver 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 company, and serves as reference when a shipper decides whether or not to request cargo delivery. The cargo request information includes information about delivery areas and pickup areas (such as area names), 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 a shipper when responding to an inquiry about package delivery from the shipper, as a guide for deciding whether or not to officially request package delivery. The reference price may be set within a price range. Furthermore, 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 explained. Figures 8 and 9 are sequence diagrams showing an outline 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 outline 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 at the driver terminal 4 when the cargo is delivered or collected. Next, based on the information input by the driver, 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. Next, the updated cargo information is sent from the driver terminal 4 to the delivery management server 2.

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

[0091] The freight request vehicle request server 1 first receives updated delivery plan information (including loading information) from the delivery management server 2. Next, the freight request vehicle request server 1 performs an update process to review the information of each item included in the freight request information (information on the size of deliverable cargo, reference price, etc.) based on the updated delivery plan information (including loading information). Next, the freight request vehicle request server 1 performs an update process to reflect the updated freight request information in the freight request information database. Furthermore, the freight request vehicle request server 1 transmits the latest freight request information to the shipper terminal 3 in response to a view request from the shipper terminal 3. The shipper terminal 3 displays the received freight request information on a screen, thereby presenting the latest freight 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 luggage. As a result, every time the driver loads or unloads luggage, the driver inputs information about the luggage to be unloaded, thereby updating the truck loading information, and the truck loading information is kept up to date. Note that the loading information may also be updated when a change in luggage in the luggage compartment is detected based on an image of a camera that photographs the luggage compartment of the truck or the detection result of a weight sensor that measures the weight of luggage loaded in the luggage compartment.

[0093] 9, when the consignor performs an operation on the consignor terminal 3 to inquire about delivery of the cargo to the transportation company, the inquiry about the cargo delivery is sent to the cargo and vehicle request server 1. This inquiry about the cargo delivery includes the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the consignor.

[0094] When the cargo request vehicle request server 1 receives a cargo delivery inquiry from the shipper terminal 3, it performs a process (delivery condition analysis process) to consider whether 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 Figure 2).

[0095] At this time, the delivery management server 2 executes a loading status prediction process for predicting the loading status based on the delivery plan and a delivery plan review process for creating a revised delivery plan as needed in response to instructions 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, a price is set according to the result of the delivery condition analysis process in the cargo and vehicle request server 1. Next, the cargo and vehicle request server 1 transmits a response to the inquiry about 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 by the driver terminal 4 is the same as when the cargo request information is presented to the shipper (see Fig. 8). Furthermore, the process performed by the delivery management server 2 is also approximately the same as when the cargo request information is presented to the shipper (see Fig. 8), but the updated delivery plan information (including loading information) is not sent from the delivery management server 2 to the cargo request vehicle request server 1. Furthermore, the cargo request vehicle request server 1 does not perform the process of updating the cargo request information and the process of updating the cargo request information database.

[0098] 11, when the consignor performs an operation on the consignor terminal 3 to inquire about delivery of the cargo to the transportation company, the inquiry about the cargo delivery is sent to the cargo and vehicle request server 1. This inquiry about the cargo delivery includes the delivery conditions (delivery date, arrival time, delivery destination, etc.) specified by the consignor.

[0099] When the freight vehicle request server 1 receives an inquiry about cargo delivery from the shipper terminal 3, it requests the delivery management server 2 to send 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 freight vehicle request server 1 performs an update process to review the information of each item (reference price, etc.) included in the freight request information based on the latest delivery plan information (including loading information). Next, the freight vehicle request server 1 performs an update process to reflect the updated freight request information in the freight request information database.

[0100] Next, the cargo vehicle request server 1 performs a process (delivery condition analysis process) to consider whether 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 Figure 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 cargo delivery to the shipper terminal 3.

[0101] Next, the processing 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 processing performed by the cargo vehicle request server 1. Fig. 13 is a flow diagram showing the procedure of the processing performed by the delivery management server 2.

[0102] In the cargo and vehicle request server 1, first, the processor 13 accepts an inquiry about cargo 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 cargo delivery. On the screen, the shipper can perform operations such as making an inquiry about cargo delivery and inputting cargo delivery conditions.

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

[0104] If the current state of the cargo 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 distance traveled due to the addition of cargo.

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

[0106] It should be noted that changing the delivery terms from those specified by the shipper may enable a cheaper price to be set. For example, if there is more available space (loading status) on trucks in operation on a day other than the delivery date specified by the shipper (for example, the next day), changing the delivery date and time to that date and time may enable a cheaper price to be set. In this case, in addition to a response corresponding to the shipper's delivery terms, ST111 may also present delivery terms different from the shipper's delivery terms and the prices for those terms. This may be expected to have the effect of reducing opportunity loss by distributing the delivery load.

[0107] Here, when the consignor formally requests cargo delivery, the consignor performs an operation to formally request cargo delivery on the consignor terminal 3. At this time, the cargo vehicle request server 1 causes the consignor terminal 3 to display a screen for performing operations related to the formal request for cargo delivery. On the screen, the consignor can perform operations to formally request cargo delivery and operations to input delivery conditions. In response to the screen operations on the consignor terminal 3, the cargo vehicle request server 1 performs processing to accept the formal request for cargo delivery from the consignor.

[0108] On the other hand, if the current cargo condition does not allow delivery 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 cargo condition 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 trucks 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 cargo state prediction process sent from the delivery management server 2 (ST104), the processor 13 determines whether delivery is possible (delivery possibility) under the delivery conditions specified by the shipper in the cargo state 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 based on the cargo status predicted based on the current delivery plan (No in ST105), then, under the control of processor 13, communication unit 11 sends an instruction to delivery management server 2 to execute a delivery plan review process (ST106).

[0113] 13(B), in the delivery management server 2, when the communication unit 21 receives an instruction to execute the delivery plan review process transmitted from the cargo vehicle request server 1 (ST211), the processor 23 creates a revised delivery plan proposal (delivery plan review process) (ST212). Next, the processor 23 predicts the loading status of the truck based on the revised delivery plan proposal (loading status prediction process) (ST213). Next, under the control of the processor 23, the communication unit 21 transmits the result of the loading status prediction process based on the revised delivery plan 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 results 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 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] If delivery is possible under the delivery conditions specified by the shipper in the cargo condition 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 that modifies the delivery conditions specified by the shipper 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 package delivery (ST111). If the shipper can accept the delivery conditions and price of the alternative plan, the shipper performs an operation to officially request package delivery.

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

[0118] Incidentally, there are cases where multiple revised delivery plan proposals can be created. In this case, the process of creating an alternative plan for each revised plan may be repeated. 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 the most highly evaluated alternative plans 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. Furthermore, 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 according to the present invention have the effect of increasing the number of cargo deliveries accepted by a transportation company, and enabling persuasive price negotiations by presenting prices with clear grounds to shippers, and are useful as a cargo and vehicle request system, server device, and program that executes a process of examining the possibility of delivering cargo based on delivery conditions specified by the shipper and providing a response to the shipper based on the results. [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 cargo based on delivery conditions specified by a shipper and providing a response to the shipper based on the results, The processor: If the current state of the cargo does not allow delivery based on 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 that sets the price to be offered to the shipper based on the results of the determination of the possibility of delivery.

2. The processor: If the cargo condition predicted based on the delivery plan does not allow delivery of the cargo according to the delivery conditions specified by the shipper, Determine the feasibility of delivery according to the predicted cargo status based on the revised delivery plan; 2. The cargo and vehicle request system according to claim 1, wherein a price to be offered to the shipper is set based on the result of the determination of the possibility of delivery.

3. The processor: If delivery is possible based on the predicted loading status based on the revised delivery plan, The cargo and vehicle request system according to claim 2, characterized in that the price offered to the shipper is set so as to reflect an increase in the amount of cargo handling work and the distance traveled based on the revised delivery plan.

4. The processor: If delivery is not possible based on the predicted loading status based on the revised delivery plan, Create an alternative plan that changes the delivery conditions specified by the shipper 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.

5. The processor: Update cargo request 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, wherein the possibility of cargo delivery is examined based on the cargo request information.

6. 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 that predicts a cargo status based on a delivery plan; a delivery plan review process for creating a revised delivery plan; 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 to consider the possibility of delivering 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.

7. 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, The processor: If the current state of the cargo does not allow delivery based on the delivery conditions specified by the shipper, Determine the feasibility of delivery according to the cargo status predicted based on the delivery plan; The server device sets the price to be offered to the shipper based on the result of the determination of the possibility of delivery.

8. 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 results, If the current state of the cargo does not allow delivery based on the delivery conditions specified by the shipper, Determine the feasibility of delivery according to the cargo status predicted based on the delivery plan; The program is characterized by setting a price to be offered to the shipper based on the result of the determination of the possibility of delivery.

Images