Subway Expansion to Kingsborough Community College

One of the perennial wishlist items for New York subway expansion is Nostrand Avenue. The 2 and 5 trains run under the avenue between Eastern Parkway and Brooklyn College, a distance of 4 km; from the start, the line was intended to be extended farther south, and in both the 1950s and 1970, there were plans for such extension as well as one shortly to the east under Utica, to be built right after Second Avenue Subway. The case for Nostrand and Utica remains strong – these two streets host Brooklyn’s two busiest buses (the B44 and B46 respectively), and another top route, the B41 on Flatbush, is closely parallel. The purpose of this post is to ask what the southern end of Nostrand should be, and whether a longer extension going to Kingsborough Community College is a good idea.

Nostrand: current plans

All plans I am aware of for extending the subway under Nostrand have it following the street to Sheepshead Bay. For example, my proposal from 2019 would terminate it right at the water, at Emmons Avenue, where the B44’s southern end is. This reflects official proposals over the last few generations: a Nostrand subway is to run just under Nostrand.

Kingsborough Community College

Right across geographic Sheepshead Bay from the neighborhood named after the bay, the eastern end of geographic Coney Island comprises the neighborhood of Manhattan Beach. It is not a dense area, and for the use of residents, there are buses to the Brighton Beach subway station. However, at the easternmost end of Manhattan Beach, Kingsborough Community College (KBCC) is a huge destination.

How huge? The bus serving it, the B1, is one of the busiest in Brooklyn, with some rush hour runs just operating back and forth as short-hop shuttles between Brighton Beach and KBCC, a distance of 2 km. Frequency at rush hour reached a bus every 3-4 minutes before corona.

This is not easily legible to commuter-oriented planning tools like OnTheMap. That area has only 1,000 jobs; KBCC itself doesn’t generate many jobs, nor does it anchor other industries around it that aim to employ graduates. Those planning tools can capture other universities if they’re more residential and higher-end – those have a higher ratio of faculty to students, have ample research labs, and anchor employers who look to locate near residential students. In contrast, a commuter college is largely invisible to them. In reality, there are 18,000 students, all of whom commute from elsewhere.

How much ridership does this generate?

KBCC has 18,000 students, and the overall area has 1,000 workers. If the modal split were 100%, this should generate 38,000 trips per weekday; commuter colleges don’t generate as many non-commute trips as do residential colleges. In reality, the modal split is not 100%, but it should be high given the low car ownership rates in the city, especially low for college students.

The bigger question is what proportion of the travel market would ride a Nostrand subway in preference to a rail-bus connection at Brighton Beach. This in turn depends on the state of the rest of the system. If the Interborough Express or some variant of it is already built, then from all points on or north of the IBX route, an all-rail route is superior to a rail-bus connection. If it isn’t, then it’s dicier, and from much of Southern Brooklyn from the Brighton Line to the west, the B1 is likely faster.

IBX should be built ahead of such a connection based on current plans, so the assumption should be the more optimistic one – and, of course, if there is long-term planning for subway extensions, then this should figure as an argument in favor of IBX. KBCC is hardly the only place that, despite being far from IBX, IBX can help riders access. In that scenario, 30,000 trips a day are not unrealistic, and 20,000 should be conservative.

How much should this cost?

I do not know. In an unusual inversion, I’m more confident of the benefits than the costs. The travel market is fairly circumscribed. In contrast, the costs have a question mark, because of the premium coming from underwater construction.

With no premium at all, New York should be able to reduce its construction costs for subways to $200 million per km on average, and less on easy sections, that is, on outer extensions of the system in the Outer Boroughs. But Nostrand has a high water table, and the underwater segment across Sheepshead Bay is not easy; figure $250-300 million per km, with a wide error margin.

This is not an onerous cost. It’s about 600-700 meters longer than the usual plan for Nostrand to Emmons, and presumably the whole route would be built at once with a tunnel boring machine, so the fixed costs are already paid. So $200 million is probably a reasonable cost.

Eno’s Project Delivery Webinar

Eno has a new report out about mass transit project delivery, which I encourage everyone to read. It compares the American situation with 10 other countries: Canada, Mexico, Chile, Norway, Germany, Italy, South Africa, Japan, South Korea, and Australia. Project head Paul Lewis just gave a webinar about this, alongside Phil Plotch. Eno looks at high-level governance issues, trying to figure out if there’s some correlation with factors like federalism, the electoral system, and the legal system; there aren’t any. Instead of those, they try teasing out project delivery questions like the role of consultants, the contracting structure, and the concept of learning from other people.

This is an insightful report, especially on the matter of contract sizing, which they’ve learned from Chile. But it has a few other gems worth noting, regarding in-house planning capacity and, at meta level, learning from other people.

How Eno differs from us

The Transit Costs Project is a deep dive into five case studies: Boston, New York, Stockholm (and to a lesser extent other Nordic examples), Istanbul (and to a lesser extent other Turkish examples), and the cities of Italy. This does not mean we know everything there is to know about these cases; for example, I can’t speak to the issues of environmental review in the Nordic countries, since they never came up in interviews or in correspondence with people discussing the issue of the cost escalation of Nya Tunnelbanan. But it does mean knowing a lot about the particular history of particular projects.

Eno instead studies more cases in less detail. This leads to insights about places that we’ve overlooked – see below about Chile and South Korea. But it also leads to some misinterpretations of the data.

The most significant is the situation in Germany. Eno notes that Germany has very high subway construction costs but fairly low light rail costs. The explanation for the latter is that German light rail is at-grade trams, the easiest form of what counts as light rail in their database to build. American light rail construction costs are much higher partly because American costs are generally very high but also partly because US light rail tends to be more metro-like, for example the Green Line Extension in Boston.

