Health, Issues, and KPIs

Overview

PI Nexus+ uses a small set of health states across the application:

• Good: the object is currently healthy based on the latest scan data.
• Warning: the object has a non-critical but actionable condition, such as stale, uninitialized, unused, or warning-level datasource health.
• Error / Bad: the object has a critical condition, such as a broken datasource, missing PI Point, broken AF Analysis, or bad value condition.
• Not Evaluated: PI Nexus+ knows about the object, but the latest scan did not produce enough usable health data to evaluate it. Missing inventory, excluded PI Points, and over-capacity PI Points are shown this way instead of carrying forward stale warning or error health.
• No Health Sources: AF Elements can show this when no scanned child attributes or analyses contribute health.
• Suppressed: the issue is intentionally hidden from active health counts and issue rollups, but remains traceable.

Dashboard health percentages are calculated from active scanned inventory and rounded to one decimal place. Domain health cards use domain-specific evaluated denominators:

• PI Points: active scanned PI Points, with warning and not-evaluated states shown separately from the dashboard health denominator.
• AF Attributes: active AF Attributes that were evaluated.
• AF Analyses: active AF Analyses.
• PI Vision Displays: active PI Vision displays.
• Overall Health: the average of the available domain health percentages.

Issue severity totals count active current issues by Error, Warning, and Info. Suppressed issues are counted separately. Suppression changes active issue counts and health rollups after the application refreshes the latest dashboard and inventory state.