Understand Tasks in MESPAS TSM

Tasks can be used to manage unplanned maintenance and events (in contrast to planned maintenance activities).

•New tasks may be created both by the office as well as on vessels:
- Tasks created by the office will be assigned a task ID starting with a capital O.
- Tasks created on vessels will be assigned a task ID starting with a capital V.

•Tasks are synchronised between the office and vessels.

•Tasks can have states "Pending", "Postponed", "Finished", "Needs confirmation".

•New tasks may be created that need confirmation after completion. If this option is ticked the person carrying out the task can not finish it, but only set it to the status "needs confirmation". It is up to the initial editor of the task to confirm its completion and set it to status "finish".

•Tasks not finished can be documented by
- adding comments and/or by
- assigning documents and/or by
- adding parts that were used to complete the task on the vessel.*
- adding the time used to work on and complete the task
- adding a SIRE code (or a code according to any other coding system)

•Finished tasks can be reopened, archived tasks can be un-archived.

•Tasks can be set as "office use only", which means that they are not synchronised to the vessels.

•Tasks that are originally created on the vessel can be committed and its ownership can be transferred to the office.

•Tasks can be assigned to a specific person responsible for carrying out the task.

•Purchase requests on the vessel can be created from a task

•Pending tasks are shown as "Pending Tasks" in "Business Data at a glance".

•The system can be configured as such, that the information, required by the user when closing a task (solution, preventive measures and root cause), become mandatory.

•Tasks may be imported.
 

* Parts used for a task can be entered on the vessel but not in the office. Unlike the parts used for overhaul in planned maintenance, there is no definition of parts that are likely to be used when a task is created.