Dynamic Schedule Delivers Timetable Clarity for Drivers
cn-mobility’s Dynamic Schedule solution transforms fragmented timetable documents into a single reliable source for drivers.
cn-mobility.eu
The application brings together all operational scheduling data, such as speed restrictions, schedule directives, future digital commands and driving recommendations to be displayed in a single, unified interface via an onboard device or tablet. This eliminates the need for drivers to switch between multiple documents on the go, whilst also providing a retrofit option for existing and older vehicles.
Instead of spending time gathering and managing information, drivers can now focus on what really matters: operating trains safely and effectively. No other independent solution currently exists that can combine all the necessary information into a single output format.
The solution’s architecture not only unites documents and information in one view; but assembles them centrally with a single train number entry. The server then compiles the individual timetable, including all relevant documents and replacement timetables and stores them on the driver’s device until expiry. This allows pre-loading timetables for departure stations with no WiFi or cellular service.
Regarding data, ownership remains with our customers, who already have contracts with infrastructure managers in place. The Dynamic Schedule simply uses that data, under contract, to generate digital timetables. The application itself doesn’t hold or own data, it simply produces the output using customer-authorised information.
Thanks to its modular, vendor-independent design, additional features such as driving recommendations and access to company documents can also be incorporated.
The Architecture Behind the Application
At the Dynamic Schedule’s core is a proxy server that connects to different data sources. These might be the infrastructure manager’s server containing the basic timetable, or files provided directly by customers and stored on the proxy. When a driver requests a timetable for a specific train number and date (most often for the same day), the system follows a defined sequence:
. Basic timetable – First, the server checks with the infrastructure manager to retrieve the official base timetable.
. Daily infrastructure updates – Next, it looks for daily bulletins, such as speed restrictions or route issues, which usually arrive the day before via the infrastructure manager. These are merged with the basic timetable.
. Construction timetables – The system then queries the construction management timetable to check if work is affecting that service. If so, the relevant construction timetables are downloaded and integrated.
. Validation checks – Once all sources are combined, the system verifies that the data can be properly aligned. If any information cannot be matched to the route (for example, if a construction site location cannot be identified), the system flags an error. In such cases, the driver is notified that the timetable is incomplete and manual verification is required.
The final file is sent to the driver’s tablet in the cab only after these checkpoints confirm that the timetable is complete and safe. At this point, the driver has every piece of information needed – from the base schedule to speed limits, construction diversions, and daily notices – all in one place. This ensures they can start their journey with confidence, knowing the timetable is accurate and up to date.
Implementation and Training
Implementation depends on the type of railway business, but technically the process is straightforward. If a company is already connected to the relevant services, setup can be completed within about two weeks, after which a pilot phase can begin. Typically, this involves five to ten drivers testing the system for eight to ten weeks. By the end of the pilot, operators can confirm that the software works as expected, is safe and can be integrated into daily operations.
Once the pilot phase is complete, the safety team must conduct a formal risk review, which usually takes a few more weeks. After that, the final step is driver training.
The scale of this depends on company size: for a small operator with 10 drivers, rollout is quick, but for a business with 250 drivers, training naturally takes more time. The technology itself is fast and simple to deploy – the main factor is how large and complex the organisation is.
To support this process, cn-mobility offers hands-on guidance during the test and pilot phases. The software is designed to be easy to use: if you can read a railway timetable, you can operate it without difficulty. The company provides a handbook and training materials, and can deliver instruction either on-site, or remotely via Teams. During pilots, cn-mobility will often work closely with company trainers or staff managers, who then become the in-house instructors for wider rollout. This ensures that by the time the system goes live, operators already have the internal expertise to train their own teams effectively.
www.cn-mobility.eu
