How to integrate Pysae with Hastus or ABC Planning

For operators who use Hastus or ABC Planning to build their rosters and timetables, the question of integration with an AVM like Pysae is central. The AVM needs planning data to function: without reliable theoretical timetables, there is no advance/delay calculation and no coherent punctuality reporting.

What Hastus and ABC Planning produce

Hastus (published by GIRO) and ABC Planning (ABC Informatique) are planning tools that manage service construction, driver and vehicle assignment, and roster optimisation. They produce structured output data exportable in standard formats including GTFS.

How Pysae consumes this data

The primary entry point is GTFS. Pysae imports planning data in GTFS (General Transit Feed Specification) format, the global open standard for transport timetables. If Hastus or ABC Planning exports a valid GTFS, Pysae can import it directly.

In practice: the planner produces rosters, exports a GTFS file, and this file is imported into Pysae (manually or automatically via API). Pysae then calculates in real time the deviations between vehicle GPS positions and the imported theoretical timetables.

Automating the synchronisation

Pysae offers an API that automates the import of new GTFS versions as soon as they are produced by the planning software. This eliminates the risk of operations running on stale data.

What to check before starting

Three points deserve attention: the quality of the GTFS produced, the desired update frequency (daily, weekly, or at every service change), and return flows (should operational data from the AVM feed back into the planning software?).

Do you use Hastus or ABC Planning? Talk to our deployment team to assess the integration.