Transit information systems such as itinerary planners, mobile apps, transit websites, passenger information pillars all depend on the transit data that feed them.
There is a clear distinction between the transit data, and the use that is made of them.
We believe that specialization is key success factor for robust information systems.
Generating the data, creating services over the data, and using the data to build an app for a end-user are all very different activities.
Collaboration between actors is a more flexible approach.
the architecture is like a chain, with different building blocks brought by different specialist actors that serve the next building block in the chain.

Open-source
We actively contribute to open source project, that's a mean to have links to other developers and build a community around a project. It is also an effective mean for innovation.

Open data
Open data is the fuel for any project. It means a possibility to create added value services.
It means that anybody can re-use the data, either for vizualition, checking or creating new services.
A limiting factor is the quality and the standardisation of data; so we try to push actors generating data though their transit activities to standardize and focus on quality. The aim is to provide transit data that can be reused in multiple contexts and projects.

Open architectures
It is important to avoid monolithic architecture that ties the customer with a specific provider and creates a de facto monopoly.
We are in favor of open-architecture, with dedicated layers that can be customized and used on-demand.
More-over the architecture should rely on a quality raw data upon which are based services that will serve multiple apps.

strong>Open standards
In open-standards the collaboration is key. It is the guarantee that a standard will be neutral and not tied to any particular interest. We promote the use of globally accepted standards. In the case of public transport, we focus on the globally accepted GTFS format for static transit data. Of course we master as well other more regional standards, but prefer GTFS because it means more possibilities for reuse as it is more global.
For the alerts and real-time several standards have emerged either at European level or world level : SIRI or GTFS-RT.

Any public transport information system is highly dependent on the quality of data.
Data that is outdated, incorrect or not accurate provide lame services, and weak information to a frustrated end-user.
Moreover the information provided should be designed to be used in several contexts.
We attach a very high importance to the quality of the data, whether static or real-time, and provide the appropriate tools to evaluate and monitor, but also to correct, filter, or augment.