VVRS Video Verification and Reliability System Request a demo

Your sensors report.
VVRS confirms.

IP cameras watch your equipment in visual, infrared, thermal and acoustic modes. AI compares what they see with what your SCADA tags say, and tells you when the two disagree.

Witness
Four camera modes, one platform
Check
Every observation against a live tag
Output
Verified or deviation, inside your SCADA
P-101 IR 41 °C terminations nominal VIS NO LEAK guard in place ACU 2× BPFO outer-race defect tone VT-101 2.1 mm/s SCADA · casing vibration PT-101 4.2 bar SCADA · discharge THM 91.3 °C outboard housing TT-101 62.4 °C inboard RTD ΔT +28.9 °C TT-101 unverified
EVT P-101 · 2026-09-07 03:14:07 · 7 tracks · 2 deviations Illustrative event, synthetic data

A wired sensor knows one point, through one path

TT-101 is a resistance thermometer on the inboard bearing of pump P-101. It reports 62.4 °C, steady for fourteen hours. SCADA shows a healthy tag. Nothing in that number can say whether the outboard bearing, two feet away with no sensor, is running at 91 °C.

  • TT-10162.4 °Cbearing temperature, inboard RTD
  • VT-1012.1 mm/scasing vibration, overall RMS
  • PT-1014.2 bardischarge pressure
  • FT-1180.0 m³/hdischarge flow, reading frozen since 02:41

Every one of these tags is a single measurement carried through a single path: a probe, a termination, a cable, an input card, a scaling block. Each step can drift, foul, loosen or freeze, and the tag keeps reporting a plausible number.

A flat line is either healthy or dead. The tag cannot say which. FT-118 has read zero for half an hour while the pump is audibly moving fluid. Your alarm list shows nothing, because nothing in it can disagree with the sensor.

VVRS gives the plant a second witness that does not share the sensor's path.

Four ways of seeing the same machine

One IP camera platform, four sensing modes. Each catches a class of failure the wired sensors cannot, and each is checked against the tags that should agree with it.

Thermal

Catches. Temperature distribution across the whole housing, not one point where an RTD happens to sit.

What the wired sensor missed. The inboard RTD reads 62 °C. The outboard bearing, with no sensor, is at 91 °C.

Where the witness and the tag meet

Every camera observation lands against the SCADA tag it should agree with. Agreement is recorded quietly as a verified reading. Disagreement stacks up as a deviation, with the evidence attached, before any wired alarm would have tripped.

Event log · P-101 · 2026-09-07 Illustrative event log, synthetic data
Time Tag SCADA value Witness Observed Result Confidence
03:14:07 TT-101 62.4 °C THM 91.3 °C outboard DEVIATION
03:14:07 VT-101 2.1 mm/s ACU 2× BPFO tone DEVIATION
03:14:07 PT-101 4.2 bar VIS no leak, steady shaft VERIFIED
03:14:07 no tag IR terminations 41 °C VERIFIED
02:58:30 LT-204 71 % VIS sight glass ≈ 70 % VERIFIED
02:41:12 FT-118 0.0 m³/h VIS + ACU shaft turning, flow noise DEVIATION
02:30:00 TT-101 62.1 °C THM 63.0 °C inboard VERIFIED

Confidence is written as line weight. A thick line means several modes and a long baseline agree on the reading. A thin line means one mode, or a short history.

Deviation names both sides. The reading, the witness, and the gap between them, so the operator can decide whether the asset or the instrument needs attention first.

Joins the SCADA you already run

VVRS does not replace your control system or ask operators to watch another screen. Verified states and deviations arrive inside the SCADA you already operate, next to the tags they refer to.

Cameras are a data source, like any other instrument on the network. Their observations become values your system can trend, alarm on, and write to the historian. The difference is that these values were produced by a different physics, on a different path, and were compared to your tags before they arrived.

Integration is scoped with your controls team: which tags are covered, how verified and deviation states are exposed, and where an evidence frame is stored for the work order.

Supported SCADA platforms and protocols: to be confirmed

ALARM SUMMARY · AREA 100 03:14:09
TimeTagStateValueVerification
03:14:07TT-101NORMAL62.4 °C UNVERIFIED · THM +28.9 °C
03:14:07VT-101NORMAL2.1 mm/s UNVERIFIED · ACU defect tone
03:14:07PT-101NORMAL4.2 bar VERIFIED · VIS
02:41:12FT-118NORMAL0.0 m³/h UNVERIFIED · frozen tag
02:58:30LT-204NORMAL71 % VERIFIED · VIS
Illustrative alarm summary. Your HMI, your tags, one added column.

Two witnesses that fail differently

A second sensor of the same kind shares most of the first one's weaknesses. A camera shares almost none of them. That is what makes agreement between the two worth more than either reading alone, and disagreement the earliest warning you can get.

Failure modeWired sensorCamera witness
Calibration drift Affected Independent
Probe fouling or coating Affected Independent
Loose termination, wiring fault Affected Independent
Fault outside the sensor's location Missed Whole housing in view
Frozen or stuck value Looks like a steady reading Motion and sound show the true state
Line of sight blocked Unaffected Affected
Lens fog, glare, contamination Unaffected Affected

Different physics, different path. A resistance thermometer measures contact temperature through copper. A thermal camera measures emitted radiation through air. For them to lie the same way at the same time, two unrelated things have to go wrong at once.

Agreement earns trust. When the camera witness confirms a tag over days of operation, that tag has been checked by something outside its own loop. Your existing sensors become more reliable without being touched.

Disagreement points somewhere. Either the asset has a problem the sensor cannot see, or the sensor has a problem the plant cannot see. Both are worth a work order, and VVRS tells you which one to write.

Request a demo

Tell us about one asset you wish you could see. We will walk through what the four modes would catch on it, and how the verified states would land in your SCADA.

  • A live event display on a comparable asset
  • Integration walkthrough with your controls team
  • No changes to your existing instruments or logic
Form endpoint: to be connected