Midday clock face scheduling on commuter rail systems

I somewhat-infrequently take the MBTA’s commuter rail network, usually for work. The trains midday are rather infrequent (with up to two-hour headways) but usable. Still, I almost certainly have to check schedules  before scheduling meetings or figuring out what time to get to the train. But not always. When I have a meeting in Lowell, I always know that I have to be at North Station at 10 past the hour, and that I’ll arrive in Lowell at 5 til the hour, and that the train leaves Lowell at quarter past and arrives in Boston on the hour (and Lowell’s hourly bus routes are timed to this, too). No schedule? No worries.

If I boarded at any other station, I’d know the schedule there, too (Winchester: inbound :42, outbound :39). It’s much easier to remember how many minutes past the hour service depart than try to memorize an entire schedule. This is called clock face scheduling, and it makes it much easier to use transit.
Commuter rail in the US is commute-time oriented, with frequent services during peak hours and less frequent (and in many cases no) service midday. The frequency, as well as the, for lack of a better word, consistency (whether a schedule adheres to clock face scheduling) varies between systems and individual lines within a system. Midday train service is not heavily utilized, and most systems run full-length trains at these times, so there is certainly not a capacity constraint. However, in many cases, confusing-if-not-Byzantine schedules are a barrier to entry to new ridership, and Americans are happy to jump in their cars if given any excuse.

But, if it’s provided at even a minimal level of service, rail transit can provide decent service over long distances, particularly when not focused on park-and-ride type service but walkable, town-center service (so, generally on older suburbs which developed around rail transit). As important, commuter rail often links smaller cities—and their transit systems—in to the larger system, especially in New York, Boston and Chicago. Rail can provide service that buses can not, because they can operate at relatively high speed, stop in a town center, and then resume their speed without getting bogged down in ten minutes of traffic in each town or having to get on and off highways. The technology of using full train sets may not be ideal—shorter multiple-unit trains would be more economical—but the trains are there, so you might as well use them. 

Here’s a chart of commuter rail lines in the US which have midday service. Some lines have a single midday run; these were not included here. I’ve categorized each by its level of service and whether it adheres to a clock face schedule. The levels of service are:
  • Local-Express (multiple stopping patterns during the off-peak)
  • + hourly (better than hourly service)
  • Hourly (service approximately every hour)
  • – hourly (service less frequently than every hour)
And the clock face levels are:
  • Yes (schedules adhere to a clock face schedule; up to 2 minutes of variation allowed)
  • Mostly (most schedules are clock face, but there are up to 5 minute variation or one or two trains with a more significant variation)
  • Partially (part of the schedule is clock face, part is not)
  • No
