Category: Good Transit
Institutional Issues: Coordination
In this installment of institutional issues, I’m going to talk about coordination, following up from procurement, professional oversight, transparency, proactive regulations, and dealing with change.
The state is to a large extent a coordinating body. Even the more extractive aspects of it, like historically the military, succeeded or failed not by who was the most brutal (they all were brutal) but by who was most efficient at organizing large groups of people.
Coordination in public transit is especially important, because it’s a system with many moving parts: infrastructure, equipment, timetable, development. These do not accrete spontaneously, not in any society that has also invented cars; transit-oriented development in the 21st century looks different from historic development before mass motorization. Organizational capacity makes the difference between a state that grows around mass transit, like Japan or South Korea or Switzerland or Sweden or increasingly France, and one that grows around cars even when the goal is nominally transit first, as is common in the United States but also most of Southeast Asia.
So in general, better coordination means overall better public transit. But it specifically means better investment – more targeted at the right places. And this is especially visible in mainline rail, which is less self-contained than urban metro lines. The right way to plan is to get different bodies to cooperate, such as different railroads and government agencies. And then there is the wrong, American way.
Coordination versus wishlists
In theory, the United States has mechanisms to get different agencies to talk to one another. The Northeast Corridor planning process understands that the corridor has many users and owners: Amtrak, MBTA, Connecticut DOT, MTA, New Jersey Transit, SEPTA, MARC. To ensure they collaborate, there are layers set on top of them, like the NEC Commission.
And yet, the NEC Commission’s plans are not worth the paper they are written on, and the people involved should not work in this field or in government again. The problem is that their idea of coordination is to ask each of the above agencies what its wishlist is, collate the responses, and staple them together.
The wishlist staple job is the opposite of coordination. Coordination means sitting down with intercity and regional rail operators, figuring out their service needs, and writing down a timetable with associated infrastructure plan that maximizes service at minimum cost. Even the accidental moves toward coordination that do exist, like the MBTA plan to complete electrification of the Providence Line and run modern EMUs rather than diesels under catenary, do not figure into the plan: Amtrak still wants a third track on the Providence Line, which such electrification obviates even if Amtrak cuts its Boston-Providence trip time in half. The third track was said to cost $400 million years ago; I do not know if it is still its budget or whether costs are higher now. One such unnecessary project at a time is what it takes to turn what should be a $15 billion project into three-figure billions.
This wishlist mentality is present whenever bad planners (e.g. all Americans) try to do something that involves more than one agency. It’s assumed that different parts of the government must constantly be at one another’s throats. Unless one agency dominates, the only solutions in this mentality are either to do a staple job, or subordinate all agencies to one new hierarchy, typically run by people who have never run transit service and do not respect those who have.
How to plan mainline rail better
Three of the legs of coordinated planning – infrastructure, rolling stock, timetable – are coordinated in an excellent way in Switzerland. (Switzerland is unfortunately too NIMBY for modern TOD.) This does not mean slavishly copying every single Swiss decision, but it does mean that it behooves planners to learn how Swiss rail planners got Europe’s best rail network on a limited (though not quite austerity) budget.
The way it should work is that everything begins from the timetable. Trains must run on the same fixed interval – typically hourly, but denser services should be planned around shorter intervals like 30 minutes or smaller divisors of the hour. This provides the base level of coordination: connections between trains at major stations are to be done at times that are compatible with this interval.
If the trip time between major stations (“Knoten”) is just a bit too long for timed connections at both ends, it means that the trains should be sped up. This is the run trains as fast as necessary maxim, beloved by many high-speed rail opponents who bring up that maxim far more often than they bring up how much rail tunneling Switzerland has built.
Everything must come based on this plan. The choice of rolling stock must be compatible. Switzerland chose bilevel EMUs, because its use case is urban stations with a surplus of platform tracks but limited platform length; the bilevel trades off higher on-train capacity per unit of train length for lower egress capacity, and in a country where the main train station has 26 tracks, the bilevel is the correct choice. Maybe in another environment it is and maybe it isn’t; in New York it is not.
The slate of infrastructure projects must likewise be based on total integration of operations and capital planning. This means being able to trace delays to their source, using data to figure out what the most problematic areas are, and fixing them. Swiss trains are not inherently punctual; delays in the 5 minute range are routine. What sets them apart is that the infrastructure has been designed, at minimum cost, to ensure that delays don’t propagate, whereas in Germany, cascading delays are more common, and the less said about the United States, the better.
Swiss integration, to be clear, operates in an environment that is highly federal, has a smattering of private railroads interoperating with SBB, is stingy about public spending, and has in most cases Western Europe’s most privatized economy. And yet there is no separation of infrastructure and operations, in contrast with the trend in Britain and the EU.
Coordination and saying no
A planning agency that has to work with operators to ensure they all collaborate has to mediate conflict in many cases. This is the origin of the wishlist mentality: by planning overly expensive systems with maximum separation between operators, conflict is avoided, at the minor cost of an order of magnitude increase in the budget.
A better way to mediate is to either propose compromises, or outright saying no. Investment that is not part of the coordinated plan is extra and infrastructure plans should not burden the taxpayers with it. If different bodies conflict, sometimes one is right and the other is wrong, and the infrastructure planners should say so; sometimes who is right and who is wrong is consistent, sometimes it isn’t. Moreover, if bodies refuse to coordinate, it’s important to be able to say no to overall plans.
All of this interfaces with previous posts on this subject. In particular, the infrastructure investment program, whether it’s a regional Verkehrsverbund or an intercity system like the NEC Commission, should consist of subject matter experts. Senior politicians should understand that those experts are paid to maximize the efficiency of an enormous infrastructure program and therefore defend their expertise against attacks.
Institutional Issues: Dealing with Technological and Social Change
I’ve covered issues of procurement, professional oversight, transparency, and proactive regulations so far. Today I’m going to cover a related institutional issue, regarding sensitivity to change. It’s imperative for the state to solve the problems of tomorrow using the tools that it expects to have, rather than wallowing in the world of yesterday. To do this, the civil service and the political system both have to be sensitive to ongoing social, economic, and technological changes and change their focus accordingly.
Most of this is not directly relevant to construction costs, except when changes favor or disfavor certain engineering methods. Rather, sensitivity to change is useful for making better projects, running public transit on the alignments where demand is or will soon be high using tools that make it work optimally for the travel of today and tomorrow. Sometimes, it’s the same as what would have worked for the world of the middle of the 20th century; other times, it’s not, and then it’s important not to get too attached to nostalgia.
Yesterday’s problems
Bad institutions often produce governments that, through slowness and stasis, focus on solving yesterday’s problems. Good institutions do the opposite. This problem is muted on issues that do not change much from decade to decade, like the political debate over overall government spending levels on socioeconomic programs. But wherever technology or some important social aspect changes quickly, this problem can grow to the point that outdated governance looks ridiculous.
Climate change is a good example, because the relative magnitudes of its various components have shifted in the last 20 years. Across the developed world, transportation emissions are rising while electricity generation emissions are falling. In electricity generation, the costs of renewable energy have cratered to the point of being competitive from scratch with just the operating costs of fossil and nuclear power. Within renewable energy, the revolution has been in wind (more onshore than offshore) and utility-scale solar, not the rooftop panels beloved by the greens of last generation; compare Northern Europe’s wind installation rates with what seemed obvious just 10 years ago.
I bring this up because in the United States today, the left’s greatest effort is spent on the Build Back Better Act, which they portray as making the difference between climate catastrophe and a green future, and which focuses on the largely solved problem of electricity. Transportation, which overtook electricity as the United States’ largest source of emissions in the late 2010s, is shrugged off in the BBB, because the political system of 2021 relitigates the battles of 2009.
This slowness cascades to smaller technical issues and to the civil service. A slow civil service may mandate equity analyses that assume that the needs of discriminated-against groups are geographic – more transit service to black or working-class neighborhoods – because they were generations ago. Today, the situation is different, and the needs are non-geographic, but not all civil service systems are good at recognizing this.
The issue of TOD
Even when the problem is static, for example how to improve public transit, the solutions may change based on social and technological changes.
The most important today is the need to integrate transportation planning with land use planning better. Historically, this wasn’t done much – Metro-land is an important counterexample, but in general, before mass motorization, developers built apartments wherever the trains went and there was no need for public supervision. The situation changed in the middle of the 20th century with mass competition with the automobile, and thence the biggest successes involved some kind of transit-oriented development (TOD), built by the state like the Swedish Million Program projects in Stockholm County or by private developer-railroads like those of Japan. Today, the default system is TOD built by private developers on land released for high-density redevelopment near publicly-built subways.
Some of the details of TOD are themselves subject to technological and social change:
- Deindustrialization means that city centers are nice, and waterfronts are desirable residential areas. There is little difference between working- and middle-class destinations, except that city center jobs are somewhat disproportionately middle-class.
- Secondary centers have slowly been erased; in New York, examples of declining job centers include Newark, Downtown Brooklyn, and Jamaica.
- Conversely, there is job spillover from city center to near-center areas, which means that it’s important to allow for commercialization of near-center residential neighborhoods; Europe does this better than the United States, which is why at scale larger than a few blocks, European cities are more centralized than American ones, despite the prominent lack of supertall office towers. Positive New York examples include Long Island City and the Jersey City waterfront, both among the most pro-development parts of the region.
- Residential TOD tends to be spiky: very tall buildings near subway stations, shorter ones farther away. Historic construction was more uniformly mid-rise. I encourage the reader to go on some Google Earth or Streetview tourism of a late-20th century city like Tokyo or Taipei and compare its central residential areas with those of an early-20th century one like Paris or Berlin.
The ideal civil service on this issue is an amalgamation of things seen in democratic East Asia, much of Western and Central Europe, and even Canada. Paris and Stockholm are both pretty good about integrating development with public transit, but only in the suburbs, where they build tens of thousands of housing units near subway stations. In their central areas, they are too nostalgic to redevelop buildings or build high-rises even on undeveloped land. Tokyo, Seoul, and Taipei are better and more forward-looking.
Public transit for the future
Besides the issue of TOD, there are details of how public transportation is built and operated that change with the times. The changes are necessarily subtle – this is mature technology, and VC-funded businesspeople who think they’re going to disrupt the industry invariably fail. This makes the technology ideal for treatment by a civil service that evolves toward the future – but it has to evolve. The following failures are regrettably common:
- Overfocus on lines that were promised long ago. Some of those lines remain useful today, and some are underrated (like Berlin’s U8 extension to Märkisches Viertel, constantly put behind higher cost-per-rider extensions in the city’s priorities). But some exist out of pure inertia, like Second Avenue Subway phases 3-4, which violates two principles of good network design.
- Proposals that are pure nostalgia, like Amtrak-style intercity trains running 1-3 times per day at average speeds that would shame most of Eastern Europe. Such proposals try to fit to the urban geography of the world of yesterday. In Germany, the coalition’s opposition to investment in high-speed rail misses how in the 21st century, German urban geography is majority-big city, where a high-speed rail network would go.
- Indifference to recent news relevant to the technology. Much of the BART to San Jose cost blowout can still be avoided if the agency throws away the large-diameter single-bore solution, proposed years ago by people who had heard of its implementation in Barcelona on L9 but perhaps not of L9’s cost overruns, making it by far Spain’s most expensive subway. In Germany, the design of intercity rail around the capabilities of the trains of 25 years ago falls in this category as well; technology moves on and the ongoing investments here work much better if new trains are acquired based on the technology of the 2020s.
- Delay in implementation of easy technological fixes that have been demonstrated elsewhere. In a world with automatic train-mounted gap fillers, there is no excuse anywhere for gaps between trains and platforms that do not permit a wheelchair user to board the train unaided.
- Slow reaction time to academic research on best practices, which can cover issues from timetabling to construction methods to pricing to bus shelter.
Probably the most fundamental issue of sensitivity to social change is that of bus versus rail modal choice. Buses are labor-intensive and therefore lose value as the economy grows; the high-frequency grid of 1960s Toronto could not work at modern wages, hence the need to shift public transit from bus to rail as soon as possible. This in turn intersects with TOD, because TOD for short-stop surface transit looks uniformly mid-rise rather than spiky. The state needs to recognize this and think about bus-to-rail modal shift as a long-term goal based on the wages of the 21st century.
The swift state
In my Niskanen piece from earlier this year, I used the expression building back, quickly, and made references to acting swiftly and the swift state. I brought up the issue of speeding up the planning lead time, such as the environmental reviews, as a necessary component for improving infrastructure. This is one component of the swift state, alongside others:
- Fast reaction to new trends, in technology, where people travel, etc. Even in deeply NIMBY areas like most of the United States, change in urban geography is rapid: job centers shift, new cities that are less NIMBY grow (Nashville’s growth rates should matter to high-speed rail planning), and connections change over time.
- Fast rulemaking to solve problems as they emerge. This means that there should be fewer layers of review; a civil servant should be empowered to make small decisions, and even the largest decisions should be delegated to a small expert team, intersecting with my previous posts about civil service empowerment.
- Fast response time to civil complaints. It’s fine to ignore a nag who thinks their property values deserve state protection, but if people complain about noise, delays, slow service, poor UI, crime, or sexism or racism, take them seriously. Look for solutions immediately instead of expecting them to engage in complex nonprofit proof-of-work schemes to show that they are serious. The state works for the people, and not the other way around.
- Constant amendment of priorities based on changes in the rest of society. A state that wishes to fight climate change must be sensitive to what the most pressing sources of emissions are and deal with them. If you’re in a mature urban or national economy, and you’re not frustrating nostalgics who show you plans from the 1950s, you’re probably doing something wrong.
In all cases, it is critical to build using the methods of the world of today, aiming to serve the needs of the world of tomorrow. Those needs are fairly predictable, because public transit is not biotech and changes therein are nowhere near as revolutionary as mRNA and viral vector vaccines. But they are not the same as the needs of 60 years ago, and good institutions recognize this and base their budgetary and regulatory focus on what is relevant now and not what was relevant when color TVs were new.
Institutional Issues: Proactive and Reactive Regulations
So far, in this series on institutional factors behind differences in the quality and cost of public transportation infrastructure, I’ve gone over procurement, public-sector oversight, and transparency. These three posts can be read together as a series: procurement is the keystone, and to get it right it is critical to have high-quality in-house supervision of the work, and to get that right in turn it’s important to cultivate transparency.
Today I’m going to turn the camera 90 degrees and talk about another relevant issue: that of proactive versus reactive state regulation and supervision. This is related to the issue of oversight, in that proactive regulation requires deeper in-house expertise and detachment from politics, so that the state can effectively make changes as necessary based on changes in travel and social patterns and advances in knowledge by scientists and practitioners.
Nudging and doing
One of the distinctions I’ve noticed regarding different regulatory traditions is whether the regulators do things or merely nudge. This is related to the issue of oversight, in that strong engineering bureaucracies that do design and planning in-house also come up with their own sets of clear rules.
The Italian civil service does rather than nudges: there are clear proactive rules by the Ministry of Culture about the protection of historical monuments, limiting the permitted building settlement in sensitive areas to 3 mm. Such proactive clear rules lead to a more predictable legal situation since it’s easy to measure what is and what is not legal, reducing risk. Long-term standards that impose real costs on business also soon sprout innovation for how to follow them while minimizing costs, as is the case for Japanese and Chinese zoning standards for light; ad hoc rules instead impose new costs every time, since the investment in trying to adapt to them would be spread across just one project rather than many.
The American regulatory apparatus has a mixture of doing and nudging. Environmental protection is almost entirely adversarial: the National Environmental Protection Act requires agencies to prepare environmental impact statements (EISes) before every project, but those are not judged by regulators but instead subject to lawsuit, and soon the nudge turns into red tape with hundreds of pages in an EIS aiming to anticipate every possible legal objection. Labor law is largely adversarial, but some states have passed triple damages statutes, in which the penalty for violation is specified at three times the missed wage and therefore workers do not have to litigate against much better-resourced employers.
The disability rights regime in the United States is a mix but include a significant amount of doing. There are clear standards for elevator accessibility, longest path of travel for people in wheelchairs, and maximum permitted gaps between the platform and the train; more recently, the FRA has wanted to mandate automatic gap fillers on mainline rail in order to permit passengers in wheelchairs to board unaided even across small gaps.
This is related to the issue of adversarial legalism, but is not exactly the same. There is plenty of adversarial legalism in the American disability rights regime, in which agencies refuse to follow the law and dare advocates to sue them.
Moreover, federal regulations in the United States remain a matter of nudging more than doing whenever there is any interaction with state and local authorities; instead of coordinating different authorities from a position of being able to engage in planning things itself, a federal agency will often try to nudge through offering incentives.
Two examples of equity
There’s a sense in much of the planning world in both the United States and Europe that it is necessary to proactively plan cities and transportation for the benefit of disadvantaged groups, or else even well-meaning planners would make unquestioned assumptions that harm such groups. It’s worthwhile examining the differences between the approaches to such planning, because one is proactive and the other reactive.
Before going on, I would like to point out a huge difference that is not about proactive planning: in the United States, the Title VI process for egalitarian planning (currently in revision, for which I’m very likely to submit comments make this and other points) centers racial equity, as a legacy of the civil rights movement that it came out of. In Europe, planners persistently ignore the problem of racism, and people of color are severely underrepresented in the civil services that I’ve seen, which issue is so glaring it makes Americans discount any European experience. However, European planners do look at class equity (for example, in Paris) and gender equity (for example, in Sweden), and there, they aim for proactive changes to reduce barriers to access.
The Swedish system is accessible to the English speaker, because feminist writers in English have occasionally looked to the Nordic world for inspiration, and outlets like Streetsblog have examined gender-based planning in Sweden. In 2015, Stockholm examined travel patterns by gender and found that women walk and take public transportation more and drive less than men, and as a result, it changed its snowplowing patterns to prioritize sidewalks over roads.
I was similarly told that when Swedish cities do surface construction, such as the cut-and-cover stations of Västlänken in Gothenburg or the cut-and-cover entry halls into the deep mined stations of the Stockholm T-bana extensions, by regulation the contractors must preserve sufficient sidewalk space on the street for pedestrians. If they need to open up most of the street, they can take car traffic lanes. The reasoning isn’t corrective discrimination, but rather that past planners, who prioritized keeping roads open over sidewalks, had erred because of conscious or unconscious discounting of the experience of women. The change in snowplowing practices led to a fall in injuries, since three times as many people in Sweden were injured walking in icy conditions as driving.
The Swedish system is proactive: the municipality or the state comes up with actionable, concrete changes based on its understanding of travel pattern. Researchers working for the city, perhaps in partnership with activists, notice a discriminatory practice, and come up with an alternative.
Now consider the American system. Title VI does not offer a clear set of practices for anti-racist transportation planning. It instead requires agencies to engage in review of their practices whenever they propose a change, leading first to status quo bias and second to arbitrary enforcement of rules. Much of the enforcement is not done top-down by regulators who are apolitical subject matter experts, but bottom-up from lawsuit or the threat thereof with supervision by judges trained in law but not in the specifics of transportation.
Status quo and reactivity
The worst aspect of reactive planning is that it leads to status quo bias. American regulations for civil rights and environmental protection require review of changes, but not of the status quo. The process can stop an agency from implementing a change or delay implementation until mitigations are done, but it cannot compel an agency to take an action it does not wish to take.
To nuance this somewhat, a judge can put an agency under a consent decree. But that already assumes an adversarial relationship between the state and itself. The process can imposing fines and constraints on an agency that does not want to do something, such as following ADA law and installing elevators at every subway station (something Berlin, an older system than New York, is about to complete systemwide). But it cannot literally build elevators there itself. It’s akin to the Jewish concept of a get, in which a rabbinical court can impose arbitrary fines on a husband who refuses to grant his wife a divorce, where what is needed is to permit women to initiate divorce without their husband’s permission.
A more proactive and less reactive regulatory culture can break out of the status quo trap. The first thing it must do is create a system that does not privilege the status quo: if a change is subject to review on such grounds as accessibility, racial equality, and environmental protection, then current practice must be as well. If it turns out that current practice falls short or is discriminatory, as Sweden’s snowplowing priorities were a decade ago, the agency must change its ways based on clear, concrete standards.
More proactive regulations are more obtrusive and visible, but they reduce costs and improve service quality. They are more sensitive to the current economic and social conditions and to the state of present-day knowledge than to the conditions and knowledge of a generation ago. They are more legible to the public and to contractors, who can then come up with ways to follow them without gambling on favorable judicial or political rulings. And they are less likely to surprise agencies deep into the process with a sudden imposition.
A state that acts as a helping hand rather than a grabbing hand helps more by governing more. Making it easier to ditch a status quo that worked for the world of yesterday but doesn’t for that of today or tomorrow, or one that never worked but was falsely believed to work, allows it to govern more efficiently. It’s necessary then to ensure that the highest-level civil servants who regulate transportation be empowered to make concrete decisions and coordinate lower-level agencies rather than just nudging in the right direction.
Institutional Issues: Transparency
Continuing with my series on institutional factors relevant to construction costs, I’d like to turn to a culture of transparency, or lack thereof. It’s unfortunate that the exact breakdown of costs by items and factors that we’ve seen in Italy and Turkey and are seeing in Sweden does not exist in the English-speaking world. It’s further unfortunate that there is an adversarial relationship in the Anglosphere between the civil service and academic researchers like us or the broad public.
It’s a delicate subject, because the cultures of opacity we’ve encountered, the American and the British, certainly correlate with high costs, but we cannot be perfectly certain that they cause them. The peripheral Anglosphere learns many things from the US and UK, so it could just be part of the general correlation between Anglosphere membership and high costs.
That said, we do have reasons to believe this matters. The opacity we’ve encountered in the US and UK is so severe that it ensures there is no proper oversight. A system that punishes junior workers for reporting problems will just not know they exist. It’s best viewed as the Xi Jinping school of governance: demand that people follow the line and not air out problems, until subordinates lie to you just as much as you lie to the public, and local party officials arrest doctors who report to the public about corona while Taiwan is already warning the world about it.
The organization of information
Many episodes of Yes, Minister prominently feature the red boxes of papers for the minister to review. The civil service prepares documents every night for review, and the minister, who thinks he is a reformer, demands to know everything – so the permanent secretary’s office gives him interminable work to look at, down to and including stationery requisition. Needless to say, the minister does not come out of this experience informed about the department’s workings.
One of the obstacles we’ve encountered to a clean itemized comparison of construction costs is that in the US (and apparently also the UK), the information either does not exist or is not made public. We know how much Second Avenue Subway cost; we know how much individual stations cost and even how the stations break down between the civil work and the finishes, but each of these is still $200-500 million in unitemized costs, given as a lump sum contract. There are independent itemized estimates used as a benchmark, but they’re confidential, since the MTA uses them to rate contractor bids.
Any further breakdown we’ve seen is at the level of the minister’s red boxes, stating individual salaries and contracts for concrete and widgets; it’s not even complete information, since most of the work is subcontracted, and what’s subcontracted is opaque even to the independent cost estimators. To the extent we have estimates at a level that’s at all useful, that is high single-digit millions to low tens of millions, they’re cobbled together from many different examples, to the great frustration of people who were hoping for a perfect recipe for them to solve the cost problem.
I must stress that this is in a relatively cooperative environment. I don’t think Janno Lieber is sitting on a detailed breakdown of contracts to tranches of about $30 million and is just making sure we don’t know it. I doubt that this information exists in an organized fashion at all – it lives in the lore of numerous private-sector middle managers each of whom knows a few items.
An example from Italy
Italy has a well-known problem with tax evasion. Pellegrino-Zingales consider tax evasion among small businesses to be one of the root causes behind Italy’s economy stagnation in the last generation, arguing that it encourages firms to hire and promote by loyalty and nepotism (alongside patronage-based credit networks) rather than by merit, and that this has been an especial drag in the age of IT.
More recently, D’Agostino-de Benedetto-Sobbrio consider this question from the other end: what makes people choose to evade taxes? They look at the impact of government spending, proposing two opposed theories: the government as a grabbing hand, which taxpayers perceive as out to get them, and the government as a helping hand, whose spending helps ordinary taxpayers. The grabbing hand model predicts that bigger government leads to more tax evasion, the helping hand model predicts the opposite. While Chinese tax evasion follows the grabbing hand model, Italian tax evasion follows the helping hand model: Italian government spending induces the taxpayers to perceive the Italian state as on their side, reducing tax cheating.
All of this should be treated as background to the fact that, in Italy, the public data on construction costs and their breakdown is of very high quality. Marco Chitti has obtained breakdowns at the level that is useful for us for the upcoming Italian case study, and having read a draft of his report, I can speak with relative confidence (less than he can, of course) about wages, staffing levels, techniques, relative costs, and what the problem sections are.
Transparency and openness
That Sweden has very high-quality public data is probably not surprising to readers who know even a little bit about Nordic institutions. Here, for example, is the published breakdown of one set of contracts for Nya Tunnelbanan. Nordic transparency is a general feature, seeping to so many places, to the point that academic hiring committees in Sweden produce public-facing spreadsheets of all applicants and brief comments on them, and if the comments are positive, along the lines of “almost makes our shortlist but we have too many good candidates this year,” then applicants use that in their next application.
But when it comes to infrastructure megaprojects, we’ve found high transparency wherever we’ve looked in Continental Europe. Italy has the same information quality – because the Italian state works for the people of Italy rather than lording over them in secret.
This transparency extends to analysis of problems. The cost overruns on Grand Paris Express have led to a report by the Cour des Comptes about what happened, with detailed analysis and cost breakdowns (albeit not at granular enough level for our case studies). The report is earnest because the French state, elitist as it is, still works for the public, and acknowledges errors. Likewise, academic work in Italy on cost problems, such as Paolo Beria’s paper on the high costs of Italian high-speed rail, is in wide circulation. In Sweden, there is not only academic student work about the cost overruns of Nya Tunnelbanan but also a brief report a civil servant involved in the project sent us explaining the issue of mid-project changes in regulations.
Then there are the UK and US, where the situation is different. The UK, and countries it influences like Australia, barely even informs the public of the expected cost of a project until it is time to approve it; David Levinson told me that in Australia all communication about costs comes from leaks and trial balloons, unlike in the more open US. Even learning the highest-level breakdown of Crossrail costs required using a freedom of information request, and project-level questions about the cost of individual stations are often redacted (Crossrail 2 made available information about relative costs of stations, not a specific number per station). Reports about critical technological change like driverless trains, increasingly adopted in Paris, are not available to the public in London except through leaks. American governance is somewhat more transparent in the early stages, but key information about choices is hidden in confidential documents; the freedom of information process takes forever and officials freely redact documents or reject handing them over. The American and British freedom of information process screams, the government doesn’t work for you – its relationship with you is adversarial.
Transparency and language
In the last year or so, observing ever more central circles of political activism in the United States, I’ve realized something important: federal policymakers, and state policymakers who interface with them, speak an inscrutable language of bureaucrats who nudge but do not do. This is best illustrated with examples:
- The Bipartisan Infrastructure Framework has a line item about federal funding for previously funded but canceled projects, inserted by Maryland’s senators in order to fund the Baltimore Red Line, which Governor Hogan canceled for racist reasons in 2017. Instead of openly including it as an earmark, or else letting the federal process play it out, the language uses a circumlocution.
- At a meeting with activists, another advocate asked Beth Osborne of Transportation for America (T4America) about bus shelter. Instead of dealing with the direct issue, she gave a soporific answer about the need for federal standards, which may be Washingtonian for what in English would be rendered as “yes, I’ll do what I can to make sure the feds fund bus shelters,” or it may be Washingtonian for endless process and yet another round of red tape; not speaking the language, I could not and still cannot tell.
The contrast is with the concrete, plain language I see elsewhere from civil servants, to the point that it’s easier for me to go through the Cour des Comptes report, in a language I speak imperfectly, than to try to translate from Washingtonian to English. All of this matters – the use of a form of language designed to speak only to Beltway insiders is itself a form of opacity and American civil servants need to train themselves to on the one hand be more technical when necessary but on the other hand be very clear about what they’re doing.
Transparency as a goal
The path forward must involve treating transparency not as an imposition to be fulfilled through checklists, which produce red boxes, but as a positive goal. It involves ensuring agencies are helpful to regulators, academics, and the broad public, rather than hiding decisions behind walls, often because the reasoning behind such decisions is weak. An academic is expected to make data available to peers and the public, and so must agencies and regulators.
Trust in the civil servants is crucial for public infrastructure to succeed. Results can speak for themselves even in a low-trust system – streets really do come before trust – but the US and UK have poor results. The adversarial relationship with the public produces bad outcomes, and people whose expertise is in stonewalling and making excuses must be replaced with people whose expertise is in building things and accurately reporting on what they’re doing so that others can replicate their success.
Institutional Issues: Professional Oversight
Continuing my series on institutional issues concerning infrastructure costs and quality, after the issue of procurement, I’d like to discuss the issue of the quality of public-sector oversight. It is critical to have extensive in-house expertise inside an apolitical civil service empowered to make technical decisions. The role of the political layer is to set up broad rules, not to micromanage. Conversely, while the top people should avoid micromanagement, they should be expert enough to be capable of making specific decisions.
Civil service and oversight
The importance of civil service to oversight is that it’s the professional layer that has to supervise planners, engineers, architects, and construction teams. There are too many small decisions for a single elected political layer, say a minister and a policy team the minister directly appoints and supervises.
In my procurement post, I was basing my recommendations on common threads I’d seen or read about in low- and medium-cost European countries, and to some extent practice in South Korea, a low-cost country on a par with Southern Europe. All of these make use of professional civil servants to make any of the following decisions:
- In-house planning. The macro-level decisions on funding levels are political (and never devolved to the agency through dedicated slush funds, unlike for US highways), but the decisions at the level just below, such as what programs to ask the politicians to fund, are made by professional agencies. High-speed rail was invented this way in Japan and then reinvented in France, while upgraded legacy rail was so invented in Germany and perfected in Switzerland.
- Design and engineering. Those can be done in-house or outsourced to consultants, or more likely some mixture of the two, but even if the design is contracted out, it’s the agency that owns the product and is responsible for it.
- Contractor selection. It is irresponsible to award a megaproject design contract based on the lowest bid. A technical score is used nearly universally in the low- and medium-cost examples we have looked at, and this means someone needs to come up with sound criteria for scoring and then evaluate each proposal. This has to be done more intelligently than just by rubric. A British source told us of a problem with British technical scoring: every large project is parceled out between different consultants, and thus all consultants can claim experience on the same project, making it impossible at that level to tell which companies do better work than others, even as industry insiders know who does bad work. The same source, when I asked about French comparisons, said that France has extensive in-house expertise and therefore doesn’t hire their consultancy.
- Contract supervision. Change orders are inevitable, especially for underground projects. Not coincidentally, in Eno’s database the American premium for subways is higher than for at-grade light rail, which is technically more predictable. It’s on the client agency to decide whether to accept or reject changes coming from unpredictable factors, and this requires extensive knowledge of the field.
In my procurement post, I spoke of flexibility. No client can have flexibility without oversight – flexibility without oversight is an anything-goes game in which the contractor abuses the client, the client abuses the contractor, or, most likely, both. And this oversight is necessarily detailed enough that it requires civil service.
An example from Sweden
I spoke to an experienced Swedish project manager earlier this year. The project manager talked to me about the major issues with the construction of Citybanan, the regional rail tunnel Stockholm opened 4 years ago, shortly after I left the country. This included issues of construction techniques (but for further engineering question my source referred me to an engineer) but also competition policy, negotiation, change orders, etc.
At one point in the interview, I asked about something a previous Swedish source told me about, called functional procurement. In functional procurement, the agency maximizes flexibility by specifying only the function of the project, such as the required capacity and schedule, and letting the contractors make suggestions as to how to fulfill it; this is similar to the military concept of mission command, stressing flexibility and training intermediate officers in how to use it in a hierarchical organization.
The project manager said of this growing trend in Swedish procurement: “I can’t say it makes it easier.” The manager then explained the constraints involved – railways have technical specs that make a functional contract not too different from a conventional one, where the design is already figured out and the contractors have to build to it with only minor modifications.
Let’s unpack what happened in that interview. A Swedish manager who does not know me, who I have never met, first of all talked to me in technically adept language, and second of all was willing to go on the record criticizing a trend in infrastructure construction procurement, a trend that the person who put us in contact had mentioned to me as a positive.
I have never heard this kind of internal criticism from American sources, unless they knew me well enough and were trying to get me to publish their internal problems in the media. And quite often, the criticism I would hear from the US was much more pungent, complaining about politics or a bad manager. “We have been trying this trend but I don’t think it’s working,” in exactly the tone you can imagine emerge from the style of quotation, is not a line I recall hearing from an American. The civil servants who criticize something are far more frantic, far more afraid. Sweden will trust its civil servants to literal death. The US (and UK) will not trust them to do anything but follow orders.
Is Sweden unique?
No. Strong traditions of professional civil service exist everywhere we’ve looked outside the US. Even the UK has a semblance of it; the problem there is that the topmost layer of civil servants – the Sir Humphreys – consists of lifelong generalist elites rather than domain experts.
In Italy, the situation is especially lopsided. The political layer of the government is weak because party control changes so often and ministers do not last, and there are so few political appointments that even with political instability, the civil service lasts across those changes. If anything, the instability makes the professional layer stronger.
Apolitical experts
It’s critical to ensure the civil service is not political. This doesn’t just mean that it should not be partisan. There are enough dominant-party jurisdictions in which it’s understood that the civil service exists to implement a predictable political agenda, which can be left-wing (Berlin, New York, California) or right-wing (Bavaria, Texas). Those jurisdictions all have problems coming from the lack of meaningful political competition, but those problems come from politicians, not civil servants. No: political noninterference goes much deeper, and means sidelining issues of petty personal priorities.
The ideal civil service has as few political appointees as possible. Those are neither elected nor meritorious. By their nature, they lack the legitimacy of both the politicians above them and the deep layer of domain experts below them. If they’re selected from among people with industry and operating experience then this is fine – technically senior generals are political appointments in both the US and Israel subject to the usual military norms, and Andy Byford was an external hire for New York City Transit with experience in the industry but not the agency. But letting generalist managers selected for political loyalty parachute in charge of agencies is a recipe for disaster.
The word for people who are always to be managed by people who are not from within their own social group is servants. Such people, knowing that their manager will always be someone who has other priorities that are not always transparent to them, will learn to lower their heads rather than proactively looking for ways to improve their institution.
A scientist working at a federal institution explained it to me this way: “There’s absolutely ways to speed things up, but they need cover from the political appointees at the top. A career officer understands their role to be following an existing plan, laid down in writing by either congress or by a planning process involving the top (i.e. political appointee) officers of the agency.”
This was meant to explain the sluggish FDA corona vaccine approval process, but can equally apply to infrastructure and operations of public transportation. Any variation from a plan written long ago by people who were often not even at the frontier of knowledge then requires political approval.
Trusting the civil service
A low-trust society isn’t one in which common people don’t trust the elites. It’s one in which the elites don’t trust the common people. In the context of civil service, it’s crucial to set up a system in which the top people affirm rather than scourge those below them.
Byford did it well, setting up a system encouraging employees to complain and suggest improvements, much to the surprise of managers at other MTA agencies who preferred scourging their subordinates. At the topmost level, it means the political layer needs to affirm the authority and expertise of the civil servants; in conflict between a petty actor such as a community advocate and the junior members of the state, the state must support its own, while internally ensuring that the proposal has technical merit. (Political merit is judged by elections, not by who screams the most loudly at midday community meetings.)
Civil servants who see that their superiors are hired and promoted from within the ranks or among peers, and judged for their ability to work with those below them and not just those above them (in the tech industry, a managerial hire spends some interview time with the team they are to supervise), will soon learn that they can show initiative. The ones with bad intuition will fail, whereas the ones whose initiative is more successful will be able to rise and transmit their ideas to the group. It goes without saying that this also requires staffing up to normal levels and paying competitive wages. This way, the state can ensure it can oversee its own projects competently; there is no alternative.
Institutional Issues: Procurement
This is the start of a multi-post series, of undecided length, focusing on institutional, managerial, and sociopolitical issues that govern the quality of infrastructure. I expect much of the content to also appear in our upcoming construction costs report, with more examples, but this is a collation of the issues that I think are most pertinent at the current state of our work.
Moreover, in this and many posts in the series, the issues covered affect both price and quality. These are not in conflict: the same institutions that produce low construction costs also produce rigorous quality of infrastructure. The tradeoffs between cost and quality are elsewhere, in some (not all) aspects of engineering and planning.
The common theme of much (but not all) of this runs through procurement. It’s not as exciting as engineering or architecture or timetables – how many railfans write contracts and contracting regulations for fun? – but it’s fundamental to a large fraction of the difference in construction costs between different countries. Some of the subheadings in this post deserve full treatments by themselves later, and thus this writeup is best viewed as an introductory overview of how things tie together.
What is procurement?
Procurement covers all issues of how the state contracts with providers of goods and services. In the case of public transportation, these goods and services may include consulting services, planning, design, engineering, construction services, equipment, materials, and operating concessions. The providers are almost always private-sector, but they can also be public companies in some cases – for example, Milan Metro provides consulting services for other Italian cities and Delhi Metro does for other Indian ones, and state-owned companies like RATP, SNCF/Keolis, and DB/Arriva sometimes bid on private contracts abroad.
The contracting process can be efficient, or it can introduce inefficiencies into the system. In the worst case I know of, that of New York, procurement problems alone can double the cost of a contract, independently of any other issue of engineering, utilities, labor, or management quality. In contrast, low-cost examples lack any such inefficiencies in construction.
The issue of oversight
On the list of services that are procured, some are more commonly contracted out than others. Construction is as far as I can tell always bid out to private-sector competition, including equipment (nobody makes their own trains), materials, and physical construction. Design and engineering may be contracted out to consultants, depending on the system. Planning never is anywhere I know of, except some unusually high-cost American examples in which public-sector planning has been hollowed out.
The best practice from Southern Europe as well as Scandinavia is that planning and oversight always stay with the public sector. Even with highly privatized contracts, there’s active in-house oversight over the entire process.
The issue of competition
It is necessary to ensure there’s healthy competition between contractors. This requires casting as wide a net as possible. This is easier to do in environments where there is already extensive private- and public-sector construction going on: Turkey builds about 1 million dwellings a year and many bridges, highways, and rail lines, and therefore has a thick domestic market. In Turkish law, it is required that every public megaproject procurement get at least three distinct bids, or else it must be rebid. This rule is generally easy to satisfy in the domestic market.
But if the domestic market is not enough, it is necessary to go elsewhere. This is fine – foreign bidders are common where they are allowed to participate, always with local oversight. Turkish contractors in Northern Europe are increasingly common, following all of the local labor laws, often partnering with a domestic firm.
Old boy networks, in which contractors are required to have a preexisting relationship with the client, are destructive. They lead to groupthink and stagnation. A Turkish contractor held an Android in front of me and, describing work in Sweden, said, “If a Swede said it’s an iPhone, the Swedes would accept that it’s an iPhone, but if I did, they’d check, and see it’s an Android.” In Sweden at least the domestic system is functional, but in a high-cost environment, it is critical to look elsewhere and let foreigners outcompete domestic business.
It is even more important to make sure the experience of bidding on public contracts is positive. A competent contractor has a choice of clients, and a nightmare client will soon lose its business. Such a loss is triple. First, the contractor would have done a good job at an affordable price. Second, the negative experience, such as micromanagement or stalling, is likely to increase costs and reduce the quality of work. And third, the loss of any contractor reduces competition. In the United States, we have repeatedly heard this complaint from contractors and their representatives, that they always have to deal with the “agency factor,” where the agency can be the MTA or any other transit agency, making things difficult and leading to higher bids.
Good client-contractor relations
The issue of avoiding being a nightmare client deserves special scrutiny. It is critical for agencies to make sure to be pleasant clients. This includes any of the following principles:
- Do not change important regulations midway through the project. In Stockholm, the otherwise-good Nya Tunnelbana project has had cost overruns due to new environmental regulations that required disposal of waste rock to the standards of toxic waste, introducing new costs of transportation.
- Avoid difficult change order process (see below for more details on itemization). It should be everyone against the project, not the agency against the contractors or one contractor against another.
- Avoid any weird process or requirements. The RFPs should look like what successful international contractors are used to; this has been a recent problem of American rolling stock procurement, which has excessively long RFPs defining what a train is, rather than the most standard documents used in Europe. This rule is especially important for peripheral markets, such as the entire United States – the contractor knows what they’re doing better than you, so you should adapt to them.
- Require some experience and track record to evaluate a bid, but do not require local experience. A contractor with extensive foreign experience may still be valuable: Israel’s rail electrification went to such a contractor, SEMI, and the results are positive in the sense that the bid was well below expectations and the only problems stem from a nuisance lawsuit launched by a competitor that bid higher and felt entitled to the contract.
- For a complex contract, the best practice here is to have an in-house team score every proposal for technical merit and make that the primary determinant of the final score, not cost. Across most of the low- and medium-cost examples we have looked at, the technical score is 50-70% of the total and cost 30-50%.
- Do not micromanage. New York’s lowest bid rules lead to a thick book of regulations that force the bids to be as similar to one another as possible in quantity and type of goods, to the point of telling contractors what materials they are allowed to use. This is bad practice. Oversight should always be done with flexibility and competent in-house engineers working in conversation with the stakeholders and never with a long checklist of rules.
Flexibility
Contracts should permit as much flexibility as practical, to allow contractors to take advantage of circumstances for everyone’s benefits and get around problems. This is especially important for underground construction and for construction in a constrained city, where geotechnical surprises are inevitable.
Most of the English-speaking world, and some parts of the rest (Copenhagen, to some extent Grand Paris Express) interpret flexibility to mean design-build (DB) contracts, in which the same firm is given a large contract to both design a project and then build it. However, DB is not used in the lowest-cost examples I know of, and rarely in medium-cost ones. If design is contracted out, then there are almost always two contracts, in what is called design-bid-build (DBB). Sources in Sweden say they use single build contracts, but they often use consultants for supplementary engineering and thus they are in practice DBB; Italy is DBB; Turkish sources claim to do design-build, but in reality there are two contracts, one for 60% design and another for going to 100% and then doing construction.
The Turkish system is a good example of how to ensure flexibility. Because the construction contractor is responsible for the finalized (but not most) design, it is possible to make little changes as needed based on market or in-the-ground conditions. In Italy and Spain, the DBB system is traditional, but the building contractor is allowed to propose changes and the in-house oversight team will generally approve them; this is also how the more functional American DBB contracts work, typically for small projects such as individual train stations, which are within the oversight capacity of the existing in-house teams.
DBB can be done inflexibly – that is, wrong – and often when this happens, everyone gets a bitter taste and comes out with the impression that DB is superior. If the building contractor has to go through onerous process to vary from the design, or is excessively incentivized to follow the design to the letter, then problems will occur.
One example of inflexibility comes from Norway. Norwegian construction costs are generally low, but the Fornebu Line’s cost is around $200 million/km, which is not as low as some other Nordic lines. Norway uses DBB, but its liability system incentivizes rigidly adhering to the design: any defect in the construction is deemed to be the designer’s fault if the builder followed the design exactly but the builder’s fault if the builder made any variation. This means small changes do not occur, and then the design consultants engage in defensive design, rather than letting the building contractor see later what risks are likely based on meter-scale geology.
Itemization and change orders
Change orders, and defensive design therefor, are a huge source of cost overruns and acrimony. Moreover, because of the risks involved, any cost overruns are transmitted back into the overall budget – that is, every attempt to clamp down on overruns will just increase absolute costs, as bidders demand more money in risk compensation. California is infamous for the way change orders drive up costs. New York only avoids that by imposing large and growing risk on the bidders (including, recently, a counterproductive blacklisting system called disbarment, a misplaced effort by Andrew Cuomo to rein in cost overruns); the bidders respond by bidding much higher.
Instead of the above morass, contracts should be itemized rather than lump-sum. The costs of materials are determined by the global, national, and local markets, and the contractor has little control over them; in fact, one of the examples an American source gave me of functional change orders in a DBB system is that the bench at a train station can be made of wood, metal, or another material, depending on what costs the least when physical construction happens.
Labor costs depend on large-scale factors as well, including market conditions and union agreements. The use of union labor ensures that the wages and benefits of the workers are known in advance and therefore unit costs can be written into the contract easily. Spain essentially turns contracts into cost-plus: costs depend on items as bid and as required by inevitable changes, and there is a fixed profit rate based on a large amount of competition between different construction firms.
The upshot is that itemized costs prevent the need to individually negotiate changes. If difficult ground conditions or unexpected utilities slow down the work, the wages of the workers during the longer construction period are already known. It is especially important to avoid litigation and the threat thereof – questions of engineering should be resolved by engineers, not lawyers.
Here, our results, based on qualitative interviews with industry experts, mirror some quantitative work in economics, including Ryan and Bolotnyy-Vasserman. Itemization reduces risk because it pre-decides some of the disputes that may arise, and therefore the required profit rate to break even net of risk is lower, reducing overall cost.
The impact of bad procurement practices
One of our sources told us that procurement problems add up to a factor of 2 increase in New York construction costs. Five specific problems of roughly equal magnitude were identified:
- A regulation for minority- and woman-owned businesses (MWB), which none of the pre-qualified contractors in the old boy network is.
- The MTA factor.
- Change order risk.
- Disbarment risk.
- Profit in a low-competition environment.
MWB and disbarment are New York-specific, but the other three appear US-wide. In California, the change order risk is if anything worse, judging by routine cost overruns coming from change orders. California, moreover, is very rigid whenever a contractor suggests design improvements, as Dragados did for its share of California High-Speed Rail, even while giving contracts to contractors that engage in nuisance change orders like Tutor Perini.
Aligning American procurement practice with best practice is therefore likely to halve construction costs across the board, and substantially reduce equipment costs due to better competition and easier contractor-client relations.
The TransitMatters Rail Electrification Report
At TransitMatters, we’ve just released a report about the costs and benefits of rail electrification. It’s anchored to our proposal to electrify and modernize the commuter rail system in the Boston area, but much of the analysis is broader than that. The non-Bostonian reader may still be interested in the description of construction costs of electrification and the short case studies of Israel, Denmark, Norway, New Zealand, Britain, Canada, and the United States. The latter two, covering Toronto and the Bay Area, are unusually expensive and we go over why that came to be and how it is possible to avoid them. The section on alternatives and why they are all inferior to stringing wire and running EMUs is of general interest as well, and I hope European policymakers read over and take it as a sign they should electrify more lines (ideally, all of them, as is being done right now in South Korea, India, and China).
The Toronto problem
When we came up with the cost range of $800 million to $1.5 billion, there was a lot of skepticism. The Reddit thread‘s two most common kinds of comment are “great, this can’t happen fast enough” and “it will cost billions because of unspecified MBTA problems.” As I said in responding to one of the comments, the higher-cost comparison cases all have specific reasons for their higher costs: Britain has clearance restrictions that do not exist anywhere else in the world, and Caltrain had unusual managerial incompetence regarding the related signaling project where the MBTA is actually doing well. But Toronto still looms large.
As I said on Reddit,
I’m not too worried about Caltrain’s errors, which were truly bespoke. Toronto worries me more, because while the specifics are avoidable, the ultimate cause is reproduced: Toronto and Boston are both huge cities with heavy peak commuter rail traffic and should have electrified generations ago, so now the benefits of electrification are so high that managers can afford to be careless about costs and still have above-water benefit-cost ratios.
So it is important to be careful and avoid Toronto’s problems with cost control. This means baking cost control into the program from the start, and aggressively protecting the budget from use by other actors as OPM:
- The budget should be set at a standard level with standard contingencies. Do not aim for the ceiling; aim for average. Nor should anyone include 100% contingency as used by Toronto; if you budget money for the project it will be used, so optimize for minimizing overall cost rather than for just-in-case funding.
- Designs should be standard, and variations should be accommodated only based on cost minimization. Basically, if it’s good enough for Germany, France, Denmark, Norway, Israel, etc.,, it’s good enough for the United States.
- If NIMBYs push back, the state should fight back. They want noise walls? Nope, EMUs are a lot quieter than diesels, quality of life will improve. They want trenches? Nope, that’s too expensive.
- Under no circumstances should passenger rail electrification money be used for corporate welfare for freight rail companies. They can pay their own way for clearance for double-stacked containers.
The importance of maximum electrification
Based on the observations that the lifecycle costs of DMUs are about twice those of EMUs, and that operating and capital costs are both driven by the peak rather than off-peak, it’s possible to establish financial rates of return on electrification. Not counting the speed and reliability benefits to passengers, the ROI is around 0.3-0.5% per US-size car per hour at the peak. Lines that run 8-car trains every 15 minutes at rush hour run 32 cars per hour and so have an ROI of 10-16%; this is why outside the US and Canada, cities that run such long trains at such frequency have long electrified their tracks.
The problem is that electrification is relatively unfamiliar in North America. It exists, but is sporadic, and there have been very few recent projects, so managers think it’s a Herculean task. In Boston I’ve seen reticence to wire more track due to institutional conservatism, even in plans that spend comparable amounts of money on things the region is more used to, like station platform upgrades and extra tracks. Worse, I’ve seen this in New Jersey, which is largely already electrified but uninterested in finishing the job.
Against such conservatism, it’s important to remember that failure to undertake a high-value investment isn’t any more moral than a large investment that goes to waste. When your ROI hits double digits, you waste public benefits by avoiding or even just delaying the project – and the above calculation comes just from savings on operating, maintenance, and capital acquisition costs, without the large benefits to passengers, the environment, etc.
Can large cities afford not to electrify? Yes. They have money for many kinds of waste, including for forgoing the benefits of commuter rail electrification. But just because they can afford to waste money and social benefits doesn’t mean they should. So, please, no talk of DMUs, or bi-modes, or pilot programs, or batteries – just wire your system already and import some high-quality EMUs.
Good Practices for State Planning and Local Public Transportation
Earlier this week, I complained about the OPM (other people’s money) problem: federal funding of American public transportation, which is managed locally, leads to cost-raising behavior as local and state governments seek to maximize federal infusion of cash. This is a companion post about more positive and fruitful interactions of government at different levels on this side of the Pond. The examples here often look pointless or acrimonious by local standards, but at the end of the day, they produce cost-effective infrastructure and are positive examples to learn from.
Of note, all the examples below are from unitary, not federal states. This is just an artifact of where I have talked to the most people about this – from what I know of Germany, Austria, Switzerland, and Belgium, they all fall within the spectrum spanned by Italy, Turkey, France, and Sweden when it comes to state-local funding allocation. Moreover, the extent of subnational fiscal autonomy in Germany is not greater than that of Sweden, where there are extensive county and municipal taxes funding subnational government, whereas in Germany nearly all taxes are federal and the Länder mostly rely on transfers.
This is a theme I’ve been investigating ever since I talked to a planner at DOTr. Philippine construction costs are high, although that’s mainly for subways, while elevated lines have fairly average costs. The planner explained to me how planning and procurement are done and specifically how it contrasts with the role of the federal government in the US. Manila Metro projects are planned and designed by DOTr, and ever since that conversation I’ve learned to interpret interviews with European experts in that light.
Sweden: state-local negotiation
The Nordic states practice consensus government. This means that decisions are done by majority vote without veto points, but also there’s no such thing as a majority. In practice, infrastructure involves negotiations between different stakeholders. Bigger projects, including the subway megaprojects we study, require funding from different sources, creating more stakeholders in the process.
In the case of Stockholm, it’s instructive to compare Citybanan and Nya Tunnelbanan. Citybanan is a regional rail tunnel, and therefore the lead agency was the state’s Trafikverket – but even then, Stockholm County had extensive input. Regions send wishlists to the state, and compete for a fixed pot of funding for grants, but there are further negotiations about project details. Nya Tunnelbanan is a subway project led by the county’s SL, but funding comes 25% from local sources, 25% from the county, and 50% from the state.
Crucially, Trafikverket builds rather than just nudges. It has a strong professional civil service capable of designing and supervising the construction of infrastructure megaprojects – and the same pool of civil servants move between agencies within the Swedish public sector, so that some of the people I’ve spoken to have moved between Trafikverket and SL. The example planners I have in mind are mid-level, not top management – this is not a case of a mobile executive suite lording over mid- and low-level career bureaucrats who can’t move between agencies easily.
There is also integration of transport and housing, in the sense that residential upzoning in Stockholm County focuses on areas that have or will soon have urban rail access. Construction rates in Stockholm County are some of the highest in Europe: per SCB, annual completions were around 6.5-7 per 1,000 people in the five years before corona. I’ve been told that it’s a consensual process, with no further elaboration; in Oslo, in contrast, the state has to compel wealthy NIMBY municipalities to upzone as a precondition of giving them subway expansion, but state-local coordination is as far as I can tell otherwise similar to the situation in Stockholm.
Turkey: state-local competition, but no OPM
Turkey has one of the world’s lowest construction cost levels; more details will be available in a report to appear soon, led by Elif Ensari. Wages in Turkey are low by European standards and social protections are weak, but the direct labor share of subway construction is small enough that it is a secondary contributor to the low costs; Turkey dos some things more efficiently than Sweden and others less efficiently.
The situation of state-local relations there is the exact opposite of Sweden’s. There is no collaboration – rather, there are metro tunnels in Istanbul funded and built by the state and others funded and built by the city.
The city is not quite local – the municipality covers the entire metropolitan area of 15.5 million people, and Istanbul politics has an ideological left (i.e. anti-Erdoğan) vs. right (i.e. pro-Erdoğan) characteristic rather than the hyperlocal ties of New York and other American cities. Moreover, now that AKP lost the municipal election and the mayor is CHP’s Ekrem İmamoğlu, who will likely challenge Erdoğan in the 2023 presidential election, there is friction between the state and the city, each trying to argue that it builds more and better infrastructure. There are arguments between pro- and anti-Erdoğan sources over who is to blame, but the city has much less access to state financing now than before İmamoğlu’s victory, which it has been able to replace with financing from the European Investment Bank and other sources of loans, like JICA and Deutsche Bank.
In this situation, there is no coordination, and this is a drag on efficiency – one of the ways Istanbul has been able to keep costs down is finding parks and state land to use for station footprint to keep station construction costs down. However, because there is direct responsibility for the state or the city for infrastructure, there is no OPM problem – İmamoğlu’s political career depends in part on his ability to build infrastructure, and Erdoğan’s ability to interfere is real but limited.
Housing construction is extremely rapid. Istanbul has a housing surplus thanks to the construction of around 160,000 annual housing units; neighborhood character is not a priority there. But I do not know whether it is integrated with subway construction as in Sweden.
France: the capital is the state
France has a convoluted set of local and regional governing mechanisms. However, in Paris, much of the power remains in state and state-appointed organs. The transport association Ile-de-France Mobilités, which would be called a Verkehrsverbund in Germany, is coordinated by the Ile-de-France region, but its two largest components, SNCF and RATP, are both state-owned (though SNCF-RATP agency turf battles remain). Public services that elsewhere in France might be devolved are in Paris often run by the state – for example, the Paris Police Prefecture is part of the National Police, and it’s smaller cities, for example in the Riviera, that have local police departments.
This is not unique to France. In infrastructure, Sweden too exhibits more state involvement in urban rail planning in the capital than in smaller cities – Västlänken in Gothenburg is a Trafikverket project but more of the planning and funding come from the county than was the case for Citybanan. London is a mix: TfL is run by the mayor, offering much more devolution than the Metropolitan Counties of England have, but conversely the construction of infrastructure megaprojects like Crossrail is really within the purview of UK-wide politics.
The issue here is one of scale. Grand Paris Express is a 200 km, 80% tunneled project, and France is a medium- rather than low-cost country. Even the state barely has enough planning capacity for it – the Cour des Comptes report on the cost overruns, not seen before for smaller Métro extensions, blamed the insufficient size of existing planning organs, but unfortunately, the solution arrived at, the special-purpose delivery vehicle (SPDV) GPE, is not good, and is either in imitation of or evolved toward convergence with Crossrail. Nothing below the level of the state could build such a project.
And because the project is so large, it’s been forced into a situation that rhymes with Sweden’s intergovernmental negotiation. It’s also been discussed as part of national politics, with some redesigns stemming from the Sarkozy-Hollande transition. In some cases, this has led to OPM – namely, M18 is unpopular among the region’s public transportation advocates and remains because of pressure by the high-income suburbs it would serve. However, there is no visible impact on unit costs; it’s notable that the OPM the state would dispense is additional infrastructure at per-rider costs that are high for France but common in the United States, rather than extras of little use like signature stations or more expensive construction methods.
Finally, housing construction in Ile-de-France is, as in Stockholm County, among the YIMBYest in Europe. Yonah Freemark’s paper on the subject is indispensable: stating around 2017, the annual construction rate rose to 80,000 units regionwide, around 6.5/1,000 people. Construction is largely in the Petite Couronne suburbs, and not the city, and focuses on regions with current or future urban rail extensions, as in Stockholm.
Italy: state planning and austerity
A full report on Italy will appear soon, on a similar timeline as Turkey, written by Marco Chitti. In Italy, there has been a transition from municipal funding and planning of metros to state funding; in Rome, there was always more state involvement as I understand it.
The situation leading up to the Financial Crisis had similarities with the United States: state funding, municipal or regional responsibility for construction. However, the state always exercised far more oversight. The Italian state builds rather than just nudging. State regulation is done through administrative rather than judicial mechanisms, and thus questions of environmental and historical protection are decided by civil servants trained in engineering, archeology, history, and ecology; there are clear rules, providing similar final outcomes to the Nordic process of negotiation and superior ones to the American process of lawsuit.
More recently, the state has devolved some of the funding to regional, provincial, and municipal governance. This was an artifact of post-Crisis austerity, so the state would fund the majority (I believe 70%) of each project’s budget but not all of it. The result has not been positive – subnational governments have no money, not even wealthy ones like Milan, and to fill in for missing state funding they’ve resorted to PPP financing, which has not impacted construction costs but in effect required hidden loans at high interest bonded to future revenue.
Mixing High- and Low-Speed Trains
I stream on Twitch (almost) every week on Saturdays – the topic starting now is fare systems. Two weeks ago, I streamed about the topic of how to mix high-speed rail and regional rail together, and unfortunately there were technical problems that wrecked the recording and therefore I did not upload the video to YouTube as I usually do. Instead, I’d like to write down how to do this. The most obvious use case for such a blending is the Northeast Corridor, but there are others.
The good news is that good high-speed rail and good legacy rail are complements, rather than competing priorities. They look like competing priorities because, as a matter of national tradition of intercity rail, Japan and France are bad at low-speed rail outside the largest cities (and China is bad even in the largest cities) and Germany is bad at high-speed rail, so it looks like one or the other. But in reality, a strong high-speed rail network means that distinguished nodes with high-speed rail stations become natural points of convergence of the rail network, and those can then be set up as low-speed rail connection nodes.
Where there is more conflict is on two-track lines with demand for both regional and intercity rail. Scheduling trains of different speeds on the same pair of tracks is dicey, but still possible given commitment to integration of schedule, rolling stock, and timetable. The compromises required are smaller than the cost of fully four-tracking a line that does not need so much capacity.
Complementarity
Whenever a high-speed line runs separately from a legacy line, they are complements. This occurs on four-track lines, on lines with separate high-speed tracks running parallel to the legacy route, and at junctions where the legacy lines serve different directions or destinations. In all cases, network effects provide complementarity.
As a toy model, let’s look at Providence Station – but not at the issue of shared track on the Northeast Corridor. Providence has a rail link not just along the Northeast Corridor but also to the northwest, to Woonsocket, with light track sharing with the mainline. Providence-Woonsocket is 25 km, which is well within S-Bahn range in a larger city, but Providence is small enough that this needs to be thought of as scheduled regional rail. A Providence-Woonsocket regional link is stronger in the presence of high-speed rail, because then Woonsocket residents can commute to Boston with a change in Providence, and travel to New York in around 2 hours also with a change in Providence.
More New England examples can be found with Northeast Corridor tie-ins – see this post, with map reproduced below:

