Fixed-route scheduling - Revision history

BK: added photo

2015-04-24T00:05:02Z

added photo

Jlarose: /* Basics */

2013-12-01T00:49:45Z

Basics

Jlarose: /* Recovery time */

2013-12-01T00:48:14Z

Recovery time

Jlarose at 00:46, 1 December 2013

2013-12-01T00:46:16Z

Jlarose at 05:17, 27 November 2013

2013-11-27T05:17:44Z

Jlarose at 22:39, 24 November 2013

2013-11-24T22:39:24Z

Jlarose: Created page with "== Introduction == Focus on scheduling for an existing or already planned route. Does not address methods for developing a new route from scratch. == Basics == Ascertain basi..."

2013-11-20T00:16:15Z

Created page with "== Introduction == Focus on scheduling for an existing or already planned route. Does not address methods for developing a new route from scratch. == Basics == Ascertain basi..."

New page

== Introduction ==
Focus on scheduling for an existing or already planned route. Does not address methods for developing a new route from scratch.

== Basics ==
Ascertain basic qualities and values: Frequency, consistency (clockface scheduling), connections with other services.
Begin with basic calculations: Based on free-flow speed limits, what is the time end-to-end? Ascertain timepoints if not already done (divide route into roughly equal points, maybe 4 timepoints approximately 10 minutes apart).
Run trial operations collecting data for all days and times of service. Determine how much variation is between peak and off-peak (can affect how many vehicles needed to maintain headways)

=== Putting it all together ===
Adding up times between timepoints. Be sure to allow time for boarding, hopefully based on real or projected ridership. Estimate delay if needed, use an agency average, etc.
Add recovery or layover time. Good rule of thumb is 10% of round-trip time.
Lay out route in a table with departures based on target frequency.

Usually good to test draft product to watch for hiccups.

Some revision may be needed. Small amounts of slack time in the middle of a route may be necessary to account for travel variations. If planning flexible transit route, need to incorporate slack time for deviations but not so much that a no-deviation trip isn't sitting around waiting exceptionally long times.

=== Agency Variation ===
The type of agency and minimum service level vary tremendously between very large cities and small urban areas. Small urban areas may only support hourly or 30-minute headways where in a large city the maximum headway may be 10 minutes or less.

Agencies working with long headways and multiple routes need to carefully consider connections and probably allow greater slack time.

== Adjusting factors ==
Sometimes once everything is factored in, a route appears inefficient. For example, a route in free-flow can do a round trip in 40 minutes, but when all other factors are added the run time is 65 minutes. It may be desirable to get the route down to 60 minutes or less.

Examine: passenger stop delay (boarding, alighting), average traffic speed, signal delay, geographic factors - are buses slowly crawling through tight areas that could be avoided, etc. Use various strategies to reduce. Avoid making route so tight only the best/senior operators are capable of handling it safely. Keep operations administration involved.

== Runcutting and operations ==
SEPARATE ARTICLE?
Once a route is scheduled (or rescheduled), service needs to be segmented into blocks of work.

=== Factors ===
Federal, state, and agency labor policy. How many hours can employees work, how is work assigned (seniority, etc.)

@@ Line 1: / Line 1: @@
 [[Category:Operating effectiveness]]
-INSERT PHOTO OF METRO BUS SCHEDULE SIGN
 == Introduction ==
 Agencies operating fixed-route buses find the need to make adjustments to route scheduling periodically in response to changing circumstances. Bus transit planners should be aware of the basics of fixed-route scheduling. This topic does not cover development of a new fixed-route service, but rather the tuning or re-tuning of an existing or already planned route.

@@ Line 7: / Line 7: @@
 == Basics ==
