How does a living map work instead?
You do not work a flyover. You work the map. In Ziptility the work is assigned to the asset on the map. Every leak, valve turn, and inspection logs right where it happened.
Here is the loop. Your assets start as gray dots from whatever you already have, paper maps, an old shapefile, a meter spreadsheet. Every time a crew member is out there working a ticket or marking an 811 locate, they confirm a dot and fill it in: a photo, a depth, a material, a fix. Over a year, the locates and repairs you already do quietly turn your old paper into a real database. Everything the crew does in the field adds something to the map or corrects something on it. That is the mechanism, and over time the record gets more and more filled in.
That is the whole idea behind Ziptility. The map updates as a byproduct of the work your crew already does, not as a project you have to find time for. Picture an operator on valve maintenance. He logs what he would note anyway, the number of turns, how hard it was to turn, the condition. That rolls straight up to the valve on the map. He did not stop to do data entry. He did valve maintenance, and the record updated itself. Ten small tasks a day across the crew builds a serious data set. Nobody ever sits down to a data project. You already have enough to do.
Can Ziptility log pipe and manhole inspections?
Yes, but as work-management cycles attached to the asset on the map, not as an aerial-defect-scoring engine. A manhole inspection, a CCTV run, a valve exercise, or a hydrant flush is a task on the asset. When the crew closes it, the condition and notes log to that asset's record, where the next person can pull them up.
Be clear on the boundary so you do not buy the wrong thing. Ziptility is not a CCTV video-coding or NASSCO-PACP scoring engine, and it is not an aerial-defect-detection tool. CCTV video is linked to the asset, not hosted inside the app, which keeps the map fast even with no signal in the field. The win is the living record the crew keeps current, not a better camera or sensor. The deeper pipe-inspection workflow lives on our wastewater inspection page.
We had our system flown with a drone. Do we have to start over?
No. Keep what the flight found and bring it in. If a drone flight is genuinely the right tool for one job, a hard-to-reach tank roof, an after-storm look at a lagoon, fine, fly it. Then bring what you learn into Ziptility as part of the asset's living record: a photo on the tank, a note on the lagoon, a follow-up task on whatever needs work. It does not go stale in a folder, and you do not have to rip anything out. You give the one-time picture a place to live where your crew actually works.
Honest about scope: we do not fly drones and we do not capture or analyze aerial imagery. That is Scopito's lane, and for power lines, wind, solar, and telecom it is a good one. We are the ground-level living map and the work record for a small buried water or wastewater system. We concede the air openly, because conceding it is what makes the ground-level argument true.
What does Ziptility cost compared to Scopito?
One yearly price, set by your number of service connections, with no per-seat fee. The whole crew gets it on a phone, not one license on the office computer. Scopito does not publish prices. Third-party reporting (G2, accessed 2026-07-04) describes pay-per-asset pricing across several editions, roughly EUR 6 to EUR 80 per asset depending on the asset type, with unlimited free users and no monthly subscription required. That shape fits an inspection campaign you price per asset, not a buried system your crew works every day.
The bigger cost is the one you cannot see on an invoice. A $28,000 flyover you cannot edit is money spent on a picture you cannot work. A living map you keep current yourself is a few thousand a year and gets better every week.