The map hides the most important complement: New Haven-Hartford-Springfield is a low-speed intercity line, and the initial implementation of high-speed rail on the Northeast Corridor should leave it as such, with high-speed upgrades later. This is likely also the case for Boston-Springfield – the only reason it might be worthwhile going straight from nothing to high-speed rail is if negotiations with freight track owner CSX get too difficult or if for another reason Massachusetts can’t electrify the tracks at reasonable cost and run fast regional trains.
There’s also complementarity with lines that are parallel to the Northeast Corridor, like the current route east of New Haven, which the route depicted in the map bypasses. This route serves Southeast Connecticut communities like Old Saybrook and can efficiently ferry passengers to New Haven for onward connections.
In all of these cases, there is something special: Woonsocket-Boston is a semireasonable commute, New London connects to the Mohegan Sun casino complex, New Haven-Hartford and Boston-Springfield are strong intercity corridors by themselves, Cape Cod is a weekend getaway destination. That’s fine. Passenger rail is not a commodity – something special almost always comes up.
But in all cases, network effects mean that the intercity line makes the regional lines stronger and vice versa. The relative strength of these two effects varies; in the Northeast, the intercity line is dominant because New York is big and off-mainline destinations like Woonsocket and Mohegan are not. But the complementarity is always there. The upshot is that in an environment with a strong regional low-speed network and not much high-speed rail, like Germany, introducing high-speed rail makes the legacy network stronger; in one that is the opposite, like France, introducing a regional takt converging on a city center TGV station would likewise strengthen the network.
Competition for track space
Blending high- and low-speed rail gets more complicated if they need to use the same tracks. Sometimes, only two tracks are available for trains of mixed speeds.
In that case, there are three ways to reduce conflict:
- Shorten the mixed segment
- Speed up the slow trains
- Slow down the fast trains
Shortening the mixed segment means choosing a route that reduces conflict. Sometimes, the conflict comes pre-shortened: if many lines converge on the same city center approach, then there is a short shared segment, which introduces route planning headaches but not big ones. In other cases, there may be a choice:
- In Boston, the Franklin Line can enter city center via the Northeast Corridor (locally called Southwest Corridor) or via the Fairmount Line; the choice between the two routes is close based on purely regional considerations, but the presence of high-speed rail tilts it toward Fairmount, to clear space for intercity trains.
- In New York, there are two routes from New Rochelle to Manhattan. Most commuter trains should use the route intercity trains don’t, which is the Grand Central route; the only commuter trains running on Penn Station Access should be local ones providing service in the Bronx.
- In the Bay Area, high-speed rail can center from the south via Pacheco Pass or from the east via Altamont Pass. The point made by Clem Tillier and Richard Mlynarik is that Pacheco Pass involves 80 km of track sharing compared with only 42 km for Altamont and therefore it requires more four-tracking at higher cost.
Speeding up the slow trains means investing in speed upgrades for them. This includes electrification where it’s absent: Boston-Providence currently takes 1:10 and could take 0:47 with electrification, high platforms, and 21st-century equipment, which compares with a present-day Amtrak schedule of 0:35 without padding and 0:45 with. Today, mixing 1:10 and 0:35 requires holding trains for an overtake at Attleboro, where four tracks are already present, even though the frequency is worse than hourly. In a high-speed rail future, 0:47 and 0:22 can mix with two overtakes every 15 minutes, since the speed difference is reduced even with the increase in intercity rail speed – and I will defend the 10-year-old timetable in the link.
If overtakes are present, then it’s desirable to decrease the speed difference on shared segments but then increase it during the overtake: ideally the speed difference on an overtake is such that the fast train goes from being just behind the slow train to just ahead of it. If the overtake is a single station, this means holding the slow train. But if the overtake is a short bypass of a slow segment, this means adding stops to the slow train to slow it down even further, to facilitate the overtake.
A good example of this principle is at the New York/Connecticut border, one of the slowest segments of the Northeast Corridor today. A bypass along I-95 is desirable, even at a speed of 200-230 km/h, because the legacy line is too curvy there. This bypass should also function as an overtake between intercity trains and express commuter trains, on a line that today has four tracks and three speed classes (those two and local commuter trains). To facilitate the overtake, the slow trains (that is, the express commuter trains – the locals run on separate track throughout) should be slowed further by being made to make more stops, and thus all Metro-North trains, even the express trains, should stop at Greenwich and perhaps also Port Chester. The choice of these stops is deliberate: Greenwich is one of the busiest stops on the line, especially for reverse-commuters; Port Chester does not have as many jobs nearby but has a historic town center that could see more traffic.
Slowing down the intercity trains is also a possibility. But it should not be seen as the default, only as one of three options. Speed deterioration coming from such blending in a serious problem, and is one reason why the compromises made for California High-Speed Rail are slowing down the trip time from the originally promised 2:40 for Los Angeles-San Francisco to 3:15 according to one of the planners working on the project who spoke to me about it privately.
What’s Frustrating About Bus Redesigns
The transit vlogger Alexandra Rose said something deeply disturbing and yet true on Twitter:
More and more I think that bus network redesigns are too often just managed decline. I was really into zero cost change redesigns a few years ago, less so recently. Literally shuffling deck chairs.
The issue isn’t that net zero cost redesigns are bad. They’re not. The results in recent years look pretty good; Nova Xarxa really did lead to ridership growth, the American redesigns were for the most part helpful too, and I stand by the claim in our report, on pp. 36-37, that the Brooklyn bus redesign we propose would raise ridership 20%.
And yet, Alexandra is completely right, because 20% of zero is still zero. Even in New York, what we call would only get New York bus ridership back to where it was on the eve of the Great Recession and the ensuing service cuts. This really concerns two separate problems of bus service and systemwide changes.
Bus decline management
Managing the decline of buses is inevitable. Buses are too labor-intensive in a developed country to remain a cost-effective solution in the long run – and the sort of cities in the first world with both the best public transit and the best prospects for growth also tend to have the highest wages. Bus drivers in New York earn $85,000/year, and that’s market-rate – there aren’t hordes of unemployed people clamoring to work as bus drivers; agencies that pay significantly less relative to local wages, like San Francisco’s Muni, find it hard to recruit drivers.
How labor-intensive are buses? Well, in New York there are around 12,000 bus drivers and 4,000 subway drivers. Subway ridership was 2.5 times bus ridership in 2019, and overall vehicle-hours, counting cars rather than trains, were 60% longer, with subway cars still substantially bigger than buses. And there’s a lot more inefficiency in crew scheduling on the subway than on the bus network – and today it’s possible to automate subways but not buses. A subway train today carries as many passengers as 17 buses on average, and is 2.5 times faster, for an overall labor efficiency factor of 44.5, without automation; it’s in practice less than this taking crew inefficiencies and maintenance into account, but remains well over a full order of magnitude.
The upshot is that the sort of service-hours that could be run with the wages of 60 years ago stopped being financially sustainable 40 years ago, and the service-hours of 20 years ago are not financially sustainable today. Net zero redesigns are about the best that is possible – because service-hours are expensive and getting more so over time.
All of these bus reforms – network redesigns, dedicated lanes, bus shelter, real-time information, signal priority – push back the decline, but they do not halt it. Eventually, something other than labor-intensive buses will be required, most likely some kind of light rail and subway combination as with the railstitutions happening here in Berlin or in Paris.
Compounding growth factors
A 20% increase in systemwide ridership is great! But, 20% of zero is still zero, and 20% of a low number is in absolute terms low growth. The question is what comes next.
If a city builds a subway line and gets noticeable ridership growth, it can compound. The one subway line succeeded, so now it can built more to new areas, not served by this line. Large increases in systemwide ridership can come from a project that is not systemwide, and then in a large city it’s easy enough to add more such projects. This is not mere linear growth as new lines open – a city that builds a subway system automatically makes city center an attractive place for business, leading to naturally-occurring transit-oriented development. It is natural for public transport advocates to be optimistic in such a situation.
Systemwide improvements compound with everything else, but are frustrating one-time affairs. Yes, a redesign can raise ridership 20% – and then what? Our Brooklyn proposal is aggressive – more so than Nova Xarxa, which included a pre-agreed number of routes with dedicated lanes, I believe 12, but nothing like the proposal we made that every route except for a handful in low-traffic areas on the edge of the borough get two-way dedicated lanes.
The only big thing our proposal didn’t touch on is bus shelter, because we didn’t realize how important it is. But bus shelter interacts negatively with interventions that increase bus frequency, since its effect is to reduce the disutility of waiting for the bus, and if the wait has already been reduced to 5-6 minutes then shelter is useful but its impact is not the 30% increase in ridership that my bus shelter post posits. Other than shelter, there’s conditional signal priority making buses less likely to bunch, but it too interacts negatively with everything else, and the speed benefits (as opposed to the more speculative reliability benefits) of signal priority are known and small.
Is it worthless?
No! Just frustrating. Bus upgrades are a one-time thing, holding back the long-term decline of the mode as better alternatives emerge. These ridership increases are nothing to sneeze at, but there’s no alternative to transitioning to rapid transit, maybe with trams as a feeder layer (or as the primary one if you’re a sub-million metro), with enough transit-oriented development that people can just walk to the subway. Everything else can b fine in the short run, but in a wealthy city that run is short indeed.