Info360 Asset is real, capable engineering software from Autodesk, the cloud successor to Innovyze's InfoAsset Planner (as of 2026-07-04, Autodesk has retired the Innovyze name into Autodesk Water Infrastructure). It does inspection management, condition assessment, risk scoring, and the deterioration modeling that drives a capital plan. It is built for the engineer, the modeler, and the consultant who do that analysis for a living.
If you are the operator who actually runs a small water or wastewater system, that is probably not you. You need the record those decisions come from to be something you keep current yourself, every day, from the field. Not something you pay an engineer to build and hand back every few years. Here is the honest difference, what we do not do, and where a small system is better off.
For a small operations team, yes, with one honest line drawn. Ziptility is where your crew builds and keeps the asset record live, so the capital plan is just ready when you need it. It is not engineer-grade deterioration modeling, and we do not pretend it is.
Think of it as two different jobs. Info360 is the analysis layer: feed it good data and it forecasts what fails when. Ziptility is the layer underneath it, where the data actually comes from. It is the map your operators pull up on a phone. Every main, valve, hydrant, pump, lift station, and manhole is on it, with the full work history attached to each one. The record stays current because the work rides on the asset. When your operator fixes a valve, he fixes it on the valve, so the history writes itself.
That covers the assets a small system runs. The standard template set includes distribution mains, service lines, curb stops, customer meters, and valves on the water side. On the sewer side: gravity mains, force mains, manholes, lift stations, and grinder pumps. Each one carries the fields you would expect, including install year, material, condition, and last inspection date. The point is not the field list. The point is simple. An operator keeps it true as a byproduct of the work, not by hiring an engineer to rebuild it from scratch on a contract.
No, and this is the line we will not cross. Ziptility does not run statistical deterioration curves, remaining-service-life forecasting by model, or hydraulic simulation. If you need a sewer-deterioration model that predicts which pipe fails in what year, that is Info360's job, and a good one. We are not that tool and will not claim to be.
What we do instead is simpler and built for an operator. Every asset can carry a criticality score right on the map. Your crew enters three things they already know: the year it was installed, its expected useful life, and how likely it is to fail. Those roll into a remaining useful life, a consequence of failure, and a 1-to-5 criticality score. It is a structured roll-up of your crew's own inputs, not a predictive model. The mains, valves, and other critical assets in the standard set carry a criticality field for exactly this. Paint the map by it and your worst, no-redundancy assets surface first. Nothing to model, nothing to maintain.
Here is the part worth saying plainly. The engineer's model is only ever as good as the record underneath it, and that record is your operators' field data. The engineer's reports are just the data your system is already producing, formatted in a good way. Ziptility is where that data gets built and kept honest. Info360 is where an engineer turns it into a forecast when a forecast is actually needed.
| Ziptility | ||
|---|---|---|
| Built for | ZiptilitySmall water and wastewater systems with a handful of staff | Info360 AssetThe engineer, the modeler, and the consultant who do analysis for a living |
| Who keeps it current? | ZiptilityYour operators, every day, from the field | Info360 AssetAn engineer builds it and hands it back every few years |
| Getting started | ZiptilityStandard water and sewer asset templates; the record fills in as the crew works | Info360 AssetFeed it good data; the model is only as good as the record underneath it |
| Work orders in the field | ZiptilityWhen your operator fixes a valve, he fixes it on the valve; the history writes itself | Info360 AssetInspection management, condition assessment, and risk scoring for the analysis |
| On a phone, in the field | ZiptilityThe map your operators pull up on a phone | Info360 AssetThe cloud analysis layer (Autodesk Water Infrastructure) |
| Pricing | ZiptilityOne yearly price by service connections, whole crew included | Info360 AssetQuote-based subscription with no public price; we will not guess at their number |
| The cost behind the cost | ZiptilityOwn the record live; a full operating setup runs in the low thousands a year | Info360 AssetThe engineer's plan is mostly your own data, formatted nicely, used once, and redone from scratch |
| Keep your current map | ZiptilityKeep your record current and feed your engineer better, fresher field data | Info360 AssetKeep Info360 for the modeling; the two jobs do not fight |
| Who actually uses it | ZiptilityThe operator who actually runs the system | Info360 AssetEngineers and consultants running deterioration models |
Info360 Asset is sold as a quote-based subscription with no public price. Trademarks belong to their owners.
Yes, and this is where a small system gets the most out of it. The same living record that your crew keeps current is the thing a capital plan is built from. Every closed job rolls up its real cost: parts pulled, equipment run, and labor at your own hourly rates. You can finally see what each asset actually costs you to keep alive. That is the number that builds an honest capital plan and backs a rate increase when the board asks why.
The deeper budgeting and funding side (rate impact, the cost roll-up across every asset, the funding-application angle) lives on our financial tracking page. If your real question is "can Info360 help plan capital improvement budgets," here is the honest answer. Info360 helps the engineer prioritize. That prioritization is only as good as the operating record underneath it. Keep that record live in Ziptility and the capital plan stops being a fire drill every few years.
You do not have to. This is the whole reframe, so here it is straight. An engineer's asset management plan is mostly your own data, formatted nicely, used once, and redone from scratch a few years later. That kind of study commonly runs $30,000 to $60,000, and it starts going stale the day they hand it over.
Own that record live instead. Depending on the utility, a full operating setup runs in the low thousands a year. It updates itself as your crew does the work. The plan is ready when the deadline comes, not a scramble you have to fund. When you genuinely need an engineer (for the modeling, the stamp, the funding submission), you hand them clean, current data. No paying them to go re-gather it first. Do not rent your own data back from a consultant every four years when you can keep it yourself.
Honest about scope: we are not an engineering analysis tool and we are not pretending to be. We do not do hydraulic modeling, statistical deterioration curves, or remaining-service-life forecasting. We make it easy for the guys in the field to log their problems and their fixes, and to hand that data to an engineer to plug into the models. Those models matter once every few years. Ziptility is for the people running the system every day.
No. Keep it. If an engineer is already running Info360 for your system, that is fine, and ripping it out is not the point.
The move is to stop being the bottleneck in their data. Keep the operating record current in Ziptility and feed your engineer better, fresher field data than they have ever had. Their analysis gets cheaper and sharper when the input is good, because they spend less time chasing down what is actually in the ground. You run the system day to day in a tool your crew will actually use from a phone. They do the modeling once in a while in the tool built for it. The two jobs do not fight.
For a small operations team, yes for keeping the asset record and the capital plan live yourself. No, it is not a replacement for engineer-grade deterioration modeling. Different jobs.
No. We do not run statistical deterioration curves or remaining-service-life forecasts. Your crew enters the install year, expected useful life, and likelihood of failure; those roll into a remaining useful life, a consequence of failure, and a 1-to-5 criticality score, painted on the map so the worst assets surface first. A structured roll-up of your crew's inputs, not a predictive model.
Yes. The living asset record plus the real cost rolled up on every closed job is what a capital plan is built from. The budgeting and funding detail lives on our financial tracking page.
No. Keep Info360 for the modeling. Keep your record current in Ziptility and feed your engineer better data, so their work gets cheaper.
One yearly price based on your service connections, with the whole crew included. No per-seat fee, and no $30,000-to-$60,000 study to redo every few years. Info360 Asset is sold as a quote-based subscription with no public price, so we will not guess at their number.