V1.1 GB

OPC FOUNDATION – www.opcfoundation.org

Manufacturer-specific extensions Open OPC Unified Architecture – – > 450 members Information models of other organisations – Platform-neutral The universal communication platform – All areas of application DA AC HA Prog for standardised information models – All connections Base services of OPC UA Productivity ➞ OPC Unified Architecture brings can also be described completely Cooperation with other – Industry standard two elementary innovations into with OPC UA. The object-oriented standardisation organi- – Manufacturer-independent – Interoperability the OPC world. On the one hand, rules according to which the ad- sations was important – Reliability the -specif- dress space of an OPC UA server for OPC UA from the ic protocol DCOM is replaced is structured and the OPC UA in- beginning by open, platform-independent terface for accessing it are thereby Collaboration protocols with integrated secu- kept so general that OPC UA can This simple extensibility by in- – Device Integration rity mechanisms. On the other, be regarded as a network-capa- formation models makes OPC – IEC 61131-3 / PLCopen – Analyzer Device Integration the proven OPC features, such ble programming language. OPC UA very interesting for other standardisation organisations. – ISA-95, ISA-88 as Data Access, Alarms & Events UA only becomes specialised for They only have to define which – MTConnect and Historical Data Access, are technology through information is to be exchanged, – Smard Grid summarised in an object-oriented specific information models such but no longer how the informa- – Field Device Integration model and supplemented by new as Data Access, Alarms & Condi- tion must be exchanged. Be- – EDDL and FDT and powerful features, such as tions, Historical Access and Pro- fore the start of the OPC UA methods and type systems. As a grams. For these information mod- specification, this was one of ADDRESS: result, not only can the OPC inter- els, there is no longer any need to the most important require- ments that OPC UA as a uni- face be directly integrated into sys- extend the basis and the protocols versal communication platform OPC Foundation tems on arbitrary platforms with or the programming interfaces. ■ and IEC standard can form a 16101 N. 82nd Street different programming languages, basis for other standards. Suite 3B but arbitrary complex systems Scottsdale, AZ 85260-1868 USA

CONTACT:

Phone: (1) 480 483-6644 OPC UA – Standardised communication acc. to IEC 62541 Fax: (1) 480 483-7202 [email protected]

OPC UNIFIED ARCHITECTURE COMPANION group of OPC members within the OPC Foundation INFORMATION: SPECIFICATIONS which defines an information model for special ➞ OPC UA consists of a list of specifications for the branches of industry or areas of application. www.opcfoundation.org basic functions and the information models based The specification OPC UA for Analyzer Devices (ADI) on them, such as Data Access and Alarms & Condi- was created in this way on the basis of customer tions. Specifications that define further information requirements. Another possibility is a common work- models beyond that are called Companion Specifi- ing group with one or more other organisations with ALREADY AVAILABLE cations. the objective of defining an OPC UA information Companion model for a standard outside the OPC Foundation. SpeCifiCationS HOW ARE COMPANION SPECIFICATIONS The information model OPC UA for IEC 61131-3 was CREATED? created in this way with PLCopen. ■ ➞ OPC UA for Devices ➞ OPC UA Companion Specifications are devel- ➞ OPC UA for Analyzer Devices oped in various ways. One possibility is a working ➞ OPC UA for IEC 61131-3 OPC UA FOR DEVICES (DI) ➞ A generally accepted model for the configura- Analyzer Devices and OPC UA for IEC 61131- tion of hardware and software components was 3. The information model defines basetypes for created in the common working group of OPC configurable components and devices; it defines Foundation, User Organisation (PNO), concepts for the logical grouping of parameters, HART Foundation, Foundation (FF) and methods and components and it defines points COOPERATION: Field Device Tool (FDT) for the standardised con- of entry in the OPC UA server address space. figuration of field devices. This base model was Besides that, information for the identification of ➞ PLCopen released by the OPC Foundation as an indepen- devices and the available protocols is defined. An ➞ ISA ➞ MTConnect dent information model and also serves as the initial version of this specification has been avail- ➞ FDT basis for further standards such as OPC UA for able since the end of 2009. ■ ➞ PNO ➞ HART ➞ FF Extended options despite simplified interface – new OPC UA communication is applied in existing and new standards

OPC UA FOR ANALYZER DEVICES (ADI Field Device Integration (FDI) ➞ This specification defines an information model for ➞ Two standards are used today for the configu- complex devices for process analyzer, for example ration of field devices. Electronic Device Description gas chromatography. Apart from the various com- Language (EDDL) works according to the principle ponents of such a device, parameters for configura- that the configuration parameters of a field device are tion and typical state machines are standardised. defined by a description file and that the configura- The ADI specification was created at the suggestion tion takes place on this basis. Field Device Tool (FDT) of the users of process analysis devices in order to works according to the principle that the equipment simplify integration into automation systems. The manufacturer provides a software component for a ADI specification uses the OPC UA DI model as a general configuration tool with the device. Both stan- basis. dards are to be merged in the future via the common FDI standard using OPC UA. OPC UA for IEC 61131-3 (PLCopen) In FDI, a field device is to be described via a so- ➞ The IEC 61131-3 standard defines various pro- called Device Package. These consist of a general gramming languages and a software model for the parameter description and user interface elements. programming of control systems. The implementa- The configuration server is thereby an OPC UA serv- tion of this software model on an OPC UA server er that fills its address space on the basis of the De- address space is defined in the specification. Thus, vice Packages, and the configuration interfaces are corresponding OPC UA object types are created OPC UA clients that access the equipment param- from declarations of function blocks in the PLC and eters via OPC UA and use specific user interface ele- corresponding OPC UA objects from instances of ments from the Device Packages for the display. ■ the function blocks. This results in the advantage that a control program, regardless of the controller being used and the OPC UA server, is always imple- mented in the same structure of objects in the ad- dress space.

OPC UA – interoperability at the semantic level

ISA-95 AND ISA-88 this field, various mappings of existing standards to ➞ The two ISA standards define information models OPC UA or the direct use of OPC UA in new stan- for production control systems for batches and MES. dards are under discussion. Mapping to OPC UA is planned. MTConnect

MORE INFORMATION Smart Grid ➞ MTConnect defines standards for the provision of ➞ There are various standards in the field of power machine data. Mappings of these data descriptions www.opcfoundation.org generation and power distribution and new stan- to an OPC UA information model are to be defined in dards are being created for smart grid networks. In a common working group. ■