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.
- Machine Maintenance (CMMS)
- Features
- Condition monitoring
Condition monitoring
Record equipment measurements with their units, measurement time and action limit.
OverviewCondition Reading History×
Machine Maintenance (CMMS) · Condition monitoring
New
Condition Reading History
Condition readings
| Id | Asset | Recorded at | Metric | Value | Unit | |
|---|---|---|---|---|---|---|
| IDD-326 | ASS-73743 | 06 Oct | MTR-712 | 180 | UNT-782 | |
| IDD-788 | ASS-21558 | 03 Oct | MTR-584 | 590 | UNT-588 | |
| IDD-783 | ASS-56147 | 04 Oct | MTR-722 | 710 | UNT-949 | |
| IDD-912 | ASS-49373 | 14 Oct | MTR-621 | 890 | UNT-641 | |
| IDD-186 | ASS-95663 | 12 Oct | MTR-341 | 640 | UNT-275 |
6 of 6 records
IDD-326Condition readings · CR-55441
AssetASS-73743
Recorded at06 Oct
MetricMTR-712
Value180
UnitUNT-782
What you can do
Give a measurement enough context to act on
A condition reading is useful when the maintenance team can identify the machine, understand the metric and compare the measured value with the intended action limit. The Technician records those details with the measurement time. The capture workflow validates the selected asset and source identity, then flags an action-limit breach for review.
This gives the Maintenance Manager a concrete observation to discuss with the Maintenance Reviewer. A high temperature recorded during an afternoon inspection belongs to that measurement time, even if the Technician enters it after the shift. Keeping the unit and metric consistent helps the team compare observations without turning unlike measurements into a misleading trend.
How the work is organized
- Measurement context. Select the asset and enter the metric, value, unit and measurement time. Use a consistent name for the measurement point so another Technician can repeat the observation and the reviewer can interpret its meaning.
- Action limit. Record the limit used for the reading. The capture workflow flags a breach, giving the reviewer a reason to inspect the evidence. Agree the operating response to the flag before collecting readings for the pilot equipment.
- Attributed capture. The acting person resolves from the authenticated account. Corrections and review evidence must retain their connection to the original observation so the team can distinguish the measurement from a later explanation or follow-up decision.
What to agree during setup
Choose the metrics, units and measurement points for the pilot. For a bearing temperature, agree whether the reading is taken at the housing or another location and what operating condition makes it comparable. Use the metric text consistently and record the appropriate limit with the observation.
Agree how quickly the Maintenance Reviewer should inspect a breach and how the Maintenance Manager decides whether to create corrective work. An instrument feed can be connected separately once the source identity and measurement-time handling are agreed. Start with a manual reading that the team can repeat so the first review conversation has an understood basis.
Check the handoff on an actual case
A Technician measures a conveyor bearing at 82 degrees Celsius against an action limit of 75. They select the conveyor, identify the bearing-temperature metric and record the measurement time. The workflow saves the reading and flags the breached limit. The Maintenance Reviewer checks the unit, asset and evidence before the Maintenance Manager decides the maintenance response.
Repeat the capture with a normal measurement, then inspect the history for the same asset and metric. Check that the later entry has not replaced the earlier observation. Try an incorrectly identified unit during rehearsal and confirm that the team catches it before treating the number as comparable. If a corrective request follows, give the request enough description to explain the concern and link it to the same equipment.
What your team sees
- Condition Reading History — Measurements with their asset, recorded time, unit and action limit for the review conversation.
- Asset Register — Equipment identity and location used to confirm the measurement belongs to the intended machine.
Follow the work through
Use condition reading review to rehearse a breached limit, then follow request planning when maintenance is needed.
What it keeps track of
Data model- Condition readings
- Condition monitoring measurements with action limits.
- Assets
- Asset register of maintainable machines and equipment with location, warranty and status.
- People
- Maintenance staff and reviewers referenced by work orders, logs and permits.
- Users
- Users
Who uses it
Permissions- Technician
- , Maintenance Reviewer, Maintenance Manager.
- The Technician captures the observation, the Maintenance Reviewer examines the evidence, and the Maintenance Manager decides the maintenance follow-up.
Set up Machine Maintenance (CMMS) your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.