Asset information model of your plant: built from your documents and systems.
Your plant's engineering documents, its data systems, and its as-built reality grew apart. Bringing them back together is the hardest work in asset information management. Raven builds that join: smart P&IDs, smart documents, and a connected, structured data layer, checked against the master data in SAP, Maximo, or whichever systems you run.
Try it — click P-101A, V-201, FCV-1102, or PSV-201 on the drawing
It starts from the documents and extracts you already have.
No preparation on your side. Send the folder and the extracts as they are — Raven reads them and connects what they describe.
Your documents
P&ID 1103 · Sh 2.pdf
DS-P101 · Rev 3.pdf
IOM manual · P-101A.pdf
P&IDs · datasheets · manuals · vendor spares lists · GA drawings · SOPs
Your system extracts · via connectors or file drops
Asset register.xlsx
Material master.xlsx
Stock · 4 sites.xlsx
SAP PM · Maximo · ERP · inventory · PM plans · MOC & work-order history · nameplate photos
The data layer · your asset information model
Every asset connected to its documents, codes, and history. Every link cited to the page it came from.
Extract. Match. Check. Publish.
Extract
Tags, lines, valves, and instruments from the P&IDs. Attributes per equipment type from datasheets and manuals. BOM items from vendor documents. Every value carries its document and page.
Match
Tags are normalized and matched against your EAM hierarchy. Parts link to material codes by maker part number. Whatever cannot be resolved goes to your engineer.
Check
Drawing, register, and stores are compared against each other. Duplicates, missing values, and wrong values surface, with the datasheet as the reference.
Publish
Confirmed values become the model: versioned, cited, queryable. Corrections go back as files your EAM team can load.
The same data, made smart.
Smart P&ID · the heart of the layer
Scanned P&IDs become smart P&IDs.
Every tag, line, and valve clickable and revision-aware. The drawing becomes the way into everything else on this page: click an object, and its records open around it.
In your plant today
In the Raven model
Datasheets, manuals, SOPs
searchable at best, unlinked
Smart documents
values extracted and cited to the page; linked to tags
DS-P101 · Rev 3 · pump datasheet
Seal plan
Plan 53B
p.4Motor
37 kW
p.4Design flow
220 m³/h
p.2linked to P-101A on the drawing
Line lists & C&E sheets
per drawing, maintained by hand
Extracted registers
line lists built from the drawings and checked against yours; interlocks and C&E linked to their tags
Line list · built from the drawings
4"-P-1103-A1A
P-101A → V-201
matches your list
3"-P-1106-A1A
V-201 → FCV-1102
not in your list
FIC-1102 · interlock I-12
C&E · sheet 4
linked to the loop
Material master & BOMs
free-text descriptions, duplicates, gaps
Cleansed master data
descriptions parsed and standardised; codes linked to equipment; duplicates flagged
Material master · parsed & linked
MS-104226
Mech seal 45 mm T-21
2 in stock
MS-118402
SEAL, MECHANICAL; 45MM
duplicate
MS-100482
Bearing 6207-2Z
linked
parsed from free text · linked to equipment
Asset register & hierarchy
drifted from the drawings
Reconciled register
matched against EAM; gaps reported; corrections handed back
Asset hierarchy · from documents, checked against EAM
FCU-1
├─ P-101A
matched
├─ P-101B
matched
└─ E-210
not in EAM
gaps reported · corrections handed back
Stays current on its own. Keeps every version.
New documents and extracts arrive through connectors or simple file drops, and Raven checks them against the model. This is the data governance the register never had: every accepted change is versioned, with its evidence attached.
P&ID 1103 · Rev 8
Current2 valves added, 1 line rerouted · from MOC-2214
BOM · P-101A
Acceptedmechanical seal added · from DS-4411 §4.2
Material master
AcceptedMS-118402 merged into MS-104226 · confirmed by materials team
P&ID 1103 · Rev 7
Rev 7superseded · kept in history, comparable side by side
Use it through Raven, or through your own agents.
Everything in the model is available over API and MCP. The agents and tools your company already builds can query the same tags, documents, and history that Raven's agents use, with the citations attached.
Raven is deployed in production — across operations, maintenance, HSE, and procurement.
The model starts from whatever you send.
One unit's P&IDs are enough to see your own unit as a smart drawing. They take minutes to send.
