SIST EN 12896-3:2017

Intelligent transport systems - Reference data model - Part 3: Timing information and vehicle scheduling

1.1   General Scope of the Standard
The main objective of the present standard is to present the Reference Data Model for Public Transport, based on:
-   the Reference Data Model, EN12896, known as Transmodel V5.1,
-   CEN EN 28701, known as IFOPT,
incorporating the requirements  of
-   EN 15531-1 to -3 and TS 15531-4 and -5: Service interface for real-time information relating to public transport operations (SIRI),
-   TS 16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular,  the specific needs for long distance train operation.
A particular attention is drawn to the data model structure and methodology:
-   the data model is described in a modular form in order to facilitate the understanding and the 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 Transmodel V5.1 Network Description extended by the IFOPT relevant parts.
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)
-   Fare Management (fare structure, sales, validation, control)
-   Operations Monitoring and Control: operating day-related data, vehicle follow-up , control actions
-   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
The different functional domains taken into account in the present standard and of which the data have been represented as the reference data model are described in Public Transport Reference Data Model - Part 1: Common Concepts.
They are:
-   Public Transport Network and Stop Description
-   Timing Information and Vehicle scheduling
-   Passenger information
-   Fare Management
-   Operations monitoring and control
-   Management information
-   Personnel Management: Driver Scheduling, Rostering, Personnel Disposition.
The aspects of multi-modal operation and multiple operators’ environment are also taken into account.
1.3   Particular Scope of this Document
The present European Standard entitled Reference Data Model for Public Transport - Part 3: Timing Information and Vehicle Scheduling. incorporates
-   Journey and Journey Times Model: describes the time-related information at the level of vehicle journeys, i.e. planned timing for the vehicles at day-type level.
-   Dated Journey Model: describes the link of the timing information for a single operating day and the day type related timing,
-   Passing Times Model: describes all the different types of passing times for the day type related information,
-   Vehicle Service Model: describes the information related the work of vehicles as planned for days types. It constitutes the main part of the Vehicle Scheduling Data Domain.
-   Vehicle Journey Assignment Model: describes operational assignments (advertised vehicle labels, stopping positions) related to particular vehicle journeys.

Öffentlicher Verkehr - Datenreferenzmodell - Teil 3: Taktinformationen und Fahrzeugdisposition

Télématique du transport routier et de la circulation - Modèle de données de référence - Partie 3 : Informations horaires et horaires des véhicules

Inteligentni transportni sistemi - Referenčni podatkovni model - 3. del: Časovne informacije in razporejanje vozil

1.1 Splošno področje uporabe standarda
Glavni cilj trenutnega standarda je predstavitev referenčnega podatkovnega modela za javni prevoz na podlagi:
– referenčnega podatkovnega modela, standard EN12896, poznan kot Transmodel različice 5.1,
– standarda CEN EN 28701, poznan kot IFOPT,
vsebuje zahteve
-– standardov od EN 15531-1 do -3 ter TS 15531-4 in -5: Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza (SIRI),
– TS 16614-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)
– Upravljanje voznin (struktura voznin, prodaja, preverjanje, nadzor)
– Vodenje in nadzor: dnevni podatki o obratovanju, spremljanje vozil, nadzorni ukrepi
– 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«.
1.2 Opis funkcionalne domene
Različne funkcionalne domene, ki so upoštevane v trenutnem standardu in katerih podatki so predstavljeni kot referenčni podatkovni model, so opisane v Referenčnem podatkovnem modelu javnega prevoza – 1.del: Skupni koncepti.
To so:
– Opis omrežja javnega prevoza in postajališč
– Časovni razpored in razpored vozil
– Informacije o potnikih
– Upravljanje voznin
– Vodenje in nadzor
– Informacije o upravljanju
– Upravljanje osebja: razpored voznikov, urniki, razporejanje osebja.
Upoštevani so tudi vidiki multimodalnosti in okolja z večkratnimi operatorji.
1.3 Posebno področje uporabe tega dokumenta
Trenutni evropski standard »Referenčni podatkovni model za javni prevoz – 3. del: Časovni razpored in razpored vozil.« vključuje
– Model potovanj in časov potovanj: opisuje časovne informacije na ravni potovanj vozil, npr. načrtovane časovne razporede za vozila na dnevni ravni.
– Model potovanj z datumi: opisuje povezavo časovnega razporeda za posamezni obratovalni dan in dnevne časovne razporede,
– Model časov prehodov: opisuje vse različne vrste časov prehodov za dnevne informacije,
– Model storitev vozil: opisuje informacije, povezane z delom vozil, kot je načrtovano za posamezne dneve. Ta model je glavni del podatkovne domene razporeda vozil.
– Model dodelitve potovanja vozil: opisuje operativne dodelitve (oglaševane oznake vozil, postajališča), povezane s potovanji določenega vozila.

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-3:2016 - Public transport - Reference data model - Part 3: Timing information and vehicle scheduling

