P&ID extraction for refining.
A refinery is a portfolio of units sharing a fence line. Each carries its own I/O baseline, rebuilt on turnaround, and a full-site master set crosses 2,000 pages once utilities, tank farm, flare, and amine are counted.
What refining drawings carry.
- FCCU drawings carry high temperature instrument density. T-prefix tags dominate
- Hydrocracker SIS uses multi-layer overpressure protection drawn as redundant PSHH, PALL pairs. Voting annotations preserved
- Sulfur recovery and amine units require BPCS, SIS separation per OSHA PSM and IEC 61511 LOPA outputs
- Tank farms and blending run as separate workspaces. Drawing density and tag conventions differ from process units
- Crude overhead corrosion monitoring, ER probes, neutralizer injection reads as analyzer-style tags. Signal class inferred correctly
- Flare header and relief network tie-ins span multiple unit drawings. Off-page connector matching ties relief load studies together
- Hydrogen and SMR units carry high-temperature service with line spec breaks at every reformer outlet
- API 614 lube and seal-oil console drawings are vendor-supplied as sub-tags of the parent equipment. Equipment list preserves the parent linkage
What the extraction delivers.
- Per-unit I/O list segmented by process area
- Instrument index with thermowell plus transmitter pairing preserved
- SIS subset filtered for IEC 61511 audit
- Line list with pipe spec breaks and metallurgy
- Revision comparison covering pre-turnaround, post-turnaround drawing sets
Instrument tags on a refining drawing.
- TI-1305Temperature indicator on a riser cyclone, FCCU train 13, loop 05
- PALL-2210-2oo3Pressure alarm low-low, voted 2-out-of-3, SIS service on hydrocracker
- FE-9402Flow element on a sour-water stripper bottoms, unit 94, loop 02
- AT-7308Analyzer transmitter on amine sweetening, online H2S monitor
- LSHH-T401Level switch high-high on tank farm overfill protection
- FT-CDU-1101Crude charge flow on the desalter feed line
Regulatory context.
- OSHA PSM 1910.119, US drives MOC discipline. Refining is one of the listed covered processes
- EPA RMP overlaps PSM with environmental documentation requirements
- IEC 61511, ISA 84 enforces SIS lifecycle including proof-test cadence
- API RP 752, 753 facility siting documentation references P&ID-derived equipment locations
Which discipline reads it.
Controls EngineersBPCS and SIS instrumentation across FCCU, hydrocracker, sulfur recovery, and amine units. Turnaround-rebuilt I/O baseline.Process EngineersPer-unit material balance and heat integration. Metallurgy breaks captured on the line list at every reformer outlet.Functional Safety EngineersMulti-layer SIS overpressure protection on hydrocracker. Redundant PSHH, PALL pairs with preserved voting annotations.Mechanical EngineersRotating equipment density across compressor strings and lube, seal-oil consoles. API 614 sub-tag preservation.
Common questions
Does Tagsight handle the 300 plus page drawing sets typical of a refinery turnaround scope.
Yes. Drawing sets of several hundred pages run as a single workspace. Pages process in parallel. Review begins on page 1 while later pages are still working. Off-page connector matching ties cross-unit interlocks together.
How does Tagsight handle metallurgy data on the line list, CS, SS316, Hastelloy, etc.
Pipe spec is preserved as drawn, including the material code. The line list export carries spec, material, service, and any pipe-class break references from the drawing notes.
Can it process tank farm drawings alongside unit P&IDs.
Tank farm drawings run as a separate workspace. Tag conventions and instrument density differ from process units. Custody-transfer metering at the terminal filters out into its own audit register.
How are vendor-supplied skid drawings handled within the unit set.
Vendor skid drawings, lube oil consoles, hydrogen makeup compressors, amine reclaimer packages extract the same way as plant drawings. Equipment from the skid is captured with the parent process equipment annotated. Instruments inherit the parent for grouping.
Does the extraction support the documentation required for an API 754 audit.
API 754 tracking, Tier 1-4 process safety events draws on tag-level event data rather than the P&ID itself. The extraction provides the underlying instrument register the API 754 tools join against, not the audit output.
Run it on your refining drawings.
Upload a P&ID set and see the instruments, equipment, and lines it reads before committing to a plan.