“Headway” denotes the maximum midday headway, not the average. 30/60 denotes more frequent service on the inner portion of a long (>50 mile) line.
Finally, the “City” column denotes whether the line serves a secondary city at its terminus, or whether it serves mostly suburbs. Examples of “City” lines would be Lowell, Providence, Worcester (MBTA), New Haven and Poughkeepsie (Metro North), Trenton (SEPTA, NJT), Baltimore (MARC), Aurora/Naperville, Waukegan, Joliet (Metra), San Jose (Caltrain). These lines should see more ridership during the midday, and benefit more from hourly, clock face scheduling.
System
Line
Service
Clockface
Headway
City
LIRR
Port Jefferson
(inner)
Local-Express
Yes
30/60
N
Metro
North
Harlem Line
Local-Express
Yes
30/60
N
Metro
North
New Haven Line
Local-Express
Yes
30/60
Y
LIRR
Babylon
Local-Express
Mostly
35
N
LIRR
Port Washington
Local-Express
Mostly
35
N
Metro
North
Hudson Line
Local-Express
Mostly
65
Y
SEPTA
Airport
+ hourly
Yes
30
N
SEPTA
Paoli/Thorndale
+ hourly
Mostly
35
N
NJT
Northeast
Corridor
+ hourly
No
38
Y
Austin
Capital
MetroRail
Hourly
Yes
60
N
Caltrain
Caltrain
Hourly
Yes
60
Y
LIRR
Far Rockaway
Hourly
Yes
60
N
LIRR
Hempstead
Hourly
Yes
60
N
LIRR
Long Beach
Hourly
Yes
60
N
LIRR
Ronkonkoma
Hourly
Yes
60
N
MBTA
Lowell
Hourly
Yes
60
Y
METRA
METRA electric
Hourly
Yes
60
N
METRA
Milwaukee
District North
Hourly
Yes
62
N
METRA
Milwaukee
District West
Hourly
Yes
60
Y
METRA
Rock Island
Hourly
Yes
60
Y
METRA
UP North
Hourly
Yes
60
Y
Metro
North
New Canaan Line
Hourly
Yes
60
N
NJT
NJ Coast Line
(inner)
Hourly
Yes
60
N
NJT
Raritan Valley
Hourly
Yes
60
N
SEPTA
Lanesdale/Doylestown
Hourly
Yes
60
N
SEPTA
Media/Elwyn
Hourly
Yes
60
N
SEPTA
Warminster
Hourly
Yes
60
N
SEPTA
West Trenton
Hourly
Yes
60
N
UTA
FrontRunner
Hourly
Yes
60
Y
Tri-Rail
Tri-Rail
Hourly
Yes
60
Y
MARC
Penn
Hourly
Mostly
66
Y
MBTA
Beverly
Hourly
Mostly
79
Y
NJT
Main Line
Hourly
Mostly
70
N
SEPTA
Manayunk/Norristown
Hourly
Mostly
60
N
SEPTA
Wilmington/Newark
Hourly
Mostly
65
Y
NJT
Morris and Essex
Hourly
Partially
60
N
SEPTA
Chestnut Hill
West
Hourly
Partially
60
N
SEPTA
Fox Chase
Hourly
Partially
74
N
SEPTA
Trenton
Hourly
Partially
65
Y
NJT
Montclair
Hourly
No
60
N
SEPTA
Chestnut Hill
East
Hourly
No
72
N
DFW
Trinity Railway
Express
– hourly
Yes
90
Y
LIRR
Montauk
– hourly
Yes
120
N
LIRR
Oyster Bay
– hourly
Yes
120
N
LIRR
Port Jefferson
(outer)
– hourly
Yes
97
N
LIRR
West Hempstead
– hourly
Yes
120
N
MBTA
Fairmount
– hourly
Yes
120
N
MBTA
Newburyport
– hourly
Yes
120
N
MBTA
Rockport
– hourly
Yes
120
Y
METRA
BNSF
– hourly
Yes
120
Y
METRA
North Central
Service
– hourly
Yes
120
N
METRA
Southwest
Service
– hourly
Yes
144
N
METRA
UP Northwest
– hourly
Yes
120
N
METRA
UP West
– hourly
Yes
120
Y
Metro
North
Waterbury
– hourly
Yes
180
Y
Metrolink
San Bernardino
– hourly
Yes
120
Y
NJT
Bergen
County
– hourly
Mostly
96
N
NICTD
South Shore Line
– hourly
Partially
120
Y
MBTA
Fitchburg
– hourly
No
120
Y
MBTA
Franklin
– hourly
No
120
N
MBTA
Greenbush
– hourly
No
141
N
MBTA
Haverhill
– hourly
No
160
Y
MBTA
Kingston
– hourly
No
142
N
MBTA
Middleboro/Lakeville
– hourly
No
141
N
MBTA
Needham
– hourly
No
130
N
MBTA
Providence
– hourly
No
150
Y
MBTA
Worcester
– hourly
No
140
Y
Metro
North
Danbury
– hourly
No
180
Y
Metrolink
Antelope Valley
– hourly
No
180
Y
NJT
Atlantic City
– hourly
No
137
Y
NJT
NJ Coast Line
(outer)
– hourly
No
120
N
NJT
Pasack Valley
– hourly
No
180
N

 Lots of interesting things going on here:

  • Nearly every line with a maximum two-hour-or-better headways has 30-, 60- or 120-minute clock face scheduling. The only exception is the Trinity Railway Express between Dallas and Forth Worth, which runs every 90 minutes. 
  • With one exception, lines with better-than-hourly service adhere to clock face scheduling. The exception is the NJ Transit Northeast Corridor Line, which may be constrained by arrival slots in the Hudson River tubes (it does run at least every 38 minutes, however).
  • Amongst the major multi-line commuter rail networks (MBTA, SEPTA, METRA, NJT, MN and LIRR) only SEPTA has full hourly service on all lines, most of them operating on a clock-face or partially clock-face schedule (headways get shorter on the shoulders of rush hour, but while 45-minute headways provide more service, it might just confuse passengers and not actually encourage ridership). 
  • The New York services have hourly-or-better service on their main lines, but some far-out branches see less service. Most other agencies have some lines with hourly service, and some with less.
  • Most hourly services are operated on-or-near clock face, and even two outliers could, with minor changes, be made hourly.
  • All METRA lines in Chicago have clock face scheduling, and many the ones which are not hourly have only one two-hour service gap.
  • The MBTA, by these metrics, probably has the worst service of any major system. The Lowell Line is the only line with hourly, clock face service; although the Beverly-Boston portion of the combined Newburyport/Rockport lines has a similar level. While several MBTA lines are commuter-oriented, others serve some of the largest cities in the region: Worcester, Fitchburg, Lawrence, Providence and Brockton. 