However, in the video they were asked about why German subway costs were high and couldn’t answer. This is something that I can answer: it’s an artifact of which subway projects Germany builds. Germany tunnels so little, due to a combination of austerity (money here goes to gas subsidies, not metro investments) and urbanist preference for trams over metros, that the tunnels that are built are disproportionately the most difficult ones, where the capacity issues are the worst. The subways under discussion mostly include the U5 extension in Berlin, U4 in Hamburg, the Kombilösung in Karlsruhe, and the slow expansion of the tunneled part of the Cologne Stadtbahn. These are all city center subways, and even some of the outer extensions, like the ongoing extension of U3 in Nuremberg, are relatively close-in. The cost estimates for proposed outer extensions like U7 at both ends in Berlin or the perennially delayed U8 to Märkisches Viertel are lower, and not too different per kilometer from French levels.

This sounds like a criticism, because it mostly is. But as we’ll see below, even if they missed the ongoing changes in Nordic project delivery, what they’ve found from elsewhere points to the exact same conclusions regarding the problems of what our Sweden report calls the globalized system, and it’s interesting to see it from another perspective; it deepens our understanding of what good cost-effective practices for infrastructure are.

The issue of contract sizing in the Transit Costs Project

Part of what we call the globalized system is a preference for fewer, larger contracts over more, smaller ones. Trafikverket’s procurement strategy backs this as a way of attracting international bidders, and thus the Västlänken in Gothenburg, budgeted at 20,000 kronor in 2009 prices or around $2.8 billion in 2022 prices, comprises just six contracts. A planner in Manila, which extensively uses international contractors from all over Asia to build its metro system (which has reasonable elevated and extremely high underground costs), likewise told us that the preference for larger contracts is good, and suggested that Singapore may have high costs because it uses smaller contracts.

While our work on Sweden suggests that the globalized system is not good, the worst of it appeared to us to be about risk allocation. The aspects of the globalized system that center private-sector innovation and offload the risk to the contractor are where we see defensive design and high costs, while the state reacts by making up new regulations that raise costs and achieve little. But nothing that we saw suggested contract sizing was a problem.

And in comes Eno and brings up why smaller contracts are preferable. In Chile, where Eno appears to have done the most fieldwork, metro projects are chopped into many small contracts, and no contractor is allowed to get two adjacent segments. The economic logic for this is the opposite of Sweden’s: Santiago wishes to make its procurement open to smaller domestic firms, which are not capable of handling contracts as large as those of Västlänken.

And with this system, Santiago has lower costs than any Nordic capital. Project 63, building Metro Lines 3 and 6 at the same time, cost in 2022 PPP dollars $170 million/km; Nya Tunnelbanan is $230 million/km if costs don’t run over further, and the other Nordic subways are somewhat more expensive.

Other issues of state capacity

Eno doesn’t use the broader political term state capacity, but constantly alludes to it. The report stresses that project delivery must maintain large in-house planning capacity. Even if consultants are used, there must be in-house capacity to supervise them and make reasonable requests; clients that lack the ability to do anything themselves end up mismanaging consultants and making ridiculous demands, which point comes out repeatedly and spontaneously for our sources as well as those of Eno. While Trafikverket aims to privatize the state on the British model, it tries to retain some in-house capacity, for example picking some rail segments to maintain in-house to benchmark private contractors against; at least so far, construction costs in Stockholm are around two-fifths those of the Battersea extension in London, and one tenth those of Second Avenue Subway Phase 1.

With their broader outlook, Eno constantly stresses the need to devolve planning decisions to expert civil servants; Santiago Metro is run by a career engineer, in line with the norms in the Spanish- and Portuguese-language world that engineering is a difficult and prestigious career. American- and Canadian-style politicization of planning turns infrastructure into a black hole of money – once the purpose of a project is spending money, it’s easy to waste any budget.

Finally, Eno stresses the need to learn from others. The example it gives is from Korea, which learned the Japanese way of building subways, and has perfected it; this is something that I’ve noticed for years in my long-delayed series on how various countries build, but just at the level of a diachronic metro map it’s possible to see how Tokyo influenced Seoul. They don’t say so, but Ecuador, another low-cost Latin American country, used Madrid Metro as consultant for the Quito Metro.

Quick Note: What’s a Megaproject?

I gave my webinar talk about the Stockholm case and uploaded the video here. I don’t want to repeat either the case or my presentation thereof, but rather just point to one thing I said during the Q&A, about what counts as a megaproject. At the time I thought it was just an extemporaneous answer, but Sandy Johnston highlit it in his livetweeting, and I think it has some deeper meaning.

The issue at hand is that the definition of what a megaproject is is relative to local capabilities and practices. Building 5 km of subway tunnel is a megaproject if you’re an American city or a small European capital, but not if you’re a large European or Asian city. What I mean by this definition is that the usual properties of megaprojects are relative to local capabilities in the following ways:

  • Megaprojects are hotly debated politically at the highest level – Crossrail and High Speed 2 were in the manifestos of both Labour and the Conservatives, and Grand Paris Express evolved with direct government involvement. In smaller cities, projects of similar levels of political importance are as one might expect smaller, like Citybanan (which is 6 km) and Nya Tunnelbanan (which is 19 km); in turn in Paris, extensions of the Métro totaling 19 km happen gradually without such political involvement.
  • Megaprojects are institutionally new. Grand Paris Express not only was decided by the government, as an expansion of Métro service almost as long as the preexisting system, but also stretched project management capacity to the point of collapse, setting up the cost overrun; thus, the current project is being built using institutionally novel techniques including a single-purpose delivery vehicle with some design-build aspect.
  • Megaprojects have a large, noticeable impact on the city or region if built; this can be an economic impact as with transport projects, but also a cultural impact, as with the Sydney Opera House, whose factor of 15 cost overrun is a case study in Bent Flyvbjerg’s oeuvre.

In a way, this means megaprojects are defined by cost. A 3 km expansion of the T-bana is not a megaproject, let alone a 3 km expansion of the Istanbul Metro, but a 3 km expansion of the New York City Subway is, because it’s a full order of magnitude costlier. A lower-cost city or country is one that builds more, simply because more projects are cost-effective, and thus it has more projects that are below the threshold of what counts as a megaproject and instead are routine extensions.

