# Predictive Maintenance Alert Work Request Template

> Source: https://netray.co/tools/predictive-maintenance-alert-work-request-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A document template that turns a vibration, thermography or oil analysis finding into a plannable maintenance work request.

## Category

maintenance

## Industry

Manufacturing

## Audience

- Condition monitoring analyst
- Reliability engineer
- Maintenance planner

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Asset / equipment ID

**Key:** asset

**Type:** text

**Default:** P-101 Cooling water pump

#### Location

**Key:** location

**Type:** text

**Default:** Utility room, Plant 2

#### Date of finding

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Analyst

**Key:** analyst

**Type:** text

**Default:** R. Singh

#### Technique

**Key:** technique

**Type:** select

**Options:**

- Vibration analysis
- Infrared thermography
- Oil analysis
- Ultrasound
- Motor current analysis

**Default:** Vibration analysis

#### Severity

**Key:** severity

**Type:** select

**Options:**

- Watch
- Alert
- Alarm
- Critical

**Default:** Alert

#### Finding

**Key:** finding

**Type:** textarea

**Default:** 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.

#### Recommended action

**Key:** action

**Type:** textarea

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

#### Plan work by

**Key:** plan_by

**Type:** date

**Default:** 2026-11-10

**Blocks:**

#### Predictive Maintenance Work Request

**Body:** Company: {{company}}
Asset: {{asset}}
Location: {{location}}
Date of finding: {{date}}
Analyst: {{analyst}}

#### Detection

**Body:** Technique: {{technique}}
Severity: {{severity}}

#### Finding and evidence

**Body:** {{finding}}

#### Readings

**Table:**

**Columns:**

- Point
- Measurement
- Baseline
- Current
- Alert limit
- Alarm limit

**Rows:**

**0:** DE horizontal

**0:** DE vertical

**0:** NDE horizontal

#### Recommended action

**Body:** {{action}}

Plan work by: {{plan_by}}

#### Approvals

**Signatures:**

- Analyst
- Maintenance planner
- Production supervisor

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use it

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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.

**Bullets:**

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

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

**Faq:**

#### Who should receive this work request?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

predictive maintenance work request template, condition monitoring report template, vibration analysis report template, maintenance notification template, condition based maintenance work order format, thermography finding report form, reliability finding report, machine health alert form

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json