Home / Solutions
Choose your starting point

The same platform, shaped to how you actually move people.

A city bus network, a staff shuttle and a charging depot do not want the same screens, the same vocabulary or the same reports. They do want the same data underneath. Start where your need is sharpest — nothing here is a separate product.

What they share

One data model underneath all seven.

The reason these are configurations rather than products: a stop, a route, a vehicle, a duty and a trip mean the same thing in every one of them.

One network, however many modes

A metro feeder, a staff shuttle and a city route sit in the same network model, so a transfer between them is a transfer rather than two unrelated journeys.

One fleet and one crew

Vehicles and drivers are not duplicated per solution. A bus that runs school transport in the morning and a charter in the evening is one vehicle with one history.

One set of numbers

Planned versus actual, cost per kilometre and on-time performance are computed the same way everywhere, which is what makes them comparable.

Scope

Where to start, honestly.

Start with the one that hurts. Every deployment we have seen that began with all seven took longer to show anything than one that began with the sharpest problem and added the rest afterwards. The platform does not charge you for that order, and nothing has to be re-entered when the second one arrives — but a first deployment that tries to be complete is a first deployment that is still being configured six months later.

Tell us which of the seven is the sharpest.

We will load your own routes, depots, fleet and crew and walk the screens you would actually use for it.

Thanks — we'll be in touch shortly.