This site will inform you about Transmodel, the Reference Data Model for Public Transport and its recent evolution.

Transmodel version EN 12896: 2006 (Transmodel V5.1) has been approved as the European Norm.

It has been developed by a European team within which various levels of end users were represented.

Transmodel has been presented at many conferences and discussed within seminars open to transport and information modelling experts for years. It has received, and still receives feedback from a wide audience to incorporate a variety of new points of view.

Since 2014 Transmodel is being revised as several extensions and enhancements have been required:

  • One of the most notable extensions is the data model referring to the fixed objects for Public Transport, known as IFOPT,
  • IFOPT and Transmodel V5.1 have been taken into account in the elaboration of the TS NeTEx (Network and Timetable Exchange),
  • Transmodel V5.1 with some supplementary requirements has been a building block of the EN  SIRI (System Interface for Real-time Information).

NeTEx and SIRI have extracted parts of Transmodel and extended them. These parts concern mainly the domain of Network Topology, Timing Information (timetables), Vehicle Scheduling, Operations Monitoring and Control.

Transmodel v5.1 concerns mainly the needs of urban bus, trolleybus, tramway and light rail, a lot of aspects of the metro for the following domains:

  • Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points
  • 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)
  • Management Information and Statistics (including data dedicated to service performance indicators).
  • Driver Management: Driver Scheduling (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).

It is applicable in the case of a multiple operators’ environment.

Transmodel v6 extends the data model to take into account heavy rail requirements. The data model is using the UML methodology, is modularised and the documentation splits into the following parts:

  • 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

By September 2014 Parts 1-2-3 have been issued.