MN IDS Project Progress Update

MN IDS Update

Progress to date Test Intersection Sensor evaluation results Benefit:cost efforts progress Human Factors (Max) Rural Intersection Pooled Fund Study (Max)

Upcoming work Intersection on line Simulator Studies MUTCD approval Benefit:cost analyses

MN IDS Test Intersection

Design Completed 15 Jan 2004 Design review with Mn/DOT traffic, geometric,

district, and ESS engineers Good advice

• Recommendations for sensor mounts• Nothing in the median lasts

Revised cross-roads surveillance • Laser sensors to Visible Light/IR Cameras

Explored opportunity to cooperate on construction• Month of negotiations, didn’t work out.

ROC 52 ESS

MN Test Intersection Overview

Present Instrumentation

Mainline Vehicle speed, position, lane of travel (Radar) 2000 foot coverage before Xroads (Radar) 800 foot coverage beyond (Radar) 53’x36’ coverage at camera (IR/Visible) Hardwired and Wireless Communication

• Cost and performance trade-off analyses

Crossroads Vehicle type (Radar and laser based) Vehicle approach speed (adapt VA technology at a later date?) Trajectory leaving minor road

• Right turn (camera + radar)• Straight through (camera)• Left turn (camera + radar)

MN Test Intersection-Mainline Sensors

Radar

Camera Suite(for evaluation)

Camera FOV53’x36’

Radar to track vehicles past crossroads (primarily for minor road trajectory recording)

Mainline Highlights

Camera / mast provides independent means to verify Radar performance Camera performance Gap tracker performance Emerging technologies

May or may not be part of final system Benefit:cost analysis Poor weather capability of vision based systems

Mainline Radar Sensor

Laser / Radar Sensor Mount

•Approved by Mn/DOT Right-of-Way Engineer•350 Crash worthy•Will include break-away conduit and connector•Will include reflector at top of 3# U channel

Radar Performance Results: Geometrics

//

Radar Beam

Lane 1

Lane 2

DLC

2

DLC

1

L1Cov

L2Cov

Radar Beam Range (440 ft)

= Radar Orientation Angle (w .r.t. lane)DLC1 = Sensor Distance from Lane-center 1DLC2 = Sensor Distance from Lane-center 2LCov1 = Theoretical Lane coverage (Lane 1)LCov2 = Theoretical Lane coverage (Lane 2)

BeamWidth(120)

ActualVehiclePosition

SensorReportedPosition

RadarStation

}}

Radar Performance Results: Coverage

Radar Performance Results: Lane Classification Errors

Radar Performance Results: Speed Errors

Intersection Crossroads-Vehicle Trajectory

C4 FOV

C3 FOV

Cameras at intersection corners capture the trajectory of vehicles entering intersection from minor roads. Mn/DOT advised that median-based sensors won’t live. (Crashed out).

Camera Mount Detail

Camera Based Validation

Tracking on this side

No tracking on this side

Intersection Crossroads – Vehicle Classification

Horizontal LaserScanner

Vertical LaserScanner

Classification Capable T-300 Radar

Classification Capable T-300 Radar

R/WIS Data from Intersection

Mn/DOT updates at 10 Minute intervals. Data collected every 10 minutes

Information Available from Intersection

Distribution of gaps accepted by drivers for right turns for left turns for crossing intersection (see next page)

Cross-correlated with Vehicle type / size Driver age (macroscopic level, limited basis initially) Driver gender (limited basis initially) Weather effects (R/WIS 0.9 Mile away), with in-road

sensors (collecting data already)

Information Available from Intersection (cont’d)

Maneuvers executed by drivers from minor road Left turn in one stage or two?

• Variation in left and right gaps accepted for each maneuver type

• Cross-correlation with vehicle type

Crossing intersection in one stage or two? • Variation in left and right gaps accepted for each maneuver

type• Cross-correlation with vehicle type

Information Available from Intersection (cont’d)

Response of mainline traffic Speed adjustment if stationary vehicle on minor road

• Do mainline drivers adjust speed if a vehicle is spotted on minor road?

• Will mainline drivers move to left lane (when possible) to provide a lane for the minor road traffic?

Reaction of drivers on major road if too small gap is accepted

• Braking?• Lane change? • Other?

Design Detail: Main Controller Cabinet

Ethernet Switch

Main Control Computer

MarshallVL2122 Rcrv

MarshallVL2122 Rcrv

MarshallVL2122 Rcrv

MarshallVL2122 Rcrv

Circuit Breaker Panel50Amp. Power

sourced from MainDistribution Cabinet

Cabinet Power Outlet

Phone Jack

Ethernet fromSouthbound Lane

Ethernet from Northbound Lane

Video fromNorthbound Lane

Video fromSouthbound Lane

Ethernet Switch

2158 Power

SupplyPowerSupply

1001RChassis21

58

2158

2158

2158

2158

2158

2158

2158

2158

2158

2158

2158 Power

SupplyPowerSupply

1001RChassis21

58

2158

2158

2158

2158

2158

2158

2158

2158

2158

2158

c

iDAQ ComputerRemovable Hard Drive

120 VAC Outlet Strip with Surge ProtectionMinimum 12 outlets

iDAQ Computer 2

c c

MarshallVL2122 Rcrv

MarshallVL2122 Rcrv

Removable Hard Drive

Cabinet, BreakerPanel, and 120 VoltOutlet Supplied byUniversity. Cabinetto be installed bycontractor.Conctractor willmake 120 voltconnection frompower distributioncabinet to the maincontroller circuitbreaker and theinternal 120 Voutlet.

Design Detail: Intersection Cabling

3" Conduit

RE1

Cable Distribution Along Southbound Leg

R1

R6

RE2RE3

RE4RE5

RE6

RE7

R7

SE2

SE1

V1

CS

AH

9

Note: This camera masthouses Extron video signalamplifier. Thus, dual cable

runs.

CABLE COUNTEleven EthernetFour VideoOne Power

Handhole

V2V3

V2

3"Conduit

Hwy52

3"

Co

nd

uit

3"

Co

nd

uit

V4

3"

Co

nd

uit

Handhole

CE1

R5R4R3R2

3"

Co

nd

uit

RE

1

RE

2

V5CE2

V1

RE

3R

E4

RE

5R

E6

RE

7S

E1

SE

2

CE

2

CE

1

V5

V4

V3

HandholesHandhole

3" Conduit 3"Conduit

V2

RE

1

RE

2

RE

3R

E4

RE

5R

E6

RE

7S

E1

SE

2

CE

2

CE

1

V5

V4V3

Handhole

4-Twisted Pair, Plenum Cat 5 Cablein 1in schedule 80 non-metal conduitunless specified otherwise

Dual Lead, common ground RG 6 cablein 1in schedule 80 conduit unlessotherwise specified

Legend

Camera Mast/Base

Radar / Laser Cabinet

ONE 3-Conductor, 4/0 gage THWN CuCable, with separate ground wire in3in non-metal schedule 80 conduit

ONE 3-Conductor, 3/0 gage THWN CuCable, with separate ground wire in 3innon-metal schedule 80 conduit.

Handholes per Mn/DOT StandardPlate 8114A

3" Conduit

Design Detail: Intersection Cabling

Cable Distribution Along Northbound Leg

SE

4

CS

AH

9

RE8

V6

RE14RE13

CE

3

CABLE COUNTEleven EthernetFour VideoOne Power

ControlCabinet(334)

PhoneConnection

ElectricMeter

From Transformer

PowerServiceCabinet

(L2)

Hwy52

3"

Co

nd

uit

3"

Co

nd

uit

R8R10 R9

RE9RE10

R11R12

RE11

RE12

Handholes

