350 likes | 576 Views
Remote Data Synchronization. Transfer process data between Exaquantum systems, for example sea based:. What is the Requirement (1)?. Or land based:. What is the Requirement (2)?. What other Methods are Available?. Exaquantum Multi-Server, however
E N D
Transfer process data between Exaquantum systems, for example sea based: What is the Requirement (1)? Remote Data Synchronization
Or land based: What is the Requirement (2)? Remote Data Synchronization
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 Remote Data Synchronization
Exaquantum Server (Publisher) Exaquantum Server (Consumer) What is the Actual Solution? Transfers historized Exaquantum Process Data over a fluctuating bandwidth Ethernet Connection such as satellite or microwave link Remote Data Synchronization
Key Benefit #1 • Efficient, secure data transfer at near real time Remote Data Synchronization
Enables History Catch-up whenever the connection is re-established Key Benefit #2 0100101 0100101 Exaquantum Server (Publisher) Exaquantum Server (Consumer) Remote Data Synchronization
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 Key Benefit #3 Remote Data Synchronization
Data Transfer Encryption available for greater security Key Benefit #4 Encrypted Data Exaquantum Server (Publisher) Exaquantum Server (Consumer) Remote Data Synchronization
Exaquantum Server (Publisher) Exaquantum Server (Consumer) 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 Remote Data Synchronization
Process data flow can be bi-directional Key Benefit #6 Exaquantum Server (Publisher & Consumer) Exaquantum Server (Publisher & Consumer) Remote Data Synchronization
Multiple Publisher Exaquantum servers can be connected to a single Consumer Exaquantum server Exaquantum Server (Consumer) Exaquantum Server (Publisher) Exaquantum Server (Publisher) Exaquantum Server (Publisher) Key Benefit #7 Remote Data Synchronization
A Publisher Exaquantum server can be connected to a multiple Consumer Exaquantum servers, for example Exaquantum Server (Publisher & Consumer) Exaquantum Server (Publisher & Consumer) Exaquantum Server (Publisher & Consumer) Exaquantum Server (Publisher & Consumer) Key Benefit #8 Remote Data Synchronization
An Exaquantum/RDS Publisher license can be connected to Exaopc, for example Exaquantum Server (Consumer) Exaopc Server (Publisher) Exaopc Server (Publisher) Exaopc Server (Publisher) Key Benefit #9 Remote Data Synchronization
Technical Information Please provide me with more information Remote Data Synchronization
Exaquantum/RDS Details • Version: R1.0 • Released: March, 2008 • Version: R2.0 • Released: December, 2008 Remote Data Synchronization
Key Features • Communication via TCP/IP • Data transfer delay can be configured for minimal delay (near real-time) or any greater value • For additional security, data encryption can be applied • Transferred historized process data includes OPC tags, Calculation tags, Manual tags including Aggregations • Tag units, tag description, etc. are also transferred upon change • A sub-set of Exaquantum tags can be transferred Remote Data Synchronization
How does it Work? TCP/IP Network Connection OPC HDA OPC HDA • Two simple functions • Extract process data from the Publisher’s Exaquantum system • Store process data into the Consumer’s Exaquantum system Remote Data Synchronization
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. Remote Data Synchronization
User Interface – Publisher Main Window Remote Data Synchronization
User Interface – Publisher (Statuses) Remote Data Synchronization
User Interface – Publisher (Settings) Remote Data Synchronization
User Interface – Publisher (Tag Mapping) Remote Data Synchronization
User Interface – Publisher (Schedule) Remote Data Synchronization
User Interface – Publisher (Tag Export) Remote Data Synchronization
User Interface – Publisher (History Catch-Up) Remote Data Synchronization
User Interface – Publisher (Logging) Remote Data Synchronization
User Interface – Consumer (Statuses) Remote Data Synchronization
User Interface – Consumer (Settings) Remote Data Synchronization
User Interface – Consumer (Tag Import) Remote Data Synchronization
User Interface – Consumer (Logging) Remote Data Synchronization
quality innovation foresight In Summary, Exaquantum/RDS Delivers… • Secure, efficient transfer of historical process data between Exaquantum Systems connected by a potentially volatile network link • Easy to install, configure and manage • Low cost of ownership Remote Data Synchronization
Thank you very much for your attention Remote Data Synchronization