PipeLens

Pipeline integrity intelligence

See the failure while it is still a warm patch of sand.

PipeLens turns drone, satellite and SCADA data into findings an engineer can verify, a risk score they can defend, and a work order the field can act on — with the evidence for every step kept next to it.

Drone RGB · change against the last flightThermal · radiometric, in °CSatellite · corridor revisitsSCADA · pressure and flow

How it works

One pipeline, from raw frame to closed repair

Nothing jumps a stage, and nothing is actioned without a human. That is the whole design: the machine measures and ranks, the engineer decides, and the system learns from the decision.

  1. Data intake

    Drone RGB and radiometric thermal frames, satellite revisits and SCADA tags land through connectors — or a CSV, when that is what the field has.

  2. AI analysis

    Detectors measure rather than guess: hotspot delta in °C, change against the previous flight, vegetation encroachment, corrosion, objects in the right-of-way.

  3. Risk triage

    Each finding moves a segment's score across five weighted factors, four for probability of failure and one for consequence.

  4. Maintenance

    A verified finding raises a work order with a recommended action and a due date, then follows a state machine the field cannot skip steps in.

  5. Learning

    Every verify and reject is a label. Precision per detector is measured, and the site classifier is retrained on your engineers' own decisions.

Why it holds up

Built to be argued with

An integrity decision has to survive a regulator, an incident review and the engineer who disagrees with it. Every number here can be traced back to what produced it.

Evidence you can open

A finding is not a row in a table. It carries the frame it came from, the overlay, the cropped evidence and the measured value that triggered it — so a reviewer can disagree with it on the merits.

Overlay · crop · measured delta · model version

A score that reads line by line

Risk is 100 · Σ wᵢ·fᵢ over five named factors. Every score stores its model version and each factor's contribution, so it can be defended in an audit years later.

Versioned weights · stored contributions · full history

Honest about what it does not know

An uninspected segment carries risk for being uninspected. A detector without its model says so instead of failing quietly, and a connector missing its credential names the variable it is waiting for.

No silent degradation

5

stages, from raw frame to closed work order

6

connectors: drone, GIS, CMMS, SCADA, satellite, AI

100%

of findings carry their own evidence

1

outbound path, and it is optional: the AI gateway

Where it runs

Your data stays where your pipeline is

PipeLens runs on your own infrastructure: the API, the vision worker, the database and the storage volume are containers you host. The map draws from your own geometry rather than a tile server, and the detectors work with no network at all. The one outbound path is the AI gateway that writes plain-language explanations — leave its key empty and the explanations become deterministic instead of missing.

Open the console

A new account can read the network — segments, findings, risk and the maintenance board. An administrator grants engineer or field access from there.

PipeLens · pipeline integrity intelligenceInspections · AI findings · Risk · Maintenance