Migrate from a legacy DCS to a modern control platform.
DCS migrations are the most expensive controls projects most operating companies ever run. The schedule isn't consumed by the new DCS configuration. It's consumed reconstructing the as-built scope of the old one from drawings, point lists, and tribal knowledge.
Workflow.
- 01
Establish the as-built baseline
Pull the current P&ID set, the legacy DCS point list, and any cable schedules into a single workspace. Tagsight extracts the drawing-side scope and cross-references against the operational point list to produce a unified baseline.
- 02
Identify migration scope
Some loops migrate one-for-one. Others get re-architected, BPCS to SIS split per IEC 61511, redundancy upgrades, voting changes. The reconciled dataset makes that scope explicit so it can be costed, scheduled, and reviewed.
- 03
Export to the target platform
Tag table for the new DCS or PLC, plus loop folder seed data for commissioning. The migration team runs to the new platform with a complete dataset that mirrors the as-built.
What you get.
- As-built I/O dataset reconciled across drawings plus operational point list
- Migration scope register, one-for-one vs re-architected
- Target-platform tag table export
- Commissioning loop folder seed, one record per loop
FAQ.
01Does this work for a partial migration, one unit migrating, others staying on legacy DCS.
Yes. Tagsight workspaces scope cleanly. Run extraction on the migrating unit only, leave the rest as-is. Cross-unit interlocks become explicit in the off-page connector matching.02How does Tagsight handle redundant transmitter pairs that need to be upgraded to 2oo3 voting in the new system.
The extracted instrument index identifies the existing redundancy. The migration scope register flags each redundant pair so the upgraded voting hardware can be costed and scheduled separately.