Metro Transit Archives

Scheduling 202 The ABCs of Scheduling and Service Planning   Cycle Time       In the previous post about headways, the term Cycle time was mentioned. It is a term so encompassing, it needed its own discussion.    Cycle Time according to MTA, is the amount of time required for a vehicle to make a round trip, including layover/recovery time at each end, used to calculate peak vehicle requirement and/or headway.    Defining what Cycle time is, can also help answer one of the most enduring questions asked by passengers: Why can't my line (insert route) run more buses?   A lot of factors goes into determining cycle time, which can determine headway or frequency. If the line has high ridership, it should run more often. If a line has low ridership, it should run less often.    There is math behind cycle time. It goes like this:   Let's say during the rush hour, it takes a line 45 minutes from one direction and 43 minutes in the other direction,

Scheduling 202 The ABCs of Scheduling and Service Planning A slight change in gears from this point on, as this blog will examine transit industry terms and definitions and what they mean in the scheduling and service planning world. Prior posts discussed headways, span of service, and deadheads. It will continue on the same vein in the hopes of better understanding for riders and advocates.  The first term discussed is called Coverage Service. MTA defines it as a bus route designed to provide service to those who need it, such as households that do not own vehicles, even if demand is low.  These are routes that usually service areas with little to no connecting services or neighborhoods with a moderate density of residents. For BaltimoreLink, there are several lines that fit this description.  The first example is the 34, which operates between Westview Mall and Falls Road Light Rail Station and Greenspring Station on weekdays. In this map, the 34 serves sev