HOW RootTruth WORKS

From a machine event to an evidence-led engineering decision.

RootTruth™ is designed to preserve the moments engineers normally miss, synchronize the evidence around them, and carry the investigation through to a documented and verifiable improvement.

THE EVENT JOURNEY

Five steps. One continuous investigation record.

01

Detect

A configured PLC condition or machine event qualifies as something RootTruth™ should preserve.

TRIGGERPLC condition · Fault · Quality event · Generic machine state
02

Capture

Rolling video and PLC buffers preserve the evidence before and after the event instead of starting only after the alarm appears.

EVIDENCEVideo · Digital tags · Analogue signals · Event context
03

Synchronize

RootTruth™ aligns the evidence on a common timeline and correlates related events so engineers can follow the sequence.

CONTEXTPrimary event · Sub-events · Signal transitions · Video
04

Investigate

The engineer reviews what changed, identifies the first meaningful cause and records the conclusion, resolution and actions.

WORKFLOWCase · Root cause · Resolution · Confidence · Actions
05

Verify & learn

Higher-tier workflows compare recurrence after the fix and retain the closed case as reusable engineering knowledge.

IMPROVEMENTEffectiveness · Recurrence · Reliability insight · Knowledge base

BEFORE. DURING. AFTER.

Capture the event window, not just the alarm.

The most useful evidence often appears before a fault bit becomes true. RootTruth™ is designed around rolling buffers so the pre-event sequence can be preserved alongside the event itself and the recovery that follows.

  • Configurable pre-event history
  • Configurable post-event recording
  • Event-specific cameras and PLC signals
  • Correlated events reuse the same evidence window where appropriate
PRE-EVENTEVENTPOST-EVENT
Evidence is preserved around the event trigger instead of beginning at the moment an engineer opens the software.

PRIMARY + SUB-EVENTS

Keep the sequence. Avoid chasing symptoms.

When several alarms appear within seconds, the first meaningful event can easily be buried by everything that follows. RootTruth™’s correlation model is designed to preserve the order and group related events into one investigation context.

10:24:18.420Product sensor blockedPRIMARY
→
10:24:18.610Conveyor stoppedSUB-EVENT
→
10:24:18.900Drive faultSUB-EVENT

THE INVESTIGATION RECORD

Capture the conclusion as carefully as the evidence.

Root cause

Record the underlying cause, not just the first alarm somebody noticed.

Resolution

Document the repair, control change, maintenance action or process change that addressed it.

Confidence

Mark conclusions as Confirmed, Highly Likely, Suspected or Unknown instead of presenting uncertainty as fact.

Verification

For Intelligence workflows, compare recurrence after the action and determine whether the improvement actually held.

THE CLOSED LOOP

A solved event becomes an asset for the next engineer.

EVENT→EVIDENCE→ROOT CAUSE→ACTION→VERIFICATION→KNOWLEDGE

RootTruth™ is designed so investigation history becomes searchable engineering knowledge rather than disappearing into shift notes, messages or individual memory.

SEE THE WORKFLOW

Bring us a real machine event and walk through how RootTruth would investigate it.