SIST EN 12896-1:2017

Public transport - Reference data model - Part 1: Common concepts

1.1   General scope of the Standard
The main objective of the present standard is to present the Public Transport Reference Data Model based on:
-   the Public Transport Reference Data Model published 2006 as EN12896 and known as Transmodel V5.1,
-   the model for the Identification of Fixed Objects for Public transport, published 2009 as EN 28701and known as IFOPT,
incorporating the requirements  of
-   EN15531-1 to 3 and TS15531-4 and 5: Service interface for real-time information relating to public transport operations (SIRI),
-   TS16614-1 and 2: Network and Timetable Exchange (NeTEx),
in particular the specific needs for long distance train operation.
Particular attention is drawn to the data model structure and methodology:
-   the data model is described in a modular form in order to facilitate understanding and use of the model,
-   the data model is entirely described in UML.
In particular, a Reference Data Model kernel is described, referring to the data domain:
-   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.
Furthermore, the following functional domains are considered:
-   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).  
The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called Common Concepts.
1.2   Functional domain description
1.2.1   Public transport network and stop description
The reference data model includes entity definitions for different types of points and links as the building elements of the topological network. Stop points, timing points and route points, for instance, reflect the different roles one point may have in the network definition: whether it is used for the definition of (topological or geographical) routes, as a point served by vehicles when operating on a line, or as a location against which timing information like departure, passing, or wait times are stored in order to construct the timetables.
The line network is the fundamental infrastructure for the service offer, to be provided in the form of vehicle journeys which passengers may use for their trips. The main entities describing the line network in the reference data model are the line, the route and the journey pattern, which refer to the concepts of an identified service offer to the public, the possible variants of itineraries vehicles would follow when serving the line, and the (possibly different) successions of stop points served by the vehicles when operating on the route.
The functional views of the network are described as layers. A projection is a mechanism enabling the description of the correspondence between the different layers. This mapping between the layers is particularly useful when spatial data from different environments (sources, functional domains) have to be combined. An example of such a situation is the mapping of the public transport network on the road network.

Öffentlicher Verkehr - Datenreferenzmodell - Teil 1: Gemeinsame Konzepte

Transports publics - Modèle de données de référence - Partie 1: Concepts communs

Javni prevoz - Referenčni podatkovni model - 1. del: Splošni pojmi

Glavni cilj trenutnega standarda je predstavitev referenčnega podatkovnega modela javnega prevoza na podlagi:
– referenčnega podatkovnega modela javnega prevoza, objavljenega leta 2006 kot standard EN12896 in poznanega kot Transmodel različice 5.1,
– modela za identifikacijo stalnih modelov za javni prevoz, objavljenega leta 2009 kot standard EN 28701 in poznanega kot IFOPT, in vsebuje zahteve
– standardov od EN15531-1 do 3 ter TS15531-4 in 5: Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza (SIRI),
– standardov TS16614-1 in 2: Izmenjava omrežnih in voznorednih podatkov (NeTEx), predvsem specifične potrebe za obratovanje vlaka med kraji.
Posebna pozornost je namenjena strukturi podatkovnega modela in metodologiji:
– podatkovni model je opisan v modularni obliki za lažje razumevanje in uporabo modela,
– podatkovni model je v celoti opisan v UML.
Opisano je zlasti jedro referenčnega podatkovnega modela, ki se nanaša na podatkovno domeno:
– Opis omrežja: poti, linije, vzorci potovanj, časi potovanj, storitveni vzorci in načrtovana postajališča.
Ta del ustreza opisu omrežja v Transmodelu različice 5.1 in je razširjen z relevantnimi deli IFOPT.
Poleg tega so obravnavane naslednje funkcionalne domene:
– Časovni razpored in razpored vozil (vozni časi, poti vozil, dnevni razporedi vozil)  
– Informacije o potnikih (načrtovane in v realnem času)
– Vodenje in nadzor: dnevni podatki o obratovanju, spremljanje vozil, nadzorni ukrepi
– Upravljanje voznin (struktura voznin in pravice za dostop, prodaja, preverjanje, nadzor)
– Informacije o upravljanju in statistika (vključno s podatki, namenjenimi kazalcem uspešnosti storitev).
– Upravljanje voznikov:
– Razpored voznikov (dnevni razporedi voznikov),
– Urniki (razporejanje dolžnosti voznikov v zaporedje glede na nekatere izbrane metode),
– Razporejanje voznega osebja (dodelitev logičnih voznikov fizičnim voznikom in beleženje storilnosti voznika).  
Določeni bodo podatkovni modeli, ki bodo zajemali večino funkcij iz zgornjih domen. Različne funkcionalne domene imajo skupnih več konceptov. Ta podatkovna domena se imenuje Skupni koncepti.

