OSIsoft PI

PISMT Installation

1. Download the PISMT (PISMT_2018_SP2_.exe or later). Follow the instructions in the OSIsoft support portal (A login to OSIsoft support is required).

2. Double-click the PISMT_2018_SP2_.exe file to start the installation and follow the installation wizard.

   1. The wizard will show you the path for files extraction,

      

   2. and the supporting software that is already installed and will be installed in your system.

      

   3. Then, it will ask for the name of the default server. Enter the IP or FQDN of the default Data server. If you need to connect to more than one PI server, you can add connections later (see Configuring additional PI servers)

      

   4. There is an option to change the Installation Directories if needed.

      

   5. A Service Status confirmation dialog pops up:

      

   6. Finally, a confirmation that the installation is complete should appear.

      

Configuring the default server

1. Open the PISDKUtility software (In Windows desktop: Start > PI System > PISDKUtility)

2. Navigate to PI SDK > Connections on the left panel.

3. You should see at least one connection in the central panel for the default server set up during installation. By selecting this connection (but NOT ticking the checkbox) you can adjust the connectivity properties in the right panel (e.g. Network Node, Port Number, or Default User Name)

4. Tick the checkbox of the connection to test connectivity to the PI server. If the connection is successful you should see a message at the bottom of the window

   

Configuring additional PI servers

If Seeq needs to connect to other servers (besides the default PI server), then you will have to add those connections in the PI SDK Utility.

1. In the same PI SDK Utility, go to the Connections tab in the main menu and click on Add Server…

   

2. Enter the IP or FQDN for the PI server you want to connect to. Uncheck the Confirm checkbox and hit OK.

   

3. Tick the checkbox of the connection to test connectivity to the PI server. If the connection is successful you should see a message at the bottom of the window.

4. If you have more PI servers to add just repeat steps 1-3.

OSIsoft PI Trust

PI Trusts are a convenient and Seeq-recommended way to authenticate services that connect to PI. Trusts use various computer network and process name properties to identify "the trust" and assign a PI Identity to the connection. Below is a sample trust, as configured with PI System Management Tools (we removed part of the IP Address for privacy). There is no additional configuration required on the Seeq Server for PI Trusts.

Windows Integrated Security

To authenticate to a PI Server using Windows Integrated Security, identify the domain account that has appropriate access then follow this article to run the Seeq Remote Agent under that account.

PI Collective Member Priority

If you are utilizing a PI Collective with multiple PI Servers as members, it is important to set the collective member priority appropriately in the PI SDK Utility that is installed on the same machine as the Seeq Remote Agent.

1. Bring up PI SDK Utility on that machine and click File > Connections,

2. Click on the collective in the list and go to the Connection menu and then Member Setup…

3. You'll see the list of servers in the collective and you can set the Priority field. 1 is the highest priority, 2 is the next highest, and so on. Use -1 if you never want this machine to connect to a particular server.

OSIsoft PI Configuration Options

Additional Configuration > Configurable behavior for multivalued samples

Seeq’s behavior when it encounters a Multivalued Sample in PI can be configured in the “Additional configuration” section of the Configuration modal. To change this, the Property Name and Value must be added as a new field at the top level of the Additional configuration’s JSON. Please note that this should only be configured on the advice of Seeq Support.

Additional Configuration > Indexing additional PI Point attributes

To index additional PI Point attributes for display in the Seeq Workbench "Item Properties" panel, you can specify which attributes to index in the AdditionalProperties field of the Additional configuration.

PIPointAttributeDefinition

Putting it all together, the AdditionalProperties field should look similar to this:

"AdditionalProperties": [
    {
      "SeeqPropertyName": "Zero",
      "PIAttributeName": "Zero"
    },
    {
      "SeeqPropertyName": "Span",
      "PIAttributeName": "Span"
    }
]

After indexing has finished, you will see these properties in the "Item Properties" panel after clicking on a signal's information.

SecuritySynchronization Configuration

Seeq supports replicating tag security into Seeq’s integrated security model. Detailed information for these fields can be found in here

Export Configuration (see Exporting Signals and Conditions to a Historian )

The Seeq OSIsoft PI connector can export signals or conditions from Seeq and write its values to the OSIsoft PI Data Archive. Detailed information for configuring the following fields can be found in Exporting Signals and Conditions to a Historian

Only one PI server appears in the Seeq Datasources tab

Make sure you follow the steps in the Configuration section above. Most likely, the connection entries in the OSIsoft PI Connector.json have not been enabled.

All users are seeing all the tags even if PIWorld is disabled

This can happen if PIWorldMapping is enabled (is set to Auth/Seeq/Everyone) and PIWorld is disabled in PI. Even if PIWorld is disabled the security string still contains PIWorld. If PIWorld is mapped to Everyone in Seeq then Everyone will be able to see all the tags.

String-valued samples appear incorrectly in Seeq

Because PI stores strings as raw bits without an attached encoding, in rare cases a PI interface may write values to PI that are not parsed correctly by the AF Client of the machine hosting the Seeq Remote Agent. For example, you may see the string ƒnƒ“ƒo�[ƒK�[ when you expect to see ハンバーガー. This is because the string was written to PI in the Shift JIS encoding, but the remote agent host has its system locale set to English (United States) or similar, so that the bits of the string are decoded with Windows-1252 or similar instead of the proper Shift JIS. To correct this, you must change the system locale to the appropriate locale to interpret the bits of the PI Point value correctly. The setting is found in the Region window of the Settings or Control Panel. You must switch to the Administrative tab and and choose “Change system locale…”, as shown here:

After selecting the correct locale, you must also uncheck the checkbox for “Beta: Use Unicode UTF-8 for worldwide language support”:

Finally, after making the change, you must reboot the remote agent host machine. Upon restarting, the strings will be correct for newly-queried data - if an item has cache enabled, you may need to clear cached values to cause Seeq to make requests to the PI server for previously-queried data instead of using the Seeq cache.