Public transport - Network and Timetable Exchange (NeTEx) - Part 2: Public transport scheduled timetables exchange format

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V5.1 (EN 12986), IFOPT (CEN/TS 28701) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3 ) and supports information exchange of relevance to public transport services for passenger information and AVMS systems.
NOTE   Many NeTEx concepts are taken directly from Transmodel and IFOPT; the definitions and explanation of these concepts are extracted directly from the respective standards and reused in NeTEx, sometimes with further adaptions in order to fit the NETEx context.
The data exchanges targeted by NeTEx are predominantly oriented towards passenger information and also for data exchange between transit scheduling systems and AVMS (Automated Vehicle Monitoring Systems). However it is not restricted to these purposes, and NeTEx can provide an effective solution to many other use cases for transport exchange.
1.2   Transport modes
Most public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tram-way, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional provisions that apply especially to air transport.
1.3   Compatibility with existing standards and recommendations
The concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train com-position and facilities; planned passing times; timetable versions and validity conditions.
In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (European Rail Agency) – TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperability, entered into force on 13 May 2011 as the Commission Regulation (EU) No 454/2011), based on UIC directives.
As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (Netherland) and NOPTIS (Nordic Public Transport Interface Standard).
The data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation.

Öffentlicher Verkehr - Netzwerk- und Fahrplan-Austausch (NeTEx) - Teil 2: Austauschformat für Fahrpläne im öffentlichen Verkehr

Transport Public - Échanges des informations planifiées (NeTEx) - Partie 2: Description de l'offre de transport

Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 2. del: Izmenjavni format za vozne rede rednega javnega prevoza

General Information

Status
Published
Publication Date
09-Jun-2020
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
28-May-2020
Due Date
02-Aug-2020
Completion Date
10-Jun-2020

RELATIONS

Buy Standard

Technical specification
SIST-TS CEN/TS 16614-2:2020 - BARVE
English language
258 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 16614-2:2020
01-julij-2020
Nadomešča:
SIST-TS CEN/TS 16614-2:2014
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 2. del:
Izmenjavni format za vozne rede rednega javnega prevoza

Public transport - Network and Timetable Exchange (NeTEx) - Part 2: Public transport

scheduled timetables exchange format
Öffentlicher Verkehr - Netzwerk- und Fahrplan-Austausch (NeTEx) - Teil 2:
Austauschformat für Fahrpläne im öffentlichen Verkehr

Transport Public - Échanges des informations planifiées (NeTEx) - Partie 2: Description

de l'offre de transport
Ta slovenski standard je istoveten z: CEN/TS 16614-2:2020
ICS:
03.220.01 Transport na splošno Transport in general
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST-TS CEN/TS 16614-2:2020 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 16614-2:2020
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
May 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60 Supersedes CEN/TS 16614-2:2014
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 2: Public transport scheduled timetables
exchange format

Transport Public - Échanges des informations Öffentlicher Verkehr - Netzwerk- und Fahrplan-

planifiées (NeTEx) - Partie 2: Description de l'offre de Austausch (NeTEx) - Teil 2: Austauschformat für

transport Fahrpläne im öffentlichen Verkehr

This Technical Specification (CEN/TS) was approved by CEN on 2 March 2020 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to

submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS

available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in

parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,

Poland, Portugal, Republic of North Macedonia, Romania, Serbia, 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: Rue de la Science 23, B-1040 Brussels

© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16614-2:2020 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
Contents Page

European foreword........................................................................................................................................ 4

Introduction ..................................................................................................................................................... 5

1 Scope ..................................................................................................................................................... 6

1.1 General ................................................................................................................................................. 6

1.2 Transport modes .............................................................................................................................. 6

1.3 Compatibility with existing standards and recommendations ....................................... 6

2 Normative references ..................................................................................................................... 6

3 Terms and definitions .................................................................................................................... 6

4 Symbols and abbreviations .......................................................................................................... 7

5 Use Cases for Journey & Journey Time Exchange ................................................................. 7

