Introduction to Maintenance Jobs

What are they, and what are their purpose.

If Issues are problems or issues that need addressing, then the maintenance job is the solution/fix to the problem.

A Maintenance job can be raised via a an issue raised directly in the Facilities Management area by an FM Operative or user with relevant permissions. The later been common for planned preventive maintenance (PPM) where an issue might not exist.

A maintenance job contains very little information in itself, and the detail is in the Tasks that form the maintenance jobs. A typical maintenance job will can be made up of many tasks, each task assigned to an individual(s) (Known as a Resource in Twinview) along with a start data, end date and any equipment that might be required for the task. A Maintenance job can contain many tasks.

These tasks can be seen and managed on the Task tab of a maintenance job as shown below. The maintenance job proposed start date is based on the start date of the earliest task, and the proposed end date is based on the last tasks end date.

A maintenance job is automatically 'completed' when all tasks are completed. When this happens any Tickets or Issues that the maintenance job was associated with will automatically update to Resolved (Issues) and Closed (Tickets).

Once a maintenance job has been created it can be made recurring if required, see the Making a Maintenance Job Recurring article for more information.

When thinking about the difference between Tickets, Issues and maintenance jobs, a good analogy is; Issues can be thought of as “the problem” , maintenance jobs are the “solution to the problem”. Tickets are someone reporting a potential problem, but at this stage the exact problem may be unknown.