Leak Sight AI Incident

One incident keeps the evidence and the decision together.

Operators see the probable source, event progression, confidence, urgency, and recommended inspection step in one reviewable record.

Inspect the IncidentSee the Workflow
92%Model confidence
Incident record

Suspected steam leak

Valve V-204 · North utility loop

Review recommended · High severity

Incident Record

Evidence organized for operator review.

Leak Sight AI keeps the probable source, severity, confidence, supporting evidence, event progression, and recommended response in one traceable record.

High Severity

Suspected steam leak

Valve V-204 · North utility loop

92%Confidence
First Observed
Probable SourceValve packing

Evidence Reviewed

  • Thermal anomaly+18 °C above adjacent pipework
  • Visible plumePersistent across 47 seconds of video
  • Pressure deviationOutside the recent operating band
  • Event progressionPlume area increasing between observations

Event Progression

  1. Thermal difference detected
  2. Visible plume persists
  3. Pressure context supports review
Recommended Next Action

Inspect the valve packing and isolate the line according to the facility’s approved procedure.

Close-up of a red-handled metal valve and pressure gauge on exposed pipeworkNamed Asset

An incident stays tied to the valve, joint, or pump under review.

Location evidence matters because a process deviation may indicate loss without identifying the physical component maintenance should inspect first.

Photo: Shixart1985 · CC BY 2.0

Incident Anatomy

Every field answers an operator question.

The record is structured for assessment and handoff, not to make an alert look more certain than the underlying evidence.

01
Location
Ties the event to a monitored zone and named asset.
02
Evidence
Keeps the visual, thermal, sensor, and temporal observations together.
03
Severity
Helps the operator order review using facility-defined criteria.
04
Confidence
Shows the model confidence without presenting certainty.
05
Progression
Makes persistence and change visible across observations.
06
Recommended response
Proposes an approved next check without taking autonomous action.

Human Decision

The incident supports three clear outcomes.

Operator feedback remains attached to the event so future calibration can reflect real site conditions.

Confirm

Accept the event for inspection and route it into the approved workflow.

Dismiss

Mark a known false signal such as washdown, exhaust, or condensation.

Monitor

Keep the zone under review when evidence is incomplete or changing.

Pilot Qualification

Define what a useful incident looks like at your facility.

Use a pilot to agree severity rules, evidence requirements, operator feedback, and the maintenance export format.

Request a Pilot