TC278 WG3
SIRI – Server Interface for
Realtime Information
Nick Knowles, CTO [email protected]
© Copyright Kizoom 2006
SIRI – Introduction
• Real-time Server-to-Server Services for Public
Transport
• Defines a Service Interface for exchanging realtime 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.
2
IFOPT: PT Stop Place model
TPEG:
Stop Place
Situation Place
SIRI Architecture
•
Modular
functional
services
Facility++
Situation++
General Message
Vehicle monitoring
Status
Connection monitoiring
Pluggable
data e.g.
NaPTAN
Connection timetable
•
Stop monitoiring
Efficient
real-time
patterns
Stop timetable
•
Estimated timetable
Common
transport
Stop Points, Vehicle Journeys, Lines, Journey Patterns, Vehicles, etc
Production timetable
•
Transmodel: PT model
SIRI Common Services
Pull
Push
3
Separation of concerns
Data
Content
defined
XML Schema
For payload
Exchange
Behaviour
well-defined interactions
with XML schema
Representations
parameterising behaviour
Transport
Protocol
Independent e.g.
HTTP POST,
SOAP.
4
Example use of SIRI Services
PT
ET
AVMSST
PT
SM
PT
ET
GMS
VM
SM
JP
ET
SM
ET
Web
SM& Mobile
VM
GMS
AVMSST
SM
GMS
GMS
GMS
GMS
ICS
ICS
Alerts
5
Example 1: Hamburg
• Federated
Modes &
Regions
6
Example 2: Copenhagen
• Integrator
7
Example: Isle de France
• Hybrid
8
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
9
Proposed New work Item SIRI Situation Model
New
• 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
10
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
12
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
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
The Bigger Picture Building
National & International models
Nick Knowles, CTO [email protected]
© Copyright Kizoom 2006
Incidents RT
(TPEG PTI)
Model Dependencies
PT Journey Planner
(JourneyWeb)
RT Timetable
(SIRI ET)
Road Journey Planner)
Departures RT
(SIRI SM)
Incidents RT
(SIRI SS)
Facilities RT
(SIRI FM)
Journey Times
Timetables
(TransModel)
Stop Place (IFOPT)
Road Network (XGDF)
Equipment
Types
Accessibility
Categories
GIS coords GML
16
Norms & Standards for Passenger Information Systems
Public Transport
Data
Reference
Transmodel
Road Information
IFOPT
GDF
Datex 2
Data Model
(Core)
Data Model
Dictionnary
Localisation
Network Reference
Data: TRIDENT
Inter-system
Data Exchange
XML Protocols
(TransXchange/VDV451-452)
SIRI
Facilities
OGC-GML
Events
Real-Time
Services
Communication
to end user
Web W3C
HTTP
Web Service
Wap I-Mode
SMS …
Datex 2
X-GDF
TPEG
RDS-TMC
17
Mapping
OS+ ITN Layer
DNF, XGDF
Points of
Interest
e.g. PointX
IFOPT
UK Public Transport Data
Exchange for JP: Use of
standards
Fares
FareXChange
Reservation
Stops
NaPTAN
Updates
Exchange
Data
Build
Engines
Bus Timetables
TransXChange
Operators
Updates
Exchange
Updates
Exchange
Data
Build
LBS/
Placefinder
Journey
Planner
Data
Build
Engines
Real-Time
StopEvents
Server
Vehicle
Services
Journeys
+ Fares
StopEvents
Distrib
ution
Timetables
Clients
StopEvents
Timetable
Train
Timetables
RJIS CIF
JourneyWeb
Places
IFOPT
Places,
Areas
NPTG
Dynamic Fares
Real-Time
Vehicles
Server
Connection
Connection
Common Abstract model (TransModel)
SIRI
IFOPT – Stop Place Model
Nick Knowles, CTO [email protected]
© Copyright Kizoom 2006
subplace of
Stop Place Introduction
1
IFOPT / TS278 SG6
Intro to
Stop Place
Model
StopPlace
StopPlaceId
• Nodes in an
interchange
• Stop Place /
Station
• Quay/Platform
• Boarding
Position
0..*
*
PublicCode()
StopPlaceName()
ShortName()
StopPlaceType()
neigbour of
is part of
*
levels1
1
1*
StopPlaceComponent
0..*
1
Level
has
0..1
is on
LevelCode
LevelName()
AbstractStopPlaceSpace
0..* 1
subzone of
Quay
-PublicCode
0..*
+QuayName()
+Label()
+DestinationDisplay()
+QuayType()
+Bearing()
1
has
BoardingPosition
PublicCode
0..*
© Crown Copyright 2007
BoardingPositionName()
Label()
BardingPositionType()
20
Administrative Model
• Distributed Management of data
21
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
22