A vague maintenance request forces technicians to reconstruct what happened. Linking the reported symptom, the asset and the work order turns a report into an assignable task while preserving its original context.
Maintenance requests
- Select the affected machine or context.
- Describe symptom, location, and objectively observed conditions.
- Indicate priorities and reasons only according to company rules.
- Check the request and verify that it is visible in the correct list.
Work orders
- Open the orders function and start creation according to the business process.
- Fill in General Data and connect the request when required.
- Complete dates, priorities, resources and other applicable data.
- Review the order and verify that it is ready for planning and execution.
Putting this into practice
For a leak on a pump, describe where it appears and when it occurs. The diagnosis will come from the intervention: a good report must first of all make the observed fact recognisable.
Learn more about ManstilNet.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.