Documentation PI Nexus+ Documentation

PI Nexus+ / Reference

Health and KPI Calculation

This reference lists the health states, how an object's health follows its issues, how the dashboard percentages are calculated, and the rules for suppressing issues. The User Guide chapters Health, Issues and KPIs and Investigate an Issue link here.

Overview

This reference lists the health states, how an object's health follows its issues, how the dashboard percentages are calculated, and the rules for suppressing issues. The User Guide chapters Health, Issues and KPIs and Investigate an Issue link here.

Health states

State (as shown)Applies toMeaning
GoodAll objectsNo open, unsuppressed Error or Warning issue
WarningAll objectsThe newest open, unsuppressed issue of the worst severity is a Warning
BadPI PointsAn open, unsuppressed Error issue
ErrorAF Attributes, AF Analyses, PI Vision displaysAn open, unsuppressed Error issue
Not EvaluatedPI Points, AF Attributes, AF Analyses, PI Vision displaysNo current verdict: missing from the latest scan, excluded by a PI Point rule, above the licensed PI Point capacity, or (analyses) disabled, stopped or not ready
UnknownPI Points, AF AttributesThe value's quality could not be determined
No Health SourcesAF Elements onlyThe element has no attributes or analyses that carry health
No statusDependency graph nodes onlyThe node has no health, for example a calculation or an external source

Suppressed is not a health state. It marks an issue that is hidden from counts.

How health follows issues

RuleEffect
An open, unsuppressed Error issue existsThe object is Bad (PI Points) or Error
Otherwise, an open, unsuppressed Warning issue existsThe object is Warning
Only Info issues, or noneThe object is Good, unless it is Not Evaluated
An issue is suppressedIt no longer counts toward the object's health
An AF Attribute reads a PI PointIt shows the PI Point's health, unless the attribute itself is Error or Not Evaluated
An AF ElementRolls up the health of its attributes and analyses

Issue severities

SeverityChanges healthCounted on the dashboard
ErrorYesErrors
WarningYesWarnings
InfoNoInfo on the Issues page

Issue states

StateMeaning
ActiveOpen, with no suppression in force. An expired suppression makes the issue active again
SuppressedOpen, with a suppression in force. Left out of counts and percentages
ResolvedThe latest check no longer found the problem. Resolved issues leave the Issues page

An issue is identified by the object's stable identity (PointID, AF GUID) and the issue type, not by name or path. A renamed or moved object keeps its open issues.

Health percentages

Only active (not missing) objects are counted. Each percentage is Good divided by the denominator below.

TypeDenominator
PI PointsAll PI Points minus Warning and Not Evaluated. PI Points with Unknown quality count as not good
AF AttributesAll AF Attributes minus Not Evaluated and Unknown
AF AnalysesAll AF Analyses minus Not Evaluated (disabled, stopped and not-ready analyses are Not Evaluated)
PI VisionAll displays minus Not Evaluated and unused displays. An unused display with a datasource error stays in
Overall HealthThe average of the type percentages that have a value. PI Vision is left out when no PI Vision instance exists

The same rule applies to the estate, a site, a server, an AF database and a PointSource.

Rounding ruleResult
Denominator is 0No value (—)
All objects good100 %
OtherwiseRounded to one decimal; a value that would round up to 100 is shown as 99.9 %

Health bands

BandPercentage
Healthy90 % and above
Degraded80 % to below 90 %
AttentionBelow 80 %
No dataNo value. Emails show Unknown

The bands colour the site tiles, the Health by type rows, the server cards and their rows, the Action View Health card, and the scan notification emails.

Suppression rules

ItemRule
RoleOperator
ScopeOne object, issue code and issue value. Most issues have no value; some do, for example one calculation on a PI Vision display
ReasonRequired
ExpiresOptional. When it passes, the issue counts again
RestoreEnds the suppression. The issue counts again if the problem is still there; resolved issues keep the suppression as history
Suppress matching / Restore matchingApplies to every issue matching the current filters and site. Suppress matching never changes issues that are already suppressed
Batch sizeUp to 1,000 matches run at once; 1,001 to 25,000 are queued (Queue Suppress, Queue Restore) and finish in the background; above 25,000 the action is refused until the filters are narrowed
Evaluation editionNot available

Acknowledging exists only for host issues; see Host Monitoring Reference.