Public works and utilities leaders are the ones who defend a capital budget to a council or a board, and the quality of that defense rests on the data underneath it. When leaders evaluate software to support sewer capital planning, the most consequential decision is not a feature checkbox. It is whether inspection and risk modeling should live inside one bundled platform or be handled by two experts working together.
Why are inspection and risk modeling two different disciplines?
Because they answer different questions and demand different expertise. One captures the true condition of the pipe. The other decides what that condition means for risk, remaining life, and funding.
Inspection is the discipline of getting field condition right. That means accurate defect identification and consistent scoring against a recognized standard, specifically NASSCO’s Pipeline Assessment Certification Program, the coding framework known across the industry as PACP. Getting NASSCO-coded condition data right is its own craft, and it is what tools like ITpipes is purpose-built to do.
Risk modeling is a different craft entirely. It takes that condition data and calculates likelihood and consequence of failure, the two measures known in asset management as LOF and COF, then estimates remaining useful life, the years an asset has left in service, and turns the result into a prioritized, costed capital plan a governing body will stand behind. That work draws on hydraulic modeling, criticality analysis, deterioration science, and financial forecasting. A firm that innovates on it daily will produce a sharper answer than a module maintained on the margins of an inspection product.
When you trust the consequence and likelihood of failure data and recommendations coming from an inspection-only software, you risk inaccurate modeling driving real decisions, which produces a capital plan that does not match the true condition of the system.
The failure mode is quiet and expensive. When the modeling engine is a bolted-on afterthought, risk scores are only as strong as the add-on that generates them. Assets get ranked on thin logic, remaining useful life leans on generic deterioration curves instead of measured condition, and the resulting plan sends money to the wrong pipes in the wrong order.
For a director, the consequence lands in the room where it hurts most. A capital plan built on shaky modeling is hard to defend when a council member asks why a particular project ranks where it does. Overspending on assets that still have life, and deferring work on assets quietly approaching failure, both trace back to the same root cause, which is a model that was never the vendor’s real specialty. The stakes are concrete: the US EPA links aging, poorly prioritized collection systems to sanitary sewer overflows, the unpermitted releases of raw wastewater that regulators and ratepayers notice immediately.
One bundled vendor or two purpose-built partners: how do they compare?
Across the criteria that decide a capital plan’s accuracy and cost, two purpose-built partners lead a single bundled vendor on every row.
What should public works leaders look for in sewer capital planning software?
Look for measured condition at the foundation and dedicated modeling on top, with a clean, automatic connection between the two.
The strongest evaluations treat inspection accuracy and modeling depth as separate requirements, then insist that the two connect without manual rework.
- Ask whether field condition is scored to the NASSCO PACP standard.
- Ask whether the risk model is the vendor’s actual specialty or a feature added to close a deal.
- Ask whether the two systems sit on a shared platform so data flows automatically instead of through a spreadsheet.
The case for keeping these disciplines independent is laid out in the ITpipes guide to why inspection hardware and software should be independent, and the same logic extends from hardware and software to inspection and modeling. Sound capital planning also aligns with how the EPA frames asset management for water and wastewater utilities, which puts condition-based prioritization at the center of responsible investment.
How do ITpipes and Aquanuity turn condition data into a capital plan?
ITpipes captures NASSCO-coded condition, and that data flows automatically into Aquanuity’s AquaTwin Asset model, which ranks risk, calculates remaining life, and builds a prioritized, costed plan traceable back to the inspection.
The ITpipes and Aquanuity partnership is the concrete proof of the two-expert approach, and it works because both companies are built on the same ground. NASSCO-coded condition data, defect detail, structural and operational scores, and the underlying inspection video move directly from ITpipes into Aquanuity’s AquaTwin Asset platform, which runs natively on Esri ArcGIS Pro, the same Esri ArcGIS foundation ITpipes is built on. Because the two share that foundation, the inspection data lands in the map the team already uses, geolocated to the right asset, with no manual export, reformat, or re-entry.
From there the modeling experts take over. AquaTwin Asset combines the ITpipes condition scores with hydraulic performance and consequence-of-failure data to rank assets by likelihood and consequence of failure, calculates remaining useful life from real inspections rather than install dates, and builds prioritized, costed capital projects. The output is a set of defensible numbers, from five-year tactical plans through longer strategic forecasts, every dollar traceable back to the inspection that informed it. Inspection findings stop living in spreadsheets and start driving a capital strategy a city council, board, or regulator will stand behind.
The point is to keep each expert to what they do best. Leave the likelihood and consequence of failure modeling to the people who innovate on it daily, and leave the inspection workflow to the people who understand it best. Your capital plan ends up more accurate because it is built on measured condition and a purpose-built model, and it usually costs less than a single vendor’s promise to do all of it.