-The characteristics of the area determine the basic components of service. How frequently will the route run? Where will the bus stops be and what is the distance between them? In small communities, suburban and rural, service may operate once an hour; in major metropolitan areas services may run every ten minutes or even more frequently. Certainly there is a wide range in between. In areas where a route operates on frequent headways, say every 10 minutes or less, passengers more often walk out to the stop without knowing the departure schedule; at most they are likely to only be waiting an average of 5 to 9 minutes for the next bus. When service is less frequent than about every 10 minutes, passengers will have to rely more heavily on the published schedule. In these cases it becomes even more critical that the route timetable is appropriate for operating conditions such as traffic levels at different times of day.
+The characteristics of the area determine the basic components of service. How frequently will the route run? [[Bus stop spacing and location|Where will the bus stops be and what is the distance between them?]] In small communities, suburban and rural, service may operate once an hour; in major metropolitan areas services may run every ten minutes or even more frequently. Certainly there is a wide range in between. In areas where a route operates on frequent headways, say every 10 minutes or less, passengers more often walk out to the stop without knowing the departure schedule; at most they are likely to only be waiting an average of 5 to 9 minutes for the next bus. When service is less frequent than about every 10 minutes, passengers will have to rely more heavily on the published schedule. In these cases it becomes even more critical that the route timetable is appropriate for operating conditions such as traffic levels at different times of day.
 While some agencies may calculate average time between every stop, it is more common for agencies to designate scheduled "'''time points'''" along a route. A time point would be a major stop by which the driver should not pass earlier than what is published. The precise time for stops in between is unpublished. Passengers read the schedule and if they are waiting at a stop in between can reasonably estimate when the bus will come based on the time points on either side of their stop. This can simplify published information and also allow flexibility on stretches of the route with a high variability of speed.
@@ Line 38: / Line 38: @@
 In the bigger picture, agencies should plan and advocate for bus stop construction that allows curb-height boarding and [[Bus rapid transit|travel lanes that are exclusive to buses]]. Some agencies have been able to implement [[Transit signal priority (TSP)|transit signal priority]] to cut down on route travel time.
 On the other hand, routes that include a [[Flexible transportation services|flexible component]] such as request stops or route deviations need to be scheduled allowing enough time for the deviation.
 == Additional Reading ==
 Walker, Jarrett. 2012. Human Transit: How Clearer Thinking About Public Transit Can Enrich Our Communities and Our Lives. Washington, DC: Island Press.

@@ Line 28: / Line 28: @@
 A good rule of thumb is to include an additional 10% of the trip-time for recovery. Layovers can be scheduled where it is convenient for the service. It may seem most straightforward to add a few extra minutes of layover at the end of the route. However, in some cases the travel time between two time points in the middle, for example, may be so variable at different times of day that some layover time between the two would be appropriate. On the other hand, too much scheduled delay in the middle of the route discourages choice riders from using the service as it appears to be inefficient. Operator needs and safety must also be considered; layovers should be in a location that operators are safe and feel comfortable, as well as have access to restrooms.
-Planners may sometimes be tempted to cut recovery time in order to keep a route to an even schedule. For example, imagine adding up travel and delay time for a trip. Before adding in recovery time, the trip comes to 58 minutes. 10% recovery time would be at least 5 minutes, but that would put the route over 60 minutes. If the route is 60 minutes long, it can be operated by two buses on exactly the same schedule every hour. However, this makes the recovery time only 2 minutes. There are trade-offs a planner must consider here. With only 2 minutes of recovery time, the margin of error for dealing with unplanned delay such as a traffic accident is very slim. On the other hand, schedules which vary from hour to hour are confusing for passengers (unless the service is so frequent that the published schedule is nearly irrelevant).
+Planners may sometimes be tempted to cut recovery time in order to keep a route to an even schedule. For example, imagine that a trip including travel time and delay time is 58 minutes long. 10% recovery time would be at least an additional 5 minutes, but that would put the route over 60 minutes. If the route is 60 minutes long, it can be operated by two buses on exactly the same schedule every hour. However, this makes the recovery time only 2 minutes. There are trade-offs a planner must consider. With only 2 minutes of recovery time, the margin of error for dealing with unplanned delay such as a traffic accident is very slim. On the other hand, schedules which vary from hour to hour are confusing for passengers (unless the service is so frequent that the published schedule is nearly irrelevant).
 === Adjusting for delay ===

