Transmodel may prove of value to:

  • organisations within the public transport industry thatspecify, acquire and operateinformation systems: Transmodel may be distilled, refined, or adapted to form a comprehensive data model for the organisation. This will enable the organisation to specify its database structures and/or its system interfaces, in such a way that separate modules can be openly tendered but will still integrate easily.
  • organisations that design, develop and supplyinformation systems for the public transport industry: Transmodel may be adapted to form a comprehensive data model for the product suite. This will enable the organisation to develop its products in such a way that separate modules will integrate easily, but also so that they may be sold separately to clients seeking Transmodel-compliant systems.

Transmodel may be applied to any framework for information systems within the public transport industry, but there are three circumstances to which it is particularly suited:

  • specification of an organisation’s ‘information architecture’;
  • specification of a database;
  • specification of a data exchange interface.

Tranmodel EN12896:2006 is an adopted European strandard. It corresponds to Transmodel Version 5.1. Transmodel Version 6 is currently being published: it will replace EN12896:2006 (and IFOPT EN28701). Three parts are currently available:

  • Part 1: Common Concepts
  • Part 2: Network Topology
  • Part 3: Timing Information and Vehicle Scheduling

Knowledge of modelling methodologies, in particular of UML basics is very useful. Notation UML 2 is an object–oriented modelling notation and is used for describing (specifying, documenting and visualizing) the conceptual data model in Transmodel. The UML specification has proved efficient because it facilitates common understanding and use of conceptual data model. Transmodel uses a notation that bears some features of UML 1 (or E/R conceptual modelling), in particular as regards the labelling of roles/relationship names. Transmodel documentation provides the necessary detailed information (Part 1: Common Concepts, Methodology for conceptual modelling).

Transmodel can serve as a starting point for the definition of a database schema, which will be used for the physical implementation of databases. Whether applications access a common database built to this schema, or have their own databases and exchange data built to consistent schemas, the use of an overall reference data model assists integration. Public transport organisations may require different applications toexchange datawith each other. Also, public transport organisations may exchange data with other organisations. In either case, the reference data model can be used to help design the interfaces. Two standards NeTEx and SIRI have already used Transmodel parts and generated standard data exchange implementations:

  • SIRIfor Real Time Passenger Information,
  • NeTEx for the domains Network Topology, Timing Information, Vehicle Scheduling, Fare Information.
In both cases the user has to determine the requirements of a particular context, extract a sub-modelbefore proceeding to the definition of a database schema or of data exchange profiles

Transmodel documentation is distributed by national standardisation bodies which determine documentation price. A further use is free of charge.

Model Structure

Several concepts are shared by the different functional domains covered by Transmodel. This data domain is called “Common Concepts”.

“Reference Data Model – Common Concepts” domain incorporates data structures used by all other data domains of Transmodel. It is composed of the following data packages:

  • Versions and Validity: describes the successive versions of data elements and the conditions to be attached to elements to precisely know when they should be used;
  • Responsibility: describes the type of responsibility or role the different organisations may have over the data;
  • Generic Framework: describes a number of generic objects and representational mechanisms that are not specific to transport but which are specialized or used by Transmodel transport related objects.
  • Reusable Components: certain common low-level components, for example TRANSPORT MODE, SERVICE CALENDAR, DAY TYPE, etc. are not specific to any particular functional part of Transmodel but are widely used in several different functional areas.
  • Explicit Frames referring to generic data: describes the mechanisms useful to build coherent sets of versioned data. Part 1 presents explicit frames for data referring to the Common Concepts domain.

Public Transport Network incorporates data structures which form the network topology description of Transmodel V5.1 and the major part of the fixed objects model of IFOPT. It is composed of three data packages:

  • Network Description: routes, lines, journey patterns, flexible routes and lines, specific point types;
  • Fixed Objects: sites, stop places, equipment, parking places;
  • Tactical Planning Components: journey patterns, timing patterns, service patterns, connections, common sections.

  • Vehicle Journeys , Service Journeys, Coupled Journeys, Flexible Service,
  • Journey Times and Journey Patterns Times, Interchanges and Interchange Rules,
  • Dated Journeys, Timetables Passing Times, Dated Passing Times.

Based on the Timing Information model, Vehicle service, i.e. the workplan for a vehicle for a whole day, planned for a specific DAY TYPE is described in terms of BLOCKs, i.e. of the work of a vehicle from the time it leaves a PARKING POINT after parking until its next return to park at a PARKING POINT.

In order to facilitate the management of information, data in an information system may be associated in groups of data, which share the same validity conditions. Such a group of data is described by a VERSION FRAME.


