Topics

Environment for Industrial System Integration

Why OPC? What is OPC? Technical features of OPC Data Access (DA) Logical Object Model of OPC Applications (Client/Server) Interfaces of OPC Data Access Data source in OPC Server Mechanism of data exchange between OPC Client/Server Structure of modern SCADA systems Implementation Application

St. Petersburg, December 3, 2002

Architecture of modern process control system

Business Management

The I/O driver problem C/C++ Application SCADA SCADA

Supervision

Software Driver A
Physical I/O

Software Driver B
Physical I/O

Software Driver C
Physical I/O

Process Management

Automatic Control

Device A

Device B
Allow
Field Management

Device C
Not allow

Each SCADA - system <=> driver for each equipment. Two applications can not have access to one driver in the same time. Remote access is not supported

How does OPC solve the problem? Architecture of modern process control system
Business Management

C/C++ Application
OPC OPC

SCADA

SCADA

OPC

Supervision

OPC

OPC

OPC

Software Driver A
Physical I/O Physical I/O

Software Driver B Device C

Software Driver C
Automatic Control

Process Management

Physical I/O

Device A

Device B

Field Management

Architecture of modern process control system

Business Management

What is OPC?

Supervision

Process Management

Automatic Control

Field Management

SCADA Company Country OPC is an industry standard created by a number of worldwide InTouch Wonderware USA leading hardware and software suppliers. GenieDAQ Advantech USA The OPC standard specifies applications applications Genesis32 Iconics an interface between client USA and servers of processAdAstra data. Trace Mode Russia The standard was purposely limited to the reading and writing of of Vijeo Look Schneider Electric France realtime process values (Data Access DA). Alarm handling, process real Citect Ci Technologies Australia events (A&E), historical data accessDATA (HDA), were all OPC ([Link] ). deferred to Factory Link Foundation United States Co. USA subsequent releases ofRockwell the standard. RSView Software Inc. Iconics USA OPC is supported ~370 companies: (USA), USA), An OPC compliant client can read and write ), data to any OPC LabView Instruments USA Wonderware (National USA), Adastra (Russia), Siemens USA), Russia compliant server. iFIX (Germany), Intellution USA Software (USA), Germany), Rockwell USA), Intellution (USA), Electric WinCC Siemens (Australia), Germany USA), Ci Technologies Australia), Schneider (France), Russia (Russia), Russia), Master SCADAIndusoft InSAT Russia Russia), Fastwel ( Russia), ABB Automation (USA), (USA), USA), Fieldbus Foundation USA), CIMPLICITY GE Fanuc USA Toshiba (Japan), ), Hitachi ( Japan), Japan Japan), National Instruments Contour Obedinenie Uig Ucraina (USA) USA), Wizcon Axeda USA CrugCrug Russia Crug-2000 Elipse SCADA Elipse Software USA
OPC Server Software driver

What is OPC? The logical object model OPC Data Access Server
OPC Interfaces

Object Linking & Embedding OPC Server OPC Group OPC Group OPC Group

OPC OLE for Process Control OPC OLE for Production Control OPC Openness, Productivity and Connectivity OPC OLE COM for Process Control
OPC Interfaces

OPC Group OPC Group OPC Item Device Tag Tag Tag

OPC Group OPC Group OPC Item

OPC Group OPC Group OPC Item Device Tag Tag Tag

COM Component Object Model provides interfaces and inter-component communication. Through COM, an application may use features of any other application object. COM is the core of DCOM (Distributed COM), ActiveX.

OPC Item Object

The path of real - time data in the integrated process control system
Supervision
SCADA station SCADA station

Connection to a data source. Properties:

v1, q1, t
OPC Server

3.1, 3.8, 3.2, 2.6, 3.9, 4.0, 3.5, 2.9, 2.7, 2.0, 2.1, 1.9, 1.8, 1.7, 1.6, 0.9,GOOD, 4.5, 4.2, 4.3, 4.6, 4.4, 4.1, BAD, , [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] v4, q ,t 4

v5
OPC Server

v6, q6, t
OPC Server

v1, q1, t

3.8, 3.2, 2.6, 3.9, 4.0, 3.5, 2.9, 2.7, 2.0, 2.1, 1.9, 1.8, 1.7, 1.6, 4.2, 4.5, 3.2, 4.3, 4.1, 5.1, 4.6, 4.4, 4.1, 4.3, 4.2, 3.1, 3.2, 3.5, 3.8, GOOD, BAD, BAD, BAD OK, ,, 4.5, v[Link] 4, q4, t [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link]

v3, q3, t
PLC Controller level Passive I/O boards

v5, q5, t' t'

v6, q6, t
Upper controller level

Item i Data value (v) VARIANT type: boolean, boolean, integer, float, string, Quality (q) UNCERTAIN, GOOD, BAD, Tag j Time stamp (t) - FILETIME: {yyyy:mm:dd:hh:mm:ss :} {yyyy:mm:dd:hh:mm:ss:} - The Timestamp should indicate the time that the value and quality was obtained by the device.

Instrumentation

PLC

v1, t

v2, t

v3, t

v4 ,t 3.1, 3.8, 3.2, 0.9, 2.6, 4.5, 5.1, 4.2, 3.9, 4.0, 4.3, 4.6, 4.4, 4.1, 3.5, 2.9, 2.7, 2.0, 2.1, 1.9, 1.8, 1.7, 1.6, [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link]

v5, t' t'

Parameters of engineering process v value, q quality, quality, t timestamp

v6, t

The logical object model OPC Data Access Server OPC Group Object

