The pitch on control system integration is often deceptively simple-sounding: just throw in the new equipment and upgrade the software, and it’s all good. But when it comes to getting all the different components working together in the real world, especially in Perth’s industrial sector where you have mining operations, water treatment facilities and manufacturing all vying for the same resources, it’s a whole different story. Production loss, safety risks, and unreliable systems are all real possibilities when integration goes wrong. The truth is, when you add new tech into an existing environment that was never designed to accommodate it, you’re looking at a whole lot more complexity than most people realise.
What Does Integration Actually Entail?
So what exactly does integration entail in the real world? It’s about getting all the new hardware and software to talk to each other and play nice with the existing systems, and that includes mapping out how the new gear communicates with all the old PLCs, DCS platforms, historian systems and SCADA layers out there. You look at things like Modbus, EtherNet/IP, PROFIBUS and OPC to figure out how it all fits together. But if you’ve got systems that use different communication protocols, well, that just adds another level of problem to solve. This is the core discipline of Control System Integration Perth specialists, who navigate these protocol differences daily. You’ve then got to design and program those translation layers that allow all these different systems to talk to each other, without losing any data along the way or slowing down the whole shebang.
The ultimate goal is to get the whole system to behave in a predictable way, even when things go wrong, whether that’s during a fault state or some other unexpected process upset. Of course, that’s a lot easier said than done.
The Problem of Different Vendors in Western Australia Industry
In Western Australia, most industries have got a mix of control systems from different vendors, often different ones on every capital project they’ve ever done. You see Allen-Bradley, Siemens, Schneider and GE Fanuc side by side, because each of those projects brought its own set of equipment based on what the engineer at the time thought was the best fit. And that’s just a nightmare to integrate.
When you get a new project and throw in the latest and greatest from a new vendor, you’re going to have to figure out a way to get that system to play nice with all the others, without breaking anything that’s currently working. And let me tell you, it’s not as simple as just installing a new patch of software or replacing a faulty piece of hardware. You’ve got to resolve all the communication and configuration differences, without having to rip out and replace any existing systems that are still functional. And then there are the different integration architectures of various SCADA platforms like Citect, Wonderware, FactoryTalk or Ignition. Getting those all to work together is a real challenge, and one that requires specific expertise.
You don’t want to end up with a solution that works from a technical standpoint, but is so complicated for the operations team to maintain that it becomes a burden on the business. Not exactly the kind of outcome you’re looking for.
Remote Operations and Cybersecurity in WA’s Dispersed Landscape
And then there’s the fact that a lot of WA’s mining and resource operations are scattered all over the place, processing facilities, pump stations, field equipment; you name it. That just adds another level of complexity to the whole integration picture, when you consider you’re going to need secure remote access to the system, so engineers and operators can keep an eye on everything from back in Perth. But you also don’t want to leave yourself open to security breaches, which is actually a very real risk. The Australian Signals Directorate reported over 1,200 cybersecurity incidents in the last reporting period, and that’s an 11% increase on the previous year. So it’s imperative you get the remote access part right, and make sure it includes proper network segmentation, strong authentication and encrypted communications.
Legacy Platform Migration While Keeping the Production Running
Keeping production up and running throughout the migration process from the old legacy platform to a more modern one is one of the most technically challenging parts of integration for existing WA facilities. It is impossible to replace old PLCs operating on obsolete equipment within the maintenance cycle. The logic of their operation, I/O connections and communication configuration should be transferred to the new platform and fully tested prior to the cutover.
The factory acceptance testing of the new configuration together with the parallel run period with the old and new configuration running simultaneously is the common method for mitigating the cutover risk. Operators should demand a comprehensive cutover plan from the integrator before the start of the job. A company which does not offer such a plan has not properly evaluated the risks for their clients’ operations.
Documentation: The Thing That Keeps Paying Off
As-built documentation of the new integrated system, including updated electrical diagrams, network configuration diagrams, backup copies of the PLC program, and SCADA configuration records, makes the system easily maintainable and modifiable by any engineer. For WA facilities with high staff turnover rate, the quality of documentation will define whether the new engineer will be able to work with the system or it will be more and more difficult even for the original integrator to work with it.
Leave a comment