using the cen netex standard to represent basic rail fare datanetex-cen.eu › wp-content ›...
TRANSCRIPT
njsk
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
WG12, AutoVehicle and Equipment Ident
WG13, Architecture & Terminology
WG14, Recovery of Stolen Vehicles
WG1, Electronic Fee Collection
CEN / TC278 Road Transport & Traffic Telematic Plenary Chair:
WG8, Road Traffic Data WG3, Public Transport
WG5, Traffic Management
WG7, Geographic Road Data
WG9, Dedicated Short Range Communications
WG10, Human-Machine Interfaces
WG4, Traffic and Traveller Information
WG15, eSaftey
njsk
CEN / TC278 / WG 3 Public Transport Plenary Chair:
SG1 Data Communication on
Vehicles
SG 3 Passenger Information
SG 5 Interoperable Fare
Management
SG 4 Datamodel– Transmodel
SG 7 Service Interfaces Real Time Information
SG 6 Identification of fixed Objects in PT
SG 8 Distributed Journey Planning
SG 9 Netex
CEN TC278 WG3 Sub-groups
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 7
Evolving a Concrete PT Timetable schema
CEN
NeTEx
1.0
Part1
UIC Rail
Timetables
SIRI
Transmodel
VDV452
Trident
TransXChange,
etc
IFOPT
Transmodel
CEN
NeTEx
1.0
Part2
Transmodel Transmodel
NaPTAN,
etc
CEN
NeTEx
1.0
Part3 Bison, Noptis,
etc
TAP TSI,
Rail Fares
Examples
FareXChange
njsk 8
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
njsk 9
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
njsk
NeTEx / Transmodel
Methodology
10
njsk
Models – Levels of Abstraction
• Conceptual model is implementation
independent
• Transmodel based, modular UML
• 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
12
PHYSICAL MODEL
For Java
IMPLEMENTATION MODEL
(Java)
IMPLEMENTATION MODEL
(DDL)
PHYSICAL MODEL for DDL
CONCEPTUAL MODEL
(UML
PHYSICAL MODEL UML
For XML
IMPLEMENTATION MODEL
(XML)
Conceptual &
Physical Models
njsk
UML Transmodel PT Concepts – NeTEx submodel
POINTS, LINKS, STOP POINTS, ROUTES, ROUTE LINKS,
JOURNEY PATTERNS, JOURNEYs, etc, etc
Packages
1. NeTEx /Transmodel Conceptual Model - UML
3.XML Implementation – NeTEx Schemas: How to Serialize?
Conceptual vs Concrete Levels; Model Driven Design,
Physical Model Concrete Classes
Points, Links, Stops, Routes, RouteLinks,
JourneyPatterns, Journeys, etc, etc
Packages
Nx XML Journeys
Nx XML Routes
Nx XML Point Nx XML Stops
Nx XML Version
Net Publication
2. NeTEx + Physical XML Class Model - UML
4.XML Examples
NeTEx Framework
VERSION, VERSION FRAME
Packages
Framework Classes
Version, ServiceFrame
NxXML ServiceFrame
njsk 15
Common Modular Organisation
of Packages
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
CEN
SIRI
NeTEx
DB
Request + Filter
as NeTEx
Delivery +
Data Objects
as NeTEx
NeTEx
Producer
NeTEx
Consumer
njsk
NeTEx
Publish
NeTEx Publication • Asynchronous
exchange
• One off or
• Periodic
• Reusable XML
components
• Same XML
payload as for
SIRI
• Data Objects
• Common
Filters
NeTEx
DB
NeTEx Publication
Filter
NeTEx
Publication + Results:
List of Data Objects
NeTEx
Consumer
Consumer
Producer
NeTEx
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 23
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
njsk 24
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)
njsk 25
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)
njsk
NeTEx / Fares Scope
26
Fare
scope
njsk
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 •
© 2006, Carl Bro Group- slide 30
DESTINATION MATRIX ELEMENT
SCHEDULED STOP POINT
or
TARIFF ZONE
njsk
NeTEx Point to Point Fare Structure
31
class XSD NeTEx TM FC Geographical Fare Structure Basic
Name: XSD NeTEx TM FC Geographical Fare Structure Basic
Author: nick.knowles
Version: 1.0
Created: 30/04/2014 17:52:10
Updated: 09/06/2014 23:55:16
PriceableObject
DistanceMatrixElement
FarePrice
DistanceMatrixElementPrice
TimingPoint
ScheduledStopPoint
Zone
TariffZone
{Exclusion}
+start
of
1
+from *
+included
in
1..*
+composed
of*
+start
of
1
+from
* +to *
+end
of
1
+to
*
+end
of
1
+related
to1 +given
for
*
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
33
class XSD NeTEx TM FC Access Right Assignment Basic1
Name: XSD NeTEx TM FC Access Right Assignment Basic1
Author: Kasia
Version: 1.0
Created: 30/04/2014 18:35:39
Updated: 10/06/2014 08:11:15
PriceableObject
FareStructureElement
ServiceAccessRight
FareProduct
Assignment
AccessRightParameterAssignment
PriceableObject
SalesPackageElement
PriceableObject
SalesPackage
FareInterval
TimeInterv al
PriceableObject
DistanceMatrixElement
PriceableObject
UsageParameter
Organisation
Operator
DataManagedObject
TrainNumber
UserProfile GroupTicket PurchaseWindow
PriceableObject
SeriesConstraint
+for 0..*
+assigned
to
0..*
+defined by 0..*
+used in 0..1
+for*
+assigned
to 0..*
+specifying
limits for
*
+specified by
1
+specifying
limits for
*
+specified by1+defined by
0..*
+used in 0..1
+specifying limits for
*
+specified
by1
+for 0..*
+assigned
to 0..*
+included
in1..*
+composed
of
1
+for *
+assigned
to
1
+specifying limits for
0..*
+specified by
0..1
+assigned to0..*
+for 0..*
+comprises 1
+via 0..*
njsk
Travel Specification
34
class XSD NeTEx TM FS Sales Transaction Basic
PassengerContractEvent
Trav elSpecification
PassengerContractEvent
SaleTransaction
Name: XSD NeTEx TM FS Sales Transaction Basic
Author: NeTEx
Version: 1.0
Created: 06/05/2014 14:54:12
Updated: 06/05/2014 15:04:23
UserProfile
PriceableObject
SalesPackage
Assignment
AccessRightParameterAssignment
ValidityParameterAssignment
SpecificParameterAssignment
PriceableObject
UsageParameter
ServiceAccessRight
FareProduct
PriceableObject
SalesPackageElement
TypeOfEntity
TypeOfTrav elDocument
DataManagedObject
Customer
UsageValidityPeriod
GroupTicket ResellingMinimumStay Reserv ing
RefundingExchangingPurchaseWindow
Replacing
describes 0..*
sale 1
concerning
*
asked for in
0..1
specifying limits for *
specified by
1
with1..*
including1
for *
assigned to 0..*
specifying limits for
*
specified by
1
for *assigned to
1
included
in1..*
composed
of
1
for *
assigned to 1
described by *
applicable to
0..1
purchase 0..*
/bought by
Rhe specific choice (out of all the possible available generic values) actually made
on a purchase.
For example a Child, Single, Off-peak fare
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
Name: XSD NeTEx TM FC Usage Parameters Intro
Author: NeTEx
Version: 1.0
Created: 30/03/2013 11:41:41
Updated: 04/06/2014 00:01:25
PriceableObject
UsageParameter
UsageValidityPeriod
FrequencyOfUse
UserProfile
Transferability
GroupTicket
FarePrice
UsageParameterPrice
Assignment
AccessRightParameterAssignment
TypeOfValue
ClassOfUse
«enumeration»
FareClassEnum
firstClass
secondClass
thirdClass
economyClass
businessClass
turista
preferente
DataManagedObject
DayType
Reselling
MinimumStay
Reserv ing
DataManagedObject
ValidityConditionAv ailabilityCondition
Interchanging
RefundingExchanging
PurchaseWindow
EntitlementRequired
Mode
«XmlImplementAs...
VehicleMode
TypeOfValue
TypeOfConcession
CommercialProfile
TypeOfEntity
TypeOfUsageParameter
CompanionProfile
EntitlementGiv en
LuggageAllowanceRoundTrip
StepLimit
Routing
Replacing
ChargingPolicy
PriceableObject
Serv iceAccessRight
PenaltyPolicy
uses
0..*
allowed
0..1
change
0..*
from 0..1
to
use
0..*
requires
0..1
classified
by
0..*
classifies0..1
can use
0..*
allows
valid
days 0..*
0..*
allows0..*
to
use 0..1
for0..*
assigned to 0..*
related to
1given for
*
classified by
0..* classifies 0..1
classified
0..*
classifies
0..1
classified by
0..*
classifies 0..1
change
0..*
to 0..1
for0..*
assigned to0..1
for 0..*
assigned to 0..*
includes *included in *
for *
assigned to 0..*
for
0..*
assigned to0..1
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
Name: XSD NeTEx TM FC Usage Parameters Intro
Author: NeTEx
Version: 1.0
Created: 30/03/2013 11:41:41
Updated: 04/06/2014 00:01:25
PriceableObject
UsageParameter
UsageValidityPeriod
FrequencyOfUse
UserProfile
Transferability
GroupTicket
FarePrice
UsageParameterPrice
Assignment
AccessRightParameterAssignment
TypeOfValue
ClassOfUse
«enumeration»
FareClassEnum
firstClass
secondClass
thirdClass
economyClass
businessClass
turista
preferente
DataManagedObject
DayType
Reselling
MinimumStay
Reserv ing
DataManagedObject
ValidityConditionAv ailabilityCondition
Interchanging
RefundingExchanging
PurchaseWindow
EntitlementRequired
Mode
«XmlImplementAs...
VehicleMode
TypeOfValue
TypeOfConcession
CommercialProfile
TypeOfEntity
TypeOfUsageParameter
CompanionProfile
EntitlementGiv en
LuggageAllowanceRoundTrip
StepLimit
Routing
Replacing
ChargingPolicy
PriceableObject
Serv iceAccessRight
PenaltyPolicy
uses
0..*
allowed
0..1
change
0..*
from 0..1
to
use
0..*
requires
0..1
classified
by
0..*
classifies0..1
can use
0..*
allows
valid
days 0..*
0..*
allows0..*
to
use 0..1
for0..*
assigned to 0..*
related to
1given for
*
classified by
0..* classifies 0..1
classified
0..*
classifies
0..1
classified by
0..*
classifies 0..1
change
0..*
to 0..1
for0..*
assigned to0..1
for 0..*
assigned to 0..*
includes *included in *
for *
assigned to 0..*
for
0..*
assigned to0..1
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
platforms,
&
entrances
60
Platforms 2 & 3 (QUAY)
Bromfied
bus
STOP PLACE
Platforms 1 (QUAY)
Platform 3 (QUAY)
Platform 2 (QUAY)
Platforms 4 (QUAY)
Access to
Platforms
(ACCESS
SPACE)
Stairs
S1
Stairs
S2
Stairs
S3Ground
Ground
Ground
Level1
Ticket Hall
(ACCESS SPACE)
A1
Entrance Hall
(ACCESS SPACE)
A2
Example
Rail Station with multiple
tracks & two entrances© Crown Copyright 2010
njsk
Example Station map -Wimbledon
61
njsk
Example Entrances & Platforms
only
62
Ground ConcourseRLY(ACCESS SPACE)
+ Stop AreaGRLS
Pla
tform
7 R
PL (
QU
AY
)
Taxi RankSHR (QUAY)
Wimbledon Station
NaPTAN Points
Exte
rnal
EN
TR
AN
CE
R
SE
Wimbledon Stop P
(Wimbledon Bridge à NW
BCT-MKD (QUAY)
Wim
ble
do
n S
top
A
(Ale
xa
nd
ra R
oa
d à
NE
)
BC
T-M
KD
(QU
AY
)
Wimbledon Stop D
(TheBroadway àSE)
BCT-MKD (QUAY)
Wimbledon Stop C
(Wimbledon Bridgeà SE
BCT-MKD (QUAY)
Wim
ble
do
n S
top
B
(Ale
xa
nd
ra R
oa
d ->
SW
)
BC
T-M
KD
(QU
AY
)
Pla
tform
8 R
PL (
QU
AY
)
Pla
tform
5
RP
L (
QU
AY
)
Pla
tform
6
RP
L (
QU
AY
)
Pla
tform
10 T
ram
Lin
k
ME
T (
QU
AY
)
Pla
tform
9 R
PL (
QU
AY
)
Pla
tform
3 L
UM
ET
(Q
UA
Y)
Pla
tform
4 L
U
ME
T (
QU
AY
)
Pla
tform
1 L
U
ME
T (
QU
AY
)
Pla
tform
2 L
UM
ET
(Q
UA
Y)
Wimbledon Stop L
(Hartfield Road àNW)
BCT-MKD (QUAY)
Main
Entr
ance
RS
E
(EN
TR
AN
CE
)
njsk
Example Complex Station model
63
Stairs S1Sta
irs
S2S
tairs
S4
Sta
irs
S3
District Line Concourse (QUAY)A5
Lift
L1
Lift
L2
Lift
L3
Lift
L4
Centre Court
Centre Court Entrance Area (Access Space)A4
Forecourt
Ticket Hall(ACCESS SPACE)A1Ground Concourse
(ACCESS SPACE)A2
Pla
tform
s 9
& 1
0 (
QU
AY
)
Pla
tform
s 7
& 8
(Q
UA
Y)
Pla
tform
s 5
&
6 (
QU
AY
)
Pla
tform
s 3
& 4
(Q
UA
Y)
Pla
tform
s 1
& 2
(Q
UA
Y)
Pla
tform
7 (
QU
AY
)
Entr
ance
A4-E
I3barr
iers
EntranceA1-EI1barriers
Stair 4 EntranceA2_ES4g
Stair 1 EntranceA2_ES1g
Stair 1 EntranceA5_ES1pl
Lift 1 EntranceA5_EL1pl Stairs S
Lift R
Stair 2 EntranceA2_ES2g
Stair 3 EntranceA2_ES3g
Stair 4Entrance9n10_ES1pl
Lift 3 Entrance7n8_EL1pl Lift 2 Entrance5n6_EL1pl
Stair 3 Entrance7m8_ES1pl
Stairs
S
R
R
R
R
Disabled parking (PARKING AREA)
R
Taxi Rank
R
PJ
A2_j2
PJ
FC_j1
Ground
Ground
Ground
Ground
Lower
LowerLower
Lower
Wimbledon Station
Topology
Exte
rnal
Entr
ance
A4-E
E1
1
2
Wimbledon Stop P
(Wimbledon Bridge à NW)
QUAY
Stair 2 Entrance5n6_ES1pl
Wim
ble
do
n S
top
A
(Ale
xa
nd
ra R
oa
d à
NE
)
QU
AY
PJ
FC_j2
R
R
PJ
A2_j1
Lift 1 EntranceA2b_EL1g
Lift 4 EntranceA2b_EL4g
Stairs
S
Lift 3 EntranceA2b_EL3gLift 2 EntranceA2b_EL2g
PJ
A2_j3
R
R
Wimbledon Stop D
(TheBroadway àSE)
QUAY
Wimbledon Stop C
(Wimbledon Bridgeà SE)
QUAY
PJ
St_W1
PJ
St_W2R
R
R
Street
Street
R
PJ
St_G1
R
R
Wim
ble
do
n S
top
B
(Ale
xa
nd
ra R
oa
d ->
SW
)
QU
AY
PJ
St_G2
R
R
Pla
tform
8 (
QU
AY
)
Pla
tform
5 (
QU
AY
)
Pla
tform
6 (
QU
AY
)
Pla
tform
10 T
ram
Lin
k
(QU
AY
)
Pla
tform
9 (
QU
AY
)
Pla
tform
3 L
U (
QU
AY
)
Pla
tform
4 L
U (
QU
AY
)
Pla
tform
1 L
U (
QU
AY
)
Pla
tform
2 L
U (
QU
AY
)
Wimbledon Stop L
(Hartfield Road àNW)
QUAYPJ
St_W3
RR
ConcourseCorridorA2b
Lift 4 EntranceA2b_EL4g
Lift 3 EntranceA2b_EL3g
Lift 2 EntranceA2b_EL2g
PJ
A2b_j5
PJ
A2b_j6
R
R
R
R
PJ
A2_j4
EntranceA2b-EI6open door
Lift
R
EntranceA2b-EI5
open door
R
Entrance3n4_EI1plOpening Entrance1n2_EI1pl
opening
R
R
R
Main
E
ntr
ance
A1-E
E1
open d
oors
Lift 4 Entrance9n10_EL1pl SB
icycle
Park
ing
A3
R
Set Down
R
Lift 1 EntranceA2b_EL1g
R
PJ
St_W4
R
R
R
PJ
St_W5
R
R
R
R
R
R
R
Lift
R
R
R
R
RR
R
PJ
S1_p1
Stairs S
njsk
Connection & Transfer Times
• CONNECTION • transfer between
SCHEDULED STOP
POINT in timetable,
with timings &
accessibility
• NAVIGATION
PATH. • Transfer between
points within SITE, with
timings and
accessibility
• ACCESS • Transfer between
SITEs (eg POINT OF
INTEREST or STOP
PLACE)., with timings &
accessibility
64
Wimbledon Station
Rail
STOP PLACE
Example of
Transfer & Connection Times© Crown Copyright 2010
Wimbledon
9400ZZLUWIM
SSP
Metro
Wimbledon
9100WIMBLEDON
SSP
Rail
Wimbledon
490000272P
SSP
Bus
Wimbledon Lawn
Tennis Club
Point of Interest
Connection
Connection
Connection
Default
Connection
Path Link(s)
Path Lnk(s)Path Link(s) Path Link(s)
Access
Q7&8àQ9&10 (NAVIGATION PATH)
Wimbledon Station
Metro
STOP PLACE
Q5&6àQ7&8 (NAVIGATION PATH) :
Q5&6àQ9&10 (NAVIGATION PATH)
Q1&2àQ7&8 (NAVIGATION PATH) :
Path Link(s)
Path Link(s)
StreetàWLTC ((NAVIGATION PATH) A
StreetàWLTC cNAVIGATION PATH) B
Path Link(s)
Wimbledon
9100WIMBLDN10
SSP
Rail
Default
Connection
Connection
Path Link(s)
Q5&6àStreet (NAVIGATION PATH) :
Pla
tfo
rm 1
&2
(Q
UA
Y)
Pla
tfo
rm 2
&3
(Q
UA
Y)
Pla
tfo
rm 5
&6
(Q
UA
Y)
Pla
tfo
rm 9
&1
0 (
QU
AY
)
Pla
tfo
rm 7
&8
(Q
UA
Y)
Sto
p P
(Q
UA
Y)
Sto
p A
(Q
UA
Y)
En
tra
nce
En
tra
nce
Hall
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
• Not every line stops at every station
• May be different in each direction
• (eg London Paris Lille)
Summer OnlySummer Only
Winter Only
Win
ter
Only
Ashford
Paris
Gare du Nord
Marne La Vallee
Winter Only Winter Only
MoutiersBourg
St MauriceAime
La Plagne
Summ
er Only
Eurostar Lines
Winter Only
Avignon
Brussels
MidiLille
EuropeCalais
FrethunEbbsfleet
London
St Pancras
Disneyland
njsk
Ashford
Eurostar London-Paris (Route 01 Outbound)
Journeys, Service Patterns & Day Types
Lille
Europe
Calais
FrethunEbbsfleetLondon
St Pancras
05:25
06:12
06:53
07:22
08:02
08:55
09:22
10:25
11:32
12:28
14:02
15:02
16:02
16:22
17:32
18:02
18:31
19:02
20:02
SP 01a
SP 01b
SP 01d
Route 01
Paris
Gare du Nord
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.
F3 – Fridays only
Everyday
Weekdays only
SP 01c
Journeys & Patterns
• London to
Paris
Outbound,
Weekdays
• 1 Route • 2
intermediate
stops
• Two passed
Stops
• 4 Service
Patterns
• 19
Journeys
njsk
AshfordParis
Gare du Nord
Eurostar London-Paris (Route 01)
Service Patterns
Lille
Europe
Calais
FrethunEbbsfleetLondon
St Pancras
01a
01c
01b
01d
01
Service Patterns
• Directional
njsk
Timing Patterns
• Not all timing points are
Stop points
Ashford
Eurostar London-Paris (Route 01)
Timing Patterns
Lille
Europe
Calais
FrethunEbbsfleet
London
St Pancras
01a
01c
01b
01d
01
Tunnel
in
Tunnel
Out Paris
Gare du Nord
njsk
Run Times & Wait Times
Compute from
Start time,
+
Timing pattern, • Timing Points,
• TimingLinks
+
Run times (for a given Time DemandType)
TLTL TLTLTL TL TL
Ashford
Eurostar London-Paris (Route 01)
Run Times & Wait Times
Lille
Europe
Calais
FrethunEbbsfleet
London
St Pancras
Tunnel
in
Tunnel
Out Paris
Gare du Nord
Run
time
Wait
Time
Run
timeRun
time
Run
time
Run
timeRun
time
Run
time
Wait
Time
Wait
Time
17M
Start
Time
d 6:12
GMT
24M 2H01M
d 6:29
GMTd 6:53
GMT
a 9:54
CT
p 8:08
CT
5M 20M 1H46M
p 6:58
GMTa 6:24
GMTa 6:49
GMT
Wait Time
njsk
Timing Link vs Timing Pattern?
Ashford
Eurostar London-Paris (Route 01)
Timing Patterns
Lille
Europe
Calais
FrethunEbbsfleet
London
St Pancras
01a
01c
01b
01d
01
Tunnel
in
Tunnel
Out Paris
Gare du Nord
Run time
17MRun time
32M
Run time
2H15M
Run time
2H05MRun time
1H52M
Run time
22M
Wait
Time
Run time
Run time
Run time
Wait
Time
Run time
Run time
Run time
Run time
Run time Run time Run time Run timeRun timeRun 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
75
Journey J2: Part B2
Journey J1 : Part A2 Journ
ey J1
: Part
A2
Journey J2 : Part B3
1234
x
1 T12
T34
Journey J2 : Part B
1
Journey J1 : Part A1
1 T12
21 3 T24
T1
3
Joining & Splitting with crossover
Journey Part Couple X1
Jo
urn
ey
Me
etin
g
M2
Journey J3 : Part C
1 Journey J3 : Part B2Jo
urney
J3 :
Part C3
x
5
5
5
Jo
urn
ey
Me
etin
g
M1
A
P
D
Q
C
B
njsk
Coupled Journeys and Train Ids
njsk
Journey parts for couple
journeys
njsk
Connections & Interchanges
78
njsk
London
St Pancras
Ashford
InternationalEbbsfleet
Lille
EuropeCalais
Frethun
LeMans Rennes
Angers
Montpellier
Geneva
Eurostar European Rail
Connections Rotterdam
AntwerpSchiphol
Amsterdam
Paris
Gare du Lyon
Avignon
Paris
Gare du Nord
Lyon Aix-En-Provence Toulon
Marseille Nice Perpignan
Brussels
Midi
Cologne
Aachen
Paris
Gare Est
BaselStrasbourg
Mulhouse Zurich
Nantes
Eurostar Connections
• Routes to the
Netherlands,
Switzerland, France
• Simple & Complex
Transfer legs
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
© 2006, Carl Bro Group- slide 82
In Transmodelese: “Fare Limitation
Parameter”
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