Using the CEN
NeTEx Standard
to represent basic
Rail fare data
- Briefing Report for the UIC
10 June 2014. UIC Paris
Nicholas Knowles
njsk
Contents
• Introduction,
• Motivation, Process, Methodology
• NeTEx Functional Scope
• Demonstration of UML & XML tools
• Rail Mappings
• Mapping Methodology
• B1, B2, B3 Mapping
• Summary Comments
njsk
NeTEx - CEN Standard
• XML standard for exchanging Public
•
Transport data – primarily for passenger
information systems
Deliverables
• CEN Specification Documents
• Part 1 – Network (Stops, routes etc)
• Part 2 - Timetables
• Part 3 – Fares
• UML Models
• XML Schema & Examples
njsk
CEN TC278 Working Groups
CEN / TC278
Road Transport & Traffic Telematic
Plenary
Chair:
WG1, Electronic Fee
Collection
WG7, Geographic Road
Data
WG12, AutoVehicle and
Equipment Ident
WG3, Public Transport
WG8, Road Traffic Data
WG13, Architecture &
Terminology
WG4, Traffic and Traveller
Information
WG9, Dedicated Short
Range Communications
WG14, Recovery of Stolen
Vehicles
WG5, Traffic Management
WG10, Human-Machine
Interfaces
WG15, eSaftey
njsk
CEN TC278 WG3 Sub-groups
CEN / TC278
/ WG 3
Public Transport
Plenary
SG1
Chair:
SG 3
Data Communication on
Vehicles
SG 4
Passenger Information
SG 5
Datamodel– Transmodel
SG 6
Interoperable Fare
Management
SG 7
Identification of fixed
Objects in PT
SG 9
SG 8
Distributed Journey
Planning
Service Interfaces Real
Time Information
Netex
njsk
CEN Process
• Multi country participation organised
through national standards bodies
• Open review and voting process
• Draft, comment, revise, vote
• Build on existing standards
• Time limitations to complete and to review
• Different tracks - Full Standard vs
Technical Specification
njsk
Evolving a Concrete PT Timetable schema
Transmodel
Transmodel
Transmodel
Transmodel
Trident
VDV452
TransXChange,
etc
Bison, Noptis,
etc
CEN
NeTEx
1.0
Part1
CEN
NeTEx
1.0
Part2
CEN
NeTEx
1.0
Part3
IFOPT
NaPTAN,
etc
Examples
SIRI
FareXChange
UIC Rail
Timetables
TAP TSI,
Rail Fares
7
njsk
Why? - Business Drivers
•
European data exchange standards
•
•
•
Reducing costs
• Shared markets, wide tool base, reusable components
• Common specifications for procurement and exchange
• Makes data costs viable for new functions
Managing Complexity
• Simplified, uniform solutions
• Harnesses know-how & best practice
Increasing Capability
• Enables Advanced function, especially electronic delivery
– Passenger information, ticketing
• Large scale coverage, multimodal
• More powerful representations & functions
• Interoperability
8
njsk
Why ? - Political Drivers
• Passenger rights
• Objective, timely information, cross-modal
– E.g. EU ITS action plan.
• Accessibility
• Sustainability / Green
• Encourage use of PT
• Make use of PT capacity efficient (ITS)
• E-ticketing enables more passengers on urban systems
• Harmonisation
• Free flow of data and system use between regions
9
njsk
NeTEx / Transmodel
Methodology
10
njsk
Models – Levels of Abstraction
•
•
Conceptual model is implementation
independent
• Transmodel based, modular UMLConceptual &
Physical Models
Conceptual model may have multiple
physical models for different target
implementations.
• NeTEx Physical design for XML as
modular UML Model
Implementation is derived from
physical model
• Eg. XML, DDL etc
• NeTEx XML Schema
CONCEPTUAL MODEL
(UML
PHYSICAL MODEL
For Java
PHYSICAL MODEL for DDL
PHYSICAL MODEL UML
For XML
•
IMPLEMENTATION MODEL
(Java)
IMPLEMENTATION MODEL
(DDL)
IMPLEMENTATION MODEL
(XML)
12
njsk
Conceptual vs Concrete Levels; Model Driven Design,
1. NeTEx /Transmodel Conceptual Model - UML
NeTEx Framework
VERSION, VERSION FRAME
Packages
UML Transmodel PT Concepts – NeTEx submodel
POINTS, LINKS, STOP POINTS, ROUTES, ROUTE LINKS,
JOURNEY PATTERNS, JOURNEYs, etc, etc
Packages
2. NeTEx + Physical XML Class Model - UML
Framework Classes
Version, ServiceFrame
Physical Model Concrete Classes
Points, Links, Stops, Routes, RouteLinks,
JourneyPatterns, Journeys, etc, etc
Packages
3.XML Implementation – NeTEx Schemas: How to Serialize?
Net Publication
Nx XML Stops
Nx XML Point
Nx XML Routes
NxXML ServiceFrame
Nx XML Journeys
Nx XML Version
4.XML Examples
njsk
Common Modular Organisation
of Packages
15
njsk
Protocols vs Formats
•
•
•
NeTEx separates payload from message
• Includes version and container (“Version Frame”)
constructs
Data exchangse as XML documents with any file
protocol
• E.g. FTP, SMTP, http
Includes SIRI based message protocol
•
•
Request/Response - data satisfying specific filter criteria
Publish/Subscribe – eg for daily timetable changes
njsk
NeTEx SIRI: Request/Response
•
•
Request
for one
or more
NeTEx
data
objects
Filter
says
which
objects
&/or
values
Request + Filter
as NeTEx
NeTEx
Consumer
NeTEx NeTEx
Producer
DB
Delivery +
Data Objects
as NeTEx
CEN
SIRI
njsk
NeTEx Publication
• Asynchronous
•
NeTEx Publication
exchange
Filter
• One off or
• Periodic
Producer
Reusable XML
components
NeTEx NeTEx
• Same XML
Publish
DB
payload as for
SIRI
• Data Objects
• Common
NeTEx
Filters
Consumer
NeTEx
Consumer
NeTEx
Publication + Results:
List of Data Objects
njsk
Data quality- XML Integrity
constraints
• Data types: E.g. valid date, time, integer,
•
•
duration, language string, enumerations,
etc
Uniqueness: Each identifier declared only
once
Referential integrity: referenced entities
are also present in document
njsk
NeTEx
Functional Scope
20
njsk
NeTEx &
Transmodel
Functional
Areas
njsk
NeTEx Functional modules
njsk
NeTEx Outline Scope: PART 1
•
•
Part 1 Framework
•
•
•
•
Versions, Version Frames,
Organisations, Responsibilities, etc.
Day Types, Service Calendars
Vehicles, trains, Accessibility
Part 1 Public transport Network Topology.
exchange format
•
•
•
•
•
•
Infrastructure, infrastructure constraints,
Stops, Stations, etc Interchangaes
Routes, service patterns, etc.
Stop Places, Points of Interest, Parking, paths, entrances
Points of Interest, Parking
Garages, Crew points, Beacon Points
23
njsk
NeTEx Outline Scope: PART 2
• Part 2 Scheduled Timetables exchange format
•
•
•
Basic time related data (shared by all the domains): journey patterns,
journey times, service patterns, operating days, journey interchanges,
etc.
Passenger information specific objects: vehicle journeys, (passing
times, Coupled Journeys, Journey Parts, Train Composition
Data used specifically in the exchanges between the scheduling &
vehicle monitoring systems (blocks and related concepts)
24
njsk
NeTEx Outline Scope: PART 3
• Part 3 Fare information
multimodal information systems providing planned passenger
information
• planned tariff information exchanged between service operators,
service operators and product owners (i.e. authorities, etc.)
• Includes
• Different Tariff Structures (Spatial, Time based, Yield managed)
• Fare Pricing Parameters
• Excludes
•
•
•
•
Management of fare product and applications
Certification, registration and identification
Purchasing and fulfillment
(price calculation)
25
njsk
NeTEx / Fares Scope
26
njsk
Fare
scope
NeTEx Fares - Use cases
•
Provide information on fare products and their
rules and restrictions to passengers
•
•
•
•
•
•
•
•
•
•
Distributing fares information for publication
Distributing fares information to online systems
Provide information on fare products and their rules and restrictions for a specific
journey,
Identify time schedules and conditions for the lowest fares
Show fare zones on topographical and schematic maps,
Exchange of fare information between long distance (i.e. heavy rail) and local
public transport
Provide a price calculator with up to date fare information
Submitting a fare scheme for approval
Provisioning of ticket vending machines with fare information
Provisioning of ticket checking devices
28
njsk
NeTEx Fares / A very
Simplified model
29
njsk
A Classic Fare Matrix
•
SCHEDULED STOP POINT
or
TARIFF ZONE
DESTINATION MATRIX ELEMENT
© 2006, Carl Bro Group- slide 30
njsk
NeTEx Point to Point Fare Structure
class XSD NeTEx TM FC Geographical Fare Structure Basic
TimingPoint
Name:
Author:
Version:
Created:
Updated:
ScheduledStopPoint
1
1
+end
of
+start
of
1..*
+included
in
XSD NeTEx TM FC Geographical Fare Structure Basic
nick.knowles
1.0
30/04/2014 17:52:10
09/06/2014 23:55:16
+composed
* of
Zone
TariffZone
+start
of
1
+end
of
1
{Exclusion}
+to
+from
*
*
+from
*
+to
*
PriceableObject
DistanceMatrixElement
+related
to
1 +given
for
FarePrice
*
DistanceMatrixElementPrice
31
njsk
Access rights & Products
• ACCESS RIGHT: right to consumer public
•
•
transport service, e.g. point to point, route,
zone, network, day,
FARE PRODUCT; Set of access rights
with additional conditions, “Usage
Parameters”, e.g. NRT Fare, Rail card,
etc etc
SALES PACKAGE: Named product with
additional sales conditions &
materialization.
njsk
NeTEx Access rights & Products
class XSD NeTEx TM FC Access Right Assignment Basic1
+specified by
PriceableObject
1
SalesPackage
+composed
of
1
+included
in
1..*
PriceableObject
SalesPackageElement
FareInterval
PriceableObject
DistanceMatrixElement
+comprises
1
+used in
0..1
+used in
*
+for
TimeInterv al
1
0..1
0..1
0..*
+defined by 0..*
+specified by
ServiceAccessRight
FareProduct
PriceableObject
FareStructureElement
+defined by
+specified
by
+assigned
to
+specified by
1
+specifying
limits for
1
+specifying limits for
+specifying
limits for
*
*
*
0..*
Assignment
AccessRightParameterAssignment
+specifying limits for
+for
+for
+via
0..*
+assigned to
0..*
+assigned
to
0..*
+for
*
0..*
PriceableObject
PriceableObject
UsageParameter
0..*
+assigned
0..*
to
DataManagedObject
TrainNumber
+for
+assigned
to
0..*
0..*
Organisation
Operator
SeriesConstraint
UserProfile
GroupTicket
PurchaseWindow
Name:
Author:
Version:
Created:
Updated:
XSD NeTEx TM FC Access Right Assignment Basic1
Kasia
1.0
30/04/2014 18:35:39
10/06/2014 08:11:15
33
njsk
Travel Specification
class XSD NeTEx TM FS Sales Transaction Basic
PriceableObject
concerning
PassengerContractEvent
*
SaleTransaction
purchase
0..*
sale
asked for in
1 composed
of
0..1
included
in
1..*
1
1
specifying limits for
describes
SalesPackage
specifying limits for
specified by
Assignment
0..*
PriceableObject
SalesPackageElement
*
for
AccessRightParameterAssignment
PassengerContractEvent
for *
Trav elSpecification
*
1
specified by
*
for
*
assigned to
ServiceAccessRight
1
FareProduct
/bought by
1
DataManagedObject
assigned to
including
Customer
ValidityParameterAssignment
assigned to
PriceableObject
described by
*
TypeOfEntity
UsageParameter
with
1
0..*
TypeOfTrav elDocument
1..*
SpecificParameterAssignment
GroupTicket
MinimumStay
Reserv ing
Reselling
applicable to
0..1
Name:
Author:
Version:
Created:
Updated:
XSD NeTEx TM FS Sales Transaction Basic
NeTEx
1.0
06/05/2014 14:54:12
06/05/2014 15:04:23
UserProfile
PurchaseWindow
UsageValidityPeriod
Exchanging
Replacing
Refunding
Rhe specific choice (out of all the possible available generic values) actually made
on a purchase.
For example a Child, Single, Off-peak fare
34
njsk
Access rights & Products
• ACCESS RIGHT: right to consumer public
•
•
transport service, e.g. point to point, route,
zone, network, day,
FARE PRODUCT; Set of access rights
with additional conditions, “Usage
Parameters”, e.g. NRT Fare, Rail card,
etc etc
SALES PACKAGE: Named product with
additional sales conditions &
materialization.
njsk
Reusable Usage Parameters
class XSD NeTEx TM FC Usage Parameters Intro
DataManagedObject
days
0..1
assigned to
ClassOfUse
DayType
0..*
0..1
for
0..*
«enumeration»
FareClassEnum
TypeOfValue
DataManagedObject
valid
Av ailabilityCondition
ValidityCondition
assigned to
assigned to
included in *
0..*
includes *
firstClass
secondClass
thirdClass
economyClass
businessClass
turista
preferente
0..*
for 0..*
for
Assignment
AccessRightParameterAssignment
*
for
assigned to
PriceableObject
UsageParameterPrice
UsageParameter
*
given for
1
«XmlImplementAs...
VehicleMode
TypeOfEntity
classifies
0..*
Mode
assigned to 0..*
classified by
related to
FarePrice
0..*
for
0..*
0..1 TypeOfUsageParameter
from
0..1to
change
RoundTrip
LuggageAllow ance
Routing
0..1
change
Reselling
ChargingPolicy
0..*
0..*
Interchanging
StepLimit
PenaltyPolicy
EntitlementGiv en
Transferability
allows
0..*
EntitlementRequired
to
use
FrequencyOfUse
UserProfile
0..*
to
use
uses
0..*
can use
0..*
0..1
PriceableObject
Serv iceAccessRight
MinimumStay
classified by
Exchanging
Refunding
allowed
0..*
classified
by
requires
classifies
0..1
0..*
allows
classified
CommercialProfile
UsageValidityPeriod
GroupTicket
0..1
PurchaseWindow
0..*
Reserv ing
Replacing
CompanionProfile
0..*
classifies
0..1
0..1
classifies
TypeOfValue
0..1
Name:
Author:
Version:
Created:
Updated:
XSD NeTEx TM FC Usage Parameters Intro
NeTEx
1.0
30/03/2013 11:41:41
04/06/2014 00:01:25
TypeOfConcession
njsk
TAP TSI
MAPPINGS
njsk
Objectives
• How to map B1 (NRT) to NeTEx?
• What are equivalent semantics?
•
•
•
Gap Analysis: What extra NeTEx Entities, Attributes,
Relationships are needed?
What implicit B1 semantics can NeTEx also describe?
Where is decomposition needed? (because NeTEx
generally separates concerns & normalizes to atomic
elements – cf B1 & B2 optimized views)
• How to do it efficiently?
•
Modularisation: which package does it go in?
• Add extra view entities?
njsk
Sources
• TAP TSI B1, B2, B3 Documents
• 2012.09 V1
• 2013.03 Updates eg Table L
• TAP TSI 5.1 Document (Rules on using)
• TAP TSI Code lists
• Sample data
njsk
Methodology - Technical
•
•
•
•
•
•
•
TAP B* Analysis Models in Enterprise Architect
• Overview & Detail diagrams
Extend NeTEx UML Physical Model
Tap B*/NeTEx Mapping Table as Spreadsheet
Extend XML schema to support B*
Create examples to help validate schema and
clarify interpretation
B* Mapping report
Model Documentation as part of NeTEx Part 3
documents
njsk
Summary
Comments
njsk
Summary
• NeTEx can represent B1, B2, B3 content
• Has additional capabilities
• Interpretation is quite complex – but then
•
so are B1, B2, B3…..
Interoperability is quite possible.
njsk
Some Comparison Points
B1, B2, B3
NeTEx
Technology
Csv files
XML document
Packaging
Separate files, naming
convention
Document (s)
Protocol
ftp
ftp and/or SIRI
Consistency
3 separate B1, B2, B3, some
common concepts
Unified, reusable
conditions
Architecture
Optimised flat files
Normalized reusable
component objects
Expressiveness
Limited to agreed concepts
Rich, extensible
Integrity checking
No
Yes
Versioning
Yes
Fine grained, uniform
Responsibility
Supplying RU
Fine grained, uniform
njsk
Some disadvantages of NeTEx
• Larger, More complex model, more effort
•
•
to understand, harder to interpret.
XML is more verbose
Slow standards process, multi-stakeholder
participation
njsk
Some Advantages of NeTEx
• More complete
• More extensible
• Greater reuse of components and of
design patterns
njsk
Reusable Usage Parameters
class XSD NeTEx TM FC Usage Parameters Intro
DataManagedObject
days
0..1
assigned to
ClassOfUse
DayType
0..*
0..1
for
0..*
«enumeration»
FareClassEnum
TypeOfValue
DataManagedObject
valid
Av ailabilityCondition
ValidityCondition
assigned to
assigned to
included in *
0..*
includes *
firstClass
secondClass
thirdClass
economyClass
businessClass
turista
preferente
0..*
for 0..*
for
Assignment
AccessRightParameterAssignment
*
for
assigned to
PriceableObject
UsageParameterPrice
UsageParameter
*
given for
1
«XmlImplementAs...
VehicleMode
TypeOfEntity
classifies
0..*
Mode
assigned to 0..*
classified by
related to
FarePrice
0..*
for
0..*
0..1 TypeOfUsageParameter
from
0..1to
change
RoundTrip
LuggageAllow ance
Routing
0..1
change
Reselling
ChargingPolicy
0..*
0..*
Interchanging
StepLimit
PenaltyPolicy
EntitlementGiv en
Transferability
allows
0..*
EntitlementRequired
to
use
FrequencyOfUse
UserProfile
0..*
to
use
uses
0..*
can use
0..*
0..1
PriceableObject
Serv iceAccessRight
MinimumStay
classified by
Exchanging
Refunding
allowed
0..*
classified
by
requires
classifies
0..1
0..*
allows
classified
CommercialProfile
UsageValidityPeriod
GroupTicket
0..1
PurchaseWindow
0..*
Reserv ing
Replacing
CompanionProfile
0..*
classifies
0..1
0..1
classifies
TypeOfValue
0..1
Name:
Author:
Version:
Created:
Updated:
XSD NeTEx TM FC Usage Parameters Intro
NeTEx
1.0
30/03/2013 11:41:41
04/06/2014 00:01:25
TypeOfConcession
njsk
References
•
•
CEN/TS 16614-1:2014 Public transport - Network and Timetable
Exchange (NeTEx) - Part 1: Public transport network topology exchange
format
CEN/TS 16614-2:2014 Public transport - Network and Timetable
Exchange (NeTEx) - Part 2: Public transport scheduled timetables
exchange format
•
ERA/2012/INTEROP/NP/01s Study on the standard for the exchange of
fare information in the context of connection with other modes of
transport (NeTEx Part 3)
•
CEN TC278, Reference Data Model For Public Transport, ENV12896
revised, june 2001,
njsk
APPENDIX
Some examples of the
sort of passenger
information NeTEx is
intended to support.
48
njsk
Network
49
njsk
Example - Paris PT & zones
njsk
Example - Fare Zones - Berlin
njsk
Example -. London
njsk
Copenhagen fare zones
njsk
Rail / Metro zoning
njsk
Rover products
njsk
More zones
njsk
Rail add on
zones
• Add on
fare
zones
njsk
Interchanges
58
njsk
Example Complex Interchanges
59
njsk
Complex interchanges station
Layout
• Multiple
Bromfied
bus
STOP PLACE
Ticket Hall
(ACCESS SPACE)
A1
platforms,
&
entrances
Platforms 1 (QUAY)
Example
Rail Station with multiple
tracks & two entrances
© Crown Copyright 2010
Stairs
S1
Ground
Access to
Platforms
(ACCESS
SPACE)
Platform 2 (QUAY)
Platforms 2 & 3 (QUAY)
Stairs
S2
Ground
Platform 3 (QUAY)
Level1
Ground
Platforms 4 (QUAY)
Stairs
S3
Entrance Hall
(ACCESS SPACE)
A2
60
njsk
Example Station map -Wimbledon
61
njsk
Example Entrances & Platforms
only
Wimbledon Stop L
(Hartfield Road àNW)
BCT-MKD (QUAY)
Wimbledon Stop C
(Wimbledon Bridgeà SE
BCT-MKD (QUAY)
Wimbledon Stop P
(Wimbledon Bridge à NW
BCT-MKD (QUAY)
Wimbledon Stop D
(TheBroadway àSE)
BCT-MKD (QUAY)
)
Entra
n
Main
Exte
ENT rnal
RAN
C
RSE E
Grou
nd C
o n co
urse
(ACC RLY
ESS
SPA
CE)
R
(ENT SE
RAN
CE)
ce
Taxi
SHR Rank
(QUA
Y
+ Sto
pA
GRL rea
S
Platf
orm
1L
MET
(QUA U
Y)
Platf
orm
2L
MET
(QUA U
Y)
Platf
orm
3L
MET
(QUA U
Y)
Platf
orm
4L
MET
(QUA U
Y)
Platf
RPL orm 5
(QUA
Y)
Platf
RPL orm 6
(QUA
Y)
Platf
o
RPL rm 7
(QUA
Y)
Platf
o
RPL rm 8
(QUA
Y)
Platf
o
RPL rm 9
(QUA
Y)
Wimbledon Stop A
(Alexandra Road àNE)
BCT-MKD (QUAY)
Wimbledon Stop B
(Alexandra Road ->SW)
BCT-MKD (QUAY)
Platf
orm
1
MET 0 TramL
ink
(QUA
Y)
Wimbledon Station
NaPTAN Points
62
njsk
Example Complex Station model
Wimbledon Stop D
(TheBroadway àSE)
QUAY
Lift
)
(QUA
Y)
QUA
Y
&6(
ms 5
Platf
or
Platf
or
m6
(QUA
Y
)
)
(QUA
Y
m7
Platf
or
&8(
Platf
or
ms 7
m8
(QUA
Y)
QUA
Y)
6_ES
1 pl
Platf
or
m 10
T
(QUA ramLink
Platf
Y)
o r ms
9&1
0 (Q
UAY
Platf
)
o rm
9 (Q
UAY
)
Stair
Entra 2
n ce
5n
Lower
-EE1
doors
open
2
1
Stair
Entra 1
n ce
A
2_ES
1g
Lif
t
LLift
1 R
Lift 1
Entra
nc
S
A5_E
L
Lower
R
Entra
n
c
R
Stairs S
PJ
S1_p1
e
Sta
ir
S1 s
R
Stairs S
1pl
Distr
e
3n4_
EI1p
l
Open
ing
Lower
PJ
St_G2
R
ict Lin R
e Co
nRc
A5
o u rs
R
e (Q
UAY
R)
Entra
n ce
1n2_
R
EI1p
l
open
ing
R
R
Stair
Entra 1
n ce
A5
_ES1
pl
Wimbledon Stop A
(Alexandra Road àNE)
QUAY
Stair
Entra 3
n ce
7m
8_ES
1pl
PJ
A2_j1
Wimbledon Stop B
(Alexandra Road ->SW)
QUAY
Platf
or
e
A2b_
EL1g
n6_E
L1pl
R
R
Lift 1
Entra
nc
Lift 2
Entra
n ce
5
Stair
Entra 4
n ce
9n10
_ES1
pl
R
)
Lift
R
8_EL
1pl
Lower
PJ
A2_j2
)
Stairs
S
s
Li
L3
Lift
Entra 3
n ce
7n
e
A2b_
EL2g
m5
_EL1
pl
Lift
R
ft
rs
e
S4
9 n10
St
ai
Lift 4
Entra
nc
Stairs
S
PJ
St_G1
wn
Disa
b
(PAR led park
ing
KING
ARE
A)
Ground
Lift 2
Entra
nc
Sta
ir
R
R
2_ES
2g
2b_E
L3g
L4
R
Stair
Entra 2
n ce
A
S3
t
Lif
Lift 3
Entra
n ce
A
EL4g
Ground
Set D
o
R
2_ES
3g
R
Fore
co u r
t
R
R
e
LU (Q
UAY
Lift 4
Entra
n ce
A2b-E
I5
open
door
Stair
Entra 3
n ce
A
A2_E
S4g
A2b_
R
Entra
nc
PJ
A2_j3
PJ
FC_j1
R
-EI1
barrie
rs
PJ
A2b_j5
R
Stair
Entra 4
n ce
g
R
m2
PJ
A2_j4
R
Wimbledon Station
Topology
R
R
R
PJ
FC_j2
R
L U (Q
UAY
A2b
2b_E
L1
ank
m1
PJ
A2b_j6
I6
door
Lift 1
Entra
n ce
A
Main
Entra
n ce
A1
Conc
R o u r se
R
C o rr
idor
Street
R
R
ms 1
open
e
EL2g
Platf
or
E1
A4-E
I3
barrie
rs
Entra
n
Centr
Rourt
Entra e C
(Acc nce Area
e ss S
p a ce
)
A4
R
Tic
(ACC ket Hall
ESS
SPA
CE)
A1
R
Entra
n ce
A1
Platf
or
ce
Exte
rn
Entra al
n
A4-E ce
R
Centr
e
Cour
t
3g
A2b_
Grou
R
n
(ACC d Conco
ESSEn urse
A2
SPtrA
aC
n ce
A2b-E E)
Ground
Lift 2
Entra
nc
Platf
or
PJ
St_W5
A2b_
EL
Taxi
R
Ground
Platf
or
Lift 3
Entra
n ce
2b_E
L4 g
Wimbledon Stop C
(Wimbledon Bridgeà SE)
QUAY
PJ
St_W1
R
Stair
s
S2
R
R
R
Platf
o rm
4 LU
Platf
(QUA
o r ms
Y)
3&4
(QUA
Y)
Platf
o rm
3 LU
(QUA
Y)
Lift 4
Entra
n ce
A
PJ
St_W2
&2(
QUA
Y)
R
Park
ing
A3
R
PJ
St_W4
Wimbledon Stop P
(Wimbledon Bridge à NW)
QUAY
R
PJ
St_W3
Bicyc
le
R
L2
Wimbledon Stop L
(Hartfield Road àNW)
QUAY
Street
63
njsk
Connection & Transfer Times
Default
Connection
CONNECTION
Wimbledon
9100WIMBLEDON
SSP
Rail
• transfer between
Wimbledon
9400ZZLUWIM
SSP
Metro
Connection
NAVIGATION
PATH.
Access
• Transfer between
SITEs (eg POINT OF
INTEREST or STOP
PLACE)., with timings &
accessibility
Stop A (QUAY)
Stop P (QUAY)
Path Link(s)
Wimbledon Lawn
Tennis Club
Path Link(s)
Point of Interest
Entrance
ACCESS
Platform 1&2 (QUAY)
•
Hall
Wimbledon Station
Rail
STOP PLACE
Path
Lnk(s)
Path
Link(s)
Path Link(s)
Platform 9&10 (QUAY)
Wimbledon Station
Metro
STOP PLACE
Path Link(s)
Path Link(s)
Path Link(s)
Entrance
Connection
• Transfer between
points within SITE, with
timings and
accessibility
Wimbledon
490000272P
SSP
Bus
Connection
Platform 5 &6 (QUAY)
•
Wimbledon
9100WIMBLDN10
SSP
Rail
Platform 2&3 (QUAY)
SCHEDULED STOP
POINT in timetable,
with timings &
accessibility
© Crown Copyright 2010
Connection
Platform 7&8 (QUAY)
•
Example of
Transfer & Connection Times
Default
Connection
StreetàWLTC ((NAVIGATION PATH) A
Q1&2àQ7&8 (NAVIGATION PATH) :
Q5&6àStreet (NAVIGATION PATH) :
StreetàWLTC cNAVIGATION PATH) B
Q5&6àQ7&8 (NAVIGATION PATH) :
Q7&8àQ9&10 (NAVIGATION PATH)
Q5&6àQ9&10 (NAVIGATION PATH)
64
njsk
Timetables
65
njsk
Timetables
• NeTEx can represent the reusable
elements used to derive timetables e.g.
JOURNEY PATTERNS, TIMING
PATTERNS, TIMING LINKs, TIME
DEMAND TYPES (peak , off peak etc) etc
• Enables advanced passenger
information
njsk
Timetables - Mainline
•
•
•
•
•
Different Service
patterns
Timing Links vs
Service Links
Different Day
Types
Exceptions
Footnotes
67
njsk
Eurostar Routes & Destinations
Eurostar Lines
Ebbsfleet
Calais
Frethun
Ashford
Brussels
Midi
Lille
Europe
Paris
Gare du Nord
Marne La Vallee
Summer Only
Su
m
Winter Only
m
Disneyland
er
On
ly
Avignon
ly
On
Winter Only
Summer Only
r
nte
Wi
London
St Pancras
•
•
Not every line
stops at every
station
May be different in
each direction
•
Moutiers
Aime
La Plagne
Winter Only
Bourg
St Maurice
Winter Only
(eg London Paris Lille)
njsk
Journeys & Patterns
Eurostar London-Paris (Route 01 Outbound)
Journeys, Service Patterns & Day Types
• London to
•
Paris
Outbound,
Weekdays
1 Route
• 2
•
intermediate
stops
Two passed
Stops
• 4 Service
•
Patterns
19
Journeys
London
St Pancras
Ebbsfleet
Ashford
Calais
Frethun
Lille
Europe
Paris
Gare du Nord
Route 01
05:25
06:12
SP 01c
06:53
07:22
08:02
08:55
SP 01d
09:22
10:25
11:32
12:28
SP 01b
14:02
15:02
16:02
16:22
17:32
SP 01a
18:02
18:31
19:02
20:02
Everyday
Weekdays only
F1 - Runs Mondays and Fridays only from 4 January to 5 February.
Runs Monday to Friday at all other times.
F2 - Runs Tuesday to Thursday from 4 January to 5 February only.
njsk
Service Patterns
Eurostar London-Paris (Route 01)
Service Patterns
London
St Pancras
Ebbsfleet
Ashford
Calais
Frethun
Lille
Europe
Paris
Gare du Nord
01
01d
01c
01b
01a
• Directional
njsk
Timing Patterns
Eurostar London-Paris (Route 01)
Timing Patterns
London
St Pancras
Ebbsfleet
Ashford
Tunnel
in
Tunnel
Out Calais
Frethun
Lille
Europe
Paris
Gare du Nord
01
01d
01c
01b
01a
• Not all timing points are
Stop points
njsk
Run Times & Wait Times
Eurostar London-Paris (Route 01)
Run Times & Wait Times
Compute from
Start time,
Start
Time
+
London
St Pancras
Ebbsfleet
TL
TL
Timing pattern,
•
•
Timing Points,
TimingLinks
Run
time
Run
time
Wait Time
+
Wait
Time
Ashford
Tunnel
in
TL
TL
Run
time
Tunnel
Out Calais
Frethun
TL
TL
Run
time
Lille
Europe
Run
time
Wait
Time
Run
time
Paris
Gare du Nord
TL
Run
time
Wait
Time
d 6:12
GMT
Run times (for a
given Time
DemandType)
5M
17M
24M
a 6:24
GMT
a 6:49
GMT
d 6:29
GMT
20M
1H46M
2H01M
p 6:58
GMT
p 8:08
CT
a 9:54
CT
d 6:53
GMT
njsk
Timing Link vs Timing Pattern?
Eurostar London-Paris (Route 01)
Timing Patterns
London
St Pancras
Ebbsfleet
Tunnel
in
Ashford
Tunnel
Calais
Out
Frethun
Lille
Europe
Paris
Gare du Nord
01
01d
01c
01b
01a
Run time
17M
Run time
2H05M
Run time
22M
Run time
2H15M
Run time
32M
Run time
Run time
Run time
Run time
Run time
Run time
Wait
Time
Run time
Run time
Run time
Run time
1H52M
Run time
Wait
Time
Run time Run time
Run time Run time
Run time
Run time Run time
Run time Run time Run time
njsk
Complex Conditions &
Footnotes
• Day Types
• Public Holidays
• Operating
•
periods
Exceptions
74
njsk
Joining and splitting
A
D
Joining & Splitting with crossover
T1
3
Jo
ur
ne
Journey Part Couple X1
yJ
B
P
Jo
e
u rn
yJ
u
Jo
3
rn
a rt
:P
J2
ey
1:
1
4
2
3
T2
tA
1
a rt
:P
Journey J1 : Part A2
Journey J3 : Part B2
C1
5
5
Pa
r
B1
Journey J2: Part B2
4
3
2
1
J
r
ou
ne
J
1
yJ
r
ou
Journey
Meeting
M2
1
Journey
Meeting
M1
2
ne
Jo u
ar
:P
3
yJ
rn e
2
2
tA
a
:P
yJ
2:
T1
1
x
C
rt
x
3
C
Pa
rt
Q
B3
T1
5
4
T3
75
njsk
Coupled Journeys and Train Ids
njsk
Journey parts for couple
journeys
njsk
Connections & Interchanges
78
njsk
Eurostar Connections
Schiphol
Brussels
Midi
Antwerp
Eurostar European Rail
Connections
Rotterdam
Amsterdam
Aachen
Cologne
London
St Pancras
Ebbsfleet
Ashford
International
Calais
Frethun
Lille
Europe
Paris
Gare du Nord
Strasbourg
• Routes to the
•
Paris
Gare du Lyon
Netherlands,
Switzerland, France
Simple & Complex
Transfer legs
Zurich
Mulhouse
Paris
Gare Est
Basel
Geneva
LeMans
Rennes
Nantes
Angers
Avignon
Lyon
Marseille
Aix-En-Provence
Nice
Toulon
Perpignan
Montpellier
njsk
Fares
80
njsk
Rail Fares with complex conditions
njsk
Product Restrictions & Limitations
•
•
•
Who can Buy,
When &
Where?
When & Where
(and How) can
it be used?
Machine
Readable
• To find a
•
•
applicable
fares
(Check
use)
Human Readable
• To explain
In Transmodelese: “Fare Limitation
Parameter”
© 2006, Carl Bro Group- slide 82
njsk
Modes & Products
njsk
Access rights & Products
njsk
Fares for a
Metropolis
•
•
•
•
Multimodal,
Complex market
segmentation /
concessions,
conditions
Multiproduct,
including
electronic payment
Complex zones,
duration of travel
etc
njsk