Moving off a SmartPlant workflow into structured tag data.
Read PDFs and scans directly. Produce the I/O list, equipment list, and line list without a project database to maintain.
No migration cliff.
The typical transition runs in three phases. First, the team picks one or two active projects and processes them through Tagsight in parallel with the existing SmartPlant workflow. The extracted I/O list, equipment list, and line list are compared against the SmartPlant output for that project.
Second, once the parallel pass confirms the extraction matches the engineering team’s expectations, new projects start in Tagsight directly. The SmartPlant workflow continues for in-flight projects until they close out. There is no migration cliff; no project database to export, no schema to convert.
Third, legacy drawings that were never modeled run as inputs. The scanned drawings sitting in the EDMS produce the same documents as the CAD-exported PDFs.
How the transition runs.
- 01Parallel passFirst, the team picks one or two active projects and processes them through Tagsight in parallel with the existing SmartPlant workflow.
- 02CutoverSecond, once the parallel pass confirms the extraction matches the engineering team’s expectations, new projects start in Tagsight directly.
- 03Legacy backfillThird, legacy drawings that were never modeled run as inputs.
Read directly from the drawing.
The drawing itself: PDF, scan, or image. No project database required, no schema to maintain.
ISA 5.1, KKS, IEC 81346, NORSOK, JIS, GOST, or an in-house code, no configuration step.
Run both workflows in parallel as long as you need.
Upload the old and new PDFs, run Revision Comparison, export an Excel Change Report for MOC.
Extracts export to Excel and standard PLC formats from day one.
- TIA Portal XML, Studio 5000 L5X, PLCCreator CSV, DEXPI XML, Excel, CSV, JSON. All available from any project.
- Supported the same way. Scanned, photographed, or vector PDF, all supported.
Two workflows, six decisions.
Where the SmartPlant workflow concentrates engineering effort, and where the Tagsight workflow concentrates it instead.
| Topic | SmartPlant P&ID | Tagsight |
|---|---|---|
| Source format | Intelligent P&ID model with a project database (.spd files, tagdb.cfg) maintained alongside the drawings. | The drawing itself: PDF, scan, or image. No project database required, no schema to maintain. |
| Tag convention | Configured up-front in the project database. New conventions require a schema edit and re-validation. | Read directly from the drawing. ISA 5.1, KKS, IEC 81346, NORSOK, JIS, GOST, or an in-house code, no configuration step. |
| Revisions | Managed through concurrent project versions and a central model; change reports generated from the model. | Upload the old and new PDFs, run Revision Comparison, export an Excel Change Report for MOC. |
| Cutover | Schema migration plus a coordinated team move. Hard to run in parallel for long. | Run both workflows in parallel as long as you need. Extracts export to Excel and standard PLC formats from day one. |
| Export formats | Vendor-native schemas plus selected interchange formats; export configurations maintained per project. | TIA Portal XML, Studio 5000 L5X, PLCCreator CSV, DEXPI XML, Excel, CSV, JSON. All available from any project. |
| Legacy drawings | Often live outside the model entirely; re-modeling each one consumes engineering time. | Supported the same way. Scanned, photographed, or vector PDF, all supported. |
Common questions
Do I need to keep the intelligent P&ID model running to use Tagsight?
What about the tag convention defined in the source project?
Can we run a parallel pass during cutover?
How do revisions work without a centralized project model?
Does Tagsight produce DEXPI?
What happens to legacy drawings that never made it into the intelligent model?
Move off SmartPlant P&ID.
Read PDFs and scans directly. Produce the I/O list, equipment list, and line list without a project database to maintain.