Services form a core element of M3 Maintenance. These are used to generate regular, planned and preventative schedules, along with forming the heart of non-recurring work such as requests and overhauls.

All work generated in M3 Maintenance is based on service definitions defined in 'Service. Open' (MOS300).

Services can be unique if they are linked to equipment, items, or positions. Or, the equipment number can be left blank, allowing the service to be used anywhere. Linking reoccurring jobs to equipment forms a library of pre-defined. This enables jobs to be completed quickly when they occur.

Services can contain extensive details of the maintenance task including any number of operations (tasks), spare parts, purchasing needs, tools, permits, skills, and detailed textual instructions.


Services are used to define all types of work.

For predictive inspections where measurements are taken, you can define the full details of the inspection including the minimum, maximum and trend readings that are acceptable. A trend reading is the maximum permissible difference between subsequent readings. A greater rate of change may indicate increased failure potential and shorter life span. The system will also produce alarms and even automatic work order requests if the alarm conditions are exceeded.

For preventive work such as lubrication and visual checks, the system allows work order requests generated from services to be collated under the same work order. This reduces the amount of paper produced.

Major work, such as for shutdowns, can be defined. This type of work may well be combined with permits, spare parts, skills, and the like. This type of work is normally triggered manually when required (unless the overhaul frequency can be defined).

If the diagnostic capabilities are being used within the system, services can be linked to them.

Services can generate work order requests automatically when an inspection is due or when an alarm condition is triggered. The due date can be based on calendar scheduling, meter based scheduling (such as running hours) and fixed date scheduling (specific dates or days of the week). Services can also be triggered on absolute values, that is when the equipment reaches a particular condition. They can also be triggered manually for Ad Hoc work. Services are converted to work order requests either when the previous inspection is complete or by using a special automatic batch component, (MOS999).

Related topics