01.11.2014 Views

Short Range Transit Plan 2008-2013 - Omnitrans

Short Range Transit Plan 2008-2013 - Omnitrans

Short Range Transit Plan 2008-2013 - Omnitrans

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

IBI GROUP<br />

SHORT RANGE TRANSIT PLAN REPORT<br />

OMNITRANS COMPREHENSIVE OPERATIONAL ASSESSMENT<br />

& SHORT RANGE TRANSIT PLAN<br />

9.5 OmniLink Service Assessment<br />

Effective May 7, 2007, OmniLink annual revenue hours were reduced by 4,000 through a combination of<br />

the discontinuation of Saturday and Sunday service and a reduction in weekday service hours due to<br />

anticipated productivity improvements. No further OmniLink service cuts are scheduled for the remainder<br />

of the <strong>2008</strong>-<strong>2013</strong> <strong>Omnitrans</strong> SRTP timeframe. The proposed OmniLink service hour cuts and fare<br />

increases will result in a planned farebox recovery ratio ranging from 7.4% in <strong>2008</strong> to 7.6% in <strong>2013</strong>,<br />

peaking at 7.8% in 2012. During the <strong>2008</strong>-<strong>2013</strong> <strong>Omnitrans</strong> SRTP timeframe, OmniLink farebox recovery<br />

will fall short of the 10% farebox recovery goal established for OmniLink service.<br />

Further productivity improvements and weekday revenue hour reductions are possible in the later stages<br />

of the <strong>2008</strong>-<strong>2013</strong> <strong>Omnitrans</strong> SRTP as the OmniLink service contractor is able to more effectively use the<br />

upgraded Trapeze PASS software. General public demand-response services in compact service areas<br />

such as Yucaipa should be able to carry five to six passengers per revenue hour. Through effective<br />

scheduling, demand-response services can reduce revenue hours and accommodate more trips with<br />

fewer revenue hours. This approach is the most effective way of reducing demand-response costs and<br />

improving farebox recovery.<br />

9.6 Potential OmniLink Service Improvements<br />

Assuming OmniLink productivity can be improved through enhanced trip assignment, the following<br />

weekday revenue hour reductions 9 are possible:<br />

Reduce Chino Hills OmniLink weekday revenue hours by 1,016 per annum.<br />

Contingent on improved scheduling efficiency, Chino Hills OmniLink can operate with 1,016 fewer annual<br />

revenue hours and one fewer bus. This reduction will facilitate reducing the peak bus pullout requirement<br />

from four to three buses. Figure 9-14 provides an overview of potential shifts for three weekday buses.<br />

Based on the analysis of passenger loads, there will be sufficient capacity to cover existing school loads,<br />

the Chino Senior Center shuttle and general trip making. This does not assume expanded school<br />

services.<br />

Reduce Yucaipa OmniLink weekday revenue hours by 3,946 per annum.<br />

Contingent on improved scheduling efficiency, Yucaipa OmniLink can operate with 3,946 fewer annual<br />

revenue hours and one fewer bus. This reduction will facilitate reducing the peak bus pullout requirement<br />

from seven to six buses. Figure 9-15 provides an overview of potential shifts for up to six weekday<br />

buses. One full straight shift was cut and the splits were left in on the days of high demand. Based on the<br />

analysis of passenger loads, there will be sufficient capacity to cover existing school loads, lunch breaks,<br />

and general trip making. This does not assume expanded school services.<br />

Procedural, service parameter and training assumptions necessary to improve scheduling efficiency are<br />

outlined in the following text.<br />

9<br />

Initially based on an assessment of OmniLink operations in October 2006. The assessment does not reflect May 7, 2007 service<br />

changes. However, it does provide a strategy worthy of consideration in the later stages of the SRTP.<br />

July 11, 2007 197

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!