Home / Platform
Platform overview
Rules in the cloud. Control at the gate.
Two layers do the work. TMS holds the operational and commercial rules. The Fast Travel Local controller connects those rules to the equipment at every lane.
Architecture
One architecture, from the operator's screen to the barrier.
Operator registration, access permissions, tariffs, sanctions and invoicing. Every recorded passage becomes a billing record at the applicable rate.
It drives the barriers and integrates plate and tag readers. Its design keeps local authorisation lists, so lanes can keep identifying vehicles if the server link drops. Behaviour is validated per site.
Delivered examples include Quercus ANPR, TagMaster RFID and Automatic Systems barriers. Equipment varies by site.
Integrations
Trip creation, retrieval, updates and cancellation for taxi and ride platforms. OAuth2, provider-scoped.
At Oslo Airport, connects bus-platform information with operators' passenger information.
EHF and PEPPOL invoicing for operators and fleets.
What's deployed
Delivered, configurable or built for your site.
We separate what runs today from what we configure for you and what is project work. You'll see the same split in every proposal.
| Capability | Status | What it means for you |
|---|---|---|
| Vehicle registration and permissions | Delivered | Operators and vehicles register once; access follows the site's rules. |
| ANPR / RFID identification and barrier control | Delivered | Vehicles identified at the lane; authorised in real time. |
| Virtual queue and call-forward | Delivered | Waiting moves off the curb; vehicles are called when needed. |
| Per-passage billing and sanctions | Delivered | Each passage invoiced at your rates; your sanctions enforced. |
| AirportAPI V2 for trip platforms | Delivered | Documented interface for external taxi and ride platforms. |
| Separate operator classes, tariffs and reporting | Configurable | New operator groups set up with their own rules and reconciliation. |
| Adapters for equipment already on your site | Project work | Integration and validation against your installed readers and lanes. |
Delivery
How a new site goes live.
Map the site.
Lanes, equipment, networks, operator records, fee rules and operating constraints.
Prove the integration.
Test equipment, events and billing outputs against agreed cases.
Go live in phases.
Migrate records, reconcile counts, keep a rollback route until acceptance.
Run it together.
Configuration, procedures, support ownership and maintenance documented.
Our Norwegian service commitments. Coverage, response and restoration targets for a new site are agreed with you.
Next step