General Information

• Status: Published
• Public Enquiry End Date: 01-Jul-2015
• Publication Date: 13-Nov-2016
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ITC - Information technology
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 04-Oct-2016
• Due Date: 09-Dec-2016
• Completion Date: 14-Nov-2016
• Ref Project: EN 12896-1:2016 - Public transport - Reference data model - Part 1: Common concepts

Relations

• Revised: SIST EN 12896:2006 - Road transport and traffic telematics - Public transport - Reference data model
• Effective Date: 16-Oct-2013
• Replaces: SIST EN 12896:2006 - Road transport and traffic telematics - Public transport - Reference data model
• Effective Date: 30-Sep-2016
• Replaces: SIST EN 12896:2006 - Road transport and traffic telematics - Public transport - Reference data model
• Effective Date: 08-Jun-2022

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 12896-1:2017
01-januar-2017
1DGRPHãþD
SIST EN 12896:2006
-DYQLSUHYR]5HIHUHQþQLSRGDWNRYQLPRGHOGHO6SORãQLSRMPL
Public transport - Reference data model - Part 1: Common concepts
Öffentlicher Verkehr - Datenreferenzmodell - Teil 1: Gemeinsame Konzepte
Transports publics - Modèle de données de référence - Partie 1: Concepts communs
Ta slovenski standard je istoveten z: EN 12896-1:2016
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 12896-1:2017 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN 12896-1:2017

---------------------- Page: 2 ----------------------

SIST EN 12896-1:2017


EN 12896-1
EUROPEAN STANDARD

NORME EUROPÉENNE

September 2016
EUROPÄISCHE NORM
ICS 35.240.60 Supersedes EN 12896:2006
English Version

Public transport - Reference data model - Part 1: Common
concepts
Transports publics - Modèle de données de référence - Öffentlicher Verkehr - Datenreferenzmodell - Teil 1:
Partie 1: Concepts communs Gemeinsame Konzepte
This European Standard was approved by CEN on 5 May 2016.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.





EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2016 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 12896-1:2016 E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST EN 12896-1:2017
EN 12896-1:2016 (E)
Contents Page
European foreword . 5
0 Introduction . 6
0.1 Rationale for the Transmodel Standard . 6
0.2 Use of the Transmodel Standard . 6
0.3 Applicability of the Transmodel Standard . 7
0.3.1 General . 7
0.3.2 Specification of information architecture . 7
0.3.3 Specification of a database. 8
0.3.4 Specification of an interface . 8
0.4 Conformance statement . 8
0.5 Transmodel origins . 9
0.5.1 ENV 12896 . 9
0.5.2 Titan . 9
0.5.3 SITP and SITP2 . 9
0.5.4 CEN TC 278 WG 3 SG 4 . 9
0.6 Reference to the previous version and other projects and documents. 10
0.6.1 General . 10
0.6.2 SIRI . 10
0.6.3 IFOPT . 10
0.6.4 NeTEx . 10
0.7 Typographic conventions . 10
0.8 Methodology for conceptual modelling . 11
0.8.1 General . 11
0.8.2 Packages . 11
0.8.3 Class diagrams . 13
0.8.4 Classes and attributes . 14
0.8.5 Association relationships . 17
0.8.6 Reflexive association relationship . 17
0.8.7 Composition association relationship . 18
0.8.8 Aggregation association relationship . 18
0.8.9 Generalization association relationship . 19
0.9 Summary of rules for Transmodel representation . 19
1 Scope . 21
1.1 General scope of the Standard . 21
1.2 Functional domain description . 22
1.2.1 Public transport network and stop description. 22
1.2.2 Timing information and vehicle scheduling. 22
1.2.3 Passenger information . 23
1.2.4 Fare management . 23
1.2.5 Operations monitoring and control . 24
1.2.6 Management information . 24
1.2.7 Multi-modal operation aspects . 25
1.2.8 Multiple operators' environment aspects . 25
1.2.9 Personnel management: driver scheduling, rostering, personnel disposition . 25
1.3 Particular scope of this document . 26
2

