exaquantum/rds copyright © yokogawa electric corporation 8 december, 2008 remote data...

Exaquantum/RDSCopyright © Yokogawa Electric Corporation8 December, 2008

Remote Data Synchronization

2



What is the Requirement (1)?

Transfer process data between Exaquantum systems, for example sea based:

3



What is the Requirement (2)?

Or land based:

4



What other Methods are Available?

Exaquantum Multi-Server, however– Possible overload of the available bandwidth

with the remote Exaquantum system due to the demands of the users for process information

– Network security risk by allowing remote users direct access to remote locations

Exaquantum OPC DA & HDA, however– OPC DA may lose process data during short

network interruptions making it unsuitable for use on a volatile network link

– Long network interruptions may result in a substantial backlog of data to transfer via OPC HDA that may not be possible based on the available network capacity

5



What is the Actual Solution?

ExaquantumServer

(Publisher)

ExaquantumServer

(Consumer)

Transfers historized Exaquantum Process Data over a fluctuating bandwidth Ethernet Connection

such as satellite or microwave link

6



Key Benefit #1

Efficient, secure data transfer at near real time

Exaquantum RDSPublisher

Application

Exaquantum RDSPublisher Service

Exaquantum RDS Storage

HDA

Exaquantum RDSConsumer Application

Exaquantum RDSConsumer

Service

Exaquantum RDS Storage

TCP/IP Network Connection HDAExaquantum

HistorianExaquantum

Historian

Exaquantum Server (Publisher) Source of Data Exaquantum Server (Consumer) Destination of Data

7



Key Benefit #2

Enables History Catch-up whenever the connection is re-established

ExaquantumServer

(Publisher)

ExaquantumServer

(Consumer)

01001010100101

8



Key Benefit #3

Source Tag names and Paths can be converted to destination Tag Names and Paths (Tag Mapping) where tag naming across the two systems is not consistent

ClientTags

Tag Mapping

ServerTags

Exaquantum HistorianConsumer

Exaquantum HistorianPublisher

9



Key Benefit #4

Data Transfer Encryption available for greater security

ExaquantumServer

(Publisher)

ExaquantumServer

(Consumer)

Encrypted Data

10



Key Benefit #5

As a result of permanent or significant network outage, tag information can be written to a CD/DVD at the Publisher and sent to the Consumer

ExaquantumServer

(Publisher)

ExaquantumServer

(Consumer)

11



Key Benefit #6

Process data flow can be bi-directional

ExaquantumServer

(Publisher& Consumer)

ExaquantumServer

(Publisher & Consumer)

12



Key Benefit #7

Multiple Publisher Exaquantum servers can be connected to a single Consumer Exaquantum server

ExaquantumServer

(Publisher)

ExaquantumServer

(Consumer)

ExaquantumServer

(Publisher)

ExaquantumServer

(Publisher)

13



Key Benefit #8

A Publisher Exaquantum server can be connected to a multiple Consumer Exaquantum servers, for example

ExaquantumServer


ExaquantumServer


ExaquantumServer


ExaquantumServer


14



Key Benefit #9

An Exaquantum/RDS Publisher license can be connected to Exaopc, for example

ExaopcServer

(Publisher)

ExaquantumServer

(Consumer)

ExaopcServer

(Publisher)

ExaopcServer

(Publisher)

15



Please provide me with more information

Technical Information

16



Exaquantum/RDS Details

Version: R1.0

– Released: March, 2008

Version: R2.0

– Released: December, 2008

17



Key Features

Communication via TCP/IPData transfer delay can be configured for minimal delay (near real-time) or any greater valueFor additional security, data encryption can be appliedTransferred historized process data includes OPC tags, Calculation tags, Manual tags including AggregationsTag units, tag description, etc. are also transferred upon changeA sub-set of Exaquantum tags can be transferred

18



How does it Work?

Two simple functions– Extract process data from the Publisher’s Exaquantum system– Store process data into the Consumer’s Exaquantum system

Exaquantum RDS Publisher Exaquantum RDS Consumer

ExaquantumHistorian

ExaquantumHistorian

OPC HDATCP/IP Network

ConnectionOPC HDA

19



Data Transmission Example

Assuming– Tag data is extracted from Exaquantum every minute– 30,000 Tag values will be sent every minute– The average length of Tag Paths will be between 40 and

50 characters long– The network connection allows 100 KB/second data

throughput

Then– 43,200,000 Tag values can be sent each day– The average size of data being sent over the network per

minute will be:• 918 KB Uncompressed Data• 670 KB Compressed (Unicode)• 254 KB Compressed (Non-Unicode)

– Non-Unicode data will take approximately 2.5 seconds to send over the network and 6.5 seconds if the data is Unicode.

20



User Interface – Publisher Main Window

21



User Interface – Publisher (Statuses)

22



User Interface – Publisher (Settings)

23



User Interface – Publisher (Tag Mapping)

24



User Interface – Publisher (Schedule)

25



User Interface – Publisher (Tag Export)

26



User Interface – Publisher (History Catch-Up)

27



User Interface – Publisher (Logging)

28



User Interface – Consumer (Statuses)

29



User Interface – Consumer (Settings)

30



User Interface – Consumer (Tag Import)

31



User Interface – Consumer (Logging)

32



foresightinnovationquality

In Summary, Exaquantum/RDS Delivers…

Secure, efficient transfer of historical process data between Exaquantum Systems connected by a potentially volatile network linkEasy to install, configure and manageLow cost of ownership

33



Thank you very much for your attention

exaquantum/rds copyright © yokogawa electric corporation 8 december, 2008 remote data...

Documents

remote exaquantum system

transfer process data

exaquantum multiserver

exaquantum systems

process data flow

secure data transfer

substantial backlog

consistent slide