Transmodel implementation in Belgium

The SPIDER STIB project is carried out by DIGINEXT in order to reorganize the operational transport information system for the STIB which is the public transport operator of the Brussel area.

Facilitate and optimize the management of the IV (improve the Marketing department efficiency), this involves the implementation of :

  • tools for centralized management of IV channels,
  • a single library,
  • remote tools for updating equipment Management,
  • automatic dissemination of information according to external events

The new information system architecture is built upon the product MobilitX.

MobilitX is a real-time high performance reliable backbone dedicated to high-speed and massive transport information exchange. MobilitX gathers all the information related to transport, the reference information as well as the real time information, producing added value services and information, and delivering the information to the transport actors and the passengers.

MobilitX implements the European standards of the transport sector: Transmodel (EN 12896) IFOPT (EN 28701), NeTEx, SIRI) as well as proprietary interfaces.

In operation since: September 2017 (Hub+Situation Management)

Fixed Equipments : Mid 2019, Onboard Vehicle : End 2019

Information provided by: DIGINEXT

Target users/location

SPIDER system is dedicated to the Public Transport Operator of the city of BRUSSELS (STIB).

Implementation scope

  • Time saving (Real time information of all travelers), by setting up a central, flexible and efficient tool adapted to programming and real-time broadcasting. IV on the entire network
  • Standardize the Passenger Information, this means setting up a technical solution that facilitates evolutions and interactions with other systems, reduces development costs and maintenance costs
  • Enrich the IV, no longer be limited to waiting times and the next stop and make available to travelers maximum information available and keep the flexibility to adapt the information disseminated.
  • Improve reliability, support the growth of channels, reduce the number of systems, better understanding of data flows


SPIDER STIB system implements the following parts of Transmodel & IFOPT:

  • Network topology
  • Timetables
  • Passenger Information
  • Situation Management
  • Accessibility
  • Facility Management


HUB and integrator of transport data from heterogeneous systems:

  • Multimode, multi operators
  • Centralizated Real Time Situation Management
  • Common data repository natively compliant with Transmodel

Transmodel implementation in Slovenia

  • Two early software systems AVRIS (2000) and SIJPRIS (2009) have implemented a nationwide IT database schema that corresponded to the early version of Transmodel conceptual model. Technically, the AVRIS system was a desktop application and SIJPRIS was a distributed information system developed by the Slovenian Roads Agency (public transport authority in Slovenia, part of Ministry of Transport at that time) primarily for the management of the public inter-urban (long distance) bus transport. The system supported public transport authority tasks (management and registration of public transport infrastructure including stop place model and scheduled services model) and concessioners’ tasks (timetables proposals, periodical reporting about financial figures, number of passengers transported) stipulated by the law. Data exchange within SIJPRIS was implemented through a web service, using XML documents formatted according to own XML schema called
  • Since 2017 a national integrated public passenger transportation system (IJPP, ) is in operation. It integrates all public transportation operators in Slovenia, including the national railways, to provide a unified ticketing & fare collection system. With 37 bus and one national railway operator, the IJPP deploys more than 1500 automated fare collection and validation terminals. By using unified ticketing users can travel across the country, regardless of the transportation provider. Ticket validations are performed with contactless cards.
    The backoffice system consist of the three modules:

    • public transport infrastructure (infrastructure points and links, stop places, zones, interchanges etc.)
    • timetables (timing information and a tool for creation of timetables)
    • management analytics and reporting (set of tools, which enable different public transport data views (i.e. temporal data, financial figures, number of passengers transported, number of kilometers driven (per PTO, per vehicle etc.), number of fares sold,  etc.) taking into account linked passenger validations on terminals).

