This chapter describes a set
of service improvements designed to provide public transportation service to
The proposed improvements
include modifications to existing routes and new routes. One of the primary design objectives was to
provide cost-effective public transportation that would have a minimal impact
on annual operating costs. Another key goal
was to provide connections to major activity centers that are direct and easy
to understand. The proposed improvements
will give some residents and businesses a new transportation alternative. For existing customers, the CityBus service
area will be expanded and access to new and planned activity centers will be
provided.
The success of the proposed
improvements will partly depend on how growth is managed in these developing
areas. If new residential areas and
retail centers are designed to make it easier for buses to circulate and stop
at customer-friendly locations, CityBus will be able to provide more efficient
and cost effective improvements in the future.
Area Description
The primary land uses in
Another development that contributed
to the interest in
CityBus already offers
outstanding connections between routes and travel destinations throughout
Proposed Improvements
This section presents a set
of alternatives designed to serve
Alternative One (Sub-Option
A) extends Route 7 to the new Clarian-Arnett Medical Center and the community
center at Faith Baptist Church. The
proposed alignment also serves the single-family housing areas east of CR
500E. A map of the proposed alignment is
provided on the following page. The
sub-options described below involve different service frequencies, and do not affect
the alignment.
Alternative One – Sub-Option A
Key Operating Characteristics
|
Round Trip Mileage |
21.2 miles |
|
Average Speed
(based on current route) |
15.0 mph |
|
Estimated Round
Trip Run Time |
85 minutes |
|
Layover/Driver
Recovery |
5 minutes |
|
Total Estimated
Run Time Per Trip |
90 minutes |
|
Weekday Hours of
Operation |
|
|
Weekday Frequency |
30 minutes |
|
Weekday Vehicle
Requirement |
3 |
|
Saturday Hours of
Operation |
|
|
Saturday Frequency |
30 minutes |
|
Saturday Vehicle
Requirement |
3 |
|
Sunday Hours of
Operation |
|
|
Sunday Frequency |
90 minutes |
|
Sunday Vehicle
Requirement |
1 |
The weekday frequency of
service (30 minutes) is maintained, but the Saturday frequency improves from 60
minutes to every 30 minutes. Under this
sub-option, it is necessary to set the Sunday frequency at 90 minutes to
minimize the vehicle requirements and costs.
The hours of operation also stay about the same. The number of buses required under this
option increases to three on weekdays and Saturdays. One vehicle is required on Sunday.
The projected revenue hours
and miles of service for Sub-Option A are compared to existing levels in the
following table.
|
|
Weekday |
Saturday |
Sunday |
|||
|
Existing |
Proposed |
Existing |
Proposed |
Existing |
Proposed |
|
|
Revenue Hours |
26.33 |
37.5 |
10.0 |
33.0 |
10.0 |
9.0 |
|
Revenue Miles |
353.5 |
530.0 |
172.7 |
466.4 |
143.9 |
127.2 |
Alternative One – Sub-Option
B is based on the same modified Route 7 alignment. Under this option, however, the weekday
service frequency will be 30 minutes while the Saturday and Sunday frequency will
be 90 minutes. Based on these specific
frequencies, the weekday vehicle requirement is three vehicles while one
vehicle is needed to operate the Saturday and Sunday service.
The hours of operation remain
the same. Operating characteristics and
the projected revenue hours and miles of service are detailed in the following
tables.
Alternative One – Sub-Option B
Key Operating Characteristics
|
Round Trip Mileage |
21.2 miles |
|
Average Speed
(based on current route) |
15.0 mph |
|
Estimated Round
Trip Run Time |
85 minutes |
|
Layover/Driver
Recovery |
5 minutes |
|
Total Estimated
Run Time Per Trip |
90 minutes |
|
Weekday Hours of
Operation |
|
|
Weekday Frequency |
30 minutes |
|
Weekday Vehicle
Requirement |
3 |
|
Saturday Hours of
Operation |
|
|
Saturday Frequency |
90 minutes |
|
Saturday Vehicle
Requirement |
1 |
|
Sunday Hours of
Operation |
|
|
Sunday Frequency |
90 minutes |
|
Sunday Vehicle
Requirement |
1 |
|
|
Weekday |
Saturday |
Sunday |
|||
|
Existing |
Proposed |
Existing |
Proposed |
Existing |
Proposed |
|
|
Revenue Hours |
26.33 |
37.5 |
10.0 |
12.0 |
10.0 |
10.5 |
|
Revenue Miles |
353.5 |
530.0 |
172.7 |
169.6 |
143.9 |
148.4 |

