© Kizoom 2006

New Data ExchangeStandards 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

Operating System (e.g. Windows/Linux)

Transporthttp, SOAP, TCP IP

Programming Modele.g. Java /Net /

Application Model

Persistence (Database)

Application Data Exchange

Operating System (e.g. Windows/Linux)

Transporthttp, SOAP, TCP IP

Programming Modele.g. Java /Net /

Application Model

Persistence (Database)

Application Data Dynamic Exchange

SIRI, JourneyWeb,

etc

TransModel

NaPTAN, IFOPT NPTG,

TransXChange, etc

Application Data Dynamic Exchange

Application Data Dynamic Exchange

Server

Server

•Data Structures

•Data Identifiers

•Data Exchange Messages

•Recovery

© Kizoom 2006

UK Public Transport Data Standards Overview

DeliveryTo

Clients

Bus TimetablesTransXChange

AtcoCIF ++

JourneyPlannerEngines

DataBuild

Stops

NaPTAN

Places,Areas

NPTG

Mapping

GIS + Feature Layers

Real-Time Delivery

Points

Services

Journeys

StopEvents

StopEvents

Timetables

Operators

Points of Interest

e.g. PointX

Common Abstract model

TrainTimetablesRJIS CIF

JourneyWeb? JourneyWeb?

UpdatesExchange

StopMonitor

Vehicle

Real-Time Server

UpdatesExchange

DataBuild

Timetable

ConnectionConnectionSIRISIRI

SIRISIRI

Journeys

TransModelTransModel

Vehicle

© Kizoom 2006

Reuse & Sharing

Timetable

Exchange

AVL Schedule

Exchange

Stop Data Exchange

Journey planning

© Kizoom 2006

CEN

SIRIServer Interface for

Real-time InformationIntro

© 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

SIRI Architecture • Modular

functional services

• Common transport

• Efficient real-time patterns

• Pluggable data e.g. NaPTAN

SIRI Common Services

Sto

p m

on

itoirin

g

Sto

p tim

etable

Pro

du

ction

timetab

le

Estim

ated tim

etable

Co

nn

ection

mo

nito

iring

Transmodel: PT modelStop Points, Vehicle Journeys, Lines, Journey Patterns, Vehicles, etc

Co

nn

ection

timetab

le

Pull Push

Gen

eral Messag

e

Situation+

+

Veh

icle mo

nito

ring

Facility+

+

Status

© Kizoom 2006

Example use of SIRI Services

AVMS

JP

ICS ICS Alerts

PT

ET

STSM

GMSGMS

GMS GMS

PT

AVMS

PT

ET

STSM

Web& Mobile

SM

ET

SM

SM

GMS

GMS

ETVM

VM

© 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

New

© Kizoom 2006

Operational Incident Exchange

Capture

Capture

Capture /Management

Capture

JP

Alerts

News

Displays

TPEGAdaptor

Capture /Management

AVLTPEGAdaptor

© Kizoom 2006

CENIdentification 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• Relationship to Topography, Access links• Data Administration

– 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

© Kizoom 2006

Fixed Object Submodels

POI ModelPOI Classification, Hierarchy

POI, POI Geometry

Stop Place ModelNetwork, Mode

Stop, Stop Area, Stop PointPath Link

AdministrativeArea

ModelArea, Hierarchy

GIS Model

Gazetteer /Topographical

ModelLocality, Hierarchy

proximity GIS Features

??

Projection

??

© Kizoom 2006

IFOPT Gene pool

TransModel5.1

CertuFR

NaPTAN& NPTG

UK

DelfiDE

Other National Models

IFOPT

TransModel++

SIRICEN

VDV 454

Trident

RTIGXML

© 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