Skip to main content

Material master and spares cleansing, from the documents up.

Raven's agents rebuild your asset list, BOMs, and spares from your drawings and vendor documents, then check SAP or Maximo against them. Duplicates, wrong specs, and missing BOMs come back found and valued in days, and cleaned in weeks.

For materials, procurement, stores, and ERP program teams.

Raven — Data quality check · Unit 300
running
Check the Unit 300 material master against its documents
Read the P&IDs, datasheets, GA drawings, and manuals
In progress
Build the asset list from the drawings
Build BOMs and spares from the vendor documents
Check SAP against the documents
Find duplicate and obsolete codes, valued
Write the corrections as a load file
Data quality report · Unit 300
compiling
What we're solving

The material master drifts from the documents.

Every code in the master was typed at purchase. What the plant actually has is written in the drawings and vendor documents. The two drift apart for years, and comparing them has meant someone reading every document by hand.

SAP · Maximo
what was typed
MS-118402
SEAL, MECHANICAL; 45MM · no equipment
MS-104226
MECH SEAL 45 MM T-21 · no equipment
P-3101A
BOM: none
PSV-3104
not in the register
The documents
what the plant has
GA-3101 · p.4
one seal: 45 mm, plan 53B, on P-3101A
GA-3101 · p.6
wear ring set · 2 off · no code exists
IOM-3101
BOM: 14 parts
P&ID 1103 · sh 2
PSV-3104 on P-3101A discharge

The documents Raven reads

P&IDs

every tag that exists on the plant, and its parent

Datasheets

the spec each equipment was bought to

GA drawings & vendor manuals

the parts list and the spares behind every equipment

SAP · Maximo · stock

what the systems say today: codes, BOMs, quantities

What Raven does

Read the documents. Build what the plant has. Reconcile the systems against it. Clean. Keep it current.

01

Read the documents

P&IDs, datasheets, GA drawings, vendor manuals: every part and spec, with its page.

02

Build the asset list, BOMs, and spares

One page per equipment: what the plant actually has.

03

Reconcile SAP or Maximo against it

Missing, wrong, duplicate, obsolete, and unlinked records, each with the evidence.

04

Clean and codify

Descriptions to your standard, duplicates merged, corrections ready to load.

05

Keep it current

New equipment, closed MOCs, revised drawings: the agents update it.

What comes back

The six deliverables.

01

The asset register, reconciled

Every tag on the drawings against the EAM: gaps, naming mismatches, wrong parents.

02

A BOM for every equipment

Built from its own vendor documents, checked against the EAM BOM.

03

The material master, cleansed and codified

Descriptions to your standard, duplicates merged, obsolete parts retired, missing codes created.

04

Duplicates and obsoletes, valued

Confirmed pairs and superseded parts, with the stock and value held against them.

05

Spares linked to equipment and stock

Which parts belong where, what is in stock and on order, what the next jobs need.

06

The data quality findings

Every finding counted and valued, with the page that proves it, for your team to confirm.

Why it's different

Raven reads every document, finds what a data cleanup can't, and does it in days instead of months.

Cleanup on the data alone

Cataloguing project

Raven

Merges duplicate codes

Rewrites descriptions to a standard

Builds BOMs from the vendor documents

Links spares to the equipment they belong to

Checks the register against the drawings

Every value carries the page it came from

Time to the findings, one plant

weeks
months
days

Kept current as the plant changes

Start with the check

You send the exports and the folder. We send back the numbers, in days.

01 · You give us

Material master export, with stock on hand

Equipment list from your EAM

P&IDs, scans are fine

Datasheets, GA drawings, vendor manuals

Your codification standard, if you have one

02 · In days, you get

Duplicate and obsolete codes, valued

Equipment with no BOM, or a wrong one

Spares coded to the wrong equipment

Tags on the drawings, missing from the register

Records that contradict their datasheets

Each with the data behind it, and its page. A fixed fee. Your team confirms the findings.

01The data quality check on one plant
02The whole cleanup, done by us or run by your team in Raven
03Kept current as the plant changes
After the cleanup

The same model keeps working.

The cleansing 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.

Customers
In production on live process plants

Raven is deployed in production — across operations, maintenance, HSE, and procurement.

See Raven on your plant