Sewer Inspection Management Software: Build vs Buy for Utilities

What WinCan, ITpipes and Info360 Asset actually do well

The tools are not the problem in the way people assume, and a utility with one crew should not be reading this as a build pitch.

WinCan, ITpipes, POSM and CUES Granite XP are competent inspection software and each does what it was built for, which is capturing and coding an inspection in a truck, offline, in a basement, with a technician wearing gloves. WinCan has the widest install base among contractors and its coding interface is fast. ITpipes has done real work on getting inspections into the hands of the utility rather than leaving them on a hard drive. On the analysis end, Autodesk Info360 Asset models risk credibly and Esri ArcGIS carries your asset register and geometry properly. Automated defect detection from video, from providers such as SewerAI and VAPAR, has improved to the point where it is genuinely useful as a second opinion.

If you run one inspection crew on one package across a modest collection system, that stack is enough. Your operators code consistently because there is one of them, the format never changes, and a custom platform would be capital better spent on cleaning and root control.

The gap sits between the truck and the utility. Nothing in the list owns the pipeline from a contractor's raw deliverable, through validation against your register, through consistent scoring, to a rehabilitation decision you can put in front of a council or a regulator. Inspection software is for the truck. Condition assessment is for the utility, and it is a different system with different requirements.

Where they stop: 640 inspections and an asset register that disagrees

A collection system manager takes delivery of a hard drive. On it are 640 inspections from a contractor's spring campaign: one vendor's database, a folder of video totalling most of a terabyte, a photo folder, and a spreadsheet the project engineer made because upstream manhole identifiers were missing on 40 runs. Last year's contractor used a different package. The year before, a third. The asset register lives in the geographic information system and uses a segment naming convention none of the three followed exactly.

Inspection software validates within its own database, not against your register, because it does not have your register. So reconciliation happens when somebody loads the deliverable and starts finding mismatches, usually months after the crew left town and long past the point where a question can be answered by driving out there. Segments split when a manhole was added in 1996. Runs inspected in reverse with the nodes swapped. A lateral coded as a mainline. An identifier typed with a leading zero this time and without one last time.

The second gap is scoring. The Pipeline Assessment Certification Program from NASSCO gives the industry a shared defect vocabulary and a structural and maintenance grading scheme, and certification means an operator was trained. It does not mean two certified operators code the same pipe the same way. One records every root intrusion, another records the significant ones. One codes a joint offset at every joint on an old clay run, another summarises. The segment grades that come out are then compared as if they were measurements, so a scoring system built on rolled-up grades quietly ranks your pipes by which contractor inspected them.

The third is that a condition score is not a rehabilitation decision. A grade 5 in a 6 inch clay line behind a residential garage is a different problem from a grade 4 in a 36 inch interceptor under a hospital access road. Consequence of failure, groundwater conditions, whether the street is under a paving moratorium until 2031, and whether the pipe can be lined under ASTM F1216 or has to be dug all belong in the decision. Condition alone ranks pipes by how bad they look.

The arithmetic: cost per inspection versus a build

Price both paths per inspection accepted per year.

Take a system inspecting about 700 segments a year. Inspection software seats for staff review, say four at $4,500, is $18,000. Video storage and backup at your volume, call it $6,000. Then the line that dominates and never appears in a software budget: half an engineer at $115,000 fully loaded, spent reconciling deliverables, chasing missing identifiers and assembling reports, so $57,500. That is $81,500, or about $116 an inspection.

The build side is close to flat. A $280,000 phased platform amortised over five years is $56,000, support at 15 to 20 percent adds around $48,000, and storage is unchanged. Call it $110,000 a year. At 700 inspections that is $157 each, and it falls to $79 at 1,400.

So the crossover sits near 900 to 1,000 inspections a year, which for most utilities means a collection system beyond roughly 500 miles inspected on a ten year cycle. Below that, buy and be disciplined about naming conventions. Above it, the reconciliation workload grows with every campaign while the platform cost does not.

One condition overrides the arithmetic entirely. Under a consent decree you carry inspection mileage commitments, defect response times and rehabilitation volumes with stipulated penalties attached, and your reporting has to be provable rather than assembled. At that point the question stops being cost per inspection and becomes whether you can answer a question about programme progress on any given day rather than at report time.

What a custom condition assessment platform costs