Similar to Alternative One, this
variation extends Route 7 to the Clarian-Arnett Medical Center, but it does not
serve the Faith Baptist Church community center and the single-family neighborhoods
east of CR 500E. It also eliminates two existing
segments of Route 7 that serve areas north of SR 26E (
The key operating
characteristics for this alternative follow:
|
Round Trip Mileage
(proposed) |
12.6 miles |
|
Average Speed
(based on current route) |
15.0 mph |
|
Estimated Round
Trip Run Time |
51 minutes |
|
Layover/Driver
Recovery |
9 minutes |
|
Total Estimated
Run Time Per Trip |
60 minutes |
|
Weekday Hours of
Operation |
|
|
Weekday Frequency |
30 minutes |
|
Weekday Vehicle
Requirement |
2 |
|
Saturday Hours of
Operation |
|
|
Saturday Frequency |
30 minutes |
|
Saturday Vehicle
Requirement |
2 |
|
Sunday Hours of
Operation |
|
|
Sunday Frequency |
60 minutes |
|
Sunday Vehicle
Requirement |
1 |
The weekday frequency of
service is the same (30 minutes), and the Saturday frequency improves from 60
minutes to every 30 minutes. Under
Sub-Option A, the number of buses required to operate weekday service stays the
same (i.e. two), but the Saturday requirement increases from one to two due to
the improved frequency of service.
Based on these
characteristics, the projected revenue hours and miles of service are compared
to the existing levels in the following table.
As the table shows, weekday hours and miles stay about the same, but
they increase significantly on Saturday and Sunday.
|
|
Weekday |
Saturday |
Sunday |
|||
|
Existing |
Proposed |
Existing |
Proposed |
Existing |
Proposed |
|
|
Revenue Hours |
26.33 |
26.0 |
10.0 |
33.0 |
10.0 |
10.0 |
|
Revenue Miles |
353.5 |
327.6 |
172.7 |
289.8 |
143.9 |
126.0 |

Sub-Option B utilizes the
same Alternative Two route alignment.
Under this option, the weekday service frequency is 30 minutes, but the
Saturday and Sunday frequency is 60 minutes as shown below.
|
Round Trip Mileage
(proposed) |
12.6 miles |
|
Average Speed
(based on current route) |
15.0 mph |
|
Estimated Round
Trip Run Time |
51 minutes |
|
Layover/Driver
Recovery |
9 minutes |
|
Total Estimated
Run Time Per Trip |
60 minutes |
|
Weekday Hours of
Operation |
|
|
Weekday Frequency |
30 minutes |
|
Weekday Vehicle
Requirement |
2 |
|
Saturday Hours of
Operation |
|
|
Saturday Frequency |
30 minutes |
|
Saturday Vehicle
Requirement |
2 |
|
Sunday Hours of
Operation |
|
|
Sunday Frequency |
60 minutes |
|
Sunday Vehicle
Requirement |
1 |
Based on the operating characteristics
of Sub-Option B, the existing and projected revenue hours and miles of service
are compared in the following table.
|
|
Weekday |
Saturday |
Sunday |
|||
|
Existing |
Proposed |
Existing |
Proposed |
Existing |
Proposed |
|
|
Revenue Hours |
26.33 |
26.0 |
10.0 |
12.0 |
10.0 |
10.0 |
|
Revenue Miles |
353.5 |
327.6 |
172.7 |
151.2 |
143.9 |
126.0 |
Estimated Cost
To estimate the incremental
operating cost of providing the proposed services in this study, a two-variable
cost model was developed. The model is
based on 2005 CityBus expenses, which were assigned according to industry
standards to either vehicle hours or vehicle miles. This approach provides two unit cost factors,
cost per vehicle hour and per vehicle mile, which can be used with the
projected hours and miles of service to project operating costs.


The difference between
current and proposed hours and miles of service are multiplied by the unit cost
factors to calculate the added daily cost.
The weekday number is then multiplied by 255, and the Saturday and
Sunday costs are multiplied by 52 to arrive at the added annual operating
costs.
The estimated annual increases
in operating cost for each alternative and sub-option are shown in the
following tables.


Ridership
The number of passengers that
will use new or improved transit routes is not easily measured. Increasing the amount of transit service is
one of the most successful ways to increase ridership, but research shows that
external factors have an even greater impact on ridership. Examples of these factors include population
changes, regional economic conditions, and other public policy decisions.
Some of the methodologies
used in the transit industry to estimate ridership include trend analysis, productivity
of analogous services, service elasticity models, and census tract analysis. For this project, the 2006 average passengers
per hour productivity of analogous CityBus routes are used.
Initially, it is assumed the
new routes will generate about one-half the number of passengers per hour carried
by the analogous routes. This assumption
is used because most new or improved transit routes require a certain period
(1-2 years) to build a stable ridership base.
During this time, management may have to make further adjustments to the
service design and schedule. The extent
of the marketing effort for the new service can also affect the development of
ridership. For example, the Ready2Go
route operated by CityBus took approximately two years to reach its current
level of ridership.
The number of new passengers the

Area Description
Similar to
The
Proposed Improvements
Three new services are
recommended to provide public transportation service to
The purpose of the express
route is to provide service from
The second proposed route is
designed to provide intra-local service within
The final improvement
recommended for
The proposed
The key operating
characteristics for the three new routes follow:
|
|
Purdue Express |
Community Route |
S. |
|
Round Trip Mileage |
10.0 miles |
13.1 miles |
12.1 miles |
|
Estimated Speed |
20.0 mph |
15.0 mph |
13.0 mph |
|
Round Trip Run Time |
58minutes |
53 minutes |
56 minutes |
|
Layover/Driver Recovery |
2 minutes |
7 minutes |
4 minutes |
|
Total Run Time |
60 minutes |
60 minutes |
60 minutes |
|
Weekday Hours of Operation |
|
|
|
|
Weekday Frequency |
30 minutes |
60 minutes |
30 minutes |
|
Weekday Vehicle Requirement |
2 AM; |
1 |
2 |
|
Saturday Hours of Operation |
na |
|
|
|
Saturday Frequency |
na |
60 minutes |
30 minutes |
|
Saturday Vehicle Requirement |
na |
1 |
2 |
|
Sunday Hours of Operation |
na |
na |
na |
|
Sunday Frequency |
na |
na |
na |
|
Sunday Vehicle Requirement |
na |
na |
na |
The estimated miles and hours
of service for each route are shown in the following table. These estimates are based on provisional schedules
designed only to estimate the hours and miles of service. Detailed schedules, which must be prepared by
CityBus staff before the service is implemented, may result in minor changes in
these numbers.

Proposed Alignment

Proposed Alignment

S.
Proposed Alignment

Estimated Cost
The annual increase in
operating costs for each proposed
The estimated costs are shown
by route for weekday and Saturday service.
At this time, no Sunday service is recommended.

Ridership
The additional passenger
trips that may be generated by the proposed
