Your P&ID set becomes the I/O list a project runs on.
The 14-column I/O list, read straight off the drawing. Tags in their original convention, signal class read from the drawing, paired to the equipment, lines, and loops on the same sheets, then exported to the format your controls team imports.
The 14-column I/O list is already on the drawing.
Every instrument on the P&ID carries a tag, a service, a loop, and a signal type. The I/O list is that data, arranged into the columns the controls team builds the controller from. The work is reading it out cleanly, in the convention the drawing was authored in, instead of a junior engineer retyping tags into a spreadsheet for a week.
Tagsight reads the sheet and hands back the list, with every row traceable to the page it came from, ready to confirm and export.
From drawing to PLC.
- 01UploadA P&ID set as PDF, scan, or image.
- 02Read as drawnTags read in their own dialect.
- 03ReviewConfirm on the drawing canvas.
- 04ClassifySignal class read from the drawing, editable.
- 05ExportThe format your controls team imports.
The fourteen columns you receive.
The columns marked drawing are read off the P&ID. Range and units come from a datasheet. Cabinet, slot, and channel are yours to assign downstream. Every row traces to its source sheet.
| # | Column | What it carries |
|---|---|---|
| 01 | Tag | Instrument tag in the drawing dialect. |
| 02 | Service description | Process service the instrument measures or controls. |
| 03 | P&ID sheet | Source drawing number and revision. |
| 04 | Loop | Control-loop number for grouping. |
| 05 | Signal class | AI, AO, DI, or DO, in the drawing's own dialect. |
| 06 | Sub-class | BPCS or SIS per IEC 61511 separation. |
| 07 | Range | Engineering range when the drawing or datasheet shows it. |
| 08 | Units | Engineering units paired with the range. |
| 09 | Set point | Process set point when specified. |
| 10 | Trip / alarm | Trip or alarm value for protective signals. |
| 11 | Cabinet | Marshalling cabinet ID, assigned downstream. |
| 12 | Card slot | PLC card slot assignment. |
| 13 | Channel | Channel number within the card slot. |
| 14 | Notes / revisions | Revision marker, MOC reference, note. |
Every tag, in the dialect it was drawn in.
A vector CAD export, a faded scan, and a phone photo of the sheet on the wall all read the same way. So does the convention. ISA 5.1, KKS and RDS-PP, IEC 81346, NORSOK, Dutch NEN, and the in-house letter codes a plant has used since commissioning are each kept in the form they were drawn in, never silently rewritten to ISA.
- ISA 5.1PT-101
- KKS10LAC01CT001
- IEC 81346=H1+R2-B1
- NENAB2WV05
- DINTIR 7001
One reviewed list, in the columns the controller needs.
Every reading lands on the drawing canvas for an engineer to confirm, reclassify, or add a missed tag. The export runs on what you confirmed, so the list that reaches the panel shop is one a person already checked.
- The 14-column workbook, tag through channel
- Signal class on every tag, AI / AO / DI / DO
- BPCS and SIS split, with the source sheet on each row
- Every export format for a drawing, once it is counted
One extraction, written to the file your controls team imports.
Common questions
Does this work on scanned drawings?
How does Tagsight handle non-ISA tag conventions?
What columns appear in the output?
How is signal class assigned?
How are off-page connectors and cross-page loops resolved?
Convert your drawings.
Upload a P&ID set in any convention, get the 14-column I/O list paired to your equipment and lines, and export to the platform your team uses.