1. Dixie Regional ITS Architecture Stakeholder Meeting #2 June 15, 2006

2. Today’s Agenda Introductions Overview of ITS Translating Needs to ITS Projects Proposed Projects ITS Project Funding Opportunities Group Exercise Project Discussion

3. Welcome and Introductions Dixie Regional ITS Architecture

4. What is ITS? Roadway Management Rural Systems Transit Systems Goods Movement Emergency Management Traveler Information Maint. and Construction

5. Roadway Management Signal control Monitoring Coordination Data Collection

6. Roadway Management Automatic warning systems Enforcement Support

7. Traveler Information Dynamic message signs 511 Websites Kiosks Highway Advisory Radio

8. UDOT 511

9. UDOT Traffic Cams

10. Goods Movement Weigh in Motion Security Monitoring/HAZMAT Vehicle Routing

11. Rural Systems Crash Prevention and Response Animal-vehicle Interaction Roadway maintenance Roadway control

12. Emergency Management Signal Preemption Dynamic Routing Coordinated Response Incident Management

13. Transit Systems Transit vehicle tracking Demand response transit operations Transit security Multi-modal coordination

14. Construction and Maintenance Automated work zones Improved Information Construction Safety

15. Project Scope Dixie Regional ITS Architecture

16. Architecture Scope Washington County City, county and state roads National Forest Indian reservation Major cities St. George Hurricane Ivins Santa Clara Washington

17. Architecture Scope Invited Stakeholders Cities County UDOT Commerce Indian Reservation Trucking Emergency Responders Neighboring Cities, states and counties

18. Mapping Needs to Projects Dixie Regional ITS Architecture

19. Architecture Process Inventory Needs Services Provided by ITS to Address Needs Functions Roles & Responsibilities System Interfaces and Info Flow Stakeholder Input

20. Dixie Region ITS Needs Collected through discussion and meetings Needs are prioritized as high, medium and low Needs are a summary of the stakeholder and Steering Committee input Eight Needs Categories

21. Arterial Traffic Management Needs (Highlights) Improve Incident Response Improve Emergency Response Reduce Intersection Delays Improve Traffic Control (monitoring, signal coordination, etc.) Improve Management during events and high traffic periods

22. Freeway Management Needs (Highlights) Improve Interagency coordination Improve Incident Detection and Response Improve Management during events and high traffic periods Improve Interchange Traffic Patterns Reduce Congestion

23. Public Transportation Needs (Highlights) Improve Transit Information and Service Notifications Be Able to Track Fleet Locations Improve Fixed and Dial-a-Ride Scheduling Improve Interregional Trip Planning

24. Maintenance and Construction Needs (Highlights) Coordination Traffic Control Plans Among Agencies Improve Work Zone Traffic Handling Increase Use of Signs and Traveler Information Systems Improve Ability to Detour Traffic Around Zones

25. Maintenance and Construction Needs (Highlights) Coordination Traffic Control Plans Among Agencies Improve Work Zone Traffic Handling Increase Use of Signs and Traveler Information Systems Improve Ability to Detour Traffic Around Zones

26. Regional Traveler Information Needs (Highlights) Improve Quality and Timeliness of Information Increase Quantity of Traveler Information Target Some Information for Tourists/Travelers Provide Real-time Travel Time/Congestion Information

27. Commercial Vehicle Operations Needs (Highlights) Provide Interstate and Regional Traveler Information Provide Information on Winter/Weather Restrictions Improve Congestion Management During Seasonal/Local Events

28. Integration Needs (Highlights) Improve Information Sharing Among Agencies Develop an Integrated GIS for the Region Develop Interagency Memorandums of Understanding to Facilitate Information Sharing and Project Coordination

29. What Happens to Needs? They are mapped to User Services Faster emergency response time Emergency Vehicle Management Route Guidance (AVL) Signal Preemption Need User Service Functions

30. What Happens to Needs? Functions are mapped to Dixie Region ITS Projects that will deliver them Route Guidance (AVL) Signal Preemption Functions Emergency Automated Vehicle Tracking Emergency Vehicle Preemption Projects

31. Proposed Dixie Region ITS Projects Dixie Regional ITS Architecture

32. Dixie Region ITS Corridors Timeframes: Near, Mid and Long Improved landline communications Improved signal interconnect and coordination Closed circuit cameras for traffic monitoring and incident detection Trailblazer and Dynamic Message Signs for directions and traffic information Signal preemption for emergency vehicles in key areas NEEDS ADDRESSED: Improve System Operation Monitoring Improve arterial management strategies Improve signal optimization Improve traffic flow monitoring Improve signal timing and control Etc.

33. Dixie Region ITS Corridors

34. Emergency Vehicle Preemption Timeframe: Near Term Allows emergency vehicles to preempt signals Improves incident response times Currently proposed for critical corridors May adversely impact traffic signal coordination NEEDS ADDRESSED: Reduce emergency vehicle delays Improve incident response times Improve intersection safety for emergency vehicles Improve response to hazardous material spills

35. Traffic Control Center Timeframe: Near Term Develop a larger facility that can house multiple agencies Expand data sharing and data collection abilities Improve incident detection and reporting Improve monitoring and surveillance NEEDS ADDRESSED: Improve system operation monitoring Improve management strategies Improve signal optimization Improve signal control and timing Improve roadway traffic surveillance Etc.