Relations

• 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-3:2017
01-januar-2017
1DGRPHãþD
SIST EN 12896:2006
,QWHOLJHQWQLWUDQVSRUWQLVLVWHPL5HIHUHQþQLSRGDWNRYQLPRGHOGHOýDVRYQH
LQIRUPDFLMHLQUD]SRUHMDQMHYR]LO
Intelligent transport systems - Reference data model - Part 3: Timing information and
vehicle scheduling
Öffentlicher Verkehr - Datenreferenzmodell - Teil 3: Taktinformationen und
Fahrzeugdisposition
Télématique du transport routier et de la circulation - Modèle de données de référence -
Partie 3 : Informations horaires et horaires des véhicules
Ta slovenski standard je istoveten z: EN 12896-3:2016
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 12896-3: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-3:2017

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

SIST EN 12896-3:2017


EN 12896-3
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 3: Timing
information and vehicle scheduling
Télématique du transport routier et de la circulation - Öffentlicher Verkehr - Datenreferenzmodell - Teil 3:
Modèle de données de référence - Partie 3 : Taktinformationen und Fahrzeugdisposition
Informations horaires et horaires des véhicules
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-3:2016 E
worldwide for CEN national Members.

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

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
1.1 General scope of the Standard . 5
1.2 Functional domain description . 6
1.3 Particular scope of this document . 6
2 Normative references . 7
3 Terms and definitions . 7
4 Symbols and abbreviations . 7
5 Timing information and vehicle scheduling data domain . 7
5.1 Introduction . 7
5.2 Overview . 8
5.2.1 Model and document structure . 8
5.3 Journey and journey times . 8
5.3.1 Vehicle journey . 8
5.3.2 Service journey . 11
5.3.3 Time demand times . 14
5.3.4 Journey timing . 16
5.3.5 Journey pattern times . 19
5.3.6 Vehicle journey times . 21
5.3.7 Interchange . 25
5.3.8 Interchange rule . 28
5.3.9 Coupled journey . 29
5.3.10 Flexible service . 36
5.3.11 Journey accounting . 38
5.4 Dated journey – Conceptual model . 39
5.5 Passing times . 40
5.5.1 Passing times . 40
5.6 Vehicle scheduling . 42
5.6.1 Tactical resource planning . 42
5.6.2 Resources for tactical planning . 43
5.6.3 Vehicle service . 43
5.7 Vehicle journey assignments . 49
5.7.1 Train component label assignment . 49
5.7.2 Stopping position assignment . 50
5.8 Explicit frames. 52
5.8.1 Timetable frame . 52
5.8.2 Vehicle schedule frame . 52
Bibliography . 85
2

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

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
European foreword
This document (EN 12896-3:2016) has been prepared by Technical Committee CEN/TC 278
“Transmodel”, 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-1:2016 and EN 12896-2:2016 supersedes
EN 12896:2006.
The series composed of 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 intends 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.
3

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

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
Introduction
EN 12896-3 presents the following items:
— rationale for the Transmodel Standard;
— use of the Transmodel Standard;
— applicability of the Transmodel Standard;
— conformance statement;
— Transmodel origins;
— reference to the previous version and other documents.
The data structures represented in EN 12896-1 are generic patterns that are referenced by different
other parts.
EN 12896-2 presents space-related data structures.
This European Standard presents time-related data structures and replaces the sections of
EN 12896:2006 referring to the time-related tactical planning components and to vehicle scheduling.
4

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

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
1 Scope
1.1 General scope of the Standard
The main objective of the present standard is to present the reference data model for public transport,
based on:
— the reference data model, EN 12896, known as Transmodel V5.1;
— EN 28701, known as IFOPT;
incorporating the requirements of:
— EN 15531-1 to −3 and CEN/TS 15531-4 and CEN/TS 15531-5, Service interface for real-time
information relating to public transport operations (SIRI);
— CEN/TS 16614-1 and CEN/TS 16614-2, Network and Timetable Exchange (NeTEx), in particular,
the specific needs for long distance train operation.
A particular attention is drawn to the data model structure and methodology:
— the data model is described in a modular form in order to facilitate the understanding and the 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 Transmodel V5.1 network description extended by the IFOPT relevant
parts.
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);
— fare management (fare structure, sales, validation, control);
— operations monitoring and control: operating day-related data, vehicle follow-up, control actions;
— 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).
5

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

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
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
The different functional domains taken into account in the present standard and of which the data have
been represented as the reference data model are described in “Public transport reference data model -
part 1: Common concepts”.
They are:
— public transport network and stop description;
— timing information and vehicle scheduling;
— passenger information;
— fare management;
— operations monitoring and control;
— management information;
— personnel management: driver scheduling, rostering, personnel disposition.
The aspects of multi-modal operation and multiple operators’ environment are also taken into account.
1.3 Particular scope of this document
The present European Standard entitled “Reference data model for public transport – Part 3: Timing
information and vehicle scheduling” incorporates:
— journey and journey times model: describes the time-related information at the level of vehicle
journeys, i.e. planned timing for the vehicles at day-type level;
— dated journey model: describes the link of the timing information for a single operating day and the
day type related timing;
— passing times model: describes all the different types of passing times for the day type related
information;
— vehicle service model: describes the information related the work of vehicles as planned for days
types. it constitutes the main part of the vehicle scheduling data domain;
— vehicle journey assignment model: describes operational assignments (advertised vehicle labels,
stopping positions) related to particular vehicle journeys.
This document itself is composed of the following parts:
— main document (normative) representing the data model;
— Annex A (normative), containing the data dictionary and attributes tables, i.e. the list of all the
concepts present in the main document together with the definitions;
— Annex B (informative), indicating the data model evolutions.
6

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

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
EN 12896-1:2016, Public transport - Reference data model - Part 1: Common concepts
3 Terms and definitions
For the purposes of this document, the terms and definitions given in EN 12896-1:2016 apply.
4 Symbols and abbreviations
AVM Automated vehicle monitoring
AVMS Automated vehicle management system
IFOPT Identification of fixed objects in public
transport
ISO International standards organization
IT Information technology
NeTEx Network and Timetable Exchange
PT Public transport
PTO Public transport operator
SIRI Service interface for real-time information
UML Unified modelling language
URI Uniform resource identifier
URL Universal resource locator
5 Timing information and vehicle scheduling data domain
5.1 Introduction
The work of the vehicles necessary to provide the service offer advertised to the public consists of
service journeys and dead runs (unproductive journeys are necessary to transfer vehicles where they
are needed, mainly from the depot into service and vice versa). Vehicle journeys are defined for day
types rather than individual operating days. A day type is a classification of all operating days for which
the same service offer has been planned. The whole tactical planning process is seen on the level of day
types in the reference data model, with all entities necessary to develop schedules. These include a
series of entities describing different types of run times and wait times, scheduled interchanges,
turnaround times etc.
Chaining vehicle journeys into blocks of vehicle operations, and cutting driver duties from the vehicle
blocks, are parts of the main functions of vehicle scheduling and driver scheduling, respectively. The
corresponding entities and relationships included in the reference data model allow a comprehensive
description of the data needs associated with this functionality, independently of the particular
methods and algorithms applied by the different software systems.
7

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

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
5.2 Overview
5.2.1 Model and document structure
The timing information model is splits into four main sub-models defined as UML packages.
— Journey and journey times model: describes the time-related information at the level of vehicle
journeys, i.e. planned timing for the vehicles at day-type level. It splits into:
— vehicle journey model;
— service journey model;
— time demand times model;
— journey timing model ;
— journey pattern times model;
— vehicle journey times model;
— interchange model;
— interchange rule model;
— coupled journey model;
— flexible service model;
— journey accounting model;
— dated journey model: describes the link of the timing information for a single operating day and the
day type related timing;
— passing times model: describes all the different types of passing times for the day type related
information;
— vehicle service model: describes the information related the work of vehicles as planned for days
types. It constitutes the main part of the vehicle scheduling data domain.
5.3 Journey and journey times
5.3.1 Vehicle journey
5.3.1.1 VEHICLE JOURNEY – Conceptual model
5.3.1.1.1 General
The daily operation of a vehicle is described by VEHICLE JOURNEYs. A VEHICLE JOURNEY is the defined
movement of a vehicle using a specified JOURNEY PATTERN on a particular ROUTE. This movement is
made between the first and the last POINTs IN JOURNEY PATTERN. Being defined for a DAY TYPE (cf.
[7]), a VEHICLE JOURNEY is a class of journeys that would take place at the same time on each day of a
specific DAY TYPE.
8

