Shell.
Shell DEP fixes the shape of the output document, not the shape of the source drawing. Contractor handovers arrive in whatever the originating EPC drafted to. The DEP-shaped output is the work between.
Shell DEP P&ID Extraction for Projects.
Shell DEP fixes the output document shape for engineering on Shell-operated assets. I/O lists and instrument indexes align with DEP expectations.
Primary standard: Shell DEP
Documentation expectations.
- Instrument tag conventions consistent with DEP 32.31.00.32 family. Hierarchical tag with area, unit, loop, function structure
- I/O list segmented by signal class with BPCS and SIS scope kept on separate sheets for IEC 61511 audit
- Instrument index covering the full drawing set with tag uniqueness enforced across pages
- Equipment list keyed to vessels, pumps, exchangers, packaged units, and skids with parent-child relationships preserved
- Line list with pipe spec, service, metallurgy, insulation, and tracing flags carried forward from the line designation
- Marshalling and I/O-card count estimated from the I/O list on the EI&T scope
- Revision comparison reports for MOC packages on brownfield revamps where Shell DEP MOC discipline applies
Where Tagsight fits.
- Shell DEP-shaped tag conventions come through alongside ISA 5.1
- Produces the I/O list with audit-trail columns suitable for inclusion in the as-built handover dossier
- Off-page connector matching across multi-page drawing sets keeps cross-train interlocks intact
- Excel exports separate BPCS and SIS scope onto distinct sheets so the safety-system review runs independently
- Revision comparison produces an added, removed, modified diff suitable for the MOC change record
- Direct exports to TIA Portal, Studio 5000, PLCCreator, and DEXPI for the controls-system import step
Common questions
Does Tagsight handle Shell DEP tag conventions.
Yes. Shell DEP-shaped tags come through alongside ISA 5.1. The original tag string is preserved verbatim. Signal classification follows the second-letter function regardless of the surrounding hierarchy.
Is Tagsight a Shell-approved tool.
Tagsight is independent. This page describes how Tagsight outputs line up with documentation expectations on Shell-operated projects. It is not a vendor-approval statement and does not represent any partnership or endorsement.
Can the I/O list export feed our DCS or PLC vendor tool directly.
Yes. Direct exports cover TIA Portal XML, Studio 5000 L5X, PLCCreator CSV, DEXPI XML, and Excel. Pick the format your downstream platform expects and bypass intermediate CSV reformatting.
How does revision comparison work for MOC packages.
Upload two revisions of the same drawing set as separate projects. The comparison view produces an added, removed, modified diff, exports a Change Report Excel, and saves the comparison to the workspace audit trail with optional MOC notes.
What about scanned legacy P&IDs from older Shell-operated assets.
Scanned PDFs and image uploads, PNG, JPG, TIFF are supported. The cleaner the scan, the less you confirm by hand. On a degraded scan you review and adjust more rows in the canvas before export.
Run it on your Shell projects.
Upload the relevant P&IDs and export the Shell-shaped instrument index and I/O list.
Shell DEP is referenced descriptively. Tagsight has no affiliation with Shell plc.