These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- IoT Data Analytics
- Features
- Review and evidence
Review and evidence
Record independent decisions and assigned follow-up after a source review.
OverviewPending review decisions×
IoT Data Analytics · Review and evidence
New
Pending review decisions
Action waits for the independent reviewer
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| SS-89460 | 830 | Pending | ER-179 | ||
| SS-44783 | 630 | Pending | ER-616 | ||
| SS-18433 | 410 | Pending | ER-745 | ||
| SS-68557 | 690 | Pending | ER-535 | ||
| SS-57441 | 840 | Pending | ER-833 |
6 of 6 records
ER-179Review decisions · RD-93552
PendingSourceSS-89460
Source revision830
What you can do
Decide and close follow-up
A review decision record names the source, revision, reviewer, decision, date, reason and evidence reference. Evidence documents attach supporting material to the same source and identify who verified it. Follow-up actions assign a title, due date and owner to work that remains after review.
How the work is organized
- Decision. The Independent Reviewer records the source revision, outcome and reason.
- Evidence. A verifier checks the linked document and records its verification state.
- Action. The Follow-up Owner takes due work to a resolution and completion date.
Keep decisions attached to the reviewed revision. If the owner supersedes that revision, retain the earlier decision and evidence rather than presenting them as a fresh approval of the successor. The action queue shows what still needs work.
What to agree during setup
Agree which source outcomes require independent review and what evidence the reviewer expects. The reviewer should be separate from the preparer in the operating procedure. Define how returned decisions reach the owner and how overdue work appears in the operational overview.
Rehearse an approved decision and a returned decision on different source revisions. The Independent Reviewer should be able to identify the evidence used for each. Give the Follow-up Owner an open action with a due date, then check that its resolution stays connected to the source.
Check the handoff on an actual case
Imagine a reviewer sees a high anomaly score but cannot verify the source attachment. They record a returned decision with a reason and reference to the missing evidence. The owner obtains the source document, and the verifier marks the document after checking it. A follow-up owner then records the corrective action, resolution and completion date.
Have the Stream Owner inspect the returned decision and its reason before correcting the source. The Independent Reviewer then checks the successor revision on its own terms; the earlier approval or rejection remains attached to the earlier revision.
When an action is assigned, the follow-up owner should be able to find the original source and the reason for the decision. Review the due date and the resolution together. A closed action is useful only when the next reader can see what was done.
What your team sees
- Pending review decisions — Decisions waiting for the named reviewer.
- Open follow-up actions — Open and in-progress work with due dates and assignees.
Follow the work through
See the related process for the handoff and the data model for the connected records.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Evidence documents
- Supporting source evidence documents and verification state.
- Follow up actions
- Assigned corrective and follow-up actions with due dates.
- Sensor streams
- Measured web properties with lifecycle status and observed outcome fields.
- People
- Analysts, owners and reviewers belonging to an organization.
Who uses it
Permissions- Independent Reviewer
- , Follow-up Owner, Stream Owner.
Set up IoT Data Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.