Everything from us
Cyzag Operations and Cyzag Intelligence together, end to end.
Operations + IntelligenceThe pilot
Ten weeks, fixed scope: from first data to first findings.
Find your number
What's your plant leaking, roughly?
Three sliders, thirty seconds, an honest first estimate. The ten-week pilot makes it precise, finding by finding, in your own numbers.
Estimated annual leak €1,500,000
Per hour €171
An estimate only, based entirely on your assumptions above. The engagement replaces this estimate with a ranked list of specific, evidenced findings, each priced from your own data.
Bring this number to a thirty-minute working session.
Book a working session →- Weeks 1–3
Connect
We map the plant and connect your historian and records, read-only.
- Weeks 4–9
Find & value
The engine learns normal, finds what is drifting, proposes the cause and prices it.
- Week 10
The readout
Findings and plan handed over, with the system live.
What it asks of you
- Read-only access to the historian and the records you already keep.
- A few hours a week from one or two engineers who know the plant, to review findings as they appear.
- Success measures agreed before week one.
- Nothing replaced, migrated or switched off.
It suits a continuous or batch process plant with a process historian, a cost that matters (energy, steam, raw materials or throughput) and an engineer who will own the findings. If that is not you yet, the first call will say so.
Yours to keep, in writing
Three things you own at the end, whatever you do next.
- 01
The costed leak list
Every finding priced per hour and per year, with its likely cause and evidence.
- 02
The payback-ranked plan
The fixes in order of return, in your numbers.
- 03
Your data, findings and confirmed causes
Your data, every finding and every cause your people confirm are yours. The software stays ours, and keeps running if you take a licence.
What it costs
One fixed fee, agreed before week one and sized to the plant. No licence unless the readout shows the numbers hold.
Ask for the figure on the first call. The costed list, the plan and your data are yours either way.
Not ready for a call?
Take the one-page summary, what it does, what the ten weeks deliver and what it asks of you, to your plant manager or your finance director first.
Cyzag on one page →How we count value
Four numbers, kept apart.
The readout reports each finding at the stage it has reached, so an estimate is never presented as a saving.
- 1
Estimated opportunity
A drift priced from your cost data. An estimate, with its assumptions.
- 2
Verified loss
Checked by your people, with the cause confirmed.
- 3
Implemented action
Approved by a named person and carried out.
- 4
Realised saving
Measured against the baseline. Only this counts as money saved.
Three ways in
The buying decisions stay separate.
Keep your own systems
Keep the historian, maintenance system and tools you already run. Cyzag Intelligence reads from them, and nothing is replaced.
Your systems + IntelligenceStart small, grow later
Start with Cyzag Intelligence; add Cyzag Operations later if it earns its place.
Intelligence → + OperationsWe work with whatever you already run. Cyzag Operations stays a separate decision, made on its own results, never a condition of entry.
What it connects to
Historians
- AVEVA PI
- GE Proficy Historian
- Aspen IP.21
- Canary
- TimescaleDB
- InfluxDB
MES and ERP
- AVEVA MES
- Proficy Plant Applications
- aspenONE
- SAP
Data and reporting
- Microsoft SQL Server
- Microsoft Azure
- Power BI
- Power Apps
Anything else, including other ERP, MES and safety systems, through the REST API.
The six questions we always get.
What do we have to integrate before this works?
Nothing moves. Cyzag reads from the systems you already run. The historian comes first, then the records your shifts keep, your lab results, your maintenance system and your procedures. Connections are read-only, and Cyzag never writes to your control system. Your systems remain the systems of record. Your historian stays. SAP stays. Nothing migrates.
Do we need data scientists to run it?
No. Agents are configured, not coded: a role, and the set of tools it is allowed to use. Set-up is no-code, so a process engineer changes a form, a threshold or a workflow the week they need it, without a ticket, a vendor or a release window.
How is this different from dashboards and copilots?
A dashboard is a system you query: you ask, it answers, and a person still has to notice the problem, work out what it costs, dig for the history, write the action and chase it. Cyzag is a system that does work: an engine watches the plant model, puts a price on what's drifting, proposes the most likely cause and puts the flag in front of the right person. The thinking and the legwork no longer fall on your busiest people.
What happens to our data?
Deployed on site or in your own tenant. Each customer's plant model is its own; nothing you record ever trains anyone else's system. Every action is time-stamped and traceable.
How fast do we see something real?
The pilot is ten weeks, fixed scope, from first data to first findings. Weeks one to three map the plant, connect your historian and records and check the model with your people. Weeks four to nine learn your plant's normal from its own history, then surface and price what is drifting and propose the likely cause, reviewed with your people as it appears. Week ten is the readout: the costed findings and the plan, with the system running on your own data.
Can our people override it?
They have to. Agents draft; your team approves. Cyzag never writes to your control system, and nothing closes an action or changes a record without a named person's sign-off. Every answer cites its sources, and every figure is computed by the engine rather than composed by the AI.
Every figure links to the reading behind it, and nothing changes in the plant until a named person approves it.
Book a working session
Bring a real problem from last week.
Thirty minutes with someone who has worked in process operations, not a scripted product tour. If it is a fit, you leave with a scope and a price. If it is not, we say so.