Definition
A maintenance notification captures an observed condition or concern (from an operator, sensor, or inspection) that may require maintenance action. It precedes approval: someone with planning authority reviews it, assesses priority and scope, and decides whether it becomes a work request or work order, or is dismissed.
Key facts
- Raised by anyone who observes a possible issue (operator, technician, or automated alert) before any work is approved.
- Not yet an approved or scheduled task; it awaits evaluation by planning or supervision.
- Captures the observation and its context (asset, symptom, urgency) rather than a defined scope of work.
- May be closed without action if evaluation finds no maintenance need, or converted into a work request.
What information does Maintenance notification preserve?
A maintenance notification records an observed condition worth flagging (unusual noise, a warning light, a near-miss, a sensor threshold) along with the asset and reporter, so it enters the maintenance workflow for review rather than being lost or handled informally.
How do maintenance teams use Maintenance notification?
A work request is a step further: someone has determined the observed condition needs maintenance action and is formally asking for it, typically with more defined scope. A work order is further still, approved, planned, and assigned. A notification is the earliest, least-defined stage: an observation awaiting evaluation, not yet a request for specific work.
FAQ
Frequently asked questions
How is an observed maintenance need reported through a notification?
It is captured with the asset, the observed condition, and the reporter, then routed to planning or supervision for evaluation, before it is approved as a work request or scheduled as a work order.
Last reviewed: