1 / 29

Regional ITS Architecture and Deployment Plan

Learn about the development process and deployment of a regional ITS architecture in line with federal regulations, covering various traffic and emergency management aspects. The plan includes projects tailored to regional needs and is based on user feedback.

farrah
Télécharger la présentation

Regional ITS Architecture and Deployment Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Outline • Project Background • ITS Architecture Overview • GVMC ITS Architecture • Deployment Plan

  2. Project Background • Funded by MDOT • Revision of current Regional ITS Architecture • Includes the geographic area covered by the GVMC MPO boundary • Project started June 2010, will complete April 2011

  3. Why Develop a Regional Architecture? • Deploy Integrated Systems • Deploy with Regional Needs in Mind • Manage Complexity • Match Needs with ITS Components • FHWA and FTA requirement for projects using federal funds

  4. National ITS Architecture • Complex! • 375 Processes • 2500 Data Flows • 91 DFD’s • Processes and Data Flows

  5. Information From Emergency Mgt to Traffic Mgt • Incident_Duration • Incident_Location • Incident_Number • Incident_Severity • Incident_Type

  6. Incident Type • “This data flow is used within both the Manage Traffic and Manage Emergency Services functions and defines an incident type using a three character code. This will use a standard set of character codes to uniquely define the type of incident. “

  7. Information From Traffic Mgt to Emergency Mgt • Incident_Video_For_Emergency_Services • Traffic_Data_For_Emergency_Services

  8. What Traffic Data? • Link_List • Link_Size • Vehicle_Count • Vehicle_Headway • Vehicle_Occupancy • Vehicle_Queue Length • Vehicle_Speed

  9. Using the Regional Architecture • Supports Varying Levels of Sophistication • Supports Varying Levels of Inter-Agency Integration

  10. ITS Architecture Development Process System Inventory ITS Architecture Workshop Draft Architecture Document IDAS Analysis & Deployment Plan Development ITS Deployment Plan Workshop Final Report ITS Architecture Development Draft Final Report June 2010 August 2010 January 2011 March 2011

  11. GVMC Boundary

  12. Concurrent Projects • Regional ITS Architectures and Deployment Plans • Statewide; Grand Region; Southwest and Portions of University • SEMCOG; Bay Region; North Region; Superior Region; TCRPC • Statewide ATMS Software • STOC Implementation • Other ITS Projects in GVMC area • GVMC Expansion Project • West Michigan TMC

  13. Review of User Needs • Expanded surveillance on freeways • Improved coordination with media • AVL technology for maintenance vehicles • Improved coordination between 911 dispatch facilities • Signal Priority for Transit Vehicles • Better access to crash data

  14. ITS Architecture Program Areas • Traffic Management (ATMS) • Emergency Management (EM) • Maintenance and Construction Management (MC) • Public Transportation (APTS) • Commercial Vehicle Operations (CVO) • Traveler Information (ATIS) • Archived Data Management (AD) • Advanced Vehicles Safety Systems (AVSS)

  15. Market Package Components • 91 possible MP choices • Identify connections between agencies • Visual representation of the layout of a system that is constructed using: • Subsystem • Element • Terminator • Architecture Flow • GVMC has a total of 104 Market Packages

  16. Sample Market Package Customization

  17. Sample Market Package Customization

  18. Interconnect Diagram

  19. From User Needs to Projects • Refined List of User Needs Is Developed • Market Packages Are Selected To Address User Needs • Projects Are Developed Based On Market Packages • Geographically defined • Technologically defined as needed • Projects Feed The Deployment Plan • Evaluated for Benefit / Cost impact • Segmented to phases for the region

  20. Draft Project List • MDOT 5-year ITS Plan • ITS Deployment Plan – 2006 • Analysis of regional and technological gaps • Stakeholder feedback

  21. Draft Project: Arterials

  22. Draft Project: Freeway

  23. Preliminary Project Listing • Total of 170 projects • 9 Freeway projects • 41 Arterial projects • 2 Transit projects • Total of 7 Freeway Service Patrol projects covering approximately 70 miles

  24. Deployment Plan Methodology and IDAS Results • Alternatives developed based on architecture and stakeholder input • GVMC Model validated and converted to ITS Deployment Analysis System (IDAS) • Cost and benefit parameters based on those used in previous MDOT Predeployment studies • Combination of local and national data • Model run to estimate benefits and costs for 2010 and 2020 • Benefits and costs are annualized

  25. Final Steps • Addressing Feedback from Deployment Plan Workshop • Refining Analysis Results from IDAS • Packaging Projects for Deployment Plan • Review by Stakeholders • Submit Final Regional ITS Architecture and Deployment Plan

More Related