JP6626380B2 - Transportation management system - Google Patents

Description

  The present invention relates to a transportation management technique for a delivery vehicle that collects and delivers packages.

  As described in Patent Literature 1, there is a luggage transportation system that performs vehicle allocation in consideration of information on the loading ratio of vehicles and the size or weight of luggage. In Patent Literature 1, a carrier presents transportation conditions of luggage to a vehicle side, and determines that the occupants of the vehicle can satisfy the presented transportation conditions in consideration of their own work schedules. It is described that a vehicle is selected by returning a response to a trader.

Japanese Patent No. 3948204

  By efficiently assigning a delivery request from a shipper to a delivery vehicle, the loading rate can be improved and the delivery cost can be reduced, but the actual situation is not so simple. For example, a specific shipper may be delivered periodically.

  In such a case, if the transport company providing the vehicle preferentially secures the vehicle to a specific shipper, the vehicle cannot perform the delivery work of another shipper. In other words, since one vehicle cannot undertake delivery requests from a plurality of shippers, it is necessary to hold many vehicles in order to undertake delivery requests from each shipper. The more vehicles you have, the higher the delivery costs, such as labor costs.

  Therefore, it is desirable for the shipper to preferentially secure the vehicle so that, for example, a vehicle cannot be secured and regular delivery cannot be performed, or a package is not delivered on a specific delivery date. However, it is necessary to guarantee the delivery cost of vehicles that cannot perform other delivery operations, so that the delivery cost cannot be kept low even for small or large packages.

  Therefore, an object of the present invention is to provide a transportation management capable of efficiently performing delivery work of another shipper while realizing preferential vehicle securing to a specific shipper.

(1) The present invention is a transportation management system for a delivery vehicle that performs collection and delivery of requested packages, and a first storage that stores operation result data including a loading ratio for each delivery vehicle based on a delivery history accumulated daily. Unit, an operation prediction unit that generates a predicted loading ratio of each delivery vehicle from the present day to the future on the basis of the operation result data, and a storage unit that stores, for each delivery vehicle, a transaction result for each shipper based on the delivery history. (2) a storage unit, and a dispatching matching unit that performs dispatching matching processing for incorporating delivery request information requested by the shipper and having at least a future date after tomorrow as a collection / delivery date into a future operation schedule of the delivery vehicle. And

  The dispatching matching unit extracts a first candidate vehicle having a transaction record with the shipper of the delivery request based on the transaction record by shipper, and requests the delivery request using the predicted loading rate of the first candidate vehicle. A first matching process for extracting a vehicle having a baggage volume equal to or less than the predicted loading rate, and a second candidate vehicle having no transaction record with the shipper of the delivery request when no vehicle is extracted in the first matching process. And performing a second matching process of extracting a vehicle in which the volume of the requested luggage requested for delivery is equal to or less than the free loading rate using the free loading rate excluding the predicted loading rate of the second candidate vehicle.

(2) In the above (1), the vehicle allocation matching unit determines whether the collection / delivery date of the delivery request is future from a predetermined number of days from the present time, and determines that it is future from the predetermined number of days. When the first matching process and the second matching process are performed and it is determined that the future is not longer than the predetermined number of days, the volume of the requested luggage of the delivery request is changed to the predicted loading ratio of the delivery vehicle and the free loading ratio. And a third matching process for extracting a vehicle having a total empty loading rate equal to or less than the total empty loading rate.

(3) In the above (1) or (2), the transaction results for each shipper include a baggage attribute of the requested baggage, and the baggage attribute specifies in advance whether or not mutual loading is possible between the attributes of the requested baggage. Can be configured. In this case, the dispatching matching unit is configured to perform, based on the transaction record by shipper, a vehicle that has delivered the package of the package attribute included in the delivery request, or a package attribute and a requested package included in the transaction record by shipper. Each of the matching processes can be performed on a vehicle whose load attribute can be mutually loaded with the luggage attribute included in the vehicle.

(4) In the above (1) to (3), the operation status data including the loading ratio of the delivery vehicle transmitted from the delivery terminal and input by the delivery person is received, and the operation status data is received for each delivery vehicle. It can be configured to further include an operation information collection unit to collect.

(5) In the above (4), the delivery terminal may have a GPS function. The operation information collection unit may receive the position information of the delivery vehicle transmitted from the delivery terminal and collect the operation status data including the position information for each delivery vehicle. At this time, the operation prediction unit generates operation prediction area data of each delivery vehicle based on the operation status data, and the dispatching matching unit determines when a plurality of vehicles are extracted in each of the matching processes. The vehicle closest to the pickup location included in the delivery request can be configured to be extracted based on the operation prediction area data.

(6) In the above (1) to (5), operation schedule plan data in which a delivery request is incorporated into the operation schedule of the delivery vehicle extracted by each of the above matching processes is generated, and the transportation company to which the delivery vehicle belongs is generated. It can be configured to further include an operation schedule plan control unit that transmits the operation schedule plan control unit to the business operator terminal.

(7) In the above (6), a delivery request receiving unit for receiving a delivery request transmitted from a shipper terminal of the shipper, and a fare estimate for the received delivery request based on fare data set in advance for the delivery vehicle. A quotation / order control unit that generates data and transmits the data to the shipper terminal. The operation schedule plan control unit generates operation schedule plan data incorporating the delivery request after the order of the delivery request is confirmed with the shipper based on the fare estimation data, and transmits the generated data to the business operator terminal. be able to.

  ADVANTAGE OF THE INVENTION According to this invention, the delivery work of another shipper can be performed efficiently, securing a vehicle preferentially with respect to a specific shipper, so that the loading rate of one unit can be improved and the delivery cost can be reduced. be able to.

FIG. 1 is a network configuration diagram of a transportation management system according to a first embodiment. It is a functional block diagram of a transportation management device of a 1st embodiment. It is a functional block diagram of a delivery person terminal of a 1st embodiment. It is a figure showing the flow of the transportation management system of a 1st embodiment. It is a figure showing the flow of the transportation management system of a 1st embodiment. It is a figure showing an example of vehicle basic information (a) and delivery person information (b) of a 1st embodiment. It is a figure for explaining the loading information acquisition function of the delivery person terminal of a 1st embodiment. It is a figure showing an example of vehicle position and loading information of a 1st embodiment. It is a figure showing an example of operation record information of a 1st embodiment. It is a figure showing an example of delivery request information of a 1st embodiment. It is a figure showing an example of operation prediction data containing an operation prediction area and an operation prediction loading rate of a 1st embodiment. FIG. 12 is a schematic diagram illustrating the operation prediction data illustrated in FIG. 11 in a itinerary table format (time chart format). It is a mimetic diagram for explaining dispatch allocation matching processing using a predicted loading rate of a 1st embodiment. FIG. 7 is a diagram illustrating an example in which a delivery request is incorporated into a delivery schedule by the vehicle allocation matching process of the first embodiment. It is a figure showing the dispatch matching processing flow of a 1st embodiment. FIG. 16 is a diagram showing a vehicle allocation matching processing flow of the first embodiment following FIG. 15. It is a figure showing an example of matching using an operation prediction area.

  Hereinafter, embodiments will be described with reference to the drawings.

