Maintenance & ReliabilityFree templatePDF, Excel, Word exportManufacturing

Predictive Maintenance Alert Work Request Template

A good condition monitoring finding is useless if the planner cannot act on it. This template structures the finding, evidence and urgency in a form that can be attached to or copied into a maintenance notification.

Fill in

Live preview
Download:

Predictive Maintenance Alert Work Request Template

Predictive Maintenance Work Request

Company: Acme Precision Ltd Asset: P-101 Cooling water pump Location: Utility room, Plant 2 Date of finding: 2026-10-20 Analyst: R. Singh

Detection

Technique: Vibration analysis Severity: Alert

Finding and evidence

Drive end bearing shows rising 1x and bearing defect frequency peaks. Overall velocity increased from 1.8 to 3.4 mm/s RMS in six weeks.

Readings

PointMeasurementBaselineCurrentAlert limitAlarm limit
DE horizontal
DE vertical
NDE horizontal

Recommended action

Inspect and regrease DE bearing, verify alignment, plan bearing replacement at next scheduled stop if trend continues.

Plan work by: 2026-11-10

Approvals

Analyst / Date
Maintenance planner / Date
Production supervisor / Date

Attach spectra, trend plots or thermal images to the request. Close the loop after the repair by recording what was found, so the finding can be validated and the alarm limits tuned.

Draft findings automatically

Optional: discuss generating work requests from monitoring data for human approval.

Optional. The tool and every export work without this. No spam.

How to use it

Fill in the asset, technique, severity and a short finding written for a planner, not another analyst. Add the readings against baseline and limits, state the recommended action and a date by which work should be planned. Export to PDF or Word, attach spectra or thermal images, and file it with the notification in your CMMS or ERP maintenance module.

What makes a finding actionable

State what changed, how fast, and what you expect to happen if nothing is done. Give a recommended action and a deadline rather than only a diagnosis. Keep severity definitions consistent across techniques so planners can prioritize across vibration, thermography and oil analysis in one list.

  • Watch: trend monitored, no work needed
  • Alert: plan inspection within weeks
  • Alarm: plan repair at next opportunity
  • Critical: stop or reduce load until inspected

Closing the loop

After the repair, record the as-found condition and the cause. This feedback is what separates a working predictive program from an expensive data collection exercise. It tells you which alarms were true, which were nuisances and how much warning time you actually had, which feeds back into limits and route frequency.

  • Compare predicted and actual fault
  • Record warning time in days
  • Update limits and route frequency

Frequently Asked Questions

Who should receive this work request?

The maintenance planner or scheduler, with a copy to the production supervisor who controls access to the machine. The planner needs evidence and a date, not a full analysis report.

How urgent is an alert versus an alarm?

Define it in your own program. A common pattern is that alert means plan an inspection within weeks and alarm means plan a repair at the next opportunity. Critical means act immediately.

What evidence should I attach?

Trend plots, a spectrum or waveform for vibration, a thermal image with reference temperature for infrared, or the lab report for oil analysis, plus the baseline for comparison.

Can I use this with SAP PM or other systems?

Yes. Copy the text into a maintenance notification long text and attach the exported file. The fields map naturally to notification fields in most CMMS and ERP systems.

Netray can draft these findings from monitoring data and create the notification in your ERP for a person to review and approve.