Archived Data User Services (ADUS). ITS Produce Data The (sensor) data are used for to help take...

Archived Data User Services (ADUS)

ITS Produce Data

• The (sensor) data are used for to help take transportation management actions– Traffic control systems– Transit vehicle performance improvements– Traveler information– Commercial vehicle operations improvements– Etc…

So,

• Did those management actions actually improve travel?

• Could you have done better?

• Were the assumptions you used when you built the system valid?

• Are there other actions you could take?

To Answer Those Questions

• Collect, store, and use the ITS data you generate to– Understand the performance of the

transportation system– Understand the performance of your

management systems– Feed the analysis efforts that examine ways to

improve the transportation system

ADUS

• Management of the transportation system can not be done without knowledge of its performance

• You can’t manage what you can’t measure

What you measure gets managed

ADUS

• We are now beginning to store the data we already collect

• The next step will be to actually use the data we store to improve management of the system

ADUS

• The difficulty comes not from collecting ITS data but from storing the data and making the stored data useful

ADUS• Data storage and use requires an archive

system– Data collection– Data transfer to the archive– Data storage (aggregation?)– Analysis and reporting

• Quality assurance

• Integration with other data sources

– Database management

ADUS

• ITS systems produce data – already - often continuous data

• Large volumes of data are:– Difficult to handle– Expensive to store and manipulate– Not something DOTs are used to dealing with

ADUS

• The collection of data for data’s sake is a waste of money

• Collecting data is only a good idea, if you intend to use it

ADUS

• To maintain a useful archive (they’re expensive), the key is:

• Does the data you collect help you run the system more effectively?– Decision support – Performance reporting

ADUS• Data can be used for

– Operations planning– Maintenance planning– Safety analysis – Facility performance monitoring– Policy analyses– Congestion monitoring– Systems planning– Environmental analysis

But are the data actually used for those purposes?

ATMS – Types of Data Available

• Vehicle volumes

• Vehicle speeds

• Travel time measurements

• Origin / destination patterns (from tolls)

• Incident locations and durations

• A variety of more specialized data items– Volumes by various vehicle classifications

APTS – Types of Data Available

• Transit ridership

• Transit vehicle performance

• Vehicle maintenance performance

• Signal system performance

ITS Data

• Continuous data allows measurement of transportation system performance variability

• Reliability is a key to management of the transportation system

ITS Data Are Different

• Allows more detailed analysis

• Requires creativity

Why Creativity?

• ITS often provide different (better) measures of performance than traditionally used

An Example of Using an Archive

Freeway Performance Data

Used for Policy Analysis

(Are our policies doing any good?)

Traditional Performance Measures

• Do not describe the complexity of what is happening on the roadway

• Are not easily understood by most decision makers and/or the public

Traditional Performance Measures

• Reported measures traditionally are:– v / c ratios

– Usually based on limited data, and a poor mechanism for showing changing conditions during the day

– LOS– Hard for non-technical people to understand

– Based on limited data

– Travel time and delay– Often based on very limited sample, or some very imperfect

calculations

0

500

1000

1500

2000

2500

12 AM 2 AM 4 AM 6 AM 8 AM 10 AM 12 PM 2 PM 4 PM 6 PM 8 PM 10 PM

Estimated Weekday Volume (Nov 98)I-405 NE 4th St-NB HOV NB _

Improved Performance Measures

• This allows you to illustrate some very important trends to a general audience in non-technical terms

I-405 NE 37th St GP SB

0

500

1000

1500

2000

2500


Estimated Weekday Volume Profile: GP and HOV Lanes (Nov 98)

GP

HOV


• But volume alone does not tell someone whether the facility is working effectively

• Color coding speed information on top of volume data yields a more descriptive picture of performance

I-5 NE 45th St-SB GP SB

0

500

1000

1500

2000

2500


Estimated Volume and Speed Conditions (2/17/00)

I-5 S Spokane St GP NB

0

500

1000

1500

2000

2500


Estimated GP and HOV Volume and Speed Conditions

HOV speed < 45 mph

Saturday, J uly 31, 1999 DataMulticolor = Average GP LaneGray = HOV Lane


