New Data Exchange Standards Briefing TfL RTIP User’s forum Windsor House 11 July 2006 nick_knowles@kizoom.com © Kizoom 2006

Topics Introduction Key Data Exchange Standards in Progress Fixed Objects (IFOPT ) SIRI SIRI PT Situations/Incidents (& Datex2) What should TfL be doing? New New © Kizoom 2006

Motivation – Standards as A Tool for Managing Complexity Value to Passenger Transport Executives and Authorities / Operators Open, modular architectures Higher quality & function, lower technical risk Protection of investment, strategic availability. & supplier independence. Wide availability of interoperable data management tools Efficient tender specification criteria. Value to Suppliers European economies of scale & markets. Reduced complexity & deployment costs More reuse, Cheaper integration Simplified tendering, quality differentiator. Value to Both Enables new types of services European / World economies of scale Lowers costs - creating new markets Modern, Modular, scaleable architectures Harnesses commodity open internet technologies for transport. © Kizoom 2006

Standards – Technology Layers SIRI, JourneyWeb, etc Trans Model Application Data Dynamic Exchange Application Data Dynamic Exchange Application Data Exchange Application Data Dynamic Exchange NaPTAN, IFOPT NPTG, TransXChange, etc Application Model Application Model Programming Model e.g. Java /Net / Programming Model e.g. Java /Net / Data Structures Data Identifiers Data Exchange Messages Recovery Persistence (Database) Persistence (Database) Operating System (e.g. Windows/Linux) Operating System (e.g. Windows/Linux) Transport http, SOAP, TCP IP Transport http, SOAP, TCP IP © Kizoom 2006

UK Public Transport Data Standards Overview Mapping GIS + Feature Layers Points of Interest e.g. PointX JourneyWeb? Stops NaPTAN Delivery To Clients Journey Planner Engines Points Updates Exchange Data Build Operators Places,Areas NPTG Services Journeys Updates Exchange Bus Timetables TransXChange AtcoCIF ++ Data Build StopEvents Timetables Timetable Real-Time Delivery Journeys Real-Time Server StopEvents StopMonitor Train Timetables RJIS CIF Vehicle Vehicle SIRI Connection SIRI Connection TransModel Common Abstract model © Kizoom 2006

Reuse & Sharing Timetable Exchange AVL Schedule Exchange Stop Data Exchange Journey planning © Kizoom 2006

UK Standards Harmonisation path Derived from UK National XML & TransModel based Common Stop Model for whole UK TransModel based Further extension Converging on shared NaPT type Packages © Kizoom 2006

CEN SIRI Server Interface for Real-time Information Intro © Kizoom 2006

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. © Kizoom 2006

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

Example use of SIRI Services AVMS PT ET JP ST PT SM PT ET GMS ET SM VM Web & Mobile SM ET AVMS VM SM GMS ST SM ICS Alerts ICS GMS GMS GMS GMS © Kizoom 2006

Example 1: Hamburg Federated Modes & Regions © Kizoom 2006

Example 2: Copenhagen Integrator © Kizoom 2006

Example: Isle de France Hybrid © Kizoom 2006

SIRI – Gene Pool/Evolution Derived from UK, German & French, & Scandinavian National XML & TransModel based Supports both pull & Push architectures Same Interfaces can be used for different operational models © Kizoom 2006

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 © Kizoom 2006

Operational Incident Exchange Capture Capture JP Capture / Management Alerts Capture / Management Displays Capture News TPEG Adaptor AVL TPEG Adaptor © Kizoom 2006

Computerised Incident Processing 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 Computer-generated, computer readable Trackable : Timestamp, Id, Cross-references Start, End, Duration/ Expiry Line, Section, Station, Area Reason, Severity Effect Summary, Detail Human readable Advisory Actions, Channels, Workgroups, etc © Kizoom 2006

CEN Identification of Fixed Objects In Public Transport (IFOPT) © Kizoom 2006

What Is It? Proposed European Technical Standard for data model & data exchange of All PT Stops, (“Euro NaPTAN”) Stations & Interchanges Stop & Interchange structure & Navigation Stop Identification, Labelling Relationship to Topography, Access links Data Administration Places that people travel to Cities, Towns, suburbs, areas Points of Interest Designed to allow incremental adoption Works with partial data, doesn’t repeat GIS data Efficient for journey planners What Is it Useful for? Journey Planning, Guidance, Navigators – Stop Finding, Interchange paths, Walk legs to POI AVL / Real-time Info Stop Finding, Direction Headings, Platform assignment Scheduling, operations, AVL, statistics, etc New © Kizoom 2006

Physical Model We have here an overview of the Dusseldorf Airport. Altogether there are 5 levels. You can see on each level the indoor routing, gateways,…. The terminals A, B, C are defined as POIs. The computed trip leads into the terminal. © Kizoom 2006

Fixed Object Submodels Administrative Area Model Area, Hierarchy POI Model POI Classification, Hierarchy POI, POI Geometry Gazetteer / Topographical Model Locality, Hierarchy Stop Place Model Network, Mode Stop, Stop Area, Stop Point Path Link ? ? Projection GIS Model proximity GIS Features © Kizoom 2006

IFOPT Gene pool Other National Models VDV 454 Delfi DE RTIGXML SIRI CEN Trident NaPTAN & NPTG UK IFOPT Certu FR TransModel 5.1 TransModel ++ © Kizoom 2006

UK Perspective /Benefits NaPTAN is currently only simple PT nodes Bus Stops, Platform forms, entrances Adds Interchange Model Navigation: Improved Journey Planning Uniform impaired access data (DDA) Advanced Navigation & Real-time applications (Detailed digitalisation) Adds POI model Access link model Enables data capture & incremental use © Kizoom 2006

What Should TfL be doing? © Kizoom 2006

In General Use standards to achieve interoperability between modes – 1to n rather than n-n Needed for joined-up Journey planning Needed for joined-up real-time Use standards to achieve interoperability between external systems Use standards to simplify ( & lower costs ) Data maintenance System procurement © Kizoom 2006

Specifically for new work items Influence standard development to meet TfL’s needs Detailed Transport Interchange (IFOPT) Enhanced journey planning (IFOPT) Alerts and Angels (SIRI SS) Mandate relevant Standards in new projects © Kizoom 2006