(1st Embodiment)
1 to 17 are diagrams showing a first embodiment. FIG. 1 is a network configuration diagram of the transportation management system of the present embodiment. As shown in FIG. 1, a shipper (shipper terminal 400) making a delivery request and a shipper (a shipper) who is a delivery destination of a package based on the delivery request are centered on a transport management device (hereinafter, referred to as a management device) 300. The terminal 500) and a transportation company that delivers the package (the business terminal 200 and the delivery terminal 100) are connected via a network. The network may be a wireless communication network / wired communication network, a dedicated line network, or the like. For example, a network such as the Internet can be used.

  FIG. 2 is a functional block diagram of the management device 300. The management device 300 includes a communication device 310, a control device 320, and a storage device 330. The communication device 310 controls data communication with each terminal connected via a network.

  The control device 320 includes a vehicle registration unit 321, an operation information collection unit 322, an operation information providing unit 323, an operation prediction unit 324, a delivery request reception unit 325, a vehicle allocation matching unit 326, an estimate / order control unit 327, and an operation schedule plan control unit. 328 and a transaction result section 329.

  FIG. 3 is a functional block diagram of the delivery terminal 100 of the present embodiment. The delivery terminal 100 includes a communication unit 110, a control unit 120, a storage unit 130, a display unit 140, an operation unit 150, and an imaging unit 160. The control unit 120 includes an operation status control unit 121 and an operation schedule data control unit 122, and the operation status control unit 121 includes a GPS control unit 121A and a loading information control unit 121B. The delivery terminal 100 is, for example, a portable information terminal having a wireless communication function.

  FIG. 4 and FIG. 5 are flowcharts showing the processing flow of the transportation management system of the present embodiment. The transport management system is a management system that aggregates and manages delivery requests from shippers and creates and provides an operation schedule plan for each delivery vehicle in response to the delivery request on behalf of the transport company that controls the delivery vehicles. is there. In addition, it has a function of providing a delivery cost estimate and a purchase order for a delivery request on behalf of the carrier, and supports order management of the delivery request between the shipper and the carrier.

  As shown in FIG. 4, the transport company registers a delivery vehicle and a delivery member when using the present transport management system. The vehicle registration unit 321 communicates with the business operator terminal 200 connected to the management apparatus 300 regarding the business operator information of the transport business operator and a plurality of delivery vehicles and delivery personnel (eg, drivers) managed by the transport business operator. Controls registration of information. Note that the delivery vehicle and the delivery person may include a sole proprietor who has made a contract with a transport company.

  For example, when the business operator terminal 200 connects to the management device 300 and makes a vehicle registration request (S201), the vehicle registration unit 321 transmits a predetermined vehicle / delivery person registration screen to the business operator terminal 200, and performs vehicle / delivery. Input control and display control for the member registration screen are performed. By inputting vehicle basic information and deliveryman information via the vehicle / deliveryman registration screen, the business operator can register each delivery vehicle and each deliveryman under his jurisdiction. The vehicle registration unit 321 performs a registration process of storing the vehicle basic information and the delivery person information input on the vehicle / delivery person registration screen in the storage device 330 (S301).

  FIG. 6A is a diagram illustrating an example of the vehicle basic information, and includes a vehicle ID, a vehicle height, a cargo room volume, and the like for each carrier ID for identifying each transport carrier. FIG. 6B is a diagram showing an example of deliveryman information, which includes a deliveryman ID for identifying each deliveryman, name, age, qualification, and the like.

  Note that the registration of the vehicle basic information and the delivery staff information can also be performed by the management side of the management device 300. For example, the transportation company sends the vehicle basic information and the delivery staff information based on the paper medium to the operation side of the management device 300 by facsimile or mail, and the input person on the operation side transmits the vehicle basic information through the registration function of the vehicle registration unit 321. Information and deliveryman information can be registered.

  The business terminal 200 receives the operation schedule data for the registered delivery vehicle from the management device 300 and transmits the operation schedule data to the corresponding delivery staff terminal 100 (S202). The operation schedule data control unit 122 of the delivery terminal 100 stores the received operation schedule data in the storage unit 130 (S101).

  The operation schedule data control unit 122 displays a delivery operation start screen on the display unit 140, and controls the delivery member to input a vehicle ID and a delivery member ID. The deliveryman inputs the vehicle ID and the deliveryman ID via the operation unit 150 such as an input button or a touch panel, and selects the business start button. When the operation start button is selected, the operation schedule data control unit 122 transmits data indicating the start of the distribution operation including the vehicle ID and the delivery member ID to the management device 300 (S102). Further, the operation schedule data control unit 122 outputs a trigger signal to the GPS control unit 121A to start the process of acquiring the position information of the delivery terminal 100 (delivery vehicle). At this time, the operation schedule data control unit 112 can also display an operation schedule data plan table in which delivery requests for today's day are arranged in chronological order on the display unit 140 (S103).

  The GPS control unit 121A of the delivery terminal 100 acquires the location information of the moving delivery vehicle during the delivery operation at predetermined intervals, and transmits the GPS data of the delivery vehicle to the management device 300 (S104). In addition, at the collection location and the delivery location of the delivery request, the delivery person registers the loading information after loading the package and the loading information after unloading at the delivery location in the management device 300. The loading information control unit 121B provides a loading information acquisition function as shown in FIG. 7 (S105).

  In the example of FIG. 7, the deliveryman starts loading information from the deliveryman terminal 100 after loading the package at the pickup location. The loading information control unit 121B displays the screen A on the display unit 140. When the loading rate registration button is selected, the loading information control unit 121B displays the screen B, and displays a message in which the delivery unit captures the luggage room after loading by the capturing unit 160. Output. The delivery member selects the camera activation button (icon) on the screen B to activate the photographing unit 160, and photographs the luggage compartment after loading the luggage. The screen C is a screen that displays a captured image of the luggage room captured by the capturing unit 160. On the screen C, the delivery person checks the captured image of the luggage room.

  Subsequently, the loading information control unit 121B displays the screen D. The screen D includes a loading rate selection field for selecting or inputting a loading rate, and the delivery person selects, for example, the loading rate of the photographed luggage room from a plurality of preset loading rate selection information. The loading information control unit 121B displays a pre-transmission confirmation screen E including the captured image of the luggage compartment and the selected loading rate on the display unit 140, and when the transmission button is selected on the screen E, the loading rate and the captured image are displayed. Generated transmission data (loading information) is transmitted to the management device 300 (S106).

  Note that, when the loading information is registered from the delivery terminal 100, the captured image of the luggage room is transmitted to the management device 300, but is not limited thereto. For example, without photographing the luggage room itself, the delivery staff selects the loading rate visually checked from a plurality of preset loading rate selection information, or the delivery staff directly inputs the loading rate. Then, it may be configured to be registered in the management device 300.

  The operation information collection unit 322 of the management device 300 receives the GPS data and the loading information of the delivery vehicle transmitted from the delivery terminal 100, and performs an operation information collection process of accumulating the operation status of each delivery vehicle in time series ( S302). The operation information collection unit 322 can receive the GPS data and the loading information from the delivery terminal 100 in real time or collectively after the end of a day's delivery operation, and store it in the storage device 330. In addition, the operation information acquisition unit 322 can perform control such that the operation status data of each delivery vehicle is stored in the storage device 330 for each day of delivery work (daily).

  FIG. 8 is a diagram illustrating an example of the vehicle position / loading information. As shown in FIG. 8, for each delivery vehicle (vehicle ID), the GPS data and the loading ratio of the delivery vehicle are arranged in chronological order. The operation information collection unit 322 assigns a sequence number every time the GPS data and the loading information are received from the delivery terminal 100, and operates the vehicle position / loading information including the date, time, empty space ratio of the loading platform, and the like. Store as situation data.

  Further, as shown in FIG. 9, the operation information collecting unit 322 can generate operation result information based on the operation status data of FIG. 8 (S304). The operation result information includes a result date, a vehicle ID, a delivery member ID, a delivery request number, a collection time at a collection location, GPS data and an empty volume ratio (100-loading ratio), a baggage volume, a reception time at a reception location, and a receipt (delivery). ) Includes GPS data and empty volume ratio (100-loading ratio) of the location.

  The operation status data and the operation result information shown in FIGS. 8 and 9 are daily delivery histories of each vehicle. The operation status data is information obtained by tracing the daily operation status in real time, and the operation result information is information indicating daily operation results generated from the operation status data. Therefore, the information generated based on the operation result information can be generated from the operation status data.

  For example, the collection time can be calculated from the operation status data shown in FIG. 8 as the time from arrival at the collection location to completion of collection. Here, the time at which the delivery vehicle arrives at the pickup location is determined, for example, at the desired pickup time to determine whether the vehicle position based on the GPS data is within the range of the location information of the pickup location that can be grasped in advance from the delivery request. By doing so, it is possible to know the time when the delivery vehicle arrives at the pickup location. Further, by determining whether or not the delivery vehicle is stopped at the pickup location based on the GPS data (eg, GPS data that is continuous in time series stays at the same position for a predetermined time), the delivery vehicle is determined to be at the pickup location. The time of arrival can be determined.

  In addition, the end of collection can be determined based on the transmission data of the loading information received from the delivery terminal 100 in the loading information acquisition process described above. The empty volume ratio can be calculated based on the loading ratio received from the delivery terminal 100. The same applies to receiving time. As shown in the example of FIG. 8, when starting the delivery business or ending the delivery business, for example, at the base of the delivery vehicle, the delivery person performs the loading information acquisition processing shown in FIG. It can be reflected in the situation data.

  The operation information providing unit 323 of the management device 300 can provide the vehicle originating terminal 400 and the receiving terminal 500 with vehicle grasping information based on the operation status data shown in FIG. 8 (S303). For example, for each delivery request, it is possible to provide a map map in which the current vehicle position and delivery location are displayed by icons, and vehicle grasp information including estimated arrival times and the like. The operation information providing unit 323 acquires the operation status data of the corresponding delivery vehicle from the storage device 330 based on the vehicle grasp request including the delivery request number from the shipper terminal 400, and corresponds to the latest GPS data of the delivery vehicle. It is possible to generate a map map in which the symbol mark (vehicle object) of the delivery vehicle is arranged on the map coordinates to be displayed. Further, a map map in which the trajectory of the delivery vehicle is traced can be displayed on the map based on the operation status data including the time-series vehicle positions.

  In addition, the operation information providing unit 323 can also provide the business operator terminal 200 with a map map including the current position and the movement locus of one or more delivery vehicles for the operation business operator. In this case, the operation information providing unit 323 can also control, for example, to display the symbol mark of each delivery vehicle with the loading rate included. By displaying each symbol mark of a plurality of delivery vehicles on one map map, the operating company can grasp the operation status of the plurality of delivery vehicles under its jurisdiction.

  The operation prediction unit 324 generates operation prediction data including an operation prediction area and an operation prediction loading rate of each delivery vehicle based on the operation status data of FIG. 8 (S305). The operation prediction data of each delivery vehicle is used for generation of delivery schedule data of the delivery vehicle in response to a delivery request from a shipper, that is, for matching of delivery vehicles to the delivery request. The process of generating the operation prediction data will be described later. The operation prediction area and the operation prediction loading rate can be generated as individual operation prediction data.

  The operation schedule data control unit 122 of the delivery staff terminal 100 displays a delivery business end screen on the display unit 140 based on the operation input by the delivery staff, transmits data indicating the end of the delivery business to the management device 300, and Control is performed so as to end the GPS data acquisition process by the situation control unit 121.

  The delivery person, for example, inputs the vehicle ID and the delivery person ID via the operation unit 150, and selects the work end button. When the operation end button is selected, the operation schedule data control unit 122 transmits data indicating the end of the distribution operation including the vehicle ID and the delivery member ID to the management device 300 (S107). Note that the delivery operation end process in combination with the loading information acquisition process shown in FIG. 7 can also be performed. For example, at the time of loading information acquisition processing at a delivery place or a delivery vehicle base where the delivery of the last delivery request has been completed, a button for selecting the end of the delivery operation is displayed to indicate the end of the delivery operation together with the loading information. The data can be transmitted to the management device 300.

  The transaction record unit 329 generates transaction ratio information based on the operation record information and the delivery request information for each registered delivery vehicle, and stores the transaction ratio information in the storage device 330 (S306). The transaction ratio information is a transaction history indicating the transaction results of each shipper, and will be described later in detail.

  Next, with reference to FIG. 5, a processing flow until a delivery vehicle of a transportation company is dispatched in response to a delivery request from a shipper will be described. As illustrated in FIG. 5, the delivery request receiving unit 325 of the management device 300 controls a delivery request with the shipper terminal 400 connected to the management device 300. The delivery request receiving unit 325 transmits, for example, a predetermined delivery request screen to the shipper terminal 400 (S311), and performs input control and display control on the delivery request screen. The shipper can input delivery request data via the delivery request screen (S401), and make a delivery request. The delivery request receiving unit 325 receives the delivery request data input from the delivery request screen and stores it in the storage device 330 (S312).

  FIG. 10 is a diagram illustrating an example of the delivery request information. For each delivery request, delivery request number, request date, client (shipper) ID, package type, collection location, desired collection time (start), desired collection time (end), package volume, number, delivery (receipt) location , Delivery (load receipt) desired time (start), delivery (load receipt) desired time (end), and the like. The delivery request screen is configured to include these input items.

  Here, the luggage volume can be input on the shipper's side, but it can also be configured so that the delivery request receiving unit 325 automatically calculates it. For example, when the shipper inputs the model number and the number of the standard corrugated cardboard, the delivery request receiving unit 325 refers to the volume information for each model number stored in the storage device 330 in advance, and determines the delivery request based on the number to be delivered. The volume of the entire package can be calculated. The method of calculating the volume of the entire package requested for delivery is not limited to this, and a known technique can be applied as appropriate.

  The vehicle assignment matching unit 326 performs a vehicle assignment matching process of assigning a delivery request from a shipper to a plurality of delivery vehicles registered by the carrier using the operation prediction data (S313). The vehicle allocation matching process will be described later.

  As a result of the vehicle allocation matching process, when it is determined that there is no allocation vehicle, that is, there is no distribution vehicle capable of incorporating (contracting) a distribution request (NO in S314), the distribution request receiving unit 325 determines whether the distribution request content is A correction notification process is performed (S315). The delivery request receiving unit 325 transmits a selection screen for selecting whether to correct the contents of the delivery request to the shipper terminal 400. When the shipper selects “correct” (YES in S402), the process returns to step S401, and the delivery request receiving unit 325 transmits a delivery request screen including the input delivery request content to the shipper terminal 400. The shipper corrects the desired collection time, the desired delivery time, the number of packages, and the like from the delivery request screen. The modified delivery request is transmitted from the shipper terminal 400 to the management device 300. If the shipper selects “do not modify” (NO in S402), a delivery request cancellation request is transmitted from the shipper terminal 400 to the management device 300 (S403), and the delivery request receiving unit 325 inputs the request in step S401. A process to stop accepting the delivery request is performed (S316).

  As a result of the vehicle allocation matching process, when it is determined that there is an allocated vehicle (YES in S314), the vehicle allocation matching unit 326 performs a temporary vehicle allocation notification process to indicate that a delivery request is allocated to the delivery vehicle of the transport company. The provisional notification is transmitted to the business operator terminal 200 (S317).

  When it is determined that there is a reserved vehicle (YES in S314), the quote / order control unit 327 calculates the fare related to the delivery request and generates quote data. For example, shipping fee data can be obtained in advance from a carrier and stored in the storage device 330, and the shipping fee for the delivery request can be calculated according to the volume, number, weight, etc. of the delivery request. The quotation / order control unit 327 generates quotation data and order form data for the delivery request, and performs quotation / order form issuance processing to be transmitted to the shipper terminal 400 (S318).

  The shipper transmits order data (order OK / NG) based on the order form data from the shipper terminal 400 to the management device 300 (S404). The quotation / order control unit 327 receives the order data transmitted from the shipper terminal 400, and if the order is NG (NO in S319), performs a cancel process for the corresponding delivery request (S320). As the cancellation process, for example, a notification for canceling the provisional vehicle allocation notification in step S317 can be transmitted to the business operator terminal 200, or the delivery request itself can be held or discarded (deleted).

  On the other hand, when the estimate / order control unit 327 determines that the order data transmitted from the shipper terminal 400 is order OK (YES in S319), the operation schedule plan control unit 328 performs matching in the vehicle allocation matching process. Operation schedule plan data in which the delivery request is incorporated into the operation schedule data of the delivery vehicle, in other words, the operation schedule data of the delivery vehicle, is generated and stored in the storage device 330 (S321). The operation schedule plan control unit 328 transmits the generated operation schedule plan data to the operator terminal 200 (S322), and the operator terminal 200 transmits the vehicle allocation schedule data based on the operation schedule plan data to the delivery terminal 100. (S203).

  In addition, the estimate / order control unit 327 can also transmit the estimate data and the order data to the shipper by FAX. In this case, the shipper sends the order form including the order OK or order NG to the management side of the management apparatus 300 by facsimile, and uses the function of the quotation / order form control unit 327 on the management side of the management apparatus 300 to place the order. You can enter data.

  As described above, in the transportation management system according to the present embodiment, the management device 300 receives the delivery request data from each shipper terminal 400, assigns the delivery request to a plurality of delivery vehicles registered by the transport company, and performs the vehicle assignment matching process. Do. The management device 300 generates the transportation schedule plan data of each delivery vehicle in which the delivery request based on the result of the vehicle assignment matching process is incorporated, and provides the data to the company terminal 200.

  In the present embodiment, the daily operation status of the delivery vehicles is grasped, and the delivery request is assigned to each delivery vehicle using the operation prediction data including at least the operation prediction loading rate, so that the shipper who has a transaction record is By realizing priority vehicle securing and enabling other shippers to carry out delivery operations, the loading rate per delivery vehicle is improved, and efficient delivery of vehicles to multiple delivery vehicles under the control of the transport company. Provide an appointment. Hereinafter, the operation prediction data generation processing and the vehicle allocation matching processing according to the present embodiment will be described in detail.