From Digital Heroes delivery experience across more than 2,000 projects, a first release covering multi-format deliverable ingestion, validation against your asset register, raw observation storage with coding quality checks, and a versioned defect score per segment runs $65,000 to $140,000 and ships in 12 to 18 weeks. A full platform adding browser video streaming with observation seek, rehabilitation decision modelling with method feasibility, geographic project packaging, contractor performance tracking and consent decree reporting runs $160,000 to $400,000 phased over 6 to 12 months.

Data migration runs 10 to 25 percent of the build, and here it is the schedule risk rather than a line item. Loading historical inspections in three formats is parsing work you can estimate. Matching them to your register is not, because if a third of your segments cannot be matched confidently that is register cleanup, and it is real work by someone who knows the system.

Year two runs 15 to 20 percent of build cost annually. It pays for new exchange formats when a contractor changes package, coding standard revisions, storage growth, and the scoring logic being retuned as your engineers learn what actually failed.

What pushes cost up: the number of distinct inspection formats you accept. Video volume and retention policy, which drives infrastructure cost directly and should be decided at design rather than discovered in month eight. Manhole and lateral inspections alongside mainlines, which bring their own coding schemes. And integration with a work order platform and a hydraulic model if you want infiltration analysis connected.

The four situations where building wins

• Regulatory fit. The Clean Water Act makes sanitary sewer overflows an enforcement matter, and enforcement produces consent decrees specifying inspection mileage, response times and rehabilitation commitments with deadlines and stipulated penalties. Once you are under one, inspection data is evidence, and commitments tracked as objects with progress computed continuously from inspection and construction records is a different position from an engineer assembling a report from four systems every quarter.
• Scale economics. Past roughly 900 to 1,000 inspections a year, or a system beyond about 500 miles, the engineer time consumed by deliverable reconciliation exceeds an amortised build, and it grows with every campaign.
• A workflow that is your competitive advantage. Your local reasoning is not in any product: this basin surcharges in wet weather so infiltration matters more here, this material and vintage combination has failed early for us repeatedly, this corridor is under a paving moratorium so the window is now. Condition, consequence and opportunity as separate weighted inputs, with the reasoning visible per segment and every version of the ranking retained, is what turns a score into a defensible capital plan.
• Integration sprawl across three or more systems. Your asset register in the geographic information system, work orders in Cityworks or its equivalent, inspections in two or three contractor packages, video on a network share, and a hydraulic model. Once five systems describe one pipe, the engineer joining them is your condition assessment programme.

How to decide in a week, with last season's hard drive

Monday, take last season's deliverable exactly as the contractor sent it and count. How many inspections carry a segment identifier that matches your register exactly. How many match only after a human interprets them. How many cannot be matched at all. That third number is the project brief.

Tuesday, run a coding consistency check by hand. Pick twenty runs of similar material, diameter and vintage inspected by two different contractors, and compare observations per hundred feet. If one contractor consistently records twice as many, your priority list is ranking contractors rather than pipes.

Wednesday, time the video. Pick five defect observations from a report and see how long it takes an engineer to get the picture on screen. If the answer involves a hard drive in a cabinet or a phone call, your most expensive evidence is functioning as an archive nobody opens.

Thursday, put the same three exercises to every developer on your shortlist. Ask how they match a contractor's inspection to your register when identifiers disagree, and expect geometry matching, upstream and downstream node pairing, length tolerance and an exception queue. Ask whether they store raw observations or only rolled-up grades, because only the grades means you can never change your scoring logic without re-inspecting. Then ask about keyframe extraction and storage cost at your volume, since anyone who has not thought about it has not costed the platform honestly.

Friday, put the per-inspection arithmetic beside your decree commitments and decide. If it points to build, start with a paid discovery whose deliverable is a signed product requirements document covering the ingestion and matching rules, the observation and scoring model, the video retention policy and acceptance criteria. At Digital Heroes no code is written before that is signed, and you keep the document either way.

We are wrong for you if your asset register is the actual problem, because that is a survey and records engagement before it is a software one. We are also wrong if you want your work order system replaced, since we will tell you to integrate with it. Where we fit: more than fifty specialists, over 2,000 delivered projects, our own products including ShopScore, HeroCheckout and Section Vault, and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. You meet the named team before signing, and our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.