I394 MnPASS HOV Lanes

1
I-394 MnPASS HOV Lanes
High Occupancy Vehicle (HOV) Pooled Fund Study
(PFS) 2005 Annual Meeting - May 17 and 18
2
Background
2002 Study Twin Cities high-occupancy (HOV )
lanes are underutilized while the adjacent
general-purpose lanes are chronically
congested. Need to preserve the transit and
carpool advantage if allowing single occupant
vehicles (SOVs) in the HOV.
3
Background (Cont)

• 394 HOV Lane built in 1992
• The funding source for HOV lanes, the 2002 HOV
  study, and the legislature established that the
  HOV lane cannot simply be opened to all SOVs
• In 2003, Legislature authorized HOV conversion to
  high occupancy toll (HOT) lanes
• Strong bi-partisan support
• Community Task Force Established
• September 2003 to September 2004

4
Schedule of Milestones

• Construction
• Completed
• Testing - Now through May
• Customer Service Center
• Opened on April 11, 2005
• Lane Striping
• Complete
• MnPASS I-394 opens
• May 16, 2005

5
How will revenues be used?

• First, to pay the cost of project infrastructure,
  administration, maintenance and operations
• After that, 50 for transit improvements and 50
  for corridor improvements (state law).
• All improvements must be in I-394 area.

6
MnPASS Objectives

• Improve efficiency of I-394 increase person and
  vehicle-carrying capabilities of HOV lanes
• Maintain free flow speeds for transit, carpools,
  and MnPASS users
• Improve highway and transit in corridor with
  revenues generated by MnPASS
• Use electronic toll collection
  tags/transponders and readers - - no toll booths
• Employ new ITS technologies such as dynamic
  pricing and in-vehicle electronic enforcement

7
I-394 Express LanesCommunity Task Force

• 22-person group of leaders and citizens appointed
  by the Governor and Lt. Governor and communities
• Bi-partisan and diverse make-up, local
  representatives
• Reviewed express lane issues
• Prices, access, enforcement, hours of operation,
  etc.
• Provided input to Mn/DOT
• Also sought input from interested people and
  groups
• Open Houses, Focus Groups, Community Council
  presentations

8
MnPASS Express Lanes

• Two-lane barrier-separated reversible section
  and one-lane-per-direction diamond lane in the
  middle of a four-lane freeway
• 10-12 miles long
• 11 access points in the diamond lane section
• HOVs and transit free- no transponder needed
• No heavy vehicles allowed
• Managed through dynamic pricing

9
Two Lane Barrier Reversible Lane
10
Diamond Lane Design
11
HOT Lane Access Points
12
Toll Collection

• Dynamic pricing based on congestion
• Peak average 1.00-4.00 8.00 max
• Off-peak average 0.25 per section

13
Hours of Operation

• Diamond Lanes operate 24/7
• Reversible section
• Eastbound from 500 a.m. to 100 p.m.
• Westbound from 2 p.m. to 4 a.m.
• Weekend schedule varied for special events
• First time open for use by SOVs

14
Enforcement

• Essential to success of MnPASS
• Increased enforcement through partnerships with
• Minneapolis Police Department
• Golden Valley Police Department
• Metro Transit Police
• Minnesota State Patrol
• Petty misdemeanor with 130 fine and a moving
  violation
• Technology will assist enforcement

15
Flashing Beacon Enforcement
16
Audio/Visual Mobile Enforcement Indicator
17
Subscribing is Easy

• Four simple steps
• Complete transponder lease agreement
• Provide credit card
• Receive transponder and instructions
• Get in and go

18
How to Subscribe

• Online
• www.mnpass.net
• By phone
• 1-866-397-4334
• In person
• Customer Service Center, 2055 N. Lilac Drive,
  Golden Valley

19
Evaluation Approach

• Two separate evaluation teams will coordinate in
  the overall assessment
• Technical System Performance Evaluation
• Attitudinal Evaluation Team
• On-going evaluation activities will be conducted
  over the next two years.

20
Technical Evaluation Goals

• Why evaluate?
• To provide the public and decision-makers with
  information on the observed impacts
• To provide feedback on system performance
• To provide a solid foundation for any future
  decisions regarding potential expansion of the
  system
• To provide a reproducible evaluation framework

21
Technical Evaluation Objectives

• Identify changes in
• travel speeds and travel times
• person and vehicle throughput
• safety
• enforcement activity
• environmental factors
• Document operations, costs, revenues

22
Whats the Biggest Tech. Evaluation Challenge?

• The MnPASS implementation will add a new variable
  (price) to what is already a dynamic operational
  environment
• Challenged is to isolate the impacts of the
  MnPASS system from the background changes when
  comparing conditions before and after deployment

23
Questions and More Information

• Visit www.mnpass.net
• Contact Nick Thompson, Project Manager
• 651-634-5310
• nick.thompson_at_dot.state.mn.us
• or
• Paul Czech, Planning Director
• 651-582-1771
• paul.czec_at_dot.state.mn.us