Custom SIRI integration development
SIRI, Service Interface for Real Time Information, is the European standard for exchanging real-time public transport information: where vehicles are, expected departure times and disruptions. In the Netherlands, real-time data still largely flows through proprietary interfaces, and the BISON platform is working on a Dutch SIRI profile. Appfront builds integrations that receive or deliver SIRI data and, where needed, translate to and from the Dutch interfaces.
What is a SIRI integration?
SIRI stands for Service Interface for Real Time Information. It is a European standard for exchanging real-time public transport data between systems: where a vehicle is, when it is expected to depart or arrive, which connections are being made, and what disruptions there are. SIRI is used in many European countries, often together with NeTEx for timetables.
In the Netherlands, real-time public transport data still largely flows through proprietary interfaces, such as KV6 for trip punctuality and KV17 for changes, which reach consumers via the data desks and DOVA's DRIS server. The BISON platform, part of DOVA, is working on a Dutch SIRI profile. If you work with international parties or use software from outside the Netherlands, you therefore often have to deal with two worlds.
We build custom solutions because situations differ: do you supply data or consume it, which standards do your partners use, and what is it for. The integration receives or delivers SIRI data and, where needed, translates to and from the Dutch interfaces. We factor the status of the Dutch profile and what your partners require into the first step.
Real-time via SIRI
Positions, predictions and disruptions.
Two worlds connected
SIRI alongside the Dutch interfaces.
Reliable data
Missing or outdated data flagged.
How we build your SIRI integration
We start with your use case: do you supply data or consume it, for which areas and operators, and which standards do the parties you work with use. Then we establish which SIRI services are needed, such as vehicle positions, expected times or disruptions, and how they relate to the Dutch interfaces and the timetable. We often start with one service and one area, because that is where the translation between standards can be tested fastest. Other services and areas follow. Afterwards, we maintain the integration as standards or profiles change.
Supplying or consuming, and for whom.
Which SIRI services and interfaces.
Receive, translate, deliver.
Go-live, monitoring and maintenance.
What a SIRI integration actually does
The components below feature in almost every SIRI integration. Which ones you need depends on your use case.
Vehicle positions
Where a vehicle is running.
Expected times
Departure and arrival.
Disruptions
With text for travellers.
Translation
To and from interfaces.
Timetable
Planned alongside real-time.
Monitoring
Outdated data flagged.
Who we build a SIRI integration for
The integration is intended for organisations that supply or use real-time public transport data and have to deal with SIRI. The more partners and areas involved, the more it delivers.
Transport operators
Supplying data. The right standard matters.
Public transport authorities
Concessions and data. Overview matters.
Travel information
Apps and displays. Up-to-date data is the core.
Mobility platforms
Combining transport. Crossing borders matters.
Technology and integrations
This page is about SIRI. For public transport software as a whole, see our page on public transport software, and you can read how we work with real-time public transport data in our case study on reliable accessibility for GVB. For integrations in general, see our page on integrations. You can read about our way of working on building software.
Why Appfront for your SIRI integration?
Two standards side by side, and data that quietly goes stale without anyone noticing, cost travellers their trust and organisations their time. That is what we build around: up-to-date data in the standard your partner asks for, a translation that is accurate, and monitoring for what is missing.
One translation
SIRI and interfaces together.
Up to date
Outdated data flagged.
Future-proof
Keeps pace with the profile.
Security and privacy in a SIRI integration
The integration processes data about vehicles, journeys and disruptions, and sometimes about staff locations or shifts. Access to deliveries and consumption is managed per party, credentials are stored encrypted, and every delivery is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. Monitoring alerts you when a source stops delivering.
Frequently asked questions about a SIRI integration
Questions that operators and travel information providers ask before they get started.
SIRI stands for Service Interface for Real Time Information. It is a European standard for exchanging real-time public transport data, such as vehicle positions, expected departure and arrival times, and disruptions. The standard consists of several services, each of which exchanges part of that information.
In the Netherlands, real-time public transport data still largely runs through proprietary interfaces, such as KV6 and KV17. The BISON platform, under DOVA, is working on a Dutch SIRI profile. If you work with international partners, software from outside the Netherlands or cross-border transport, you already encounter SIRI today.
Yes, as far as the data corresponds. The integration can convert SIRI data into what a Dutch consumer expects, or the other way around. Where the standards do not match one to one, we agree in the first step how that is handled.
NeTEx is the European standard for planned data, such as the timetable and the network. SIRI is for real-time data during the day. In an integration they often go together: SIRI tells you what is happening now with a journey that is in the timetable.
The integration reports it. Data that is too old is not passed on as current, so an app or display does not show an expected time that is no longer correct. How long data stays valid, we tailor to the application.
We keep the integration up to date when the profile or the standard changes. Because the Dutch profile is still being developed, we build in such a way that changes to the profile do not affect the entire integration.
For carriers who need to supply data to partners that require SIRI, for suppliers of apps and stop displays that work with international software, for mobility platforms that combine cross-border transport, and for public transport authorities dealing with multiple standards.
Real-time public transport data using SIRI?
Tell us whether you supply or consume data, for which areas, and which standards your partners use. We'll show you what the integration looks like.