Cyzag
Estimate leak

The platform

We map your plant. Everything else runs on the plant model.

One model of your plant, fed read-only by your systems. Cyzag Operations runs the shift on it; Cyzag Intelligence finds what it is costing.

Book a working session → See what it covers
Cyzag on a desktop, laptop, tablet and phone: plant key metrics, a parameter drill-down, the shift logbook with the safety cross, and a live trend

Trusted by

  • Nobian
  • Nouryon
  • Perstorp, a subsidiary of PETRONAS Chemicals Group
  • Stolt Tankers (Stolt-Nielsen)
  • Deutsche Gasrußwerke

The plant model

Your systems feed two products, and a person approves every action.

Read it from the bottom: your systems feed it read-only, the crews record onto it, and every action waits for a person.

CYZAG

What you get

  • Costed flags Ranked by cost, each naming its most likely cause.
  • Likely causes The likely cause, its evidence, and what else was checked.
  • Step-by-step workflows Your procedures, step by step, signed off by a person at each gate; AI can gather and draft along the way.
  • Cited answers Every claim clicks through to its reading or record.
  • Knowledge kept The settings and fixes that live in people's heads, written down against the equipment.
  • Alarm floods Forty alarms become a few incidents, first alarm named.
  • Mass and energy A loss shows as a gap before the month-end report.
FLAGS · each with its most likely cause
ACTIONS · each needs a person's approval

Cyzag Intelligence · finds what is costing you money, and finds the cause

The plant model Every asset, reading, record and past fix, linked into one model of the plant.
The engine Learns your normal, watches equipment, loops and instruments for drift, prices what matters and proposes the likely cause.
Agents A role plus the read-only tools it may use. They gather evidence and draft the action.

Cyzag Operations · runs the shift · a product in its own right

ShiftRoundsImproveOEEProcess EfficiencyQuality & Care Handovers, rounds, investigations and quality, recorded as the crews work.

read-only · nothing migrates · nothing replaced

Your systems, as they are

Historian and sensors Your historian: trends, setpoints, alarms.
Lab and quality Results and specifications, against the process.
Maintenance and procedures Work orders, equipment history, procedures, documents.

Two products

Start with either. The decisions stay separate.

Most plants start with one and add the other. Neither requires the other.

Shift board · Day shift

Log entries

10:39 EV-201 steam per tonne high Deviation
09:15 P-301 vibration checked, logged Routine

Tasks

Weekly 5S, control room Open
Shift OEE categorisation Open

Inspection rounds

Daily walkdown, unit 2 Open
Manual readings, unit 2 Closed

Shift sign-off

Signed in 09:00 · Day shift lead Note: reactor to finish at 15:00

Cyzag Operations

Runs the shift

Six modules your crews use every shift: Shift, Rounds, Improve, OEE, Process Efficiency, Quality & Care.

Cyzag Operations →
Ask the plant

Which equipment is costing us most this week?

EV-201. Steam per tonne is 8% above normal, about €21 an hour 1. It started after the cleaning interval moved from four to six weeks 2; the root-cause analysis confirms it 3.

  1. Flag EV-201, week 28
  2. Logbook, 14 March: cleaning interval changed
  3. Root-cause analysis, EV-201

Cyzag Intelligence

Finds what is costing you money, and finds the cause

Prices what is drifting and proposes the likely cause, with its evidence.

Cyzag Intelligence →

Solutions

Eleven ways to use it, on one plant model.

Each delivered by Operations, Intelligence or both. Start with the one that costs you most.

Run the shift
Find and fix losses
Keep what your people know
All solutions →

Industries

Built for operations that run around the clock.

In production on chemical plants and at sea, and built for any operation that runs shifts.

Chemicals and process

In production

Nobian · Nouryon · Perstorp · Deutsche Gasrußwerke

Continuous and batch plants, from salt and chlor-alkali to specialty chemicals and carbon black.

  • Shift handover and daily meetings
  • Variable cost: energy, steam and raw materials
  • OEE and loss accounting
  • SPC and batch records

Shipping

In production

Stolt Tankers

Chemical tankers at sea, with one improvement system across the fleet.

  • PDCA and improvement across a fleet
  • Rounds and checks offline, without signal
  • Handover between rotating crews
  • Inspection and vetting evidence, ready on board

Also built for

  • Pharmaceuticals
  • Food and beverage
  • Oil and gas
  • Energy storage and terminals
  • Logistics and distribution
  • Packaging
  • Utilities
  • Pulp and paper
  • Textiles
  • Mining and metals
  • Cement and building materials

Connections

Connects to what you already run.

Read-only. Nothing is written to your control system, and nothing migrates.

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.

Safe by design

If you have been burned by an AI project before, read this.

Every figure links to the reading behind it, and nothing changes in the plant until a named person approves it.

  • The numbers are never guessed

    Every figure comes from the engine. The AI writes the words, never the numbers.

  • Every answer shows its sources

    Each claim links to the reading, log entry or investigation behind it.

  • People decide, always

    Cyzag never writes to your control system. Nothing closes an action or changes a record without a named person's sign-off.

  • Your data stays yours

    On site or in your own tenant. Nothing you record trains anyone else's system.

For your IT and OT teams

What it touches, where it runs, and who sets it up.

  • Never writes to your control system

    Read-only connections. Your historian, lab and maintenance systems stay the systems of record.

  • Configured, not coded

    Your engineers set up forms, workflows and objectives themselves.

  • One set-up, every site

    Standardise across sites and regions, in your crews' languages.

  • Desk, tablet and phone

    The same records everywhere; rounds and forms work offline.

  • An audit trail on everything

    Every entry and change time-stamped and attributed.

  • Seven tiers, documented

    The architecture is below, for the technically curious.

The seven tiers, for the technically curious

Each tier stands on the one below. Most plants start low, with the plant model, because it is the cheapest thing to prove.

Each tier builds on the one below

  1. 7
    Outcomes Cited chat · flags with their cause · one-click briefings · actions drafted for approval and recorded in Cyzag
  2. 6
    Monitors When a condition is met, investigate, then act, with approval. The Objective Engine lives here.
  3. 5
    Teams & workflows Teams of agents that test a cause from several sides · step-by-step processes with human sign-off
  4. 4
    Agents A role plus a set of tools: the basic worker
  5. 3
    Grounded search + tools Cited search over the plant model, and the tools agents are allowed to use
  6. 2
    The plant model Every asset, reading, record and past fix, linked: a knowledge graph of the plant
  7. 1
    Data and connectors Historian · handovers and rounds · investigations · lab · maintenance, work orders and procedures
Citations everywherePeople approveNo-code set-upSecurity & governance

Outcomes and new work flow back into the data, so the system keeps itself current.

Start here

See it work on your own plant in ten weeks.

Clear success measures. Fixed scope and fee. No licence commitment until the results speak for themselves.

Book a working session → Explore the pilot