No, Let’s Not “Uber” Our Bus System

Have you just read another article claiming that public transit would be better off if we unleashed private innovation?  Ask whether they're talking about privatized operations or privatized planning.  These are totally different things, but it's currently fashionable to confuse them.

Graduate student August Ruhnka, writing in the Denver Post, is the latest in a series.  After reviewing the real cost and quality control issues plaguing US bus systems, he goes on to propose a fatal confusion between privatization of operations and privatization of planning.

The remedy is simple. The city awards a route bus contract after a competitive bidding process, thus entering into a private/public partnership.

So far so good.  This is the standard model of privatized operation.  But then, OMG:

By privatizing our bus system's day-to-day operations while still providing public oversight, private operators will be able to change routes, schedules and fares as frequently as necessary without the need for lengthy public hearings and political approval.

"Change routes, schedules, and fares?"  This is the privatization of planning.  It features the abolition of "political approval," which is a polite term for the abolition of democratic controls over spending the public purse.   It's also produced some of the worst bus systems — in terms of both disutility and waste — that I've ever encountered in 23 years doing network planning.  Ruhnka goes on:

Today, successful privately operated transit projects like the Sydney Metropolitan Bus System, Hudson-Bergen Line in New Jersey and the JFK Air Train in New York are chugging away.

Only one of these examples is even a bus service, where route changes are an issue, and none of them are examples of the privatization of planning that Rohnka proposes.   They are all examples of privatized operations.  

The Sydney example is more apt than Rohnka knows.  Planning was controlled by private operating companies over much of Australia and New Zealand when I started working there in 2006.  Now, all over both countries, planning is being moved back into the public sector, while operations remain private. That's happening, in part, because transit planning by operating companies produced fantastically inefficient bus systems such as the one in Auckland, New Zealand, which I have been helping the new Auckland Transport to redesign.  

The problem was not just privatization but turf.  Private companies who control just certain bus routes may optimize their own bus routes, but that doesn't optimize the whole taxpayer funded network and can in fact make it worse.  (The same problem can afflict turf-bound governments, of course, but turning them over to the private sector does nothing to solve that problem, while it does remove our ability to hold elected officials accountable for it.)

In cities across the world, major bus corridors are becoming important redevelopment areas.  Bus service has a huge nexus with a range of important government activities, notably road design and land use planning.  To give up control over the design of bus services is to give up control that's needed to do those jobs well.

Public hearings are a drag, and the approval process for bus service changes in America is exhausting for both elected officials and the public.  Preparing for this process is central to every project I do.  My job is to help elected officials (or their appointees) make clear decisions about the real tradeoffs that transit planning requires.  These are hard choices that must reflect a city's ambitions and values, and that must be linked to a city's decisions about land use, urban form, and social policy.

All these thoughts are supposed to give way, of course, to the romantic idea that we could "Uber" our bus system.  

In light of our Uber-dominated downtown, it is time for us to make this switch. Private-route contracts establish a sustainable procedure to constantly test the market to achieve the lowest cost. Commuting in downtown Denver requires three things that currently RTD lacks: demand-response (paratransit) operation; experimental services; and remedying routes that have low ridership. All the above situations require a level of flexibility that the private sector can provide.

Uber is big and new and financed and sexy, so how could this not be better than our old bus services?   (A dismissive view of  "political approval," too, is part of the Uber mystique.)

Uber today is a taxi and (limited) shared ride service using small vehicles to carry small numbers of people at once.   Assuming you pay the driver decently (a big assumption in the private sector) the cost-effectiveness of transit is going to lie in passengers per driver, because pending driverless vehicles, the driver is most of the cost.  And the only way to get that number high is to run large vehicles in fixed-route services that are so well designed, and optimized over so many purposes, that lots of people ride them.   The Uber model does not scale to large-vehicle fixed-route transit, which is also known as cost-effective transit.  

