A row of horizontal centrifugal pumps on concrete plinths inside a pump house

One layer under all five.

The five products are not five businesses that happen to share a logo. They share a clock, a fleet, an asset graph and a set of models grounded in the same physics, and that shared layer is what turns five instruments into one operational picture.

The platform, in three layersThree stacked bands. The lowest is physical infrastructure, the middle is the five product families, and the highest is the shared intelligence layer. Vertical lines connect each product to the layers above and below it.PipeGuardPipe networksTrusted timeMachineGuardRotating machinesFleet and asset graphVisionGuardProduction linesPhysics-grounded modelsOTGuardOT networksEvidencePNTGuardPosition and timeAPIs
The three layers. Read it upwards: what exists in the plant, what we put on it, and what the platform does with what comes back.

What each layer holds.

THE INTELLIGENCE LAYER

  • Device identity
  • Trusted time
  • Edge computing
  • Secure communications
  • Fleet management
  • Asset graph
  • Physics-grounded models
  • Event correlation
  • Evidence
  • APIs

THE PRODUCTS

  • PipeGuard
  • MachineGuard
  • VisionGuard
  • OTGuard
  • PNTGuard

THE PHYSICAL WORLD

  • Pipelines
  • Rotating machinery
  • Production lines
  • Control systems
  • Substations
  • Vehicles and robots
  • Field personnel

One event, one record.

An anomaly on a line is not five alerts from five systems. It is one operational event with a position, a time, a classification, a corroboration and a route it travelled.

ProductDoesWhat that means here
PipeGuarddetectsAn abnormal acoustic event on a line, localised between two nodes.
PNTGuardtimestampsAgainst a clock that can say which source it trusted at that instant, so the localisation and the record agree.
VisionGuardinspectsDispatched to the position with its confidence attached, and returns a classification and not another alarm.
MachineGuardcorroboratesSays whether the pump feeding that line changed behaviour in the same minute, which turns a coincidence into a cause.
OTGuardmoves itCarries what is needed across the boundary and nothing else, with a record of what crossed and under which rule.

Every observation the platform produces carries five things with it: what measured it, when, against which clock, under which model version, and to what confidence. Strip one away and what is left is a number. Operators act on evidence, and those five fields are the whole difference between the two.

Talk to engineering.

Start from a specification, a drawing, an isometric or a photograph of what you are trying to instrument. The first questions are the same every time: what is in it, at what pressure, what it is made of, how long the run is, and what runs beside it that makes noise.