The Transit Costs Project hasn’t consciously made any comparison of megaprojects with technically similar non-megaproject transit expansion. The Istanbul case comes closest with its focus on Marmaray and smaller metro projects, but Istanbul Metro expansion writ large should be viewed as a megaproject (it’s certainly planned and politicized as such), and Marmaray is genuinely more technically difficult than just about any other urban rail project. A vulgar quantitative comparison across our database is probably infeasible – there are too few examples by definition, and, moreover, because megaprojects are in practice defined by cost, they’re likelier to be more expensive, even if their specific features do not raise costs.

That said, I do believe that megaprojects are likely to be costlier than equivalent non-megaproject extensions. Stockholm is not a good example for this because it isn’t doing incremental urban rail expansion, only megaprojects. But Paris is a good example, and the per-km cost rose dramatically in the wake of Grand Paris Express. In Barcelona, L9 is a very expensive megaproject; part of its mega- status comes from its worse-than-factor-of-3 cost overrun, but it’s also a large extension of the metro and its construction technique, a large-diameter tunnel boring machine, was new.

Berlin is more complex. We’ll need to wait to see which of the U-Bahn extensions under discussion are built, but those are liminally mega-, sharing some features of megaprojects (namely, political debate, consisting of modal warfare between U-Bahn and streetcar expansion) but not others (they’re not institutionally new and nobody claims they’re transformational for the city). That said, I tilt toward not viewing them as a megaproject, because the debate over them is more general modal warfare, in the same way I don’t think a project subject to debate over spending versus austerity or road versus public transport investment is a megaproject. The key political attribute is not that there’s any political debate, but rather that the political debate introduces politicization of technical decisions over alignment and construction methods; the modal warfare in urban Germany between streetcars and rapid transit is a proxy for much broader fight between consumption- and quality of life-oriented urbanism on the one hand (favoring streetcars and bike lanes) and production- and job access-oriented urbanism on the other (favoring rapid transit and also motorway construction).

IBX Cannot be a Tram

Clay Guse of the NY Daily News reports that in New York, the plans for the Interborough Express connector between Brooklyn and Queens are starting to lean in the direction of light rail. To be very clear, light rail in this context just means running light rail vehicles on infrastructure that is entirely grade-separated, either in the Bay Ridge Branch right-of-way (which has a handful of freight trains and is mostly wide enough for light rail and freight on separate tracks) or on viaducts (over the sections of the branch that are too narrow). I do not think there is any plan to downgrade IBX to a tramway. However, on Twitter I was asked about this anyway: why not make it a tramway, for more on-street flexibility?

What is a tram? Or a streetcar? Or light rail?

A tram or streetcar is a rail vehicle that runs predominantly on-street. The quality of the right-of-way may vary, from full mixed traffic as was traditional, to dedicated lanes that may be shared with buses and emergency traffic, to a grassy median that is no longer usable by road vehicles. But the distinguishing feature of the streetcar is that it runs on a street.

The doesn’t mean the streetcar has to run on-street the entire way. Street running is slow, even with dedicated lanes. Paris’s T3, an orbital tram in the grassy median of the Boulevards des Maréchaux on the outer margin of the city, averages 18 km/h. Berlin’s streetcars average 19 km/h; a handful of central sections are mixed-traffic but most have dedicated lanes, and in outer parts of the city there’s just less traffic and lines are generally faster.

There are two main ways to speed up the streetcar: make it faster in city center via tunneling (called subway-surface, Stadtbahn, or premetro), or make it faster outside city center by finding grade-separated rights-of-way (called tram-trains). Confusing, both subway-surface and tram-train systems are called light rail in the US, and Germany’s most celebrated tram-train, that of Karlsruhe, is also called Stadtbahn. Because these systems have evolved from all-surface streetcars, the separation between them and streetcars is not always perfect, which is why the American distinction between light rail (either subway-surface or tram-train) and streetcar (all on-street) is sometimes muddied in popular reporting.

Can IBX function as a tram variant?

No.

The problem with running an orbital tram parallel to the right-of-way is that there is no good street for it to run on. On the map below, the thick black line denotes the right-of-way that IBX is to use:

Cropped from the official bus map

There are no on-street alternatives to the right-of-way. Brooklyn has three major orbital buses: the B35 on Church, and the B6 and B82. Church is not wide – dedicated lanes there would be contentious and still produce inferior speeds to those of T3, let alone streetcars in less dense cities; it’s a great corridor for dedicated bus lanes, but not for a tram. The B6 and B82 shift between different streets, as do other crosstown routes, like the B1, B3, B8, B9, and B11. Even Kings Highway is only 24 meters wide.

This, in turn, is why IBX is such a great idea: it provides service that the surface bus networks can’t provide, because the quality of rights-of-way is poor unless one uses the Bay Ridge Branch. When the street network is poor, surface transit ridership is suppressed relative to travel demand, which means that a rapid transit service like IBX will overperform any model trained on existing travel volumes.

This is also why no variant with any street running is viable. Not only is there no good street for a streetcar, but also there is no section of a street that is good for a streetcar. The narrow sections of the Bay Ridge Branch right-of-way, mainly the segment between the F and Q trains, don’t parallel any convenient street.

Moreover, subway-surface alignments work by branching the grade-separated core into many surface branches, but there is no good tie-in. Circumferential lines sometimes do branch, but the best use case is when there are major destinations just off the route. This is not the case for IBX: Brooklyn College is on-route. The most significant destination in Brooklyn off the route is Kings County Hospital/SUNY Downstate, which is unusually poorly-served by the street network even by Brooklyn standards, and is therefore only on one bus route, the B12, rather than at the intersection of multiple buses as it ideally should be. There is no viable surface deviation off of the IBX right-of-way that serves it.

So why light rail?

The modal alternatives analysis seems biased in favor of light rail. This, to be clear, is not light rail as a service or infrastructure technology – the plan is to use viaducts wherever the Bay Ridge Branch right-of-way is too narrow for IBX and freight tracks side by side. Rather, the plan is to use light rail vehicles on a service that is entirely rapid transit.

