Kern COG ITS Plan STAKEHOLDER WORKSHOP OCTOBER 17, 2017 10:00 A.M. - - PowerPoint PPT Presentation

Kern COG ITS Plan

STAKEHOLDER WORKSHOP

OCTOBER 17, 2017 10:00 A.M. – 1:00 P.M.

1

Agenda

• Introductions
• Review ITS Plan Vision
• Architecture Overview
• Changes to National ITS Architecture
• Connected Vehicles Services
• ITS Services Prioritization
• ITS Projects
• Any Connected Vehicle projects planned?
• Public Safety/Center to Center?
• Emergency Operations?
• Operational Roles and Responsibilities
• Next Steps
• Adjourn

2

ITS Plan Vision

Through community ITS investment, coordination and data sharing between transportation agencies, travel in Kern is safe and efficient.

3

What is an ITS Architecture?

A planning framework for the deployment of integrated transportation systems

• Inventory of existing and planned ITS elements
• Interfaces and standards that support data exchange and interoperability
• Operational concepts identifying agency roles and responsibilities involved in ITS
• Guidance on architecture use for project planning and implementation
• Guidance on architecture maintenance

4

An ITS Architecture Includes: Agencies, Systems, Communications and Information Flows

traffic information request for traffic info

Traveler Info Transit Traffic Emergency Services

5

What is ARC‐IT?

USDOT developed the new National ITS Architecture (NITSA) in July 2017 and named it the Architecture Reference for Cooperative and Intelligent Transportation (ARC‐IT) Version 8.0.

• This version merges and enhances the NITSA Version 7.1 and Connected Vehicle Reference ITS

Architecture (CVRIA) Version 2.2

• Combines the services of the NITSA with the connected vehicle content of CVRIA
• Access at www.arc‐it.net

National ITS Architecture CVRIA

ARC-IT

6

What’s New in ARC‐IT?

7

Layers  Views

Merging Architectures

Source: USDOT ITS JPO Webinar

8

Defined around 4 views:

• Enterprises to carry out services
• Functions to implement services
• Physical objects to implement that

functionality

• Communications protocols required for

implementation

Organized by Service Packages

ARC‐IT Structure and Organization

Service Packages

Source: USDOT ITS JPO Webinar

9

10

Architecture Overview

Connected Vehicles History

• Connected Vehicles (CV) planning framework “lived” in the Connected Vehicle

Reference Implementation Architecture (CVRIA)

• CV implementation is complex and requires an unprecedented amount of

connectivity and technical interfaces

• CVRIA established a framework for integrating CV applications & technologies to

identify interfaces for standardization

11

Creating an Environment that Enables CV

Communications Technology

• Wide‐Area Wireless Communication
• Short Range Wireless Communication
• Internet

Institutional

• Smart Devices/Internet of Things (IoT)
• Expectation of Connectivity
• Privacy
• Security

12

Planning for CV/AV

Technology and Best Practices are currently being developed in the private sector and tested in partnership with public agencies through pilot programs Need State or Federal guidance before widespread implementation and investment to prevent segmentation of technology from region‐to‐region or state‐to‐state “Automated Driving Systems 2.0: A Vision for Safety” was published by USDOT and NHTSA

• Provides voluntary guidance for technology design
• Provides Best Practices for legislatures and State Highway Officials
• Does not provide guidance on technology and infrastructure for regional planning

Caltrans is modifying lane lines from 4 inches to 6 inches thick to allow AVs to “see” the lines.

13

What can an MPO do?

Ready your technology

• Ensure communications systems are robust and redundant to support live data exchange
• Understand how current and upcoming projects can support long‐term technology goals
• Identify areas where communication devices can be deployed first (high collision and heavy congestion

intersections and corridors)

• Inventory back office to determine its readiness to collect, store, analyze, and disseminate data

Maintain and upgrade existing assets that can be used or retrofitted for AV/CV

• Improve lane lines, signs, and signals so that smart cars can “read” them
• With higher penetration of AV/CV, consider converting existing lanes to narrower lanes

14

What can an MPO do?

Institutional Readiness

• Plan for deployment – how and when to roll out technologies
• Tie ITS to agency goals
• Apply for federal grants
• Identify and implement policies that may encourage AV/CV
• Re‐evaluate core competencies within the agency. Hire or contract technical expertise needed.
• Watch for trends and best practices in security and privacy in data networks

Educate stakeholders

• Sign up for ITS Webinars and attend workshops
• Plan a successful public outreach and communication program
• Meet with local stakeholders to understand regional needs and perspectives

15

Connected Vehicles in ARC‐IT

Scope of Connected Vehicles (CV) in ARC‐IT is broader in scope than in CVRIA CV Applications are now integrated into Service Packages in ARC‐IT Changes from CVRIA to ARC‐IT

• CV enterprise and functional viewpoints are defined,

but view content will be provided in a future release

• CVRIA physical view and communications view

