Software Defined Automation, usually shortened to SDA, is a way of building control systems where the software is treated as the long term asset and the hardware underneath it can change over time. This post explains what that means in practice and why it matters to anyone who runs a plant.
The way it has always been done
For the last forty years most industrial control has followed the same pattern. You choose a make of PLC, you write the program in that manufacturer’s software, and from then on the program and the hardware are tied together. If you want to move to a different controller, even a newer model from the same supplier, the program usually has to be converted or rewritten and tested again. The same is true for the operator screens, the drives and the way everything talks to each other.
That worked well enough when a control system was installed and left alone for twenty years. It works less well now that plants are expected to change more often: new lines, new products, new data requirements from the business, and hardware that goes out of production long before the plant does.
What changes with Software Defined Automation
SDA turns the relationship round. The control application is written once, in a form that does not depend on any particular manufacturer, and it is then run on whatever hardware suits the job. The hardware can be a conventional PLC, an industrial PC, an edge device on the machine, or a server in a control room. If a piece of hardware is replaced, the same software is loaded on to the replacement and carries on.
The technology that makes this possible is an international standard called IEC 61499. It describes control software as a set of small function blocks that are linked together and can be spread across several devices. Because the standard is open, software written to it is not owned by one supplier. Platinum is a member of UniversalAutomation.org, the independent association whose members share a common runtime built on IEC 61499, so the same application can run on hardware from different manufacturers.
What it means for a plant manager
In plain terms, four things change.
Hardware becomes a choice, not a commitment. When a controller goes obsolete you can replace it with the best option available at the time, rather than being limited to whatever is compatible with the old program.
Changes are quicker and safer. Because the application is built from tested blocks, adding a new machine or changing a sequence means adding or adjusting blocks rather than rewriting large sections of code. The change can be tested away from the plant before it is loaded.
Data is built in, not bolted on. An SDA application can pass live information straight to the business systems, dashboards and cloud services that need it, without a separate data collection project afterwards. This is the link between our Software Defined Automation and Systems Integration services.
The software becomes an asset you own. The application is documented, portable and can be supported by more than one integrator, which reduces the risk of being tied to a single supplier for the life of the plant.
Is it right for every site?
Not always, and not all at once. A simple machine with a single small PLC that is doing its job does not need to change. SDA earns its keep where there are many controllers to coordinate, where hardware obsolescence is a known challenge, or where the business wants better information from production. In most cases it is introduced gradually, starting with one area or one new project, and the existing systems keep running alongside it. Our next post looks at exactly that: how SDA can sit above existing PLCs as an orchestration layer and let a site upgrade at its own pace.
Talk to us
If you would like to understand what SDA might look like on your site, we are happy to walk through it with you. There is no obligation, and the first conversation is usually about your plant and its challenges rather than about technology. Contact us to arrange a call.
Watch the videos
These two short videos explain the ideas in this article in plain English. They are part of our free software defined automation explainer videos.
Watch on YouTube
Foundations, episode 1
What actually changes
About 3 minutes
A plain English introduction to the two international standards used to program industrial control systems, IEC 61131-3 and IEC 61499. It shows how each one is laid out, what changes when you move to IEC 61499, and why that change is easier than many engineers expect.
Play video
What it means for your plant, episode 1
Software that outlives the hardware
About 2 minutes
Every control system has two parts: the hardware you can see, and the software that makes it work. In most plants today, the two are tied together.
What this episode covers
- Your engineering is protected
- A hardware replacement becomes a planned, smaller job
- You have a choice
- That choice changes the conversation when you buy
- What to be clear about before you start
Planning a project? Platinum SpecWorks is our tool for writing a clear IEC 61499 request for proposal, so that every bidder answers the same questions. See how it works, or ask us for access.