How to better manage routes, timetables, journeys, tickets, disruptions and passenger information
Digital maturity
medium
Skaitmenizacijos potencialas
79/100
Biggest challenge
The timetable does not reflect actual journey progress
Biggest opportunity
Reliable passenger journey in real time
The greatest result is created by a reliable passenger journey from ticket to actual arrival, not by a separate app or display board.
How passenger transport operates
The business area covers urban, suburban, intercity, international and chartered passenger transport. Service quality is determined by the route network, timetable, transport accessibility, ticketing, punctuality and the ability to manage disruptions.
Service runs on schedule
Even a minor delay can affect connections and passenger plans.
Capacity is limited
Vehicles and drivers cannot be rapidly increased through software alone.
Many public information channels
The same change must reach the app, website, display boards and customer service simultaneously.
Tariffs and concessions are complex
Ticket rules may depend on zone, passenger group, time and mode of transport.
Market and Technology Context
Single journey planning and payment platforms, account-based tickets, contactless payment and real-time data are changing passenger expectations. Practical value is created by reliable management of planned and actual journey data.
Real-Time Information ExpectationPassengers expect to see the actual vehicle location, estimated arrival time and impact of disruptions.
More Unified Ticketing ModelsCities and operators seek simpler settlement between zones and transport modes.
Labour and Transport Cost PressureMore accurate planning of schedules, transport and drivers is becoming more important.
Accessibility RequirementsPassengers need reliable information on low-floor transport, stops and assistance.
Typical activity chain
01
Route and timetable planning
Routes, journeys, stops, times and required capacity are planned.
02
Transport and driver assignment
Vehicles and drivers are assigned to journeys, restrictions are checked.
03
Ticketing and passenger service
Tickets are sold and validated, concessions are managed, and passenger accounts are maintained.
04
Actual journey execution
Location, arrivals, departures, occupancy and deviations are recorded.
05
Disruption management and communication
A contingency plan is created and relevant information is communicated to passengers.
06
Performance analysis
Punctuality, journey completion, demand, costs and passenger experience are evaluated.
Digital Maturity Model
0
Timetables and passenger information managed manually
Journey progress is checked by phone, tickets and changes are recorded separately, and passenger information depends on staff actions.
1
Separate timetable, ticketing and vehicle location systems
Core solutions are in use, but actual journey status and passenger channels are updated separately.
2
Digitalised channels without unified journey status
Ticketing, journey planning and real-time information channels are operational, but disruption management and data quality are inconsistent.
3
Integrated journey and passenger information chain Typical current situation
Planned timetable, actual journey status, disruption and passenger notifications linked across key routes.
4
Real-time network management Siektina
Disruptions, transfers, transport assignment and passenger information adjusted according to actual events and demand.
5
Predictive and adaptive transport network
Demand and disruption models enable advance adjustment of capacity, timetables and passenger communication based on clear control rules.
Key finding
The biggest gap arises between the planned timetable and actual trip progress. When vehicle location, disruption and passenger notifications are managed separately, information is delayed.
The ticketing system, trip management and passenger information channels must use the same route, trip, stop and disruption data.
It is worth first selecting one route or transport mode and connecting actual trip status, disruption management and passenger information.
Related topics
Passenger information systemTicketing and fare managementJourney and disruption management
Problemos
Most common digitalisation issues
The most significant gaps arise between the planned timetable, actual journey progress, ticketing and passenger communication.
The timetable does not reflect actual journey progress
Critical
Planned and actual journeys, vehicle location and stop statuses are updated in different systems.
Consequences
Passengers receive inaccurate information, whilst dispatchers are slow to respond to deviations.
Tickets, tariffs and concessions are managed in a fragmented manner
Critical
Different channels, operators or zones use separate fare, account and settlement rules.
Consequences
The journey becomes complicated for the passenger, whilst the operator struggles to manage a unified view of sales and revenue.
Disruption management begins too late
Critical
Journey cancellations, delays, replacement transport and passenger communication are often coordinated only after the disruption has already occurred.
Consequences
Dispatchers have less time for contingency planning, whilst passengers receive information about journey changes too late.
Passenger communication is delayed or inconsistent across channels
Critical
Changes do not always reach the app, website, stop displays and customer service simultaneously.
Consequences
Passengers cannot replan in time and lose confidence in the service.
Capacity is planned using overly generalised demand data
High
Ticketing, validation, seasonality, events and actual passenger flow data are used separately.
Consequences
Some journeys have insufficient transport, whilst others have unused capacity.
Accessibility information is insufficiently reliable for passengers
Medium
Data on accessible vehicles, lifts, station conditions and assistance are not consistently updated.
Consequences
Passengers with mobility difficulties cannot reliably plan their journey.
Opportunities
Greatest digitalisation opportunities
Single route real-time information scenarioVery high impactConnect planned timetable, actual vehicle location, disruption registration, contingency plan and passenger notifications across all main channels on a single route.More reliable journey
Account-based ticketing and fare systemVery high impactManage tickets, zones, concessions, journey history and payment in a single account.Simpler ticketing
Real-time trip and disruption managementVery high impactShow the dispatcher actual trips, deviations, replacements and passenger communication actions in one place.Fewer cancellations
Route and capacity planning based on actual demandHigh impactUse ticket, validation, passenger flow and event data to select timetables and transport type.Better capacity
Passenger self-serviceHigh impactEnable trip planning, ticket purchase, alert reception, request or complaint submission and status visibility.Less service staff workload
Biggest opportunity
Reliable passenger journey in real time
Connect the timetable, actual vehicle location, ticket, interchanges, disruptions and passenger information.
Greater punctuality
Fewer complaints and information enquiries
Greater ticket availability
Faster disruption management
Expected impact on operations and financial performance
More reliable serviceMore accurate real-time information and faster disruption management reduce cancellations and passenger dissatisfaction.
Greater ticket availabilityUnified fares and channels make ticket purchase and use easier.
Better transport capacity utilisationDemand data helps allocate vehicles and schedules more accurately.
Reduced service workloadSelf-service and proactive notifications reduce the number of calls and enquiries.
More accurate contractual KPI monitoringReliable actual journey data enables punctuality, fulfilment and compensation to be substantiated.
Sprendimai
How to solve these problems
Solution directions linked to specific business area problems they address.
Problema
The timetable does not reflect the actual progress of the trip
→
Sprendimo kryptis
Passenger information and journey planning platform
Connects timetables, real-time status, interchanges, disruptions, notifications and accessibility information.
Problema
Passenger information is delayed or differs between channels
→
Sprendimo kryptis
Passenger information and journey planning platform
Connects timetables, real-time status, interchanges, disruptions, notifications and accessibility information.
Problema
Accessibility information is insufficiently reliable for passengers
Passengers with mobility difficulties cannot reliably plan their journey.
→
Sprendimo kryptis
Passenger information and journey planning platform
Connects timetables, real-time status, interchanges, disruptions, notifications and accessibility information.
Problema
Tickets, fares and concessions are managed in a fragmented way
Connects vehicles, drivers, services, actual statuses, disruptions and contingency plans.
Passenger flow and service planning analytics
Analyses ticketing, validation, actual service and passenger flow data to improve routes, timetables and capacity.
When the investment is justified
Investment justified
Many complaints about inaccurate information
Disruptions are managed by phone and messages
Ticket or validation data are not used for planning
Different channels show different statuses
Reikia atsargumo
There are no unified route and trip identifiers
It is unclear which system is the source of actual trip status
The first phase covers the entire network
There are no punctuality and information quality KPIs
Ideal first version
One route or transport type that integrates timetable, real-time vehicle location, disruption recording, passenger notifications and the core ticketing scenario.
Actual trip status
Shows vehicle location, stops and deviations.
Disruption workflow
Creates responsible staff actions and a contingency plan.
Passenger notifications
Updates key information channels in one action.
Core ticketing scenario
Enables ticket purchase or validation in the selected channel.
Punctuality KPIs
Compares scheduled and actual trips.
Kam pirmiausiaDispatchers · Drivers · Passengers · Customer service staff
What not to include in the first versionFull route network · Consolidation of all operator tariffs · Fully autonomous timetable optimisation
Investment priorities
Connect the actual progress of a single route and passenger informationIntegrate the planned timetable, actual status, disruption actions and passenger notifications within a single route.
Standardise route, trip and stop dataDefine common identifiers for route, trip, stop, vehicle, disruption and accessibility.
Organise the ticket and fare modelStandardise the rules for fares, zones, concessions, ticket entitlements and channels.
Use demand data for planningCompare ticket, counting and actual trip data by time, route and stop.
Only then expand forecasts and AIDeploy forecasts and optimisation only when there is a reliable history of actual trips, disruptions and passenger flows.
Key implementation conditions
Real-time data must have a clear status
The passenger must be able to see when information was updated and whether it is planned, actual or forecast.
Critical functions must operate during connectivity outages
Ticket validation and driver operations cannot completely stop due to central system or connectivity failure.
Fare rules must be auditable
Concessions, zones and price changes must have validity periods and confirmation history.
Passenger information must be consistent across all channels
The same disruption cannot have different values in the app, information board and customer service system.
Personal data must be separated from operational data
Ticket and passenger account information must only be used for clearly defined purposes.
Recommended implementation sequence
01
Single route and information process diagnostics
Select one route and identify where planned information, actual status and passenger notifications diverge.
Scheduled and actual journey map
Data source assessment
Disruption scenarios
Initial punctuality KPIs
02
Common data model for route, trip and stop
Define the relationships between planned and actual trip, vehicle, stop, disruption and passenger notification.
Identifiers and statuses
Data quality rules
Accessibility attributes
Integration contracts
03
Real-time trip and disruption management
Integrate actual trip progress, disruption resolution and passenger information in one route.
Dispatcher workflow
Actual statuses
Contingency plan tasks
Channel publishing
04
Pilot passenger information and ticket link
Validate actual usage, information accuracy and impact on passenger enquiries and punctuality perception.
Passenger channel pilot
Ticket scenario
Fallback information mode
KPI comparison
05
Network expansion and demand analytics
Scale the validated model across the network and use actual flow data to improve schedules and capacity.
Additional routes
Interchange information
Demand Forecast
Capacity Recommendations
Recommended KPIs
Share of journeys completed on time%
Measure punctuality according to a clearly defined tolerance.
Share of cancelled journeys%
Assess operational stability and disruption management.
Real-time information coverage% journeys
Measure how many journeys have reliable actual data.
Predicted arrival time forecast errormin.
Assess the accuracy of arrival time displayed to passengers.
Share of digitally sold tickets%
Monitor self-service and ticketing channel usage.
Number of information enquiriesenquiries / period
Assess the impact of proactive information on service load.
Accessibility information completeness% journeys
Assess how many journeys have reliable data on vehicle and station accessibility.
Key risks
Inaccurate real-time information displayedGPS or trip status is delayed, but presented to passengers as reliable.Kaip suvaldyti Display update time, data quality and have a clear fallback notification mode.
The first version covers the entire transport networkAttempting to change all routes, tariffs and channels at once.Kaip suvaldyti Start with one route or transport mode and an end-to-end scenario.
Replacing the ticketing system disrupts revenueImproperly tested tariffs or validation directly affects passengers and accounting.Kaip suvaldyti Apply parallel operation, clear tariff testing and a rollback plan.
Disruption information does not reach all channelsSystems are integrated inconsistently or use different statuses.Kaip suvaldyti Have a single source of disruption and automated publishing across channels.
Demand forecasting ignores atypical eventsThe model does not account for events, roadworks or changed passenger behaviour.Kaip suvaldyti Allow human correction, event calendars and continuously measure forecast error.
Inovacijos
Advanced digital innovations
Advanced solutions only make sense with reliable journey, ticketing, passenger flow and disruption data.
Market expansion2
Passenger flow forecasting
Relevant
Models predict demand based on time, route, events and historical flows.
How it is applied For timetable and transport capacity recommendations.
What value can be created
Better capacity utilisation
Fewer overcrowded journeys
What is needed for this to work
Ticket or validation data
Reliable actual journeys
Medium-termCommercial solutions are available
More accurate arrival time forecasting
Relevant
Models assess actual location, traffic, stops and historical deviations.
How it is applied For passenger information and transfer risk.
What value can be created
More accurate promises
What is needed for this to work
GPS data
Stop and journey identifiers
Medium-termCommercial solutions are available
Early stage2
AI assistance for disruption management
Relevant
The system suggests alternative journeys, transport changes and passenger information actions.
How it is applied To assist dispatcher decision-making.
What value can be created
Faster response
Fewer cancellations
What is needed for this to work
Clear operating rules
Disruption history
Medium-termCommercial solutions are available
Route network scenario modelling
Relevant
Virtual modelling of route, timetable, transfer and passenger flow changes.
How it is applied For network changes and investment appraisal.
What value can be created
More accurate planning decisions
What is needed for this to work
Route model
Demand data
Long-term perspectiveCommercial solutions are available
D.U.K.
Frequently asked questions
Where to start with passenger transport digitalisation?
Select one route or mode of transport and connect the scheduled timetable, real-time trip status, disruption management and passenger communications.
Does the ticketing system need to be changed first?
Not necessarily. If the biggest problem is inaccurate real-time information or disruption management, the first phase can start with operations and passenger communications integration.
What should the first version of the project be?
One clear scenario: actual trip status, deviation registration, passenger alert and one ticketing or journey planning channel.
How to manage disruptions in real time?
A disruption must simultaneously trigger dispatcher actions, contingency plan tasks and passenger notifications across all key channels.
How to ensure accessibility information?
Link accessibility attributes to the specific vehicle, station and their real-time status, rather than keeping them in a general description.
How to assess project return on investment?
Measure punctuality, cancelled trips, number of information enquiries, cost per ticket sold, passenger satisfaction and capacity utilisation.
Next step
Assess where reliability is lost in the passenger journey
Review the processes for routes, trips, ticketing, disruptions and passenger communications and help select one first phase where benefits can be measured.