The Infrastructure Investment and Jobs Act allocated more than $65 billion specifically for broadband, with additional billions in the transportation, water, grid modernization, and resilience programs that feed directly into smart city and connected infrastructure work. For municipalities and regional governments, this represents a once-in-a-generation opportunity to modernize physical infrastructure with digital intelligence built in.
It also represents a serious implementation challenge. Spending IIJA funds responsibly — in ways that actually deliver the intended benefits, survive federal oversight, and remain operational after the grant period ends — is harder than it looks.
The Deployment Gap
There’s a consistent pattern in technology-enabled infrastructure programs: the deployment phase looks nothing like the planning phase.
Sensor networks that were specced for a suburban environment get deployed in a downtown core with multipath interference the vendor’s bench testing didn’t anticipate. Data platform architectures that assumed reliable connectivity encounter dead zones that create gaps in operational data. Integration with legacy city systems — traffic management, utilities, emergency dispatch — runs into vendor lock-in and API limitations that nobody mapped during procurement.
None of these are insurmountable, but they’re common enough to be predictable. Programs that budget time and resources for discovery and adaptation during deployment fare better than ones that assume the planning phase captured everything.
The Standards Question Matters More Than You Think
One of the most consequential decisions in a smart infrastructure program is often the least visible: which data and communication standards to adopt.
The IoT and smart city landscape still has significant standards fragmentation. LoRaWAN vs. NB-IoT vs. LTE-M for sensor connectivity. NTCIP vs. proprietary protocols for traffic management. C-ITS standards for vehicle-infrastructure communication. The choice of standards determines what equipment you can use, what vendors you’re dependent on, and — critically — what you’ll be able to integrate with when the next generation of technology arrives.
Programs that adopt open, widely-supported standards at the data layer retain more flexibility over time. Programs that accept proprietary platforms for operational simplicity often find themselves locked into a vendor relationship with unfavorable economics by year three.
Sustainability After the Grant Period Ends
Federal grants fund capital deployment. They don’t fund ongoing operations. The programs that fail after the grant period ends are almost always the ones that didn’t build a sustainable operating model during the planning phase.
For a smart infrastructure deployment, sustainable operations require:
Defined ownership. Which city department owns each system component, and is accountable for its continued operation? This is often unclear after multi-agency deployments where different program offices led different workstreams.
Maintenance funding. Sensors fail. Software needs updating. Connectivity costs are recurring. The operating budget required to keep a smart infrastructure deployment running needs to be identified and committed before deployment, not after the grant ends.
Staff capacity. New infrastructure creates new operational requirements. Someone needs to monitor the network, respond to failures, analyze the data being generated, and manage the vendor relationships. Often this requires either new hires or significant reskilling of existing staff — both of which take time to develop.
Data utilization. The business case for most smart city investments depends on the data being used — for traffic optimization, infrastructure maintenance prediction, emergency response improvement, or similar operational applications. Programs that deploy sensors but never build the data analysis and operational integration layer are paying for infrastructure that doesn’t deliver its intended value.
What Good Looks Like
The smart city programs delivering durable results started with operational problems, not technology enthusiasm. They identified specific problems — traffic signal timing inefficiency, water main failure patterns, energy waste in municipal facilities — and selected technology to address those specific problems.
They involved operational staff in design, not just technology staff, because the people who will run these systems every day have practical knowledge that shapes whether they’re actually useful. They built procurement processes that evaluated long-term total cost of ownership, including operations, not just acquisition cost. And they treated the technology as an enabler of operational improvement rather than the goal itself.
The IIJA funding window is real, and the programs worth building are the ones where the infrastructure investment is in service of a clear operational mission — not just a technology modernization for its own sake.