connected corridors/i-210 pilot streets and freeways ......aimsun model components (coding, freeway,...

Post on 06-Apr-2020

5 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

August 18, 2016

Connected Corridors/I-210 Pilot

Streets and Freeways Subcommittee

August 18, 2016

Agenda

Introduction: Connected Corridors and the I-210 Pilot

I-210 Pilot details: map, assets, accidents, stakeholders, major

incidents

Operational scenario example

Progress so far

Outreach and system requirements

Schedule

Architecture, High-Level Design, AMS, Response Plan Generation

Aimsun Model – Coding, Freeway, Intersections

2

Connected Corridors Program and the I-210 Pilot

Connected Corridors

Statewide program looking at all opportunities

to move people and goods in the most efficient

manner

Focused on transportation corridors in order to

ensure the greatest gains in operational

performance.

Includes freeways, arterials, transit, parking,

travel demand strategies, agency collaboration,

and more

I-210 Pilot

In the San Gabriel Valley – northeast of LA – is

the first Connected Corridors deployment. The

Pilot started approximately four years ago.

3

The I-210 Corridor

4

5

Express Commuter Buses Parking

Light-Rail, Transitway

& Commuter Rail

Freeway/Arterial

Signal Systems

I-210 Project Corridor Assets

I-210 Pilot Core Stakeholders

6

California Department of Transportation

Los Angeles Metropolitan Transportation Authority

Los Angeles County Department of Public Works

City of Pasadena

City of Arcadia

City of Monrovia

City of Duarte

Southern California Association of Governments

San Gabriel Valley Council of Governments

Foothill Transit

University of California, Berkeley - PATH

7

Bald

win

Alle

n

Hill

Lake

Los

Rob

les

Fair

Oak

s

Alta

dena

Sier

ra M

adre

Myr

tl

Mou

ntai

n

Buen

a Vi

sta

Citr

us

Gra

nd

San

Dim

as C

anyo

n

San

Dim

as A

ve

Lone

Hill

Amel

ia

Irwin

dale

Azus

a

Sant

a An

ita

San

Gab

riel

6.8

5.0

3.2

5.6

3.7

2.9

15.7

3.8

1.9

6.7

2.8

1.2

5.9 8.2 3.9 8.5 2.9

2.8 1.2 13.3 7.5

11.2 2.9 9.5 3.1 3.5 3.6

1.2

3.8

3.3 0.8 3.4

2.4

5.8 6.3

2.5

1.5

3.8 13.9 3.2 9.4

8.5

2.6 4.5 9.7

4.9

5.0 2.5

In 2013 a total of approximately 6,000 incidents were reported within the

project limits. (500 per month)

Major Incidents on I-210 (2009 – 2013)

2.3

3.2

6.2

5.0

10.5

9.0 2.2

10.6

2.8

3.8

8.8 14.0

3.5

5.8

6.0

24.0

0.0 – 5.0 hrs.

5.1 – 10.0 hrs.

10.1 – 23.9 hrs.

24.0 + hrs.

Los Angeles County Department of Public Works

I-210 Pilot Operational Scenario Example

8

ACCIDENT AHEAD

ACCIDENT AHEAD Freeway CMS

DMS/Trailblazer ACCIDENT

AHEADACCIDENT

AHEAD

Adjust Upstream Ramp Meter

Adjust Downstream Ramp Meter

Adjust Signal Timing

Go 511

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

ACCIDENT AHEAD

I-210 Pilot: Progress So Far

Successfully completed the planning phase

Project Charter signed in June 2015

Concept of Operations agreed upon

Other Systems Engineering documents available as templates

Creation of a new organization at Caltrans focused on TSM&O and performance. Creation of Corridor Manager position.

Funding

$20M in SHOPP funds secured for freeway improvements; completion in 2017

$6M in Metro 2015 Call for Projects funding. Entire process managed by Caltrans with input from cities and County. Completion 2018.

Currently in the requirements and high level design phase

Requirements document in approval process

High level design started

9

I-210 Pilot: Outreach and System Requirements

Outreach

Next Quarterly Connected Newsletter in August

ATCMTD Proposal Submitted on June 23rd

Connected Corridors website (http://connected-corridors.berkeley.edu/)

System Requirements

Nearing completion – we have processed over 500 stakeholder

comments

10

11

Schedule – Launch date July 2018

2014 2016 2017 2nd Half 1st Half 2nd Half 1st Half 2nd Half 1st Half

1. Project Management 10/1/13 - 12/31/19

2. Outreach & Communications 10/1/13 - 12/31/19

3. Concept Exploration & User Needs 11/1/13 - 12/26/14

4. Corridor Preparation 12/2/13 - 9/30/16

5a. AMS - Phase 1 1/6/14 - 5/29/15

5b. AMS - Phase 2 6/1/15 - 6/30/19

5c. AMS - Phase 3 7/01/18 - 7/31/19

6. SEMP 12/29/14 -

6/26/15 7. ConOps 9/12/14 - 5/20/15

8a. System Requirements

4/23/15 - 6/30/16

2018

6. SEMP Updates 6/30/15 - 6/28/16

9. Organizational Design 9/1/15 - 12/31/16

13. Institutional Deployment & Operations

1/1/17- 12/31/19

10. Technical Design 7/1/16 – 7/01/17

11. Component Development 8/15/16 - 4/30/18

12. System Integration 7/01/17 – 7/01/18

14. Technical

Deployment 1/01/18 –

07/01/18

17. System Operations 07/01/18 - 12/31/19

15. Training 07/01/18 -

16. System Validation & Acceptance 01/01/18 – 12/13/18

18. System Evaluation 9/1/15 - 12/31/19

8b. Validation Plan

7/5/16 - 1/30/17

2015 Start 10/1/1

3 1st Half 2nd Half 1st Half 2nd Half

12/31/19

19. Lessons Learned

9/1/19 – 12/31/19

2019 1st Half 2nd Half

2020 1st Half

Architecture, High-Level Design, AMS, Response Plan

Generation

Architecture and High Level Design

High Level Design has begun

Stakeholders and Systems

Current Proposed Architecture

AMS/Response Plan Generation

PATH is making good progress on Corridor Model and Response Plan

Rules

Response Plan Elements

Aimsun Model Components (coding, freeway, intersection, transit)

12

Stakeholders and Systems

13

Current Proposed ICM Architecture

14

Response Plan Elements

Resp

ons

e P

lan

Information Dissemination

Equipment Requests

Trucks Portable Equipment

Cars

Passenger Cars

Trucks

Buses

Detour Routes

Transit Operators

Roadway Operators

First Responders

Parking Operators

Emergency Services

Personnel Requests

Traffic Engineers

Safety Personnel

Others

On routes

Not on routes

Ramp Meter Control Requests

Intersection Signal Control Requests

On routes

Not on Routes

Fixed Devices

Portable DevicesCMS Messages

511 Services 3rd Party Info Providers

TravelersTrailblazer Signs

Corridor Operators

HAR Messages

15

Aimsun Model

Coding of geometrical and basic control elements completed

16

Aimsun Model

Freeway elements

Roadways

Mainline lanes

HOV lanes

On-ramps and off-ramps

Speed limits

65 mph on freeway

50 mph on ramps

Truck restrictions

Two leftmost lanes

Traffic detectors

Mainline, ramps, HOV lanes

Ramp meters

Time-of-day operations for now

Changeable message signs

Current and future

17

Aimsun Model

Intersection elements

Lane markings

Approach speed limits

25 to 45 mph, based on posted signs and local regulations

Movements within intersection

Destination lanes

Yielding movements

Right turn on red

Traffic detectors

Location

Size

Signal control phase associations

Traffic signal operations

Fixed time and actuated-coordinated operations

Timing plan schedule (over 24 hours, weekdays and weekend)

Stop-controlled intersections

18

Transit bay

Detectors

Transit stop

top related