Vehicle dispatch support system

Abstract

We provide a dispatch support system that can appropriately handle situations where registered vehicles are delayed in arriving. [Solution] In the present invention, when the communication device 2 receives a delay notification from a registered vehicle that is executing a dispatch plan, the controller 3 determines whether there are other dispatch plans affected by the delay. If it determines that there are other affected plans, it cancels the affected plans and performs a recalculation process to change the reservation request corresponding to the affected plans into a new reservation request, which is a re-reservation request. The recalculation process includes a process to change the estimated arrival time within an acceptable range of arrival time for one or more waypoints in the other dispatch plans, as a simulation for assigning the re-reservation request.

Description

[[Technical Field]]

[0001] The present invention relates to a vehicle dispatch support system. [[Background Art]]

[0002] Recently, in response to requests for human transportation, luggage delivery, and the like, computer systems that create vehicle dispatch plans for registered vehicles have been developed. For example, Japanese Patent No. 7511080 discloses a system that creates a vehicle dispatch plan capable of efficiently fulfilling requests in consideration of the spare time of vehicles. [[Prior Art Documents]] [[Patent Documents]]

[0003] [[Patent Document 1]] Japanese Patent No. 7511080 [[Summary of the Invention]] [[Problem to be Solved by the Invention]]

[0004] However, the above system has room for improvement in terms of handling situations where the actual arrival of a registered vehicle is delayed or is likely to be delayed with respect to the plan. An object of the present invention is to provide a vehicle dispatch support system that can cope with cases where the arrival of a registered vehicle is delayed. [[Means for Solving the Problem]]

[0005] The dispatch support system of the present invention comprises a communication device that receives reservation requests including information on a plurality of intermediate locations where work will occur and a desired time of arrival at at least one of the intermediate locations, and a controller that manages a plurality of registered vehicles and sets a dispatch plan for the registered vehicles based on the reservation requests received by the communication device. One dispatch plan is set for one of the reservation requests. Each of the intermediate locations in the dispatch plan is set with an estimated time of arrival at the intermediate location and an allowable arrival time range, which is between the earliest allowable time and the latest allowable time, as the period during which arrival at the intermediate location is permitted. When the communication device receives a delay notification from a registered vehicle executing the dispatch plan, indicating that the estimated time of arrival or the actual time of arrival at the intermediate location is later than the latest allowable time for that intermediate location, and which includes information on the estimated time of arrival or the time of arrival, the controller determines whether there are any affected plans, which are other dispatch plans affected by the delay of the dispatch plan corresponding to the delay notification. If the controller determines that there is an affected plan, it cancels the affected plan and performs a recalculation process to recalculate the reservation request corresponding to the affected plan as a new reservation request, which is a re-reservation request. The recalculation process includes a process to change the estimated arrival time within the range of the allowable arrival time range for one or more of the waypoints in other vehicle dispatch plans, as a simulation for assigning the re-reservation request. [Effects of the Invention]

[0006] According to the present invention, if a delay is estimated to occur in the dispatch schedule or if a delay actually occurs, the affected dispatch schedule is canceled, and a recalculation process is performed as a new reservation request (re-reservation request). In the recalculation process, the estimated arrival time is adjusted within the range of acceptable arrival time, so there is a higher probability that a re-reservation request will be assigned within the acceptable range. The present invention also makes it possible to handle cases where the arrival of registered vehicles is delayed. [Brief explanation of the drawing]

[0007] [Figure 1]This is a diagram showing the configuration of the dispatch support system of this embodiment. [Figure 2] This is a flowchart illustrating the recalculation process flow of this embodiment. [Figure 3] This is a conceptual diagram illustrating the vehicle dispatch plan of this embodiment. [Figure 4] This is a conceptual diagram illustrating the recalculation process in this embodiment. [Modes for carrying out the invention]

[0008] Hereinafter, a dispatch support system 1, which is one embodiment of the present invention, will be described in detail with reference to the figures. It should be noted that, in addition to the embodiments described below, the present invention can be implemented in various forms with various modifications and improvements based on the knowledge of those skilled in the art.

[0009] As shown in Figure 1, the dispatch support system 1 comprises a communication device 2, a controller 3, a user terminal 4, and a vehicle terminal 5. The communication device 2 is a wireless or wired communication device that can connect to a network such as the Internet. The communication device 2 is responsible for the communication function of the controller 3, transmits received information to the controller 3, and transmits information upon transmission instructions from the controller 3. The communication device 2 is configured to receive reservation requests from the user terminal 4.

