Documentation PI Nexus+ Documentation

PI Nexus+ / Reference

Compression Tuning Reference

This reference lists the classifications, observation modes, limits, profiles and statuses of Compression Tuning. The User Guide chapter Compression Tuning links here.

Overview

This reference lists the classifications, observation modes, limits, profiles and statuses of Compression Tuning. The User Guide chapter Compression Tuning links here.

Result classifications

Classification (as shown)MeaningReview groupSuggested response
UndercompressedThe point stores more archive events than needed while already preserving the signalApply when the candidate passes every guardrail, otherwise InvestigateCompare the trends; apply the larger deviations
Overcompressed RiskThe current settings may hide real process movement. A high overall fidelity does not rule this outAs aboveCompare Snapshot and Archive; apply the more conservative recommendation
GoodThe current settings balance signal and volume; the tested alternative brings no material safe reductionNo actionSkip when reviewed
Hard To CompressThe signal is so noisy or busy that reducing events would remove detail. Shown as Limited compression savings when the safeguards pass only with a dense archiveInvestigateCheck sensor noise, vibration or instrumentation first
Limited dataSamples were analyzed, but the evidence is too thin to trust the calculated settingsInvestigateObserve longer, during representative operation
FlatlineThe signal shows little or no movementInvestigateCheck whether the process is stable or the point is inactive or frozen
Zero/span issueObserved values do not fit the point's zero and spanInvestigateCorrect zero and span before tuning
Insufficient DataFewer than 20 valid samplesInvestigateRun again with a longer observation
UnsupportedNon-numeric type or unsupported metadataNot listedDo not tune with Compression Tuning
ExcludedExcluded from future runsNot listedAllow tuning again on Point Exclusions

Only Undercompressed and Overcompressed Risk can be applied in bulk. Hard To Compress, Limited data, Flatline, Zero/span issue and Insufficient Data, and actionable results whose candidate failed a guardrail, can only be applied one point at a time from the comparison dialog with Apply tested candidate.

When several runs tuned the same point, the newest run with a valid result supplies the current recommendation; older unresolved results become Superseded.

Observation modes and limits

SettingAdaptive samples (Recommended)Fixed window
Point finishesWhen it has reached the sample target and the minimum durationAfter the window
Sample targetQuick 1,000, Recommended 2,000 (default), High confidence 5,000Not used
DurationMinimum 1 hour (default); maximum default 168 hours (7 days), up to 720 hours1 to 24 hours, default 1
At the maximumThe valid samples are analyzed when there are at least 20; otherwise Insufficient Data
Run limitValue
Points per runWarning above 10,000, blocked above 50,000
Estimated run timeFixed window: blocked above 72 hours. Adaptive: blocked above 720 hours
Valid samples per adaptive waveAt most 50,000,000 (active points × sample target)
Default target Data Fidelity97 %

Tuning profiles

ProfileLoadActive tags per batchParallel batchesActive tags per PI Data Archive
ConservativeLow5001500
Balanced (default)Medium1,00044,000
FastHigher2,500410,000

Points beyond the per-archive limit are observed in later waves.

Run statuses

StatusMeaning
Queued, Preparing, Observing, Restoring, AnalyzingIn progress (In Progress card)
ReadyAnalysis finished; results to review
ApplyingSettings being written
CompletedEvery result resolved
Failed, CanceledDid not complete
Restore failedOriginal exception settings could not be restored; retry or correct the point manually
InsufficientNo point is ready for review and at least one had too little data; Review shows N need more data instead of N ready

Point statuses in a run

TabStatuses
ReadyReady for review, Insufficient data
PendingQueued, Preparing, Observing, Restored, Analysis queued, Analyzing; adaptive points show sample progress
AppliedApplied, or resolved (superseded or excluded after processing)
SkippedSkipped for this run, excluded or unsupported
Failed / canceledFailed, Apply failed, Restore failed, Canceled

Safety

  • Before observation, the original exception and compression settings of every point are saved.
  • Only exception deviation is lowered during observation; compression settings are not touched.
  • Settings are restored before analysis, and also when a run is canceled or fails. A failed restore stays visible and is never cleaned up automatically.
  • Every applied change records the previous and new settings, user and time in the tuning audit and in Change History.

Auto Tune

ItemBehaviour
MembershipFollows a PI Point Rule, or a fixed selection made on the PI Points page or a point's dialog
CoverageEach point once per plan; enable retuning and a cooldown (default 90 days) to repeat
Batch sizeAt most 10,000 points
FailuresAn infrastructure failure retries the same batch up to 3 times (after 15 minutes, 1 hour and 4 hours); a point failure is retried on a later pass; a restore failure pauses the plan
CapacityOpen actionable recommendations plus points reserved by running batches. Warning from half the maximum; Held (no new batches) at the maximum, 100,000 by default (10,000 to 1,000,000); resumes below 80 % of it
ResultRecommendations only; applying stays manual