6 Generic Physical Model and XSD mapping rules................................................................... 7

7 Timing Information – Conceptual and physical data model ............................................. 7

7.1 Introduction ....................................................................................................................................... 7

7.2 Journey and Journey Times – Model dependencies ............................................................. 8

7.3 Explicit Frames ................................................................................................................................. 9

7.3.1 Timetable Frame .............................................................................................................................. 9

7.4 Journey and Journey Times ........................................................................................................18

7.4.1 Vehicle Journey ...............................................................................................................................18

7.4.2 Vehicle Journey Assignment ......................................................................................................38

7.4.3 Service Journey ...............................................................................................................................45

7.4.4 Time Demand Times .....................................................................................................................68

7.4.5 Journey Timing ...............................................................................................................................78

7.4.6 Journey Pattern Times .................................................................................................................86

7.4.7 Vehicle Journey Times ..................................................................................................................94

7.4.8 Vehicle Journey Frequency ...................................................................................................... 101

7.4.9 Interchange ................................................................................................................................... 111

7.4.10 Interchange Rule ......................................................................................................................... 131

7.4.11 Coupled Journey .......................................................................................................................... 142

7.4.12 Flexible Service ............................................................................................................................ 163

7.4.13 Journey Accounting .................................................................................................................... 171

7.4.14 Dated Journey ............................................................................................................................... 175

7.4.15 Passing Times ............................................................................................................................... 181

7.4.16 Call .................................................................................................................................................... 189

7.4.17 Dated Call ....................................................................................................................................... 208

8 Vehicle Scheduling ...................................................................................................................... 210

8.1 Vehicle Scheduling – Model dependencies......................................................................... 210

8.2 Vehicle Scheduling ...................................................................................................................... 211

8.2.1 Vehicle Schedule Frame ............................................................................................................ 211

8.2.2 Vehicle Service ............................................................................................................................. 214

8.2.3 Train Service ................................................................................................................................. 227

Annex A (informative) Monitoring & Control .................................................................................. 232

A.1 Introduction .................................................................................................................................. 232

A.2 Monitoring & Control ................................................................................................................. 232

A.2.1 Monitored Vehicle Journey ...................................................................................................... 232

A.2.2 Dated Passing Times – Physical Model ................................................................................ 239

Annex B (informative) Driver Scheduling ......................................................................................... 244

---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)

B.1 Introduction ................................................................................................................................. 244

B.2 Driver Scheduling ....................................................................................................................... 244

B.2.1 Driver Schedule Frame ............................................................................................................. 244

B.2.2 Duty.................................................................................................................................................. 247

B.2.3 Duty Stretch .................................................................................................................................. 254

Annex C (informative) Changes in NeTEx Version 1.1 .................................................................. 257

C.1 Introduction ................................................................................................................................. 257

C.2 General Changes .......................................................................................................................... 257

C.3 List of changes .............................................................................................................................. 257

Bibliography ............................................................................................................................................... 258

---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
European foreword

This document (CEN/TS 16614-2:2020) has been prepared by Technical Committee CEN/TC 278

“Intelligent transport systems”, the secretariat of which is held by NEN.

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 supersedes CEN/TS 16614-2:2014.

This document presents Part 2 of the European Technical Specification known as “NeTEx”. NeTEx

provides a framework for specifying communications and data exchange protocols for organisa-

tions wishing to exchange scheduled Information relating to public transport operations.

NeTEx is made up of three parts defining a single European Standard, which provides a complete

exchange format for public transport networks, timetable description and fare information.

• Part 1 is the description of the public transport network topology exchange format. It also contains

use case shared with part 2, and modelling rules and the description of a framework shared by all

parts.
• Part 2 is the description of the scheduled timetables exchange format.
• Part 3 is the description of the fare information exchange format.
Part 1 is fully standalone, and Parts 2 and 3 rely on Part 1.

The XML schema can be downloaded from http://netex-cen.eu, along with available guidance on

its use, example XML files, and case studies of national and local deployments.

