PI historian integration — field asset telemetry retrieval done right
Most utilities already run OSIsoft PI or AVEVA System Platform. Fieldiq retrieves field asset telemetry from PI historian archives, with configuration guidance for tag hierarchy, compression deadband, and PI AF asset context.
Historian integration details
Bringing distribution field-asset telemetry into the historian requires decisions about tag hierarchy, compression deadband, and how to structure asset context in PI AF. Fieldiq's onboarding documentation covers each of these decisions.
-
Tag hierarchy recommendations
Fieldiq recommends a feeder-zone → asset-id → measurement tag hierarchy that aligns with how distribution assets are organized in most utility GIS and asset management systems. Standard tag naming templates are provided for common IED and sensor types.
-
Compression deadband configuration
Vibration and temperature signals require appropriately tight compression settings to preserve the anomaly signatures Fieldiq's models detect. Fieldiq provides per-measurement-type deadband recommendations based on the signal characteristics of each asset class.
-
PI Asset Framework (AF) context
Fieldiq reads asset metadata from PI AF element attributes — transformer kVA rating, installation date, manufacturer — to initialize per-asset model calibration without manual data entry.
-
Historical backfill for model bootstrap
Fieldiq retrieves up to 90 days of historical tag data on first connection to bootstrap the model calibration baseline. This reduces the cold-start period before first anomaly detection from 30 days to as few as 7 days.
Connect your PI historian to Fieldiq
If your utility runs OSIsoft PI or AVEVA System Platform, Fieldiq can begin retrieving field asset telemetry with minimal configuration. Our onboarding team provides tag mapping templates and compression guidance specific to your historian version.