SPM Basics & Applications Overview

Mark Taylor

January 27, 2016

Mark Taylor, P.E., PTOETraffic Signal Operations EngineerUDOTmarktaylor@utah.gov

1

SPM Basic Concept

- Signal controller- Probe source

- Signal- Corridor- System

Automated Data Collection

Useful Information about Performance

System Requirements for SPM’s

3) Server

4) Website

1) High-resolution Controller

5) Detection (optional)Can be done independent of a central system!

2) Communications Econolite Cobalt: Any Version Econolite ASC3 NEMA: V. 2.50+ & OS 1.14.03+ Econolite 2070 with 1C CPU Module: V. 32.50+ Intelight Maxtime: V. 1.7.0+ Peek ATC Greenwave 03.05.0528+ Trafficware 980ATC V. 76.10+ Siemens M50 Linux & M60 ATC

ECOM V. 3.52+ NTCIP V. 4.53+

McCain ATC Omni eX 1.6+

3

Controller EnumerationsEvent Code, Event Description, Parameter

High-resolution DataTimestamp, Enumeration Code, Parameter

Detector 5 OFF

Phase 8 GREEN

Detector 5 ON

http://udottraffic.utah.gov/signalperformancemetrics

Coordination Optimization Example: Progression Quality

Vehicles arrive on green

Vehicles arrive on yellow

Vehicles arrive on red

One approach shown

Metric: Purdue Coordination DiagramDetection Requirements: Advance Counters

7

Purdue Coordination DiagramBangerter & 5400 S (3/7/2013)

8Metric: Purdue Coordination DiagramDetection Requirements: Advance Counters

Approach Speeds

Bluff & 100 S, St. George, NB

Use 85th percentile to set yellow & redclearance intervals

Posted speed

Metric: Approach SpeedsDetection Requirements: Wavetronix Advance Radar

9

Operations & Traffic Study Example:Vehicle Speeds at Intersections

Metric: Approach SpeedsDetection Requirements: Wavetronix Advance Radar

Snow Storm Starts

10

Approach Volumes

Metric: Approach VolumesDetection Requirements: Advance Counters

When to take a lane for maintenance Directional splits for offset optimization Network models

11

Lane-by-Lane Volume CountsUse for traffic studies, models, adjust splits, coordination balance

Metric: Turning Movement CountsDetection Requirements: Stop Bar Counters

12

Red Light MonitoringUse for identifying safety trends and engineering countermeasures

Metric: Red Light MonitoringDetection Requirements: Stop Bar Counterswith speed filter or detectors in intersection13

Red Light Monitoring

14

Is green time too short? – Would increasing the split fix the problem? Is coordination poor? – More vehicles arriving on green could fix this? Is sight distance poor? – Are their trucks or other obstructions blocking signal? Is law enforcement needed? – Time can be pinned down for law enforcement.

Analysis: 7:00 AM to 8:15 AM - May 18, 2015

Metric 1: Purdue Coordination DiagramDetection Requirements: Advance

Metric 2: Purdue Travel Time DiagramRequirements: Probe data set 15

Sunnyside Avenue

1300 S

2300 E

1700 S

2100 S

Foothill Boulevard

+3%

+18%

+13%

+4%

-3%

+8%

+1%

+5%

+20%

+35%

-3%

-2%

-1%

+5%

14%

-1%

Initial Percent Arrival on Green

Increase in Percent Arrival on Green

Decrease in Percent Arrival on Green

Corridor Midday Arrival on Green

74%

7%

2013Purdue Coordination

Diagrams

Sunnyside Avenue

1300 S

2300 E

1700 S

2100 S

Foothill Boulevard

0%

+9%

+2%

+2%

-7%

+7%

-6%

+7%

+7%

+13%

+6%

+4%

-1%

-3%

-1%

-1%

77%

2%

-1%

Initial Percent Arrival on Green

Increase in Percent Arrival on Green

Decrease in Percent Arrival on Green

Corridor Midday Arrival on Green

2015Purdue Link Pivot