Why, then, does downtown Denver require "demand-responsive operation"?  Downtowns are big, dense, and need to use street space efficiently, so large vehicles are the key.  Compared to big buses with decent ridership, demand-responsive service is a way of carrying very few people at a high cost.    There is no way that a demand-responsive solution, in a place where fixed routes could work just as well, makes any sense as a way to make transit affordable to low-income people, one of Ruhnka's alleged concerns.  Affordability is scalability.  If a solution doesn't scale efficiently — in terms of labor cost, energy, and urban space, it will naturally be expensive.  

So to the extent that some people think they need a demand-responsive service downtown (apart from paratransit for the disabled) by all means let Uber and Lyft do that.  Demand-responsive is such an intrinsically inefficient form of transit that deploying it downtown can only be for the purpose of serving relatively fortunate people at fares much higher than transit fares.  That's a great role for the private sector.  There is also a role for demand responsive service in suburban areas where development patterns preclude efficient transit, through contracts between demand responsive providers and transit agencies.  But not downtown.

Another way of describing all of the "demand responsive" or "Uberization" fantasies is that they are predicated on moving large amounts of steel and rubber per customer trip, compared to big-vehicle fixed-route transit.  Even without considering the economics of labor, this can only be less efficient, in terms of energy and urban space, then what crowded big-vehicle transit achieves.  (And yes, you've probably read that a lot of big buses run around empty, as though this means that buses are a poor tool.  The refutation of that argument is here, and here.)

Transit is full of opportunities for private sector involvement, including in operations, infrastructure, and my own job, professional advice.  The private sector is always welcome to innovate, and there are markets — generally for higher-end services and higher fares — that the private sector will probably take over.  There are also fascinating opportunities to use Uber/Lyft models to improve the efficiency of services to low-demand areas — that will require partnership with suburban communities or transit agencies.

But privatize planning?  Let private companies re-arrange transit services without regard to the impact on the city and its values?  That's the opposite of democracy.

Quote of the week: bike-bus conflicts

On the inevitable problem of curb bike lanes interacting with bus stops:

Generally, transit advocates are also bike advocates, but with regular on-street bike lanes, this conflict point becomes an unavoidable ally-versus-ally battle … As a bicyclist, I am constantly on the lookout for oncoming buses even when I’m in a bike lane. As a transit rider, the mere seconds delay to wait for a biker can cause my bus to miss a traffic signal, which can cause me to miss my transfer, which can cause me to arrive 15 minutes late to work on the day where a coworker brought in Mel-O-Glaze Donuts, which can then cause me to be donut-less for the whole morning. Like, I said, none of this is good.

Chris Iverson at the Minneapolis blog streets.mn

This came across my email just as I'd finished a meeting about a bike vs bus lane problem on Auckland's Karangahape Road.  The interaction of curb-running bicycles and bus stops is a problem on every continent and island, because it's a geometry problem.

And that means, chill!  Obviously, we push back on anyone who says that either bikes or buses are "just more important" than the other; that's just tribalism.  But then you accept the difficulty and the unsatisfactoriness of any compromise, including the one Chris proposes, the "floating bus stop" shown here in an image from the NACTO Street Design Guidelines:

Seattle_unknown_21

This works fine as long as the bus stop isn't busy, but of course there are likely to be lots of pedestrians crossing the bike lane at the times when the bus is stopped there, so a cyclist's odds of actually passing a stopped bus on the curb side may be limited.  I also prefer "table" or shared space solutions for the bike lane that alert the cyclist to yield to peds in this situation.  

Is it perfect?  No, but there isn't a perfect solution.  We know that geometrically, so: chill!

Raleigh: Four (or 36) alternatives for Wake County’s transit future

Wake_transit_logo_full_colorToday, Wake County (the Raleigh, North Carolina area) released our report outlining four possible directions that the community could take in defining a future transit network.  Download it here.  Happily, the local newspaper's coverage is clear and accurate.  

This begins a period of public discussion about the report and the choices it outlines.  That discussion will give us direction on what form the final recommended plan should take.  That plan, in turn, will form the basis for a proposed referendum on a sales tax increment to fund expanded transit.

Actually, there are more than four possible futures, and the final plan won't look quite like any of these.  Read on:

The key idea — as in much of our work — is to build an "alternatives space" in which people can figure out where they want to come down on the two most difficult policy tradeoffs:

  • Ridership vs coverage?  What percentage of resources should to go pursuing a goal of maximum ridership — which will tend to generate frequent service in the densest urban markets — as opposed to the goal of coverage — spreading service out so that as many people as possible have some service nearby?
  • Infrastructure vs service?  How much to spend on building transit as opposed to operating transit.  Obviously infrastructure can make service more attractive and efficient, but too much infrastructure can lead to not enough ordinary bus service covering the whole county.  

Both of these tradeoffs are explored in detail in Chapter 5 of our report.

The idea is to use these four mapped alternatives to imply 36 alternatives, as follows:

Alternatives Space

The four red squares are the four mapped network alternatives, while the white squares are other possible positions that we can tabulate.  The idea is to ask people questions roughly of this form:

  1. "Which alternative is closest to what you want?"
  2. Would you like that alternative even more if it moved a bit toward coverage or toward ridership? (a step left or right in this table)
  3. Would you like that alternative even more if there it moved a bit toward infrastructure or toward service? (a step up or down in this table)

Obviously the questions can be phrased in ways that don't require the user to visualize this matrix.  This is just a high-level description of what we'll be after.

This approach allows everyone responding to navigate us to one of 36 squares indicating their preference, giving us feedback that is both nuanced and yet quantifiable.  Most public feedback is one or the other but not both.   And that's good for everyone who's responding, because in my experience, tabulated feedback is more influential feedback.  Written feedback is certain still welcome and will be reviewed, but tabulated feedback really tells what lots of people are thinking.

If you live in Wake County or know anyone there, it's now time to get involved.  Download the report, read at least the executive summary, form your own view, and express it!  The more people respond, the more confident we'll be in defining the final plan based on their guidance.

Our fun short course in network design comes to Tampa June 1-2

Course in NYC 2014On June 1 and 2 in Tampa, Florida, I'll be teaching another session of our popular Interactive Course in Transit Network Design.  It's part of the Community Transportation Association of America conference, but you can attend the course without attending the conference.  

The price is $750 if you or your organization doesn't belong to CTAA, $650 if you do.  Yes, this is higher than we charge when we teach it directly, but at this stage we don't have another direct offering until October in Portland.

We designed this course to fill a gap in the training of most planning professionals.  Few graduate programs teach public transit "from the inside," building an understanding of its unique opportunities and limitations through the experience of actually working with the tool.  Still fewer hire teachers who are both seasoned practitioners and skilled in relating public transit to larger narratives that motivate people.  If you care about public transit as part of your future city, invite your favorite land use planner to take this course!   They'll come out much savvier about how to recognize development proposals that truly work with public transit, as distinct from those that are just paying lip-service in order to "paint development green."  

Register here.  Select "2-Day Intensive Training" and "Transit Network Design."  You can also use this paper form:   Download Expo2015regform-9

 

Local bus systems reduce employee turnover! (quote of the week)

This.  Is.  So.  Important.

We find that the size of the fixed-route bus system (measured as real per capita operating expenditures) is negatively related to employee turnover rates [for local employers]: An increase in bus systems’ per capita operating expenditures is associated with a decrease in employee turnover. Decreases in employee turnover represent cost savings to businesses by reducing the costs associated with training new workers and rebuilding firm-specific knowledge or better employee-employer matches. These results suggest that access to fixed-route bus transit should be a component of the economic development strategy for communities not only for the access to jobs that it provides low-income workers but also for the benefits accruing to businesses that hire these workers.

Dagney Faulk and Michael J. Hicks,
"The Impact of Bus Transit on Employee Turnover:
Evidence from Quasi-experimental Samples"
Urban Studies

This also means that new employers need to read this before they choose their location!

I could wish that they had measured transit quantity using revenue hours rather than expenditures, because revenue hours are a better measure of service to the customer.  But still, this is a big deal.  Eric Jaffe also has the story at Citylab.