SCADA/Historian Connectivity & TSDB
Gets the live sensor data out of the control system safely and stores it at full resolution, which almost nothing else on this site does.
Watches the control network passively for devices, traffic and commands that should not be there.
Most control networks have no inventory of what is connected to them and no record of normal traffic. A new engineering laptop, a modified controller program or an unexpected command sequence is invisible until something breaks.
Passive traffic monitoring via SPAN ports builds an asset inventory and a baseline of normal protocol behaviour per device, then alerts on new assets, protocol anomalies and unauthorised programming commands. Monitoring is strictly passive — no active scanning of production controllers, ever — and zones follow the Purdue model with IEC 62443 conduit definitions.
Passive monitoring sees only what crosses the monitored segments; an attack contained within an unmonitored cell is invisible, and serial and fieldbus links below the monitored layer are generally not covered. This is detection, not prevention, and it does not remove the need for segmentation, hardening and access control.
Every capability page states a real limitation. If a vendor cannot tell you where their product stops, you are not being told the truth about where it starts.
Gets the live sensor data out of the control system safely and stores it at full resolution, which almost nothing else on this site does.
One room, and one screen layout, where production, drilling, maintenance and HSE see the same numbers at the same time.
Adds optical gas imaging and flame detection on camera to the fixed point detectors, so a leak between detectors is still seen.
Builds a methane inventory from measurements rather than from emission factors, at the level of detail OGMP 2.0 actually asks for.
Flies or drives the inspection route so that people do not have to work at height or enter confined spaces as often.