What this is
What is a sensor and IoT data review?
What is a sensor and IoT data review?
It is a periodic audit of a condition-monitoring programme, not of a single asset. It checks whether sensors are reporting, whether alarms are being actioned rather than muted, and whether the data is actually changing what maintenance does. It is built against ISO 55001 cl.9.1 and sits inside the Reliability and Predictive Maintenance programme.
How is this different from a condition monitoring route?
A route record (MNT-088) captures a technician physically walking a circuit and taking readings. This review looks at the fixed, continuously reporting sensor network and asks a governance question: is the alarm and data pipeline still doing its job, or has it quietly degraded into noise everyone ignores?
Why does a review of sensors need its own form at all?
Because sensor networks fail silently. A broken transmitter, a stuck threshold or a suppressed nuisance alarm produces no immediate incident, only a slow loss of coverage. Without a scheduled review, that loss is invisible until a failure the network was meant to catch goes undetected.
Scope
When is a sensor and iot data review required?
This review sits above the sensor readings themselves. It is the point where someone asks whether the whole alarm-to-action chain still works, not where anyone records an individual reading or fixes an individual fault.
Use this template when
- The review interval for the monitored asset group or site has been reached
- A trigger event has occurred — a spike in alarm volume, a known sensor outage, or a near-miss the network should have caught
- The monitoring programme is being set up and the baseline needs recording before alarms start accumulating history
- Someone downstream is querying why a failure was missed and the alarm-response chain needs to be checked
- A linked record needs this one to exist — condition monitoring routes and work orders both reference it
Do not use it for
- Motor Current Signature Analysis, which analyses motor current to find rotor bar, air gap and load faults without stopping the machine.
- Alignment and Balance Record, which records shaft alignment or rotor balancing work, with before and after readings.
- Lubrication Route Record, which records the lubrication round, with what was applied where, how much, and any condition observed.
- Condition Monitoring Route Plan, which defines the walked circuit and reading points a technician follows, not the fixed sensor network's own health.
- Anything outside KnowMaintain, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 55001 cl.9.1 requirements does this satisfy?
The template maps onto ISO 55001 cl.9.1, which requires an organisation to monitor, measure, analyse and evaluate the performance of its asset management activities. The sections below are where that obligation actually lands in the form.
| Clause | Requirement | Where it lands |
|---|---|---|
| cl.9.1(a) — determine what needs monitoring and measuring | The scope of the monitoring programme and the period under review must be defined before results are read. | Header |
| cl.9.1(b) — methods for monitoring, measurement, analysis | Sensor coverage, calibration status and data plausibility must be checked, not assumed, before the underlying alarm data is trusted. | Data quality |
| cl.9.1(c) — when monitoring and measuring shall be performed | Alarm generation and response must be reviewed against a defined interval, with any drift in response time surfaced explicitly. | Alarms |
| cl.9.1(d) — when results shall be analysed and evaluated | The review must state whether the data changed a maintenance decision in the period, not merely whether it was collected. | Value delivered |
| cl.9.1(e) — evaluate asset management performance | A monitored asset with a failure the network should have caught is a performance finding in its own right, separate from the alarm count. | Value delivered |
| cl.9.1 — retain documented information as evidence | The result, any action raised and the sign-off chain must be retained against the record, with a route back to the monitoring plan it covers. | Result |
What it does not cover
- Alarm Limits Reviewed, which is answered No while alarm volume has visibly changed since the last review, with no explanation of why the limits were left untouched.
- Any Alarm Muted Without Fix, which is answered Yes and left unlinked to an action record, so the muted alarm has no route back to being fixed.
- Sensors Offline Or Failed, which is left at a plausible-looking low number while Data Gaps In Period is marked Significant for the same period.
- Failures On Monitored Assets Missed, which shows a non-zero count with no corresponding entry against Alarm Limits Reviewed or Sensor Placement Still Valid to explain why.
- Data Used In Planning, which is answered Yes with no interventions recorded against Interventions Triggered By Data in the same period.
Global
Sensor and IoT Data Review requirements by country
ISO 55001 is voluntary and international, but the weight it carries varies by where the sensor network sits and who is asking.
ISO 55001:2014 cl.9.1, alongside ISO 55000 for terminology and ISO 55002 for implementation guidance
The certification standard sits at this level; a certifying body auditing an asset management system expects a monitoring review of exactly this shape, with evidence retained.
Treat this record as the audit trail an assessor will ask to see first when testing whether performance monitoring is real or paper-only.
BSI-published ISO 55001, with the Institute of Asset Management's competency and practice frameworks widely referenced alongside it
UK operators often layer IAM guidance on top of the bare standard, particularly around how monitoring data feeds decisions rather than just compliance.
Expect the Value Delivered fields to be scrutinised more heavily here than in a jurisdiction only checking for certification.
ISO 55001 as adopted via AS ISO 55001, heavily used across mining and utility asset registers
Regulators and insurers in asset-heavy sectors treat a working condition-monitoring review as evidence against negligence claims after a missed failure.
Failures On Monitored Assets Missed carries particular weight here — a record showing nothing flagged before a failure is weaker evidence than one showing the anomaly was caught.
How to complete it
How to complete a sensor and iot data review, step by step
Filling in the fields is mechanical. The judgement calls below are what decide whether the finished record actually tells anyone the truth about the network.
Nuisance Alarms Suppressed Correctly distinguishes cause fixed or limit adjusted with reason from muted. The reviewer has to be willing to mark an alarm muted even when a colleague suppressed it under pressure — recording it as fixed when it was not defeats the point of the field.
Data Gaps In Period only has three bands, and Some is a judgement call, not a fixed threshold. A reviewer has to decide, using knowledge of which sensors covered which failure modes, whether the gap that occurred could plausibly have hidden a real event.
Response Time Acceptable is easy to mark Yes from memory of a typical response rather than from the actual out-of-hours alarms in the period. The honest answer requires checking the slowest response in the period, not the average one.
Data Used In Planning invites a reflexive Yes. It should only be marked Yes when a specific intervention in Interventions Triggered By Data can be pointed to — otherwise the network is producing readings, not decisions, and the record should say so.
What auditors find
Most common sensor and iot data review findings
The patterns below recur across sensor and IoT reviews and each one undermines a different part of the chain from sensor to action.
| Finding | Clause | What fixes it |
|---|---|---|
| Sensors have gone offline and stayed offline across several review cycles without anyone raising it as a gap in coverage. | ISO 55001 cl.9.1(b) | Require Sensors Offline Or Failed to trigger an action record automatically past a defined count, rather than relying on the reviewer to notice a repeat pattern. |
| Alarm limits were set at commissioning and never revisited even as duty cycles and load profiles changed. | ISO 55001 cl.9.1(c) | Tie Alarm Limits Reviewed to a fixed maximum interval independent of alarm volume, so limits get revisited on a schedule rather than only when alarms become a nuisance. |
| A nuisance alarm was muted at the control system rather than fixed at its source, and stayed muted for months. | ISO 55001 cl.9.1(a) | Any Alarm Muted Without Fix answered Yes should force a CAPA reference before the record can be marked Complete. |
| A monitored asset failed in a mode the sensor network was specifically installed to catch, and the review recorded it as a routine number with no analysis. | ISO 55001 cl.9.1(d), (e) | Route any non-zero Failures On Monitored Assets Missed into a root cause review rather than letting it sit as an unexamined field on this record. |
| Sensor placement was validated at installation and never checked again despite equipment being moved. | ISO 55001 cl.9.1(b) | Pair Sensor Placement Still Valid with a physical walkdown on a longer cadence than the alarm review, since placement drift is slower. |
| The review scored high on alarms while Completeness Percent was low, masking that whole sections went unanswered. | ISO 55001 cl.9.1 | Read Score Percent only alongside Completeness Percent, and block Result Band Pass where completeness falls under an agreed floor. |
Case in point
Case in point: the alarm nobody wanted to see again
A vibration sensor on a critical pump began raising a low-level alarm several times a week. Rather than investigate, an operator adjusted the alarm limit upward, and the alarm stopped firing. Three review cycles later, the record showed Alarm Limits Reviewed as Yes and Any Alarm Muted Without Fix as No, because the limit change was never distinguished from a fix.
The pump failed at the bearing the original alarm was flagging. The post-failure review found the limit-adjustment history in the control system logs, which the maintenance record had never captured. The fix was procedural: Nuisance Alarms Suppressed Correctly now forces a choice between cause fixed and limit adjusted with reason, and an adjustment with no stated reason is treated the same as a mute.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
6 sections
- Reference
- MNT-089
- Archetype
- Review
- Record ID
- IOT-2026-000
- Scoring
- Alarms actioned
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 55001 cl.9.1
- Links
- Links Condition monitoring, Work orders
- Tags
- Predictive, Sensors
- Sections
- 6
- Fields
- 45
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 3
Header
10 fieldsReview ID*
Auto sequence. Format IOT-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Alarms Everybody Has Learned To Ignore
Continuous monitoring with no review process produces a wall of alerts that get muted. The review is what turns data into maintenance.
Period Reviewed*
Reviewed By*
Sensors In Service*
Data quality
6 fieldsSensors Reporting*
Sensors Offline Or Failed*
Data Gaps In Period*
- None3 pts
- Some1 pt
- Significant0 pts
Sensor Calibration Current*
- Yes3 pts
- Some overdue1 pt
- No0 pts
Readings Plausible*
- Yes3 pts
- Some suspect1 pt
- No0 pts
Sensor Placement Still Valid*
- Yes3 pts
- Some moved1 pt
- No0 pts
Alarms
9 fieldsAlarms Generated*
Alarms Actioned*
Alarms Acknowledged And Ignored*
Repeat Alarms From One Source*
Alarm Limits Reviewed*
- Yes3 pts
- No0 pts
Nuisance Alarms Suppressed Correctly*
Suppressing a nuisance alarm by fixing its cause is good. Muting it is how real alarms get missed.
- Cause fixed3 pts
- Limit adjusted with reason2 pts
- Muted0 pts
- None present3 pts
Any Alarm Muted Without Fix*
- No3 pts
- Yes0 pts
Out Of Hours Alarm Route Defined*
- Yes3 pts
- No0 pts
Response Time Acceptable*
- Yes3 pts
- Marginal1 pt
- No0 pts
Value delivered
6 fieldsInterventions Triggered By Data*
Failures Avoided
Failures On Monitored Assets Missed*
Data Used In Planning*
- Yes3 pts
- Sometimes1 pt
- No0 pts
Sensors Recommended For Removal
Additional Sensors Recommended
Related records
1 fieldRoute Plan ID
The monitoring route these sensors belong to.
Links to MNT-088 Route Plan ID
Result
13 fieldsItems Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Reliability*
Signature*
Engineering Manager*
Second Signature*
MNT-089 · record IDs look like IOT-2026-000 · Links Condition monitoring, Work orders
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures a point-in-time judgement. Keeping the alarm history current, routing muted alarms to an owner, and holding the evidence trail together across cycles is the part that actually slips.
Holds the sensor and IoT data review against the condition monitoring register, links muted alarms to their CAPA records, and keeps the review cycle from drifting off schedule.
Surfaces sensor coverage and alarm-response trends alongside other operational metrics, so a quietly degrading monitoring network shows up before it costs a missed failure.
Flags where a muted or unactioned alarm on a monitored asset carries a safety dimension, and keeps that escalation separate from routine reliability housekeeping.
Coordinates the crew across reliability and operations, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Sensor and IoT Data Review definitions and key terms
- Nuisance alarm
- An alarm that fires more often than it delivers useful information, typically because its threshold no longer matches normal operating variation. The correct response is to fix the underlying cause or adjust the limit with a documented reason, not to silence it.
- Alarm rationalisation
- The structured process of reviewing an alarm system's limits, priorities and routing against actual plant behaviour, so that alarms correspond to conditions that genuinely require a response.
- Sensor coverage
- The proportion of the intended monitoring points that are actually reporting valid data at a given time, as distinct from the number of sensors installed.
- Bad actor (monitoring context)
- A sensor, alarm point or asset that repeatedly produces unreliable or ignored signals, consuming review time without useful information until it is fixed or retired.
- Condition-based maintenance
- Maintenance triggered by measured condition data rather than a calendar interval, dependent on the monitoring network this review checks the health of.
FAQ
Frequently asked questions about sensor and iot data review
What is the sensor and IoT data review template based on?+
It is built against ISO 55001 cl.9.1, which requires organisations to monitor, measure, analyse and evaluate asset management performance. The template applies that requirement specifically to a continuous sensor and alarm network.
What sections does the sensor and IoT data review contain?+
There are six sections: Header, Data quality, Alarms, Value delivered, Related records and Result. Together they hold 45 fields, 37 of which are required.
How many sensor and IoT data review records should we have?+
This is a singleton — one live record per workspace, maintained on a review cycle rather than raised per incident. Individual events are captured instead in the linked condition monitoring and work order records.
How is a sensor and IoT data review scored?+
Scoring runs on alarms actioned, and high is good. But the score should always be read alongside Completeness Percent and Data Gaps In Period, since a high score on an incomplete or gap-riddled period is not evidence the network is healthy.
What is the single most important field on this form?+
Any Alarm Muted Without Fix. Everything else on the form can look fine while this field, answered honestly, reveals whether the alarm chain has quietly stopped functioning.
Can the sensor and IoT data review template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust thresholds against their own alarm history.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Reliability and Predictive Maintenance
Root Cause Analysis
Finds out why something happened rather than who was involved
Equipment Failure Report
Records that an asset has failed and stopped or degraded production
Failure Mode Record
Records how an asset failed, using standard failure mode codes rather than free text
Repair Record
Records what was actually done to fix the asset, including parts replaced and settings changed
Temporary Repair Record
Records a repair that is not permanent, with an expiry date and a plan for the proper fix
Repeat Failure Review
Reviews an asset that has failed the same way more than once
More in Predictive Maintenance
Motor Current Signature Analysis
Analyses motor current to find rotor bar, air gap and load faults without stopping the machine
Alignment and Balance Record
Records shaft alignment or rotor balancing work, with before and after readings
Lubrication Route Record
Records the lubrication round, with what was applied where, how much, and any condition observed
Condition Monitoring Route Plan
Sets which assets are monitored, by which technique, at what interval and against which alarm limits
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 55001:2014 — Asset management systems, cl.9.1
- ISO 55000:2014 — Asset management, overview and terminology
- ISO 55002:2018 — Asset management systems, guidelines for the application of ISO 55001
- ISO 14224:2016 — Collection and exchange of reliability and maintenance data for equipment
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.