Memphis MPO Regional ITS Architecture Update. Stakeholder Workshop June 6, 2018

Size: px
Start display at page:

Download "Memphis MPO Regional ITS Architecture Update. Stakeholder Workshop June 6, 2018"

Transcription

1 Memphis MPO Regional ITS Architecture Update Stakeholder Workshop June 6, 2018

2 Workshop Overview Welcome and Introductions Overview of the Regional ITS Architecture Review of Regional ITS Needs Review of Existing and Planned ITS Projects in the Region Discussion on Potential Regional ITS Projects and Operations Initiatives that Require Multi-Agency Collaboration Wrap Up 2

3 INTRODUCTIONS

4 Fall 2017 Summer 2018 October 2018 January 2020 The Big Picture Livability 2050 Regional Transportation Plan Travel Model Update ITS Architecture Update October 2018 ITS Ready for Use Letter from FHWA FY TIP 4

5 What is the Regional ITS Architecture?

6 What is ITS? ITS An acronym that stands for Intelligent Transportation Systems. One Definition of ITS The application of data processing and data communications to surface transportation to increase safety and efficiency. 6

7 What is ITS? 7

8 Emerging ITS Technologies Automated Vehicles Connected Vehicles Active Traffic Management Integrated Corridor Management Decision Support Systems Privatized Traffic Data

9 Why Deploy ITS? REDUCE CONGESTION Congestion caused urban Americans to travel 6.9 billion hours longer and use an extra 3.1 billion gallons of fuel for an estimated congestion cost of $160 billion.* INCREASE SAFETY In 2016, Tennessee had 1,041 traffic fatalities and Mississippi had 690. IMPROVE RELIABILTY and DECREASE TRAVELER FRUSTRATION Travelers report variability in travel times to be one of their greatest sources of frustration. *from the 2015 Urban Mobility Scorecard

10 What is a Regional ITS Architecture? A long-range plan for the deployment, integration, and operation of ITS. The architecture acts as a framework for ensuring institutional agreement and technical integration among stakeholders for the implementation of ITS projects in a particular region. 10

11 Regional ITS Architecture Components Requirements of a Regional ITS Architecture Regional Description Stakeholder Identification Inventory of ITS Elements Identification of ITS Services Operations Concepts (Roles and Responsibilities) Functions Interfaces/Information Flows Standards Identification Project Sequencing Agreements Maintenance Plan 11

12 Memphis Regional ITS Architecture ITS Inventory and Needs Defines ITS Services and Agencies Involved Projects to be Deployed October 2014

13 History in Memphis MPO Region First developed in 2002 Updated in 2010 Last updated in 2014 A living document updated in coordination with the Regional Transportation Plan update (typically on a 4-year basis) 13

14 Purpose of the Architecture To provide a vision for ITS in the region To develop a blueprint for the integration of systems To provide a framework for more detailed project design To demonstrate conformity for federal funding To identify key stakeholders and interagency relationships To identify ITS project needs and inform financially constrained planning efforts To help identify project-level requirements 14

15 Architecture Update Process Update 2014 Memphis Architecture to National ITS Architecture Version 8.0 Gather Stakeholder Input through Interviews and Workshop Develop Updated Memphis Regional ITS Architecture and Deployment Plan FHWA and TDOT Ready for Use Letter 15

16 National ITS Architecture Structure Twelve Service Areas for ITS Traffic Management Traveler Information Public Safety Maintenance and Construction Commercial Vehicle Operations Sustainable Travel Public Transportation Weather Data Management Support Parking Management Vehicle Safety 16

17 National ITS Architecture Structure Each service area includes multiple ITS service package. Total of 139 ITS service packages in the National ITS Architecture. The ITS service packages provide a visual representation of how ITS services are deployed and how information is shared. 17

18 National ITS Architecture Structure Media Information Service Provider Transit Management Traffic Management DMS Roadway Emergency Management TM08 Traffic Incident Management ITS Service Package 18

19 National ITS Architecture Structure TM08 Traffic Incident Management ITS Service Package 19

