Skip to content
Koidra
Book a demo

AI insights

Predix

Reports that say what changed and what to do next, and early warning of a failing machine.

Monday starts with the decision instead of the spreadsheet, and a failing bearing becomes a repair you booked rather than a line that stopped.

How it works

What Predix produces, and what you put in From unified operational data, Predix produces daily and weekly reports that say what to adjust or keep, and maintenance work orders raised when an asset is due. Your team acts on them and sets the targets, which shape what is measured. Unified operational data Daily and weekly reports what to adjust, or keep Maintenance work orders raised when an asset is due Your team acts, and sets the targets arrives on its own your targets
Predix works on the unified operational data from DataPilot and Maintenance Management, measured against the targets you set.

What it takes over from

  • The weekly report someone rebuilds by hand every Monday
  • Asking three people what happened last week
  • Waiting for a consultant to say what to change
  • A separate condition-monitoring tool whose alerts never become a work order

Pays for itself by

Putting the numbers and the recommended change in front of the Monday meeting, so the hour goes to deciding. Catching a failing bearing early enough to replace it on a planned stop, before it stops the line.

The number a buyer checks: Hours a week spent building reports, and hours of unplanned downtime.

Reports that arrive automatically

What Predix sends from unified operational dataFrom unified operational data, Predix sends daily and weekly reports that summarize the past period and recommend what to adjust or keep, and opens an inspection or repair work order when an asset is due for maintenance.Unified operational dataDaily and weekly reportswhat happened, and what to adjust or keepPredictive maintenancean inspection or repair work order, opened when an asset is due
Each report covers the past day or week and recommends what to adjust, or what to keep. Daily and weekly are the same report at two speeds. We shape them with your team, around the decisions each role makes.

Grounded in physics and in your own data

Predix runs models grounded in the physics of your process on your own data. What it recommends has been checked against how the plant behaves.

What goes into a Predix reportTwo ingredients go into Predix, your plant's own data and the physics of how your process behaves. What comes out is the daily and weekly report on what changed and what to do about it.Your plant's datareadings, operator entries,maintenance historyPredixHow your process behavesthe physics behindyour numbersYour daily and weekly reportwhat changed,what to do about it
A language model alone can describe your numbers. Predix computes against the physics behind them, so a recommendation can be a better way to run, such as a setpoint to move or a changeover to reschedule, as well as a repair.

Predictive maintenance

When an asset is due, Predix opens the inspection or repair work order itself. Three signs it watches for:

A sensor that has stopped changing

The machine is running, but the reading holds perfectly still. The sensor is failing, not the process.

Then: An inspection of the instrument, not another process alarm.

Two signals closing on each other

Neither is abnormal alone. Dryer exhaust temperature is closing on the dew point, which brings condensation and buildup.

Then: Maintenance booked before the buildup becomes a larger problem.

Slow wear against the machine's own history

Vibration climbs for days and never crosses its alarm limit.

Then: A maintenance task raised against the machine's own baseline, before it turns critical.

How a failure announces itself for weeks A vibration trend over several weeks, drawn as a sawtooth. Each cycle climbs as dust builds on the rotor, drops when the machine is cleaned, and starts the next cycle higher than the last. An alarm threshold runs across the top of the chart. Every individual peak sits below it until the final one crosses, at which point the machine fails, even though the trend had been rising for weeks. alarm threshold cleancleancleanclean it breaks week one week six Vibration, cleaned four times, never investigated once
Each cleaning brings the vibration down, but the crack underneath stays, so it comes back higher every time. Four work orders, each closed on its own. The vibration trend that linked them was one no maintenance system was watching.

Where this sits

You can start with Maintenance Management or with DataPilot. Predix needs both.

  1. Start here

    Maintenance Management

    Work orders, preventive maintenance, asset records and spare parts, on the phone your technicians already carry.

  2. Start here

    DataPilot

    Every signal the plant produces, in one place, live and historical.

  3. AI insights

    Predix

    Reports that say what changed and what to do next, and early warning of a failing machine.

  4. Autonomous control

    KoPilot

    Closed-loop control of the process, minute by minute, with no human at the panel.

On top of this sits KoPilot, scoped against the process it runs.

Includes Maintenance Management + DataPilot.

See Koidra on your own plant data

Bring a week of readings from one line. We will show you what the platform sees, what it would have flagged, and what it would have scheduled.

Book a demo