So, yeah, the MBTA. Alon Levy wrote at some length about its poor service levels, and I concur. What’s particularly bothersome is that the MBTA has an example of a line which lines up against some of the better commuter rail lines in midday service in Lowell. And while Lowell trains aren’t packing five cars full, they regularly disgorge 100 riders each hour on to the platforms at North Station. I’m not necessarily saying that the T should try to improve the service on every line (without better funding, that’s probably a non-starter) but it certainly could use the Lowell line as a bit of a model.
The MBTA is also hamstrung by some single-track bottlenecks which hamper more frequent service, particularly on the Old Colony Lines and those to Franklin, Needham, Fitchburg and Haverhill (portions of the latter two are being double-tracked). And there are dispatching and scheduling issues to Worcester and Providence, respectively, and there is hourly, clock face service to Beverly before the split to Newburyport and Rockport.

Here are the minutes between trains for midday service between Worcester and Boston (the two largest cities in New England):

Inbound: 60, 140, 90, 110, 75, 90, 77. Outbound: 135, 85, 112, 53, 90, 80

And for Boston and Providence (cities 1 and 3):

 Inbound: 85, 90, 146, 149, 62, 48. Outbound: 60, 155, 85, 145, 105, 30

At 180,000 apiece, Providence and Worcester are two of the largest non-hub cities served by commuter rail (only Aurora and some cities in the LA agglomeration are bigger; I’m excluding major cities at the ends of smaller systems like Baltimore, San Jose, Fort Worth and Tacoma). And, yet, their service is sub-par.

Other MBTA lines are similarly random. I can’t imagine that the train times are a response to any specific peaks in demand at certain times, nor do they appear to be a response to other traffic on the railroad. They just don’t make any sense.

Still, this can be remedied. Fitchburg and Haverhill could have hourly service with ongoing improvements to their trackage (hopefully this will be a goal for the Fitchburg Line once it is (re)duplicated in 2014). The state is paying an arm and a leg to acquire the line to Worcester, and they ought to try to improve frequencies to the state’s second-largest city (outside of rush hour, private buses provide relatively-frequent service to Worcester, but don’t serve any towns in between). And while the Providence line does have intercity trains running at double the speed of the commuter rail, there are only two per hour, and with passing tracks stray commuter trains could be scheduled in between. Or—even better—the T could acquire electric motors or multiple units and run the Providence line under the wire, with faster running times and cheaper operation.
One hour frequencies certainly aren’t ideal—consider that in Melbourne, Australia (population 4m) most suburban lines run every 10, 15 or 20 minutes with a stated goal of clock face scheduling (and attract 700k riders per day, more than double Chicago and nearly as many as in New York City!)—but they provide a base level of transit. Two hour headways are quite minimal, and especially sub-par when they don’t even operate on any reliable frequency. More frequent and predictable midday service also help ridership during peak periods by giving commuters more of a guarantee that, should they have to leave at a non-peak time, there will be predictable service.