This document is highly technical, and a special care has been taken on keeping the text readable.

This has been done through a set of editorial rules enhancing usual CEN writing rules:

• To avoid confusion with usual wording, Transmodel terms are in capital letters (JOURNEY PAT-

TERN for example).

• To avoid confusion with usual wording, attributes names are in bold/italic style and use camelcase

style with no spaces (JourneyPattern for example).

• To avoid confusion with usual wording, attributes types are in italic style and use camelcase style

with no spaces (TypeOfEntity for example).

According to the CEN/CENELEC Internal Regulations, the national standards organisations of the

following countries are bound to announce this document: Austria, Belgium, Bulgaria, Croatia, Cy-

prus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ire-

land, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic

of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and

the United Kingdom.
---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
Introduction

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: set-

ting schedules and timetables; managing vehicle fleets; issuing tickets and receipts; providing real-time infor-

mation on service running, and so on.

This European Technical Specification specifies a Network and Timetable Exchange (NeTEx) about public

transport. It is intended to be used to exchange data relating to scheduled public transport between the systems

of PT organisations. It can also be seen as a complement to the SIRI (Service Interface for Real-time Information)

standard, as SIRI needs a prior exchange of reference data from NeTEx’s scope to provide the necessary context

for the subsequent exchange of a real-time data.

Well-defined, open interfaces have a crucial role in improving the economic and technical viability of public

transport Information Systems of all kinds. Using standardised interfaces, systems can be implemented as dis-

crete pluggable modules that can be chosen from a wide variety of suppliers in a competitive market, rather than

as monolithic proprietary systems from a single supplier. Interfaces also allow the systematic automated testing

of each functional module, vital for managing the complexity of increasing large and dynamic systems. Further-

more, individual functional modules can be replaced or evolved, without unexpected breakages of obscurely de-

pendent function.

This standard will improve a number of features of public transport information and service management: In-

teroperability – the standard will facilitate interoperability between information processing systems of the

transport operators by: (i) introducing common architectures for message exchange; (ii) introducing a modular

set of compatible information services for real-time vehicle information; (ii) using common data models and

schemas for the messages exchanged for each service; and (iv) introducing a consistent approach to data man-

agement.

Technical advantages include the following: reusing a common communication layer shared with SIRI for all the

various technical services enables cost-effective implementations, and makes the standard readily extensible in

future.
---------------------- Page: 7 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
1 Scope
1.1 General

NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Trans-

model V5.1 (EN 12986), IFOPT (CEN/TS 28701) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3 ) and sup-

ports information exchange of relevance to public transport services for passenger information and AVMS sys-

tems.

NOTE Many NeTEx concepts are taken directly from Transmodel and IFOPT; the definitions and explanation of these

concepts are extracted directly from the respective standards and reused in NeTEx, sometimes with further adaptions in

order to fit the NETEx context.

The data exchanges targeted by NeTEx are predominantly oriented towards passenger information and also for

data exchange between transit scheduling systems and AVMS (Automated Vehicle Monitoring Systems). How-

ever it is not restricted to these purposes, and NeTEx can provide an effective solution to many other use cases

for transport exchange.
1.2 Transport modes

Most public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry,

and their submodes. It is possible to describe airports and air journeys, but there has not been any specific con-

sideration of any additional provisions that apply especially to air transport.
1.3 Compatibility with existing standards and recommendations

The concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and

related organizations; stations and related equipment; journey coupling and journey parts; train composition

and facilities; planned passing times; timetable versions and validity conditions.

In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (Euro-

pean Rail Agency) – TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperabil-

ity, entered into force on 13 May 2011 as the Commission Regulation (EU) No 454/2011), based on UIC direc-

tives.

As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452

(Germany), NEPTUNE (France), UIC Leaflet, BISON (Netherland) and NOPTIS (Nordic Public Transport Interface

Standard).

The data exchange is possible either through dedicated web services, through data file exchanges, or using the

SIRI exchange protocol as described in part 2 of the SIRI documentation.
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.

