How it works

One unit, one workflow, and the message that reaches the console.

The rtOpX platform page covers what the diagnostics are. This one covers what actually happens: what the system finds on a live column, how a HazOp study becomes a console message, and who ends up reading it.

rtOpX

On one unit

Eight things wrong at once, each one named

This is a single distillation column running normally — no alarm has tripped. rtOpX is reporting eight developing conditions simultaneously, and for each one it names the equipment, the probable cause, and which diagnostic layer found it.

TOWERDRUMHXCHXRFEEDVENTOVHDBTMSSTMCONDTTI3003PPDI3001LLC3002FFC3004FFC3003PPC300112345678
  1. 1

    Instrumentation issues

    SCD

    Transmitters reading outside their expected relationship with the rest of the unit.

  2. 2

    Valve sticking

    SCD

    Reflux control valve no longer responding proportionally to controller output.

  3. 3

    Exchanger fouling

    EKM

    Overhead condenser duty drifting away from its clean-condition model. Needs cleaning.

  4. 4

    Controller PV vs SP

    SCD

    Process value not tracking set point — the controller, the valve, or the measurement.

  5. 5

    Pump cavitating

    EKM

    Motor current signature and suction conditions consistent with cavitation.

  6. 6

    Column mass balance problem

    EKM

    Feed in and products out no longer reconcile against the column model.

  7. 7

    Plugging starting to occur

    EKM

    Pressure drop rising against flow — a restriction forming in the bottoms circuit.

  8. 8

    Exchanger efficiency declining

    EKM

    Reboiler transferring less duty for the same steam rate.

None of these are alarms. Every one of them is a condition that would eventually become an alarm — or an incident — if nobody acted on it first.

Workflow

From HazOp study to console message

The knowledge that defines an abnormal situation already exists inside your organization. The workflow is how it gets from a binder to the operator's screen — every time, on every shift.

YOURoperatingintellectualpropertyOperatorknowledgeHazOp & operatingproceduresHSEproceduresAdvanced applications(MVC, etc.)BestpracticesEngineeringknowledge
Knowledge Models capture what the organization already knows — from HazOp studies, procedures, and the judgment of experienced operators — and hold it as a live asset rather than a binder on a shelf.
  1. 01

    Identify the conditions

    Abnormal situations are defined from HazOp/FMEA studies, operating experience, process models, and existing operating procedures.

  2. 02

    Apply multi-variant logic

    Logic is applied across many inputs at once so an event is detected early — long before a single-parameter alarm limit would trip.

  3. 03

    Associate root cause

    Nexus SCD and equipment diagnostics run alongside the detection logic to attach a probable root cause to the event.

  4. 04

    Apply the best response

    The 'best' best-practice response is drawn from the client's own operating intellectual property and presented with the diagnosis.

  5. 05

    Deploy and leverage

    The same operating IP reaches operators, shifts, units, and the wider enterprise — consistently, every time.

And then it reaches everyone at once

Your operating IPdeployed once, leveraged everywhereOperatorsthe console,in real timeShiftsthe same answerat every handoverUnitsone model library,many unitsEnterprisesite-wide andcorporate-wide
The same diagnosis and the same recommended response reach every audience simultaneously — which is what makes the answer consistent across shifts rather than dependent on who happens to be at the console.

Deployment

Who sees it, and what they see

Direct operator support

The console operator sees the event, the diagnosis, the explanation, and the recommended action — in one place, in the language of the unit.

  • Prioritized message board, ranked by severity
  • Plain-language explanation of what the system observed
  • Best-practice recommended response, drawn from your own procedures
  • Trend, cause, and document links one click away

Support for the organization

Process control, reliability, and operations management work from the same models and the same evidence the operator sees.

  • Engine Explorer for model configuration and tuning
  • Indicator and equipment libraries shared across units
  • Common evidence base for post-event reviews
  • Site-wide and corporate-wide rollout from one framework

The sensor diagnostics behind this still run today.

Findings 1, 2 and 4 on the column above came from Sensor & Controller Diagnostics — the module now delivered through VALID8A.AI as real-time process sensor data validation.

Continue to VALID8A.AISee measured results