The integration concept can be extended to share measure and KPI data with other systems to complement current datasets and visualisation capabilities. Important KPIs can now be made available for users in traditional Historian solutions to make decisions based on KPIs that cannot be calculated with data originating solely from the control system, for example, Planned vs. Actual Production.
This leverages Flow as a decision support system, making information available to anyone and everyone in the plant, from Operations to Management and to multiple systems.
The merging of real time visualization KPIs and historical KPIs has becomes ever more important to truly optimize plant efficiency and performance. This can be achieved by sharing historical KPIs with the Canary Historian. Axiom, Canary's Visualization platform, can now display real time data, historical trending as well as Historical KPIs and calc from Flow.
Potentially, utilizing Canary's view services, KPI information can complement current asset structures as defined in the views.
The Flow Canary Consumer act as a bridge between Flow data and Canary Historian by use of Canary's Sender service.
The Flow Consumer will connect to the local Canary Sender service using the "Local Only" Net.Pipe endpoint.
Configuring a Canary Historian Consumer
To create a connection to a Canary Historian, right-click on Data Consumers to add a new Consumer. Select “New”.
This will list the Canary Historian Consumer called “Canary Historian”. Select The “Canary Historian” consumer to open its editor:
To successfully push data to a Canary Historian, the following properties needs to be set.
|
Name to identify the consumer. |
|
Location of the server or address where your Canary Historian is installed (Server Name or IP Address). |
|
The Dataset as defined in Canary to use to push Flow data to. |
|
Time the Client session will be kept open before Canary closes the connection. |
Note: Best practise is to configure a "Heartbeat" measure to keep the connection open. The measure must update in an interval shorter than the Client Timeout configured. Normally a 5 minutely measure will be used with a Client Timeout set to 360 seconds.
After configuring the properties, test the connection by clicking the “Test” button. If successful, a pop-up will confirm your connection or display an error message describing the issue that needs to be rectified.
This will allow you to specify a specific Tag name to use, or, if left blank, it will use the Hierarchical name as the Tag name that will be created in Canary.
One can also decide to integrate values or Values and comments added in Flow. Comments will be added as annotations to a data point in Canary.
All that is left is to do is to deploy the integration on the measure to start pushing data to Canary.