CEN/TS 16614-1, Public transport — Network and Timetable Exchange (NeTEx) — Part 1: Public transport net-

work topology exchange format
3 Terms and definitions

For the purposes of this document, the terms and definitions given in CEN/TS 16614-1 apply.

Under preparation.
---------------------- Page: 8 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
4 Symbols and abbreviations

For the purposes of this document, the symbols and abbreviations given in CEN/TS 16614-1 apply.

5 Use Cases for Journey & Journey Time Exchange

NeTEx Part 2 shares its use cases with NeTEx Part 1 since many use cases involve both part 1 and part 2 entities.

Please refer to NeTEx Part 1 for a detailed use case description.
6 Generic Physical Model and XSD mapping rules

For consistency, the mapping rules for transforming a Conceptual Model to Physical Model and then to XSD are

shared between all parts of NeTEx.

Please refer to NeTEx Part 1 for a detailed description of the Physical Model and XSD mapping rules.

7 Timing Information – Conceptual and physical data model
7.1 Introduction

The NeTEx Part 2 timing information model is split into four main submodels defined as UML packages.

Figure 1 – NeTEx Part 2 main packages

The Journey and Journey Times model: describes the model planned services and dead runs and their timings

Figure 2 – JourneyAndJourneyTimes packages
• The dated journey model: describes the services for a single operating day
• The passing times model: describes all the different types of passing times

• The vehicle service model: describes the information related to vehicles and their services

---------------------- Page: 9 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
7.2 Journey and Journey Times – Model dependencies

The JOURNEY AND JOURNEY TIMES Model describes the VEHICLE JOURNEYs and other components making up

a timetable and is itself divided into a number of separate submodels covering different aspects of VEHICLE

JOURNEYs. For ease of understanding, the submodels are presented one at a time, each describing only a small

set of related concepts.

The submodels depend on a number of general NeTEx framework models and reusable components described

elsewhere (for example, the GENERIC POINT AND LINK model, NOTICE model, etc.,) – See NeTEx Part 1 for fur-

ther details.

The following figure shows the dependencies between the JOURNEY AND JOURNEY TIMES physical submodels.

The terminal packages contain the SERVICE FRAME and the TIMETABLE FRAME. These two VERSION FRAMEs

are containers that organise the other payload elements into a coherent set of elements suitable for exchange as

a serialised file. The payload elements are contained in the following packages:
TIMETABLE FRAME
• VEHICLE JOURNEY: models journeys that vehicles make.

• SERVICE JOURNEY: additionally models the properties of journeys that carry passengers.

• TIME DEMAND TIMEs: models the times of the different demand levels found during a day.

• PASSING TIMEs: describes the times of vehicles at points in their journey.
• JOURNEY TIMINGs: describes the common timing properties for journeys.
• JOURNEY PATTERN TIMEs: describes the timings of JOURNEY PATTERNs.
• VEHICLE JOURNEY TIMEs: describes the timings of VEHICLE JOURNEYs.
• INTERCHANGE: describes interchanges between journeys.
• COUPLED JOURNEY: describes multipart journeys which join and split.
• FLEXIBLE SERVICE: additional describes demand responsive transport services.
• JOURNEY ACCOUNTING: assigns a cost basis for journeys.
---------------------- Page: 10 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
pkg XSD NeTEx - Part 2 - Journey & Journey Times Model Dependencies
OC DeadRunCallModel
XSD NeTEx - Part 1 - Tactical Planning
TI InterchangeModel
TI InterchangeRuleModel
DeadRunCall
TP ServicePatternModel
TI ServiceJourneyModel
DeadRunArrival DefaultInterchange
InterchangeRule
TP StopAssignmentModel
DeadRunDeparture Interchange StopArea
GroupOfServices
InterchangeRuleParameter
ServiceJourneyInterchange StopAssignment ScheduledStopPoint
ServiceJourney DeadRunCallPart
InterchangeRuleTiming

SpecialService ServiceJourneyPatternInterchange PassengerStopAssignment ServiceLink

