Transcript Next Generation Transit Service Information Portal - Wiki

Next Generation Transit Service
Information Portal
REGIONAL STAKEHOLDER TWG
KICKOFF WEBINAR
MAY 4
1:30-3:30 PM
Agenda
 Transit Information and Data Industry Scan
 TSIP Project Overview
 Subject Matter Technical Working Groups
 Planning
 Real-Time
 Fare Collection
 SDP Maintenance and Data Processing
 TSIP Requirements and Specification
Transit Information and Data Industry Scan
 Data Topics
 Regional Transit Planning


What Transit Service Information are needed to support current
and emerging planning tools
Transit Situational Service Status
Real Time Information – ETA & Schedule Adherence
 Ad Hoc Schedules
 Incident reporting


Fare Data

Supports Regional “Fare Calculator”
Scan: Regional Transit Planning (existing)
 Focus: Regional Transit Planning requirements
 Data, Tools, Applications, Audiences, and Organizations
 Data: NY Regional Transit Planning data needs (performance
and metadata);
 Tools: Travel Demand Model, GIS / Spatial Analysis
 Applications: Travel Demand Forecasting, Air Quality
Conformity, Corridor Plans, Transit Development Plans
 Audiences: regional and service planners (strategic)
 Organizations: MPOs, Operating & Planning Agencies, Local
Jurisdictions, NYSDOT
 Request interviews from key organizations to learn
about existing regional planning requirements.
Scan: Regional Transit Planning (emerging)
 Industry Scan of emerging tools and techniques, and
their data needs



What are emerging planning tools? What can they do? What
are their data input requirements?
e.g., T-Best (FDOT)
(Are there other tools that you want to know about?)
 Is there a “Common Transit Planning Language”
Scan: Transit
Situational
Status
Types of Web
Services
Text Message
Control
Web Service



ETA, Schedule
Adherence
Incident reporting
Ad Hoc schedules
for events,
incidents and
disruptions to
regular service
Other information
Web Service or User
Interface
User
Prediction
Data
511 Phone/
IVR
Focus: Customer
Communications

Types of Presentation
Media
By Stop (agency,
route, route direction,
etc.)
Real-Time Sign
Controller
PDA or Mobile
Web Device
All routes at a stop
511 Table /Web
View
Agency Data
Transfer
Agency Transfer
Coordination
Within a coverage
area (e.g., map view)
By route and
direction
By Itinerary
Web Map View
Trip Planner
Logical Architecture for Delivering Situational Information
Transit Services used to Disseminate Incident
Reports to Customers
WMATA uses Service Disruption
Reporting Tool
Mass 511 Integrating Incident
Reporting information using
Web Services (concept)
Display Driver Message
Display Incident Report
Status Msg
(busID, blockID,
driverID, location, time)
Canned Incident
Message
(busID, driverID,
time, location)
Update Incident
Report
Transit Mgmt Center
CAD Server
Web Application
Web
Application
Web Service with
Event Report
[Automated
Interface]
Driver Console/
Key Pad
Web Service with
Real time bus location file
[Automated Interface]
SDRS report is automatically
generated when system is
delayed by X minutes
Assign message, priority,
security; automatically sends
certain messages to RITIS
Event Reporting
System (at Traffic
and Emergency
Management Centers)
RT Bus
Info
ERS Server
Mass511
Server
Specify web services
to exchange incident
and situational
information directly
in AVL/CAD
Scan: Transit Situational Status
(watch for survey)
Scan: Fare Data
(starting in late June)
 Focus: Data that drives a Regional “Fare Calculator”
 Scan of data models
 TRANSMODEL – Fare Collection Requirements & Business
Package
 TCIP 1.0 and 3.0 – Fare Collection Business Area
 UTFS (CFMS) – “Fare Policy Framework”
 Fare Calculation Tool Requirements
 Do you know of any of any tools?
 C-CAM / OMB “Common Accounting Language”
TSIP will provide Access
to Transit Service
Information.
Actors (users, systems)
can lookup and request
information via standard
interfaces.
Authorized Actors can
use services to view, edit,
or process data,
including key
stakeholder groups like
Regional Transit
Planners, Transit
Providers and
Customers
Transit Service Information Portal
Concept
Task &
Schedule
Task 2 & 3 – 11 Months
 Task 2: SDP Extensions
 Planning Data
 Real Time / Status Data
 Fare Data
