![Twinview Academy - Purple Background (3).png]](https://content.twinview.com/hs-fs/hubfs/Twinview%20Academy%20-%20Purple%20Background%20(3).png?height=50&name=Twinview%20Academy%20-%20Purple%20Background%20(3).png)
If issues are problems that need addressing, then the maintenance job is the solution/fix to the problem.
A Maintenance job can be raised via an issue raised directly in the Facilities Management area by an FM Operator or user with relevant permissions. This is common for planned preventive maintenance (PPM), where an issue might not exist.
A maintenance job contains very little information, and the details are in the Tasks that form it. A typical maintenance job can comprise many tasks, each assigned to an individual(s) (Known as a Resource in Twinview) along with the start date, end date, and any equipment that might be required for the task.
These tasks can be seen and managed on the Task tab of a maintenance job, as shown below. The proposed start date of the maintenance job is based on the start date of the earliest task, and the proposed end date is based on the last task's 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 be updated to resolved (Issues) and closed (Tickets).
Once a maintenance job has been created, it can be made recurring if necessary. For more information, see the Making a Maintenance Job Recurring article.
When considering the difference between Tickets, Issues, and Maintenance Jobs, a good analogy is that tickets are someone reporting a potential problem. Issues can be considered “the problem,” and Maintenance Jobs are the “solution to the problem.”