1. TC278 WG3 SIRI – Server Interface for Realtime Information Nick Knowles, CTO Nick.Knowles@kizoom.com © Copyright Kizoom 2006

2. 2 SIRI – Introduction Real-time Server-to-Server Services for Public Transport Defines a Service Interface for exchanging real- time information for public transport networks. Complements an underlying static information model for network and timetable description Provides information on any change on the timetabled information, from original publication to the actual & predicted transport running times.

3. 3 SIRI Architecture Modular functional services Common transport Efficient real-time patterns Pluggable data e.g. NaPTAN SIRI Common Services Stop monitoiring Stop timetable Production timetable Estimated timetable Connection monitoiring Transmodel: PT model Stop Points, Vehicle Journeys, Lines, Journey Patterns, Vehicles, etc Connection timetable PullPush General Message Situation++ Vehicle monitoring Facility++ Status IFOPT: PT Stop Place model Stop Place TPEG: Situation Place

4. 4 Separation of concerns Data Content Exchange Behaviour Transport Protocol well-defined interactions with XML schema Representations parameterising behaviour Independent e.g. HTTP POST, SOAP. defined XML Schema For payload

5. 5 Example use of SIRI Services AVMS JP ICS Alerts PT ET ST SM GMS PT AVMS PT ET ST SM Web & Mobile SM ET SM GMS ET VM

6. 6 Example 1: Hamburg Federated Modes & Regions

7. 7 Example 2: Copenhagen Integrator

8. 8 Example: Isle de France Hybrid

9. 9 SIRI – Gene Pool/Evolution Derived from UK, German & French, & Scandinavian National XML & TransModel based Supports both pull & Push architectures Same Interface s can be used for different operational models

10. 10 Proposed New work Item SIRI Situation Model Add a Full Incident Service to Includes addition information for internal management & user of incidents Full XML integrated with SIRI models. Requirements Support advanced ITS operations – eg RTJP, alerts, angels Multi-modal, Road Interoperable with TPEG – Export Interoperable with Datex To do Review Incident categories and properties Review operational requirements Review Datex2 & Road requirements New

11. 11 Computerised Incident Processing Line, Section, Station, Area Reason, Severity Start, End, Duration/ Expiry Trackable : Timestamp, Id, Cross-references Actions, Channels, Workgroups, etc Summary, Detail Summary, Detail Advisory Computer- generated, computer readable Human readable Effect Processing by Computers XML & other renderings Presenting to Humans Multi-channel delivery Incident is self describing object Rich Structured Model Identity Management Standards based Classification Standards based Location Model Distribution Actions & directives Quality data Many Distribution “Rules Engine” Business Rules Relate to This Model

12. 12 New SIRI Services SIRI Situation Exchange (SX): Scope:Real-time Unplanned/Planned Incidents “Back TransModel network & service model SIRI RT Transport IFOPT Place model TPEG Categories and classifications “Back Office for TPEG” Status Initial Draft Feb 2007 Working on revised Draft for May 2007

13. 13 New SIRI Services SIRI Facilities Monitoring Scope: Real-time Changes to Availability of Equipment / Local services SIRI Transport IFOPT Place model & Equipment Categories IFOPT Accessibility model (Harmonise with IFOPT GDF etc) Status Initial Draft Feb 2007 Working on revised Draft

14. 14 New SIRI Services SIRI Facilities Monitoring Scope: Real-time Changes to Availability of Equipment / Local services SIRI Transport IFOPT Place model & Equipment Categories IFOPT Accessibility model (Harmonise with IFOPT GDF etc) Status Initial Draft Feb 2007 Working on revised Draft

15. The Bigger Picture Building National & International models Nick Knowles, CTO Nick.Knowles@kizoom.com © Copyright Kizoom 2006

16. 16 Model Dependencies Stop Place (IFOPT) Incidents RT (SIRI SS) Timetables (TransModel) Facilities RT (SIRI FM) Road Journey Planner) RT Timetable (SIRI ET) Accessibility Categories GIS coords GML PT Journey Planner (JourneyWeb) Departures RT (SIRI SM) Road Network (XGDF) Journey Times Equipment Types Incidents RT (TPEG PTI)

17. 17 Public TransportRoad Information Data Reference Inter-system Data Exchange Communication to end user IFOPT GDF Data Model Datex 2 (Core) Transmodel Web W3C HTTP Web Service Wap I-Mode SMS … Norms & Standards for Passenger Information Systems Data Model Dictionnary Localisation XML Protocols SIRI Real-Time Services Datex 2 Events TPEG RDS-TMC Facilities Network Reference Data: TRIDENT (TransXchange/VDV451-452) OGC-GML X-GDF

18. Distrib ution Clients UK Public Transport Data Exchange for JP: Use of standards Bus Timetables TransXChange Journey Planner Engines Data Build Stops NaPTAN Places, Areas NPTG Mapping OS+ ITN Layer DNF, XGDF Real-Time Server Places Services Journeys StopEvents Timetables Operators Points of Interest e.g. PointX IFOPT Common Abstract model (TransModel) Train Timetables RJIS CIF JourneyWeb Updates Exchange StopEvents Vehicle Real-Time Server Updates Exchange Data Build Timetable Connection + Fares Fares FareXChange Vehicles Reservation Engines SIRI Data Build Dynamic Fares Updates Exchange LBS/ Placefinder IFOPT

19. IFOPT – Stop Place Model Nick Knowles, CTO Nick.Knowles@kizoom.com © Copyright Kizoom 2006

20. 20 Stop Place Introduction Nodes in an interchange Stop Place / Station Quay/Platform Boarding Position

21. 21 Administrative Model Distributed Management of data

22. 22 IFOPT Ancillary Models POI model Relationship of Places of interest to PT access Entrances, Accessibility Classification Administrative How to split a country for data administration “Data jurisdictions” by area/mode/role Distributed issuing of identifiers National Stop Public standards? eg uk.rail.kgx, de.air.muc, Topographical Model Relationship of Stops to Towns cities etc