P&ID to instrument index.
Your P&ID set becomes the facility-wide instrument index. Every instrument tag deduplicated across every sheet in the project, paired with its loop, signal class, linked equipment, datasheet reference, and source drawing.
One source for the instrument index, I/O list, and equipment list.
The instrument index ships as a spreadsheet alongside the I/O list and equipment list, so all three documents stay in sync from a single source.
From sheets to a master list.
- 01UploadWhole P&ID set
- 02ExtractEvery instrument per sheet
- 03DedupTags across the facility
- 04ExportExcel or CSV
Every tag, in the dialect it was drawn in.
Each sheet's tag convention is read as-is. Tags are never silently rewritten to ISA. Multi-site projects with mixed conventions produce one merged instrument index, with every tag in the form it was drawn in.
- ISA 5.1PT-101, FCV-203, TIC-4407
- KKS10LAC01CT001, 20MAL10AA001
- IEC 81346=A1+B2-PT001
- DIN 19227PIRA+02-301
- NORSOK Z-DP-00220-PT-3201
- NEN Dutch HVACKB3DH02, XL7VK04
- Shell DEP12-PIT-0421
- In-house formatsPI-CRACK-101A
One deduplicated instrument index, ready to export.
- Formatted workbook with signal class, loop, and source-drawing columns
- Flat table for import into an existing instrument register
- Topology-linked XML carrying instrument and equipment nodes
Common questions
How is the instrument index different from the I/O list?
The I/O list is the controls document: one row per signal, with the columns the PLC and DCS team need to assign and wire. The instrument index is the facility-wide master list: one row per instrument tag, with the columns process and maintenance engineers reference across the asset lifetime. They share the same source extraction, presented for different audiences.
What happens when the same tag appears on multiple drawings?
The two rows are deduplicated into a single index entry. The P&ID sheet column lists every drawing the tag was found on, and any conflicting service descriptions or loop assignments are presented for your review.
Can I upload an existing instrument register?
Yes. Upload it as an Excel reference file. Tagsight cross-references the extracted index against the register and flags tags that appear on the drawings but are absent from the register, and vice versa.
Are non-ISA dialects supported?
Yes. The tag convention is read from each drawing. ISA 5.1, KKS, IEC 81346, DIN 19227, NORSOK Z-DP-002, Shell DEP, Aramco SAES, and in-house operator formats are all carried through.
Where do range and set-point values come from?
From any value annotated directly on the drawing and from attached datasheets. Tagsight does not invent values: if the drawing and datasheet both lack the value, the cell stays blank.
Convert your drawings.
Upload a P&ID set in any drawing convention, get a facility-wide instrument index with one row per tag, export Excel or CSV.