[0010] There are two types of reservation requests: passenger reservation requests for transporting people and delivery reservation requests for transporting goods. A passenger reservation request includes information such as the passenger's boarding and alighting locations and their desired (or feasible) times. A delivery reservation request includes information such as the package pickup and delivery locations and their desired (or feasible) times. Thus, a reservation request includes information about the location and time of execution for a pair of operations (boarding and alighting, pickup and delivery). The execution time information included in a reservation request may only include one of the times. In this case, the controller 3 sets the other time.

[0011] The user can send their desired reservation request (ride reservation request or delivery reservation request) to the communication device 2 from their user terminal 4. The user terminal 4 is a communication terminal that can communicate with the communication device 2 and display information, such as a smartphone or tablet. The user terminal 4 can acquire its own location information, for example, using a GPS function, and send it to the communication device 2. The user can select their desired time from a range of time slots presented on the user terminal 4.

[0012] Controller 3 consists of a computer with one or more processors and one or more memories. The communication device 2 may be located inside Controller 3. Controller 3 determines the dispatch plan for registered vehicles based on reservation requests received by the communication device 2. Controller 3 can also be considered a server. Controller 3 periodically exchanges information with user terminals 4 and vehicle terminals 5.

[0013] As described above, a ride reservation request includes information on the boarding location, alighting location, desired boarding time, and desired alighting time. The boarding location may be the location information of the user terminal 4. A delivery reservation request includes information on the place (e.g., store) where the package (e.g., goods) will be picked up, the delivery destination, a specified pick-up time, and a desired pick-up time. For example, the information on the pick-up time of the package displayed on the user terminal 4 is updated based on rules set in the controller 3 or information obtained from stores, etc. Multiple vehicles are registered as registered vehicles in the controller 3.

[0014] Vehicle terminal 5 is a communication terminal capable of communicating with controller 3 and displaying information, and is, for example, a smartphone, tablet, or a device mounted on a vehicle. Vehicle terminal 5 receives the dispatch plan for the corresponding registered vehicle from controller 3 and displays the plan details on its screen. The driver of the registered vehicle obtains the dispatch plan information from vehicle terminal 5. Controller 3 stores the locations where work (such as getting on and off the vehicle, handing over cargo, etc.) occurs as "intermediate points (or work occurrence locations)".

[0015] The screen of the vehicle terminal 5 displays, for example, waypoints, desired arrival time at each waypoint (and / or acceptable arrival time range as described later), details of work at each waypoint (number of passengers, number of passengers alighting, user information, type and number of packages to be received, type and number of packages to be handed over, etc.), and recommended driving route. The vehicle terminal 5 can acquire its own location information, for example, through its own GPS function or by sharing information with registered vehicles, and transmit it to the communication device 2. The vehicle terminal 5 transmits its own location information (corresponding to the location information of the registered vehicle), the remaining driving range shared with the registered vehicle, and the charging status (if the registered vehicle is an electric vehicle) to the communication device 2.

[0016] (Recalculation process) In the dispatch support system 1, one dispatch plan is created for each reservation request. The dispatch plan for a single ride reservation request includes at least the estimated arrival time at the pick-up location and the estimated arrival time at the drop-off location (as described later, an acceptable time range is set for the estimated times). The controller 3 sets up multiple dispatch plans for multiple reservation requests, so that each reservation request corresponds to one dispatch plan.

[0017] The dispatch plan includes a "tolerable arrival time range" for each stop along the route. For example, if the desired pick-up time in a ride reservation request is 3:00 PM, the dispatch plan will set the estimated arrival time at the pick-up location to 3:00 PM, and the tolerable arrival time range will be set to, for example, 2:50 PM to 3:30 PM, based on the desired pick-up time and the actual vehicle situation (feasibility). In this case, for example, user terminal 4 and vehicle terminal 5 will display an estimated arrival time of 3:00 PM and a tolerable arrival time range of 2:50 PM to 3:30 PM. Thus, each stop along the route in the dispatch plan has an estimated arrival time and a tolerable arrival time range, which is the period during which arrival is permitted. The estimated arrival time is set within the range of the tolerable arrival time range. Hereinafter, the earliest time within the tolerable arrival time range will be referred to as the "earliest tolerable time," and the latest time will be referred to as the "latest tolerable time."

