|
1
|
- Brian Cronin
- Federal Transit Administration
- ITSA Annual Conference
- May 4, 2005
|
|
2
|
|
|
3
|
|
|
4
|
- Integrate existing knowledge
- Establish baseline data
- Develop information repository
- Leverage resources with concurrent activities and initiatives
|
|
5
|
- Conduct Basic Research
- Needs/barriers
- Solutions and strategies (ITS and overall)
- State of the practice/art
- Gaps and prioritization
- Validate with Stakeholders Input
- 4 discussion groups
- Private industry sounding board
- Federal program steering group
- Recommend next steps
|
|
6
|
- Five basic needs relative to transit trip making
- Understanding the systems and planning the trip
- Accessing the transportation from origin
- Entering, using or riding, and exiting the transportation
- Trip chaining and transferring between systems as needed
- Arriving at the destination
|
|
7
|
- Service availability
- Vehicle accessibility
- Information
- Financial status
- Funding
- Environmental situations
- Human interaction
- Service coordination
|
|
8
|
- Technological
- ITS
- Assistive technologies
- other
- Non-Technological
- Institutional/organizational
- Legislative
- Training & outreach
- Others
|
|
9
|
|
|
10
|
- Using a combination of advisory briefings and discussion groups to
- Validate and calibrate researchers hypotheses and technologies
- Solicit stakeholder inputs and strengthen stakeholders support for the
initiative
|
|
11
|
- Discussion Groups
- Consumer (Advocates) – 03/15/05
- Community and Non-Profit Transportation Agencies – 04/06/05
- Public Transit Agencies – 04/12/05
- Public Administrators – 04/12/05
- Federal Program Steering Group – 04/13/2005
- Private Industry Sounding Board
|
|
12
|
- Build upon existing technologies
- AVL / CAD
- Traveler information (web, 211/511, etc.)
- Scheduling Software, with improvements
- Leverage emerging technologies
- Connection Protection systems
- Financial management systems
- Funding, Eligibility, Invoicing
- Integrate systems and agencies
- Through web services
- Data standards
|
|
13
|
- Need to raise awareness of potential benefits
- Need for a champion
- To develop and maintain system
- Need to consider the human factor
- Undertake proper systems engineering approach
- Carefully document user needs
- Develop use cases
- Customer Centric
- Supplement with structured training program
|
|
14
|
- System must balance benefits from integration with personalization
offered by smaller, stove-piped services
- Must be sensitive to the possibility of winners and losers when
optimizing the system
- Design must be addressed in context of Eligibility and Funding
- System should be all-encompassing within a given geographic area
|
|
15
|
- 13 ongoing rural ITS transit operational tests focusing on mobility
enhancement and service coordination
- Major system functions
- Interagency, intermodal
- Customer management and eligibility
- Coordinated scheduling, dispatching, and routing
- Driver manifests and directions
- Mobility management
- Electronic fare system
- Cost sharing, billing, and reporting
- Traveler Information & trip planning
- Automated reservation, cancellation, confirmation, and notification
|
|
16
|
- Evaluation Plan
- Data Collection
- Data Analysis
- Evaluation Report
|
|
17
|
- Based on foundation research findings
- Assess and scope technology integration tests
- Draft TMCC concept of operations and system requirements
- Develop technology transfer and outreach plans
- Obtain DOT management approval for continuation
- Continue stakeholder participation
- Stakeholder facilitation
- Overall program stakeholder oversight and working groups
- Define Measures of Effectiveness (MOE)
|
|
18
|
- Your continuing participation and engagement is a key to the overall
success of the MSAA program
- For more information:
- www.unitedweride.gov
- www.its.dot.gov/msaa/index.htm
|
|
19
|
|