See a trip coming before it stops a unit.
Track vibration, temperatures, seal and lube oil data against each machine’s own history, and plan the fix before it fails.
Turn unplanned stops into planned onesOil, gas & chemicals
Keep the complex running, unit by unit.
Refining, petrochemical and chemical units, utilities, tank farm and flare, brought into one live twin of the site. See which equipment puts output at risk, what a security alert touches, and where energy and gas are lost.
Critical equipment protectedCompressors, pumps and heaters, with risk valued in money and downtime
Security in contextAn alert names the unit and equipment it affects
Flaring and energy tracedFlare, fuel and steam linked back to their source
One meaning per tagThe same definitions across units, DCS and historian
01The complex
The whole site in one twin, not one unit at a time.
Built from the DCS, SCADA and plant historian you already run. We connect over OPC UA or Modbus, or from historian exports, with nothing installed on your controllers. Each tag is mapped once, so a reading means the same thing in every unit.
Process units
Crude, conversion, petrochemical and chemical units, with their compressors, pumps, heaters and exchangers.
Site utilities
Steam, power, fuel gas, cooling water and air, and which units draw on them.
Tank farm
Tank levels and transfers between units, storage and dispatch.
Flare
Flare flow and the relief and vent sources that feed it.
02Security
Know what a security alert puts at risk.
VeldtGraph watches control network traffic passively, so nothing is added to the control path. Every alert is joined to the twin, so your team sees the unit and equipment it affects, not just two network addresses.
The twin knows
Controller CC-201↓Hydrocracker unit↓Recycle gas compressor train↓Anti-surge control
The network shows
Controller CC-201↓New connection, never seen before↓Unknown host on the plant network
What your team sees
Hydrocracker recycle compressor controller talking to an unexpected host.Priority set by the equipment at stake, so operations and security see the same alert together.
Designed to support operators’ IEC 62443 programs.
03Decisions
From signal to a decision worth making.
Every recommendation shows the data behind it and what is at stake in money and downtime. Operators approve every action.
Fix the pumps that matter most first.
Link each pump’s condition to the unit it feeds and to its spare, so the crew starts where the most output is at risk.
Repair lists ranked by value at riskCatch heater fouling and hot spots early.
Compare tube temperatures, draft and fuel use with design and history, and see what the drift costs in fuel and run length.
Heater drift valued in fuel and downtimeRespond first to what touches production.
Rank security alerts by the unit and equipment behind them, and give operations and security one shared view.
Alerts ranked by operational impactTrace every flare event to its source.
Line up flare flow with relief valves, unit upsets and compressor trips, so each event has a cause and an owner.
Flare events linked to the unit behind themSee where fuel and steam go.
Balance steam, fuel gas and power across units, and find the users and losses that cost the most.
Energy and steam use per unitStart with one unit.
Then extend the same definitions across the complex.
A focused first engagement, measured against your own baseline.
- We map one unit’s DCS tags, historian data and critical equipment with your team.
- We agree one outcome and a baseline, for example compressor availability or flare events.
- The first unit goes live, then the same model covers the next units and utilities.
First results in 2 to 4 weeks. You decide on rollout after you see them.