I’d like to share an example of how to implement coordinated planning for public transportation, using an example of something I’ve been working on with TransitMatters in and around Boston. Right now we’re writing schedules and proposing concrete investments including electrification on each commuter line into Boston; the process is different for each line, but the first line we’ve launched the document for, the Worcester Line, is illustrative in itself. You can find the file here and the broader proposal here; the first link bundles two separate documents, of which the Worcester proposal is the second. I’ve harped a lot on using the Swiss model for better regional rail, and here is one example of how to get a city whose rail technology is stuck in the 1930s to have what Zurich has.
Slogans and principles
I’ve harped on a few Swiss and Swiss-adjacent slogans before:
Organization before electronics before concrete. Investments in more tracks, tunnels, and so on should come last as they are expensive, and beforehand agencies should improve signaling and electrify as it is much cheaper. Moreover, fixing organizational issues, for example writing good schedules and integrating planning between different agencies, should come before anything else, as it requires planners to do more work but is otherwise cost-free.
Takt and symmetry. If a train leaves your station going eastbound at 7:14 am and the schedule is every half hour, then a train leaves your station going eastbound at :14 and :44 all day, every day; this is also called a clockface schedule. If there’s additional service during rush hour, it should fit into the takt, e.g. more trains coming at :29 and :59 for 2 morning hours and 2 afternoon hours. By the same token, trains going westbound should serve your station at :16 and :46, since 60-14 = 46. This means the overtakes, meets on a single-track line, etc. all occur at consistent places.
The magic triangle of infrastructure, rolling stock, and timetable. The plan must account for all three sides of the triangle simultaneously, in order to optimize investment. For example, if additional tracks are required for timed overtakes, then the agency should know what trains it’s going to run and how frequent it’s going to run them in order to know where the overtakes are needed. With a takt, the overtakes will be at consistent location where the region can target investment.
Run trains as fast as necessary. Increases in speed should be designed around making timed connections and limiting train downtime. One refinement on a suburban line is that the stop spacing should depend on the schedule: if the one-way trip time is 52 minutes then a short turnaround makes an hour and additional stops are difficult to fit in, whereas if it is 46 minutes then the turnaround is longer and there is room for more stops.
The knot system: knots (or nodes, same word in German) occur at major stations at regular intervals – at a minimum an interval equal to half the systemwide takt frequency. If trains run half-hourly, then a station with service at :00 and :30 or with service at :15 and :45 will be served in both directions at the same time, so it’s a good place for bus and train connections. This works in both planning directions: if the schedule happens to place a knot at a station then buses should go there, and conversely if a city is a major node then the schedule should be written to a place a knot there.
What we propose for Worcester
The proposal as written calls for two service patterns, one express and one local. At rush hour, both run every 15 minutes. Off-peak, the express pattern drops to 30-minute frequency, but the local pattern stays at 15 minutes, as it serves Boston neighborhoods and Newton, close enough in that high off-peak ridership can be expected. With electrification and high platforms, the following schedule is feasible:
|Lansdowne (Fenway Park)||4||0:09||0:16|
Express trains overtake locals at Wellesley Farms; there are plans for triple-tracking Wellesley (and farther west, but it’s not necessary). At Framingham, locals take 12 minutes to turn, which means there needs to be a non-revenue move around 0:41 westbound to a yard just west of Framingham to avoid getting in the way of express trains at :43 and :47 before getting back to Framingham at 0:49 to collect passengers; triple-tracking Framingham is also an option but is more expensive.
How it fits the principles
Let’s go over the Swiss principles one by one and see how this all fits.
Organization before electronics before concrete. As presented the plan includes elements of all three: organization is better-timed schedules and the potential use of the yard as a pocket track to avoid triple-tracking Framingham, electronics is electrification, concrete is the triple track. The electronics-concrete order is important – without the triple track but with electrification, EMUs can still do Boston-Worcester in around 57 minutes with the above stops, or 55 without infill at West Station and Newton Corner, either of which is faster than the fastest express trains today. The ultimate in concrete in the Boston area is the North-South Rail Link, which should come only after full electrification and related modernization steps, such as high platforms.
Takt and symmetry. The timetable is on a takt and symmetric, to ensure the overtake takes place at a manageable spot in Wellesley. It would be easier to change the offset slightly and overtake around West Newton, but there the tracks are in a constrained location where triple-tracking is prohibitively expensive. Note also that with the above timetable, the westbound overtake is at :11, :26, :41, :56, and the eastbound overtake is at :04, :19, :34, :49, which means it requires triple-tracking but not four-tracking.
The magic triangle of infrastructure, rolling stock, and timetable. The timetable is calibrated around the performance specs of the latest EMUs, like Coradias, Mireos, Talent 3s, and FLIRTs. The high acceleration capabilities of these trains let a local train leave Boston just 7 minutes ahead of the next express train, and still keep up through double-track narrows in Newton until Wellesley Farms, the sixth station skipped.
Run trains as fast as necessary. Without onward connections beyond Worcester, transfers between trains are not really a factor. Thus, what matters is tight turnaround times to keep trains moving and earning revenue rather than loitering at the terminal. The local train spends 35 out of 45 minutes running, and the express train 45 out of 60.
The knot system. Knots occur wherever trains stop around :00, :15, :30, and :45. The word around includes a few minutes of wiggle time, especially at a terminal, where transfers are unidirectional. Thus Worcester is a knot at :00, with a few minutes of rail-to-bus and bus-to-rail transfer. Framingham is a knot at :30, as long as the buses get there before :28 to transfer to eastbound express trains and depart after :32 to accommodate transfers from westbound express trains. On local trains, Newton Corner may be a knot, with a connecting bus shuttle to Watertown.
Framingham and Worcester already exist as bus nodes, and in both cities, the main city bus hub is already the train station. The next step is to integrate the schedules. The rule is generally that bus timetabling should follow rail timetabling, because trains require more infrastructure whereas buses can be moved more easily; there are exceptions, but not many.
The principles for bus design on the Zurich model aren’t as catchy as for rail design, but they are still useful and generally worth learning:
One ticket for all. Fares must be totally integrated. If a train makes two stops in the same zone (for example, Framingham and West Natick), it should charge the same as a bus. A train ticket should be valid within the entire zone traversed, which includes bus transfers. The same fare media should be used on all modes – and they should be paper tickets with no surveillance, not Boston’s ongoing smartcard disaster (“AFC 2.0”). Fare integration requires a mechanism for sharing revenue across agencies, but this is organization, and is doable under the aegis of the Massachusetts state government, with revenue allocated to agencies based on periodic counts to ascertain ridership (Berlin’s are every 3 years).
Timed transfers. Suburban buses should come every half hour, on a takt of course, with timed transfers to the trains at the relevant knot. Worcester’s bus agency, WRTA, does not do this at all – bus #1 runs on an hourly takt, but other routes may run every 50 minutes or every 75. Framingham’s, MWRTA, has 65-minute headways, and a route that runs to a Green Line station rather than much closer to a commuter rail station.
High vehicle utilization. If the bus takes around 25 minutes to reach its outlying destination, then two vehicles serve one route, and if it takes 40 minutes, then three vehicles do. Buses should run as fast as necessary as well, deleting meanders, installing queue jump lanes, and shortening the route in order to squeeze inside a timetable with short turnaround times.
Connections between different train stations. A bus can connect two different train stations, either on the same line or on different lines. It should be timed at both ends, though it if runs parallel to the train, then it’s fine to time only right-way connections (e.g. eastbound bus to eastbound train, westbound bus to westbound train), which do not require knots.