---------------------- Page: 4 ----------------------

SIST EN 12896-1:2017
EN 12896-1:2016 (E)
2 Normative references . 26
3 Terms and definitions . 26
4 Abbreviations . 29
5 Common concepts domain . 29
5.1 Introduction to the common concepts . 29
5.2 Versions and validity . 31
5.2.1 Introduction. 31
5.2.2 Version and validity – Model overview . 32
5.2.3 Generic entity . 32
5.2.4 Generic version. 33
5.2.5 Generic version frame . 34
5.2.6 Generic validity . 36
5.2.7 Generic delta model . 37
5.3 Responsibility . 38
5.3.1 Introduction. 38
5.3.2 Responsibility – Model overview . 39
5.3.3 Generic responsibility . 39
5.3.4 Responsibility role . 41
5.3.5 Generic organization . 42
5.4 Explicit frames . 43
5.4.1 Composite frame . 44
5.4.2 General frame . 45
5.4.3 Resource frame. 46
5.4.4 Service calendar frame . 47
5.4.5 Other explicit frames . 48
5.5 Generic framework model. 49
5.5.1 General . 49
5.5.2 Generic framework – Model overview . 49
5.5.3 Location Model . 49
5.5.4 Generic grouping - Introduction . 50
5.5.5 Generic point and link. 52
5.5.6 Generic point and link sequence . 55
5.5.7 Generic zone and feature . 56
5.5.8 Generic projection . 58
5.5.9 Generic place . 63
5.5.10 Accessibility . 64
5.6 Reusable Components . 67
5.6.1 General . 67
5.6.2 Reusable components – Model overview . 67
5.6.3 Transport Mode . 68
5.6.4 Transport Submode . 69
5.6.5 Service calendar . 69
5.6.6 Availability condition . 71
5.6.7 Topographic place . 72
5.6.8 Transport organizations . 73
5.6.9 Additional organizations . 74
5.6.10 Generic equipment . 76
5.6.11 Vehicle type . 78
5.6.12 Actual vehicle equipment . 79
5.6.13 Vehicle passenger equipment . 80
5.6.14 Facility . 81
3

---------------------- Page: 5 ----------------------

SIST EN 12896-1:2017
EN 12896-1:2016 (E)
5.6.15 Train . 82
5.6.16 Schematic map . 85
5.6.17 Notice . 86
5.6.18 Service restriction . 87
5.6.19 Alternative name . 88
Bibliography . 132

4

---------------------- Page: 6 ----------------------

SIST EN 12896-1:2017
EN 12896-1:2016 (E)
European foreword
This document (EN 12896-1:2016) has been prepared by Technical Committee CEN/TC 278 “Intelligent
transport systems”, the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by March 2017, and conflicting national standards shall
be withdrawn at the latest by March 2017.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document together with documents EN 12896-2:2016 and EN 12896-3:2016 supersedes
EN 12896:2006.
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 create version 6 of the European Standard EN 12896, known as “Transmodel” and thus
replace Transmodel V5.1.
The split into several documents is intended to ease the task of users interested in particular functional
domains. Modularisation of Transmodel undertaken within the NeTEx project has contributed
significantly to this new edition of Transmodel.
In addition to the eight Parts of this European Standard an informative Technical Report (Public
Transport – Reference Data Model – Informative Documentation) is also being prepared to provide
additional information to help those implementing projects involving the use of Transmodel. It is
intended that this Technical Report will be extended and republished as all the eight parts are
completed.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.
5

---------------------- Page: 7 ----------------------

