SG7 - SIRI SG9 - NeTEx Service Interface for Real-time Information Network and Timetable Exchange

1. SG7 - SIRISG9 - NeTExService Interface for Real-time InformationNetwork and Timetable Exchange Christophe Duquesne

2. 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 !

3. 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

4. SIRI & NeTEXCommon key points • European Level design • Germany • France • UK • Sweden • Holland • Hungary • And rail organisations • UIC • ERA

5. SIRI & NeTEX Data Model Inter-System Data Exchange End-user communication

6. 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,

7. 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

8. Overview Examples of inter-system exchanges

9. NeTEx

10. 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 »

11. 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.) .

12. 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) .

13. NeTEx

14. NeTEx

15. NeTExUse case examples Timetable Planning System Journey Planner System NeTEx Detailed Planned Service Journey Plan (Lines, Transfer stops, Timing, Fares)

16. NeTExUse case examples Real-time vehicle location SIRI AVMS System Passenger Information System NeTEx Timetable Planning System NeTEx Estimated Vehicle Arrival Time Timetable (arrival times, speeds)

17. SIRI

18. 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

19. 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

20. 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

21. SIRI ServicesConnection services • Connection Timetable • Distribute planned interchanges • Stop Centric • Connection Monitoring • Connection management • Guaranteed connection support

22. SIRI ServicesGeneral Messageservices • General Message • Simple messages exchange • Situation, operational, and general info messages

23. SIRI ServicesFacility 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

24. SIRIUse case examples

25. SIRIUse case examples

26. SIRIUse case examples

27. SIRIUse case examples

28. Communication Layer

29. 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

30. Communication Layer • 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

31. Communication Layer • 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

32. Communication Layer • 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…)

33. NeTEx and SIRI XML Files Production Timetable Vehicle Monitoring Facility Monitoring Situation Exchange Stop Monitoring Stop Timetable Estimated Timetable Connection Timetable Connection Monitoring General message NeTEx (Reference Data eXchange) Network topology, Timetable passing times, Etc. (Transmodel 5 / IFOPT) SIRI communication layer (XML-PubSub-Soap…)

34. Thank You SG7 – SIRI Winfried Bruns : bruns@vdv.deSG9 - NeTEx Christophe Duquesne : christophe.duquesne@dryade.net