PC-OCT23-PG34.1_Layout 1 03/10/2023 10:14 Page 34


SCADA & DATA ACQUISITION WHAT’S NEXT FOR SCADA?


and use them to determine smart goals. Is achieving better energy efficiency a key company goal? The platform should be capable of identifying areas of high energy usage, and this is where that organisation should start their process. Is improved capacity to produce customised projects a goal? In this case, data on equipment availability will be key. In order for the company to make informed decisions on digitalisation, having access to a full facility of data sets is key. Without having clear visualisation of all the


Stefan Reuther, member of the executive board at industrial software specialist, COPA-DATA, examines the role of SCADA in Industry 4.0


ambitious, and our expectations of facility data increases, how is technology for data capture and analysis changing? Let’s get this straight: SCADA as we knew it is


D


gone. The traditional automation pyramid has collapsed, and IT/OT convergence is on the rise. The next generation of solutions has arrived and is paving the way for advanced manufacturing. We are in the age of industrial digitalisation,


and control and monitoring software has never been so ubiquitous. Before we can understand the purpose of SCADA in Industry 4.0 journeys, we need to understand how the technology is changing. The technology has shifted from a tool for monitoring and data capture, to the technology shaping the smart factories of the future. One of the crucial ways this is achieved is the use of platforms with open system architecture. Open system architecture describes the


elimination of vendor dependence that is often associated with early and proprietary SCADA systems. In practice, an open system is not limited to operating with one original equipment manufacturers (OEMs) products, or a limited number of communication protocols. This level of flexibility is key to ensuring


modern systems are fit for purpose in modern factories. Moreover, providers of futureproof SCADA systems must be willing to continually adopt and embrace new standards to keep up with the growing scale of Industrial Internet of Things (IIoT) device networks. When specifying a software platform, guaranteed


34 OCTOBER 2023 | PROCESS & CONTROL


ata plays a vital role in the digitalisation of industrial facilities. But, as industry’s digitalisation goals become more


updates are on the one hand a necessity, however vendors do also need to ensure Long-term support (LTS) for up to ten years. Another consideration is the integration of


Information Technology (IT). Some modern platforms are capable of integrating data sets that were previously limited to the IT space. For instance, capturing data from Enterprise Resource Management (ERP) systems or Manufacturing Execution Systems (MES) for consideration alongside Operational Technology (OT) data from the factory floor. Data collected by IT systems can be used to


streamline production processes, fix critical issues faster and make better informed decisions — but only if it is collected, transmitted and processed effectively and securely. The most effective systems will be able to operate across both of these technology spheres. In addition, a software platform doesn’t only gather data from different hardware and IT systems but also needs to provide data in an open format and accessible for third parties, e.g. through a REST API. Modern SCADA can operate like a data hub or, as you could also name it, as an OTIL (Operation Technology Integration Layer). Now we understand the potential of modern


SCADA systems — how do engineers use this technology in their digitalisation journey? On its most basic level, a SCADA system lets an operator verify that its machinery is operating correctly. However, modern systems should enable an operator to use SCADA data to determine how to make improvements or adjustments to equipment to maximise productivity or efficiency. At the beginning of any digitalisation project, a manufacturer should consider its data sets


data produced from a facility, it is impossible to embark on an informed Industry 4.0 journey. In fact, proper investment in data collection technology should come before any other smart factory investment — including any hardware. A common challenge faced by engineers


when updating their SCADA system is setting up new automation projects. Overhauling aging SCADA systems can leave engineers with a significant programming burden. However, good systems are capable of removing the need for complex programming. The product philosophy of COPA-DATA’s


zenon, as an example, is to set parameters instead of programming. In practice, this means an extensive library of pre-designed static and dynamic elements and symbols. This means that no prior knowledge of programming is needed and projects can be created via clicking instead of coding — in comparison to an engineer having to write tens of thousands of lines of code. This can result in less downtime for a manufacturer switching its system and crucially, a reduced need for investment, recruitment and training resources for the engineering team. This ease-of-use is crucial for a next


generation SCADA to be implemented in an Industry 4.0 project. Frankly, the only good digital tools you will invest in, are the ones you will actually use. There is no doubt that Industry 4.0 is


transforming the way manufacturers operate, but it is also transforming how SCADA systems work, and what businesses should expect from them. At COPA-DATA, we took the decision to move


away from using heavily the terminology ‘SCADA’ for our solutions approximately 5 years ago. The zenon software platform had developed into a far more advanced tool for data capture, visualisation, analysis and reporting. For manufacturers with Industry 4.0 goals, a platform with this level of comprehension is necessary.


COPA-DATA www.copadata.com/en/


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50