[0018] When the communication device 2 receives a delay notification indicating that the estimated arrival time or actual arrival time at a waypoint of the currently traveling registered vehicle is later than the allowable latest time, the controller 3 executes recalculation processing. The delay notification is transmitted from, for example, the vehicle terminal 5. The vehicle terminal 5 periodically estimates the time when the registered vehicle will arrive at the next waypoint, or acquires information on the estimated arrival time through information sharing with the registered vehicle.

[0019] When the vehicle terminal 5 determines that the estimated arrival time at the waypoint will be later than the allowable latest time for some reason such as traffic congestion or an accident, the vehicle terminal 5 transmits a delay notification including the estimated arrival time to the communication device 2. The vehicle terminal 5 may periodically transmit the estimated arrival time at the waypoint it is currently heading to. The vehicle terminal 5 acquires information on the estimated arrival time through information sharing with the vehicle's navigation system or from a map application or the like in the vehicle terminal 5. For example, the vehicle terminal 5 monitors the estimated arrival time, and transmits a delay notification when the estimated arrival time is later than the allowable latest time by a predetermined time or more (predetermined time ≧ 0). When the estimated arrival time is updated, the vehicle terminal 5 transmits the information to the communication device 2. Note that when the controller 3 determines whether there is a delay based on the estimated arrival time, it can be said that the notification of the estimated arrival time corresponds to the delay notification.

[0020] The transmission timing of the delay notification by the vehicle terminal 5 may be, for example, (1) the timing at which it is determined that the estimated arrival time at the next waypoint or the first waypoint of the next vehicle allocation plan will be delayed by a predetermined time (predetermined time ≧ 0) or more, (2) the timing at which the allowable latest time is exceeded while the vehicle has not arrived at the next waypoint in the currently executed vehicle allocation plan, and / or (3) the timing at which the vehicle actually arrives at the waypoint. In transmission at the timings of (1) and (2), the delay notification includes information on the estimated arrival time, and in transmission at the timing of (3), the delay notification includes information on the actual arrival time. The transmission timing of the delay notification may be all of (1) to (3), or may be a part of them. In this example, the delay notification is transmitted at least at the timing of (1).

[0021] Referring to Fig. 2, the recalculation process will be described. When the controller 3 receives a delay notification from the vehicle terminal 5, it investigates a vehicle dispatch plan affected by the delay (hereinafter also referred to as an "affected target plan") from the set vehicle dispatch plans (S101). The controller 3 acquires various types of information for each registered vehicle through communication with the vehicle terminal 5 of each registered vehicle, for example, information on the achievement status of the vehicle dispatch plan, the cruising range, and the charging status (in the case of an electric vehicle). The controller 3 determines which vehicle dispatch plans will be affected by the delay in consideration of the estimated arrival time of the delayed vehicle, other vehicle dispatch plans, and the status of other registered vehicles.

[0022] For example, as shown in Fig. 3, when a previously executed vehicle dispatch plan a1 and a vehicle dispatch plan a2 scheduled to be executed after the vehicle dispatch plan a1 are set for a registered vehicle A, the controller 3 calculates whether the vehicle dispatch plan a2 can be executed as scheduled (within the allowable time range) due to the delay of the currently executed vehicle dispatch plan a1. For example, when the estimated arrival time of the vehicle dispatch plan a2 at the waypoint 72 is later than the allowable latest time of the waypoint 72 due to the delay of the vehicle dispatch plan a1, the controller 3 determines that the vehicle dispatch plan a2 is an affected target plan. On the other hand, it is determined that the vehicle dispatch plan b1 set for the registered vehicle B, which is a different vehicle from the registered vehicle A, is not affected by the delay of the registered vehicle A. Although the delay of the vehicle dispatch plan a1 cannot be addressed, the recalculation process is executed for the affected target plan a2. The transmission of the delay notification by the vehicle terminal 5 and the determination of whether there is an influence of the delay by the controller 3 may be performed, for example, at the timing when the estimated arrival time of the vehicle dispatch plan a1 at the waypoint 71 becomes later than the allowable latest time of the waypoint 71, or may be performed at the timing when the estimated arrival time of the vehicle dispatch plan a2 at the waypoint 72 becomes later than the allowable latest time of the waypoint 72.

[0023] If there are no affected plans (S102: No), controller 3 terminates the recalculation process. If there is one or more affected plans (S102: Yes), controller 3 cancels (deactivates) the affected plans and returns to the reservation request stage (S103). The affected plans are canceled and return to the reservation request stage, and are subject to calculation in the same way as new reservation requests. Reservation requests corresponding to canceled dispatch plans are referred to as "re-reservation requests".

