Equipmate
Request a pilot

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.

Decision OS keeps what your plant knows: every decision, its reasons, who verified it and how it turned out, scored against what happened next, so decisions stay consistent across shifts and operations and the methods that hold up are the ones it keeps.

We are starting with refineries. Today it runs on a refinery's integrity and turnaround decisions, from the exports and documents a refinery already keeps. The process industry is the target; refineries are where it starts.

Today Harrow Point Refinery · an illustrative plant

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
Reality keeping score 180 calls settled by the last survey · 164 right · 16 wrong, all on four circuits changed in 2022

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

C-104 minimum wall6.1 mm
Corrosion rate0.21 mm/yr
Next survey2027-05
Work orders open14

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 commitment, 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

Fifteen 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 else was considered.

  1. Needs the unit down, or notThis job needs the unit down; this one does not
  2. Operating limitThis is the limit for this circuit, from this page
  3. Uploaded file's columnsThis file is this kind of export and its columns map this way
  4. Turnaround scopeIn, out, or measure first, for each item on the list
  5. DeferralThis deferral is safe to make, or it is not
  6. Rule checkThis plan passes, or breaks, this rule
  7. Conflicting recordsThese two records cannot both be right, an inspection report and the inspection data included
  8. Recurring failureThese events are one recurring problem; these are not
  9. Overdue commitmentThis commitment is overdue and this later event is the same problem
  10. Inspection strategy basisThis strategy's stated basis is for an engineer to review
  11. Temporary repair approvalThis approval may be reused, or must be redone
  12. Lapsing recordsThis certificate, relief valve test or assessment has lapsed or lapses before the next shutdown, or this study is past its date
  13. Change without follow-throughThis change took effect and nothing since shows anyone looked at what it does
  14. Finding responseThis finding needs monitoring to this date, investigating by this date, or repairing by this date
  15. History notes with no readingThis history note sits at a point with no thickness reading since it was written; measure it and add a reading point

Where a circuit has a damage mechanism and no operating limit on file, the product says what to limit. It knows seven refining mechanisms: sulfidation, hydrochloric acid corrosion, naphthenic acid corrosion, ammonium bisulfide corrosion, ammonium chloride corrosion, sour water corrosion and erosion-corrosion. For any other mechanism it names the circuit and says it does not know what to limit. An operating limit whose figure differs from the one in its own source document goes to an engineer, with both figures and the page.

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.

  1. 1What is decidedOne sentence, in the plant's own words, that can be right or wrong.
  2. 2What else was consideredEach alternative, and why it was not chosen. There is always at least one.
  3. 3Why, in plain wordsThe reasoning an engineer can follow without opening the data.
  4. 4What it rests on - the records, by nameEvery reading, plan, notification and limit the call used, each one a link.
  5. 5What it is worthThe value in the plant's own units. Where the data cannot support a figure, the decision says so instead of estimating.
  6. 6What a person must verifyWhat to check, how, who, by when, what the decision becomes if a check fails, and the risk. Nothing is accepted with an item unticked.
  7. 7How reality will score itWhat the next survey must find for the call to have been right.
Decision D-2026-118 · Deferral · C-104 · Harrow Point, illustrative

1 · Decided

Safe to defer the 14 locations on circuit C-104 to the 2029 turnaround.

2 · Also considered

Survey the 14 in 2027 as planned. Not chosen: the thinnest reaches its limit in 2034, so a 2027 survey adds a shutdown task without changing the call.

3 · 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.

4 · Rests on

5 · Worth

14 locations off the 2027 turnaround list, with the scaffolding and insulation work they need. No hours or cost: this plant's records do not hold them.

6 · Must verify

  • 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

If any check fails: the decision becomes not as it stands, and C-104 goes back on the 2027 list.

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.

Verify Overrule, with a reason Either way it is scored.

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.

Record Harrow Point Refinery · illustrative · one survey's closeout
DecisionCalledFoundResult
D-2023-041 · C-104 · point 76.2 mm6.1 mmRight
D-2023-058 · C-118 · point 38.9 mm8.9 mmRight
D-2023-097 · C-212 · point 125.4 mm4.6 mmWrong · circuit changed June 2022
D-2023-133 · C-305 · point 111.0 mm10.9 mmRight

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 and documents a refinery already has.

