Difference between revisions of "MRO Objects (Client)"
(→Work Package) |
|||
| Line 5: | Line 5: | ||
==== Work Package==== | ==== Work Package==== | ||
| − | A [[MROCLS_MRO_WORKPACKAGE#Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage | + | A [[MROCLS_MRO_WORKPACKAGE#Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. MOre complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages. |
| + | |||
==== Task ==== | ==== Task ==== | ||
Revision as of 08:43, 23 June 2016
MRO is a set of UBIK® objects object which allow to represent and document maintenance, repair and operations work on the mobile client. Therefore, a set of specific objects can be used to provide the needed structure of MRO jobs:
Contents
Task Owner
A MROCLS MRO TASKOWNER is an object having a substructure of jobs to be done. It can have a tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress informations. With a task owner a user can get an overview of all the work to be done in the underlying job structure.
Work Package
A MROCLS MRO WORKPACKAGE is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. MOre complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages.
Task
A MROCLS MRO TASK is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects.
Measurement Task
A MROCLS MRO MEASUREMENT TASK Inherits from MROCLS MRO TASK. This task documents a measured value (e.g. read from a pressure gauge). Therefore, clicking the value on the shown task opens an editor to enter the desired number. Once this is done, the task is finished. ALternatively, the task can also be closed by the option "Not Applicable" to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken).
Progress Task
MROCLS MRO PROGRESS TASK Inherits from MROCLS MRO MEASUREMENT TASK. This task type reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option "Not Applicable".
Check Task
A MROCLS MRO CHECK TASK Inherits from MROCLS MRO TASK. This task type is finished, when the user reports with a positive or negataive answer or "Not Applicable" (e.g. reporting a yes/no answer for existing equipment).
Inspection Task
MROCLS MRO INSPECTION TASK Inherits from MROCLS MRO TASK. This task is finisher einter by reporting "Done" or reoprting "Not Applicable". This is intended for a simple To-Do task that is either done or not.
See also
- MROCLS MRO TASKOWNER (Classification)
- MROCLS MRO WORKPACKAGE (Classification)
- MROCLS MRO TASK (Classification)
- MROCLS MRO MEASUREMENT TASK (Classification)
- MROCLS MRO PROGRESS TASK (Classification)
- MROCLS MRO CHECK TASK (Classification)
- MROCLS MRO INSPECTION TASK (Classification)