[0024] One constraint in recalculation is that, in principle, if the work (boarding, receiving) at the first stop in the dispatch plan has been completed, the dispatch plan can only be executed by the registered vehicle that performed that work. For example, if the first dispatch plan involves the first registered vehicle receiving the first and second packages at the first stop and handing over the first package at the second stop, and the second dispatch plan involves handing over the second package at the third stop, then even if the first dispatch plan is delayed, the second dispatch plan must be executed by the first registered vehicle. This constraint, which specifies which registered vehicle is subject to the dispatch plan, is called a "vehicle specification constraint."

[0025] Examples of vehicle-specific constraints include delivery reservation requests that involve work performed in registered vehicles equipped with boxes that have cooling or heating functions (e.g., food pickup), and passenger reservation requests that involve work performed in registered vehicles with boarding / alighting assistance functions or wheelchair-accessible registered vehicles (e.g., passenger boarding). In other words, vehicle-specific constraints apply to dispatch plans where work has already been performed at one of the intermediate stops, or dispatch plans that require vehicles with specific functions, or "dispatch plans where work performed in a specific registered vehicle is essential." The presence or absence of vehicle-specific constraints is considered in the relationship between the recalculated dispatch plan and the re-reservation request. If the content of the re-reservation request is subject to a vehicle-specific constraint, controller 3 performs a recalculation (reallocation, replanning) to realize a dispatch plan using a specific registered vehicle.

[0026] Controller 3 determines the order in which to recalculate (S105) if there are multiple re-reservation requests (S104: Yes). Recalculating re-reservation requests has the property that requests executed earlier are relatively easier to allocate. In other words, earlier requests have relatively more available space (registered vehicles and time) and greater flexibility than later requests. Therefore, Controller 3 is configured to recalculate re-reservation requests that are more difficult to allocate first.

[0027] The difficulty of the allocation can be determined, for example, based on the difference between the current time and the latest possible time for the next transit point in the rebooking request (i.e., the grace period). The smaller the grace period, the higher the difficulty (constraint) of the recalculation, and the earlier the recalculation will be performed. In other words, controller 3 sets the order of recalculations so that the rebooking requests are sorted in descending order of difficulty (so that the most difficult rebooking requests come first).

[0028] Furthermore, Controller 3 determines that a re-reservation request is more difficult if it is subject to a vehicle-specific constraint. In other words, Controller 3 recalculates re-reservation requests with vehicle-specific constraints first. In this example, requests with vehicle-specific constraints are processed first, regardless of the amount of grace time. For example, the order of recalculation, from fastest to slowest, is: "re-reservation request with vehicle-specific constraints and a small grace time," "re-reservation request with vehicle-specific constraints and a large grace time," "re-reservation request without vehicle-specific constraints and a small grace time," and "re-reservation request without vehicle-specific constraints and a large grace time." Controller 3 determines the order of recalculation based on the grace time and the presence or absence of vehicle-specific constraints. Note that if there is only one re-reservation request (S104: No), Controller 3 proceeds to the next step (S106).

[0029] Controller 3 assigns rebooking requests one by one using sequential optimization according to the determined recalculation order (S106). To explain sequential optimization, Controller 3 first calculates whether a rebooking request can be assigned by changing one or more scheduled arrival times within the allowable arrival time range for each stop in each dispatch plan.

[0030] For example, as shown in Figure 4, a dispatch plan a1 is set for registered vehicle A, which involves picking up package Z1 at store 81 (intermediate location) and handing over package Z1 at user's home 82 (intermediate location). The controller 3 moves the scheduled arrival time at store 81 to an earlier date within the allowable arrival time range (pickup period) and moves the scheduled arrival time at user's home 82 to a later date within the allowable arrival time range (delivery period) for the unexecuted dispatch plan a1. This creates leeway in the time required to travel from store 81 to user's home 82. The controller 3 calculates whether a rebooking request is allocated to this leeway. The movement (modification) of the scheduled arrival time is done within the allowable arrival time range and within the limits that the registered vehicle can achieve (especially regarding the movement to an earlier date).

[0031] In the example in Figure 4, the rebooking request specifies that package Z2 be picked up at store 91 and delivered to the user's home 92. Controller 3 considers the allowable arrival time range (pickup period) at store 91, the allowable arrival time range (delivery period) at user's home 92, and the travel time of registered vehicle A to determine whether registered vehicle A can perform the rebooking request within the slack time of dispatch plan a1. Controller 3 similarly simulates the modification of the estimated arrival time for other registered vehicles. Figure 4 shows an example where a rebooking request is assigned to the slack time of dispatch plan a1, resulting in dispatch plan a2.