• Unfortunately, averaging speeds over many days often hides the fact of how often a facility is congested

0

500

1000

1500

2000

2500


Estimated Weekday Volume, Speed (1997)I-405 NE 4th St-NB HOV NB _


• We display that information based on the percentage of time a facility falls below a designated speed

I-405 SE 64th St GP NB

0

500

1000

1500

2000

2500


Veh

icle

s P

er

Lan

e P

er

Hou

r (V

PLP

H)

0

10

20

30

40

50

60

70

80

90

100

Con

gesti

on

Fre

qu

en

cy (

%)

Estimated Volume, Speed, and Reliability Conditions (2003)

Freq. Of LOS F(stop and go)


• This can show you what happens when a major change in freeway operations takes place

• In this case a switch from outside to inside HOV lane operation

• It also illustrates other trends

0

500

1000

1500

2000

2500


0

10

20

30

40

50

60

70

80

90

100Cong.VPLPH

Estimated Weekday Volume, Speed, and Reliability Conditions (1997)I-405 NE 4th St-NB HOV NB _

0

500

1000

1500

2000

2500


Estimated Weekday Volume (Nov 98)I-405 NE 4th St-NB HOV NB _

I-405 NE 37th St GP NB

0

500

1000

1500

2000

2500

12 AM 2 AM 4 AM 6 AM 8 AM 10 AM 12 PM 2 PM 4 PM 6 PM 8 PM 10 PM0

10

20

30

40

50

60

70

80

90

100

Estimated Weekday Volume, Speed, and Reliability Conditions (1999)

GP

HOV


• But freeway performance varies significantly from location to location

SR-520 76th Ave NE GP WB

0

500

1000

1500

2000

2500


0

10

20

30

40

50

60

70

80

90

100

Estimated Weekday Volume, Speed, and Reliability Conditions

SR-520 76th Ave NE GP EB

0

500

1000

1500

2000

2500


0

10

20

30

40

50

60

70

80

90

100

Estimated Weekday Volume, Speed, and Reliability Conditions

SR-520 76th Ave NE GP WB

-20

0

20

40

60

80

100


