23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

OPC UA 57-3<br />

Enterprise network<br />

Operations network<br />

Plant floor<br />

network<br />

UA<br />

server<br />

UA<br />

server<br />

UA<br />

client<br />

UA<br />

client<br />

UA<br />

client<br />

UA<br />

client<br />

UA<br />

server<br />

UA<br />

server<br />

UA<br />

client<br />

UA<br />

server<br />

UA<br />

client<br />

Enterprise<br />

semantics<br />

Process<br />

semantics<br />

Device<br />

semantics<br />

“Aggregating” UA Servers<br />

extract and process data<br />

from lower level “Device”<br />

UA Servers.<br />

Data is recast using<br />

different information models<br />

appropriate for the clients at<br />

the higher level.<br />

FIGURE 57.3<br />

Chaining of UA servers and UA clients.<br />

• Manufacturing execution system (MES) that is usually deployed in the supervisory, simulation,<br />

and scheduling of batch processes (e.g., pharmaceutical process).<br />

• Middleware that serves intra-plant applications and extra-plant (enterprise wide) applications<br />

(Figure 57.3).<br />

Middleware is a piece of software that serves to “glue together” or mediate between two separate and<br />

usually already existing programs. Middleware is sometimes called plumbing because it connects two<br />

sides of an application and passes data between them. Middleware plays a crucial role in enterprise<br />

applications by integrating system components, allowing them to interoperate correctly and reliably,<br />

and facilitating system management and evolution. This is a very important domain of applications that<br />

OPC UA is aimed at, bridging the <strong>industrial</strong> information <strong>systems</strong> with the enterprise one.<br />

The system architecture of OPC UA is based on the well-known concept of client–server interaction.<br />

Each system may contain multiple clients and servers. Each client may interact concurrently with one<br />

or more servers, and each server may interact concurrently with one or more clients. An application may<br />

combine server and client components to allow interaction with other servers and clients, as shown in<br />

Figure 57.3. Peer-to-peer interactions between servers are also possible, as shown in Figure 57.4:<br />

UA server<br />

UA Binary TCP<br />

or<br />

SOAP XML over HTTP<br />

Server<br />

interface<br />

Client<br />

interface<br />

IP network<br />

Client<br />

interface<br />

Server<br />

interface<br />

UA server<br />

FIGURE 57.4<br />

Peer-to-peer interactions between UA servers.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!