Is Ziptility an alternative to Info360 Asset?
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.
Does Ziptility do deterioration modeling like Info360?
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.