|
1
|
|
|
2
|
- Where We Have Been
- Where We Are
|
|
3
|
- Pre-ISTEA (Before 1991)
- Mobility 2000 Working Group
- Convened by FHWA
- Recognition that building new infrastructure is not the only option
- Technology offered new opportunities
|
|
4
|
|
|
5
|
|
|
6
|
|
|
7
|
|
|
8
|
|
|
9
|
|
|
10
|
|
|
11
|
- Overview of the Current ITS Program
- Major ITS Initiatives
- Technology Transfer Initiatives
|
|
12
|
- Clarus will develop and demonstrate a high resolution, integrated
weather observing, forecasting and data management system, featuring a
road weather observational database capable of generating required
information
- System will enable public agencies to implement advisory, control and
treatment strategies to improve mobility and safety
- Upon completion system will be transferred to NOAA
|
|
13
|
- Program strategy is to:
- Integrate existing state and local networks, as well as NOAA assets for
road weather applications
- Develop partnerships across the surface transportation and weather
communities (FHWA and NOAA )
- Provide multiple mechanisms to communicate improved road weather
information to transportation managers and travelers
- Key milestones include:
- Clarus Multi-state Regional Demonstration – Jan 2008
- Proof of concept demonstration (with participation by Utah, Minnesota
and Alaska) – Completed – Dec 2006
- Development awarded – Sep 2008
- Development completed – Sep 2010
- Clarus – Compatible Road Weather Information System Deployment Kit
Completed – Sep 2010
- Convergence with NOAA – Dec 2011
|
|
14
|
- Cost/Proposed Budget (SAFETEA-LU Mandated):
|
|
15
|
- Objective:
- Use vehicle and infrastructure-based technologies to warn drivers in
time and avoid potential crossing-path crashes at intersections
- Determine effectiveness of technologies and driver acceptance
- Development of objective test procedures
- Ultimate inclusion of intersection collision avoidance systems in
NHTSA’s NCAP rating system
- How to Achieve:
- Combine vehicle-based and infrastructure-based technologies into 3
applications to warn and assist drivers
- Signal and stop sign violation
- Signalized left turn assist
- Stop sign assist
|
|
16
|
- Historical Timeline
- Initiative began in 1st quarter of FY 2005
- Project Completion:
- Three tracks on different schedules
- Signal and stop sign violation field tests and benefits assessment by
Sep 2010
- Completion of all field tests is planned for FY 2011
- Status:
- Signal and stop sign violation – ConOps developed, prototype being
developed, real world engineering tests underway in CA, MI, and VA
- Signalized left turn assist – initial research completed, observational
research studies conducted
- Stop sign assist – initial concept, alert-timing development, and
simulator studies being conducted
|
|
17
|
|
|
18
|
- Objective:
- Reduce congestion in major urban areas through application of transit,
tolling, technology, and telecommuting initiatives
- Demonstrate significant improvements in congestion:
- Targeting 10% - 20% reduction in travel time
- Travel time reliability
- Transit ridership improvement
- Greater peak hour throughput
- Lessons learned from the 5 urban partners – travel behavior, operations,
and technical, and institutional issues
|
|
19
|
- Program strategy is to:
- Select urban partners
- Establish evaluation plans
- Showcase the concepts
- Historical Timeline
- Initiative began 1st quarter of FY 2007
- Preliminary partner selection – June 2007
- Announced awards – August 2007
- (1) San Francisco (2) New York City
- (3) Miami (4) Minneapolis
- (5) Seattle (6) San Diego (smaller award)
- Initiate projects – FY 2008
|
|
20
|
- Project Completion:
- FY 2010
- Status:
- Six projects will be initiated in FY 2008
- Evaluation will be initiated in 2008
|
|
21
|
- Objective:
- Promote and evaluate innovative e-business concepts
- Enable process coordination and information sharing for supply chain
partners through public-private collaboration
- Program strategy is to:
- Conduct the Columbus EFM deployment test by implementing all the
components of the Architecture necessary to support a select Limited
Brands International “truck-air-truck” supply chain.
- Historical Timeline:
- Developed a freight information highway architecture
- Created transportation web services
- Developed an implementation guide for new users
- Developed international freight standards
|
|
22
|
- Project Completion:
- Final EFM evaluation report in May 2008
- Status:
- Complete adoption strategy to build awareness through:
- Expansion to all modes of transportation
- Expansion of architecture and standards based upon business
requirements
- Cost-Benefit analysis to support adoption
- CEFM FOT has been initiated
- FOT evaluation in-progress; objectives include:
- System usefulness
- Cargo visibility
- Supply chain and logistics performance
- Deployment scalability (from CEFM to EFM)
- Continue joint presentations with project partner champions at key
conferences
- Develop critical guidance documentation
- Solicit other partners to explore additional supply chain linkages
|
|
23
|
|
|
24
|
- Objective:
- Foster the development of tools and processes that support
transportation systems operators during emergencies
- Promote faster and better prepared responses to major incidents and
evacuations
- Program strategy is to:
- Engage a wide range of stakeholders to determine their needs
- Apply ITS to support safe and efficient transportation operations during
emergencies
- Plan for the management of transportation-related emergencies including
those requiring evacuation
|
|
25
|
- Historical Timeline:
- Project began in 4th quarter of FY 2004
- Determined technical requirements, developed operational procedures, and
evaluated the use of camera phones to improve incident response
- Developed practitioners toolkit for using ATIS during emergencies
- Developed comprehensive guidance documentation on evacuation planning
methodologies and decision support tools; currently refining follow-on
products
- Project Completion:
- Project deliverables completed:
- Camera Phone Proof of Concept Guidance Report
- Communicating with Public Using ATIS During Disasters: A Guide for
Practitioners
- Evacuation Operations Modeling Assessment
|
|
26
|
|
|
27
|
- Objective:
- Reduce traffic congestion and improve safety through integration of
management capabilities across all modes in a corridor setting
- Working with 8 sites to develop concepts of operation
- Developing and validating analysis, modeling, and simulation (AMS)
methodologies
- Demonstrating capabilities at 3 pioneer sites
- Program strategy is to:
- Provide institutional guidance and operational capabilities
- Provide policies, strategies, and tools to implement ICM systems
- Select AMS methodologies sites
- Select “Pioneer Sites” for demonstrations
|
|
28
|
- Historical Timeline
- Initiative began in 1st quarter of FY 2005
- 8 pioneer sites completed their respective ConOps spring 2007
(Minneapolis; Dallas; Houston; San Antonio; San Diego; Oakland, MI;
Seattle; and Montgomery County, MD)
- Decision to proceed with 3 selected Pioneer sites for AMS – Dec 2007
- Project Completion:
- FY 2010
- Status:
- Eight Pioneer sites completing their requirements documentation
- Develop modeling and analysis approach for evaluation of alternative
strategies
- Select 3 finalist sites
|
|
29
|
|
|
30
|
- Objective:
- Accelerate the commercial availability of integrated safety systems in
the U.S. light vehicle and heavy commercial truck fleets
- Reduce driver workload and reaction time to prevent conflicting
warnings, reduce false alarms, and reduce unintended consequences from
accident avoidance
- Program strategy is to:
- Conducting FOTs of light and heavy vehicles
- Focus on three areas
- forward-looking collision warning
- road/lane departure warning
- lane-change collision warning
- Develop prototypes incorporating integrated driver assistance systems
(forward-looking collision warning; road/lane departure warning;
lane-change collision warning)
|
|
31
|
- Historical Timeline:
- Initiative began in 1st quarter of FY 2005
- Draft verification test procedures completed June 2007
- Light vehicle and heavy truck verification tests completed November 2007
- Conduct FOT of advanced technologies in light vehicles and heavy trucks
(Phase 2)
- Project Completion:
- Project completion in December 2009
- Status:
- Phase 2 begins
- Vehicle fleet will be fabricated and tested
- Limited FOT will begin to check conflicts, near crashes, severity of
near crashes, driver acceptance
|
|
32
|
|
|
33
|
- Objective:
- Use ITS to improve effectiveness and efficiency of human service
transportation through:
- customer-based travel information and coordination
- across modes, social welfare programs, and geographic areas
- Program strategy is to:
- Develop concepts of operations for coordinated services for 8 sites
- Demonstration at 2 sites
- Follow 6 non-selected sites for independent development of coordinated
services
- Historical Timeline:
- Complements the Federal interagency United We Ride national initiative
- Presidential Executive Order requires federal agencies to work together
to enhance transportation access and minimize duplication of services
- Project began in 4th quarter of FY 2004
- Phase 1 sites (8) announced January 2007
- Demonstration workshop to kick off phase 1
- Release MSAA stakeholder outreach and technology transfer plan for
review and comment
|
|
34
|
- Project Completion:
- Complete demonstration evaluations in June 2010
- Status:
- Complete model designs in July 2008
- Phase 2 sites (2) selection in December 2008
- Concepts of Operations development for 8 sites
- Aiken, SC
- Atlanta, GA
- Cherry Hill, NC
- Fitchburg, MA
- Kent, OH
- Louisville, KY
- Orlando, FL
- Paducah, KY
|
|
35
|
|
|
36
|
- Objective:
- Establish the foundation for public emergency communication in a
wireless, mobile society
- Enable 9-1-1 access (voice, data & video) via modern communication
devices currently available and used by the public
- Improved safety, reduced congestion, improved mobility
- Program strategy is to:
- Define a system architecture
- Develop a transition plan for deploying IP-based emergency services
across the U.S.
- Demonstrate aspects of the architecture in up to 5 Public Safety
Answering Points (PSAPs)
|
|
37
|
- Historical Timeline:
- Initiative began in 1st quarter of FY 2005
- Architecture analysis report reflecting open systems design for
receiving and managing emergency information
- Developed and validated requirements for the NG 9-1-1 system
- Published a preliminary concept of operations
- Implemented a Strategic Outreach Plan
- Project Completion:
- The final transition plan is expected to be completed in November 2008
- Status:
- Proof of Concept demonstration by September 2008
- Final transition plan in November 2008
|
|
38
|
|
|
39
|
- Objective:
- Develop and test an information infrastructure using advanced
communications technologies to exchange real-time information between
the roadside and vehicle and vehicle–to–vehicle in support of safety,
mobility and commercial applications
- Determine technical feasibility, economic viability, and social
acceptability of a nationwide deployment of VII
- Perform the necessary research in the areas of technology, applications,
and policy to facilitate a nationwide deployment
- Program strategy is to:
- Demonstration of near-term VII capabilities by Dec 2008
- Refocus Proof of Concept (POC) test to support research for phased
deployment
- Define phased deployment strategies that will capitalize on commercially
available products and services
- Identify business models and governance approaches that leverage
public-private partnerships
- Leverage technology evolutions to enhance system capabilities
|
|
40
|
- Historical Timeline:
- Initiative began in 4th quarter of FY 2004
- Project Completion:
- Demonstration operational – Dec 2008
- Research program timeline under development
|
|
41
|
- Status:
- Volpe team has been identified to develop and implement the
demonstration field test
- Proof of Concept test laboratory (Herndon, VA) is operational
- Proof of Concept test bed in MI conducting final software beta-testing
- Cost-benefit model development is ongoing
- Business models, management models and privacy policies underway
- Proof of Concept testing to be completed April 2008
|
|
42
|
|
|
43
|
- The ITS Program Assessment Program collects and analyzes data from ITS
deployments, and develops knowledge products to support investment
decision-makers; planners; deployers; operators; and maintainers
- Major Program activities include:
- Field Evaluations of
deployment/integration projects; field operational tests; and model
deployments
- Tracking deployments of ITS
infrastructure and evolution of the state of the ITS practice
- Documenting benefits, costs and
lessons learned
- Supports informed decision making by transportation leaders
- Contains results of evaluations of deployed ITS (transportation
impacts)
- Documents the costs of ITS deployments (unit and system)
- Captures experiences of stakeholders in their planning deployment,
operations, maintenance and evaluation of ITS
|
|
44
|
- Key recurring products include:
- ITS Benefits, Costs, Deployment Statistics and Lessons Learned Update
Report – Biennial
- ITS/Operations Resource Guide – Annual
- Extensive compilation of evaluation reports; Cross-cutting studies;
Leaflets; Brochures; Case studies
- Field Evaluation Activity during the era of TEA-21 comprises:
- Independent field evaluation of 32 TEA-21 ITS Integration Program
earmarks
- A small subset of the total carefully selected for high value
evaluation results
- 20 reports received for analysis and development of lessons learned
- Support and mentoring of 430 earmarked projects conducting
self-evaluations funded from local resources
- > 90 Self-evaluation reports received for analysis/development of
lessons learned
|
|
45
|
- Deployment Tracking has evolved into the State of the Practice Website –
not just “how much deployed” but “how deployed”
- Only national source of ITS deployment information available at no cost
- From 1996-to-2007, 17,434 surveys distributed with average response
rate > 92%
- Collects deployment data on all categories of ITS (freeway, arterial,
statewide/rural, etc)
|
|
46
|
|
|
47
|
|
|
48
|
|
|
49
|
|
|
50
|
|
|
51
|
|
|
52
|
- Status:
- TEA-21 ITS Integration Program Earmark independent field evaluations in
progress - 12
- Non-earmarked project field evaluations started 40 (30 reports received
and 10 in progress)
- ITS Major Initiative evaluations in progress - 2
|
|
53
|
- Objective:
- Development (completed) - a consensus based architecture, integrating
multiple transportation systems, and utilizing open ITS standards
- Maintenance (ongoing)
- Ensure a current National ITS Architecture is available
- Reflect the latest concepts in the transportation and ITS industries
- Respond to stakeholder interests and concerns
- Program strategy is to:
- Retain a small team of ITS Architecture professionals
- Ensure that the team includes field experience at the regional level
- Transfer technology through proactive support by architecture team
|
|
54
|
- Historical Timeline:
- Development completed 1996
- Architecture training program (2500+ students, 150+ courses)
- Architecture development workshops to assist regions (80+)
- Turbo Architecture software tool developed to assist regions
- FHWA Rule on National ITS Architecture and Standards issued 2001
- Added four new user services 1997 - 2003
- Architecture use and maintenance workshops developed (10 in 2007)
- National ITS Architecture Version 6.0 issued 2007
|
|
55
|
- Status:
- Determine quality of sample of regional ITS architectures – FY 2008
- Integrate concepts from VII, ICM, and Clarus initiatives – FY 2008
- Continue to review stakeholder comments and enhance functionality of
Architecture and Turbo Architecture software tool
|
|
56
|
- Objective:
- Development (near completion of version 1)
- Develop consensus based open ITS standards
- Enable a seamless national transportation system
- Test to ensure better developed standards
- Broad use of open ITS standards
- Maintenance (ongoing)
- Changes based on field comments from deployment
- Major changes require a second or third version of the standard
- Program strategy is to:
- Use SDOs (AASHTO, ASTM, IEEE, ITE, NEMA, SAE, and APTA)
- Ensure coordination through state, and private sector personnel
- Accelerate technology transfer by making ITS standards available at no
cost
- Standards development is decreasing; Standards testing is increasing
- Developing Standards Strategic Plan per TRB recommendations
|
|
57
|
- Historical Timeline:
- Development began as outgrowth of Architecture program in 1996
- Determined the standards that would be developed (106)
- Conducted standards training courses throughout the country
- Conducted workshops
- Developed standards guides to facilitate deployment
- Developed Website as the focal point of current status and information
about ITS standards
|
|
58
|
- Status:
- Program lean and nearing completion of version 1 development
- 88 published, 8 approved, 5 in ballot, 5 under development
- Testing at four sites – Texas, Idaho, New Hampshire, Florida
|
|
59
|
- Objective:
- Expand the knowledge, skills, and abilities of the ITS workforce
- Foster the professional development of the ITS professionals
- Enlighten both decision makers and the public
- Support major U.S. DOT initiatives, regulations, and policies
- Program strategy is to provide:
- Training
- PCB classroom course curriculum for nearly 40 courses
- (Click here to view the list of PCB Classroom Courses )
- T3 Webinar series of internet and telephone PowerPoint presentations
- Web-based training courses developed with CITE
- Education
- Catalog of ITS courses offered by U.S. universities and colleges
- Partnership with CITE
- Link to University Transportation Centers to transfer research and
knowledge into the PCB courses
- Technical Assistance
- ITS Peer-to-Peer program
- ITS Helpline
|
|
60
|
- Project Completion:
- Continual with personnel turnover, ensuring updates in all three areas
on a regular basis
- Status:
- Develop cooperative training/education efforts with associations and
universities
- Provide 15 or more Webinars
- Provide technical assistance and technology transfer
- Provide 10 or more special workshops on selected ITS topics
|
|
61
|
|
|
62
|
|