Picture the moment this search usually happens. A utility director has a shortlist of three or four asset management platforms, a demo booked for Thursday, and a budget that does not comfortably stretch to any of them. Meanwhile the actual asset register lives in two spreadsheets, a GIS layer nobody has reconciled since 2021, and the head of one operator who retires in eighteen months.
Every buyer’s guide for this category will help with the shortlist. Almost none of them will tell you that the shortlist is the wrong place to start, or that a good share of small and mid-sized utilities already own most of the pieces they are about to pay for again.
This guide covers what utility asset management software does, how to judge whether you need to buy a platform, and what it looks like when a utility builds one on the Microsoft licenses it already holds.
What does utility asset management software actually do?
Utility asset management software is the system of record for a utility’s physical assets, holding the asset register, condition and inspection history, maintenance planning and work orders in one place so the information stops living in separate spreadsheets and systems.
It helps to split the category in two. There is the register, meaning what you own, where it sits, and what condition it is in. Then there is the work layer, meaning what needs doing, who did it, and what it cost. Most platforms sold under the label do both, and most are only as reliable as the register underneath them.
For a water or wastewater utility it also has to reach in two directions at once: a field crew standing at a lift station with a phone, and a finance team building a ten-year capital plan.
- Maintains the asset register and its hierarchy
- Tracks condition and inspection history
- Plans and schedules preventive maintenance
- Issues, assigns and closes work orders
- Reports for compliance and capital planning
Start with the asset register, not the vendor shortlist
Software cannot fix an asset list nobody trusts.
This is the part that gets skipped, and it is the part that decides whether the project works. Before a demo is worth taking, someone has to answer a short set of questions honestly. Do we have one list of our assets, or several that disagree? Does that list use consistent naming, or does the same pump appear three ways depending on who entered it? Do we know the install date and the condition of the things on it, or only the ones that have failed recently? Is any of this connected to what we spend on them?
Utilities that skip this step tend to follow the same path. They buy the platform, discover during implementation that the register has to be rebuilt anyway, and spend the first year of a multi-year contract paying a vendor to host data that is still wrong. The software gets blamed. The register was the problem.
There is a second reason to do this first. Once you have a clean register with consistent naming, a documented hierarchy and condition data attached, you have the thing that actually determines your options. That work is portable. It is equally useful whether you end up buying a platform, building one, or running the next three years on what you have while you fix the bigger problems. The register is the asset. The software is just where you keep it.
It is also the point where a single asset registry with enforced naming and validation stops being an abstract feature on a comparison chart and starts being the thing your maintenance planning depends on.
EAM, CMMS, and what the labels actually mean
The category has two overlapping labels and vendors are not consistent about them.
A CMMS, a computerized maintenance management system, is built around maintenance. Work orders, preventive maintenance schedules, labour and parts, maintenance history. Its centre of gravity is the work.
An EAM, enterprise asset management, is built around the asset across its whole life, from design and commissioning through operation, maintenance and replacement. It usually carries the maintenance functions a CMMS has, and adds lifecycle cost, capital planning and financial reporting.
In practice the distinction matters less than the sales conversation implies. Most modern platforms sold to utilities carry both sets of functions, and the useful question is not which acronym applies but which end of the lifecycle your actual problem sits at. If your problem is that preventive maintenance is not getting done, you have a work problem. If your problem is that nobody can tell you what replacing the west basin will cost in 2031, you have a lifecycle problem, and a maintenance tool will not answer it no matter what it is called.
The option the buyer’s guides leave out
Here is the position no vendor has any reason to put in front of you: a meaningful share of small and mid-sized utilities already license most of what asset management requires, and have never been told.
It pays to be precise here, because both vendors and enthusiasts get this wrong in opposite directions. Microsoft 365 E1, E3 and E5 include seeded Power Platform rights: you can build Power Apps canvas apps and Power Automate flows over Microsoft 365 data sources such as SharePoint, Teams, Excel and Outlook at no extra cost (Microsoft Power Platform Licensing Guide, August 2026). E5 also includes Power BI Pro. That alone is enough to run an asset register in SharePoint, put an inspection form on a phone, and route a failed inspection to a work order.
What is not included is worth knowing before anyone promises otherwise. Dataverse and the other premium connectors, including SQL Server and most non-Microsoft systems, sit behind Power Apps Premium or Power Automate Premium, which are separate per-user subscriptions (Microsoft Power Platform Licensing Guide, August 2026). On E3 rather than E5, Power BI Pro is an add-on too.
So the honest version is this: many utilities already own enough to run asset management on SharePoint and seeded Power Platform rights, and a larger build using Dataverse costs something, just far less than a per-asset platform subscription. Either way the licensing question has a definite answer, and almost nobody asks it before booking demos.
None of that is a reason to build. It is a reason to check before you buy, which is a different and much cheaper decision.
Every buyer’s guide in this category is published by a company that sells one of the platforms, or by a site earning affiliate revenue when you pick one. That is not dishonest, but it does explain a consistent blind spot. The option that costs the vendor a sale does not appear on the comparison chart.
The comparison worth running looks like this:
| What you need | Dedicated EAM platform | Built on Microsoft 365 you already license |
|---|---|---|
| Asset register and hierarchy | Built in, opinionated, fast to stand up | Built to your naming and structure, needs designing first |
| Mobile field inspections | Included, works out of the box | Power Apps, including offline capture |
| Work order management | Mature and deep | Power Automate, strong for standard routing, more work for complex scheduling |
| SCADA and telemetry integration | Often prebuilt connectors | Possible via Azure, genuinely more effort |
| Link to capital planning | Varies widely, often a separate module | Direct, since the finance data is already in the tenant |
| Reporting and dashboards | Vendor’s reporting tool | Power BI, included with E5, add-on on E3 |
| Where the data lives | Vendor’s environment | Your own Microsoft tenant |
| Ongoing cost | Annual per-user or per-asset subscription | Build cost, then support. Seeded rights are free, Dataverse needs premium licences |
Read the SCADA row honestly before anything else. If your operation depends on deep, real-time telemetry integration, that row is where a build gets expensive and a purpose-built platform earns its price. The rest of the table tends to favour building for utilities that already have a Microsoft footprint. That one row can outweigh all of it.
This is the same reasoning behind an equipment information management system built inside Microsoft 365: not a cheaper copy of an EAM, but the same capability assembled from licences the agency is already buying, and owned outright.
UNIFIED UTILITY MANAGEMENT
Want to see what your Microsoft licenses already cover?
Nexinite builds the asset register, mobile inspections and capital planning into the Microsoft 365 your agency already pays for, in your own tenant. No new platform, and no forever licensing.
When buying a dedicated EAM platform is the right call
Building is not the answer for everyone, and pretending otherwise would be its own kind of sales pitch. There are three situations where buying is the better decision.
You run a large linear asset network with heavy regulatory reporting. Thousands of miles of pipe or line, with mandated condition reporting on a fixed cycle, is exactly what the big platforms were designed for. The reporting templates alone can justify the licence.
You need deep SCADA or telemetry integration on day one. If work orders have to be generated automatically from real-time operational data across many asset classes, prebuilt connectors are worth paying for. This is the row in the table above that most often decides it.
You have no internal capacity to own a system. A built solution is yours, which is the main argument for it and also the responsibility that comes with it. If there is no internal IT function and no appetite for a support relationship, a vendor platform with a support contract is the more honest choice.
If none of those three describe your utility, the case for buying is weaker than the demo will make it sound.
How Silicon Valley Clean Water built asset management on Microsoft 365
Silicon Valley Clean Water had the problem in its most common form. Asset data was scattered across financial systems, project management tools and SCADA. Engineering teams could not align operations and maintenance data with capital improvement planning, and the finance team had no clear view of what assets were costing across their lives, which made budget planning guesswork.
None of that is unusual. What makes it worth reading is what they did about it.
Rather than buying a platform to sit alongside the systems they already ran, SVCW built an equipment information management system inside the Microsoft stack they were already licensed for: SharePoint, Power Apps, Power BI, Power Automate, Dataverse and Azure. Individual assets were organised into process areas so the hierarchy matched how the plant actually operates rather than how a finance system happened to list them. Maintenance scheduling was tied to manufacturer guidance and warranty conditions. A feedback loop was built between finance, engineering and operations so that capital planning drew on real maintenance history instead of estimates.
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 informed directly by operations and maintenance data. You can read the detail in the SVCW equipment tracking and asset management case study.
The part worth stealing is not the technology. It is the sequence. SVCW fixed the hierarchy and the data flow first and let the tooling follow, which is also why the capital improvement planning side could be connected at all. A platform bought a year earlier would have inherited the same disconnected data.
How to evaluate what you already own
Before the next vendor call, this takes an afternoon and changes the conversation.
- Pull your Microsoft 365 licence detail. Ask IT which plan the agency is on. E3 and E5 both seed Power Apps and Power Automate over SharePoint. Confirm separately whether you hold any Power Apps Premium licences, since that is what governs Dataverse.
- Count your asset registers. Every spreadsheet, GIS layer and database that claims to list assets. If the answer is more than one, that is the first project.
- Name the real problem. Maintenance not getting done, or lifecycle cost you cannot forecast. They need different things.
- Check the SCADA requirement. Be specific about what has to integrate and how quickly, because this is the row that decides build or buy.
- Ask what your reporting actually has to produce. If it is board and compliance reporting, Power BI will handle it, and it is already included if you are on E5.
Frequently asked questions
What is utility asset management software?
Utility asset management software is the system of record for a utility’s physical assets. It holds the asset register, condition and inspection history, maintenance planning, work orders and the reporting built on top of them, so that information about what a utility owns and what it costs to run stops living in separate spreadsheets and disconnected systems.
Is EAM the same thing as a CMMS?
Not quite. A CMMS is built around maintenance work. An EAM covers the full asset lifecycle including capital planning and lifecycle cost. Most platforms sold to utilities now do both.
Can we run asset management on Microsoft 365 instead of buying an EAM platform?
Often, yes, and it is worth checking before you buy. Microsoft 365 E1, E3 and E5 include seeded rights to build Power Apps canvas apps and Power Automate flows over Microsoft 365 data such as SharePoint, which covers an asset register, mobile inspections and work order routing (Microsoft Power Platform Licensing Guide, August 2026). Power BI Pro comes with E5. Dataverse and other premium connectors need Power Apps Premium or Power Automate Premium on top, so a larger build does carry a licence cost. Silicon Valley Clean Water built a system of this kind and reported a 40% reduction in unplanned maintenance.
The honest caveats are that it has to be designed rather than switched on, deep real-time SCADA integration is more effort than a prebuilt connector, and you need either internal capacity or a support relationship to own it afterwards. What you get in exchange is a system that fits how your utility actually works, with the data in your own tenant and no per-user subscription attached to it.
How does utility asset management software work with GIS?
GIS usually holds the spatial record of where assets are, while the asset management system holds condition, maintenance history and cost. The two need to reference the same asset identifiers so a crew can move from a map to a work order without re-keying anything. Getting that identifier scheme consistent is normally the real integration work, not the connection itself.
Does our asset data stay in our own system?
That depends entirely on which route you take, and it is worth asking directly. With a vendor platform your asset data lives in the vendor’s environment under their terms. With a system built on your own Microsoft 365 tenant, it stays in infrastructure your agency already controls, which also simplifies public records and retention obligations.
Where to start
If you are early in this, do the register work before the demos. It is the one piece of the project that pays off no matter which way the decision goes, and it is the piece that most often decides whether the software you eventually pick does what you hoped.
If you want a view on what your existing Microsoft licences could already carry, that is a conversation worth having before the shortlist narrows.