Transport Regional Its Architecture and Operational Concept Report

Transport Regional Its Architecture and Operational Concept Report

Regional ITS Architecture & Operational Concept Plan for the Portland Metro Region prepared for Oregon Department TransPort of Transportation INTERSTATE 5 Clark County Vancouver INTERSTATE 205 Banks North Plains Camas Multnomah County Washougal Maywood Park INTERSTATE 26 84 Fairview INTERSTATE 405 Wood Troutdale Forest Hillsboro Village Grove Cornelius Portland Gresham Beaverton 217 INTERSTATE Washington County 5 Milwaukie Happy Valley Gaston Tigard Lake Oswego Johnson King City City Durham Sandy Gladstone Rivergrove Tualatin West INTERSTATE Linn 205 Sherwood Clackamas County Oregon City Yamhill County Wilsonville Newberg Carlton Estacada Dundee INTERSTATE 5 Canby Barlow Lafayette Dayton prepared by December 2016 TRANSPORT REGIONAL ITS ARCHITECTURE AND OPERATIONAL CONCEPT REPORT ACKNOWLEDGMENTS Metro Project Manager Chris Myers Metro TransPort Committee Jabra Khasho City of Beaverton Aszita Mansor City of Beaverton Tina Nguyen City of Beaverton Jim Gelhar City of Gresham Dan Hazel City of Hillsboro Tegan Enloe City of Hillsboro Amanda Owings City of Lake Oswego Willie Rotich City of Portland Peter Koonce City of Portland Mike Ward City of Wilsonville Bikram Raghubansh Clackamas County Nathaniel Price Federal Highway Administration Caleb Winter Metro Andrew Dick Oregon Department of Transportation Kate Freitag Oregon Department of Transportation Galen McGill Oregon Department of Transportation Dennis Mitchell Oregon Department of Transportation Kristin Tufte Portland State University Mike Coleman Port of Portland Phil Healy Port of Portland Steve Callas TriMet A.J. O’Connor TriMet Ken Turner TriMet Stacy Shetler Washington County Other Stakeholders/Contributors Ron White TriMet Bob Hart Regional Transportation Committee (RTC) Consultant Team DKS Associates IBI Group Jennifer Bachman Jim Peters Mike Haas Keith Ponto Renee Hurtado Danella Whitt Bruno Peters June Park Adrian Pearmine Alexis Biddle December 2016 Page i of v TRANSPORT REGIONAL ITS ARCHITECTURE AND OPERATIONAL CONCEPT REPORT TABLE OF CONTENTS 1 Contents 1 Introduction .............................................................................................................................1 1.1 What Was Updated? ................................................................................................................ 1 1.2 Who is TransPort? .................................................................................................................... 1 1.3 What is ITS? .............................................................................................................................. 2 1.4 Why Develop an ITS Architecture? .......................................................................................... 2 1.5 Report Elements ....................................................................................................................... 2 2 National ITS Architecture Overview ..........................................................................................4 2.1 Logical Architecture ................................................................................................................. 5 2.2 Physical Architecture................................................................................................................ 5 2.2.1 Subsystems ................................................................................................................................. 7 2.2.2 Equipment Packages .................................................................................................................. 7 2.2.3 Terminators ................................................................................................................................ 7 2.2.4 Architecture Flows ..................................................................................................................... 8 2.2.5 Architecture Interconnects ........................................................................................................ 8 3 TransPort Regional ITS Architecture ..........................................................................................9 3.1 Regional ITS Plans .................................................................................................................. 10 3.2 Architecture Update Process ................................................................................................. 12 3.2.1 Status Field in Turbo Architecture ............................................................................................ 14 3.3 Geographic Boundary ............................................................................................................ 14 3.4 Timeframe .............................................................................................................................. 16 3.5 Scope ...................................................................................................................................... 16 3.6 Stakeholders ........................................................................................................................... 16 3.6.1 Agreements .............................................................................................................................. 16 3.7 System Inventory ................................................................................................................... 17 3.8 User Services .......................................................................................................................... 18 3.9 Service Packages .................................................................................................................... 19 3.10 High-Level Physical Architecture Interconnects ................................................................. 23 3.11 Functional Requirements .................................................................................................... 24 4 Maintenance Plan .................................................................................................................. 26 4.1 Who Maintains the Regional ITS Architecture? ..................................................................... 26 4.2 What is Maintained in the Regional ITS Architecture? .......................................................... 26 4.3 When is the Regional ITS Architecture Updated? .................................................................. 27 4.3.1 Option 1: Periodic Update (Every Five to Ten Years) ............................................................... 27 4.3.2 Option 2: Project-Based Update ............................................................................................... 27 December 2016 Page ii of v TRANSPORT REGIONAL ITS ARCHITECTURE AND OPERATIONAL CONCEPT REPORT 4.4 How is the Regional ITS Architecture Maintained? ............................................................... 27 5 Operational Concept PlanS ..................................................................................................... 29 5.1.1 Operational Concept Development Approach ......................................................................... 30 5.1.2 Operational Concept Service Areas .......................................................................................... 30 5.1.3 Organization of the Operational Concept by Service Area ....................................................... 31 5.2 Regional Traffic Control ......................................................................................................... 33 5.2.1 Potential Connected Vehicle Applications ............................................................................... 36 5.2.2 Operational Concept Graphic ................................................................................................... 36 5.2.4 Stakeholder Roles and Responsibilities .................................................................................... 39 5.3 Traveler Information .............................................................................................................. 42 5.3.1 Potential Connected Vehicle Applications ............................................................................... 43 5.3.2 Operational Concept Graphic ................................................................................................... 43 5.3.4 Stakeholders Roles and Responsibilities .................................................................................. 45 5.4 Incident Management ............................................................................................................ 48 5.4.1 Potential Connected Vehicle Applications ............................................................................... 50 5.4.2 Operational Concept Graphic ................................................................................................... 50 5.4.4 Stakeholder Roles and Responsibilities .................................................................................... 52 5.5 Maintenance and Construction Management ....................................................................... 55 5.5.1 Potential Connected Vehicle Applications ............................................................................... 56 5.5.2 Operational Concept Graphic ................................................................................................... 57 5.5.3 Stakeholder Roles and Responsibilities .................................................................................... 57 5.6 Public Transportation

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    164 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us