<Operation forecast data generation processing>
In this embodiment, based on the operation result information (operation state data), the operation predicted loading rate of each delivery vehicle from the present time to the future each day is generated. For example, as shown in FIG. 8 and FIG. 9, since past operation status data and operation result information are accumulated, each delivery such as day, day of the week, week, month, quarter, half year, one year, etc. It is possible to grasp the delivery history including the actual operation route of the vehicle and the loading rate.

  As an example of generating the future operation predicted loading rate and the operation prediction area, for example, when the current date (X day) is February 15, 2016 (Monday), tomorrow ((X + 1) day) February 16 ( As the operation prediction data on Tuesday, it is possible to extract the delivery history of every past Tuesday, calculate the average loading rate for each predetermined time period from the delivery history on each Tuesday, and apply this as the tomorrow's operation prediction loading rate. it can.

  The same applies to the operation prediction area. An area based on each vehicle position in each time zone (for example, an area within a predetermined range including each vehicle position) is calculated from the past delivery history of every Tuesday, and this is calculated tomorrow. It can be applied as an operation prediction area. In this way, the operation prediction data of each future day ((X + 1) day, (X + 2) day,..., (X + n) day) from the current date is generated and stored in the storage device 330.

  FIG. 11 is a diagram illustrating an example of operation prediction data including an operation prediction area and an operation prediction loading rate. The operation prediction data can be configured to be partitioned at predetermined time intervals and include coordinate information (coordinate information on a map) of each operation prediction area arranged in chronological order and the operation prediction loading rate. FIG. 12 is a schematic diagram showing, in the operation prediction data shown in FIG. 11, the operation prediction loading rate in the itinerary table format (time chart format).

  The operation prediction unit 324 can update the operation prediction data every time the daily operation results (operation status data) are accumulated, and change based on the operation results each time the operation prediction data generation processing is performed. . For example, if the current operation status data on February 15 is accumulated, the operation prediction area and the operation prediction loading rate on February 22, 2016 (Monday) next week will be the current delivery history on February 15 Reflected and updated. The operation prediction data generation processing can be performed in real time, or can be performed at long-term timing such as one week, one month, or six months.

  The example of generating the operation prediction data described above is an example, and the present invention is not limited to this example. The operation prediction data can be generated using various methods. For example, it is also possible to generate operation prediction data in consideration of a time instead of a day of the week. When the operation prediction data for a certain day in May 2016 next month is generated using a certain day in April 2016 as the current date, March, April, May, May of last year, and March, 2016 of the same period last year, It is possible to extract the actual delivery history data for April, and to generate operation prediction data for each daily time zone based on comparisons, trends, and the like of past data.

<Vehicle allocation matching processing>
FIG. 13 to FIG. 17 are diagrams for explaining the vehicle allocation matching process of the present embodiment. The vehicle allocation matching process according to the present embodiment is a process for incorporating a delivery request requested by a shipper and having at least a future day after tomorrow from the present time as a collection and delivery date into a future operation schedule of the delivery vehicle. Note that the vehicle allocation matching unit 326 can perform the vehicle allocation matching process with the current day as the collection and delivery date, and can also perform the vehicle allocation matching process with the same day as the collection and delivery date by a process different from the vehicle allocation matching unit 326. You can also.

  The vehicle assignment matching unit 326 extracts the first candidate vehicle having the transaction result with the shipper of the delivery request based on the transaction result for each shipper, and uses the operation predicted loading rate of the first candidate vehicle to calculate the requested package of the delivery request. A first matching process for extracting a vehicle whose volume is equal to or less than the predicted operation loading ratio, and a second candidate vehicle having no transaction record with the shipper of the delivery request when no vehicle is extracted in the first matching process; Using the free loading rate excluding the predicted operation loading rate of the candidate vehicles, a second matching process is performed to extract vehicles in which the volume of the requested luggage of the delivery request is equal to or less than the free loading rate.

  FIG. 13 is a schematic diagram for explaining a vehicle allocation matching process using the predicted operation loading ratio. The delivery request includes a package V (package volume), a shipper S, and a package type X. First, the vehicle assignment matching unit 326 refers to the transaction ratio information and extracts a delivery vehicle having a transaction record with the shipper S who has requested delivery.

  Here, as shown in FIG. 13, the transaction ratio information is information including a shipper who has delivered in the past and the type of the package (package attribute) for each delivery vehicle. , The ratio of the number of delivery requests of the shipper to the total number of delivery requests accepted within a certain period in the past. It should be noted that, other than the number of delivery requests, it may be a ratio of the total amount of the delivery charges of the shipper to the total amount of the above-mentioned transportation charges within a certain period in the past.

  The luggage type is information that defines the attribute of the requested luggage, and is information for identifying each luggage such as food, daily necessities, and clothes. The package type can preliminarily determine whether or not mutual loading is possible between the attributes of the requested package. For example, since the luggage type: foodstuffs may give off an odor, the luggage type: stored in the storage device 330 as mutual loading rule information that specifies whether or not clothes can be mutually loaded (OK / NG). I can put it. It is to be noted that mutual loading means not only that the loading on the loading platform is NG, but also that after carrying one type of loading between the loading types of which the loading is NG, the other type of loading is performed. Forbidden to carry.

  The vehicle allocation matching unit 326 can extract the vehicle A and the vehicle C as the delivery vehicles having the transaction record with the shipper S who has requested the delivery (circle 1 in FIG. 13). Then, the vehicle allocation matching unit 326 uses the extracted predicted operation load rates of the vehicles A and C to determine that the volume of the package V is equal to or less than the predicted operation load rate, and that the volume of the package V is the same as the predicted operation load rate. A nearby vehicle is extracted (circular character 2 in FIG. 13). In the case of the vehicle A, since the volume of the package V exceeds the predicted operation loading ratio, the vehicle C having the volume of the package V equal to or less than the predicted operation loading ratio is extracted as the allocation vehicle, and the vehicle C A delivery request is assigned (circle 3 in FIG. 13). The processing of circled characters 1 to 3 in FIG. 13 corresponds to the first matching processing.

  Here, in the first matching processing, if a delivery request (scheduled to be determined) has already been assigned to the area of the predicted operation loading rate, it is not extracted as the first candidate vehicle. Can be configured so that no delivery request is assigned. For example, the vehicle allocation matching unit 326 determines in step S503 or S504 in FIG. 15 whether or not a scheduled area is assigned to the predicted operation loading rate, and only one delivery request is assigned to the area of the predicted operation loading rate. Can be assigned.

  On the other hand, in the processing of the circled character 2 in FIG. 13, the vehicle allocation matching unit 326 determines whether the vehicle having the volume of the baggage V equal to or less than the predicted operation load ratio is not extracted from the vehicles having the transaction history with the shipper S. , A vehicle having no transaction record with the shipper S is extracted (circle 4 in FIG. 13). For example, the vehicles B and D are extracted as vehicles having no transaction record with the shipper S. Next, the vehicle allocation matching unit 326 uses the free area (100-operated predicted loading rate = free loaded rate) excluding the predicted operating loading rate without using the predicted operating loading rates of the vehicles B and D, and calculates the load V The vehicle whose volume is less than or equal to the free area and whose volume of the load V is closest to the free area is extracted (circle 5 in FIG. 13). In the case of the vehicle B, since the volume of the baggage V exceeds the free area, the vehicle D having the volume of the baggage V equal to or smaller than the free area is extracted as the allocation vehicle, and the delivery request of the shipper S is assigned to the vehicle D. (Circular character 5 in FIG. 13). The processing of the circled characters 4 and 5 in FIG. 13 corresponds to the second matching processing.

  Here, in the second matching process, even if a delivery request (scheduled to be determined) has already been assigned to the free area, the free area may be configured to be extracted as a second candidate vehicle. For example, the free area may be obtained by dividing the predicted operation load rate and the scheduled area from the entire area, and a plurality of delivery requests may be assigned to the free area. Further, similarly to the first matching process, it may be configured such that only one delivery request is assigned to the free area.

  FIG. 14 is a diagram illustrating an example in which a delivery request is incorporated into a delivery schedule by the vehicle allocation matching process of the present embodiment. As shown in FIG. 14, for each registered delivery vehicle, the operation prediction loading rate of each day from the present time to the future is stored in the storage device 330 by the operation prediction data generation processing. The operation predicted loading rate for each day in the example of FIG. 14 is shown in a itinerary table format as shown in FIG.

  As shown in FIG. 14, for the registered delivery schedule of each vehicle, for example, a delivery request is assigned to an area of the predicted operation loading rate (predicted loading area) and a free area (100−predicted loading rate) ( Overwritten). Note that the fixed scheduled area is an area to which a delivery request has already been assigned. If a delivery request has already been assigned to a free area, the remaining area is a free area.

  If a delivery request has already been assigned to the predicted loading area, an area obtained by subtracting the scheduled area from the predicted loading area can be assigned to the free area. In other words, the predicted loading area after the delivery request is assigned can be configured not to assign another delivery request. The second matching process can be performed by changing to the free area and expanding the free area.

  Then, as shown in FIG. 14, in the present embodiment, it is determined whether or not the collection / delivery date of the delivery request is future than a predetermined number of days from the present time, and when it is determined that it is future than the predetermined number of days, When the first matching process and the second matching process are performed and it is determined that the future is not more than a predetermined number of days, the volume of the requested baggage of the delivery request is equal to or less than the entire vacant loading ratio including the predicted loading region and the free region of the delivery vehicle. A third matching process for extracting a vehicle to be performed is performed.

  That is, for the period up to a predetermined number of days ahead of the current time, the predicted loading area to which the delivery request is not assigned is set to the free area without using the predicted loading rate for the operation of the delivery vehicle as an empty area and using the predicted loading rate for the operation. Make changes to free up priority allocations for past transactions. In this case, as described above, even if a delivery request has already been assigned to the predicted loading area, if there is a vacancy in the predicted loading area, the free area is changed to the free area, and the free area is extended. You may.

  On the other hand, in the future ahead of the predetermined number of days with respect to the present, the vehicle allocation matching process that secures the priority assignment area of the delivery request based on the past transaction results is performed using the predicted operation loading rate. In other words, the predicted operation loading rate is an allocation area that is allocated preferentially in order to allocate future delivery requests to shippers who have a transaction record, and the free area is the delivery area of shippers who have a transaction record. On the other hand, it is an area secured for allocating a delivery request of a shipper who has no transaction record as another job.

  FIG. 15 is a diagram showing a vehicle allocation matching processing flow of the present embodiment. As shown in FIG. 15, the vehicle dispatch matching unit 326 extracts the volume of the requested package, the shipper, and the package type together with the collection location, the desired collection time, the delivery location, and the desired delivery time from the delivery request information of the sender (S501). . At this time, when storing the delivery request information received from the shipper in the storage device 330, the delivery request receiving unit 325 converts the address information of the collection location and the delivery location into coordinate information on the map, and stores the delivery location and the delivery location. And the delivery request information including the coordinate information on the map together with the address information.

  Next, the vehicle allocation matching unit 326 determines whether or not the collection date of the delivery request information to be matched is a future date after a predetermined number of days from the current date (S502). If it is determined that the collection date is a future date after a predetermined number of days from the current date, the process proceeds to step S503, where the first matching process and the second matching process are performed. If it is determined that the collection date is a future date that is less than the predetermined number of days from the current date, the process proceeds to A (S601) in FIG. 16 to perform a third matching process.

  In step S503, the vehicle assignment matching unit 326 refers to the transaction ratio information, and has a transaction record with the shipper of the delivery request information (transaction ratio> 0) and can carry the package type of the delivery request information (first candidate vehicle). Is extracted. Here, in the baggage type check processing for determining whether or not the vehicle can carry the baggage type of the delivery request information, for example, the baggage type associated with the shipper's transaction record includes the package type of the delivery request information. It is determined based on the mutual loading rule information whether or not the package type that is not included is a package type that is associated with the transaction result and that has mutual loading OK. The baggage type check process can be performed in the first to third vehicle allocation matching processes.

  The vehicle allocation matching unit 326 extracts the operation predicted loading rate at the desired collection time of the delivery request information from the operation prediction data for one or a plurality of vehicles extracted in step S503, and matches the volume of the requested luggage ( S504). The vehicle allocation matching unit 326 extracts vehicles whose requested luggage volume is equal to or less than the predicted operation load ratio using the predicted operation load ratio. When a plurality of vehicles whose requested baggage volume is equal to or less than the predicted operation load ratio are extracted, the vehicle whose requested baggage volume is closest to the predicted operation load ratio, that is, the requested baggage volume is subtracted from the predicted operation load ratio. The vehicle with the smallest difference is extracted (S505).

  In step S506, the vehicle allocation matching unit 326 determines whether a plurality of vehicles have been extracted in step S505. When it is determined that a plurality of vehicles have been extracted, the vehicle allocation matching unit 326 proceeds to step S507, and uses the operation prediction area data to determine the position (the distance or time) of the shortest (distance or time) from the plurality of vehicles to the pickup location. The vehicle to be extracted is extracted as an allocation vehicle for the delivery request information to be matched (S507).

  FIG. 17 is a diagram illustrating an example of matching using the operation prediction area data. As shown in FIG. 17, for each vehicle, operation prediction data at the desired pickup time is generated. Therefore, it is possible to extract a vehicle that includes the pickup location P in the operation prediction area at the desired pickup time and has the shortest access distance or time from the center of the operation prediction area. By using the operation prediction area, allocation prioritization of vehicles predicted to be in the area of the collection location or the receiving location of the delivery request information can be performed. The operation prediction data can improve the accuracy of the vehicle assignment matching process, and can be used for analysis of, for example, how many vehicles are in a certain area or a certain vehicle has a high ratio in a certain area.

  On the other hand, if it is determined in step S505 that no vehicle whose requested luggage volume is equal to or smaller than the predicted operation loading ratio is extracted, the process proceeds to step S508 to perform a second matching process. In step S508, the vehicle allocation matching unit 326 refers to the transaction ratio information, and has no transaction record with the shipper in the delivery request information (transaction ratio = 0), and can carry the package type of the delivery request information (second candidate vehicle). Is extracted.

  The vehicle allocation matching unit 326 extracts a free area at the desired collection time of the delivery request information from the operation prediction data for one or a plurality of vehicles extracted in step S508, and matches the free area with the requested package volume (S509). . The vehicle allocation matching unit 326 extracts vehicles in which the volume of requested luggage is equal to or less than the free area using the free area without using the predicted operation loading ratio. When a plurality of vehicles whose requested baggage volume is equal to or smaller than the free area are extracted, the vehicle whose requested baggage volume is closest to the free area, that is, the vehicle in which the difference obtained by subtracting the requested baggage volume from the free area is the smallest. Is extracted (S510).

  In step S511, the vehicle allocation matching unit 326 determines whether a plurality of vehicles have been extracted in step S510. If it is determined that a plurality of vehicles have been extracted, the vehicle allocation matching unit 326 proceeds to step S512, and uses the operation prediction area data to determine the shortest distance (distance or time) from the plurality of vehicles to the pickup location. A vehicle to be extracted is extracted as an allocation vehicle for the delivery request information to be matched (S512).

  In step S510, if the allocation vehicle for the delivery request information to be matched is not extracted in the second matching process (S508 to S510) after the first matching process (S503 to S505) (NO in S510), the matching vehicle It is determined that there is no processing, and the process ends.

  FIG. 16 is a diagram showing a process flow of the third matching process when it is determined in step S502 in FIG. 15 that the pickup date is a future date that is less than the predetermined number of days from the current date (NO in S502). .

  In step S601, the vehicle allocation matching unit 326 refers to the transaction ratio information and extracts vehicles that can carry the package type of the delivery request information, as in step S503 in FIG. The vehicle allocation matching unit 326 extracts, from one or more vehicles that can carry the package type of the delivery request information, the predicted operation loading ratio and the free area at the desired collection time of the delivery request information from the operation prediction data. At this time, the vehicle allocation matching unit 326 releases the entire operation predicted loading rate if the scheduled operation area is not assigned to the predicted operation loading rate, and releases an empty area as the free area if the scheduled operation area is allocated. Then, the entire free area excluding the area to be fixed is set as a free area and matched with the volume of the requested luggage (S602). The vehicle allocation matching unit 326 uses the entire free area irrespective of the predicted operation loading ratio, and extracts a vehicle whose requested baggage volume is equal to or less than the free area and whose requested baggage volume is closest to the free area (S603). .

  In step S604, the vehicle allocation matching unit 326 determines whether a plurality of vehicles have been extracted in step S603. When it is determined that a plurality of vehicles have been extracted, the vehicle allocation matching unit 326 proceeds to step S605, and uses the operation prediction area data to determine the position (the distance or time) from the plurality of vehicles to the shortest distance (distance or time) to the pickup location. The vehicle to be extracted is extracted as an allocation vehicle for the delivery request information to be matched.

  In step S603, if no allocation vehicle is extracted for the delivery request information to be matched in the third matching process (S601 to S603) (NO in S603), it is determined that there is no matching vehicle, and the process ends.

  According to the present embodiment, an operation predicted loading rate of each vehicle from the present time to the future on each day is generated from the daily delivery history (operation results). The predicted operation loading rate is used to incorporate a future delivery schedule from the present time. Based on the transaction results for each shipper and the predicted operation loading rate, a delivery request with a future collection date is matched and a reserved vehicle is extracted. On the other hand, for vehicles having no transaction record with the shipper of the delivery request, the delivery request is assigned using the free loading ratio excluding the predicted operation loading ratio without using the predicted operation loading ratio.

  With this configuration, for the shipper, the vehicle is preferentially secured, and the vehicle cannot be secured and regular delivery cannot be performed, or the package may not be delivered on a specific delivery date. In addition to being restrained, the transport company that provides vehicles will be able to carry out delivery work of other shippers while preferentially securing vehicles for specific shippers, so it is necessary to have many vehicles to carry In addition, delivery costs such as labor costs can be reduced.

  In other words, with regard to future delivery schedules, priority loading of vehicles to specific shippers is realized using transaction results and predicted operation load rates, while division as a separate job from specific shippers, free loading Provide freight management that can efficiently carry out delivery work of other shippers using the rate. Since the delivery request can be efficiently matched with the divided prediction and the vacancy, the loading rate per vehicle can be improved, and the delivery cost can be reduced.

  Further, in the present embodiment, as shown in FIGS. 14 and 16, during the period up to a predetermined number of days from the present, the operation predicted loading rate is released as an empty area without using the operation predicted loading rate. To free up the priority allocation area for past transaction results. With this configuration, it is possible to increase the chances of assigning a delivery request to vehicles whose delivery schedule in the near future is not filled, and to improve the loading ratio.

  In the present embodiment, the package type check process is performed with reference to the transaction ratio information. For this reason, while efficiently assigning a delivery request between mutually loadable luggage, a delivery request between mutually prohibited luggage is not assigned. Loading can be suppressed.

  Note that, in the vehicle allocation matching processing of the present embodiment, an example of processing in which both the operation prediction area data and the operation prediction loading rate are applied has been described, but the present invention is not limited to this. That is, by performing the vehicle allocation matching process using at least the predicted operation loading ratio, the effect of the transportation management system of the present embodiment described above can be obtained.

  Further, in the vehicle assignment matching processing shown in FIGS. 15 and 16, one day's delivery work time (workable time frame) of the delivery staff can be considered. In this case, it is possible to configure so as not to extract as a reserved vehicle when the time exceeds the workable time frame. A workable time frame (for example, from 8:00 am to 6:00 pm) is defined in advance for each delivery member and stored in the storage device 330, and the dispatching matching unit 326 assigns the assigned vehicle to the assigned vehicle determined to have the matching process. On the other hand, a workable time frame determination process is performed. For example, if the desired delivery time of the delivery request is 9:00 pm, the allocated vehicle is excluded without being extracted as a matching vehicle, and the working hours of the delivery staff can be optimized.

  Although the embodiment of the present invention has been described above, the delivery terminal 100, the business operator terminal 200, the shipping terminal 400, and the receiving terminal 500 are provided with a portable information terminal or a PDA (Personal Digital Assistant) having a communication function. And information processing terminal devices having a communication function and an arithmetic function such as a personal computer. Further, a browser function for controlling display of screens and information can be provided.

  The management device 300 is, for example, a server device, and has a hardware configuration other than those described above, such as a CPU that controls the entire device (each unit), a memory (main storage device), a mouse, a keyboard, a touch panel, a scanner, and the like. An operation input unit, a printer, an output unit such as a speaker, an auxiliary storage device (such as a hard disk), and the like can be provided (or connected). The same applies to the hardware configuration of the delivery staff terminal 100, the business operator terminal 200, the shipping terminal 400, and the receiving terminal 500.

  Further, each function of the present invention can be realized by a program, and a computer program prepared in advance to realize each function is stored in the auxiliary storage device, and a control unit such as a CPU is stored in the auxiliary storage device. The program is read into the main storage device, and the control unit executes the program read into the main storage device, so that the computer device can operate the functions of the respective units of the management device 300 and the delivery terminal 100. On the other hand, each function of the present invention can be configured by a separate control device, and a plurality of control devices can be connected directly or via a network to configure, for example, the management device 300.

  Further, the program can be provided to a computer in a state where the program is recorded on a computer-readable recording medium. Computer-readable recording media include optical disks such as CD-ROMs, phase-change optical disks such as DVD-ROMs, magneto-optical disks such as MO (Magnet Optical) and MD (Mini Disk), and floppy (registered trademark) disks. Examples include a magnetic disk such as a removable hard disk, a compact flash (registered trademark), a smart media, an SD memory card, and a memory card such as a memory stick. Further, a hardware device such as an integrated circuit (such as an IC chip) specially designed and configured for the purpose of the present invention is also included as a recording medium.

100 Delivery terminal 110 Communication unit 120 Control unit (CPU)
121 Operation status control unit 121A GPS control unit 121B Loading information control unit 130 Storage unit 140 Display unit 150 Operation unit 160 Imaging unit 200 Business terminal 300 Transport management device 310 Communication device 320 Control device 321 Vehicle registration unit 322 Operation information collection unit 323 Operation information providing unit 324 Operation prediction unit 325 Delivery request reception unit 326 Vehicle allocation matching unit 327 Estimation / order control unit 328 Operation schedule plan control unit 329 Transaction result unit 330 Storage device 400 Shipper terminal 500 Shipper terminal

Claims (9)

A transportation management system for a delivery vehicle that performs collection and delivery of requested packages,
A first storage unit that stores operation result data including a loading ratio for each delivery vehicle based on a delivery history accumulated daily;
An operation prediction unit that generates a predicted loading rate of each delivery vehicle from the present time to each future day based on the operation result data,
A second storage unit for storing, for each delivery vehicle, transaction results for each shipper based on the delivery history;
A dispatcher matching unit that performs a dispatching matching process for assembling the delivery request information that is requested from the shipper and has at least a future date after tomorrow and a future date as a collection and delivery date in a future operation schedule of the delivery vehicle,
The vehicle allocation matching unit,
A first candidate vehicle having a transaction record with the shipper of the delivery request is extracted based on the transaction record by shipper, and the volume of the requested package of the delivery request is predicted using the predicted loading rate of the first candidate vehicle. A first matching process for extracting a vehicle having a loading ratio or less;
If no vehicle is extracted in the first matching process, a second candidate vehicle having no transaction record with the shipper of the delivery request is extracted, and the delivery is performed using the free loading rate excluding the predicted loading rate of the second candidate vehicle. A second matching process for extracting a vehicle in which the volume of the requested luggage is equal to or less than the free loading ratio. The vehicle allocation matching unit,
It is determined whether or not the collection / delivery date of the delivery request is future than a predetermined number of days from the present time, and when it is determined that it is future than the predetermined number of days, the first matching process and the second matching process are performed. When it is determined that it is not the future than the predetermined number of days, a vehicle for which the volume of the requested luggage of the delivery request is equal to or less than the entire empty loading rate including the predicted loading rate and the free loading rate of the delivery vehicle is extracted. The transportation management system according to claim 1, wherein three matching processes are performed. The transaction results by shipper include the baggage attribute of the requested baggage,
In the baggage attribute, whether or not mutual loading is possible between the attributes of the requested baggage is defined in advance,
The vehicle allocation matching unit,
Based on the transaction results by shipper, a vehicle that has delivered the package of the package attribute included in the delivery request, or the package attribute included in the transaction result by shipper and the package attribute included in the requested package mutually The transportation management system according to claim 1, wherein the matching process is performed on a vehicle that can be loaded.   It further includes an operation information collection unit that receives operation status data including a loading ratio of a delivery vehicle that is transmitted from the delivery terminal and that is input by the delivery person, and collects the operation status data for each delivery vehicle. The transportation management system according to any one of claims 1 to 3, wherein: The delivery terminal has a GPS function,
The operation information collection unit receives the position information of the delivery vehicle transmitted from the delivery terminal, and for each delivery vehicle, collects the operation status data including the position information,
The operation prediction unit generates operation prediction area data of each delivery vehicle based on the operation status data,
The vehicle allocation matching unit,
The transportation according to claim 4, wherein when a plurality of vehicles are extracted in each of the matching processes, a vehicle closest to a pickup location included in the delivery request is extracted based on the operation prediction area data. Management system.   An operation schedule plan control unit that generates operation schedule plan data incorporating a delivery request in the operation schedule of the delivery vehicle extracted by each of the matching processes, and transmits the generated operation schedule plan data to the operator terminal of the transport company to which the delivery vehicle belongs. The transportation management system according to any one of claims 1 to 5, further comprising: A delivery request receiving unit for receiving a delivery request transmitted from the shipper's shipper terminal;
A quotation / order control unit that generates fare estimate data for the received delivery request based on the fare data set in advance for the delivery vehicle and transmits the generated fare estimate data to the shipper terminal,
The operation schedule plan control unit generates operation schedule plan data incorporating the delivery request after the order of the delivery request is confirmed with the shipper based on the fare estimation data, and transmits the generated data to the business operator terminal. The transportation management system according to claim 6, wherein: A transportation management device for a delivery vehicle that performs collection and delivery of requested packages,
A first storage unit that stores operation result data including a loading ratio for each delivery vehicle based on a delivery history accumulated daily;
An operation prediction unit that generates a predicted loading rate of each delivery vehicle from the present time to each future day based on the operation result data,
A second storage unit for storing, for each delivery vehicle, transaction results for each shipper based on the delivery history;
A delivery matching unit that performs a delivery matching process for assembling delivery request information requested by the shipper and having at least a future date after tomorrow as a collection / delivery date from the present time into a future operation schedule of the delivery vehicle,
The vehicle allocation matching unit,
A first candidate vehicle having a transaction record with the shipper of the delivery request is extracted based on the transaction record by shipper, and the volume of the requested package of the delivery request is predicted using the predicted loading rate of the first candidate vehicle. A first matching process for extracting a vehicle having a loading ratio or less;
If no vehicle is extracted in the first matching process, a second candidate vehicle having no transaction record with the shipper of the delivery request is extracted, and the delivery is performed using the free loading rate excluding the predicted loading rate of the second candidate vehicle. A second matching process for extracting a vehicle in which the requested luggage volume is equal to or less than the free loading ratio. A program for causing a computer to execute a transportation management process of a delivery vehicle that performs collection and delivery of requested packages,
A first function of storing operation result data including a loading rate for each delivery vehicle based on a delivery history accumulated daily;
A second function of generating a predicted loading rate of each delivery vehicle from the present time to each future day based on the operation result data;
A third function of storing, for each delivery vehicle, transaction results for each shipper based on the delivery history;
And a fourth function of performing a dispatch matching process for incorporating delivery request information requested by the shipper and having at least a future date after tomorrow as a collection / delivery date into a future operation schedule of the delivery vehicle,
The fourth function is:
A first candidate vehicle having a transaction record with the shipper of the delivery request is extracted based on the transaction record by shipper, and the volume of the requested package of the delivery request is predicted using the predicted loading rate of the first candidate vehicle. A first matching process for extracting a vehicle having a loading ratio or less;
If no vehicle is extracted in the first matching process, a second candidate vehicle having no transaction record with the shipper of the delivery request is extracted, and the delivery is performed using the free loading rate excluding the predicted loading rate of the second candidate vehicle. A second matching process for extracting a vehicle in which the volume of the requested baggage is equal to or less than the free loading ratio.