20 Approach to Regional ITS Architecture Plan Previous versions of the Regional Architecture o Focused on detailed customized service packages for each agency o Focused on identifying individual ITS projects for each agency Current version of the Regional ITS Architecture o Focus on identifying service packages but detailed customization will take place at the project level o Focus on identifying regional projects and initiatives that will benefit most from use of the ITS architecture Documentation o Regional ITS Architecture and Deployment Plan Report o Document and Interactive Version on MPO s website: memphismpo.org/plans/safety-mobility/its 20

21 Systems Engineering Definition Systems engineering is an interdisciplinary approach to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem. Requirements Using a systems engineering approach is required by the USDOT for ITS projects. The process includes demonstrating conformance to the Regional ITS Architecture. Guidance can be found in the TDOT ITS Project Development Guidelines

22 What Have We Heard so Far?

23 Regional ITS Needs State Level o Need connection between TDOT and MDOT o Need connection between TDOT and City of Memphis o Need to continue to expand freeway management system o Need for additional active traffic management strategies like variable speed limits and ramp metering (TDOT) o Need a freeway service patrol (MDOT) Local Level o Need to complete implementation of CMAQ arterial ITS program in Shelby County o Need funding to replace CMAQ funding reduction due to region being in attainment o Need to expand capability to share traffic conditions between agencies: State DOT - Local Traffic Agencies -Transit o Need to expand capability to get accurate traveler information out to the public (Waze Connected Citizens Program in Memphis) 23

24 What are our Regional Needs and Level of ITS Deployment? Discussion on Level of Deployment of Each ITS Service Area and Additional Needs

25 Service Area 1 Traffic Management Example service packages include: o Traffic Signal Control o Traffic Incident Management System o Variable Speed Limit Signs o Ramp Metering 25

26 Service Area 2 Traveler Information Example service packages include: o Broadcast Traveler Information o Dynamic Route Guidance o In-vehicle Signage 26

27 Service Area 3 Public Safety Example service packages include: o Emergency Vehicle Preemption o Roadway Service Patrols o Disaster Response and Recovery 27

28 Service Area 4 Maintenance and Construction Example service packages include: o Maintenance Vehicle and Equipment Tracking o Infrastructure Monitoring o Roadway Automated Treatment 28

29 Service Area 5 Commercial Vehicle Operations Example service packages include: o Electronic Clearance o HAZMAT Management o Roadside and Virtual Weigh-in-Motion 29

30 Service Area 6 Sustainable Travel Example service packages include: o Emissions Monitoring o Electric Charging Stations Management o HOV/HOT Lane Management 30

31 Service Area 7 Public Transportation Example service packages include: o Transit Vehicle Tracking o Transit Traveler Information o Transit Signal Priority 31

32 Service Area 8 Weather Example service packages include: o Weather Data Collection o Weather Information Processing and Distribution o Spot Weather Impact Warning 32

33 Service Area 9 Data Management Example service packages include: o ITS Data Warehouse o Performance Monitoring 33

34 Service Area 10 Support Catch-all category for systems supporting transportation operations. Example service packages include: o Map Management o Data Distribution o Security and Credentials Management 34

35 Service Area 11 Parking Management Example service packages include: o Parking Space Management o Parking Electronic Payment o Smart Park and Ride System 35

36 Service Area 12 Vehicle Safety Example service packages include: o Connected Vehicle Curve Speed Warning o Connected Vehicle Queue Warning o Automated Vehicle Operations 36

37 Potential Regional ITS Projects and Operations Initiatives Discussion on Initiatives Requiring Multi-Agency Collaboration

38 Regional Projects to Discuss Regional Traveler Information Improvements Integrated Corridor Management Freeway Service Patrol (Mississippi) Center-to-Center Communications (State-to-State) Center-to-Center Communications (State-to-Local) Archived Data Warehouse Implementation Other Regional Projects

39 Project Discussion Regional Traveler Information Improvements Regional Traveler Information Stakeholders TDOT, MDOT, ArDOT, MATA, MPO, Counties, Cities and Towns Components Travel times and road conditions, planned construction and special event closures, transit information, connected citizen s program (Waze), customized information for travelers Status Limited information on arterials, information is currently spread out over many agencies in many locations, limited ability for travelers to customize information. TDOT and Memphis have connected citizens program but others do not have third party data agreements. Priority High

