CEN TC 278 WG3

SG7 - SIRISG9 - NeTEx

Service Interface for Real-time InformationNetwork and Timetable Exchange

Christophe Duquesne

CEN TC 278 WG3

SIRI & NeTEXCommon key points

• CEN standards

• Server-to-Server Services and exchange mechanism for public transport

• Focused on AVMS and Passenger Information System but with no use limitation

• Defines an independent communication layer shared by SIRI and NeTEx

• Tool box, well designed for gradual implementation

• It is not a Magic Staff … only an exchange standard !

CEN TC 278 WG3

SIRI & NeTEXCommon key points

• Common underlying standards– TransModel : main data model– IFOPT : stop place model– UIC recommendations and leaflets– GML, WGS84– XML, XSD– WS-Soap-WSDL-PubSub : Web Service

enabled

CEN TC 278 WG3

SIRI & NeTEXCommon key points

• European Level design– Germany– France– UK– Sweden– Holland– Hungary

• And rail organisations– UIC– ERA

CEN TC 278 WG3

DataModel

Inter-SystemData Exchange

End-user communication

SIRI & NeTEX

CEN TC 278 WG3

Business Drivers

• Reducing costs– Shared Markets, Tool base, reusable components– Common specifications for procurement and

implementation– Makes data costs viable for new functions

• Managing Complexity– Simplified, uniform solutions– Harnesses European wide know-how & best

practice• Increasing Capability

– Enables Advanced function– Large scale coverage, multimodal– More powerful representations & functions– Interoperability,

CEN TC 278 WG3

Political Drivers

• Sustainability / Green

– Encourage use of PT

– Make use of PT capacity efficient (ITS)• Harmonisation

– Free flow of data and system use between regions • Passenger rights

– Objective timely information

– Accessibility

CEN TC 278 WG3

OverviewExamples of inter-system exchanges

CEN TC 278 WG3

NeTEx

CEN TC 278 WG3

NeTEx Scope

• Reference (scheduled) data exchange (Network,Timetables and Fares)

• Focuses on objects and information required for passenger information and exchange between transit scheduling systems and AVMS

• European level standard– TransXChange in UK– VDV 452 in Germany– TRIDENT in France

• SIRI reference data services– Current SIRI reference data services are « embryonic »

CEN TC 278 WG3

NeTEx

• Status: under development : workplan – 18 to 24 months, with the objective to issue a final document

by end 2010.– issue a first document covering parts 1, 2A and 2B (see

below) by 2010. Parts 2C, 2D and 3 will be processed in 2011.

• Part 1 : Public transport network topology (routes, lines, route points, stop places and their components, stop points, navigation paths and other places linked to the PT network and relevant for passenger information, stop place equipment and services, network version, administrative information, etc.) .

CEN TC 278 WG3

NeTEx

• Part 2 : Scheduled Timetables (service patterns, service journeys, timetabled passing times, day types, timetable versions, mobility issues):

– Part 2A : Basic Data (shared): journey patterns, journey times, service patterns, operating days, interchanges, etc.

– Part 2B : Passenger information specific objects: trip patterns, trip duration (for journey planning), passing times, places, etc.

– Part 2C : Data used specifically in the exchanges between the scheduling and AVMS (additional scheduled data, such as blocks and related concepts)

– Part 2D : Data used in and/or defined by the AVMS, data linked to vehicle equipment and necessary for passenger information systems (mainly for SIRI).

• Part 3 : Fare Information (strictly dedicated to the passenger information) .

CEN TC 278 WG3

NeTEx

CEN TC 278 WG3

NeTEx

CEN TC 278 WG3

NeTExUse case examples

Timetable Planning System

Journey Planner System

Detailed Planned Service

Journey Plan (Lines, Transfer stops, Timing,

Fares)

NeTExNeTEx

CEN TC 278 WG3

NeTExUse case examples

Timetable Planning System

Passenger Information

System

Timetable (arrival times, speeds)

Estimated Vehicle Arrival Time

SIRIAVMS System

Real-time vehicle location

NeTExNeTEx

NeTExNeTEx

