Work Orders · Intermediate

Review and Respond to a Maintenance Request

Learn to evaluate a pending maintenance request in ManWinWin Web, record a response and approve or reject it. When information is insufficient, ask for clarification through Messages before deciding.

Effectively managing incoming maintenance requests is crucial for operational efficiency and asset reliability. This process ensures that reported issues are properly understood, prioritized, and addressed, preventing unnecessary downtime and optimizing resource allocation.

Where it's available and step by step

Step by step in ManWinWin Web

1
In Requests, select the pending request to be reviewed and click <Open>.
2
Read the Title, Description and Urgency, and check the Destination to establish what is being reported and where maintenance is needed.
3
Review any Diagnosis and attached Documents to determine whether the information supports the reported need.
4
Assess the request’s validity, priority and resource needs; identify any missing details that prevent a decision.
5
Expand Messages and click <+>; write your assessment, instructions or a specific question about the missing information, then click Save.
6
If clarification is needed, leave the request pending rather than approving or rejecting it; read subsequent replies by clicking the message icon before completing the review.
7
Once there is enough information to decide, click <Approve> or <Reject> in the open request, according to your assessment.

Theory and technical background

Importance of a Structured Request Review Process

A structured review process for maintenance requests is vital for preventing work order backlogs and ensuring that critical issues receive timely attention. It aligns with ISO 55000 principles by fostering a systematic approach to asset management, transforming raw requests into actionable tasks. This process allows for initial screening, prioritizing based on criticality, and validating the need before committing resources. Without it, maintenance efforts can become reactive and inefficient, leading to increased costs and reduced asset lifespan.

Utilizing Communication for Clarity (ISO 14224)

Clear communication is paramount when a maintenance request lacks sufficient detail. Leveraging internal messaging functions, as suggested by ISO 14224's emphasis on data quality, helps clarify ambiguities and gather necessary information directly from the requestor. This proactive approach avoids misinterpretations, reduces the risk of incorrect repairs, and minimizes wasted time and resources on vague issues. It ensures that any subsequent work order is based on complete and accurate data, improving the effectiveness of maintenance activities.

Decision-Making: Approval, Rejection, and Prioritization

The decision to approve or reject a maintenance request is a critical step that impacts resource allocation and operational continuity. Approval typically leads to work order generation, while rejection prevents unnecessary work. Prioritization, often guided by asset criticality and potential impact on OEE (Overall Equipment Effectiveness), ensures that high-impact issues are addressed first. A well-informed decision, supported by clear communication and complete information, optimizes maintenance scheduling and contributes to overall asset health.

Best practices

Always verify the reported urgency against asset criticality and potential operational impact.
Use attached documents (e.g., photos, manuals) to confirm the reported problem's scope.
When in doubt, use the 'Messages' feature to get more details before making a decision.
Document the reason for rejection clearly to provide feedback and prevent future similar invalid requests.

Frequently asked questions

Why should I use the 'Messages' feature instead of just calling the requestor?

Using 'Messages' within ManWinWin creates a documented audit trail of all communications related to the request. This provides transparency, helps track clarifications, and can be useful for future reference or compliance purposes, ensuring no details are lost.

What factors should I consider when assessing the 'Urgency' of a request?

Consider the asset's criticality, potential safety risks, impact on production or services (e.g., OEE), regulatory compliance implications, and the potential for escalation of damage if not addressed promptly. Don't rely solely on the requestor's stated urgency.

Can I edit a maintenance request after it has been submitted?

Typically, the original request details remain as submitted for audit purposes. However, you can add diagnoses, comments, and clarifying information via messages. If fundamental changes are needed, you might reject it and ask for a resubmission with correct details, or approve it and modify the resulting work order.

Need help with this topic?

Back to Winston Help Center

Ask Winston or explore other lessons.

Winston Help Center