[0032] Controller 3, in this manner, performs calculations for each registered vehicle, as a simulation, to shift the estimated arrival time at each intermediate stop within the range of acceptable arrival time, thereby generating buffer time. Controller 3 assigns points to registered vehicles that were available for rebooking requests within the buffer time using a predetermined evaluation function. The evaluation function can be set as appropriate, but as an example, it is set so that the shorter the overall mileage and mileage of registered vehicles after assignment, the higher the score. Also, for example, in the evaluation function for the delivery of food that needs to be delivered while still warm, such as bento boxes, the earlier the estimated arrival time at the handover intermediate stop, the higher the score. In the evaluation function of this example, a higher score indicates a higher evaluation.

[0033] If the results of the allocation calculation and evaluation function calculation are, for example, "Registered vehicle A scores 80 points," "Registered vehicle B scores 70 points," and "Registered vehicle C is not assignable and therefore not included in the calculation," then Registered vehicle A is determined to be the vehicle to be allocated to the re-booking request. Controller 3 sets up a dispatch plan corresponding to the re-booking request, for example, by utilizing the available time of Registered vehicle A. Thus, sequential optimization (sequential optimization processing) means that the re-booking request is allocated to the registered vehicle with the highest score in the evaluation function. Controller 3 performs sequential optimization for each re-booking request in the set order. The re-booking request is allocated as a new reservation and becomes a dispatch plan again. The evaluation function may also be used for the dispatch plan for the reservation request (the initial dispatch plan). Also, in the case of Figure 3, if Registered vehicle B can execute the affected plan a2, the re-booking request may be allocated to Registered vehicle B. The re-booking request may be allocated to another registered vehicle without changing the estimated arrival time. Even in such cases, the registered vehicle may be set according to the score of the evaluation function.

[0034] If, as a result of sequential optimization, there are no re-reservation requests for vehicles that cannot be assigned (S107: Yes), the controller 3 transmits the revised plan details to the corresponding vehicle terminal 5 via the communication device 2 (S108). The driver of the registered vehicle can then confirm the revised plan details on the vehicle terminal 5. If there are re-reservation requests for vehicles that cannot be assigned (S107: No), the controller 3 transmits information about the situation to the operator terminal 6 and requests help from the operator (human) (S109). The operator can, for example, assign a new registered vehicle and have the re-reservation requests handled by that newly assigned vehicle.

[0035] The timing of the recalculation may be after a delay notification, when it is determined that there is a dispatch plan affected by the delay (i.e., when it is determined that a recalculation is necessary). Alternatively, the timing of the recalculation may be from the time it is determined that a recalculation is necessary until a predetermined time before the time when the allocation can be realized, depending on the degree of delay (the degree of deviation between the planned and actual schedule). This allows that if a new reservation request with a shorter grace period comes in, that reservation request can be allocated with priority over the re-reservation request. In other words, by holding off on the allocation of re-reservation requests to some extent, the flexibility of allocating later reservation requests can be increased. If a new reservation request comes in while the recalculation is being held, the controller 3 may set the order of recalculation for the new reservation request and the re-reservation request at that time (when the new reservation request is received) and execute the recalculation in the set order. In addition, the registered vehicle may be an autonomous vehicle. In this case, the registered vehicle will be driven autonomously based on the dispatch plan information transmitted to the vehicle terminal 5.

[0036] (Summary of this embodiment) The dispatch support system 1 of this embodiment includes a communication device 2 that receives reservation requests containing information about multiple waypoints where work will occur and desired arrival times at at least one waypoint, and a controller 3 that manages multiple registered vehicles and sets a dispatch plan for registered vehicles based on the reservation requests received by the communication device 2. In the dispatch support system 1, one dispatch plan is set for one reservation request. Each waypoint in the dispatch plan is set with an estimated arrival time to the waypoint and an allowable arrival time range, which is the period between the earliest allowable time and the latest allowable time for arrival at the waypoint.

[0037] When the communication device 2 receives a delay notification from a registered vehicle (vehicle terminal 5) that is executing a dispatch plan, the controller 3 determines whether there are any other dispatch plans affected by the delay of the dispatch plan corresponding to the delay notification. A delay notification is a notification indicating that the estimated or actual arrival time at a transit point is later than the latest allowable arrival time at that transit point, and includes information on the estimated or actual arrival time. If the controller 3 determines that there are affected plans, it cancels the affected plans and performs a recalculation process to change the reservation request corresponding to the affected plans into a new reservation request, which is a re-reservation request. The recalculation process includes a process to change the estimated arrival time within the allowable arrival time range for one or more transit points in other dispatch plans as a simulation for assigning the re-reservation request.

