Documentation PI Nexus+ Documentation

PI Nexus+ / User Guide

PI Interfaces

Open PI Interfaces to see where PI Point data originates and how tags are assigned to legacy PI Interfaces and scan classes.

Overview

Open PI Interfaces to see where PI Point data originates and how tags are assigned to legacy PI Interfaces and scan classes.

PI Interfaces workspace

The page is populated after a PI Point or Full Inventory scan when an administrator has:

  • Enabled Interface Tracking for the PI Data Archive.
  • Installed the optional 64-bit legacy PI SDK on the PI Nexus+ server.
  • Configured the target to use Windows authentication.

The KPI cards and filters answer four common operational questions:

  • Which interfaces have configuration errors or warnings?
  • Which interfaces currently feed unhealthy PI Points?
  • Which monitored interfaces are running, degraded, offline, or unreadable from PI?
  • Which PointSources and PI Data Archives belong to an interface?
  • How many tags are advised, polled, watchdog, event, or output tags in each scan class?

Click an interface to open its detail dialog:

  • Overview shows the Module Database path, host, service, interface ID, PointSources, failover metadata, inventory state, and last-seen time.
  • Connections lists every mapped PI Point with PointSource, decoded processing mode, scan class, Location1-5 values, and current PI Point health.
  • Scan Classes shows the configured period and offset plus advised, polled, and other tag counts.
  • Issues includes interface-level configuration findings and findings on mapped PI Points. Suppressed issues remain visible and labeled.
  • Runtime shows the latest UniInt health evidence, mapping source, signal quality and age, performance counters, and runtime status transitions. Admins can configure an exact core-health PI Point, clear a manual mapping, or rediscover standard markers.
  • Dependency Graph shows the interface and the highest-priority mapped tags. Use Connections for the complete list when the graph is limited.
  • Changes shows detected interface configuration changes between scans.

Read the three health columns independently:

  • Configuration Health reports Module Database and PI Point mapping consistency.
  • Data Health rolls up the health of mapped PI Points.
  • Runtime reports live interface evidence only after Runtime Monitoring is enabled. An idle interface is not unhealthy merely because throughput is zero.

Runtime evidence is grouped into Core Health, Interface, Scan Classes, and Process. Missing optional performance counters appear as unavailable; they do not make the interface unhealthy by themselves. Only Core Health signals can be mapped manually.

Other useful behavior:

  • Runtime email alerts are configured separately under Admin > Notifications. Suppressed runtime issues do not generate alerts.
  • When Change Tracking is enabled, the Changes tab records runtime-signal mapping changes without recording every health poll.
  • Overview explains the Location1-5 meanings for supported interface families. Unknown families retain their raw values and show Mapping only / Not Decoded rather than applying assumptions.

If the page is empty, ask an administrator to:

  1. Enable Interface Tracking under Admin > PI Data Archives > Actions.
  2. Run Test Module DB.
  3. Run a PI Point or Full Inventory scan.
  4. Enable Runtime Monitoring separately if live runtime health is required.