---------------------- Page: 10 ----------------------

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
5.3.1.1.2 Basic vehicle journey – Conceptual model
There are two different main types of VEHICLE JOURNEYs: passenger-carrying SERVICE JOURNEYs and
non-service DEAD RUNs.
— A SERVICE JOURNEY is a VEHICLE JOURNEY on which passengers will be allowed to board or alight
from vehicles at stops. These journeys are usually published and known by passengers.
— A DEAD RUN may be necessary for the vehicle to proceed from the PARKING POINT (cf. [7]) at
which it was parked to the first SCHEDULED STOP POINT of the JOURNEY PATTERN (cf. [8]) where
it will start its service operation. In the opposite direction, a DEAD RUN may relate the last
SCHEDULED STOP POINT the vehicle has stopped at (finishing its service) to the PARKING POINT
where it will be parked. A DEAD RUN may also occur when a vehicle changes from one ROUTE (cf.
[8]) to another one in order to continue its service there, or for various other reasons.
class TI JT Vehicle Journey Basic MODEL
Name: TI JT Vehicle Journey Basic MODEL
Author: Transmodel
Version: 1.0
JOURNEY
Created: 05/02/2014 11:25:26
Updated: 03/09/2014 13:30:15 + Description [0.1]
+ TransportMode [0.1]
CC Service
+ TransportSubmode [0.1]
Calendar MODEL::
+ Monitored [0.1]
DAY TYPE
+for
«UID»
1.*
+ Id
+worked on *
LINK SEQUENCE
VEHICLE JOURNEY
+for +made using
NT Journey Pattern
+ DepartureTime [0.1]
MODEL::JOURNEY
1 *
+ JourneyDuration [0.1]
PATTERN
«UID»
+ Id
0.1
+by default
timed from
+timed from 0.*
+the timing
+the timing
0.1
reference for
reference for 1
POINT IN LINK SEQUENCE
NT Journey Pattern MODEL:: DEAD RUN
TIMING POINT IN JOURNEY
TI Service
+ DirectionType [0.1]
PATTERN
Journey MODEL::
+ DeadRunType [0.1]
SERVICE
«UID»
+a view of *
JOURNEY
+ Id
+viewed as 1
POINT
NT Timing Pattern
MODEL::TIMING
POINT

