Urban Transit
61
-7
Second, the headway is usually restricted to a set of acceptable values, {
h
}. This set is based on four
considerations: (1) whole minute headways are usually required because schedules are written in whole
minutes (exception: some rail systems use the half-minute or quarter-minute as the basic unit);
(2) multiples of 5 min are desired for long headways; (3) headways that repeat every hour (e.g., 12, 15,
20, 30 min) are desirable; and (4) there is a maximum headway, called a
policy headway,
that may not
be exceeded, usually 60 min but sometimes 30 min or smaller in peak periods. For example, one set of
acceptable headways might be
(61.5)
while a more restrictive set might be
(61.6)
Third, the number of vehicles must be an integer (unless the route is not operated in isolation, in which
case scheduling must be done jointly for a number of routes, as discussed in Section 61.5). The result of
these last two constraints is to force additional slack into the schedule, in the form of both excess capacity
and excess layover.
Schedule design usually begins with a given peak volume and a given minimum cycle time (
c
min
) that
accounts for running time and minimum necessary layover. The schedule design procedure that follows
has as its primary objective minimizing fleet size (about the same as minimizing cost); its secondary
objective, for a given fleet size, is to maximize service frequency (maximize service quality). In what
follows, [ ]
+
means round up and [ ]
–
means round down. This procedure assumes that cycle times and
headways are in minutes, while frequencies and passenger volumes are hourly.
Step 1.
h
max
= [
k
/(
v
*
/60)]
–
(round down to next acceptable headway)
Step 2.
n
= [
c
min
/
h
max
]
+
Step 3.
h
= [
c
min
/
n
]
+
(round up to next acceptable headway)
Step 4.
Given
n
and
h
, determine the remaining parameters (
c, q, l
p
) using Eqs. (61.2) and (61.4). The
difference between
c and c
min
, called schedule slack, is added to the layover.
The rounding involved in steps 1 and 2 can add substantially to operating cost. For example, consider
a route for which v* = 260/h, c
min
= 51 min, and k = 50. If one ignores rounding, the minimal service
frequency is 260/50 = 5.2/h, the headway is 60/5.2 = 11.5 min, and the number of vehicles needed is
51/11.5 = 4.4. While this kind of analysis can be done in sketch planning, it does not produce a workable
design. Following are two designs using the preceding procedure; their difference is that one uses set {h
I
},
which allows an 11-min headway, while the other uses {h
II
}, which does not.
This example demonstrates the substantial effect of rounding. In case I, rounding increased fleet
requirements from the sketch planning value of 4.4 to 5. The extra resources consumed are manifest as
slack in the cycle time (the final cycle time, 55 min, is 4 min greater than required) and in slack capacity
(peak load, 47.7, is below the allowed capacity of 50). Case II, by not permitting an 11-min headway,
requires more rounding, increasing the vehicle requirement to 6. However, the extra resources are not
all wasted but are partially converted into extra service as service frequency increases, reducing passenger
Set of h
max
Acceptable Unrounded h
max
nhc
Case Headways (min) (min) Unrounded n (min) (min) l
p
I{h
1
} 11.5 11 4.64 5 11 55 47.7
II {h
II
} 11.5 10 5.1 6 9 54 39.0
h
I
{}
=º
{}
12 2025 30 35 40 45 50 55 60,, , ,,,,,,,,
h
II
{}
=º
{}
12 1012 15 20 30 60,, , ,,,,,