ITpipes API · Data and Workflow Gateway
Connect Your Sewer Inspection Data to Your System of Record
Condition data that reaches the people planning the work and defending the budget.
Your inspection program produces the most detailed record your utility has of what is happening underground. The ITpipes API puts that record into the systems where the decisions get made: the asset management system your crews work from, the warehouse your analysts query, and the model behind your capital plan.
The case for connecting
Six Things Your Program Stops Doing By Hand
Every one of these is work someone on your team is doing today with an export, a phone call, or a login they should not need.
Operations and Public Works
Engineering and Condition Assessment
Data, Reporting, and IT
Capital planning
The Detail That Carries a Capital Plan Through Budget Review
A rating tells you a pipe scored a 4. An observation tells you what is wrong with it, where along the run, and how bad. The ITpipes API returns the observations.
What every inspection carries
- NASSCO pipe ratings calculated by ITpipes, so your team does not recompute them: OPR, SPR, and MPR, and up to six more
- Which ratings you receive depends on what your inspection template defines, which is set by what matters to your team
- Video and images on the paged inspection list, each with a file name and a media URL
What every observation carries
- Its NASSCO code
- Its severity grade
- Its distance along the asset
At budget time that detail does the arguing for you. A rehabilitation list built on defect level records, carried straight from the inspection system into the report your council sees, answers why this pipe and why this year without anyone rebuilding the case by hand.
It compounds over time. Every inspection your crews run adds to a record that your condition models, your risk scoring, and your rehabilitation ranking can read directly from CoreVision. The value of the program you have already paid for goes up each year the data stays connected, rather than aging inside an export somebody made once.
The API returns the underlying records at full detail, and your systems decide what to do with them. No summary layer sits in between deciding what you get to see.
Access control
Give Visibility.
Keep Control.
The split is deliberate, and it is what makes the rest of this page safe to act on. A utility can give read access to a consultant, a dashboard, or a business intelligence tool without giving anyone the ability to change what the crew recorded. The record of your network stays the record of your network.
Read key
Goes to whoever needs the data
Assets, inspections, observations, defect filters, completion checks. Read-only: it cannot create or change anything in ITpipes.
Write key
Stays with your team
Creating assets and inspections, and setting the work-order fields. Issued separately, for the systems that drive the work-order loop.
The platform
Your Full Sewer Inspection Suite
The API connects all of it outward. Capture the inspection in the field, manage it in the office, let AI take the first pass at coding, and run the whole program as a single system of record.
NASSCO-compliant inspection capture in the field, online or offline, by your own crews or your contractors.
Step 2 · In the office
Manage, analyze, report, map, and share every inspection. This is the page you are on.
Step 3 · In the review
AI-assisted defect coding takes the first pass, and your NASSCO-certified coder confirms, corrects, or rejects every observation.
All of it, connected
Field and office deployed together as one connected system of record, from the camera to the capital plan.
Questions
Frequently Asked Questions
Resources
Keep Reading
Ready to Open the Gateway
We turn on access and issue the keys, and your team sets up the data flow into the systems you already use.
