Passenger service planning and dispatch system
Dispatcher assigns transport and drivers for specific day trips. When the trip is disrupted, it can combine an alternate option and see the impact on other departures.
The actual departure, transport change or missed stoppage has no reliable connection to the particular day's trip. The plan is displayed as an ongoing service, although the operations team and passenger need other information.
How the solution works
- A valid voyage is linked to the appointment of a specific day's transport and driver.
- The actual transport movement and changes approved by the dispatcher update the status of the trip.
- The disorder receives the affected scope and responsible dispatcher action; a known fact is passed on to the informant.
- The substitution is checked against real capacity, fitness and further commitments.
- The approved change reaches the executors and the passenger information process, preserving the actual result.
Key challenges
- The schedule does not reflect the actual course of the voyage
- Trip disruptions are addressed too late
Solution capabilities
Day trip and appointment
The timetable entry is linked to the actual transport and driver; the reassignment maintains a continuous sequence of jobs.
Actual execution
The start, stops and completion have a reliable source. The missing data connection is not interpreted as the trip that occurred or its cancellation.
Disruption management
Affected voyages, responsible personnel and scheduled actions are indicated at the incident. circumstances not yet confirmed are clearly noted.
Alternate plan check
Assessing available transport, driver, required capacity and availability, and impact on another task.
Communicating changes
The enforcer receives the approved plan, and the outreach function - a proper change of voyage and stops and its validity.
Business context
- The schedule does not reflect the actual course of the voyage
- The actual departure, transport change or missed stoppage has no reliable connection to the particular day's trip. The plan is displayed as an ongoing service, although the operations team and passenger need other information.
- Trip disruptions are addressed too late
- Known disruption is not transmitted with affected journeys and responsible reaction; alternate transport and driver options are adjusted separately. Alignment of the decision is prolonged, and changing one trip may disrupt further transport work.
- Change of voyage coordinated as part of passenger journey
- The lack of a vehicle or driver can affect multiple departures. Visible dependencies help the dispatcher check the alternate plan and pass on the confirmed information. The result that matters to the passenger is a clearer actual travel path and a timely explained change.
Core features
- Day trip and appointment
- Actual execution
- Disruption management
- Alternate plan check
- Communicating changes
Key integrations
- Schedule or charter plan
- Valid volume of the voyage, stops and terms of service.
- Driver and Property Readiness Sources
- Trusted appointments, limitations and genuine eligibility of replacement capacity.
- Telematics and the driver's work channel
- Actual events, their relevance and acceptance of the approved task.
- Passenger information function
- A reliable fact of the disorder, a later solution and the cancellation of an expired replacement.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Time for coordination of the disorder solution
6–25%Decreasing
This illustrative scenario assumes that 20-50% of waiting caused by missing information or unclear responsibility can be addressed. That share is assumed to fall by 30-50%. Company data is needed to verify both the addressable share and the resulting change.
The time between the receipt of a reliable malfunction and the reasonable plan and the reception of the executor is measured.
Number of changes to the designation with an underestimated follow-up
12–42%Decreasing
This illustrative scenario assumes that 30-60% of errors can be addressed through the data and rule checks described. That share is assumed to fall by 40-70%. Company data is needed to verify both the addressable share and the resulting change.
Estimates of the changes to the designation that had to be corrected due to the pre-decision known further trip conflict. The extent of the affected voyages is described separately and not added to the number of changes.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- Transport has been modified, but real-life data is still available from the previously designated unit.
- An alternate decision is made without evaluating which other journeys were to be carried out by that transport and driver.
Implementation requirements
For dispatching, the links between voyages, vehicles and the works scheduled after them are compatible. Actual starts, non-execution stops and changes in appropriate capacity must reach the responsible participants; the scope of the network organizer is limited by the decisions it manages.
Further development options
- Developing alternatives to recurrent disorders under verified capacity constraints
- Combining actions of multiple units to change trip execution