OPC client & server in I/A

Agenda

What is OPC?
OPC FBM (232/233)
Part of FDSI FBMs
AIM OPC Server 3.3
OPC IOGate Client
Security issues with OPC
Problem solving

Invensys Confidential

What is OPC?

What is OPC? - Acronyms

OPC = OLE for Process Control
OLE = Object Linking & Embedding
(Microsoft standard)
OLE is based on COM technology
COM = Common Object Model
Microsoft renamed & enhanced COM into:
DCOM = Distributed Common Object Model
DCOM is also used as the communication fundament
for ActiveX
4

Invensys Confidential

What is OPC? - Different standards

The standards:
OPC DA
Used to move real-time data from PLCs, DCSs, and other control devices to HMIs and other
display clients.

OPC HDA
Where OPC Data Access provides access to real-time, continually changing data, OPC Historical
Data Access provides access to data already stored. From a simple serial data logging system
to a complex SCADA system, historical archives can be retrieved in a uniform manner.

OPC A&E
Provides alarm and event notifications on demand (in contrast to the continuous data flow of
Data Access). These include process alarms, operator actions, informational messages, and
tracking/auditing messages.

OPC DX
This specification takes us from client/server to server-to-server with communication across
Ethernet fieldbus networks. And adds remote configuration, diagnostic and
monitoring/management services.

Invensys Confidential

What is OPC? - example 1

3rd party opc server

AIM opc server

Corporate network

AIMAPI server

Control network
opc client

Invensys Confidential

What is OPC? - example 2 - Linking I/A

systems
I/A 6.x/7.x
legacy nodebus

I/A 8.0
Control network

Corporate network

opc client
AIMAPI server

AIM opc server

Invensys Confidential

What is OPC? - example 3 status

exchange
I/A 8.0
Control network

Corporate network

opc client
3 party server
status bits

0x????

Opc status bits

0x00c0

I/A status bits

0x0023

rd

3rd party opc server

Invensys Confidential

OPC FBM (232/233)

OPC FBM 232/233

Hardware:
FBM 232 and FBM233 are FDSI FBMs
Hardware the same, difference is in the driver.
FBM 232 partno: P0926GW
FBM 233 partno: P0926GX
Software:
OPC client only.
Can connect to one opc server at a time
opc.ziph file
B0700AH document FDSI FBM
B0700BH document OPC FBM
10

Invensys Confidential

OPC FBM 232/233 configuration overview

3 part configuration:
Enter ECB200/201 details (see FDSI presentation)
Enter OPC details in FDSI configurator
Enter tag details in FDSI configurator

11

Invensys Confidential

OPC FBM 232/233 ECB configuration

FDSI config opc fbm

12

FDSI config opc tag group

Invensys Confidential

OPC FBM 232/233 configuration files

Choose type

Choose type of protocol

13

Invensys Confidential

OPC FBM 232/233 config file for ecb200

Choose type of fbm

Edit source & dest. IP address

Enter OPC Server details

14

Invensys Confidential

OPC FBM 232/233 config file for ecb201

Auto-generate tags

Enter opc tag details

List of opc tags

15

Invensys Confidential

OPC FBM 232/233 - SMDH FCP Detail

16

Invensys Confidential

OPC FBM 232/233 FBM Equip Info page 1

Most important fields

17

Invensys Confidential

OPC FBM 232/233 FBM Equip Info page 2

Most important fields

18

Invensys Confidential

OPC FBM 232/233 FBM Equip Info page 3

Most important fields

19

Invensys Confidential

OPC FBM 232/233 FBM Equip Change

Most important fields

20

Invensys Confidential

OPC FBM 232/233 Group Equip Info page

1
Most important fields

21

Invensys Confidential

OPC FBM 232/233 Group Equip Info page

2

22

Invensys Confidential

OPC FBM 232/233 Group Equip Change

Most important fields

23

Invensys Confidential

AIM OPC Server

AIM OPC Server - Configuration

AIMapi configuration
OPC server configuration
Create Alias.cfg for OPC server
With alias.cfg information OPC server can already open
connections to aimapi

25

Invensys Confidential

AIM OPC Server aimapi configuration 1

OPCDAO license keys

Machine name == user name

Add machine name here:

26

Invensys Confidential

AIM OPC Server aimapi configuration 2

Check OPCDAO package

27

Invensys Confidential

AIM OPC Server Client/Server

configuration
Dcomcnfg details
Creating users
Checking user rights
Adding users on both machines

28

Invensys Confidential

AIM OPC Server

Dcomcnfg tool

Enable DCOM

Check settings

29

Invensys Confidential

OPC IOGate Client

OPC IOGate Client

I/A 8.0 does not support AW70 integrators, so IOGate is
not supported on 8.0
I/A 8.1 will support AW70 integrators.

31

Invensys Confidential

Security considerations

OPC FBM Security

Good security because:
FBM separates OPC network and our

3rd party opc server

AIM opc server

control network
Only CP's can talk to FBMs via fieldbus
No need for user accounts in FBM
No acces into control network via FBM

Corporate network
AIMAPI server

Control network
opc client

33

Invensys Confidential

AIM OPC Server 1Box example

3rd party opc client

Bad
NeedtoopenDCOM
portsinfirewall

Corporate network

AIM OPC server

AIMAPI server

1box approach Bad

AW70+AIMAPI+AIM OPC Server on one machine
Central point of failure
OPC needs open ports to corporate network (DCOM)
Needs constant maintenance and MS hotfix installation

34

Invensys Confidential

Control network

AIM OPC Server 2Box example

AIM OPC server

3rd party opc client

Good
StandardWindows
machine

Corporate network

Good
Onlyneedtoopenaimapi
portonfirewall

AIMapi server

2box approach Good

Control network

AW70+AIMAPI on one machine, AIM OPC server on another machine

AIM OPC Server is not an AW70
Can put firewall in between AW70 and OPC, only AIMAPI needs to go through
(port 45678)
Customer can install MS hotfixes on OPC server
35

Invensys Confidential

Troubleshooting

Troubleshooting OPC FBM

Diagnostic Utility for OPC client driver - K0173WG

37

Invensys Confidential

Troubleshooting AIM OPC server

AIM OPC server
Server logfile
AW70 AIMapi server tools
Apispy menu 913 (shows list of C:B.Ps in api
memory)
Som opdb (shows list of C:B.Ps in OM)

38

Invensys Confidential

Q&A

Pleaseemailquestions&commentsto
ips.csc@invensys.comwithV8.0Inquiries
inthesubjectfield
39

Invensys Confidential