Search any public works forum for asset management software and you find the same thread on repeat: a city or county asking which platform to buy, and a dozen replies naming a dozen different tools. AssetWorks. Cityworks. OpenGov. iWorQ. NexGen. Each reply is confident, and none of them agrees.
The reason the answers scatter is that the question skips a step. Public works is not one asset problem. It is streets, fleet, facilities, parks, signs and signals, water and sewer, each usually run by a different division with its own list. Software cannot merge divisions that do not want to be merged. That is the work that comes first.
This guide covers what asset management software for public works actually does, why the buy decision is really a consolidation decision, and when a city already owns the platform it is about to go shopping for.
What is asset management software for public works?
Asset management software for public works is the system of record for a public works department’s physical assets, holding the asset inventory, condition data, maintenance schedules and work orders across every division in one place instead of in separate spreadsheets and legacy databases.
The public works version has one feature that sets it apart from a single-purpose maintenance tool: it has to hold very different asset classes at once. A road segment, a backhoe, a pump station, a ballfield and a stop sign have almost nothing in common in how they are inspected, maintained or funded, and the software has to treat each on its own terms while still rolling them up into one capital picture.
- Holds a shared inventory across streets, fleet, facilities, parks and utilities
- Tracks condition and inspection history per asset class
- Schedules preventive maintenance and manages work orders
- Captures citizen requests and routes them to the right crew
- Feeds the capital plan and the annual budget with real data
The buy decision is really a consolidation decision
Here is what actually happens when a public works director shops for software before doing the groundwork.
Streets keeps its pavement condition in one system. Fleet runs a separate maintenance package the mechanics like. Facilities has a spreadsheet. Parks has a different spreadsheet. Utilities may have a real asset system because the state makes them report on it. Each division owns its list, defends its list, and has good reasons for the way it works.
A new platform does not dissolve those boundaries. It inherits them. The city signs a contract, then spends the first year discovering that the five divisions still will not agree on what counts as an asset, how to name it, or who updates it. The software gets blamed for a problem it was never able to solve.
The groundwork is unglamorous and it is the whole game: agree on one asset hierarchy across divisions, agree on naming, agree on who owns each record, and decide which citizen-request and work-order flows everyone will actually use. Do that, and almost any competent platform will work. Skip it, and none of them will. This is the same lesson a water utility learns when it tries to buy its way out of a messy asset register, which we covered in our guide to utility asset management software and the buy or build question.
Once the divisions agree on one structure, that structure is the asset. It is portable, and it is what makes a single asset registry across departments possible no matter what software sits on top of it.
The asset classes a city has to hold at once
Not every division needs the same depth, and pretending they do is how cities overbuy. A quick read on where the real complexity sits:
| Division | What it tracks | How demanding |
|---|---|---|
| Streets and roads | Pavement condition, signs, signals, right of way | High, condition scoring drives most of the capital plan |
| Fleet | Vehicles, equipment, fuel, parts, mechanic labour | High, and often already on a dedicated fleet tool |
| Water and sewer | Mains, pumps, meters, treatment assets | High, and usually driven by state reporting |
| Facilities | Buildings, HVAC, lighting, grounds | Medium, work-order heavy |
| Parks | Fields, playgrounds, trails, irrigation | Lower, seasonal patterns |
Read the fleet and water rows carefully before you buy anything general. Both often run on tools built for exactly that job, and ripping them out to force everything into one public-works platform can cost more capability than it gains. Consolidation does not have to mean one system for all five. It can mean one shared inventory and one reporting layer, with the specialist tools feeding it.
The option the vendor comparisons leave out
No public works software comparison mentions the platform most cities already own, because the companies writing those comparisons sell the alternative.
If your city runs Microsoft 365, every division is already in the same tenant, with the same logins, the same permissions model and the same audit trail. That matters more than it sounds, because the reason the divisions are siloed is rarely the software. It is that each bought its own tool at a different time. A shared tenant is the one thing they already have in common.
On that tenant, SharePoint and Dataverse can hold a shared asset inventory with a hierarchy that fits how the city is actually organised. Power Apps can put a work-order form and an inspection form on a phone for a streets crew and a different one for facilities, without buying two products. Power Automate can take a citizen pothole report and route it to the right division. Power BI can put the whole capital picture in front of the council.
To be precise about the licensing, because both vendors and enthusiasts get it wrong: Microsoft 365 E1, E3 and E5 include seeded rights to build Power Apps and Power Automate over Microsoft 365 data such as SharePoint, and E5 includes Power BI Pro (Microsoft Power Platform Licensing Guide, August 2026). Dataverse and other premium connectors need Power Apps Premium or Power Automate Premium on top. So a light build is effectively covered, and a deeper one costs something, just far less than a per-asset municipal platform subscription across five divisions.
None of that means every city should build. It means the check is worth an afternoon before signing a multi-year contract, because the answer surprises a lot of directors.
UNIFIED UTILITY MANAGEMENT
Could your divisions share one system they already pay for?
Nexinite builds a shared asset inventory, mobile work orders and capital reporting into the Microsoft 365 your city already runs, in your own tenant. No new platform per division, and no forever licensing.
When a dedicated public works platform is the right buy
Building is not the answer for every city, and there are clear cases where a purpose-built platform earns its price.
You need deep GIS at the centre of everything. If your operation runs on Esri and every asset decision starts from the map, a platform with native ArcGIS integration saves real effort. This is the single most common honest reason to buy.
Your state mandates a specific reporting format you do not want to build. When a regulator dictates the exact asset condition report on a fixed cycle, a vendor that ships that template can be worth the licence on its own.
You have no internal IT capacity and no appetite for one. A built system is yours to own, which is its main advantage and also its cost. A small city with one overworked IT generalist may be better served by a vendor and a support contract.
If none of those fit, the pull toward buying is mostly momentum and a good demo.
How a shared Microsoft 365 approach looks in practice
The clearest proof comes from the utility side, where the stakes and the reporting are highest. Silicon Valley Clean Water had asset data scattered across financial systems, project management tools and SCADA, with engineering and operations unable to align. Rather than buy another platform to sit beside those systems, they built an equipment information management system on the Microsoft stack they already licensed: SharePoint, Power Apps, Power BI, Power Automate, Dataverse and Azure.
According to Nexinite’s published case study with the utility, the result was a 40% reduction in unplanned maintenance and an estimated 20% saving in operational costs, with capital planning now drawing on real operations data. The full detail is in the SVCW equipment tracking and asset management case study.
A public works department is the same shape of problem with more divisions. Nexinite works with municipal clients including the Cities of Watsonville, Coronado, Cupertino and Rancho Cordova, and the Cupertino work connects asset and project data into capital improvement planning. The transferable part is not the technology. It is fixing the shared structure first and letting the tooling follow.
How to evaluate what your city already owns
Before the next demo, this takes an afternoon and changes the conversation with every vendor.
- List every asset system across divisions. Streets, fleet, facilities, parks, utilities. Every spreadsheet counts. The length of this list is your real project.
- Pull your Microsoft 365 plan. Ask IT whether Power Apps and Power Automate over SharePoint are covered, and whether you hold any Power Apps Premium licences for Dataverse.
- Decide what has to unify and what can stay specialist. Fleet and water often stay on their own tools and feed a shared inventory.
- Name the reporting the council and the state actually require, because Power BI likely already covers it on E5.
Frequently asked questions
What is asset management software for public works?
It is the system of record for a public works department’s physical assets across every division, from roads and fleet to facilities, parks and utilities. It holds the asset inventory, condition data, maintenance schedules, work orders and citizen requests in one place, and feeds the capital plan and budget with real data instead of scattered spreadsheets.
What is the difference between a CMMS and public works asset management software?
A CMMS is centred on maintenance work orders. Public works asset management is broader, covering the full lifecycle and capital planning across many asset classes. Most municipal platforms now include CMMS functions inside a wider asset system.
Can a city run public works asset management on Microsoft 365?
Often, yes, and it is worth checking before buying. If your city runs Microsoft 365, every division already shares one tenant. SharePoint holds the inventory, Power Apps handles mobile inspections and work orders, Power Automate routes citizen requests, and Power BI reports to the council. Seeded rights over SharePoint are included on E1, E3 and E5, while Dataverse needs Power Apps Premium (Microsoft Power Platform Licensing Guide, August 2026). The real work is getting the divisions to agree on one asset structure, which no purchased platform does for you either.
Do we need one system for every division?
No. Consolidation can mean one shared inventory and one reporting layer, with specialist tools like a fleet package feeding it. Forcing every division into a single platform sometimes costs more capability than it gains.
Does our asset data stay under the city’s control?
With a vendor platform, the data lives in the vendor’s environment. With a system built on your own Microsoft 365 tenant, it stays in infrastructure the city already controls, which also simplifies public records and retention duties.
Where to start
Do the consolidation work before the demos. Getting your divisions to agree on one asset structure is the piece that pays off no matter which way you decide, and it is the piece that determines whether the software you pick ever delivers.
If you want a view on what your existing Microsoft licences could already carry across divisions, that is worth a conversation before the shortlist narrows.