This has precedent in the United States. In the same manner that historic streetcars evolved into subway-surface lines in Boston, Philadelphia, and San Francisco, and into the tram-trains that are called light rail elsewhere (with inspiration from Germany, brought in by American troops serving there in the Cold War), some light rail lines evolve into fully grade-separated rapid transit. It’s uncommon, because usually the parts that are left on the surface are the most difficult to construct, but it does exist. The Green Line in Los Angeles runs LRVs on a fully grade-separated right-of-way, mostly in the median of the 105, and the Gold Line’s initial section to and beyond Pasadena has just 1.5 km of street running, on Marmion Way. In Calgary and Dallas there are plans to bury light rail lines, which could result in fully grade-separated lines that still run LRVs and are locally conceived of as light rail.

But in New York, this is not a wise course of action. Running rapid transit with LRVs is great for a city that has LRVs but not subway trains, like the Los Angeles of the early 1990s. A city with both may potentially still elect to use LRVs if it expects some surface extensions. But New York has large-scale operations and maintenance for subway rolling stock, and none for LRVs. The only light rail in the region is in Jersey City and Newark, which do not share management or maintenance facilities with the city, and couldn’t do the latter even if they wanted to since they’re on the wrong side of the Hudson.

If intermediate-capacity transit is desired, New York could build shorter platforms, only long enough for 4- or 5-car trains. If even less capacity is desired, it could go down to 2-car platforms; the rolling stock would need to be somewhat captive to the line, since the rest of the system runs permanently coupled 4- and 5-car trains, but that’s completely normal for a large subway system, and heavy maintenance facilities can still be shared. I’m wary of reductions in capacity just for the sake of downsizing – this is an entirely above-ground project, so station costs are not as onerous as they are underground – but I can see a case for smaller trains.

I can’t find a good reason for this preference for light rail over subway equipment for what is, by infrastructure and service, rapid transit. I can find many bad ones, of which the most likely is a desire for something different from the subway with all the connotations it has.

But this does not mean that the IBX plan is a tram. It’s not; it’s rapid transit service, which could easily be a normal subway, running LRVs for bad reasons.

Meme Weeding: Rich West, Poor East

There’s a common line in global history – I think it’s popularized through Eric Hobsbawm – that there is a universal east-west divide in temperate latitude cities. The idea is that the west side of those cities is consistently richer than the east side and has been continuously since industrialization, because prevailing winds are westerly and so rich people moved west to be upwind of industrial pollution. I saw this repeated on Twitter just now and would like to push back. Some cities have this pattern, some don’t, some even have the opposite pattern. Among cities the casual urbanist reader is likely to be familiar with, about the only one where this is true is Paris.

London

London famously has a rich west and poor east. I think this is why the line positing this directional pattern as universal is so common. Unfortunately, the origin of this pattern is too recent to be about prevailing winds.

In an early example of data visualization, Charles Booth made a block by block map of London in 1889, colored by social class, with a narrative description of each neighborhood. The maps indeed show the expected directionality, but with far more nuance. The major streets were middle-class even on the East End: Mile End Road was lined with middle-class homes, hardly what one would expect based on pollution. The poverty was on back alleys. South London exhibited the same pattern: middle-class major throughfares, back alleys with exactly the kind of poverty Victorian England was infamous for. West London was different – most of it was well-off, either middle-class or wealthier than that – but even there one can find the occasional slum.

East London in truth had a lot of working poor because it had a lot of working-class jobs, thanks to its proximity to the docks, which were east of the City because ports have been moving downriver for centuries with the increase in ship size. Those working poor did not always have consistent work and therefore some slipped into non-working poverty. The rich clustered in enclaves away from the poverty and those happened to be in the west, some predating any kind of industrialization. Over time the horizontal segregation intensified, as slums were likelier to be redeveloped (i.e. evicted) in higher-property value areas near wealth, and the pattern diffused to the broader east-west one of today.

Berlin

Berlin has a rich west and poor east – but this is a Cold War artifact of when West Berlin was richer than East Berlin, and the easternmost neighborhoods of the West were poor because they were near the Wall (thus, half their walk radius was behind the Iron Curtain) and far from City West jobs.

Before WW2, the pattern was different. West of city center, Charlottenburg was pretty well-off – but so was Friedrichshain, to the east. The sharpest division in Berlin was as in London, often within the same apartment building, which would house tens of apartments: well-off people lived facing the street, while the poor lived in apartments facing internal courtyards, with worse lighting and no vegetation in sight.

Tokyo

Tokyo has a similar east-west directionality as London, but with its own set of nuances. This should not be too surprising – it’s at 35 degrees north, too far south for the westerlies of Northern Europe; the winds change and are most commonly southerly there. The directionality in Tokyo is more about the opposition between uphill Yamanote and sea-level Shitamachi (the Yamanote Line is so named because the neighborhoods it passes through – Ikebukuro, Shinjuku, and Shibuya – formed the old core of Yamanote).

What’s more, the old Yamanote-Shitamachi pattern is also layered with a rich-center-poor-outskirts pattern. Chuo, historically in Shitamachi, is one of the wealthiest wards of Tokyo, thanks to its proximity to CBD jobs and the high rents commanded in an area where businesses build office towers.

The American pattern

The most common American pattern is that rich people live in the suburbs and poor people live in the inner city; the very center of an American city tends to be gentrified, creating a poverty donut surrounding near-center gentrification and in turn surrounded by suburban wealth. Bill Rankin of Radical Cartography has some maps, all as of 2000, and yet indicative of longer-term patterns.

New York is perhaps the best example of the poverty donut model: going outside the wealthy core consisting of Manhattan south of Harlem, inner Brooklyn, and a handful of gentrified areas in Jersey City and Hoboken near Manhattan, one always encounters poor areas before eventually emerging into middle-class suburbia. Directionality is weak, and usually localized – for example, the North Shore of Long Island is much wealthier than the South Shore, but both are east of the city.