SIST EN 12896-1:2017
EN 12896-1:2016 (E)
0 Introduction
0.1 Rationale for the Transmodel Standard
Public transport services rely increasingly on information systems to ensure reliable, efficient operation
and widely accessible, accurate passenger information. These systems are used for a range of specific
purposes: setting schedules and timetables, managing vehicle fleets, issuing tickets and receipts,
providing real time information on service running, and so on.
This standard will improve a number of features of public transport information and service
management: in particular, the standard will facilitate interoperability between information processing
systems of the transport operators and agencies by using similar definitions, structures and meanings
for their data for the systems being part of one solution. This applies both to connecting different
applications within an organization, and also to connecting applications between interworking
organizations (for instance, a public authority and a transport operator).
The Transmodel standard presented in this European Standard provides a framework for defining and
agreeing data models, and covers the whole area of public transport operations. By making use of this
European Standard, and of data models derived from it, it will be possible for operators, authorities and
software suppliers to work together much more easily towards integrated systems. Moreover, the
breadth of the standard will help to ensure that future systems’ developments can be accommodated
with the minimum of difficulty.
0.2 Use of the Transmodel Standard
This European Standard presents version 6.0 of the European Standard EN 12896, known as
“Transmodel”. Transmodel 6.0 is a reference standard which provides a conceptual data model for use
by organizations with an interest in information systems for the public transport industry.
As a reference standard, it is not necessary for individual systems or specifications to implement
Transmodel as a whole.
It needs to be 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 prove of value to:
— organizations within the public transport industry that specify, acquire and operate information
systems;
— organizations that design, develop and supply information systems for the public transport
industry.
For an organization within the public transport industry wishing to specify, acquire and operate
information systems, Transmodel may be distilled, refined, or adapted to form a comprehensive data
model for the organization. This will enable the organization 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. The organization also has a greater likelihood that information exchange interfaces with external
organizations will be easily achieved.
For an organization wishing to design, develop and supply information systems for the public transport
industry, Transmodel may be distilled, refined, or adapted to form a comprehensive data model for the
product suite. This will enable the organization to develop its products in such a way that separate
6

---------------------- Page: 8 ----------------------

SIST EN 12896-1:2017
EN 12896-1:2016 (E)
modules will integrate easily, but also so that they may be sold separately to clients seeking
Transmodel-compliant systems.
Transmodel is a large and complex model, and allows for great flexibility. Consequently it takes some
skills and resource to apply it effectively in order to develop the physical data model and its
implementations for a particular aspect, e.g. one particular functional domain, such as vehicle
scheduling or fare management or for a particular interface, as between a ticket machine and a
management system, or a particular organizational boundary, as between two connecting transport
operators.
For such situations, Transmodel provides a wider setting and a starting point. The specific elements of
Transmodel have to be refined, attributes and data formats will have to be completed, for a specific sub-
model of the Transmodel data model. The resulting specification, although specific, will facilitate the
built of a coherent overall systems framework, since it will coexist more readily with other Transmodel-
based specifications.
For all of these potential users, the adoption of Transmodel as a basis for development means that a
common language is being used. Thus, users will understand and assess the claims of suppliers better,
and specification developers will be more likely to be working in alignment with each other.
0.3 Applicability of the Transmodel Standard
0.3.1 General
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 organization’s ‘information architecture’;
— specification of a database;
— specification of a data exchange interface.
0.3.2 Specification of information architecture
An ‘information architecture’ refers to the overall structure of information used by an information
system, which is used to determine:
— the structure of data held in system databases;
— the structure of data exchanged across interfaces between systems.
It may be used as a strategic guide to system planning and evolution, and as the basis for the
specification and acquisition of individual systems.
An information architecture made up of independent modules with well-defined interfaces is easier to
maintain. A malfunctioning module can be taken out of service or completely replaced without
disrupting the rest of the system. This is particularly beneficial for online or safety critical systems. The
modules can also be more easily reconfigured on to hardware located elsewhere on the network to fit in
with changes in organizational arrangements for managing the business and data administration
processes.
The information architecture itself should be evaluated from time to time to make sure that it is still
meeting the needs of the organization. Technological changes in communications and computing are
continuously bringing forward new opportunities for evolving the systems supporting the business.
7

---------------------- Page: 9 ----------------------

SIST EN 12896-1:2017
EN 12896-1:2016 (E)
0.3.3 Specification of a database
At a more technical level, an organization’s systems will have a collection of data in one or more
databases, which may be associated with individual applications or may be common to many
applications.
In either case, 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.
Technical constraints (such as memory capacity restrictions of smart cards) may affect the detail and
complexity of the data models that can be used in particular data storage devices. Transmodel does not
itself specify a level of detail to adopt.
0.3.4 Specification of an interface
Public transport organizations may require different applications to exchange data with each other.
Also, public transport organizations may exchange data with other organizations. In either case, the
reference data model can be used to help des
...