T3 Webinar:
10/23/2008 — Arizona E-VII Program: Strategies for Improving Emergency Response to Traffic Incidents while Enhancing Safety for Emergency Responders
October 23, 2008
Text version of Webinar presentation:
"E-VII Arizona's Emergency VII Program
Description of image or images on a slide contained in brackets.
Back to Webinar Files
Slide 1: E-VII Arizona's Emergency VII Program
Slide 2: Today's Webinar Focus
- National Perspective on VII
- Update on Michigan and California VII Activities and Initiatives
- Arizona's E-VII Program Overview
- Concept Development and Applications
- E-VII Peer-to-Peer Exchange
- Outreach to Public Safety Community
- Questions for the Webinar Presenters
Slide 3: E-VII Website
http://www.vehicle-infrastructure.org
Slide 4: Today's Presenters
- Valerie Briggs, ITS JPO/RITA, VII Policy Program Manager
- Greg Larson, Caltrans, SAFETRIP Program Manager
- Faisal Saleem, Maricopa County DOT, E-VII Program Manager
- Larry Head, University of Arizona, E-VII Application Development
- Lisa Burgess, Kimley-Horn and Associates, E-VII Program Support
Slide 5: National VII Program Overview
Valerie Briggs
USDOT, ITS Joint Program Office
Research and Innovative Technology Administration
Slide 6: Arizona Emergency Vehicle Infrastructure Integration (E-VII)
Program Overview
Faisal Saleem, Maricopa County DOT
Slide 7: Arizona Crash Facts
Time...Lives...Money
- In 2006 alone in Arizona
- 3 people killed in crashes every day
- 1 person injured in a crash every 7 minutes
- More than 82% of crashes were in urban areas
- Motor vehicle crashes cost AZ $3.67 billion
- In Maricopa County, crashes had a $2 billion impact to the region's economy
Safety is the motivation for E-VII
Slide 8: Arizona Safety Vision & Goal
- VISION:
"Zero fatalities on Arizona roads, your life depends on it"
- GOAL:
In the first five years, this goal requires a reduction in the number of fatalities of approximately 12 percent. The first five year period will be 2008–2012, and the base year of comparison will be 2007.
Slide 9: E-VII Driving Force
VII TECHNOLOGY
HAS SIGNIFICANT POTENTIAL
TO ADVANCE SAFETY
THROUGH ENHANCED
EMERGENCY MANAGEMENT
Slide 10: Key Emergency Response Issues
- Average response time in urban areas from notification to arrival of Emergency response vehicle at hospital is about 35 minutes (For incidents that specifically involve vehicular accidents)
- Outcomes associated with injury trauma are time-dependent.
- In some cases saved time may be the difference between life and death or less damage to property.
- 20% – 25% of firefighter fatalities result from vehicle crashes
- Intersections are mostly likely locations for Emergency Vehicle to involve in crash
Slide 11: What is the Potential for VII?
[A photo of traffic congestion appears.]
- Reduce time for responders to reach incident scene
- Optimize Incident responder routing
- Improve safety for responders and for traveling public
- Streamline the different public safety/law enforcement platforms
- Advance the current technolog
y
Slide 12: Arizona E-VII Partnership
| FHWA |
Oversight and national liaison |
| Arizona DOT |
Arizona VII Program leadership and representation at National VII Coalition |
| Maricopa County DOT |
Arizona VII Program leadership and development, funding support, VII implementation, and program expansion |
| Univ. of Arizona |
Application research and development |
| Arizona State Univ. |
E-VII Evaluation |
| Kimley-Horn |
Program Support for Phase 1 and 2 |
| Econolite |
Equipment and field deployment support |
| OZ Engineering/Shel Leader |
Integration and field deployment support |
| Savari Networks |
Equipment and field deployment support |
| AZTech™ Partners |
Guidance and technical direction |
Slide 13: E-VII Builds on Strong Public Safety and Transportation Partnerships
- CAD feed from DPS, Phoenix Fire to transportation
- ALERT, REACT, Freeway Service Patrol collaboration
- Video sharing system with public safety (internet)
Slide 14: AZTech System Diagram
[A diagram appears of the flow of information for the AZTech E-VII System. The flow of information involves the following ITS applications and systems: the Traffic Management System (TMS), the Transit Orbital Vehicle Management System, the Regional Archived Data Server (RADS), Closed Circuit Television (CCTV), Dynamic Message Signs Center-to-Center s(DMS C2C), the Highway Condition Reporting System (HCRS), and Emergency Management System Center-to-Center.]
Slide 15: Initial E-VII Development
- AZTech™ / ATRC / MCDOT fundin
g
- Established local E-VII Coalition
- E-VII Proof of Concept selected in competitive process for ATRC funds
- Project Started Sept. 2007
Slide 16: Current Program Activities
- Review of other VII programs
- Developed concepts for Four capabilities
- Workshop with Public Safety and Peers
- Develop applications (V2V and V2I)
- 'Parking Lot' demonstration
- Evaluation
- Plan for next steps / broader deployment
- Study Dynamic Routing Requirements
Slide 17: Benefits and Anticipated Outcomes
- Unique Incident Management focus
- Reduce response times
- Enhance safety (responder, public)
- Establish ad-hoc communications network at incident site
- More timely and accurate traveler information directly from incident location
- Contribute in the development of national VII program (local proving ground)
Slide 18: E-VII Applications Development
Larry Head, University of Arizona
Slide 19: VII "101" — A Quick Reference
- RSU — Roadside Unit
- RSE — Roadside Equipment
- OBU — On-Board Unit
- OBE — On-Board Equipment
- GID — Geographic Intersection Description
- RADS — AZTech™ data server
Slide 20: E-VII Pilot Applications
[A photo appears of an auto mobile accident and a wether-realted incident.]
- Ramp meter priority / queue flushing
- Traffic signal preemption / priority
- Mobile incident warning (vehicle-vehicle)
- Transmit incident details back to center and other incident responders
Slide 21: E-VII Concepts
[A diagram appears that describes three stages in the development of the E-VII Concepts. Stage 1 is a demonstration of an emergency vehicles ramp meter flush. Stage 2 is demonstration of an emergency vehicle preempt signal. Stage 3 displays the ad hoc warning traveler information dissemination. The diagram shows how the traveler information is ultimately sent to the public via PDA through AZTech, the Regional Archived Data Server.
]
Slide 22: E-VII Capability 1 and 2: Preemption and Priority Operations at Intersections and Ramp Meters
- Secure preemption capability
- Support for multiple, simultaneous preemptions/priority requests
- Early gree
n
- Green extend
- Full preemptions
- Multi agency support
Slide 23: View Stage 1 and Stage 2 Animations
Slide 24: E-VII Capability 3: Vehicle-to-Vehicle Warning and Ad Hoc Network
[A diagram appears of the how the GPS Waypoints for ED Map works with Ad-hoc RSU]
- Units on board EV become transmitters, establishes an ad-hoc network
- Near-term — sends incident details to other responders:
- Location
- Severity
- Special requirements
- Future — communicate details to other VII equipped vehicles
Slide 25: View Stage 3 Animations
Slide 26: Demo E-VII On-board Display
[A screen shot of incident reporting software displaying current vehicle status appears.]
Slide 27: E-VII Capability 4: Response Vehicles Send Lane and Closure Information to TOC/TMC, and Disseminate through ATIS
[A picture appears of the Phoenix area traffic map along with an image of a dynamic message sign instructing travelers to dial 511 to obtain road conditions.]
Slide 28: View Stage 4 Animations
Slide 29: Demo E-VII Traveler Information Incident.Status Display
[A picture appears of a conceptual aerial view of an area in AZ that shows how traveler information incident status can be displayed.]
Slide 30: From Lab to Field
- Evaluated potential sites for field deployment test
- Controlled environment
- Limit interference of radio equipment
- Provide adequate accessibility to test drivers and evaluators
- Selected site on MCDOT property
- Trial runs at lab at Univ. of Arizona
Slide 31: E-VII Field.Demo Location
[An aerial map appears that displays the various locations in relation to the MCDOT Traffic Operations Building of different equipment and facilities that communicate an incident/accident.]
Slide 32: E-VII Demo System Architecture
[A diagram appears of the E-VII Demo System Architecture that demonstrates the flow of information between the Signal Controller and Ramp Controller.]
Slide 33: E-VII Field Demo Location
[A picture appears of two field workers. Two additional pictures display a Linksys roadside unit and an on-board unit mounted on a vehicle’s dashboard.]
Slide 34: E-VII Field Demo Location
[The first picture on this slide is an example of how an object in the road can trigger a Signal Preemption. The second picture displays how Ramp Meter Priority works in the field with various vehicles.]
Slide 35: E-VII Field Demo Location
[The first picture on this slide demonstrates how a computer can be used to generate an Incident Warning Alert. The second picture demonstrates two people in a parking lot with two vehicles involved in an Incident Beacon Ad-Hoc Network.]
Slide 36: E-VII Field Demo Signal Pre-Emption Video
Slide 37: E-VII Field Demo Ramp Meter Video
Slide 38: What E-VII Provides...
- Direct communications path to other response vehicles in the area
- Advances the mapping capabilities for emergency responders
- Reduces illegal preempts through more secure technology
Automates the interaction between public safety and transportation networks
- Proof of Concept looks at integration with legacy systems — what is the readiness of current networks/systems to support VII?
Slide 39: E-VII Evaluation Focus
- Issues/difficulties in implementing E-VII
- Cost-benefit analysis
- Potential delay savings
- Faster incident response (improved access at intersections, on-ramps and freeways)
- More effective signal phasing and timing for the vehicles affected by pre-emption
- Real-time dissemination of incident information to motorists
- Safety
- Perspective of emergency response personnel on safety and operations
Slide 40: E-VII Peer-to-Peer and Public Safety Forum
Lisa Burgess, Kimley-Horn and Associates, Inc.
Slide 41: Leverage Partnerships — Key Goal of E-VII
- E-VII wants to complement and learn from other VII deployers
- Unique incident management focus of E-VII
- Lessons learned from experienced deployers
- Technology
- Institutional issues
- Partnerships
Slide 42: April 24, 2008 — Peer Exchange Forum
- Invited Michigan, California and USDOT
- Local public safety community
- Comm. center managers, PSAP dispatcher
s
- Field responders — Fire, EMS, Police/Law Enforcement
- Morning — public safety forum and breakout groups
- Afternoon — VII Peer Exchange Meeting
Slide 43: Public Safety Input
- Overall, very positive about E-VII potential
- Could provide valuable dynamic routing info
- Critical gap are specifics about road/travel conditions on arterials
- Exact lane restrictions, work zones, one-way streets, LRT crossings, active RR crossing
- Integrate with current dispatch and vehicle
- Look at potential for providing on-scene details (video snapshots)
- Intersection warning capability (Code3)
- Communications interoperability a challenge — E-VII can bridge that gap
Slide 44: Peer-to-Peer Discussion
- Focus on applications first, field deployment later
- Engage cities/field equip owners early — state DOT cannot do it alone
- Leverage standards development in MI, CA, national activities
- IM is a niche focus — other states eager to follow progress, look for ways to partner
Slide 45: E-VII Next Steps — Dynamic Routing
- Outcome from public safety forum
- Responder information needs
- Field responder
- Dispatch/communications
- How best to deliver info to responders en-route
- Integration of real-time vehicle network data (E-VII) with ADOT HCRS and RADS
- Integration with public safety CAD
Slide 46: Routing Challenges for Emergency Vehicles
[AN aerial map appears that displays the location of an incident/accident.]
- Incident location reporting.
- Precise routing details and info.
- Geographic identifiers.
- VII standards
Slide 47: Dynamic Routing Project Moving Forward
- Accepted for ADOT FY09 Research Funding
- Concept plan for how to deliver real-time routing information to responders
- Avoid congestion
- Precise ramp and lane restrictions
- Avoid LRT/rail conflicts
- Faster, safer response to incidents
- Real-time system for day-to-day use
- Complements current ADOT evac planning
Slide 48: How Will E-VII Shape the Future?
- Advance and automate the transportation/public safety interface
- Operational safety for emergency responders
- Equipment/interface requirements
- Transportation management
- Emergency response vehicles
Slide 49: E-VII Contact Information
back to top