InterchangeTimes DynamicStopAssignment ServicePattern
TemplateServiceJourney
JourneyMeeting ServiceJourneyPattern
JourneyEndpoint
TI VehicleJourneyFrequencyModel
StopPointInJourneyPattern
JourneyFrequencyGroup
TP JourneyPatternModel Connection
HeadwayJourneyGroup
TypeOfStopPoint
JourneyPattern
TI JourneyTimingModel
RhythmicalJourneyGroup
OC CallModel
DeadRunPattern
VehicleJourneyHeadway
JourneyTiming
PointInJourneyPattern
Call
JourneyFrequency
JourneyRunTime
TimingPointInJourneyPattern
Arrival
JourneyWaitTime
TimingLinkInJourneyPattern
Departure
RC NoticeAssignmentModel
JourneyLayover
TypeOfJourneyPattern
OnwardServiceLinkView
JourneyHeadway
TI VehicleJourneyTimesModel NoticeAssignment
OnwardTimingLinkView
TurnaroundTimeLimit
TimingAlgorithm
CallPart
HeadwayInterval
VehicleJourneyLayover
TP TimeDemandTypeModel
VehicleJourneyRunTime
XSD NeTEx - Part 2 - Schedules and Versions
VehicleJourneyWaitTime TimeDemandType
TI CoupledJourneyModel
TI VehicleServiceModel
TimeDemandTypeAssignment
JourneyPart
Block TypeOfTimeDemandType
CoupledJourney
TI JourneyPatternTimesModel
BlockPart
JourneyPartCouple
JourneyPatternWaitTime CompoundBlock
JourneyPartPosition
JourneyPatternRunTime DatedBlock
PurposeOfJourneyPartition
XSD NeTEx - Part 1 - Network Description
NormalDatedBlock
JourneyPatternLayover
TypeOfCoupling
JourneyPatternHeadway CourseOfJourneys
ND RouteModel
VehicleTypePreference ReliefOpportunity
TI VehicleJourneyModel
VehicleService
ND FlexibleNetworkModel
Direction
Journey
VehicleServicePart
RoutePoint
FlexibleRoute
TI FlexibleServiceModel
VehicleJourney
TI TimeDemandTimesModel RouteLink
FlexibleLine
DeadRun
FlexibleServiceProperties
Route
FlexiblePointProperties
DefaultServiceJourneyRunTime
TemplateVehicleJourney
FlexibleStopAssignment
PointOnRoute
FlexibleLinkProperties
DefaultDeadRunRunTime
TrainNumber
TypeOfFlexibleService
TurnStation
TypeOfService
TypeOfProductCategory
XSD NeTEx RC Reusable Component
JourneyDesignator
Name: XSD NeTEx - Part 2 - Journey & Journey Times Model Dependencies
RC VehicleTypeModel
RC FacilityModel Author: NeTEx
Version: 1.0
Vehicle
FacilitySet
Created: 07/02/2010 22:30:50
VehicleDimensions
ServiceFacilitySet Updated: 12/08/2017 13:17:49
VehicleType
SiteFacilitySet
TI PassingTimesModel VehicleModel
RC ServiceRequirementModel
Accommodation
VehicleEquipmentProfile
PassingTime
Facility
VehicleRequirement
PassengerCapacity
TimetabledPassingTime
OnboardStay
ManoeuvringRequirement
PurposeOfEquipmentProfile
TypeOfFacility
PassengerCarryingRequirement
TypeOfFuel
FacilityList
FacilityRequirement
Figure 3 — Journey – Model Dependencies
7.3 Explicit Frames
7.3.1 Timetable Frame
7.3.1.1 TIMETABLE FRAME – Conceptual MODEL

The elements of the JOURNEY AND JOURNEY TIMES model can be grouped with a TIMETABLE FRAME which

holds a coherent set of timetable related elements for data exchange (see VERSION FRAME in the NeTEx Frame-

work section for general concepts relating to version frames).

