1. Install OSIsoft PI SDK
a. Allow the installer to unzip its files.
b. Click OK to let the installer update or install applications as necessary.
c. Proceed with the installation wizard by clicking next.
d. Specify organization names and click next to proceed with the installation.
e. Click Browse if you want to alter where the PI SDK is being installed. Then, click next to
proceed with the installation.
f.
Choose the username for your default PI account. The adapter allows you to specify a
different username and server in the connection string, so this isn’t a big deal for this
use case.
g. Click start to allow the installer to update and add files as necessary.
h. Click finish to end the PI SDK installation.
NOTE: If you installed the x64 version of the PI SDK, you may want to also install the x86 version to
achieve buffering. Installing the buffering subsystem will increase performance, but it is not required.
2. Copy PIAdapters.dll to your OpenPDC installation folder (likely C:\Program Files\openPDC\)
3. Configure a historian in the OpenPDC Manager for PI output.
a. Go to Adapters -> Historians in the OpenPDC manager
b. Click clear to create a new historian and set up the necessary configuration
Most of the configuration fields are up to you (acronym, name, description, etc).
However, the type name must be set to PIAdapters.PIOutputAdapter, and the assembly
name should be set to PIAdapters.dll. Here is a sample connection string:
server=<PIserver>;username=<username>;password=<password>;runMetadataSync=Tr
ue;
Replace <PI server> with the name of your PI server as configured in the PI SDK utility.
For example, I have a MISO PI collective and my PI test machine in the PISDKUtility so I
would enter either MISO or CL-RMCCOY here.
For username and password, enter your PI user account information. Finally, set
runMetadataSync to true or false depending on if you want to manage your own PI
points. If you set this to true, OpenPDC will automatically create PI points for all points
coming into the adapter and start updating those points in PI. However, the tags will be
created using the OpenPDC point tag as the PI tag name. If that doesn’t work for you,
just set this field to false. The output adapter will still feed data to PI if it sees that
measurements coming into the adapter have a point tag or alternate tag that matches a
point tag name in PI. So if you want to manually manage your PI points, the idea is that
you set runMetadataSync=False, then you create your PI points on the PI server, then
you put the PI tag name into the alternate tag for the corresponding OpenPDC
measurement.
c. Set up measurements to feed into the PI output historian. There are two ways to feed
measurements into the historian: one is to set the historian on the device in OpenPDC.
To do this, go to Devices -> Browse, and click on the device for which you want to
archive data in PI. Then, set the device’s historian to your PI historian and save the
change.
If you want to send data to PI on a per point basis instead of for a whole device, you can
do that under Manage -> Measurements. Just click on the measurement you want to
send to PI, switch its historian to your PI historian and then click save. This is also where
you can update the alternate tag if you want to manually manage your PI points.