Feature SCADA & Data Acquisition The battle for globalisation


The line of functionality between SCADA and DCS is blurring. These two traditionally disparate technologies are now seen as competitors in similar application environments. Here Frank Horden of Yokogawa argues that the changing nature of globalisation means that there are still distinct benefits in using SCADA as an umbrella layer on top of a DCS core


inevitable. The much loved cartoon show The Simpsons, seems to have flouted this rule as it enters its 25th season. The show has captivated millions for nearly a quarter of a century.


N


One of the key reasons for its success is the protagonist Homer Simpson. Viewers can relate to his on- screen antics and naivety. His lovable nature however, seems somewhat para- doxical to his job as a safety inspector at Springfield’s nuclear power plant. It’s frightening to think that human beings, with our haphazard Homer tendencies, still form an integral part of such a highly regulated, automated and controlled environment. At the heart of such environments


lie platforms such as the distributed control system (DCS) which has devel- oped over the years, from humble beginnings as a single loop controller housed in a panel. It is now cheaper and more intuitive, partly as a result of the use of PLC interfaces.


The strength of a DCS lies in a single database set-up with minimal com- plexity and low risk of data redun- dancy. Recent developments have seen a push towards better smart reporting and relaying of management informa- tion (MI) through Human Machine Interfaces (HMI).


On the other hand, the supervisory control and data acquisition system SCADA (supervisory control and data acquisition), has developed from a simple visualisation tool used in a bank of relays. It has reached a point where it can now provide an increas- ingly object oriented approach, storing hard I/O tags from numerous devices in its fast Historian databases.


The confusion This convergence of the two overlap- ping technologies has created a level of confusion in the industry. At first glance, it seems that SCADA and DCS


Automation FEBRUARY 2014


Above and below: Yokogawa’s integrated


approach seeks to compliment the robust control of DCS on a plant level, with SCADA as a supervisory umbrella at the hybrid


enterprise level


have become direct competitors, doing essentially the same thing.


Buyers look to vendors that provide


turnkey solutions with proprietary hardware


that requires a minimal


amount of customisation. However, vendors may often use this as a market- ing tool and promote overlapping func- tionality in order to maximise sales. Essentially, DCS systems are some- times sold under the SCADA label and SCADA is sometimes branded as DCS. This does more harm than good for the industry by blurring the boundaries. The boundaries are evident when the production environment is seen as a garden. DCS is an ‘inside the fence’ solution best suited to those continu- ous, PID control intensive applica- tions. In contrast, SCADA can be seen as an ‘outside the fence’ solution, better suited to geographically dis- persed environments using commer- cial off the shelf hardware.


Globalisation


The evolution of these technologies has come amidst a greater shift in globalisation. Supply chain networks are being strengthened by advance- ments


in international trade,


improved transport infrastructure and telecommunications such as fibre optic broadband. Although this has reduced response


times, production environments are under greater stress to deliver. With the news of Toyota’s recall of 885,000 vehicles in the US, it is evident that non-traditional duties such as reverse logistics are placing undue stress on production environments.


ot many things in life remain con- stant and ulti- mately change is


Holistic architecture Yokogawa has always favoured an inte- grated approach. The developments in globalisation have meant that new norms in control architecture are now upon us. The irony is that a theory developed in a pre-World Wide Web era is more relevant today than ever. Purdue enterprise reference archi- tecture (PERA) is a reference model for enterprise architecture in computer integrated manufacturing. Developed in the 1990s, PERA theory led to the modern enterprise control standard known as ANSI/ISA-95.


The ISA-95 standard breaks down control environments into levels of integration. Level zero is defined as the physical process in a plant. Level one consists of intelligent devices such as smart sensing and actuation. Level two brings in control systems DCS and SCADA for supervising, monitoring and controlling the process. It is evident that modern develop- ments have blurred the lines between these levels. As such, Yokogawa's inte- grated approach seeks to compliment the robust control of DCS on a plant level, with SCADA as a supervisory umbrella at the hybrid enterprise level.


The future


So what of the future? Only five years ago the forward thinking trend was for real time information and big data. The internet of things justified the idea of context-based events, from alarm notifications to smart diagnostics. A new era of HMI is rolling-out through the use of intuitive touchscreen tablet devices. Maintenance crews can be notified via satellite ground position- ing systems (GPS), of nearby alarms, allowing them to respond immediately, pulling up PDF troubleshooting and datasheets in the process.


All this data is increasingly being stored in the Cloud. Although there are still security concerns for mission critical applications, improvements in data encryption mean that this is fast becoming a viable option. As we move towards an uncertain but exciting future, one thing remains certain - change is constant. Human beings are still very much part of the process and will remain so for the foreseeable future. We can only hope that we have as lasting an impact as Homer Simpson!


Yokogawa www.yokogawa.com/uk T: 01928 597 100


Enter 205 19


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  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56