The document discusses Dublin City Council's real-time passenger information (RTPI) system, including how it provides arrival predictions for public transport, its integration across different modes and operators, and how open data access is being provided to allow third party developers to access RTPI data through web services. Key elements of the national RTPI programme are also outlined, such as working with operators to ensure accurate predictions and delivering integrated information through various channels.
3.
RTPI an essential element of any modern Transport system
Takes the guesswork out of when your bus will arrive.
Makes it possible to plan and reduces waiting on street.
Provides a public face on how a service operates.
DCC since 1994 had wanted to introduce RTPI but technically not
possible until fleet equipped.
When in 2009 RTPI was finally approved –
Dublin City Council Traffic Department undertook the task of delivering
it initially in Dublin and then throughout the country.
4.
Integrated Public Products
Integrated Real Time
Integrated Ticketing
Integrated Journey
Planner
INFORMATION
Real Time
Journey Planner
Leap Card
Virtuous Circle
The data behind these products
assists regulatory control to
improve services and produce
better information for to the
public
Monitoring and
Improving Public
Transport
Contracts
More Information
for Service
analysis
5. 3 Main Elements to the National Real Time Information
Programme
1.
Working with Public Transport Operators to ensure
accurate predictions
2.
Delivering integrated real time information to on street
displays in Greater Dublin Area, Cork, Galway, Limerick
and Waterford
3.
Delivering integrated real time information for Bus, Luas
and Irish Rail via www.TransportforIreland.ie, smartphone
apps and sms services.
6. AVL = Automatic Vehicle Location
Dublin Bus
Bus Éireann
Luas
Irish Rail
Other Operators
No Server &
Time estimation
system
CENTRAL
RTPI
SERVER
Website and Apps
Signs
SMS service
10.
Uses SIRI ET ( Estimated Timetable ) Dublin Bus
Journey Centric with ref to Timetable contained in VDV 452
Not suitable for use in Displays on Street as no Clear Down.
Same updates as with SM but much less data Transfer as it tracks
a journey and visits to each stop.
Uses VDV 454 ( Estimated Time Table ) Bus Eireann
Not suitable for use in Displays on Street as no Clear Down.
Same updates as with SM but much less data Transfer as it tracks
a journey and visits to each stop.
11.
12.
13. Interchange Display
• For Train/Bus Station
• Airport
• Hospital
•Multiple Stops
•Multiple Operators
14. DCC CENTRAL
RTPI
SERVER
AVL-equipped
fleet Init
SM feed
SM feed
Radio
comms
ET feed
Server & time
estimation system
ET feed
VDV 453 SM
feed
AVL-equipped
fleet Trapeze
GPRS
comms
Server & time
estimation system
Other Bus
operators
Not AVL-equipped
No Server & Time estimation
system
ET feed to
National
Journey
Planner
Website
VDV 454
SM feed to both
website and
signs
Luas
Irish Rail
Track based
estimation
Direct feed from
API to App only
Api database
open sky – will
facilitate
public API also
APP
SMS
service
15. • Provide Open data access for third Party Developers.
• Published Web Services Interface.
• Allows access to all RTPI data in the System.
• Queries can be made on Bus Stops.
• Currently being tested for DCC developed APP .
• Service hosted in the “Cloud “
• In Line with DUBLINKED initiative.
Web
Services
RTPI
System
SIRI SM
Open Data Platform
17.
Retrieve real time bus information for given stop
number.
Retrieve Timetable Bus Information by Date
Filtered by route and Operator
Filtered by Operator, route, Date and Stop ID
Retrieve Full Timetable Bus Information
Retrieve Bus Stop Information
Retrieve Route Information
Retrieve Real Time Route ( Bus position )
Information ( later release)
18.
19.
stopid - required, existing bus stop id
routeid – optional, route identifier
maxresults – optional, maximum number of results, if not
provided system will limit number of results depending on
server configuration
operator – optional, bus service operator (e.g. DublinBus), if not
provided information for all providers is returned
format – optional, valid values: xml, json; if not provided JSON
format is used by default
23.
XML:
<realtimeinformation>
<errorcode>[Error code]</errorcode>
<errormessage>[Additional error details]</errormessage>
<numberofresults>[Number of results]</numberofresults>
<stopid>[Stop Id]</stopid>
<timestamp>[Date/time information returned]</timestamp>
<results>
<result>
<arrivaldatetime>[Arrival time in dd/MM/yyyy HH:mm:ss
format]</arrivaldatetime>
<destination>[Service destination name]</destination>
<destinationlocalized>[Translated service destination name]</destinationlocalized>
<operator>[Bus service operator name]</operator>
<lowfloorstatus>[Bus low floor status (yes or no)]</lowfloorstatus>
<route>[Route]</route>
</result>
</results>
</realtimeinformation>
24.
First use is for the new App
APP will be released shortly
Some time to assess operation and determine
with Dublinked how it will be made available.
Release to Third part developers late Q1/Q2
2013
Suggestions for what to do with the data.????
Notas do Editor
Big impact for modest cost proposals, maximising use of existing infrastructure. Research shows that waiting time is a strong detterent for using public transport, and that 80% are report frustration
This was the system architecture as it developed and as the NTA received a collaboration between:The National Transport Authority as the funding and managing body; Dublin City Council as:IT system developer including the consolidated web site and SMS; Responsible for the procurement and design of on street signs;Local authority lead in the Greater Dublin Area for installing on street signage Local Authorities in Cork, Waterford, Galway and Limerick for installing on street signage in their local areas.Dublin Bus, Bus Eireann and other public transport operators, for the provision of predicted arrival time informationRTPI signage was first proposed by Dublin Bus, as part of their AVL proposal, the DoT rightly separated the elements, approving AVL but not approving a RTPI system that would be owned and operated by Dublin Bus In the absence of a regional transport authority, Dublin City Council proposed to the department that they would procure the infrastrucutre for outputting RTPI information on signs, sms and web and keep the system open to all participants who wished to avail of the service.Bus Eireann had a AVL was equipped in 2008. SCALE The Dublin Bus Network carries, on an average week day, approximately 400,000 passengers, on a fleet of 1,000 buses, stopping at approximately 5,000 stops. Dublin Bus carries 70% of all bus commuters in Dublin during peak times. When the number of stops are compared to LUAS (49 stops) and DART (31 stops), the extent and complexity of Dublin’s Bus system can be seen. Unlike trains or trams, the travle on the road network, stop more often and are subject to traffic congestion or disruptions. The NTA co-ordinating, managing and funding the project. Whereas a weakness in the original set up was that DCC had no formal relationship with bus operators, the NTA can exercise the legislative authority to require data and insist the operators prioritise the project. A lot of time was spend working on the interfaces, however this was a key requriement of having an open system
Each Arrow is a ProcessOperators requirements and responsibilitiesVehicle Control and Monitoring Equipment Control and Monitoring Process of technical and operational resolutionNTA responsibilitiesData interface requirementsContract Control Process of technical and operational resolution
This was the system architecture as it developed and as the NTA received a collaboration between:The National Transport Authority as the funding and managing body; Dublin City Council as:IT system developer including the consolidated web site and SMS; Responsible for the procurement and design of on street signs;Local authority lead in the Greater Dublin Area for installing on street signage Local Authorities in Cork, Waterford, Galway and Limerick for installing on street signage in their local areas.Dublin Bus, Bus Eireann and other public transport operators, for the provision of predicted arrival time informationRTPI signage was first proposed by Dublin Bus, as part of their AVL proposal, the DoT rightly separated the elements, approving AVL but not approving a RTPI system that would be owned and operated by Dublin Bus In the absence of a regional transport authority, Dublin City Council proposed to the department that they would procure the infrastrucutre for outputting RTPI information on signs, sms and web and keep the system open to all participants who wished to avail of the service.Bus Eireann had a AVL was equipped in 2008. SCALE The Dublin Bus Network carries, on an average week day, approximately 400,000 passengers, on a fleet of 1,000 buses, stopping at approximately 5,000 stops. Dublin Bus carries 70% of all bus commuters in Dublin during peak times. When the number of stops are compared to LUAS (49 stops) and DART (31 stops), the extent and complexity of Dublin’s Bus system can be seen. Unlike trains or trams, the travle on the road network, stop more often and are subject to traffic congestion or disruptions. The NTA co-ordinating, managing and funding the project. Whereas a weakness in the original set up was that DCC had no formal relationship with bus operators, the NTA can exercise the legislative authority to require data and insist the operators prioritise the project. A lot of time was spend working on the interfaces, however this was a key requriement of having an open system