alarm_analysis:resilient_data_transfer
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
alarm_analysis:resilient_data_transfer [2018/02/21 10:24] – su | alarm_analysis:resilient_data_transfer [2022/02/28 14:02] – su | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Overview ===== | ===== Overview ===== | ||
- | Intelligent Plant produces highly configurable tools for capturing | + | Before reading this guide, you should be familiar with [[alarm_analysis: |
- | We provide solutions that are deployed in high-security/ | + | In these scenarios, it is necessary to configure Data Core installations to act as a data relay. Moreover, if the connectivity between relays is unreliable, further configuration is required to guarantee resilient data transfer. |
- | This document describes best practice for a particular use-case: | + | This guide focuses on such a scenario |
- | //How to collect Alarm & Event data from a Process | + | Data is gathered |
- | // | + | |
- | ===== Terminology ===== | + | {{ : |
- | | Alarm Analysis | Intelligent Plant application that processes Alarm & Event data to produce interactive EEMUA (Engineering Equipment and Materials Users Association) grade reports and analysis. | | + | A two box installation is required, with the following |
- | | Data Core Node | Intelligent Plant' | + | |
- | | Industrial App Store | Cloud portal for industrial apps (including online editions of Intelligent Plant applications). | | + | |
- | | App Store Connect | An instance of Data Core Node pre-configured for secure connections with the Industrial App Store. | | + | |
- | | PCN | Process Control Network. | | + | |
- | | PIN | Process Information Network. | | + | |
- | | BN | Business Network. Also referred to as the Enterprise Network. | | + | |
- | | TCP | Transmission Control Protocol. A network communication protocol. | | + | |
+ | {{ : | ||
- | ===== Network Topology ===== | + | * Data Core listens for events (TCP Printer Stream). Arriving events are parsed and sent... |
+ | - On an immediate data relay to App Store Connect (Fast TCP Out) | ||
+ | - To a local data repository (Big Data Sink) | ||
- | {{ : | + | * A second process on the Data Core Node polls the local data repository for stored events (Big Data Source) and sends to... |
+ | - a further data relay that awaits an Ack from the App Store Connect (TCP Out). If Ack is not received, data is resubitted. | ||
- | | + | |
- | - This physical architecture guarantees one-way data-flow. \\ \\ | + | |
- | - The Data Core node installation on the PIN includes: | + | |
- | - TCP Printer Port listener (listening for input from the Serial to Ethernet Converter) | + | |
- | - Alarm & Event Collector (collecting A&E data from the PCN) | + | |
- | - a TCP Out Channel for data transfer \\ \\ | + | |
- | - The Data Core TCP Out Channel (on the PIN) initiates an authenticated TCP connection with App Store Connect (on the BN). Data transmitted on the TCP channel is signed | + | |
- | - App Store Connect acts as local data processor and supports connections to the Industrial App Store. \\ \\ App Store Connect incudes: | + | |
- | - TCP Listener | + | |
- | - Alarm & Event Collector (collecting A&E data from the Alarm Analysis server) | + | |
- | - Alarm Analysis Processing (converting A&E data to Alarm Analysis records) \\ \\ Alarm Analysis data remains on the Business Network. \\ \\ | + | |
- | - App Store Connect initiates a connection to the Industrial App Store using Microsoft' | + | |
- | - The Industrial App Store: a cloud portal of industrial applications that can connect to business data sources through App Store Connect. \\ \\ | + | |
- | - Users inside and outside the Business Network (e.g. office and home workers) access Alarm Analysis via the Internet. They log-in to the Industrial App Store and select the Alarm Analysis app. \\ NB. App Store users must be granted access to the Alarm Analysis data source (configured on the Business Network App Store Connection). \\ For instructions on sharing data, refer to the App Store Wiki: Share Data with other App Store Users. \\ \\ | + | |
- | ===== Deployment | + | While connectivity between the PIN and BN is good, all events will reach the destination twice. The fast stream means data arrives quickly, the second stream guarantees resilience. App Store Connect consolidates the two streams |
- | The network topology above assumes data crosses into the PIN via a serial printer feed. | ||
- | In order to collect data on the printer stream and transfer to the BN we need to undertake the following: | ||
- | - Install | + | ====== Step by Step Install |
- | - Install App Store Connect on the PIN | + | |
- | The configuration of these //Nodes// is as follows: | + | **1. Install Data Core Node on PIN** |
- | {{ :data_core:resilienttransfer_02.png |}} | + | For detailed instructions on how to deploy a Data Core node, see: [[data_core:stand-alone_installation]]. |
+ | **2. Data Core Node Configuration** | ||
- | ==== 1. PIN: Data Core Node ==== | + | Configure the following |
- | + | ||
- | For detailed instructions on how to deploy a Data Core node, see: [[data_core: | + | |
For detailed instructions on how to create an Event Source to Sink subscription, | For detailed instructions on how to create an Event Source to Sink subscription, | ||
- | |||
- | Configure the following Data Core components (assume default settings unless otherwise stated): | ||
^ //TCP Printer Stream// ^^ | ^ //TCP Printer Stream// ^^ | ||
Line 112: | Line 89: | ||
^ // | ^ // | ||
- | + | **3. Install | |
- | ==== 2. BN: App Store Connect | + | |
For detailed instructions on how to deploy App Store Connect, see: [[data_core: | For detailed instructions on how to deploy App Store Connect, see: [[data_core: | ||
- | Configure the following Data Core components (assume default settings unless otherwise stated): | + | |
+ | **4. App Store Connect Configuration** | ||
+ | |||
+ | Configure the following Data Core components (assume default settings unless otherwise stated). | ||
+ | |||
+ | For detailed instructions on how to create an Event Source to Sink subscription, | ||
^ //TCP In// ^^ | ^ //TCP In// ^^ | ||
Line 134: | Line 115: | ||
- | ==== 3. Firewall | + | **5. Firewall |
- | Intelligent Plant software is firewall friendly and designed | + | Firewalls will need to allow passage for the following protocols on ports: |
^ Firewall ^ Requirements ^ | ^ Firewall ^ Requirements ^ | ||
Line 144: | Line 125: | ||
| PCN:PIN Network Firewall | No inbound access required. | | | PCN:PIN Network Firewall | No inbound access required. | | ||
- | ==== 4. Alarm Analysis Processing | + | ==== 5. Testing ==== |
+ | |||
+ | Assuming that the TCP Printer Stream configured above is listening to an active | ||
+ | |||
+ | A quick test is to execute a URL search query. | ||
+ | |||
+ | 1. Log on to servers hosting Data Core Node | ||
+ | |||
+ | Open web browser and enter | ||
+ | < | ||
+ | |||
+ | A " | ||
+ | |||
+ | < | ||
+ | health status index pri rep docs.count docs.deleted store.size pri.store.size | ||
+ | green open | ||
+ | </ | ||
+ | |||
+ | A " | ||
+ | |||
+ | 2. Log on to servers hosting App Store Connect | ||
+ | |||
+ | Open web browser and enter | ||
+ | < | ||
+ | |||
+ | You should expect to see something like: | ||
+ | |||
+ | < | ||
+ | health status index pri rep docs.count docs.deleted store.size pri.store.size | ||
+ | green open | ||
+ | </ | ||
+ | |||
+ | A " | ||
+ | |||
+ | A " | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== 6. Next Steps ==== | ||
So far, we've moved Alarm & Event data across a network. We are now ready to configure Alarm Analysis processing. | So far, we've moved Alarm & Event data across a network. We are now ready to configure Alarm Analysis processing. |
alarm_analysis/resilient_data_transfer.txt · Last modified: 2023/12/29 13:41 by su