How a scheduling module reduces duty allocation errors on a bus network

On a bus network, a duty allocation error can seem trivial on paper. In practice, it means a bus with no driver, a service not operated, a contractual penalty, and a passenger left waiting. The question is not whether errors happen, but why they happen, and how to eliminate them structurally.

Why duty allocation errors persist

The main source of duty errors is not planner incompetence: it is the tool. A roster built in Excel, or in software that does not communicate with the rest of the system, mechanically creates inconsistency risks.

What a scheduling module does

A dedicated service scheduling module is built on a single database that simultaneously holds timetable data, regulatory constraints (driving time, rest periods, collective agreement rules), and driver and vehicle availability. With every change, the system automatically checks the consistency of the whole picture. It is impossible to assign a driver already on duty, allocate a bus in maintenance, or create a sequence that violates a collective agreement rule.

The measurable gains

Fewer errors at sign-on. Drivers find a coherent, complete, and up-to-date service in the onboard app.
Time saved on roster production. Automated consistency checks reduce weekly roster production time from several hours to a few tens of minutes.
More reliable contractual reporting. The operated transport plan is directly traceable from the initial schedule.

Integration with the AVM: the missing link

An isolated scheduling module improves roster production, but it is its connection with the AVM that transforms operations. When scheduling and supervision share the same database, a service change propagates automatically to the driver app and GTFS-RT feeds.

This is the logic Pysae implements with its Network module, natively connected to the Operations module.

Want to assess the avoidable errors on your network? Request a demonstration.