[0038] With this configuration, if a delay is estimated to occur in the dispatch schedule, or if a delay actually occurs, the affected dispatch schedule is canceled, and a recalculation process is performed as a new reservation request (re-reservation request). In the recalculation process, the estimated arrival time is adjusted within the acceptable range of arrival time, increasing the likelihood that a re-reservation request will be assigned within the acceptable range. This configuration can also handle cases where the arrival of registered vehicles is delayed. In other words, this configuration can mitigate the impact of delays.

[0039] In the recalculation process, Controller 3 determines whether it is possible to assign the rebooking request to a registered vehicle by changing the estimated arrival time at the intermediate stops within the acceptable arrival time range for other dispatch plans. If there is only one registered vehicle that can be assigned, Controller 3 assigns the rebooking request to that vehicle. If there are multiple registered vehicles that can be assigned, Controller 3 assigns the rebooking request to the vehicle with the highest evaluation using a predetermined evaluation function. If there are no registered vehicles that can be assigned, Controller 3 sends the rebooking request information to the operator.

[0040] In the recalculation process, if there are multiple re-reservation requests, Controller 3 calculates the difficulty of assignment for each re-reservation request and executes the recalculation process in order of increasing difficulty. For dispatch plans or re-reservation requests that require work with a specific registered vehicle, Controller 3 imposes a vehicle identification constraint that mandates the use of that specific registered vehicle, and executes the recalculation process based on the vehicle identification constraint. As described above, the dispatch support system 1 of this embodiment has a more practical configuration. [Explanation of symbols]

[0041] 1... Dispatch support system, 2... Communication device, 3... Controller, 4... User terminal, 5... Vehicle terminal.

Claims

1. A communication device that receives a reservation request including information about multiple transit points where work will be performed and the desired time of arrival at at least one of the transit points, A controller that manages multiple registered vehicles and sets a dispatch plan for the registered vehicles based on the reservation request received by the communication device, A dispatch support system comprising, wherein one dispatch plan is set for one reservation request, Each of the aforementioned transit points in the dispatch plan is set with an estimated arrival time to the transit point and an allowable arrival time range, which is the period from the earliest allowable time to the latest allowable time for arrival at the transit point. The aforementioned controller, When the communication device receives a delay notification from a registered vehicle that is executing the dispatch plan, indicating that the estimated or actual arrival time at the transit point is later than the latest permitted arrival time at the transit point, and which includes information on the estimated or actual arrival time, Determine whether there are any other affected plans, which are other dispatch plans, that are affected by the delay of the dispatch plan corresponding to the delay notification. If it is determined that there is an affected plan, the affected plan is canceled, and the reservation request corresponding to the affected plan is recalculated as a new reservation request, which is a re-reservation request. The recalculation process includes, as a simulation for assigning the rebooking request, a process to change the estimated arrival time for one or more of the transit points in other vehicle dispatch plans within the range of the allowable arrival time. Vehicle dispatch support system.

2. In the recalculation process, the controller For other vehicle dispatch plans, determine whether it is possible to assign the re-booking request to the registered vehicle by changing the scheduled arrival time at the transit point within the range of the allowable arrival time. If there is only one registered vehicle that can be assigned, the re-reservation request will be assigned to that registered vehicle. If there are multiple registered vehicles that can be assigned, the re-reservation request is assigned to the registered vehicle that has the highest evaluation using a predetermined evaluation function. The vehicle dispatch support system according to claim 1.

3. The aforementioned controller, If no registered vehicle is available for allocation, the operator is sent information regarding the re-booking request. The vehicle dispatch support system according to claim 2.

4. In the recalculation process, the controller If there are multiple re-reservation requests, the difficulty of allocation is calculated for each re-reservation request, and the recalculation process is executed in order of increasing difficulty. The vehicle dispatch support system according to claim 1.

5. The aforementioned controller, For dispatch plans or rebooking requests that require work to be performed by a specific registered vehicle, a vehicle-specific restriction is imposed that compels the use of that specific registered vehicle. Based on the aforementioned vehicle-specific constraints, the recalculation process is performed. A vehicle dispatch support system according to any one of claims 1 to 4.

Images