How a migration runs

Read-only scan. Tags, pictures, alarms, scripts and connections, with a report of what is unused, broken or written directly by scripts.
Mapping. Legacy tags mapped to a clean UDT structure, agreed with your engineers.
Draft. New screens, alarms and scripts generated on a development system, never on the running plant.
Review and test. Engineers check every screen and binding and test against simulation or the real controllers in an agreed window.
Cutover. A planned switchover with the old system ready as a fallback.

Demo on a fictional plant. All data shown is illustrative. No sound; on-screen text explains each step.

Our rules for AI on OT systems

Read-only access to the legacy project by default
New work happens on a development system
An engineer approves every change
Your data stays your data

Questions we get

Which legacy systems can you migrate?

Our tooling reads Siemens WinCC V7 and TIA Portal projects today. For other platforms we start from exports and documentation. Tell us what you run and we will tell you honestly what can be automated.

Does the AI change anything on our running system?

No. The legacy project is only read, and the new project is built on a development system. Nothing reaches production until an engineer has reviewed it and you have approved the cutover.

How long does a migration take?

That depends on the number of screens and scripts and on how clean the existing project is. The read-only scan gives a clear picture early, and we base the plan and price on it.

Is our project data used to train AI models?

We work through the business offerings of Anthropic and OpenAI, whose commercial terms say customer data is not used to train their models by default. We also agree with you which data the assistant may see.

Legacy PLC and SCADA migration, AI-assisted

How a migration runs

Our rules for AI on OT systems

Questions we get

A new line, an upgrade, or AI for your plant?