Most utilities come at asset management backwards. They start by looking at software, sit through demos, and then try to reverse-engineer a program to fit the tool they picked. It is the wrong order, and it is why so many asset systems end up as expensive inventories nobody trusts.
Asset management for water and wastewater utilities is a discipline first and a piece of software second. Before any tool matters, a utility has to answer a small set of questions about its own system, and the good news is that most of the data needed to answer them can live in tools the utility already owns.
This guide walks the recognized framework for a utility asset management program, then shows where each part actually lives in practice.
What is asset management for water and wastewater utilities?
Asset management for water and wastewater utilities is the practice of managing physical infrastructure to deliver a required level of service at the lowest lifecycle cost, using data on asset condition, criticality and cost to decide what to maintain, rehabilitate or replace and when.
The EPA and the American Water Works Association frame it around five core questions every utility should be able to answer. They are the backbone of any real program:
- What is the current state of my assets?
- What is my required level of service?
- Which assets are critical to sustained performance?
- What are my minimum lifecycle-cost strategies?
- What is my best long-term funding strategy?
Notice that not one of those questions is about software. They are about knowing your system. The software comes in only to hold the answers and keep them current.
The program comes before the purchase
Here is the trap. A utility feels the pain of aging pipes and reactive repairs, decides it needs asset management software, and buys a platform. Then it discovers the platform is an empty shell until someone answers the five questions, and answering them is months of work the software cannot do for you.
A tool can store your condition data. It cannot decide what condition means for a 60-year-old force main versus a 5-year-old pump. It can hold a criticality score. It cannot tell you which assets, if they failed tomorrow, would put you in violation or in the newspaper. Those judgments are the program, and they are what turn an asset list into an asset management plan.
Utilities that answer the questions first get two things. They get a plan that any competent software can then support, and they get clarity on what they actually need the software to do, which usually turns out to be far less than the all-in-one demo suggested. That is the same lesson behind the buy-versus-build decision in our guide to utility asset management software: the register and the plan are the asset, the tool is just where you keep them.
Where each of the five answers actually lives
The framework is well established. What almost no one tells a utility is how ordinary the tooling for it can be. Here is where each answer tends to live once you stop assuming you need a dedicated platform to begin.
| Core question | What it needs | Where it can live |
|---|---|---|
| Current state of assets | A register with condition and age | SharePoint or Dataverse, fed by mobile inspections |
| Required level of service | Documented targets and standards | Shared documents plus reporting |
| Asset criticality | A scoring model per asset | A structured field on each record |
| Minimum lifecycle cost | Cost and maintenance history tied to assets | Records linked to finance data |
| Long-term funding | Capital plan built on the above | Reporting into the capital improvement plan |
Read the criticality row first, because it is where programs stall. Criticality is a judgment your staff make, not a number a vendor supplies, and it is the single most valuable field in the whole system. A modest tool with a well-argued criticality model beats an expensive platform with an empty one every time.
You do not need the software to start the program
The most useful thing to know is that the first phase of an asset management program needs almost no new software at all.
If your utility runs Microsoft 365, you already have what it takes to begin. SharePoint and the Power Platform can hold the asset register and the condition data, and E1, E3 and E5 include seeded rights to build Power Apps and Power Automate over SharePoint (Microsoft Power Platform Licensing Guide, August 2026). Power Apps can put an inspection form on a phone so condition data comes off paper. Power BI, included with E5, can turn all of it into the funding picture the board and the state want to see.
A deeper build using Dataverse does carry a licence cost through Power Apps Premium, but by the time you need that, you have a real program driving the requirement rather than a vendor driving the purchase. Starting on what you own means the program leads and the software follows, which is the order that works.
EQUIPMENT INFORMATION MANAGEMENT
Want to start the program on tools you already own?
Nexinite builds the asset register, condition capture and criticality scoring into the Microsoft 365 you already pay for, in your own tenant, so the program can start before you commit to a platform.
When to bring in an engineering firm
Building the program on your own tenant does not mean doing it alone. There are points where outside help is the right call.
Condition assessment at scale. Inspecting and scoring buried infrastructure is specialized field work, and an engineering firm often does it faster and more defensibly than internal staff. Nexinite works alongside firms like Carollo and Tanner Pacific for exactly this reason.
Criticality and risk modelling for large systems. A big utility with thousands of assets may want an engineering partner to build the risk model, then hold the result in a system it owns.
Regulatory-driven planning. When the program has to satisfy a specific state framework, a firm that knows that framework can shorten the path.
The distinction worth holding onto is that consultants help you answer the questions, and the system you own holds the answers. Do not let the two blur into a dependency you cannot maintain.
How one utility connected the plan to its capital budget
Silicon Valley Clean Water shows what the finished shape looks like. Its asset data was scattered across financial systems, project management tools and SCADA, so the lifecycle-cost and funding questions were impossible to answer with confidence. Nexinite built an equipment information management system on the Microsoft stack SVCW already licensed, organising assets into process areas and linking operations and maintenance data to capital planning.
According to Nexinite’s published case study, the result was a 40% reduction in unplanned maintenance and an estimated 20% saving in operational costs, with capital planning now informed by real data. The detail is in the SVCW case study, and the same link between asset data and the budget is the heart of capital improvement planning.
Frequently asked questions
What is asset management for water and wastewater utilities?
It is the practice of managing infrastructure to deliver a required level of service at the lowest lifecycle cost. It uses condition, criticality and cost data to decide what to maintain, rehabilitate or replace and when, and it is built around five core questions about the current state of assets, required service levels, criticality, lifecycle cost and long-term funding.
What are the five core questions of asset management?
What is the current state of my assets, what is my required level of service, which assets are critical, what are my minimum lifecycle-cost strategies, and what is my best long-term funding strategy. The EPA and AWWA use this framework as the foundation of a utility asset management program.
Do we need software to start an asset management program?
No, and starting with software is usually a mistake. The first phase is answering the five questions, which is judgment and data work, not a tool. If you run Microsoft 365, you can hold the early register and condition data on SharePoint and the Power Platform using rights you already have (Microsoft Power Platform Licensing Guide, August 2026), then decide what dedicated software, if any, you need once the program is real.
What is asset criticality?
Criticality is a judgment about how much an asset’s failure would hurt, in service, compliance or cost. It is scored per asset by your own staff, and it is the most important field in the system because it drives where maintenance and capital money should go first.
Should we hire an engineering firm?
Often for condition assessment, risk modelling on large systems, or regulatory-driven planning. The rule of thumb is that consultants help you answer the questions while the system you own holds the answers, so you keep the program in-house afterward.
Where to start
Answer the five questions before you shop. The current-state register and a real criticality model are the foundation, and both can start on tools you already own. Software chosen after the program is defined will always fit better than a platform bought before it.