Task 4 – about Month 6
 Task 3: TSIP Requirements
Task 5 – 11th Month
 Task 4: External TSIP
Requirements
 Task 5: Procurement Approach
TSIP Project Systems Engineering Approach
(similar to TSDEA project – current “artifacts”)
Concept of Operations
for
Regional Schedule Data
Repository
Trip Planning Use Case
Ad Hoc Scheduling Use Case
(includes 3 Use Cases of
downstream application
needs)
Static & Dynamic Timetables Use Case
Functional Requirements
of
Schedule Data needs
Physical Data Model
(to meet downstream
application requirements)
Prototype SDP &
Calendar XML Schema
Demonstration
Validate SDP XML Documents
with Downstream Applications
Timetable Publisher
(static timetable)
Timetable Generator
(dynamic timetable)
Web Data
Maintenance System/
Trips123
(trip planner)
Final Deliverables
Google Transit
(1) SDP Guidance Documents
(2) SDP XML Schema (final)
(3) Updated Functional Requirements Document
& Conceptual Data Reference Model
(4) Statewide Deployment Plan
SDP Planning Extension – Planning TWG
(Tasks and Deliverables)
Two white
papers:
-- scan of NY
regional planning
-- industry scan:
emerging tools
Concept of Operations
for
TSIP
(includes Use Cases for
downstream application
needs)
Transit Planning Use Case Submitting Data
Transit Planning Use Case Using Data
Planning Data Decomposition
Functional Requirement
Documents
(1) Planning Performance
Measures from SDP
(2) Additional SDP Data
Req’ts
Physical Data Model
Prototype SDP XML
Schema Extension
Demonstration
Validate SDP XML Documents
with Downstream Application
Final Deliverables
(1) SDP Guidance Documents
(2) SDP XML Schema (final)
(3) Updated Functional Requirements Document
& Conceptual Data Reference Model
Planning Application
or Report
Real-Time Status Extension – RT TWG
(Tasks and Deliverables)
White paper:
-- Industry scan:
Issues,
architectures,
standards
-- Survey on
Situational Data
Needs for region
Concept of Operations
for
TSIP
Provider View Use Case
Integration View Use Case
(includes 3 Use Cases)
Consumer View Use Case
Functional/Data
Requirements Document
(i) Real-time data from
Providers
(2) Web Service
Prototype RT XML
Schema & Dissemination
Web Service
Demonstration
(Technical Support)
Validate SDP XML Documents
with Downstream Applications
Final Deliverables
(1) SDP Guidance Documents
(2) SDP XML Schema and Web Service (final)
(3) Updated Functional Requirements Document
& Conceptual Data Reference Model
Any Volunteers ??
Fare Data – FC TWG
(Tasks and Deliverables)
White Paper
-- Industry scan:
Models, tools and
issues
-- NY Fare Policies
SDP Maintenance Project -- RSTWG
 Maintain SDP XML Schema et al with SDP Regional
Stakeholder Technical Working Group (RSTWG).
 Process Schedule Data (for NY511) – currently 6 data
sets; expect 11 by end of year.
 Develop registration web site to automate exchange:



Providers process, validate and load SDP, and
Consumers (NY511) get SDP
Other tools to view, edit, and disseminate SDP documents
 Support new providers: two close to ready; 1 under
development.
 Technical support to users and NYSDOT contractors as
needed.
Vision for a Next Generation Transit Service
Information Portal: TSIP RSTWG Role
Web Data Maintenance
System
511(s)
Trip
Planner
Ad-Hoc /Emergency
Scheduling Tools
Real-Time Info
Location/ETA Info
Transcom RA
Multi-Agency
Fare Info
Next
Generation
Transit
Service
Information
Portal
Connecting Modes
Detail
Facility Navigation
Detail
(ADA, Park & Ride, etc.)
OTHER
Multi-Operator
Exchange
(Operations/Coordination)
Integrated
Vendor Apps
(AVL/APC/AFC)
Third Party Information
Outlets
FOIL Requests
Planning MPO
Performance Reporting
Agency GIS
SDP
Plus
Open Source Apps
Timetable Publisher
Collaboration Tool – ngtsip.pbworks.com
Request
Access
Request Access
Fill in the Request (and wait for an email)
Wiki Next Steps
 Wait for email notification.
 Click here…
 Set up your account
Set up Account