3" Conduit 3"Conduit

V2

RE

1

RE

2

RE

3R

E4

RE

5R

E6

RE

7S

E1

SE

2

CE

2

CE

1

V5

V4V3

3" Conduit

V2

3"Conduit

RE

1

RE

2

RE

3R

E4

RE

5R

E6

RE

7S

E1

SE

2

CE

2

CE

1

V5

V4

V3

V8

3"

Co

nd

uit

S3

S4

R14 R13

3"

Co

nd

uit

SE

3V

7

HandholesCE4

4-Twisted Pair, Plenum Cat 5 Cablein 1in schedule 80 non-metal conduitunless specified otherwise

Dual Lead, common ground RG 6 cablein 1in schedule 80 conduit unlessotherwise specified

Legend

Camera Mast/Base

Radar / Laser Cabinet

ONE 3-Conductor, 4/0 gage THWN CuCable, with separate ground wire in3in non-metal schedule 80 conduit

ONE 3-Conductor, 3/0 gage THWN CuCable, with separate ground wire in 3innon-metal schedule 80 conduit.

Handholes per Mn/DOT StandardPlate 8114A

Intersection Build Details

Hardware Cameras, radar, lasers, camera masts, radar

stations, etc., ordered or out on bid. iDAQ (intersection Data AcQuisition) computers built

Software Camera based vehicle tracking software under

continued development (20 FPS vs. existing 5 FPS for improved tracking and robustness)

Wireless system integrity software scaled from Demo 2003 version

Intersection Build Details

Construction Bid to purchasing 12 March 2004 UMN VP signature expected 16 March 2004 Bids due back 2 weeks after bid is published. 04 June 2004 end date specified Cold cold winter, need to avoid frozen ground

trenching costs.

MUTCD Approval Process

Howard Preston contract, phase II executed.

Task Highlights which follow Mn/MUTCD Section 1A.10 Documentation of the design process, from crash analysis to

simulator study results Patent search Development of acceptable research plan for the ensuing FOT

• Data collection

• MOE’s Semi-annual progress reports to FHWA Office of

Transportation Operations

Benefit Cost Analysis: Concept

Service ChargesOther Costs

Fatality & InjuryProperty Damage

Time SavingsFuel Consumption

Benefits Costs

Users

ServiceProviders

Society/Community

Capital CostsOperating and

Maintaining Costs

Capital CostsOther Costs

Cost Savings(O&M)

EfficiencyEnhanced Facility

Fatality & InjuryProperty Damage

Emissions

Benefit Cost Analysis: Framework

Sensitivity Analysis

TraditionalEngineering

ScenarioITS Scenario

Baseline(Do-Nothing)

Scenario

CostAnalysis

BenefitAnalysis

CostAnalysis

BenefitAnalysis

CostAnalysis

BenefitAnalysis

Benefit Cost Ratio Comparison

Recommendations

Identify Sub-Market Impacts

NPV NPV

Identify Sub-Market Impacts

Identify Sub-Market Impacts

NPV

NPV: Net Present Value

Benefit Cost Analysis: Status

Work complete/in progress Subtask C1: Identify relevant

technologies, Review of Literature.

Subtask C2: Develop Benefit Cost Framework.

Subtask C3: Estimate Lifespan of Technology.

Subtask C4: Estimate Costs of technology.

Subtask C5: Estimate Benefits of Countermeasures.

Subtask C6: Lifecycle Analysis.

Work yet to be undertaken Subtask C7: Recommend

Countermeasures. Subtask C8: Analyze Inter-

technology Effects. Subtask C9: Determine

Performance Metrics. Subtask C10: Develop

cost:performance models. Subtask 11: Analyze

Synergies. Subtask 12: Optimize

Counter-measure Combination.

Schedule Adherence

TODAYIntersection Brought On-lineHuman Factors Simulator DII Testing BeginsFinal Report Preparation Begins