OPC Interfaces

OPC Server

Group i Item 1 Item 2 Item 3

OPC Interfaces

OPC Group OPC Group OPC Group

OPC Group OPC Group OPC Item OPC Group OPC Group OPC Item Device Tag Tag Tag

OPC Group OPC Group OPC Item

Collection of items. Clients must use group to access items. Properties: Requested update rate; Percent dead band; Time bias;

Device

Tag Tag Tag

The logical object model OPC Data Access Server

OPC Server Object

OPC Interfaces

OPC Server

It is a COM object. Collection of groups.

Server i Group 1 OPC Group OPC Group OPC Item Device Group 2 Group 3

OPC Interfaces

OPC Group OPC Group OPC Group

OPC Group OPC Group OPC Item

OPC Group OPC Group OPC Item

Device

Tag Tag Tag

Tag Tag Tag

OPC Interfaces

OPC Group OPC Group OPC Group Device Object OPC Group OPC Group OPC Item Device Tag Tag Tag

OPC Group OPC Group OPC Item

OPC Group OPC Group OPC Item

Device

Device i Tag 1 Tag 2 Tag 3

Tag Tag Tag

Physical device abstraction, hardware connection management. Direct communication with I/O devices or user designed DLL. Collection of tags. Tags are updated regularly.

Tag

OPC DA 1.0

Parameter of engineering process. Analog, digital, mumeric, mumeric, string, etc. Item Name = Full tag name

Item i Name = [Link] [Link]

Device 1 Name = Meteorologic Meteorologic

Tag 1 Name = Temperature

Tag 2 Name = Pressure

Tag 3 Name = Humidity

Class Tag { public: GetValue(.); GetValue(.); SetValue(); SetValue(); private: CString DWORD VARIANT DWORD FILETIME }

Name; Address; Value; Quality; TimeStamp; TimeStamp;

Overall picture of the client/server interaction Client 2

Client 1

Data source in OPC Servers

Read from servers internal cache. Read directly from device. Write directly to the device.

Server 1 Group Group 12

Server 2

Group Group 12

Modes of data exchange in OPC Servers

Item 1 Item 2 Item 1

Item 1

Item 1

OPC Server

Item 2

Item 3 Device 2 Tag 1 Tag 2

Synchronous read/write. Asynchronous read/write. Subscription (for read). Refresh (for read).

Device 1

Tag 1 Tag 2 Tag 3

Synchronous mode

Asynchronous mode Client 1

Data

Client 1

Server 1

Server 1 Group Group 12 Item 1 Item 1

OPC Server

Group Group 12

Item 1

Item 1 Item 2 Item 3 Device 1 Tag 1 Tag 2 Tag 3 Device 2 Tag 1 Tag 2

OPC Server

Item 2

Item 3 Device 2 Tag 1 Tag 2

Device 1

Tag 1 Tag 2 Tag 3

Subscription Client 1

Refresh = Asynchronous mode for all items in a group

Client 1

Server 1 Group Group 12 Item 1

OPC Server

Server 1

Group Group 12 Item 1 Item 2 Item 3 Device 1 Tag 1 Tag 2 Tag 3 Item 1

Item 1

OPC Server

Item 2 Data changed

Item 3 Data changed Device 2 Tag 1 Tag 2

Device 1

Device 2 Tag 1 Tag 2

Tag 1 Tag 2 Tag 3

Structure of modern SCADA systems

Alarm & Events Historical DA OPC Server OPC Server

Implementation
From zero OPC Specification; Protocol, Driver or Server of I/O devices; COM Programmers, Visual studio C++. OPC Toolkits Very high price; Restriction. Universal OPC Server
OPC Client OPC Client I/O Device I/O Device DAQ Component (DLL) DLL) DAQ Component (EXE) EXE)

MatLab, XML MatLab, Excel, VB, VC++ OPC Server

Data Base

SCADA
Data Access OPC Server PLC Control Object

Data Access OPC Server

General part EXE) ) (EXE

PLC

Coordinator (DLL) DLL)

Control Object

Control Object

Fixed

Specific part

Universal OPC Server

Overpatching by manufacturing engineer

Application
GeniDAQ
Very interesting concept Need for industrial system integration (industrial devices, SCADA SCADA systems) Standard across vendors, no longer separate drivers for SCADA. Allow applications to easily access subsystem data Are optimized for use over a network

Summary

GeniDAQ

References
X-Ray luminescent Separator
1. 2.

3. 4. 5. 6.

Frank Iwanittz, Iwanittz, Jrgen Lange. OPC: fundamentals, implementation, and application / [Softing ]. Heidelberg: Huthig. [Softing]. Huthig. 2002. 221 p. Frantiek Plil, Plil, Michael Stal. Stal. An architecture view of distributed objects and components in CORBA, Java RMI and COM/DCOM // Software Concepts & Tools. 1998. 19. P. 1414-28. Mike Santory. Santory. OPC: OLE for Process Control // RealReal-Time Magazine. 1997. 4. P. 7878-81. OPC Alarms and Events Custom Interface Standard Version 1.02. OPC OPC Foundation. Austin, Texas, November 1999. OPC Data Access Custom Interface Standard Version 2.05. OPC Foundation. Foundation. Austin, Texas, December 2001. OPC Historical Data Access Custom Interface Standard Version 1.1. 1.1. OPC Foundation. Austin, Texas, January 2001.

Truong D. Chau, Chau, Department of Automatics & Computing, Faculty of Technical Cybernetics, SaintSaint-Petersburg State Polytechnic University, Russia e-mail: tanchau@[Link]