Many American cities tend to have strong directionality in lieu of or in addition to the poverty donut. In Chicago, the North Side is rich, the West Side is working-class, and the South Side is poor. Many cities have favored quarters, such as the Main Line of Philadelphia, but that’s in addition to a poverty donut: it’s silly to speak of rich people moving west of Center City when West Philadelphia is one of the poorest areas in the region.

Where east-west directionality exists as in the meme, it’s often in cities without westerly winds. Los Angeles is at 34 degrees north and famously has a rich Westside and a poor Eastside – but those cannot possibly emerge from a prevailing wind pattern that isn’t consistent until one travels thousands of kilometers north. Houston is at 30 degrees north. More likely, the pattern in Los Angeles emerges from the fact that beachfront communities have always been recreational and the rich preferred to live nearby, and only the far south near the mouth of the river, in San Pedro and Long Beach, had an active industrial waterfront.

Sometimes, the directionality is the opposite of that of the meme. Providence has a rich east and poorer west. This is partly a longstanding pattern: the rivers flow west to east and north to south, and normally you’d expect rich people to prefer to live upriver, but in Providence the rivers are so small that only at their falls was there enough water power for early mills, producing industrial jobs and attracting working-class residents. However, the pattern is also reinforced with recent gentrification, which has built itself out of Brown’s campus on College Hill, spreading from there to historically less-well off East Side neighborhoods like Fox Point; industrial areas have no reason to gentrify in a city the size of Providence, and, due to the generations-long deindustrialization of New England, every reason to decline.

The Sweden Cost Report is Launched!

You can read it here. It evolved a lot during writing, partly because of the rising costs in the Nordic countries, partly because of the tension between the forward-looking rhetoric of what the report calls the globalized system and what interviewees with more practical involvement have said, partly because of the voluminous literature on models of capital construction and maintenance that only look at Northern Europe or the UK.

In a similar manner to the webinar about the Italian and Turkish cases, there is going to be a webinar about this one. The date is the 20th of September, 17:00 Central European Summer Time (UTC+2); here is the Zoom registration page. It will take the format of a short presentation, around half an hour, to be followed by a Q&A of indefinite duration, and I will try not to be mostly negative – even with the cost overruns, Nya Tunnelbanan is noticeably cheaper per km than the average 2020s subway, and there are a lot of commendable aspects of the Nordic model of infrastructure construction including at least one (labor efficiency) that is superior to the otherwise-cheaper Southern European models.

Deinterlining and Schedule Robustness

There’s an excellent Uday Schultz blog post (but I repeat myself) about subway scheduling in New York. He details some stunning incompetence, coming from the process used to schedule special service during maintenance (at this point, covering the entirety of the weekend period but also some of the weekday off-peak). Some of the schedules are physically impossible – trains are scheduled to overtake other trains on the same track, and at one point four trains are timetabled on the same track. Uday blames this on a combination of outdated software, low maintenance productivity, aggressive slowdowns near work zones, and an understaffed planning department.

Of these, the most important issue is maintenance productivity. Uday’s written about this issue in the past and it’s a big topic, of similar magnitude to the Transit Costs Project’s comparison of expansion costs. But for a fixed level of maintenance productivity, there are still going to be diversions, called general orders or GOs in New York, and operations planning needs to schedule for them. How can this be done better?

The issue of office productivity

Uday lists problems that are specific to scheduling, such as outdated software. But the software is being updated, it just happens to be near the end of the cycle for the current version.

More ominous is the shrinking size of ops planning: in 2016 it had a paper size of 400 with 377 positions actually filled, and by 2021 this fell to 350 paper positions and 284 actually filled ones. Hiring in the American public sector has always been a challenge, and all of the following problems have hit it hard:

  • HR moves extraordinarily slowly, measured in months, sometimes years.
  • Politicians and their appointees, under pressure to reduce the budget, do so stupidly, imposing blanket hiring freezes even if some departments are understaffed; those politicians universally lack the competence to know which positions are truly necessary and where three people do the job of one.
  • The above two issues interact to produce soft hiring freezes: there’s no hiring freeze announced, but management drags the process in order to discourage people from applying.
  • Pay is uncompetitive whenever unemployment is low – the compensation per employee is not too far from private-sector norms, but much of it is locked in pensions that vest after 25 years, which is not the time horizon most new hires think in.
  • The combination of all the above encourages a time clock managerial culture in which people do not try to rock the boat (because then they will be noticed and may be fired – lifetime employment is an informal and not a formal promise) and advancement is slow, and this too deters junior applicants with ambition.

Scheduling productivity is low, but going from 377 to 284 people in ops planning has not come from productivity enhancements that made 93 workers redundant. To the contrary, as Uday explains, the workload has increased, because the maintenance slowdowns have hit a tipping point in which it’s no longer enough to schedule express trains on local train time; with further slowdowns, trains miss their slots at key merge points with other lines, and this creates cascading delays.

Deinterlining and schedule complexity

One of the benefits of deinterlining is that it reduces the workload for ops planning. There are others, all pertaining to the schedule, such as reliability and capacity, but in this context, what matters is that it’s easier to plan. If there’s a GO slowing down the F train, the current system has to consider how the F interacts with every other lettered route except the L, but a deinterlined system would only have to consider the F and trains on the same trunk.

This in turn has implications for how to do deinterlining. The most urgent deinterlining in New York is at DeKalb Avenue in Brooklyn, where to the north the B and D share two tracks (to Sixth Avenue) and the N and Q share two tracks (to Broadway), and to the south the B and Q share tracks (to Coney Island via Brighton) and the D and N share tracks (to Coney Island via Fourth Avenue Express). The junction is so slow that trains lose two minutes just waiting for the merge point to clear, and a camera has to be set up pointing at the trains to help dispatch. There are two ways of deinterlining this system: the Sixth Avenue trains can go via Brighton and Broadway trains via Fourth Avenue, or the other way around. There are pros and cons either way, but the issue of service changes implies that Broadway should be paired with Fourth Avenue, switching the Q and D while leaving the B and N as they are. The reason is that the Fourth Avenue local tracks carry the R, which then runs local along Broadway in Manhattan; if it’s expected that service changes put the express trains on local tracks often, then it’s best to set the system up in a way that local and express pairings are consistent, to ensure there’s no interlining even during service changes.