The primary component exchanged by a TIMETABLE FRAME is a SERVICE JOURNEY, which describes an indi-

vidual journey. This and other components of a TIMETABLE FRAME are described in detail in the following sec-

tions.
---------------------- Page: 11 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
class NeTEx EF Timetable Frame MODEL
+defined for
Name: NeTEx EF Timetable Frame MODEL
CC Generic Validity MODEL:: TYPE OF VALUE
CC Generic Version MODEL::
Author: NeTEx
VALIDITY CONDITION
JT Vehicle Journey MODEL::
VERSION FRAME Version: 1.0
0..*
+restricted to TYPE OF SERVICE
Created: 23/05/2011 16:16:28
Updated: 06/12/2017 20:45:30
TYPE OF VALUE TYPE OF VALUE
RC Reusable Availability MODEL::
AVAILABILITY CONDITION JT Coupled Journey MODEL:: JT Coupled Journey MODEL::TYPE
PURPOSE OF JOURNEY OF COUPLING
CC Service Calendar Frame MODEL:: PARTITION
SERVICE CALENDAR FRAME
0..1
+take use of
+dated by 0..*
TIMETABLE FRAME
GROUP OF ENTITIES
GROUP OF ENTITIES
CG Generic Point & Link MODEL::
RC Notice MODEL::
JA Journey Accounting MODEL::
GROUP OF LINKS
JT Service Journey MODEL::
NOTICE
JOURNEY ACCOUNTING
GROUP OF SERVICES
GROUP OF ENTITIES
JT Vehicle Journey Times MODEL::
JOURNEY FREQUENCY GROUP
JT Coupled Journey MODEL::
JOURNEY PART COUPLE
JT Interchange MODEL::
0..1
+runs on
JOURNEY MEETING
+identified by
0..*
0..1 0..1
1..* +including
JOURNEY
+including
+valid for
as joining
JT Vehicle Journey MODEL::VEHICLE JOURNEY
as main
+composed of part
INTERCHANGE
+used by default by part
+made using 0..*
+identified by 0..*
JT Interchange MODEL::
0..* +subdivided in SERVICE JOURNEY
+identifying
INTERCHANGE
+identifying
TP Time Demand Type MODEL:: 0..1
0..*
TIME DEMAND TYPE
JT Vehicle Journey MODEL::
+for 1
TRAIN NUMBER
+used
INTERCHANGE
JT Service Journey MODEL::
+identifying 0..1 JT Interchange MODEL::
main
SERVICE JOURNEY
SERVICE JOURNEY PATTERN
part in 1
+identified by 0..* +joining 1
INTERCHANGE
0..*
+used to define 0..*
JT Coupled Journey MODEL::
JT Vehicle Journey MODEL::
JOURNEY PART
ASSIGNMENT
DEAD RUN
+part of
TP Time Demand Type MODEL::
TIME DEMAND TYPE
ASSIGNMENT
JT Vehicle Journey MODEL::
TEMPLATE VEHICLE JOURNEY
Figure 4 — Timetable Frame – Conceptual MODEL (UML)
---------------------- Page: 12 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
7.3.1.2 Timetable Frame – Physical Model
The following diagram gives an overview of the contents of a TIMETABLE FRAME.
Figure 5 — Timetable Frame Contents – Physical Model (UML)
---------------------- Page: 13 ----------------------
SIST-TS CEN/TS 16614-2:2020
CEN/TS 16614-2:2020 (E)
7.3.1.3 Timetable Frame Details – Physical Model
The following diagram shows the Physical model for a TIMETABLE FRAME.
class XSD NeTEx TI TP Timetable Frame Model
VersionFrame
DataManagedObject
0..1
RC ServiceCalendarFrameModel::ServiceCalendarFrame
+used in
RC ServiceCalendarModel::
+dating
Assignment
DayType ValidBetween
+dating
TP TimeDemandTypeModel:: +valid on 0..1
0..* RC AvailabilityConditionModel:: TypeOfValue
TimeDemandTypeAssignment
AvailabilityCondition
«Imp
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.