A tag register built from your drawings. Every document linked to it.
Raven reads your P&IDs into a complete register, checks it against what your EAM holds, and links each tag's datasheets, manuals, and history to it. For an information handover, a system migration, or a register nobody trusts.
For engineering, document control, and project information teams.
| Tag | On drawing | In EAM | Documents |
|---|---|---|---|
| P-3101A | PID-3101 r7 | matched | datasheet · IOM · 2 more |
| FCV-1102 | PID-3102 r4 | not in EAM | loop dwg · datasheet |
| V-201 | PID-3101 r7 | matched | datasheet · U-1 dossier · 4 more |
| E-2205B | on no drawing | in EAM | none linked |
Register builds and handovers still run on tracing drawings by hand.
Registers are traced by hand
A register build or handover means people tracing P&IDs into spreadsheets, tag by tag, sheet by sheet.
The EAM is never checked back
What accumulated in the system over the years and what the drawings actually show are two different lists, and nobody has compared them.
Documents stay in folders
The datasheet exists, somewhere. Finding it means already knowing where to look, and handover dossiers arrive as folders, not links.
Drawings in. A checked, linked register back.
01
You send the drawings
The unit's P&IDs, an EAM extract, and whatever document set you have: dossiers, datasheets, manuals. Scans are fine.
02
Raven extracts and matches
Every equipment, line, valve, and instrument is extracted from the drawings into a register. Each tag is matched against the EAM, and its documents are found and linked to it.
03
Gaps reported, register delivered
Tags missing from the EAM, entries no drawing carries, and unlinked documents come back as findings with the evidence attached. The register is delivered as loadable files, and your engineers approve it.
The drawings themselves come back smart: click any tag on the P&ID and its page opens. See Smart P&ID
The register the plant can actually trust.
Built from the drawings
The register reflects the plant as drawn, not what accumulated in the system. Every tag carries the drawing and revision it came from.
Checked both ways
Drawings against the EAM and the EAM against the drawings: missing tags and orphan entries both surface, each with its evidence.
Structured how the handover asks
CFIHOS or ISO 14224 structure where the project requires it, and plain loadable files where it doesn't.
One unit first.
Send one unit's P&IDs and an EAM extract. The unit comes back as validated smart drawings with its register, the EAM comparison, and the linked documents, in two to four weeks. From there we agree the scope unit by unit, and your engineers approve each delivery.
What to send: One unit's P&IDs as PDF scans (any quality), the equipment list export from your EAM for that unit, and whatever datasheets or manuals you hold for it.
Delivered at production scale.
At Indorama's fertilizer and petrochemical operations, 10 plant units have been processed, more than 10,000 documents are connected to their assets, and over 1,000 users across four functions work on the result daily.
Send one unit's P&IDs. Get the unit's register back.
Scans are fine. You see your own unit as a smart drawing with its register beside it.
