INTEGRATION

Add an investigation layer without rebuilding your automation stack.

RootTruth™ is being designed to work around the PLCs, cameras and on-site infrastructure already running your operation, with vendor-neutral connectivity and local-first deployment at the centre of the architecture.

REFERENCE ARCHITECTURE

Existing systems in. Synchronized evidence out.

PLC / CONTROLOPC UASelected tags, states and triggers
VIDEORTSP / ONVIFExisting or dedicated IP cameras
EVENT CONFIGRootTruth rulesTriggers, capture windows and evidence sets
→
RootTruth SERVERCapture · Synchronize · StoreRolling buffers, event correlation, case evidence and APIs
→
WINDOWS CLIENTInvestigate locally
FUTURE / OPTIONALWeb · Cloud · APIs

This represents the intended product architecture. Exact deployment sizing and supported device combinations will be validated against each site as the product matures.

01

OPC UA-first

RootTruth™’s primary controls integration is designed around OPC UA so it can work across mixed PLC environments without forcing a customer into one automation vendor.

02

RTSP / ONVIF video

Standard IP camera protocols are the target approach so suitable existing camera infrastructure can be reused where practical.

03

Local-first operation

Core event capture and investigation should continue on site without relying on a permanent internet connection.

04

Configuration-led deployment

Machines, events, cameras and tags are intended to be configured rather than custom-coded for every standard deployment.

WHAT RootTruth DOES NOT REPLACE

Keep the systems that already run the plant.

RootTruth™ is not intended to become the PLC, HMI, SCADA, historian or CCTV system. Its job is to bring the relevant evidence from those environments into a purpose-built investigation workflow.

PLCHMISCADACCTV / IP VIDEOHISTORIANCMMS / OTHER SYSTEMS

A STANDARD DEPLOYMENT

Designed to become repeatable, not bespoke forever.

01

Connect

Establish RootTruth™ access to the relevant PLC endpoint and camera streams within the customer’s approved network architecture.

02

Browse & select

Select the tags, event conditions and cameras that matter for each machine or system.

03

Configure

Set event logic, pre/post windows, correlation behaviour, case rules and notification preferences.

04

Validate

Use a controlled test trigger to confirm timestamps, evidence capture and replay before activation.

05

Operate

RootTruth™ then waits for configured events and automatically preserves the investigation evidence.

LOCAL DATA. CUSTOMER CONTROL.

Designed for industrial environments where data location matters.

The core deployment philosophy is local-first: event evidence can remain on customer-controlled infrastructure, with optional cloud-enabled capabilities introduced separately where the customer wants them.

On-premises capableCore capture and investigation without continuous internet dependency.
Named user accessRole-based access and auditability are part of the product direction.
No automatic machine controlRootTruth observes, records and supports investigation; it is not intended to command PLC outputs as part of the standard evidence workflow.

SITE DISCOVERY

What we would review before deployment.

PLC connectivity

Controller types, OPC UA availability, network route and the event/tag scope required.

Camera environment

Existing IP cameras, stream compatibility, retention expectations and where new cameras may be useful.

Server / VM capacity

Expected event volume, video load, storage window and deployment location.

Security requirements

Network segmentation, user access, retention policy and customer IT/OT standards.

YOUR ENVIRONMENT

Tell us what PLCs, cameras and systems you already run.

We can use that information to shape a pilot or deployment approach around the environment you already have.