36. Trailblazers Timeframe: Near Term Strategically located signs to direct traffic Inexpensive traffic routing Electronic signs can be used for events or incidents NEEDS ADDRESSED: Provide alternate routes Improve traveler information/route suggestions Expand traveler information delivery methods Better manage traffic flow to recreation areas Better manage periods of high traffic demand

37. Dixie Regional Emergency Operations Center Timeframe: Near Term Expanded facility compared to current dispatch center Accommodate other agencies Monitor traffic conditions Provide facilities for the media Improve emergency and disaster response capabilities NEEDS ADDRESSED: Improve incident response coordination Improve incident detection Better information dissemination Improve ability to detect and warn about floods/fire/etc. Improve information sharing among agencies

38. Dispatch Integration with CommuterLink Timeframe: Near Term Links the dispatch with the traffic information system Provides a means for disseminating incident and event information Gives the Region access to other event and incident information NEEDS ADDRESSED: More timely traffic information dissemination Provide real-time congestion information Improve ability to detect and warn about floods/fires/etc. Provide timely, accurate information about roadway conditions

39. Incident Management Strategies Timeframe: Mid Term Develop information sharing systems Strategies for interagency coordination Tracking and sharing resources that may be used to respond to incidents NEEDS ADDRESSED: Improve incident response coordination Improve incident detection Better information dissemination Improve information sharing among agencies Coordinate traffic control plans among jurisdictions Develop interagency agreements

40. Incident Response Vehicles Timeframe: Mid Term Fast deploying vehicles equipped for incident response Perform cleanup and traffic control Can control message signs and signals, take pictures May roam or be dispatched NEEDS ADDRESSED: Improve incident response coordination Improve incident detection Better information dissemination Improve traffic surveillance Improve incident management Increase use of traffic control equipment Provide rapid mobile response to incidents

41. CommuterLink Marketing Timeframe: Mid Term CommuterLink is a statewide traveler information system Promote the use of CommuterLink for information dissemination Encourage the development of systems that integrate with CommuterLink NEEDS ADDRESSED: Provide quality real-time congestion information Expand traveler information delivery methods Improve quality and timeliness of communications Improve targeted information for tourists

42. Maintenance Coordination Timeframe: Mid Term Develop systems for sharing maintenance information among agencies Establish agreements for interagency and other entities maintenance and construction planning Coordinate maintenance plans NEEDS ADDRESSED: Improve coordination on construction notification and information distribution Coordinate traffic control plans between jurisdictions Interagency coordination on placement of maintenance vehicles

43. Road Weather Smart Systems (Flood Warning) Timeframe: Mid Term Deploy detectors to sense water levels and report them to Traffic Control and Dispatch Provide alerts to travelers of existing and impending flooding NEEDS ADDRESSED: Improve ability to detect and warn about floods Improve incident detection Improve traveler information

44. Improved Traveler Information Timeframe: Long Term Develop means for providing traveler information Coordinating with CommuterLink Providing kiosks in tourist areas Providing telephone and Internet access to roadway conditions NEEDS ADDRESSED: Provide quality real-time congestion information Provide quality construction and maintenance information Improve ability to detect and warn about floods/fires/etc. Expand traveler information delivery methods

45. Transit Vehicle Tracking Timeframe: Long Term Track the location of transit vehicles using GPS and transit center mapping Improve scheduling and run-cutting Improve routing efficiency NEEDS ADDRESSED: Improve patron safety Enable SunTran to locate bus fleet Improved service planning

46. Transit Operations Upgrade Timeframe: Long Term Upgrade dispatch, reporting and accounting software for transit operations Integrate transit information into the regional information systems NEEDS ADDRESSED: Improve regional and interregional trip planning Improved information exchange Improved service planning Improved back-office systems Improved transit transfers

47. ITS Funding Opportunities Dixie Regional ITS Architecture

48. Funding Strategies Prioritize ITS Include it in plans and recognize what ITS has high benefit to cost ratios Include it in your plans Take the money available Reprioritize projects based on what money is available Obligate a small percentage of some roadway projects to ITS Use this plan to justify your ITS needs

49. Local Funding Local funding may be available by “mainstreaming” ITS projects into the transportation plans Incrementally adding ITS to traditional roadway projects Defining ITS project priorities to compete with traditional projects Partnerships among local agencies to share costs

50. State Funding State funding may be available for projects that impact or share state facilities Interchanges, state and US highways Incorporate ITS into roadway projects by setting a percentage to be used for ITS Finding statewide programs such as transit or air quality that may have funds Partnerships among local agencies to share costs

51. Federal Funding Federal Transit Administration Funds A recent emphasis on small transit operations Federal Highway Administration Funds A completed architecture qualifies the region for Federal funds to be used for ITS Research funds for innovative projects Homeland Security Flood and fire warning Infrastructure protection

52. Group Exercise Dixie Regional ITS Architecture

53. Today’s Exercise Small groups of 4-7 people Review the project list and comment on: Coverage area Stakeholders ITS devices or plan Other projects? Other elements not included in existing projects?

54. Next Steps Dixie Regional ITS MPO Architecture

55. Next Steps Revise projects and estimate budgets Develop an Implementation Plan Project list Architecture Maintenance Define needed agreements Plan Final Stakeholder Meeting End of July

56. Questions and More Information Dian Williams, UDOT 801-887-3457, dianwilliams@utah.govdianwilliams@utah.gov Gary Zabriskie, Dixie MPO 435-673-3548, gzabriskie@fcaog.state.ut.usgzabriskie@fcaog.state.ut.us Matt Weatherford, Iteris, Inc. 720-898-0265, mrw@iteris.commrw@iteris.com