T3 Webinar Presentation

RCTOs in Action: Portland, Detroit, Tucson, and Hampton Roads Discuss their Regional Concept for Transportation Operations (July 25, 2007)

Pima Association of Governments (PAG)

Presenter:   Paul Casertano
Presenter's Org:   Pima Association of Governments (PAG)

HTML version of the presentation
Image descriptions are contained in brackets. [ ]
Back to Webinar Files

T3 Webinars are brought to you by the ITS Professional Capacity Building Program (ITS PCB) at the U.S. Department of Transportation's (USDOT) ITS Joint Program Office, Research and Innovative Technology Administration (RITA)

Slide 1: Regional Context

[This slide displays a map showing the PAG boundaries in relation to some of the other MPOs and COG (Council of Governments) in Arizona.]

Slide 2: Motivation for RCTO

  • Region is highly dependent upon arterial system
  • Interstate-10 reconstruction over next 3-years
  • Regional ITS Strategic Plan and Architecture
  • Potential passage of Ĺ cent sales tax for transportation

Slide 3: Development Process

  • Establish framework for a multi-year RCTO program
  • "Drill-down, target approach"
  • Began wide, narrowed in on immediate needs
  • Greater detail on immediate needs
  • Other needs will be addressed over time

Slide 4: Operations Areas

  • Traffic Incident Management
  • Arterial Management
  • Freeway Management
  • Work Zone Management
  • Traveler Information
  • Others Category (transit, homeland security)

Slide 5: Development Process

[This slide shows the development process of the Pima Association of Governments (PAG) Regional Concept for Transportation Operations. The image is of a sideways equilateral triangle, broken into three sections, pointing at a bull's-eye, which is the PAG Regional Concept for Transportation Operations. First the PAG Identified Multiple Operations Areas, second they selected focus operations areas, and third they prioritized needed policies. ]

Slide 6: Development Process

  • Identified Multiple Operations Areas
    • Vision Statement
    • Conducted Inventory
    • Established Goals and Performance Measures
  • Selected Focus Operations Areas
    • Developed list of needed policies, practices, or procedures for focus areas
      1. Arterial management
      2. Work zone management
      3. Traveler information
  • Prioritized Needed Action Plans
    • Develop high-priority action plans
    • Identify Resources and Institutional Relationships
    • Update Tucson Area Operations Manual

Slide 7: Example Action Plan Template

  • Introduction:
    • Establish a regional traffic signal operations program
  • Need:
    • Enhance ability to proactively manage the regionís traffic signal system
  • Institutional Arrangements:
    • Guided by PAG Subcommittee
    • Consultant contracts managed by PAG
    • Project-level working groups established on a project-by-project basis
  • Roles and Responsibilities:
    • Agencies retain control, but have certain participation obligations to the region
  • Resources Required and Estimated Costs:
    • Agency staff time commitment
    • On-call consultant program
    • Identify funding mechanism
  • Status:

Slide 8: Development Partners

  • ADOT
    • Traffic Operations Center (FMS, Phoenix)
    • Tucson District, traffic engineering and project management
  • Local jurisdictions:
    • Traffic engineering
    • Construction managers
    • Information technology

Slide 9: Development Partners

  • Outreach to the following on a case-by-base basis (it's more difficult to keep their attention throughout RCTO development process):
    • Arizona Department of Public Safety
    • Fire Chiefs Association
    • Tucson Police Department
    • SunTran (transit)
    • Indian Communities

Slide 10: Achievements and Implementation Activities

  • Traveler information
    • Achieved agreement on regional traveler information framework/integration with existing statewide 511 system
  • Regional program for gathering, producing, distributing traveler information.
    • Building block for regional archived data center
    • Funded through MPO work program

Slide 11: Achievements and Implementation Activities

[The slide displays a flow chart that begins with data from various sources being sent directly to the server of transview - Tucson's traveler information source. Incident data is inputted from servers at the Pima County Sheriff's and Tucson Police Departments; event and construction data is sent from the servers of the City of Tucson and Pima County DOTs; and additional event and construction data is entered manually from other local jurisdictions, including: the town of Marana, the town of Oro Valley, the Pascua Yaqui Tribe, the town of Sahuarita, the city of South Tucson, and the Tohono O'odham Nation. From the transview server an arrow is pointing to an image of the transview website (www.transview.org) where information provided by the various agencies is disseminated.]

[From the transview server incident related data is exchanged, using the IEEE 1512 family of standards, with the Regional Archived Data Server (RADS) - Maricopa County's archive and retrieval system for ITS data. The RADS is then shown exchanging that incident data with the Arizona DOT's Highway Conditions and Reporting System (HCRS), again using the IEEE 1512 standards family. Another input of incident data into the HCRS is shown from the Arizona Department of Public Safety. The HCRS is then shown releasing the incoming incident data via Arizona's 511 travel information website and hotline and to an ftp site for the media.]

Slide 12: Achievements and Implementation Activities

  • Arterial management
    • Planning and programming for regional traffic signal program. Physical infrastructure and services.
    • Regional traffic signal services on-call program
    • Provide assistance to local agencies to implement coordinated timing plans, etc.

Slide 13: Achievements and Implementation Activities

  • Work zone coordination
    • Initiated monthly/bimonthly regional construction coordination meetings
    • Developed region wide map of existing and planned construction projects. Developing update and maintenance protocols.

Slide 14: RCTO and the Planning Process

  • Challenge:
    • 2 to 3 year timeframe does not fit in with traditional 5-year TIP cycle
  • Solutions:
    • Introduced TIP projects for future years
    • Identified funding from recent sales tax initiative
    • "Regionalizing" operations related projects
    • Use existing resources, (MPO staff & work program funds)

Slide 15: RCTO Implementation

  • Implementation an important part of the RCTO process
  • Stakeholders must remain engaged
    • Money
    • Tangible outcomes
    • Sense of ownership
    • Follow through on concepts - champions

Slide 16: Insights and Observations

  • Utilize existing committee structures
  • RCTO is an evolving document - scaleable and can be expanded upon over time
  • Initial operational objectives should be attainable - "low-hanging fruit"
  • Most successful meetings are in smaller settings, rather than larger, more formal settings
  • Operators natural tendency is to focus on the "equipment"
  • Fight for operations projects/programs in TIP and RTP - look to local agencies to help get you there

Next >>  An Action Plan to Address Transportation Operations in Southeast Michigan

back to top