Estimated Change in Travel Reliability Conditions (1997 vs.

The Effect of Starting AM Ramp Metering on SR-520

0

10

20

30

40

50

60

70

80

90

5:30 AM 7:30 AM 9:30 AM 11:30 AM 1:30 PM 3:30 PM 5:30 PM 7:30 PM

Time of Day

Fre

qu

ency

of

Co

ng

esti

on

0

200

400

600

800

1000

1200

1400

1600

1800

2000

Ho

url

y V

olu

me

Per

Lan

e (v

plp

h)

2001 Congestion

1999 Congestion

2001 Volume

1999 Volume

170 veh / hr / ln improvement

LOS F occurs 1 day per week less often

Improved Performance Measures• This means that it is important to

– Choose your location carefully– Report on multiple locations– Report on geographic variation

• So we developed a geographic illustration of traffic performance

Time PMAM0 2 4 6 8 10 12 2 4 6 8 10 12

Time PMAM0 2 4 6 8 10 12 2 4 6 8 10 12

405

5

Montlake Blvd.

520

Arboretum

92nd Ave.

B’vue. Way

148th Ave.

NE 60th St.

84th Ave.

Lk. Wash.

Uncongested, near speed limit

Restricted movement but near speed limit

More heavily congested, 45 - 55 mph

Extremely congested, unstable flow

Westbound

SR 520 Traffic Profile General Purpose Lanes 1997 Weekday Average East bound


• Geographic illustration can be

– Volume– Speed– Lane occupancy– Other

Time

182

180

178

176

174

172

170

168

166

Mil

ep

os

t

0 2 4 6 8 10 12 2 4 6 8 10 12

Time

182

180

178

176

174

172

170

168

166

Mil

ep

os

t

0 2 4 6 8 10 12 2 4 6 8 10 12AM PM AM PM

Olive Way

Snohomish County

King County

NE 175th

Northgate Way

405

5

520

522

NE 45th

Uncongested, near speed limit

Restricted movement but near speed limit

More heavily congested, 45 - 55 mph

Extremely congested, unstable flow

NorthboundSouthbound

Interstate 5 North Traffic Profile General Purpose Lanes 1997 Weekday Average

Time

Mil

ep

os

t

0 2 4 6 8 10 12 2 4 6 8 10 12AM PM

153

189

160

170

180

0 2 4 6 8 10 12 2 4 6 8 10 12

Time

Mil

ep

os

t

AM PM

153

189

160

170

180Snohomish Co.

King County

4055

526

99

90

405

520

522

128th St

175th St

Spokane St

Madison St

145th St

< 1 1 - 1.9 2 - 2.9 3 - 3.9 4 - 5.9

Congested weekend days per month

6+

Interstate 5 LOS F Frequency General Purpose Lanes 1999 Weekend Average

Time

Mil

ep

os

t

0 2 4 6 8 10 12 2 4 6 8 10 12AM PM

153

189

160

170

180

0 2 4 6 8 10 12 2 4 6 8 10 12

Time

Mil

ep

os

t

AM PM

153

189

160

170

180Snohomish Co.

King County

4055

526

99

90

405

520

522

128th St

175th St

Spokane St

Madison St

145th St

< 1 1 - 1.9 2 - 2.9 3 - 3.9 4 - 5.9


6+

Interstate 5 LOS E Frequency General Purpose Lanes 1999 Weekend Average

Time

Mil

ep

os

t

0 2 4 6 8 10 12 2 4 6 8 10 12AM PM

153

189

160

170

180

0 2 4 6 8 10 12 2 4 6 8 10 12

Time

Mil

ep

os

t

AM PM

153

189

160

170

180Snohomish Co.

King County

4055

526

99

90

405

520

522

128th St

175th St

Spokane St

Madison St

145th St

< 1 1 - 1.9 2 - 2.9 3 - 3.9 4 - 5.9


6+

Interstate 5 LOS D Frequency General Purpose Lanes 1999 Weekend Average


• The basic geographic by time of day matrix allows us to compute travel times starting every five minutes, 365 days per year

• These travel times can then be summarized

0:00

0:10

0:20

0:30

0:40

0:50

1:00


Trip Start Time

Est

imate

d A

vera

ge T

ravel Tim

e (

hou

r:m

in)

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

Con

g.

Freq

uen

cy (

Sp

eed

< 3

5 m

ph

)

Congestion Frequency Avg. GP Travel Time 90th Percentile GP Travel Time

405

90

520

N

Bellevue

Tukwila

5

4


• Travel time summaries include

– Average travel time for a given O/D pair by time of day (every five minutes)

– 90th percentile travel time– Frequency with which a given average speed is

not achieved


• Travel times can also be compared

– Against standards

– For HOV versus SOV

Northbound, Andover Park E to Coal Creek Pkwy (9.4 miles)

0

10

20

30

40

50

60

Trip Start Time

Av

era

ge

Sp

ee

d (

mp

h)

0

10

20

30

40

50

60

70

80

90

100

Sp

ee

d R

eli

ab

ilit

y (

% d

ay

s <

45

mp

h)

Speed Threshold: >=45mph

Speed Relibility Threshold: Speed lower than 45mph occurs <=10% of time Speed Reliability (%)

90th Percentile Average Speed (MPH)

Northbound, SE 20th St to NE 160th St (10.7 miles)

0:10

0:11

0:12

0:13

0:14

0:15

0:16

0:17

0:18

0:19

0:20

0:21

0:22

0:23

0:24

Trip Start Time

Ave

rage

Tra

vel T

ime

(hr:

min

)

HOV

GP

Average Travel Time Savings in HOV Lane During PM Peak Period: 8 Minutes


• When truck volume and weight data become available for freeways, these same matrices (and some assumptions) can be used to compute:

– Truck hours of delay

– Truck miles of delay

– Ton-miles of delay

– Value of freight delay


• Each time we use our new tools to answer a question, we develop new ways to display that information

• The goal is to make that information – Easier to understand– More accurate of “real life”

Archived Data User Services (ADUS). ITS Produce Data The (sensor) data are used for to help take...

Documents

Transcript of Archived Data User Services (ADUS). ITS Produce Data The (sensor) data are used for to help take...