Combining hourly service and clock face schedules is the standard for American commuter rail systems, but many lines fall far short It should be the goal of commuter rail operators to offer at least this level of service whenever possible. The facilities are there and the vehicles are there. The trains won’t be full, but making schedules and service easier to understand will certainly increase ridership.

New York ridership-vs-distance chart

On his blog Pedestrian Observations, Alon Levy recently compared ridership on the different commuter lines in New York. It’s an interesting post, with a chart of the different lines which was begging to be thrown in to Excel and graphed. Which I’ve done:

Notes: line width is proportional to ridership. Lines are grouped by color. Green = NJT. Yellow = NJT operating in to New York. Blue = Metro North. Red = LIRR. The chart will definitely make more sense when referenced to the original post

Levy points out that lines are almost operating as separate systems: some as closely-spaced commuter rail (the group of lines more to the left) and some as almost intercity rail (the ones more to the right). In the first group, half of the ridership rides from stations between 30 and 40 km from the city center. In the second, half the ridership takes rides from at least 50 km out. What’s interesting to note is that each group has lines from each system; it’s not like the LIRR has denser lines while the Metro North has far-flung stations.

It does seem that lines which were once or are now major intercity routes are more likely to have longer-distance commuters and look more like intercity trains. The four lines in this group constitute the three main lines which operate frequent intercity service from New York (the LIRR doesn’t have any cities to operate to, of course) to Boston (New Haven), Albany (Hudson) and Philly/DC (NEC). Of course, even though the Metro North in Connecticut serves trains to Boston and Springfield, it is still painfully slow with maximum speeds of only 70 mph, half the speed of the NJT NEC towards Trenton.

Anyway, I think the chart looks pretty cool. (Next up: giving the same treatment to Boston’s trains, and whining about the MBTA’s commuter services a bit.)

Apparently, there are folks whose schedules don’t fit Northstar

Last week, I wrote about how late night commuter service helps rush hour trips. The main contention is that for anyone who doesn’t have a very stable 8-4 or 9-5 job, the Northstar Line is not a viable option, and how this is actually the case for many other commuter rail systems in the country.

One of these prospective riders wrote about it in the Star Tribune. We seem to agree. Her worry is, however, that if ridership is muted, it will never be able to expand north or to change its schedule. The politics and logistics of adding trips are very tricky, but it seems that having a later evening trip or two (8 p.m. and 11 p.m.) would provide a safety net allowing many more commuters on the late trains. A sweeper bus or two would work as a preliminary measure (there is currently one bus which leaves at 7:00 and only serves some stations). If not, well, it means more cars on the road, and fewer riders on the rails.

The Northstar Line, and how late night service helps rush hour ridership

A shorter version of this was originally posted as a comment on The Transport Politic.

One problem with Northstar, and most new systems, is that by running only at rush hour they are aimed strictly at the 8-4 / 9-5 crowd. Anyone who ever has to stay later at their job can’t take the train, or wind up a very costly ($80-120) mile cab ride from home. In order to plug a deficit, the MBTA proposed cutting service after 7 p.m. in Boston and there was a ton of outcry. People basically said “having late trains, even ones running every two hours, allows me to take the train every day. If you cut those trains, I have to drive.” So there’s a whole market which is ignored by limiting transit to commute hours only.

Of course, Boston and other legacy commuter systems (New York, Philly, some of DC, Chicago and San Francisco) have existing trackage rights or own their track outright, so don’t have to worry about freight rail’s demands. (The Northstar Line shares track with a major BNSF transcon route which sees about 50 freight trains a day.) Of the non-legacy systems, only Miami-West Palm Beach, Utah, Dallas-Fort Worth, and Connecticut’s Shore Line East provide any sort of evening service.

