Protocolizing Potholes
The Protocol Institutes November book writing month starting today offers a prompt: take a field you’re familiar with and reexamine that space through the lens of protocols. I have a lot of thoughts about potholes and smart cities stuff. I’m not prioritizing putting those all together formally into book form by the end of November but do intend to do some riffing.[0] This piece is a first stub of that larger smart cities / civic tech inquiry.
Potholes are a high visible unit of city performance. Many mayors focus a nontrivial piece their tenure on the problem. “Fixing potholes” has become a synechdoche for nonpartisan good government through better tech or improved business practices or the like. Potholes also served as a key focal point for the Bureau of Municipal Research. In the early days of the foundational effort, the BMR counted the potholes actually fixed in NYC. (Rather than relying on the biased reports of the political patronage machine. Or at least that’s my recollection.)
Waymo recently announced that they were sharing data on potholes with the City and County of San Francisco. The many cameras and other sensors provide a tool to show where potholes are and inform city management practices. This information can be useful. Cities don’t actually know where all the potholes are. Instead laser vans, windshield surveys and 311 provide an operational picture of where potholes are. Those information are used to allocate moneys for which roads to streets.[1]
For a long time, I thought that was a data problem. The root of the issue was the wrong information being used to make street management decisions and the solution was using the right information. Looking downstream at how that information gets utilized in decisions from the budgetary to the operational level, I’m now convinced the problem is protocolized.
In the states, funding for cities from higher levels of government tends to be tied to the Pavement Condition Index. I did a bunch of public records act requests from cities across the country on how they track and manage potholes. The divergence of data formats and practices was illuminating. It’s quite the mess. That’s obvious though. Look around: the public sector struggles to deliver these days!
Taking a more protocolized lens, some questions to explore and potentially follow up on:
- What are the tradeoffs between efficiency and thoroughness in the current equilibrium? What are the leverage points to expand the ETTO frontier?
- What is the current system solving for? What are the incentivizes of different actors from vendors fixing the streets to consultants crunching street quality numbers to civil servants managing the programs and all the specific folks therein?
- What is the historical evolution of the pavement condition index? What other standards does it mirror and where might be the leverage points to evolve that index?
- Where might an integrated pilot deploying not just novel sensors but also looking at
- What is the right temporal perspective for shifting pothole maintenance? Potholes typically go through a seasonal cadence with weather. Modern roads like many other civilly engineered infrastructure goes on a generational scale of several decades.
- How is pothole maintenance a synecdoche for the larger shift to cyberphysical infrastructure and evolution of civil engineering? See the argument in Real Engineers Deliver Results that engineering is defined by whether things work in the world, not by credentials or process, which is a useful yardstick for civil engineering as it takes on cyberphysical systems.
- How do other cities globally fix their potholes? What are the consequences of public contracting procedures in places like the states? What are possible alternative protocols to improve the situation?
[0] My plan in November is to iterate on a very rough children’s book that I have ~31% written called _A Portal to Primeland. [1] Not this a US based perspective. For more context on ARGO’s past work in potholes, see:
[ARGO's street quality identification device, or SQUID, was our attempt to test whether cities could measure road conditions with cheap, open hardware instead of relying only on laser vans, windshield surveys, and 311 complaints. The project documents a low-cost sensor package that can ride along on ordinary vehicles and capture location-tagged data about how rough the pavement is. The idea was that a city could collect street quality information continuously, as a byproduct of the driving it already does, rather than in occasional and expensive survey passes. The build write-up is meant to be reproducible, so other governments and civic technologists can adapt the device for their own needs. In hindsight, SQUID also showed how much the value of better sensing depends on whether a city's existing processes can absorb the data.]
v2
PAtwater