@@ Line 1: / Line 1: @@
-THIS ARTICLE IS UNDER CONSTRUCTION
+[[Category:Operating effectiveness]]
 == Introduction ==
 Agencies operating fixed-route buses find the need to make adjustments to route scheduling periodically in response to changing circumstances. Bus transit planners should be aware of the basics of fixed-route scheduling. This topic does not cover development of a new fixed-route service, but rather the tuning or re-tuning of an existing or already planned route.
@@ Line 6: / Line 7: @@
 == Basics ==
-The characteristics of the area will often determine the basic components of service. How frequently will the route run? Where will the bus stops be and what is the distance between them? In small communities, suburban and rural, service may operate once an hour; in major metropolitan areas services may run every ten minutes or even more frequently. Certainly there is a wide range in between. In areas where a route operates on frequent headways, say every 10 minutes or less, passengers more often walk out to the stop without knowing the departure schedule; at most they are likely to only be waiting an average of 5 to 9 minutes for the next bus. When service is less frequent than about every 10 minutes, passengers will have to rely more heavily on the published schedule. In these cases it becomes even more critical that the route timetable is appropriate for operating conditions such as traffic levels at different times of day.
+The characteristics of the area determine the basic components of service. How frequently will the route run? Where will the bus stops be and what is the distance between them? In small communities, suburban and rural, service may operate once an hour; in major metropolitan areas services may run every ten minutes or even more frequently. Certainly there is a wide range in between. In areas where a route operates on frequent headways, say every 10 minutes or less, passengers more often walk out to the stop without knowing the departure schedule; at most they are likely to only be waiting an average of 5 to 9 minutes for the next bus. When service is less frequent than about every 10 minutes, passengers will have to rely more heavily on the published schedule. In these cases it becomes even more critical that the route timetable is appropriate for operating conditions such as traffic levels at different times of day.
-While some agencies may calculate average time between every stop, it is more common for agencies to designate scheduled "'''time points'''" along a route. A time point would be a major stop by which the driver knows they cannot pass earlier than what is published. The precise time for stops in between is unpublished. Passengers read the schedule and if they are waiting at a stop in between can reasonably estimate when the bus will come based on the time points on either side of their stop. This can simplify published information and also allow flexibility on stretches of the route with a high variability of speed.
+While some agencies may calculate average time between every stop, it is more common for agencies to designate scheduled "'''time points'''" along a route. A time point would be a major stop by which the driver should not pass earlier than what is published. The precise time for stops in between is unpublished. Passengers read the schedule and if they are waiting at a stop in between can reasonably estimate when the bus will come based on the time points on either side of their stop. This can simplify published information and also allow flexibility on stretches of the route with a high variability of speed.
 To establish a basic schedule, it is best to set time points that are evenly spaced along the duration of the route. A reasonable guideline would be a time point every five to ten minutes apart. Agencies often set time points using major and recognizable landmarks or intersections. Calculate the average free-flow (no traffic delay) time between each time point.
 === Putting it all together ===
