Equipment and control-loop performance, watched against what it should do.

Pumps drift off their curves and valves stick long before anything trips. Cyzag Intelligence watches each one against what it should do and prices the gap.

Delivered by Cyzag Operations Cyzag Intelligence

Book a working session → What it does

Analysis · Evaporation · 7 days

AI summary Since Monday, FIC-220 has started to oscillate and EV-201 steam per tonne is 8% above normal.

EV-201 steam per tonne

C-210 temperature gap

FIC-220 flow

FIC-220 valve position

Control-loop check · FIC-220

Oscillation Yes, about every 4 min

Saturation No

Valve or tuning Valve problem more likely

Charts on one grid, with a control-loop check open on FIC-220

What it does

Six things it does.

Built with Analysis workspace Cause-and-effect flow Process diagrams Historians

Equipment against its design curve

Pumps, compressors and exchangers against the curve they were bought to.
Control loops and valves

Oscillating loops and sticking valves, found and priced.
Instruments that freeze or drift

Flat-lined or drifting measurements flagged before they mislead.
Alarm floods, grouped

A few incidents instead of forty alarms, each with its first alarm named.
Equipment out of service

See what goes unwatched while equipment is out.
One set-up, every site

Set up an equipment type once, reuse it on every site.

How it works

How it works, in four steps.

1 Read-only connections bring in the historian tags for the equipment, loops and instruments.
2 Enter design curves once per equipment type, or pick a good period.
3 The engine watches each asset, prices the gap and proposes the likely cause with its evidence.
4 Your people confirm the cause; a named owner approves the fix.

Who does what

Cyzag Operations → Findings arrive in the shift and open a root-cause workflow with the crew's own record attached.
Cyzag Intelligence → Watches equipment, loops and instruments against their design curves and learned normal, and prices the gap.

Where it runs

Read-only connections to your historian, MES and SAP
Deployed on site or in your own tenant
Configured by your engineers, with no code
An audit trail on every record

What it connects to →

Questions

What buyers ask us.

Do we need a first-principles model or a digital twin?

No. The expectation comes from what you already have: the equipment's design curves, a good period of its own history, or a mass or energy balance.

Which equipment does it cover?

Rotating equipment such as pumps and compressors, heat exchangers, control loops, valves and instruments, wherever the historian holds the measurements.

Does it change setpoints or tuning?

No. Cyzag never writes to your control system; connections are read-only. Findings and drafted actions go to people, and nothing changes without a named person's approval.

How is a finding different from an alarm?

An alarm says a limit was crossed. A finding says a unit has departed from what it should be doing, what that is costing and what most likely caused it, often long before any limit is reached.