1. Description 

Objective 

The objective of this article is to explain how to configure the PI Event Frame connector in the SEEQ administration page to limit root/child condition to a specific hierarchy of event frames, in order to retrieve the conditions from a large number of events.

Context 

In this article, we are going to proceed with the example use case of the site Pasadena for Novecare. 

Here, the hierarchy refers to the hierarchy of child events for the event type “Procedure”, in the section Event Frames of PI System Explorer, as listed in the picture below. Normally, the complete hierarchy contains 4 levels:  "UnitProcedure" >  "Operation" > "Phase" > "PhaseState". 

Displaying image.png

In this case, the hierarchy requested by the user is : "UnitProcedure" > "Operation" > "Phase", without the last one  "PhaseState". 

So the main purpose is to exclude the "PhaseState" conditions for the site Pasadena, through the configuration of Event Frame Connector.

2. Knowledge Reference : Indexing Exclusions

In order to realize this configuration, we can use the rule of Indexing Exclusions to exclude items from indexing (please see the picture below). 

You can go to the link below to check more information :

Seeq Connector Property Transforms 

https://support.seeq.com/kb/R58/cloud/connector-property-transforms#id-%28R58%29ConnectorPropertyTransforms-IndexingExclusions

In our case, “PhaseState” conditions conclude 5 items to exclude : Running, Held, Restarting, Holding, Complete.

Displaying image.png

3. EF Connector Configuration

Prerequisites

We need to collect  first the following informations regarding the AF database & EF template:

  • AF server.
  • AF database.
  • EF template.

Configuration

Go to the directory  C:\ProgramData\Seeq\data\configuration\link 

  • Make a copy of the configuration file  (for back-up reason)
  • Edit the configuration of the OSIsoft AF Event Frames Connector

Go to the section “Name”: “ACEW1PSTEKPAF02 Event Frames”, then set “Enabled” to true. 

Check connector in SEEQ \ ADMINISTRATION TAB:



Note: Starting with Seeq Server version R54, connector configuration JSON files do not need to be updated manually on the machine running the agent and can instead be managed through the administration page. 

In the datasources tab, select the datasource of interest and click “Manage” for the associated connection card:

Go to the section “Name”: “PAS_NOVECARE”, then set “Enabled” to true:




Blocks to add

Now we can add blocks using the Indexing Exclusions transform (see 2.Knowledge Reference).  

For the site Pasadena Novecare, as “PhaseState” contains 5 conditions : Running, Held, Restarting, Holding, Complete. We add 1 block for each condition.

Here are the specific blocks to add as transforms :

  • Held

  • Running

  • Complete

  • Holding 

  • Restarting 

How to get Data ID 

As you can see, in each block we need to specify the Value of Data ID :



In order to get this Data ID, we need to go to Seeq, open your workbook in the Seeq Workbench Analysis environment, find the exact condition you are looking for, and then click on the “ i ” icon in front of it.  

The Value of Data ID will appear on the left panel.

 

  • No labels