concepts all carry forward to ARC‐IT.

All Service Areas have Service Packages with CV components

ARC‐IT Service Areas Traffic Management (TM) Traveler Information (TI) Public Transportation (PT) Public Safety (PS) Commercial Vehicle Operations (CVO) Maintenance and Construction (MC) Data Management (DM) Vehicle Safety (VS) Support (SU) Sustainable Travel (ST) Parking Management (PM) Weather (WX)

16

For Example…

Traffic Management TM01 Infrastructure‐Based Traffic Surveillance TM13 Standard Railroad Grade Crossing TM02 Vehicle‐Based Traffic Surveillance TM14 Advanced Railroad Grade Crossing TM03 Traffic Signal Control TM15 Railroad Operations Coordination TM04 Connected Vehicle Traffic Signal System TM16 Reversible Lane Management TM05 Traffic Metering TM17 Speed Warning and Enforcement TM06 Traffic Information Dissemination TM18 Drawbridge Management TM07 Regional Traffic Management TM19 Roadway Closure Management TM08 Traffic Incident Management System TM20 Variable Speed Limits TM09 Integrated Decision Support and Demand Management TM21 Speed Harmonization TM10 Electronic Toll Collection TM22 Dynamic Lane Management and Shoulder Use TM11 Road Use Charging TM23 Border Management Systems TM12 Dynamic Roadway Warning

17

TM04: Connected Vehicle Traffic Signal System Physical Diagram

18

ARC‐IT Service Package Areas

Traffic Management Maintenance and Construction Commercial Vehicle Operations Public Safety Public Transportation Data Management Vehicle Safety Parking Management Support Sustainable Travel Weather Traveler Information

Source: USDOT ITS JPO Webinar

19

ARC‐IT Tools

Two companion tools are available to assist with development and use of the Architecture.

• Regional Architecture Development for Intelligent

Transportation:

• Tool to create/maintain ITS architectures (formerly Turbo Architecture)
• Focuses on regional planning & the development of Operational

Concepts

• Systems Engineering Tool for Intelligent

Transportation:

• Tool to create diagram‐based project architectures for Physical,

Enterprise, and Communications Viewpoints

• Focuses on projects that are scoped in the Regional Architecture

20

Using the ITS Architecture for Planning

Development of the Regional ITS Architecture can…

• Support Long Range Planning by promoting increased stakeholder participation and promoting system

and inter‐jurisdictional integration

• Support ITS Strategic Planning by providing the basis that identifies the ITS services and projects the

region needs, with additional effort required to define funding, system management and operation, and regional technology

The ITS Architecture provides inputs for planning such as:

• Stakeholder involvement and institutional dependencies
• Regional vision, goals, and needs
• Integration, security, and functional requirements for project phasing

Enterprise View provides most of the Planning perspectives

21

Using the ITS Architecture for Programming and Budgeting

Regional ITS Architecture…

• Can support the selection of projects identified in programming and budgeting through project

definition and sequencing/prioritization

• Can assist the MPO in developing periodical capital planning and budgeting process

ITS Elements identified to be needed by various stakeholders in a region can be funded by federal funding. Applications are made stronger with justification of regional need, which can be taken from the Regional Architecture.

22

Using the ITS Architecture for Project Design and Implementation

1. Consult the architecture inventory 2. Find related stakeholder roles & responsibilities 3. Find related functional requirements 4. Review information flows & interfaces 5. Identify appropriate communication standards 6. Determine if agency agreements are needed

23

24

Systems Engineering Process

Using the ITS Architecture for Project Design and Implementation

25

ITS Services Prioritization

Divide ITS Services into timeframes based on priority, prerequisites, and ease of implementation:

• Short‐Term Timeframe (0‐5 years) ‐ RED Sticker
• Medium‐Term Timeframe (5‐10 years) – GREEN Sticker
• Long‐Term Timeframe (10+ years) – YELLOW Sticker
• Not currently planned – BLUE Sticker

26

ITS Projects

• Any Connected Vehicle projects planned?
• Any Public Safety‐type projects planned?
• System upgrades?
• Information sharing?
• Center to Center projects?
• Information sharing between TMCs or Transit Operations Centers?
• New Data Exchange systems for Traveler Information? Coordinated operations? Big Data?
• Emergency Operations?

27

Operational Roles & Responsibilities

Operational Responsibilities ‐ Who does what with whom?

Traffic Management

• TMCs
• Signal control and coordination – independent or with partners?

Incident Management

• Coordinated efforts
• Flush plans

Transit Management

• Transit Signal Priority
• Electronic Fare Payment
• Traveler Information

28

Next Steps

• Update ITS Strategies
• Develop Operational Scenarios
• Update ITS Architecture

29

http://www.kerncog.org/category/docs/its/ Alyssa Phaneuf Alyssa.Phaneuf@kimley‐horn.com (213) 261‐4047

30

Questions?