The IJPP system was built on the experiences from the previous AVRIS and SIJPRIS systems. It adopted the Transmodel-like conceptual database model (see Figure 1). However, the model does not yet consistently separate infrastructure, timing and service pattern layers as suggested in Transmodel.
Components of the IJPP system (Figure 2) are: IJPP database and the three PT systems (PT journey planner, national PT timetables, national PT infrastructure (daljinar).

  • Based on the IJPP, a national journey planner was developed, which integrates all public transport in Slovenia (urban, inter-urban and rural travel, long distance travel):

Figure 1:  Transmodel-like conceptual data model of the IJPP

Figure 2:  IT architecture of the IJPP system

Target users

Different IJPP IT systems for target different users:

  • PT journey planner is aimed for all passengers.
  • Smartcard ticketing initially started with student population in 2017 and is planned to extend for all passengers.
  • The national PT timetables system is mandatory used by all PT operators for timetable design and timetable submission to the PT authority. PT authority manages timetables (registration, modification, rejection).
  • National PT infrastructure system manages physical stop points within PT network.

Implementation scope

All systems comprising IJPP are nation-wide system.


Functionalities of the IJPP system enable:

  • Management of the national infrastructure (registration of stop places its location, status and inventory (i.e. information display)
  • Management of timetables for urban (city), inter-urban () and rural areas for city buses, coaches and rail
  • Passengers can plan a PT journey planner using
  • The IJPP system uses a card centric approach where the media is a prepaid smart card


System has been in use since 2017 and will be integrated with National Access Point (NAP, compliant with Transmodel and NeTEx) in 2019.

Transmodel implementation in Switzerland

General information

The current standards for the exchange of Public Transport information are HRDF and VDV 453/454. For the public transport open data server VDV 431 was used (

The introduction of IFOPT in Switzerland has already begun.

The SBB uses an internal architecture model (Famoos).

To integrate traffic in the Léman area (SBB and SNCF) we are now starting to use (Transmodel based) NeTEx and Siri standards. The project will be production ready by the end of 2019.

The current systems (Info+ for timetable and CUS for real-time PI aggregate the whole data on public transport in Switzerland in a single file and stream and provides it in different flavours to all data users. Data providers are obliged by law to provide the necessary information. SBB is tasked by the federal government in the form of SKI with aggregating and delivering the information. SBB is also tasked with improving the quality. In fact: There is already one national access point for the whole public transport system. There is no integration with air travel and some types of long-distance buses are not part of the system.

Fares are handled currently outside of this framework.

SBB is increasing its awareness of European standards. Currently the focus is in the blue shaded area. In addition, the green area will be considered more in future. Also, more focus on Transmodel as an architecture model is considered. As transforming in interfaces is easier, when the business architecture model is based on the same standard.

Note: VDV is also partially Transmodel based:  e.g. VDV431 and CEN/TS 17118

Target users

  • Operators
  • Data consumers (application providers)
  • Open Data Users

Implementation scope

  • All cross-border traffic and lines
  • All lines stopping at defined interesting stop places (in the case of France the railway stations of Léman Express, in Germany the stop places where SBB GmbH = SBB corporation train stops).
  • All lines stopping at other defined points of interest (e.g. when with a 50 m walk over the border there may be an interchange.

For the project Léman Express PI (Passenger Information) will be exchanged with France. SBB will provide NeTEx timetables for the region (train and local transportation) and will obtain the relevant border belt from France (time tables for the three adjacent departments).  For real-time exchange the subscription model will be used. SBB intends to import Siri ET for the border belt, SNCF intends to obtain Siri SM for selected points. Currently the definition of the border belt in Switzerland is:

  • all cross-border traffic and lines
  • all lines stopping at defined interesting stop places (in the case of France the railway stations of Léman Express, in Germany the stop places where SBB GmbH = SBB corporation train stops).
  • All lines stopping at other defined points of interest (e.g. when with a 50 m walk over the border there may be an interchange.

Definition on the profiles to be used have started and experimental export of the data was done. The current implementation will act as a transformer HRDF <-> NeTEx and VDV <-> Siri (HRDF – Hafas Rohdatenformat = Hafas raw data format, , VDV ). This will restrict the profiles for the time being. For real time currently two variants (A and C) are discussed.


  • T – Transformation
  • C – Changes needed
  • DIVA and DDIP are products by Mentz
  • DIVA: Dialoggesteuertes Verkehrsmanagement- und Auskunftsystem = Time table planning system and collector

DIVA4 is web-based, multi-client capable that visualizes all planning contents on maps. DIVA4 meets the needs of smaller transport companies for quick, easy timetable scheduling and of large operators for complex planning and optimization tasks. DIVA4 is used by transport authorities and associations to exchange data and synchronized timetable data for any number of large networks. DIVA4 is thus able to serve as a database for high-quality, multimodal journey planning systems.

  • DDIP: Dynamische Datenintegrationsplattform = Dynamic Data Integration Platform

The Dynamic Data Integration Platform (DDIP) is a central data platform for the reception, intermediate storage and transmission of real-time transport data from different data suppliers to diverse data recipients (subscribers). DDIP communicates with serving systems using standard real-time interfaces to exchange information. The common international standards supported are: VDV453 (ANS, REF-ANS, DFI, REF-DFI, VIS, AND), VDV454 (AUS, REF-AUS), SIRI (ET, PT, SM, ST, VM, CM, CT, SX and FM).

  • Info+:

System for transformation of operational timetable data into data for passenger information, as well as a system for collecting, merging and providing timetable data originating from numerous sources (all Swiss transport organizations and from foreign countries).

  • CUS:

The Customer Information System (CUS) is the centerpiece of the dynamic passenger information of the Swiss Rail (SBB). CUS is operated by SBB based on a direction of Swiss Federal Government and it is the real-time data platform for public transport Switzerland. The main advantage of CUS is the automation of providing passenger information for announcements or screens in railway stock. CUS includes around 20 single products like for example SMS alarm, mobile information tool for customer contact or VDV (Verband deutscher Verkehrsunternehmen) interfaces.

DiDok Dienststellendokumentation = National Stop Database

DiDok contains all national stop points in Switzerland. Also, important foreign stop points are mapped within DiDok. Currently the most used part is an Excel implementation. For the time table currently HRDF contains all necessary stop point information. There may be differences between DiDok codes and Info+ codes for foreign stop points. The NeTEx implementation will contain the stop point information as well. DiDok will remain the master (and primarily accessible by an API – application interface - for internal usage).

Further Activites

SBB is considering further implementations


  • Timetable data exchange with NeTEx and Siri between SNCF and SBB
  • Realtime data exchange with NeTEx and Siri between SNCF and SBB


Permantent data exchange from 2019 onwards for timetables and realtime data.

Transmodel implementation in Norway

General information

The Norwegian public transport sector has recently been re-aligning to facilitate next-generation dynamic services. As part of this initiative, the Norwegian State Railways has been reorganized and the majority of its system portfolio migrated to a modernized architecture, ensuring a scalable and maintainable platform. This to facilitate innovation, rapid change and shorter time to marked in order to keep the public transport solutions both customer centric and constantly improved. Which in turn will ensure better availability of public transport, simpler use and increased popularity of such services.


Per 2018, compliant projects in Norway support elements from Part 1 to 6 of Transmodel, as described in further detail below:

National Journey Planner

The Norwegian National Journey Planner project has implemented support for NeTEx parts 1 and 2 for its Stop Place and Network/Timetable data hubs, and SIRI (numerous parts) for its real-time proxy handling Estimated Timetable, Situation Exchange and Vehicle Monitoring feeds. Support for NeTEx part 3 is partially implemented, with ticket sales for travel by railway and within the greater Oslo region provided within the Journey Planer smartphone apps.

Most backend systems are implemented using open source tools:

Furthermore, data and service APIs are publicly available and free to use by third parties at no charge.

Additionally, there is a Norwegian initiative to align and "translate" the APIs and graph search services of source projects Open Street Map (OSM) and its corresponding Open Trip Planner (OTP) to Transmodel based terms. This is both done as a supplement to shift its current GTFS centric implementation towards richer Transmodel data structures, in order to ensure that upcoming features can be supported, as well as ensuring that readily available Norwegian services for stop places management and travel information management/queries will be standard compliant.

Products and Travel Rights

As a proof of concept, the current Railway Price and Product backend system is being migrated to a Transmodel oriented model, with relevant data for price and product implemented as NeTEx Fare type objects. The project goal is to ensure that most of the related architecture, data structures, information exchange and system implementations align to Transmodel topology and its NeTEx implementation (e.g. ticketing and booking systems, national data hubs, public and private APIs etc.)

The future ambition is to fully support NeTEx part 3 in flexible combinations of dynamic price elements, i.e. pricing and its parameters within different levels the product model level, to ensure all necessary fare related information – including sales packages and access/travel rights – can be collected and distributed through this format for all modes of transport in Norway.

Next Generation Ticketing

Currently, standardized travel cards (and additional paper and mobile ticketing QR codes for some fare domains) are the interoperable ticketing platform for all counties in Norway. Implementing a common Travel Rights Storage in the National Order Database (NOD), a Transmodel based National cloud-based storage for account information and tickets / travel agreements will however facilitate the migration to account based ticketing as the mandatory interoperable platform.

Initially, this service will support pre-purchased tickets. In later iterations, the objective is to enable automatic purchases as well as fare aggregation and capping for both local and multi-region/operator journeys. Eventually, the aim will be to provide pay-as-you-go by use of positioning and/or beacon-based check-in/check-out sensors with on-the-fly fare calculation and payment.

Entur will also provide APIs to enable third party vendors to sell nationwide seamless travels.

Target users

  • Government
  • Public transport authorities (PTAs)
  • Public transport operators (PTOs)
  • Passengers

Implementation scope

All modes of public transport in Norway


Elements from Transmodel currently implemented:

  • Stops / Points of Interest (incl. equipment/facilities and geo-location)
  • Network
  • Timetable
  • Fares (partial)
  • Vehicle scheduling (partial)


Norwegian National Journey Planner (with ticketing)

Transmodel implementation in Modena

General information

SETA S.p.A (Emiliana Autofiloviari Company) is the operator of the local public transport service in the provincial areas of Modena, Reggio Emilia and Piacenza.

Since 1 January 2012, SETA SpA was founded by the aggregation of the public transport companies of Modena, Reggio Emilia and Piacenza, and is responsible for the entire production system of PT bus service  of the three provincial area: from the exercise of the Urban and extra-urban bus transportation, maintenance, ticketing and customer service (information, complaints, etc.).

Seta S.p.A manages 29.7 million kilometres of local public transport, has a staff of 1,046 employees and a fleet of 810 vehicles.


The Exbus - AVM ( Automatic vehicle monitoring ) in operation is compliant with Transmodel and developed under ORACLE DBMS.

Target users

Emilia Romagna Region – Modena Province – operator SETA SpA 450 vehicles , more than 3.000 stops , urban service in Modena , Carpi , Sassuolo , Interurban : Modena Province.


Service Data version, Transport Network Topology , Line/route description, Vehicle Data, Run data, running times, Drivers shifts, Driver shifts assignments, Final data of shifts, final data of passing time, Vehicle alarms, Depot data.

Transmodel implementation in Catania

General information

The urban service of the city of Catania stretches to the municipalities of Aci Castello, San Pietro Clarenza, Mascalucia and also reaches the town of Vaccarizzo, south of the city.

Approximately fifty ordinary lines operate the service, a quick shuttle ("Alibus") connects the center to the airport and a quick shuttle ("BRT") connects the Two Obelisks Parking with Stesicoro Square. The latter is the first of four lines provided by the Municipality of Catania with preferential lanes;


The Exbus - AVM (Automatic vehicle monitoring) in operation is compliant with Transmodel and developed under ORACLE DBMS.

Target users

Catania city – Approximately 400 bus , 1100 stops


Service Data version, Transport Network Topology , Line/route description, Vehicle Data, Run data, running times, Drivers shifts, Driver shifts assignments, Final data of shifts, final data of passing time, Vehicle alarms, Depot data.

Transmodel implementation in Spain

GMV is a leading firm in the design, development, implementation and rollout of Intelligent Transportation Systems (ITS) based on IoT, mobile communications and GNSS, guaranteeing compliance with sector standards such as TRANSMODEL, GTFS, SIRI, NeTEx and CAN bus. GMV offers all-in, turnkey, ready-to-go solutions, getting involved in the complete development of the project and incorporating its own in-house hardware and software.

Our experience and continual innovative drive has brought GMV solutions to over 400 transport operators from 100 cities in countries like the United States, Spain, Malaysia, Poland, Morocco, Sweden and Mexico.

In particular GMV provides Fleet Management Systems (CAD/AVL), Fare Collection Systems, Passenger information system (on board the vehicle, at the stations, websites, mobile APPs, etc.), Service Planning Optimization tool and resource planning Optimization tool.  These tools are provided both for bus and railway transportation.

The goal of GMV ITS Solutions is to increase ridership by improving the convenience, punctuality and reliability of the transportation services. Additionally passenger information engine generates accurate and real-time information and spreads it through the channels that passengers demand today.

Return of Investment is achievable through the efficiencies and cost reduction that GMV ITS Solutions brings to Transport Providers’ operations team. Having the right information at the time when it is needed will help making the right decisions.

GMV-ITS in figures:

Compliance with industry standards

GMV is compliant with the relevant industry standards to share information across systems, either supplied by GMV or third parties. This feature allows for GMV ITS Solutions integration in multimodal environments and smart mobility initiatives. GMV’s systems are based on CEN Transmodel conceptual model and some of supported exchange formats are:

  • GTFS: GMV imports and exports information through GTFS files. The GTFS files exported by GMV can be used by google to publish information to the passengers (routes, schedules, fares, arrival times, etc.).
  • CSV: GMV system allows to import information through predefined CSV files.
  • TransXchange v2.5 is a XML based data standard orignated in the UK for the interchange of bus route and timetable information between Transport Authority, Bus Operators and passengers, and others involved in the provision of passenger information. TransXchange is based on CEN Transmodel conceptual model.

GMV system allows to import information through TransXchange from transport operators or authorities (i.e. routes, variants, stop points) as well as from a third-party system.

  • SIRI: The Service Interface for Real Time Information or SIRI is an XML protocol to allow distributed computers to exchange real time information about public transport services and vehicles. The protocol is a CEN technical specification, developed with initial participation by France, Germany (Verband Deutscher Verkehrsunternehmen), Scandinavia, and the UK (RTIG). SIRI is based on the CEN Transmodel abstract model for public transport information, and comprises a general purpose model, and an XML schema for public transport information.

GMV system allow to export information through SIRI, for example to provide information to a third-party system (Web Site with information for transport users, Smartphone Applications, displays at stop points, etc).

  • RTIG (Digital Air Interface Protocol): RTIG is a standard air interface protocol to communicate between bus and control center. This allows having on board units supplied by different providers. RTIG is based on the CEN Transmodel

GMV’s Control Centre applications permit the connection to third party on-board units as long as they use the RTIG standard for that communication.

GMV near future plans include the implementation of Netext and Opra.

GMV decided to implement this exchange formats for several reasons:

  • A constant growth of integrations with different providers. For this reason it became necessary to use standards.
  • The wish in the industry of independence from software and hardware suppliers.
  • The need to provide information to the passengers through displays at stops, google transit, proprietary applications (Android, iOS, etc.), websites, etc.
  • The need to facilitate the information exchange between different sub-systems with a common model like Transmodel and standard protocols.
  • This feature allows GMV ITS Solutions integration in multimodal environments and smart mobility initiatives


The figure below indicates high level integration architecture of GMV ITS systems with CEN and other standards covered.

The system is composed by Fleet Management and Fare Collection subsystems working as a whole. There are several interfaces that implements different exchange protocols, and a set of web applications used in the control centre.

Target users

  • Public authorities
  • Public transport operators
  • Private Transport Operators
  • Passengers

Implementation scope

  • GMV system involves over 750 Public and private Transport Operators, nearly 34.000 vehicles, more than 1,240 on stop displays, 750,000 passengers per day knowing the ETA of the next vehicle, 1,700 millions of passengers per year. There are different implementations depending on the place:
    • Some include all the protocols and others only a number of them.
    • Some implementations exchange data with all stakeholders (Public Administrations, Operators, passengers) and others only with some of them.
    The main clients of GMV are:
    • ALSA Group.
    • Avanza Group.
    • Prasarana Malaysia.
    • Regional transport consortium of Madrid.
    • Metropolitan transport authority of Barcelona.
    • TMB (metropolitan transport of Barcelona).
    • RENFE (Spanish National Railways).
    • Government of Cyprus (Cyprus).
    • Government of Galicia (Spain).
    • Government of Castilla y león (Spain).
    • A lot of local governments and private companies in different cities all over the world: Urban Transport of Santiago de Compostela (Spain), Urban Transport of Ourense (Spain), Urban transports of Gijon (Spain), Zaragoza Tram (Spain), Urban Transport of Valladolid (Spain),  Urban Transport of Segovia (Spain), Urban Transport of Soria (Spain), Urban Transport of Caceres (Spain), Urban Transport of Mérida (Spain), Urban Transport of Toledo (Spain), Urban transport of Malaga (Spain), Urban Transport of Terrasa (Spain), Urban transport of Guadalajara (Mexico), Meknes (Morocco),  Kenitra (Morocco), Kaohsiung Tram (Taiwan), Lanstrafiken Transport Company - Kronoberg (Sweden), Syarikat Prasarana Negara Berhad – Kuantan City (Malaysia), Malta Public Transport (Malta), Railway company of Mallorca Island (Spain), Warsaw Tram (Poland), Public Transport System of Szczecin city (Poland), Bus Rapid Transit of Jakarta city (Indonesia), BRT System, Ahmedabad (India), Public Transport System of the cities Gdansk, Sopot y Gdynia  (Poland), etc.

Transmodel implementation in Hungary

Utilizing Transmodel in Hungary on national level was introduced to the community when passenger information developments began in partially EU-funded projects in regional and long-distance bus transport. Currently, 3 (of total 7) state-owned bus operators have existing Transmodel and SIRI-based solutions in their whole area of activity, 2 operators utilize Transmodel without SIRI, and 2 operators use Transmodel and SIRI partially.

Most regional operators have additional responsibility to provide local transport in particular cities, in which Transmodel and SIRI is also present. Most cities that provide local transport through municipality-owned operators also introduced Transmodel and SIRI, and are able to exchange data with regional and long-distance bus operators.

The capital, Budapest, also started utilizing Transmodel, data exchange with regional and railway operators is in development phase. Partially state-owned railway operator GySEV has already introduced Transmodel and SIRI, fully state-owned railway operator MÁV (Hungarian State Railways) has conducted pilot project together with bus and water transport operators to gain experience on working in multimodal and multi-operator environment.

Transportation government is looking to make the use of Transmodel and related standards mandatory in the future through public service contracts, and national electronic ticketing is planned to be based on these standards, as well.

Target users

  • Passenger Information
  • Public Transport Authorities and Operators
  • Institute of Transportation Science

Implementation scope

  • Implementations include network and timetable data, operation monitoring and control, driver management and passenger information through on-board, on-site and online (web & mobile) equipments.
  • Real-time data exchange utilizes SIRI standards.


  • Precise public transport stop dataset
  • Network and timetable exchange
  • Operation control
  • Real-time information about interchanges, vehicles and estimated passing times


Covers planning & operations for bus operators within ERP systems