This should also include a more consistent clockface timetable for all lines. Present-day timetabling practice in New York is to fine-tune each numbered and lettered service’s frequency at all times of day based on crowding at the peak point. It creates awkward situations in which the 4 train may run every 4.5 minutes and the 5, with which it shares track most of the way, runs every 5.5, so that they cannot perfectly alternate and sometimes two 4s follow in succession. This setup has many drawbacks when it comes to reliability, and the resulting schedule is so irregular that it visibly does not produce the intended crowding. Until 2010 the guideline was that off-peak, every train should be occupied to seated capacity at the most crowded point and since 2010 it has been 125% of seated capacity; subway riders know how in practice it’s frequently worse than this even when it shouldn’t be, because the timetables aren’t regular enough. As far as is relevant for scheduling, though, it’s also easier to set up a working clockface schedule guaranteeing that trains do not conflict at merge points than to fine-tune many different services.

Deinterlining and delocalization of institutional knowledge

Uday talks about New York-specific institutional knowledge that is lost whenever departments are understaffed. There are so many unique aspects of the subway that it’s hard to rely on scheduling cultures that come from elsewhere or hire experienced schedulers from other cities.

There is a solution to this, which is to delocalize knowledge. If New York does something one way, and peers in the US and abroad do it another way, New York should figure out how to delocalize so that it can rely on rest-of-world knowledge more readily. Local uniqueness works when you’re at the top of the world, but the subway has high operating costs and poor planning and operations productivity and therefore its assumption should be that its unique features are in fact bugs.

Deinterlining happens to achieve this. If the subway lines are operated as separate systems, then it’s easier to use the scheduling tools that work for places with a high degree of separation between lines, like Boston or Paris or to a large extent London and Berlin. This also has implications for what capital work is to be done, always in the direction of streamlining the system to be more normal, so that it can cover declining employee numbers with more experienced hires from elsewhere.

The Nine-Euro Ticket

A three-month experiment has just ended: the 9€ monthly, valid on all local and regional public transport in Germany. The results are sufficiently inconclusive that nobody is certain whether they want it extended or not. September monthlies are reverting to normal fares, but some states (including Berlin and Brandenburg) are talking about restoring something like it starting October, and Finance and Transport Ministers Christian Lindner and Volker Wissing (both FDP) are discussing a higher-price version on the same principle of one monthly valid nationwide.

The intent of the nine-euro ticket

The 9€ ticket was a public subsidy designed to reduce the burden of high fuel prices – along with a large three-month cut in the fuel tax, which is replaced by a more permanent cut in the VAT on fuel from 19% to 7%. Germany has 2.9% unemployment as of July and 7.9% inflation as of August, with core inflation (excluding energy and food) at 3.4%, lower but still well above the long-term target. It does not need to stimulate demand.

Moreover, with Russia living off of energy exports, Germany does not need to be subsidizing energy consumption. It needs to suppress consumption, and a few places like Hanover are already restricting heating this winter to 19 degrees and no higher. The 9€ ticket has had multiple effects: higher use of rail, more domestic tourism, and mode shift – but because Germany does not need fiscal stimulus right now and does need to suppress fuel consumption, the policy needs to be evaluated purely on the basis of mode shift. Has it done so?

The impact of the nine-euro ticket on modal split

The excellent transport blog Zukunft Mobilität aggregated some studies in late July. Not all reported results of changes in behavior. One that did comes from Munich, where, during the June-early July period, car traffic fell 3%. This is not the effect of the 9€ ticket net of the reduction in fuel taxes – market prices for fuel rose through this period, so the reduction in fuel taxes was little felt by the consumer. This is just the effect of more-or-less free mass transit. Is it worth it?

Farebox recovery and some elasticities

In 2017 and 2018, public transport in Germany had a combined annual expenditure of about 14 billion €, of which a little more than half came from fare revenue (source, table 45 on p. 36). In the long run, maintaining the 9€ ticket would thus involve spending around 7 billion € in additional annual subsidy, rising over time as ridership grows due to induced demand and not just modal shift. The question is what the alternative is – that is, what else the federal government and the Länder can spent 7 billion € on when it comes to better public transport operations.

Well, one thing they can do is increase service. That requires us to figure out how much service growth can be had for a given increase in subsidy, and what it would do to the system. This in turn requires looking at service elasticity estimates. As a note of caution, the apparent increase in public transport ridership over the three months of more or less free service has been a lot less than what one would predict from past elasticity estimates, which suggests that at least fare elasticity is capped – demand is not actually infinite at zero fares. Service elasticities are uncertain for another reason: they mostly measure frequency, and frequency too has a capped impact – ridership is not infinite if service arrives every zero minutes. Best we can do is look at different elasticity estimates for different regimes of preexisting frequency; in the highest-frequency bucket (every 10 minutes or better), which category includes most urban rail in Germany, it is around 0.4 per the review of Totten-Levinson and their own work in Minneapolis. If it’s purely proportional, then doubling the subsidy means increasing service by 60% and ridership by 20%.

The situation is more complicated than a purely proportional story, though, and this can work in favor of expanding service. Just increasing service does not mean doubling Berlin U-Bahn frequency from every 5 to every 2.5 minutes; that would achieve very little. Instead, it would bump up midday service on the few German rail services with less midday than peak frequency, upgrade hourly regional lines to half-hourly (in which case the elasticity is not 0.4 but about 1), add minor capital work to improve speed and reliability, and add minor capital work to save long-term operating costs (for example, by replacing busy buses with streetcars and automating U-Bahns).

The other issue is that short- and long-term elasticities differ – and long-term elasticities are higher for both fares (more negative) and service (more positive). In general, ridership grows more from service increase than from fare cutting in the short and long run, but it grows more in the long run in both cases.

The issue of investment

