PI Nexus+ v1.6:
live interface monitoring, health scans and recalculation

PI Nexus+ v1.6 brings PI Interface scanning, live interface monitoring and frequent health checks together for ongoing PI System monitoring. Teams can track interface runtime, detect unhealthy tags sooner and receive configured alerts. Manual and scheduled analysis recalculation help address affected downstream results after source data is corrected.

Product: PI Nexus+ for AVEVA PI System Release: v1.6 Date: September 21, 2026

This release update covers changes since our v1.3 announcement: interface intelligence introduced in v1.4, managed health scans in v1.5, and the monitoring controls, inventory updates and recalculation capabilities delivered with v1.6. If you are upgrading, read What changes when you upgrade.

PI Interface scanning and live monitoring

PI Nexus+ brings interface inventory and ongoing runtime monitoring into the same workspace. Administrators can see which interfaces collect their data, which PI Points depend on them, and whether the interfaces are operating normally. This makes PI Nexus+ an ongoing monitoring tool as well as a health and dependency scanner.

Scan interfaces and trace their impact

The PI Interfaces workspace brings together interface identity, host, PointSources, scan classes, mapped PI Points, issues and configuration changes. Interface-to-tag relationships let you trace a data problem back to the interface feeding it and understand which downstream objects may be affected.

A dedicated PI Interfaces scan and individual Check health actions let you inspect interfaces without rebuilding the entire PI Point inventory. Configuration Health, mapped-tag Data Health and Runtime are shown separately, helping you distinguish configuration problems, unhealthy tag data and interface runtime evidence.

Live runtime monitoring and alerts

Enable optional Runtime Monitoring to follow interface operation through UniInt health points. PI Nexus+ supports automatic discovery and manual signal mapping, shows signal quality and age, exposes available performance counters, and keeps runtime status history. Freshness warnings make it clear when runtime evidence has stopped updating.

Optional PI Interface runtime alerts notify your team about confirmed degradation, escalation and recovery. Alerts respect suppressed runtime issues and avoid repeating the same open alert at the same severity. Together, current runtime evidence and email alerts help operators follow interface health between manual investigations. Monitoring depends on the available health signals and their refresh cadence.

Frequent health scans and earlier alerts

Operational health scans check current PI Point values and analysis runtime health separately from full inventory scans. This lets PI Nexus+ refresh health between the heavier scans that rebuild configuration and relationships, helping teams detect a tag that becomes stale, reports a bad value or stops changing sooner.

Combined with configured scan-result email notifications, these checks can alert your team when a health scan identifies problems, instead of waiting for someone to notice an affected dashboard. Detection and notification timing depend on the effective scan cadence, the configured issue thresholds and the email delivery rules; there is no single fixed response time for every installation.

Low, Medium and High scan intensity settings let administrators tune monitoring to their environment. PI Nexus+ derives per-target health and full-verification intervals from measured scan durations. You can review target coverage, explicitly adopt automation, pause it and set a heavy-work window.

Stale-value and bad-value checks are complemented by configurable frozen-value detection for numeric PI Points, introduced in v1.5.1. Health changes in directly referenced PI Points and AF Attributes propagate to PI Vision displays, helping teams see the downstream impact. Asset-context displays still require their own scan or targeted check. Unreadable or unscanned objects remain distinguishable from confirmed unhealthy objects.

Analysis recalculation

Manual analysis recalculation and recovery suggestions

AF Analyses > Analysis Recalculation lets operators prepare, review and submit historical recalculation requests for supported, checked-in AF Expression analyses with usable PI Point outputs. Start from affected PI Points, AF Attributes, PI Interfaces or issues, inspect downstream dependency paths, then select the analyses and time period. Choose Fill gaps or Replace existing results and review warnings before submission.

Recovery suggestions identify periods to review after monitored PI Points recover from qualifying bad or stale episodes. They retain source evidence and do not submit requests automatically. Shared history records per-analysis submission details and supports retries of eligible requests. Eligible resolved history has a configurable 90-day default retention period; active and unresolved work is retained.

Restore and verify source history first: PI Nexus+ does not restore source data, and Event Frame generation analyses are outside this workflow. Request sent confirms submission to the native service; check execution and completion in PI System Explorer. With replacement mode, Recalculate dependent analyses lets PI Analysis Service expand and order downstream work, potentially beyond the AF databases registered in PI Nexus+.

Scheduled recalculation

Save a selection of up to 100 analyses for Hourly, Daily or Weekly recalculation. PI time expressions define the calculation period, and the preview shows the next run and resolved period. This supports recurring recalculation after manual data entry or historical corrections.

Schedules use the Worker server's timezone. Relative periods are resolved against the scheduled trigger time, even if processing is delayed. Saving a plan authorizes future automatic runs, with current permissions and analysis eligibility checked on each occurrence. You can edit, pause, resume or delete plans. Run now also works while paused and leaves the next automatic run unchanged. After downtime, only the latest due occurrence is processed, rather than every missed interval.

Change-driven inventory updates

Supported AF, PI Data Archive and PI Vision sources can refresh changed objects between full scans. Feed status shows whether updates are current, with a full-scan fallback when a feed is unavailable or needs recovery. In object details, Update inventory reloads configuration and relationships, while Check health checks the current health of the object.

Notifications and administration

• Recalculation suggestions: optional grouped emails prompt operators to review new suggestions; they do not start recalculation.
• AF scan results: submissions spanning multiple AF databases produce one email with a per-database breakdown.
• Compression Tuning: recommendation loading and filtering are improved, with validation against live settings before tuning and expanded dashboard insights. Compression Tuning itself predates this release.

Fixes

• Fixed excessive SQL staging allocation growth during large AF inventory scans; persistence and batching reduce allocation pressure and repeated writes.
• Fixed PI Data Archive discovery touching unrelated AF connections; discovery avoids those unnecessary connections.
• Fixed PI Vision datasource parsing failures with unexpected database column types; those values are handled more defensively.
• Fixed health reads treating transport failures as bad values; the last confirmed health is retained and the read failure is reported separately.
• Fixed installer configuration for passwordless group Managed Service Accounts (gMSAs); those accounts can be configured without a password.

What changes when you upgrade

After updating, review the settings for the monitoring and recalculation features you want to use:

• Enable interface monitoring. For legacy interface discovery, install the 64-bit PI SDK on the PI Nexus+ server if it is not already present. Enable Interface Tracking and Runtime Monitoring separately for each PI Data Archive.
• Turn on health monitoring. Review the monitored targets and scan intensity, then adopt Scan Automation. It replaces the previous recurring-scan model; existing installations start with automation unadopted.
• Configure alerts. Check email recipients and delivery rules, and enable interface runtime alerts as needed. Recalculation suggestions and suggestion emails are separate settings.
• Review recalculation access. Enable write authorization for the AF databases you intend to use. Saving a recurring recalculation plan authorizes its future runs.

Documentation

Use the version-matched User Guide and Installation and Administration Guide included with PI Nexus+ for monitoring, notifications, recalculation and administration. The online documentation hub provides PI Nexus+ reference material.