Tie-in I/O lists, extracted from the existing P&ID set.
Upload the current P&IDs to baseline the facility. Drag the new equipment region on the canvas to extract the tie-in scope. Compare, merge, and export an updated tag table to TIA Portal, Studio 5000, or PLCCreator.
What the tie-in pass produces.
Three documents, all from the same workspace. The baseline you only pay for once, the Change Report your panel shop reads, and the merged tag table your engineering team imports.
The baseline read returns the full I/O list of the facility as it stands today. Every instrument, signal class, equipment owner, and source-page reference is preserved. Re-uses cached results when re-run on the same drawings, so the baseline only pays once.
Tie-in delta report.
Compare the baseline against the post-tie-in extraction. The Excel Change Report opens with a Summary sheet plus colour-coded Added, Removed, and Modified tabs. Tag number, instrument type, signal class, description, location, and page reference travel through on every row.
- A Summary sheet with Added / Removed / Modified counts, plus three colour-coded tabs: Added Instruments in green, Removed Instruments in red, Modified Instruments in yellow.
- Each row carries Tag Number, Instrument Type, Signal Class, Description, Location, and source-page reference.
Merged tag table.
The full merged I/O list exports to TIA Portal XML, Studio 5000 L5X, or PLCCreator CSV. New rows carry the same signal-class assignment and module-sizing fields as the baseline, so the engineering team imports one file and runs.
- The merged I/O list exports as a Siemens TIA Portal XML GlobalDB block sized for S7-1200 or S7-1500, as a Rockwell Studio 5000 L5X for ControlLogix 5380 or 5580, or as a PLCCreator Device IO List CSV that covers Honeywell Experion, Schneider EcoStruxure, Yokogawa CENTUM, Emerson DeltaV, Foxboro Evo, and ABB 800xA.
- The engineering team imports the merged file directly on their workstation. The originals stay in the customer EDMS.
A merged tie-in tag table, worked through.
Three baseline instruments on the existing separator, three new tags added with the tie-in scope. The merged export carries both, each row traceable to its source.
| Tag | Signal | Service | Loop | Source |
|---|---|---|---|---|
| PT-101 | AI | Separator pressure | 101 | Baseline |
| FT-102 | AI | Separator flow | 102 | Baseline |
| TIC-204 | AO | Separator temperature | 204 | Baseline |
| ESDV-307 | DO | Inlet ESD valve | 307 | Tie-in |
| FT-201 | AI | Meter run flow | 201 | Tie-in |
| PT-105 | AI | Discharge pressure | 105 | Tie-in |
How a tie-in runs through Tagsight.
- 01Upload the existing packageDrag the current P&IDs, instrument indexes, datasheets, and loop diagrams into a workspace. Vector PDFs from CAD process fastest. Scanned legacy drawings are read at high resolution; you review uncertain rows before export.
- 02Mark the new tie-in scopeOpen the v3 review canvas and drag a rectangle around the new equipment area on each affected drawing. Tagsight re-extracts just that region and merges the new rows into the project. Every drag is logged in the project audit drawer and reversible.
- 03Export the merged I/O listRun the comparison against the baseline. The Excel Change Report lands in seconds with Summary, Added, Removed, and Modified sheets. Then pick TIA Portal XML, Studio 5000 L5X, or PLCCreator CSV for the merged tag table.
Common questions
What is a tie-in I/O list and when do I need one?
How does Tagsight scope the new tie-in equipment on an existing P&ID?
What is in the Excel Change Report for a tie-in revision?
Does Tagsight support TIA Portal, Studio 5000, and PLCCreator for the merged export?
How is the existing baseline re-used across multiple tie-ins on the same facility?
Is the region re-analyze step free, and what are the limits?
Tie-in I/O lists, extracted from the existing P&ID set.
Upload the current P&IDs to baseline the facility. Drag the new equipment region on the canvas to extract the tie-in scope. Compare, merge, and export an updated tag table to TIA Portal, Studio 5000, or PLCCreator.