The bigger reason to end the 9€ ticket experiment and instead improve service is the interaction with investment. Higher investment levels call for more service – there’s no point in building new S-Bahn tunnels if there’s no service through them. The same effect with fares is more muted. All urban public transport agencies project ridership growth, and population growth is largely urban and transit-oriented suburban.

An extra 7 billion € a year in investment would go a long way, even if divided out with direct operating costs for service increase. It’s around 250 km of tramway, or 50 km of U-Bahn – and at least the Berlin U-Bahn (I think also the others) operationally breaks even so once built it’s free money. In Berlin a pro-rated share – 300 million €/year – would be a noticeable addition to the city’s 2035 rail plan. Investment also has the habit to stick in the long term once built, which is especially good if the point is not to suppress short-term car traffic or to provide short-term fiscal stimulus to a 3% unemployment economy but to engage in long-term economic investment.

Nordic Costs and Institutional Knowledge

Institutional knowledge at agencies that build infrastructure shapes up to be an important factor behind how well they handle projects. Good agencies build up a knowledge base over time that lets them see what works and what doesn’t, and this way they’re capable of making in-house planning decisions, and even when they use consultants, they make sure to learn what the consultants have taught them and implement those lessons in the future. In our Italian, Turkish, and (soon to be released) Swedish cases, the agencies have all built up this knowledge over decades.

Denmark provides an interesting test case for this, because Copenhagen opened its metro in 2002 (Helsinki: 1982; Oslo: 1966, Stockholm: 1950), and so it’s possible to compare it with the other Nordic capitals. The construction costs in Copenhagen are notably higher: the City Circle Line (built 2009-19) cost 25,300 DKK for 15.5 km, which in 2022 PPP dollars is around $280 million/km, and the soon-to-open M4 extension to Sydhavn is 9,100 DKK for 4.5 km, or $330 million/km; in contrast, we have the following costs for the other Nordic capitals:

CityLineLengthYearsCostCost/km (2022 PPP)
OsloLøren1.613-161.33b NOK$110 million
OsloFornebu8.220-2916.2b NOK, ’18
26.4b NOK, ’21		$330 million
StockholmNya Tunnelbanan1920-3032b SEK, ’16$235 million
HelsinkiWest Metro phase 113.509-171.171b€$145 million
HelsinkiWest Metro phase 2714-231.159b€$275 million

All of these costs are higher than you may have seen in past posts – this is mostly an inflation artifact (and in particular, you should mentally increment all costs by 25% if you remember them in mid-2010s dollars). But it’s notable that in both Oslo and Helsinki, real costs are sharply up; the Fornebu Line is more complex than the Løren Line, but much of its complexity is an engineering choice to deep-mine the stations.

In Stockholm there’s no similar comparison, but Citybanan cost, also in 2022 PPP dollars, $365 million/km, and a factor of 1.5 is an unusually low premium for city center regional rail carrying 250 meter trains over regular metro trains; the RER premium in Paris looks like a factor of 2, and the Munich S-Bahn tunnel was budgeted at a factor of 2 premium over a current U-Bahn extension and has since announced a factor of 2 overrun over that, for which it has been widely mocked in the German press. It’s plausible that when the regional rail premium is netted out properly, Stockholm has in fact seen a large real increase in costs, which matches the history of Nya Tunnelbanan’s cost overrun, from 23 to 32 billion kronor.

Denmark is seeing a real cost increase as well, but a much smaller one. In effect, what’s happening is that Copenhagen started building its metro in the 1990s at higher cost than Nordic norms, and in the generation since then, costs in the other Nordic countries have converged to Danish costs.

So what’s going on?

Some hints can be found in the details of the most recent Danish extension, M4 to Sydhavn. The soft cost multiplier over hard costs is higher than one would find elsewhere, and the contingency is 30% at the contract award, an unusually high figure; 20% is more typical, or even less at contract award (but more during earlier planning). Moreover, the entire project was awarded as a single design-build contract to a joint venture of Vinci and Hochtief, with hard costs worth 460M€.

The entire Nordic world is trying to transition to that style of contracting. This is inspired by British and Dutch models of privatization, which the state, academic, and consultant studies I’ve read while writing the Stockholm report view positively. The procurement strategy for Trafikverket in Sweden calls for transitioning to a so-called “pure client” model for the next big rail investment, Gothenburg’s West Link, like Citybanan not included on the above table as it is a regional rail through-running tunnel. The emerging model in the Nordic countries, which I call globalized in the report since it aims at international competitiveness attracting global contracting firms, can be compared with the traditional model as follows:

TraditionalGlobalized
Design-bid-buildDesign-build
Itemized contractsFixed price contracts
Smaller contracts (hundreds of millions of kronor)Larger contracts (billions of kronor)
Product procurement (“how to build”)Functional procurement (“what to build”)
Public client riskPrivate contractor risk

The Nordic project I’m most familiar with, Nya Tunnelbanan, does not use the globalized system; it uses elements of both the globalized and the traditional systems, but the trend is to be more globalized. Moreover, the Fornebu Line uses design-bid-build; its problem is partly that the private risk allocation encourages defensive design. If the builder strictly follows the design, all liability is on the designer, otherwise it’s on the builder; thus, the builder strictly follows the design, and because geotechnical surprises are inevitable during tunneling, the designer is overly cautious and tries to anticipate every potential problem rather than seeing what is actually necessary while the tunnel is dug. The traditional system has problems, especially when the risk allocation is improper like this. What’s more, the preference for larger contracts over smaller ones comes from ongoing industry consolidation – there just aren’t enough domestic contractors anymore, and pan-European ones, let alone global ones, are not going to enter an unfamiliar market for a $100 million contract. Unfortunately, the move to privatization of risk under the pure client model does not improve things, and is associated with higher costs.

I am less familiar with the Copenhagen Metro than with the Stockholm Metro, but from reading both how the expansion is done and what Eno is saying about its model (it did a case there but not in Stockholm), Denmark was an early adopter of the globalized system. Eno even pointed out that it uses design-build to showcase that low-construction cost cities use it successfully.

