Buying asset and work management for public works: EAM, CMMS, and the GIS question
Whether you need a GIS-native EAM or a lightweight CMMS depends on your dominant asset class. Here's how to tell which you are, and how the vendor field lines up behind fleet, facilities, and linear assets.
Enterprise asset management (EAM) and work-order systems track the condition, maintenance, and lifecycle of public infrastructure — roads, water and sewer networks, facilities, and fleet — and link field work to capital planning. The category is broad enough that two agencies can both say they need "asset management" and mean almost entirely different things. The buyer's first job is not to compare products; it is to name the dominant asset class the system will actually serve, because that single fact reorders the whole shortlist.
The most useful cut through this market is by asset type: linear assets (the pipe, pavement, and network world), facilities and general maintenance (the CMMS world), and fleet (the vehicle-maintenance world). The strongest products lean hard into one of these, and the mismatch between what an agency buys and what it actually maintains is the most common and expensive error in the category.
First decide how GIS-centric you need to be
For agencies whose assets are fundamentally spatial — water, sewer, stormwater, roads — the map is not a nice-to-have; it is the natural system of record. Cityworks, now part of Trimble, is built natively on Esri ArcGIS, using the GIS itself as the asset register, which makes it exceptionally strong for asset and work management in GIS-mature public-works and utility organizations. If you have already standardized on Esri and your dominant assets are linear networks, a GIS-native EAM is usually the right architecture, because it avoids maintaining a second, divergent copy of the asset inventory.
For agencies whose work is really facilities and general maintenance — buildings, HVAC, work orders, preventive maintenance — a full GIS-native EAM can be more architecture than the job needs. This is CMMS territory, where speed of stand-up and ease of use matter more than deep spatial modeling.
The vendor field by dominant asset class
On the GIS-centric, linear-asset side, Cityworks (Trimble) is the natural choice for Esri-standardized shops, and Trimble's broader geospatial and field-data portfolio reinforces that fit for infrastructure and public-works organizations. Cartegraph, now part of OpenGov, is a well-regarded operations and asset-management platform with particular strength in pavement, facilities, and infrastructure condition tracking, and a cleaner interface than many legacy EAM tools — its OpenGov ownership is a real draw for agencies that want asset management alongside OpenGov budgeting and permitting, and it fits small and mid-size public-works departments well.
On the facilities and general-maintenance side, Brightly (formerly Dude Solutions, now a Siemens company) is a widely adopted operations and maintenance suite covering facilities, infrastructure, and fleet, with especially deep penetration among school districts and mid-size governments via its Asset Essentials product; its appeal is approachable, cloud-based CMMS that stands up faster than enterprise asset systems. On the fleet side, AssetWorks is a specialist best known for its FleetFocus fleet-maintenance system used by large DOTs, counties, and cities, with genuine depth in work orders, parts, motor pool, and fuel-management integration — the right answer when the vehicle fleet, not the pipe network, is the dominant asset class.
Evaluation criteria and failure modes
Weight the evaluation on the things that actually drive value: fit to your dominant asset class, the quality and offline capability of the mobile field app the crews will live in, GIS integration (real and bidirectional, or a thin export?), and the link from work-order history to capital and replacement planning — the payoff that separates asset management from a glorified work-order log. Total cost over a multi-year horizon and implementation risk carry the same weight they do everywhere.
The failure modes are consistent. Buying a facilities CMMS for a linear-asset utility (or vice versa) produces a system the field never fully adopts. Underinvesting in the asset inventory itself — the data — leaves you with an elegant tool managing a register nobody trusts. And a field app that does not work offline in the places crews actually work will not get used, no matter how good the office-side reporting looks. Name your dominant asset class honestly, shortlist within it, and pressure-test the mobile and GIS story before the office-facing dashboards seduce the committee.