MAY-JUN 2019

Issue link:

Contents of this Issue


Page 13 of 55

most aspects of industrial automation, the O-PAS Standard will greatly im- prove interoperability among indus- trial automation systems and compo- nents. This will lower implementation and support costs for end users, while allowing vendors to innovate around an open standard. For more information on OPAS Ver- sion 1.0, please download the standard at p190. Submit feedback by emailing ■ ABOUT THE AUTHOR Dave Emerson is vice president of Yokogawa's U.S. Technology Center in Dallas, Texas. He is experienced in applying and devel- oping automation systems used in the process industries. Emerson is an ISA Fel- low and a member of Control magazine's Process Automation Hall of Fame. He has more than 30 years of experience partici- pating on U.S. and international consen- sus standards committees, such as ISA- 88, ISA-95, IEC TC65, and ISO TC184. He also represents Yokogawa in several industry groups, including leadership roles with MESA, MIMOSA, and the OPC Foundation. Emerson is Yokogawa's pri- mary representative with OPAF and is currently co-chair of OPAF's Enterprise Architecture Working Group. View the online version at Building a system End users today must work with and integrate multiple systems in most every process plant or facility. There- fore, the OPAS Standard was designed so users can construct systems from components and subsystems supplied by multiple vendors, without requir- ing custom integration. With the OPAS Standard it becomes feasible to assimi- late multiple systems, enabling them to work together as one OPAS-compliant whole. This reduces work on capital projects and during the lifetime of the facility or plant, leading to a lower total cost of ownership. By decoupling hardware and soft- ware and employing an SOA, the neces- sary software functions can be situated in many different locations or proces- sors. Not only can software applica- tions run in all hardware, but they can also access any I/O to increase flexibil- ity when designing a system. One set of components can be used to create many different systems us- ing centralized architectures, distrib- uted architectures, or a hybrid of the two. System sizes may range from small to large and can include best- in-class elements of DCS, PLC, SCA - DA, and IIoT systems and devices as needed. Information technology (IT) can also be incorporated deeper into industrial automation operational technology (OT). For example, DMTF Redfish is an IT technology for securely managing data center platforms. OPAF is adopt- ing this technology to meet OPAS sys- tem management requirements. Comprehensive and open Each industrial automation supplier offers a variety of devices and sys- tems, most of which are proprietary and incompatible with similar prod- ucts from other vendors and some- times with earlier versions of their own products. End users and system integrators trying to integrate auto- mation systems of varying vintages from different suppliers therefore have a challenging job. To address these issues, OPAF is making great strides toward assem- bling a comprehensive, open process automation standard. Partially built on other established industry stan - dards, and extending to incorporate COVER STORY 14 INTECH MAY/JUNE 2019 WWW.ISA.ORG External management tool OCF networking infrastructure Application Configuration information Distributed control node (DCN) Distributed control platform (DCP) DCF services Distributed control node (DCN) Distributed control framework (DFC) Field devices, sensors, actuators... Figure 3. DCNs are conceived as modular elements containing DCP (hardware) and DCF (software), both of which are used to interface field devices to the OCF. RESOURCES "New software for next-gen automation" "Breaking closed architecture bonds" "End users want COTS, and they want it now"

Articles in this issue

Links on this page

Archives of this issue

view archives of InTech - MAY-JUN 2019