CEN TC 278 WG3

SIRI

CEN TC 278 WG3

SIRI Scope

• Defines a service interface for real-time information on public transport network

• Complements an underlying static information for network and timetable description (NeTEx)– SIRI does not define the underlying object structure and

data-model (Stop Points, Lines, Route, etc.)– Only dated information

• European level standard– RTIG in UK– VDV 453/454 in Germany

• Provides information on any change on the timetabled information, from publication to the transport running time

CEN TC 278 WG3

SIRI ServicesLine centric Services

• Production Timetable– Distribute latest timetable before vehicle

run

• Estimated Timetable– Distribute latest timetable including real-

time • Cancellations, additions, short working

• Realtime-predictions

CEN TC 278 WG3

SIRI ServicesStop centric services

• Stop Timetable– Distributes latest timetable

• Stop Centric Timetables

• Provisions Clients with latest data.

• Stop Monitoring– Real time Arrival & Departure Boards

• Arrivals, Departures, pass-throughs

• At stop, onboard, away

CEN TC 278 WG3

SIRI Services Connection services

• Connection Timetable– Distribute planned interchanges

• Stop Centric •

• Connection Monitoring– Connection management– Guaranteed connection support

CEN TC 278 WG3

SIRI Services General Message services

• General Message– Simple messages exchange

• Situation, operational, and general info messages

CEN TC 278 WG3

SIRI Services Facility Monitoring & Situation Exchange

• Facility Monitoring– Availability of facilities and equipments for

stops, vehicle and service. – Mobility restricted people information

• Designed to take care of most specific needs

• Situation Exchange– Enhance General Message Service – Structured incident model describing disruptions

to service– Based on TPEG, DATEX & TransModel

CEN TC 278 WG3

SIRIUse case examples

CEN TC 278 WG3

SIRIUse case examples

CEN TC 278 WG3

SIRIUse case examples

CEN TC 278 WG3

SIRIUse case examples

CEN TC 278 WG3

Communication Layer

CEN TC 278 WG3

Communication Layer

• Separation of Concerns– Transport layer is separate – Independent of Functional Message Content

• Web Service architecture: HTTP/SOAP…– Based on new Web services standard WS-

PubSub, etc (W3C) – Robust, scalable, architecture for Real-Time– Tunable for efficient deployment

CEN TC 278 WG3

• General Functions Common to all SIRI Service Types

– Subscription Management– Bulk exchange (NeTEx)

– Recovery & Restart– Access Controls – who is allowed to access– Versioning – allows distributed upgrades– Discovery – which systems have which

data/service

• Some Capabilities are Optional

Communication Layer

CEN TC 278 WG3

• Alternate Patterns of Interaction– Request/Response vs. Publish/Subscribe

• Choose for scalability & responsibility

– Direct Delivery vs. Fetched Delivery• Allows efficient implementation choices

– Notification Mediation• Reduces traffic for publish subscribe

– Last Update, Change Threshold,

– Subscriber Groups

Communication Layer

CEN TC 278 WG3

• Simple requests with powerful filtering capabilities

• Data traffic reduction– Incremental Data Changes:

• Only send data changes since last update

– Change threshold • Only notify if change is more than a certain amount

– Grouping of subscriptions • One notification for changes to many subscriptions in

a group

– Periodic publication (NeTEx)• Bulk publication, only for changed structures

(Lines…)

Communication Layer

CEN TC 278 WG3

NeTEx and SIRI

Production T

imetable

SIRI communication layer(XML-PubSub-Soap…)

Estim

ated Tim

etable

Vehicle M

onitoring

Connection T

imetable

Stop T

imetable

Stop M

onitoring

Connection M

onitoring

General m

essage

Facility M

onitoring

Situation E

xchange

XMLFiles

NeTEx(Reference Data

eXchange)

Network topology,Timetable passing times,

Etc.

(Transmodel 5 / IFOPT)

CEN TC 278 WG3

Thank You

SG7 – SIRI Winfried Bruns : bruns@vdv.de

SG9 - NeTEx Christophe Duquesne : christophe.duquesne@dryade.net