Material master and spares cleansing, by AI that reads your documents.
Classify, de-duplicate, enrich, and connect to BOMs: the same scope a cataloguing project quotes, delivered in weeks. Every finding carries the document page that proves it.
For materials, procurement, stores, and ERP program teams.
| Finding | Count | What comes with it |
|---|---|---|
| Duplicate code pairs | 412 | valued at the stock held against them |
| Equipment with no BOM | 1,180 | BOMs proposed from vendor documents |
| Parts in stores, no code | 96 | codes and descriptions proposed |
| Records contradicting datasheets | 3,400 | each with the document page attached |
This work is bought as a cataloguing project. It runs on people reading documents.
People read the documents
Spare parts lists, IOM manuals, GA drawings, datasheets: the truth about every part is in there, and someone has to read it.
Match and code by hand
Each description is broken down, matched against the catalogue, and coded line by line. On a large register this takes a team months.
And the drift comes back
New purchase orders, projects, and handovers add codes faster than a one-time cleanup removes them.
Meanwhile the cost stays invisible: until someone counts the mismatches, nobody has to react to them.
Every finding, with the page that proves it.
Duplicates come as confirmed pairs valued at the stock held against them. Missing BOMs come proposed from the equipment's own vendor documents. Nothing arrives as a bare list you have to re-verify.
| Code | Description | Stock | Finding | Evidence |
|---|---|---|---|---|
| MS-118402 | SEAL, MECHANICAL; 45MM; T-21 | 2 · site A | duplicate pair | DS-4411 §4.2 |
| MS-104226 | MECH SEAL 45 MM TYPE T21 | 1 · site C | same maker part no. | GA-3101 |
| P-3101A | EAM BOM · seal not listed | — | missing from BOM | IOM-3101 p.24 |
| GSK-2205 | Gasket, spiral wound 6″ | 40 | superseded · flagged | vendor notice |
Extracts in. Confirmed corrections back.
01
You send extracts
A material master extract, the stock reports, and a folder of vendor documents. Nothing installs, and nothing migrates.
02
Raven reads and checks
Agents read the documents into one model of your plant: every equipment, part, and material code linked to its page. Your extracts are laid over it, and every disagreement is flagged with the evidence attached.
03
Your team confirms
Candidates go to your materials team. Confirmed duplicates are valued at the stock held against them, and the corrections come back as loadable files for your EAM.
The register, checked against the plant's own documents.
Checked against the documents
Register tools clean what is inside the register. Raven checks the register against what the engineering documents say, which is the part the tools do not do.
Weeks, not months
The reading is done by agents. The document work that takes a cataloguing team months comes back in weeks, with the same scope: classify, de-duplicate, enrich, connect to BOMs.
You keep the model
After the job, every code is linked to its equipment and its source page. BOM checks, spares before jobs, and daily questions keep running on it.
The same model keeps working.
The cleansing job leaves behind a model of your plant with every code linked to its equipment and its page. The rest of the materials work runs on it.
Start with the data quality check.
Send a material master extract, the stock reports, and a folder of vendor documents. For a fixed fee, in two to three weeks, you get one report of everything the checks find: duplicate candidates valued, records contradicted by datasheets, missing linkage, and equipment with no BOM, with counts and values.
It shows how big the cleanup is and how much money is stuck in it. From there we agree the scope: we do the job for you, or your team does it themselves in Raven. Your engineers approve the result either way.
What to send: Material master export from SAP MM or Maximo (Excel or CSV, all plants), stock on hand by plant, and if you have it, a folder of vendor spare-parts lists or IOM manuals. One plant is enough.
Built on delivered work, not a slide.
Raven runs in production at Indorama's fertilizer and petrochemical operations, where plant documents and drawings are processed into the model and used daily across maintenance, operations, and procurement. On materials work: BOMs built from vendor documents and duplicate codes valued on a live refinery unit's own data.
Send one register extract. See what the checks find.
If the checks find nothing you didn't already know, you've lost nothing.