This evening service, while not well patronized, helps more people take transit. While there are no definitive numbers, let’s make a some assumptions/educated guesses for cities with full-schedule commuter rail. Eighty percent of transit ridership is during traditional rush hours: in by 9, out between 3:30 and 6:30. Ten percent is on midday services, and ten percent on evening services. It seems that you could cut these services, and lose only 20% of your ridership while eliminating 40% of the trains. However, it’s not this simple.

One of the reasons people don’t ride transit is because of their families. A frequent issue brought up by many potential riders is “what happens if my kid gets sick and I need to pick them up at at school?” (Nevermind that this is an infrequent enough occurrence that the money saved on gas and parking would more than cover a cab fare twice a year.) But, it’s a valid concern, especially for systems where suburban transit quits from 9 to 3. Even with hourly or every-two-hour service, it provides some safety net. If your kid gets sick you’ll be able to get there at some point in before the school day is out.

The other reason people eschew transit in underserved cities is the “what happens if I have to stay late?” question. As mentioned, in the the legacy commuter rail cities, if you have to stay late, you’ll get home. You might not be able to walk down to the station and get on a train which runs every twenty minutes like at rush hour, but if you have to stay until 7:00 you’ll at least get home in time to say the proverbial good night to the kids. The late trains provide a sort of safety net—for people who have to occasionally and unexpectedly stay late, it allows to them to come to work without a car and know that they’ll get home. For a lot of employees, this makes the difference between taking the train to work and driving.

So let’s go back to the 80-20 rush hour–non-rush split. For people who might sometimes have to work late, probably 95% of their trips are during rush hour—ten or twelve times a year they have to stay late at work. So, out of a hypothetical 100 riders, 95 of are crowding trains at rush hour, and 5 are taking trains later on. However, if you cut the late service, you not only lose the five people on these relatively uncrowded services, but the 95 on the earlier trains, too. So you can’t cut evening trains and expect to retain your full peak ridership.

There is another element to running late-night service: it allows people who work downtown to stay downtown. Many American cities has 9-5 downtowns: they empty out at night and seem desolate. This is mainly because there is not the critical mass of people to populate the streets and go to restaurants and shows. In a city like Minneapolis, which has a rather high transit mode-split but little late night service, people who want to stay out late, if they are from the suburbs, are forced to drive. Minneapolis has a good number of services downtown, from a full-scale Macys (originally Daytons) to a full-scale Target, as well as baseball and basketball arenas, as well as the Guthrie Theater and Orchestra Hall. Providing later service would allow people to take transit in in the morning and stay downtown to avail themselves of the amenities which are not available in the suburbs.

One means to this end might be shorter trains or, in the very long run, electrification of commuter runs. The Trinity Railway Express between Dallas and Fort Worth uses old Budd RDCs for some off-peak trips, which are more efficient for transporting smaller numbers of passengers. With locomotive-hauled services (or motor-hauled electric services) there is little incentive to shorten trains, as uncoupling a few cars decreases efficiency very little. (This is why off-peak trains in Boston, for example, often operate full-length trains with only two or three cars open.) With DMUs or EMUs, there is a significant energy-use savings with shorter trains.

In the long run, the plan is to run service from Minneapolis to Saint Cloud. While criticisms of the first phase of this project may be apt, it will make much more sense if there are trains running to the proper end of the line there. It would be more of a cross between intercity rail and a commuter service, and would probably necessitate midday and evening trips (these could be run every three hours in each direction with only one train set and crew). Saint Cloud is home to 60,000 people, has a local bus system, and, possibly most importantly, has a 20,000 student state university, with most of the students undergrads, and many from the Twin Cities. The campus is about 1/2 mile from the potential station site, adjacent to downtown, and bus lines currently connect the two.

So while the first phase is probably not cost effective, the overall project—with passenger rail service between two cities’ downtowns at highway-competitive speeds—may be quite a bit more useful to quite a few more riders.