Figure 1 — Vehicle journey – Basic conceptual model (UML)
5.3.1.1.3 Vehicle journey details – Conceptual model
A VEHICLE JOURNEY may be further defined by a number of other elements, as shown in Figure 2.
These include interactions with other journeys (JOURNEY PART, JOURNEY MEETING, etc.); temporal
and other conditions (DAY TYPE, VALIDITY CONDITION, cf. [7]); further descriptive and classification
9

---------------------- Page: 11 ----------------------

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
information (TRAIN NUMBER, PRODUCT CATEGORY, TYPE OF SERVICE, stops etc,); and operational
data (BLOCK).
A TEMPLATE JOURNEY allows a set of VEHICLE JOURNEYs to be defined that follow a common
temporal pattern.
class TI JT Vehicle Journey MODEL
CC Generic Accessibility
+including 0.* +part of 0.*
LINK SEQUENCE
+by default
MODEL::ACCESSIBILITY
POINT IN LINK SEQUENCE
1 timed from NT Journey Pattern MODEL::JOURNEY PATTERN
ASSESSMENT +determining
CC Generic Validity
NT Journey Pattern MODEL::
MODEL::VALIDITY
TIMING POINT IN JOURNEY +the timing
0.1 0.* 0.*
CONDITION
PATTERN reference for
+determined
+characterised +characterising 0.1
+for 1 0.*
by
by
+the timing reference for 0.1
+applicable for 0.*
0.*
+characterising
+characterised by 0.1
CC Transport
JOURNEY +characterised by
0.1
Organisations
+ Description [0.1]
MODEL::
CC Service Calendar
+ TransportMode [0.1]
OPERATIONAL +the classification for
MODEL::DAY TYPE
CONTEXT + TransportSubmode [0.1]
+for
+ Monitored [0.1] * +classified as 0.1 TYPE OF SERVICE
«UID»
+characterising 0.1
1.*
«UID»
+ Id
+for 1.* +timed
+made
+ Id
+worked
from
* using +characterised by
0.* 0.* 0.*
on *
+classified as
+worked on *
VEHICLE JOURNEY
+including +in
TI Vehicle Service + DepartureTime [0.1]
0.1
MODEL::BLOCK 0.1 *
+ JourneyDuration [0.1]
TYPE OF PRODUCT
+subdivided in +a classification for
«UID» CATEGORY
+ Id
1
«UID»
0.* +identified by
+ Id
+part
of
TI Coupled Journey
*
MODEL::JOURNEY
+identifying
TEMPLATE VEHICLE
PART
0.*
JOURNEY
+identified by 0.1
TRAIN NUMBER
0.* +identifying
«UID»
+made using 0.1
+ Id
+ ForAdvertisement [0.1]
DEAD RUN
TI Service Journey
+ ForProduction [0.1]
MODEL::SERVICE
+ DirectionType [0.1]
+ Description [0.1]
JOURNEY
+ DeadRunType [0.1]
+for 0.*
«UID»
+ Id «UID»
FACILITY SET
+ Id
0.1
CC Facility MODEL: Name: TI JT Vehicle Journey MODEL
:SERVICE FACILITY Author: Transmodel
+for
Version: 1.0
SET
+made using
Created: 05/02/2014 11:25:26
0.*
+comprising Updated: 21/09/2014 09:33:30
0.1
TI Service Journey
+part of 1.*
MODEL::TEMPLATE
SERVICE JOURNEY
CC Facility
MODEL::
FACILITY