40 Project Discussion Integrated Corridor Management Deployment Regional Traveler Information Stakeholders TDOT, MDOT, MPO, Counties, Cities and Towns Components Freeway and arterial monitoring, CAD incident data sharing, freeway service patrol, signal timing plans for incidents, ramp metering, variable speed limits, training Status Freeway and arterial monitoring exists but could be expanded, limited CAD incident data sharing, signal timing in response to incidents is needed, possible need for automated signage for detour routes, additional incident management training Priority Medium

41 Project Discussion Regional Traveler Information Freeway Service Patrol Stakeholders MDOT, MPO Components Freeway Service Patrol vehicles, dispatching, coordination with public safety Status Currently only operated by TDOT in Tennessee, no deployments by MDOT in Mississippi. Primary concern is on-going funding to maintain the program. Priority Medium

42 Project Discussion Center-to-Center Communications (State-to-State) Regional Traveler Information Stakeholders TDOT, MDOT, ArDOT Components Video sharing, DMS message sharing, incident data sharing, closure information sharing, other travel information Status Connections needed include TDOT-to-MDOT and TDOT-to-ArDOT Priority High

43 Project Discussion Center-to-Center Communications (State-to-Local) Regional Traveler Information Stakeholders TDOT, City of Memphis, MDOT, NW Mississippi Cities Components Video sharing, DMS message sharing, incident data sharing, closure information sharing, detour routing, other travel information Status Connections needed include TDOT-to-City of Memphis (which provided connectivity to other Shelby County Cities) and MDOT-to-NW Mississippi Cities Priority High

44 Project Discussion Archived Data Warehouse Implementation Regional Traveler Information Stakeholders TDOT, MDOT, MPO, MATA, Counties, Cities and Towns Components Data warehouse to store regional travel data. Could be a done virtually. Status Agencies store limited data but warehouse is not available Priority Low

45 Regional Projects to Discuss Regional Traveler Information Improvements Integrated Corridor Management Freeway Service Patrol (Mississippi) Center-to-Center Communications (State-to-State) Center-to-Center Communications (State-to-Local) Archived Data Warehouse Implementation Other Regional Projects

46 Wrap Up

47 Next Steps Conduct additional outreach for input into the Regional ITS Architecture Develop Draft Memphis Urban Area Regional ITS Architecture and Deployment Plan Finalize plan after stakeholder input Work with FHWA and TDOT to Obtain Ready for Use Letter 47

48 Thank You Tom Fowler Kimley-Horn James Collins Kimley-Horn Sajid Hossain Memphis MPO 48

49 49

50 Why Deploy ITS?

51 Why Update the Architecture? FAST Act new planning theme areas Integration of newly completed and ongoing planning efforts Updated demographic data Emerging trends and technologies 53

52 Next Steps Summarize Stakeholder Input from Today s Workshop Develop Updated Memphis Regional ITS Architecture Develop Updated Regional ITS Deployment Plan

53 ITS Benefits Increased roadway and transit efficiency Enhanced incident and special event management Improved safety for travelers, public safety, and maintenance personnel Accurate and timely traveler information

54 Use of the Architecture In planning: o Architecture represents a consensus vision of Operations and Planning stakeholders for deployment of ITS systems o Addresses both short range projects and long range strategies In programming and budgeting: o Links objectives and needs of the region with ITS deployed in the field o Takes a regional view o Begins coordination of projects of various organizations by defining from the same reference point 57

55 Use of the Architecture In project identification: o Projects are listed in Project Sequencing (or can be identified from other components of architecture) o Use architecture to help define project details, including: Project description Stakeholders involved Stakeholder roles and responsibilities Potential partners Elements involved Integration opportunities Dependencies Budget estimate 58

56 Use of the Architecture In performance monitoring: o Architecture defines collection of data from operational systems to support performance monitoring o Consider regional elements of Archived Data User System to automate collection of data from: Traffic Transit Emergency Services Traveler Information 59

57 Maintenance of the Architecture Create maintenance plan that includes: o WHO will be responsible? o WHEN will updates occur? o WHAT will be maintained? o HOW will the changes be made? 60

58 Maintenance of the Architecture Factors that cause changes to an architecture: o ITS project deployments o Changes in project plans o Shifts in ITS goals and objectives and the services to meet them o Additional stakeholders o Errata and enhancements 61