I’ve been working on a project for a research center in New Brunswick over the last few months. The legwork has involved conducting interviews with officials at Metropolitan Planning Organizations (MPOs) and state DOTs to document their experiences with TELUS, a database-management platform that’s employed for logistical and compliance purposes. Agencies use the software to assemble their federally-mandated Transportation Improvement Plans (TIPs), track their infrastructure spending, classify and prioritize individual projects, and share project data. A web-based version helps officials comply with SAFETEA-LU requirements for public transparency; a land-use projection model works in tandem with TELUS to allow agencies to predict future traffic and land use patterns, as well as employment and population growth.

From what we’ve learned, TELUS seems to have been a big help for state and local transportation agencies. Instead of copying information back and forth between e-mail accounts, Access databases, and Excel sheets (as had been the practice), those that adopted TELUS now have a global framework for managing their project data and making it available. One problem that dogs all of the software in this niche is a lack of standardization among competing platforms. A number of state and local agencies have developed their own programs to carry out the same tasks that TELUS handles. The programs all seem to have been developed separately, with little regard for compatibility with others. In some cases agencies require their subordinate partners to submit data in their proprietary formats, making the adoption of an outside framework complicated. There’s a period of this that occurs in every wave of development– whether it’s rail gauges, or radio frequencies, or operating systems. Individual participants can waste a lot of effort and money by picking the wrong horse. It’s interesting (as an observer).

At the end of the research, two observations (personal, not directly related to TELUS) stand out. The first is the enormous role that the federal government plays in local infrastructure projects, especially in conservative, rural parts of the country. The second is the lopsided preference that federal funding gives to highway infrastructure, as opposed to passenger rail, freight rail, bicycle/pedestrian provisions, and ferry/shipping services. It’s almost a cliché that mass-transit is an insolvent business model, and one that requires massive public investments, while cars and trucks remain ubiquitous symbols of potent American individualism. Imagine how that picture would change if, instead of the highway system, the feds maintained all of the rail infrastructure, and allowed private companies to use it, for profit, at little or no fee? If the highways were all maintained by private entities who had to raise revenues through tolls, or forgo their maintenance?

I’ll post a link to our report when it’s published.