Figure 2 — Vehicle journey – conceptual model (UML)
5.3.1.2 Vehicle journey notice assignment
For passenger information (or sometimes driver information) purposes, it is often useful to attach
remarks to various parts of the supply (a point, a line, a section, etc.). For instance, the fact that a
shortened journey pattern is used exceptionally may be emphasized. Such remarks are usually printed
as footnotes on public timetables at stops, timetable booklets or, for driver information, on driver cards.
The entity NOTICE (cf. [7]). describes such remarks. It may concern a whole LINE, or a GROUP OF
POINTS, e.g. one or several STOP AREAs.
More frequently, a NOTICE will be assigned to a JOURNEY PATTERN, a COMMON SECTION (cf. [8]), or
even a specific VEHICLE JOURNEY. In such a case, the same NOTICE often will be assigned to several
objects (e.g. to several consecutive VEHICLE JOURNEYs).
Moreover, the validity of a NOTICE, for instance on a JOURNEY PATTERN or a COMMON SECTION, may
be restricted from a POINT IN JOURNEY PATTERN, or to another POINT IN JOURNEY PATTERN.
10

---------------------- Page: 12 ----------------------

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
The entity NOTICE ASSIGNMENT (cf. [8]) describes these spatial or operational assignments. Only the
most frequent assignments are represented in the model. Other may be added using the same
construction.
A NOTICE ASSIGNMENT may be subject to various other conditions of validity (such as DAY TYPE, TIME
BAND), represented by VALIDITY CONDITIONs.
A NOTICE has a different meaning than a DESTINATION DISPLAY (cf. [8]). The first is designed to
specify some characteristics of a journey or a journey pattern which are likely to evolve. They are in
most cases printed in leaflets, but may also be queried by dynamic trip planning tools. A DESTINATION
DISPLAY corresponds to stable information attached to a JOURNEY PATTERN, for instance the
destination announcement displayed on bus headsigns.
class TI JT Vehicle Journey Notice Assignment MODEL
Name: TI JT Vehicle Journey Notice Assignment MODEL
POINT IN LINK SEQUENCE
Author: Transmodel
LINK SEQUENCE NT Journey Pattern MODEL::
Version: 1.0
+made up of
+on POINT IN JOURNEY
NT Journey Pattern MODEL::
Created: 17/02/2014 18:30:19
PATTERN
JOURNEY PATTERN
Updated: 03/09/2014 13:35:40
1 1.*
+part of 0.*
+including 0.*
+used to +for +marked
1.* 1
0.1
0.1
define by +end 0.1 +start of
CC Generic Validity
of MODEL::VALIDITY
+applicable for
CONDITION
+defined
0.*
for
* +made using
+assigned
+applicable for *
+from
to *
* +to * *
JOURNEY
TI Vehicle Journey MODEL::
0.1
+assigned to NT Notice Assignment MODEL::NOTICE
VEHICLE JOURNEY
ASSIGNMENT +defined for *
*
+marked by
+ DepartureTime [0.1]
+assigned by +marked by
+ JourneyDuration [0.1] TI Interchange
+assigned to
MODEL::
«UID»
0.* 0.1
INTERCHANGE
+ Id
0.*
+assigned * +using *
to
+marked by
+used by 1
TI Service Journey
MODEL::GROUP OF 0.1
CC Notice MODEL::
+a classification for
0.*
SERVICES
CC Notice MODEL::
TYPE OF NOTICE
NOTICE
+classified as 0.1
+marked
+defined 0.1
by
1
for
NT Common Section MODEL::
+provided as
+providing 0.*
0.*
COMMON SECTION
CC Notice MODEL:: CC Notice MODEL::
0.1
+classiifed as
DELIVERY VARIANT TYPE OF DELIVERY
VARIANT
0.*
+a classification for

Figure 3 — Vehicle journey notice assignment – Conceptual model (UML)
5.3.2 Service journey
5.3.2.1 SERVICE JOURNEY – Conceptual model
A SERVICE JOURNEY is a VEHICLE JOURNEY on which passengers will be allowed to board or alight
from vehicles at stops. There are several different possible ways to define SERVICE JOURNEYs, in
particular the two following:
— as the service between an origin and a destination, as advertised to the public;
— as the longest service during which a passenger is allowed to stay on the same vehicle.
11

---------------------- Page: 13 ----------------------

SIST EN 12896-3:2017
EN 12896-3:2016 (E)
class TI JT Basic Service Journey MODEL
TI Vehicle Journey
TI Vehicle Journey
* +the classification for MODEL::TYPE OF
MODEL::JOURNEY
SERVICE
+classified as
0.1
GROUP OF SERVICES
+made up of
1.*
...