Decision OS for the process industry
Every decision that keeps a plant safe and profitable: made by AI, verified by an engineer, scored by reality.
Give the process industry decisions it can act on: less risk, more knowledge, margins recovered, fewer surprises - AI deciding, engineers verifying, plants executing, reality keeping score.
We are starting with refineries. Today it runs on a refinery's integrity and turnaround decisions, from the exports a refinery already keeps. The process industry is the target; refineries are where it starts.
Monday 5 October. Seven decisions wait for an engineer. Two are due before Friday. One survey is planned later than half the remaining life of its worst point.
- Deferral Safe to defer the 14 locations on circuit C-104: nothing else was found counting on this work Waiting for J. Okafor Due Thu
- Turnaround scope In: the internal inspection of V-310 is statutory and due March 2027, before the 2027 turnaround Waiting for R. Mehta Waiting
- Rule check The survey of circuit C-212 is planned for May 2028. That is later than half the remaining life of its worst point. Bring it to October 2027 Waiting for J. Okafor Due Fri
- Recurring failure Six notifications and two failures on P-105 since 2024 are one recurring problem: seal flush lost on low suction pressure Waiting for A. Lindqvist Waiting
02 · Not a dashboard
A dashboard waits to be read. Decision OS has already decided.
Most software for a plant shows numbers and leaves the deciding to whoever is looking. The decision is made in a corridor, written nowhere, and never checked against what happened next. Decision OS makes the call, writes down why, and hands it to a named engineer to verify.
A dashboardWaits to be read
So - is it safe to defer? Somebody decides. Nothing records it.
Decision OSAlready decided
Deferral · C-104 · 14 locations
Safe to defer: nothing else was found counting on this work
The 14 locations have more than twice the remaining life needed to reach the 2029 turnaround at the long-term rate. No open promise, notification or strategy assumption names this circuit.
- The rate used is the long-term trend, not last year's
- No notification on C-104 since the last survey
- The 2029 turnaround date has not moved
Waiting for J. Okafor to verify · due Thursday
Verified, overruled, or still waiting. Reality scores it at the next survey either way.
03 · Made by AI
Eleven kinds of decision a refinery makes every week.
Each one is made from the plant's own records, written in plain words, and comes with what it rests on and what would change it.
- Needs the unit down, or notThis job needs the unit down; this one does not
- Operating limitThis is the limit for this circuit, from this page
- File mappingThis file is this kind of export and its columns map this way
- Turnaround scopeIn, out, or measure first, for each item on the list
- DeferralThis deferral is safe to make, or it is not
- Rule checkThis plan passes, or breaks, this rule
- Conflicting recordsThese two records cannot both be right
- Recurring failureThese events are one recurring problem; these are not
- Overdue promiseThis promise is overdue and this later event is the same problem
- Strategy basisThis strategy's stated basis no longer holds
- Approval reuseThis approval may be reused, or must be redone
04 · Verified by an engineer
Nothing counts until a named person has checked every item, or overruled with a reason.
Every decision arrives as one package, in seven parts. The engineer who verifies it is accountable for it, as the signer is today. An overrule is not a failure: it is recorded with its reason and scored by the same rule the system's call would have been.
- 1What is decidedOne sentence, in the plant's own words, that can be right or wrong.
- 2Why, in plain wordsThe reasoning an engineer can follow without opening the data.
- 3What it rests on - the records, by nameEvery reading, plan, notification and limit the call used, each one a link.
- 4What would change itThe facts that, if different, would turn the decision the other way.
- 5What to check before verifyingA short list the engineer ticks. Nothing is accepted with an item unticked.
- 6Who verifies, and by whenA named person, from the plant's own roles, with a date.
- 7How reality will score itWhat the next survey must find for the call to have been right.
1 · Decided
Safe to defer the 14 locations on circuit C-104 to the 2029 turnaround.
2 · Why
At the long-term rate of 0.21 mm a year, the thinnest of the 14 reaches its limit in 2034. Nothing open on this circuit depends on the work being done in 2027.
3 · Rests on
Thickness readings, 2019 to 2025Inspection plan, rev 7Notifications, C-104, none openTurnaround premise, 2029
4 · Would change it
A reading below 6.0 mm at any of the 14; a new notification on C-104; the 2029 date moving.
5 · Check before verifying
- The rate used is the long-term trend, not last year's
- No notification on C-104 since the last survey
- The 2029 turnaround date has not moved
6 · Verifier
J. Okafor, inspection engineer · due Thursday 8 October
7 · Scored by
The 2029 survey: every one of the 14 reads 6.0 mm or more.
05 · Scored by reality
Every call is written in advance, in a form the next reading can settle.
A prediction is not an opinion here. It says what will be found, where, and by when. When the survey comes back, the record scores it - right or wrong - and the plant learns which calls to trust and where the records were thin.
| Decision | Called | Found | Result |
|---|---|---|---|
| D-2023-041 · C-104 · point 7 | 6.2 mm | 6.1 mm | Right |
| D-2023-058 · C-118 · point 3 | 8.9 mm | 8.9 mm | Right |
| D-2023-097 · C-212 · point 12 | 5.4 mm | 4.6 mm | Wrong · circuit changed June 2022 |
| D-2023-133 · C-305 · point 1 | 11.0 mm | 10.9 mm | Right |
180 scored · 164 right · 16 wrong, every one on a circuit whose service changed in 2022 and whose records did not say so
06 · Your data
It starts from the exports a refinery already has.
Equipment lists, thickness readings, inspection plans, notifications, work orders, operating limits, the turnaround list. Nothing new to install on the plant. Each file is recognized by its headings, mapped once, and every row that cannot be read is set aside and named - never dropped quietly.
Must have
- Thickness readings
- Register of reading points
- Equipment and line list
- Turnaround work list
- Turnaround dates and criteria
Wanted
- Circuits and damage mechanisms
- Inspection plan and history
- Operating limits
- Notifications and work orders
- Temporary repairs
- Failures and leaks
- Deferrals, approvals and open actions
- Risk ranking
Nice to have
- Lab results
- Probe and sensor trends
- Process data for the limits
- Your own job costs and durations
- Line list and study assumptions
- The last turnaround's lists and criteria
- Who verifies what
Where it runs today
One host per plant, run by us, kept apart from every other plant: your exports and your record only.
Where it is designed to run
Inside your own network, on one host, with nothing leaving the plant. That is the shape the product is built for; ask us where it stands for your site.
07 · Security
Where it runs, and where the model runs. You choose both.
A refinery's security review asks two questions first: where does the software run, and where does the AI model run. Each has two answers, and the product supports both of each. What is in place today and what is designed but not yet stood up is said here as it is.
Where the software runs
Hosted by us Today
One host per plant on our cloud, kept apart from every other plant: your exports, your record, your address and certificate. Nothing shared between plants.
Your private cloud or data center Designed for
The same stack on one host inside your network, so nothing leaves the plant. Your connectors push outward from your side; nothing dials in. Scoped with your network team before anything is installed.
Where the model runs
A hosted model Today
The assistant uses a hosted model provider. What reaches it is the question and the passages of your records needed to answer it; nothing is used to train anyone's model.
A local model, inside the stack Supported
The same assistant on a model that runs on the same host, with nothing leaving it. Built and run; today it answers one question at a time, which suits a plant and not a crowd.
08 · See it on your plant
Refineries: send us the exports from one unit.
We show you that unit's decisions, waiting for your engineers, on your own data. You keep the record.
Not a refinery? We are starting with refineries, so please send no data yet. Chemicals, gas, fertilizer, power: write and say which plant you run, and we will tell you when it fits.