So the Denmark effect is real – this does appear to be a matter of experience. Having never built a metro before – the last urban rail tunnel in Denmark, the S-tog, opened in 1934 – Copenhagen never had the institutional knowledge of how to use the traditional system, so it opted for (elements of) the globalized system, which was not how the other Nordic countries did things but was what British consultants recommended. Note that this does not mean higher costs (that is, around global average, rather than far less) were inevitable in Denmark – it could have adopted the traditional system by leaning on intra-Nordic connections, which are extensive. But perhaps in the 1990s, and certainly in the 2000s, even the other Nordic countries started to come to believe in greater privatization of risk.

The tragedy is that we can see, in real time, how good institutional knowledge is forgotten. Nya Tunnelbanan is, by itself, a pretty straightforward case of cost overrun. But in the context of parallel trends in Helsinki and Oslo, and perhaps an imputation of how much more complex Citybanan was, the situation is different. Real costs increased over time – this was not a mere matter of cost underestimation. Moreover, they increased during a time of ongoing, successful construction of metro projects – the lines that have opened all have healthy ridership, encouraging plans to build even more. And yet, the real problems with the traditional system have led to the adoption of what appears to be a worse procurement system, supported every step of the way by the same agencies that used to compete for world records for low-cost construction.

The Baboon Rule

I made a four-hour video about New York commuter rail timetabling on Tuesday (I stream on Twitch most Tuesdays at 19:00 Berlin time); for this post, I’d like to extract just one piece of this, which informs how I do commuter rail proposals versus how Americans do them. For lack of a better term, on video I called one of the American planning maxims that I violate the baboon rule. The baboon rule states that an agency must assume that other agencies that it needs to interface with are run by baboons, who are both stupid and unmovable. This applies to commuter rail schedule planning but also to infrastructure construction, which topic I don’t cover in the video.

How coordination works

Coordination is a vital principle of good infrastructure planning. This means that multiple users of the same infrastructure, such as different operators running on the same rail tracks, or different utilities on city streets, need to communicate their needs and establish long-term horizontal relationships (between different users) and vertical ones (between the users and regulatory or coordinating bodies).

In rail planning this is the Verkehrsverbund, which coordinates fares primarily but also timetables. There are timed transfers between the U- and S-Bahn in Berlin even though they have two different operators and complex networks with many nodes. In Zurich, not only are bus-rail transfers in the suburbs timed on a 30-minute Takt, but also buses often connect two distinct S-Bahn lines, with timed connections at both ends, with all that this implies about how the rail timetables must be built.

But even in urban infrastructure, something like this is necessary. The same street carries electric lines, water mains, sewer mains, and subway tunnels. These utilities need to coordinate. In Milan, Metropolitana Milanese gets to coordinate all such infrastructure; more commonly, the relationships between the different utilities are horizontal. This is necessary because the only affordable way to build urban subways is with cut-and-cover stations, and those require some utility relocation, which means some communication between the subway builders and the utility providers is unavoidable.

The baboon rule

The baboon rule eschews coordination. The idea, either implicit or explicit, is that it’s not really possible to coordinate with those other agencies, because they are always unreasonable and have no interest in resolving the speaker’s problems. Commuter rail operators in the Northeastern US hate Amtrak and have a litany of complaints about its dispatching, and vice versa – and as far as I can tell those complaints are largely correct.

Likewise, subway builders in the US, and not just New York, prefer deep tunneling at high costs and avoid cut-and-cover stations just to avoid dealing with utilities. This is not because American utilities are unusually complex – New York is an old industrial city but San Jose, where I’ve heard the same justification for avoiding cut-and-cover stations, is not. The utilities are unusually secretive about where their lines are located, but that’s part of general American (or pan-Anglosphere) culture of pointless government secrecy.

I call this the baboon rule partly because I came up with it on the fly during a Twitch stream, and I’m a lot less guarded there than I am in writing. But that expression came to mind because of the sheer horror that important people at some agencies exuded when talking about coordination. Those other agencies must be completely banally evil – dispatching trains without regard for systemwide reliability, or demanding their own supervisors have veto power over plans, or (for utilities) demanding their own supervisors be present in all tunneling projects touching their turf. And this isn’t the mastermind kind of evil, but rather the stupid kind – none of the complaints I’ve heard suggests those agencies get anything out of this.

The baboon rule and coordination

The commonality to both cases – that of rail planning and that of utility relocation – is the pervasive belief that the baboons are unmovable. Commuter rail planners ask to be separated from Amtrak and vice versa, on the theory that the other side will never get better. Likewise, subway builders assume electric and water utilities will always be intransigent and there’s nothing to be done about it except carve a separate turf.

And this is where they lose me. These agencies largely answer to the same political authority. All Northeastern commuter rail agencies are wards of the federal government; in Boston, the idea that they could ever modernize commuter rail without extensive federal funding is treated as unthinkable, to the point that both petty government officials and advocates try to guess what political appointees want and trying to pitch plans based on that (they never directly ask, as far as I can tell – one does not communicate with baboons). Amtrak is of course a purely federal creature. A coordinating body is fully possible.

Instead, the attempts at coordination, like NEC Future, ask each agency what it wants. Every agency answers the same: the other agencies are baboons, get them out of our way. This way the plan has been written without any meaningful coordination, by a body that absolutely can figure out combined schedules and a coordinated rolling stock purchase programs that works for everyone’s core passenger needs (speed, capacity, reliability, etc.).

The issue of utilities is not too different. The water mains in New York are run by DEP, which is a city agency whereas the MTA is a state agency – but city politicians constantly proclaim their desire to improve city infrastructure, contribute to MTA finances and plans (and the 7 extension was entirely city-funded), and would gain political capital from taking a role in facilitating subway construction. And yet, it’s not possible to figure out where the water mains are, the agency is so secretive. Electricity and steam are run by privately-owned Con Ed, but Con Ed is tightly regulated and the state could play a more active role in coordinating where all the underground infrastructure is.

And yet, in no case do the agencies even ask for such coordination. No: they ask for turf separation. They call everyone else baboons, if not by that literal term, but make the same demands as the agencies that they fight turf wars with.