When a plant still runs on Siemens S5, or on an S7-300 whose spares are getting harder to find, the risk is no longer technical — it is commercial. One failed CPU can stop production for days while somebody hunts a used card on the grey market. ATMAN migrates legacy Siemens control systems to current platforms, planned around your shutdown window and your existing field wiring, without rewriting the plant.

The Point at Which a Control System Becomes a Business Risk

Almost nobody replaces a working PLC because it is old. They replace it when one of these becomes true — usually more than one at once:

• Spares are scarce or grey-market. Cards are sourced from traders rather than the OEM, at rising prices and with no warranty on what arrives.
• Nobody left can edit the program. The engineer who wrote it has retired, the logic was never documented, and no one will touch it in case something breaks.
• The programming environment no longer exists. STEP 7 Classic needs an old PC, an old Windows version and a licence dongle sitting in a drawer.
• You cannot get data out. Production, energy and downtime figures are locked inside a controller that cannot talk to anything modern.
• A customer or auditor asks for records the system was never built to produce.
• An expansion is blocked because the rack is full or the CPU has no memory left.

What We Migrate

We work on Siemens. That is a deliberate choice, not a limitation — depth on one platform is worth more to you than shallow familiarity with six.

The Hard Part Is Not the Hardware

Swapping a CPU is the easy day. The difficulty is that the plant’s real operating knowledge lives inside the old program — and usually nowhere else.

Twenty years of interlocks, timing tweaks, exception handling and operator workarounds are in that code. None of it is in a document. Some of it nobody remembers the reason for. Migrate it blindly and you carry forward faults nobody understands; strip it out and you break behaviour the plant depends on.

• Read and document the existing logic first — before touching hardware, before quoting a changeover window
• Separate what is deliberate from what is accumulated, with your operators and maintenance team in the room
• Question every interlock but remove none unilaterally — every one gets a decision with a name against it
• Rebuild to a standard structure so the next engineer inherits something readable
• Hand over documentation as a deliverable, not an afterthought

How We Sequence It

1. Audit and backup. Read out and archive the running program, HMI project and parameters. Nothing else begins until a verified backup exists — including a proven restore.
2. Obsolescence and risk register. Every card, every panel, spares position, single points of failure, ranked by what stops production.
3. Functional specification. What the plant does today, written down and signed off. This is where undocumented logic becomes documented.
4. Hardware and architecture design. CPU sizing, I/O strategy, network, redundancy where it is justified and not where it is not.
5. Software migration and rebuild in TIA Portal, structured and commented.
6. Factory Acceptance Test against simulated I/O — errors found here cost hours; errors found on site cost production.
7. Changeover in a planned window. Pre-wiring and pre-labelling done in advance so the outage carries only the work that truly needs the plant stopped.
8. Commissioning, operator training, as-built documentation.

Reusing Your Existing Field Wiring

On most migrations the field side — sensors, actuators, cabling to the marshalling racks — is sound. It is the controller that is obsolete. Rewiring a whole plant when the wiring is fine is a way to convert a manageable project into a shutdown nobody can afford.

• Retain field cabling and marshalling wherever condition and documentation allow
• Use migration-friendly I/O arrangements so terminations move rather than get remade
• Replace only the instruments that are genuinely at end of life, or where measurement was never adequate
• Re-terminate to a proper schedule so the as-built drawings finally match the plant

The result is a shorter outage and a materially lower cost than a wholesale replacement — which is usually the difference between a project that is approved and one that keeps getting deferred.

The Changeover Window Is the Commercial Question

For most plants, the cost of the migration is not the CPU. It is the production not made while the plant is down. So the window drives everything.

• Phased migration by area where the process allows it, so no single outage carries the whole risk
• Parallel running on suitable sections, with the new system observing before it controls
• Pre-tested panels arriving on site already proven at FAT
• A written rollback plan — the old system stays restorable until the new one has run a full production cycle
• Shutdown-aligned scheduling so the work rides an outage you were taking anyway

What You Get Back

• Supportable hardware — spares from the OEM, not from a trader
• A readable program that a competent engineer can maintain without archaeology
• Documentation that matches the plant — drawings, I/O schedules, functional description
• Data out of the machine — production, energy, downtime and alarms available to your MIS or a dashboard
• Room to grow — capacity for the next line, the next instrument, the next customer requirement
• A quantified failure position instead of an assumption

Why ATMAN

A migration is not only a software job. It touches process, control panels, power distribution and often utilities at the same time. Where those sit with separate vendors, the gaps between them become your problem to manage.

• Process engineering, automation, electrical and HVAC in-house — one contract, one accountable party
• Panel design and build in-house, so control and power are engineered together rather than negotiated between suppliers
• Operating since 2008, on live plants in production, not laboratory conditions
• Siemens focus — including 5 LLPD dairy plant automation on Siemens PLC for Bharuch District Co-operative

Where Migration Sits Against a Full Modernization

These are different projects and are often confused when budgets are set:

If your process is sound and only the controls have aged, migration is the cheaper and faster answer. If you are also changing capacity or product mix, see plant modernization and retrofit — and do both under one contract rather than two.

Common Questions

Related

Related: Industrial Automation · PLC Programming · SCADA System Integration · Plant Modernization & Retrofit · Control Panels