Should you build or buy Public Works & Infrastructure Asset Management?
Public works asset management software tracks the physical infrastructure a city or county owns, from roads, signs and signals to stormwater and water mains, and runs the work-order loop from citizen request through inspection, maintenance, cost tracking and GASB reporting. Public works directors, GIS staff and finance teams buying for a municipality or utility use it daily.
Buy the public-works EAM and let ArcGIS-native apps handle local workflows around it.
Build it, buy it, or bridge?
When building makes sense
Building makes sense for a county or utility that already runs ArcGIS and has GIS staff who can own a work-order module as a permanent product. Some agencies have paired ArcGIS Online with Survey123 and Workforce to run inspections and mobile-crew dispatch as production apps, without buying a full EAM suite. What building does not replace is the audited half of the job: GASB 34 evidence, 311 intake wired to a call center, and the multi-year support contract that keeps a system running after the developer who wrote it leaves. Building earns its keep for the integration and field layer around a vendor system, or for an agency with genuine GIS capacity and appetite for long-term ownership.
When buying makes sense
Buying is the right call for most public-works departments because the audited half of this job, GASB 34 evidence, 311 intake and mobile-crew dispatch, arrives configured out of the box. Cartegraph, Cityworks and Lucity are purpose-built for the asset, inspection and work-order loop that every department runs, and they carry the population-tiered pricing and packaged compliance templates that a homegrown system would have to invent from scratch. Cityworks (recently folded into Trimble Unity Maintain) is built natively on Esri's ArcGIS platform, so a department that already licenses ArcGIS gets both the vendor's audit trail and the GIS integration in one contract instead of stitching the two together itself. Buying wins when a department needs a support line, a documented upgrade path and a vendor that has already solved GASB reporting for thousands of municipalities.
The desk read
Build-versus-buy analysis for Public Works & Infrastructure Asset Management is being written. In the meantime, the framework that drives every B4 call is on the B4 Index page.
Frequently asked
What is public works asset management software?
It's the work-order and inspection system that sits on top of a city's or county's GIS, turning a citizen complaint or a scheduled inspection into a tracked job with cost coding, a crew assignment and the paper trail an auditor checks against GASB 34 standards.
Can a city really build its own asset-management system?
It happens on top of Esri's ArcGIS, where a county with in-house GIS staff can assemble Survey123 and Workforce into a working inspection and dispatch system without buying a packaged EAM. It stays rare because most public-works departments don't carry that kind of GIS staff, which is why the vendor suites remain the default.
Why does Cityworks require ArcGIS?
Cityworks, recently folded into Trimble Unity Maintain, was built GIS-first from day one, with your parcel and asset layers as the single source of truth. That's the selling point for a department already on Esri's platform, and the reason a department without ArcGIS should compare Cartegraph or Lucity instead.
What do these systems actually cost?
Pricing is population-tiered and quote-based rather than published as a flat rate, so a small city pays far less than a large county running a citywide rollout with GASB reporting and 311 integration built in. Get quotes from at least two vendors before assuming the smaller name is cheaper.
What are the main public works asset management vendors?
Representative vendors include Cartegraph, Lucity. B4 Pro includes the category score and the full vendor list.