Equipment lists, thickness readings, inspection plans, notifications, work orders, operating limits, the turnaround list, the registers of statutory certificates and relief valves. Exports and documents go into one drop area. Nothing new to install on the plant. Each export is recognized by its headings, mapped once, and every row that cannot be read is set aside and named - never dropped quietly.

Must have

  1. Thickness readings
  2. Register of reading points
  3. Equipment and line list
  4. Turnaround work list
  5. Turnaround dates and criteria
  6. Statutory certificates register
  7. Relief valves and their tests

Wanted

  1. Circuits and damage mechanisms
  2. Inspection plan and history
  3. Operating limits
  4. Notifications and work orders
  5. Temporary repairs
  6. Failures and leaks
  7. Deferrals, approvals and open actions
  8. Risk ranking
  9. Recommendations
  10. Design basis
  11. Desalter readings

Nice to have

  1. Lab results
  2. Probe and sensor trends
  3. Process data for the limits
  4. Your own job costs and durations
  5. Hazard study assumptions
  6. The last turnaround's lists and criteria
  7. Who verifies what
  8. Corrosion probe readings
  9. Thickness sensor readings
  10. Feed quality
  11. Operator log
  12. Alarm journal

Documents are read, and checked against the exports

A plant sends sixteen kinds of document, listed below. Each is filed against its row in the plant's document list. Every document goes to the assistant, which answers questions from it and cites the page. Inspection reports are also read for their facts. Statutory certificates, relief valve records and fitness-for-service assessments are read for the date each one lapses. Every fact keeps the sentence it came from and its page. The other documents are optional: the decisions are still made without them. Each night the inspection reports are compared with the inspection data, in code. Where they disagree, an engineer decides which is right; the decision is signed, kept on the record and scored. The file the plant sent is never changed. A scanned PDF is turned into text by the product itself, on its own host. A lapse date read from a scan that is still ahead is not relied on until a person confirms it.

Must have

  1. Statutory certificates
  2. Relief valve test and overhaul records
  3. Fitness-for-service assessments
  4. Inspection reports

Wanted

  1. Risk-based inspection studies
  2. Equipment data sheets and nameplates
  3. Thickness survey reports
  4. Corrosion control documents and damage mechanism reviews
  5. Integrity operating window documents
  6. Repair and alteration records
  7. Isometric drawings with monitoring locations

Nice to have

  1. Manufacturer's data books
  2. Corrosion loop and circuit drawings
  3. Welding procedures and qualifications
  4. Material verification (PMI) reports
  5. Piping material specifications

Inspection reportRead when it arrives

Tag11-C-101
Inspected10 Mar 2024
Inspect next by9 Mar 2028
Readings12 points

Every fact keeps the sentence it came from and its page. A fact that is not written in its own sentence is not kept.

Decision OSTwo records disagree

Conflicting records · 11-C-101

The report and the inspection history give different next inspection dates

The report says, on page 1: "Re-inspect internally by 9 Mar 2028." The inspection history gives 9 Mar 2029 for the same inspection. Hold both until an engineer decides which is right.

  • Which is right: the report or the inspection data
  • The decision is signed, kept on the record and scored

Waiting for J. Okafor to verify

The comparison is made in code, not by the model: dates must match, readings agree within three hundredths of a millimeter.

Where it runs today

One host per plant, run by us, kept apart from every other plant: your exports and your record only.

Where else it runs

Inside your own network, on one host, with nothing leaving the plant. Scoped with your network team before anything is installed.

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. "Today" is how plants run now. "Available today" is built and tested by us, and not yet running at a plant.

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 Available today

The same stack on one host inside your network, so nothing leaves the plant. 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 text of each document when the document is read, and then 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 Available today

The same assistant on a model that runs on the same host, with nothing leaving it.

Which model reads your documents is set once, when the product is installed, and nobody changes it from inside the product. In both cases a scanned PDF is turned into text on the product's own host; sending pages to an outside reading service is not supported. Each document's page says how it was read, and the Documents page says which choice is in force.

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.