-Adding up times between timepoints. Be sure to allow time for boarding, hopefully based on real or projected ridership. Estimate delay if needed, use an agency average, etc.
+Add all of the time between time points in free-flow travel. The schedule should be padded with what is known as "passenger-stop" delay time. This is the average time the bus is delayed from moving to board and alight passengers. This amount of time varies between agencies. It can be affected by many factors, such as:
-Add recovery or layover time. Good rule of thumb is 10% of round-trip time.
+* How fares are handled (cash only systems tend to experience more delay than those with [[Near field communications|electronic fare media]])
-Lay out route in a table with departures based on target frequency.
+* Whether agency policy is to wait for passengers to be seated before departing
-Usually good to test draft product to watch for hiccups.
+Delay must also be calculated for other factors, especially traffic congestion and traffic control such as signals, stop signs, and left turns across traffic. These can vary tremendously even on different lengths of the same road.
-Some revision may be needed. Small amounts of slack time in the middle of a route may be necessary to account for travel variations. If planning flexible transit route, need to incorporate slack time for deviations but not so much that a no-deviation trip isn't sitting around waiting exceptionally long times.
+Finally, "recovery" or layover time should be added to the route. This serves as an insurance policy against abnormal delay on one trip significantly impacting subsequent trips. It is also essential for operations staff; driving a bus for any length of time is wearing on an operator. Bus drivers need time to stretch, use the bathroom, eat, etc. Routes with too little recovery time are stressful for the driver, and in turn the passengers, especially if the route suffers from poor on-time performance.
-=== Agency Variation ===
+=== Recovery time ===
-Agencies working with long headways and multiple routes need to carefully consider connections and probably allow greater slack time.
+A good rule of thumb is to include an additional 10% of the trip-time for recovery. Layovers can be scheduled where it is convenient for the service. It may seem most straightforward to add a few extra minutes of layover at the end of the route. However, in some cases the travel time between two time points in the middle, for example, may be so variable at different times of day that some layover time between the two would be appropriate. On the other hand, too much scheduled delay in the middle of the route discourages choice riders from using the service as it appears to be inefficient. Operator needs and safety must also be considered; layovers should be in a location that operators are safe and feel comfortable, as well as have access to restrooms.
-== Adjusting factors ==
+Planners may sometimes be tempted to cut recovery time in order to keep a route to an even schedule. For example, imagine adding up travel and delay time for a trip. Before adding in recovery time, the trip comes to 58 minutes. 10% recovery time would be at least 5 minutes, but that would put the route over 60 minutes. If the route is 60 minutes long, it can be operated by two buses on exactly the same schedule every hour. However, this makes the recovery time only 2 minutes. There are trade-offs a planner must consider here. With only 2 minutes of recovery time, the margin of error for dealing with unplanned delay such as a traffic accident is very slim. On the other hand, schedules which vary from hour to hour are confusing for passengers (unless the service is so frequent that the published schedule is nearly irrelevant).
-Examine: passenger stop delay (boarding, alighting), average traffic speed, signal delay, geographic factors - are buses slowly crawling through tight areas that could be avoided, etc. Use various strategies to reduce. Avoid making route so tight only the best/senior operators are capable of handling it safely. Keep operations administration involved.
+=== Adjusting for delay ===
-== Runcutting and operations ==
+Because planners cannot control every factor on the road delaying a bus route, they must instead focus on adjusting factors that are within the agency's control. In the example above, a planner faces the choice of making a very tight schedule with little recovery time, or creating an inconsistent schedule that shifts over the course of the day. To alleviate this issue, service could be cut somewhere to bring the route time down. However, there may be other strategies that are also appropriate.
-=== Factors ===
+Scheduling a route should, as much as possible, take a holistic view of policies and operating procedure. Agencies should consider the delay factors noted above and how they can manage them to reduce travel time. For example, encouraging passengers to use fare media and passes that are more efficient for boarding than fumbling for exact change can speed up boarding time. Strong operator training programs can facilitate tighter operating times without sacrificing safety and comfort. Some agencies may be able to accommodate all-door boarding (typically using electronic fare media).
-Federal, state, and agency labor policy. How many hours can employees work, how is work assigned (seniority, etc.)

← Older revision		Revision as of 22:39, 24 November 2013
Line 1:		Line 1:
		+	THIS ARTICLE IS UNDER CONSTRUCTION
	== Introduction ==		== Introduction ==
	Focus on scheduling for an existing or already planned route. Does not address methods for developing a new route from scratch.		Focus on scheduling for an existing or already planned route. Does not address methods for developing a new route from scratch.