Anomaly review

The Operations Analyst opens a validated stream and compares its reading value with the effective lower and upper bounds. The quality flag and anomaly score help explain the recorded outcome. The anomaly workflow persists a run and numbered steps, then reads the stream back before calling the run successful.

• Value. The Operations Analyst compares the stream reading with its lower and upper bounds.
• Effect. The run and numbered steps show what changed and whether read-back confirmed it.
• Decision. The Independent Reviewer records a decision against the reviewed revision when required.

A returned decision gives the Stream Owner a reason to inspect or correct the stream. The reviewer can see the source revision and evidence reference. The owner can then create a successor revision, preserving the original run and judgement for later comparison.

Agree who sets bounds and how an uncertain or bad quality flag is handled. Define when a review decision is required and who may make it. A decision must identify the exact stream revision so a later correction cannot silently change the subject of an earlier approval.

Use a normal reading and one beyond the upper bound. The Operations Analyst checks the stream value, quality flag and anomaly score, then compares the saved fields with the run result. The Independent Reviewer uses the exact revision and evidence reference when a decision is needed.

Suppose a reading lies above the upper bound. The analyst checks the parent stream, observation date and collection basis, reviews the bound in force, and records the outcome. The read-back confirms the stream fields actually changed. The Independent Reviewer checks supporting evidence and records an approved, returned or rejected decision for that revision when approval is required.

If read-back cannot confirm a changed stream, the Operations Analyst checks the run steps before trying again. The Independent Reviewer should see the actual stream fields and the revision under review; a successful write attempt alone is not the final outcome.

Before the decision, compare the recorded stream status with the run status. If they disagree, the analyst investigates the step trail and the current stream fields. The reviewer should see the corrected explanation before deciding on that revision. A visible anomaly score alone does not settle the source decision.

• Streams ready for anomaly review — Validated streams with observed reading values and bounds.
• Pending review decisions — Source revisions awaiting a reviewer decision.

See the related process for the handoff and the data model for the connected records.