Transmodel v6 is provided in modular form. The series comprises the following documents:

  • Public Transport Reference Data Model – Part 1: Common Concepts
  • Public Transport Reference Data Model – Part 2:  Public Transport Network
  • Public Transport Reference Data Model – Part 3:  Timing Information and Vehicle Scheduling
  • Public Transport Reference Data Model – Part 4: Operations Monitoring and Control
  • Public Transport Reference Data Model – Part 5: Fare Management
  • Public Transport Reference Data Model – Part 6: Passenger Information
  • Public Transport Reference Data Model – Part 7: Driver Management
  • Public Transport Reference Data Model – Part 8: Management Information and Statistics
Together these documents create version 6 of the European Standard EN 12896, known as “Transmodel” and thus replace Transmodel V5.1 and IFOPT (Identification of Fixed Objects for Public Transport, EN28701).

The split into several documents is intended to ease the task of users interested in particular functional domains. Parts 1,2 and 3 were finalised in 2015.

To get the documentation the users have to address their national standardisation organisations.

The web site gives a lot of additional information. Contacts are available to the Transmodel development team.

Transmodel partial data dictionaries (i.e. referring to the Common Concepts, to the Network Description, to Timing Information and Vehicle Sheduling) are available the corresponding documentation parts.

An overall Data Dictionary, for Parts 1-8 all together, is provided in Public Transport Reference Data Model-Part 9:Informative Documentation (TR 12896:2018) which replaces the 2016 version. This Part contains additional information as regards the model evolution or model dependency graphs which is useful for those who implement Transmodel, in particular for users who have already some knowledge of previous Transmodel versions. This version of the Data Dictionary defines not only the concepts, but tables also provide definitions of the detailed attributes together with a short description of them.


Transmodel is the European Reference Data Model for public transport, and constitutes an offer to public transport companies and other providers of services related to the process of passenger transportation (planning, operation and information), to suppliers of software products supporting these processes, and to consultants and other experts acting in the field of public transport in the widest sense.

The reference data model, developed at conceptual level, can support the development of software applications, their interaction or combination in an integrated information system, and the system‘s organisation and information management which rules the utilisation of the existing telematics environment in a company (or group of companies) running computer applications supporting the different functional areas of public transport.

As a reference standard, it is not necessary for individual systems or specifications to implement Transmodel as a whole. It is possible to describe for those elements of systems, interfaces and specifications which fall within the scope of Transmodel:

  • the aspects of Transmodel that they have adopted;
  • the aspects of Transmodel that they have chosen NOT to adopt.

Transmodel may be applied to any framework for information systems within the public transport industry, but there are three circumstances to which it is particularly suited:

  • specification of an organisation’s ‘information architecture’;
  • specification of a database;
  • specification of a data exchange interface.

The Reference Data Model (Transmodel v6) covers the following data domains:

  • Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places: this part corresponds to the network description as in Transmodel V5.1 extended by the relevant parts of IFOPT (EN28701);
  • Timing Information and Vehicle Scheduling: runtimes, vehicle journeys, day type-related vehicle schedules;
  • Passenger Information: planned and real-time;
  • Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions;
  • Fare Management: fare structure and access rights definition, sales, validation, control of access rights and/or travel documents;
  • Management Information and Statistics including data dedicated to service performance indicators;
  • Driver Management:
    • Driver Scheduling: definition of day-type related driver schedules,
    • Rostering: ordering of driver duties into sequences according to some chosen methods,
    • Driving Personnel Disposition: assignment of logical drivers to physical drivers and recording of driver performance.
NeTEx is an implementation of Transmodel. More explanations concerning  model semantics is here.

Transmodel is a conceptual model, developed and presented in UML. It may be used for the tackle the definition of a data base schema or data exchange messages, however, Transmodel task is not implementation but the definition of a conceptual based on UML (Enterprise Architect was used to create it) of the different public transport domains. The UML model is available from the Transmodel Web Site.
There are two standardized data exchange format as regards the implementation of Transmodel: SIRI and NeTEx. These projects have used submodels of Transmodel to generate physical models and xml schemas. Currently one more implementation using Transmodel is being standardised: Open API for Distributed Planing Systems and another one is planned: Operational Raw Data exchange.

Yes, there is a staged approach in the Transmodel update process;Part 1- Common Concepts, Part 2- Public transport Network and Part3 – Timing Information & Vehicle scheduling documents have already been published. Part 4: Operations Monitoring and Control and Part 5: Fare Management documents will be ready by end of 2017. Part 6: Passenger Information and Part 7: Driver Management early Part 8 - Management Information and Statistics mid 2018.
Since Transmodel is a CEN standard, to get the documentation you have to contact your national standardisation body.