MRO is a set of UBIK® objects object which allow to represent and document maintenance, repair and operations work on the mobile client. The WinX client UI displays MRO configured objects lika any other root- or child-object enriched by some additional logic and features.
Contents
UI
The representation of MRO in the UBIK comprises some indicators and interactive controls for interaction. In the UBIK child list, the main object displays cumulated technical and organisational status as well as the overall work progress that included in the underlying data branch. UBIK objects classified as MRO objects in general provide the indicator for the MRO status. This means the status is shown next to the main icon of a child-/details-/documents-page as well as next to the icons of in the child list items:
Technical Status
The technical status indicator is shown on all objects that represent a technical state or receive the technical status from subsequent objects in the underlying data branch. If e.g. a inventory object is reported as damaged, its parent objects will all display the exclamation mark symbol to indicate that a problem was reported in the child items.
MRO Technical Status Indicator (WinX)
Organisational Status
The organisational status indicator is shown on all objects that represent an organisational state or receive the organisational status from subsequent objects in the underlying data branch. This indicator shows the amount of confirmed work done in the data branch. It can as well display work package to be already confirmed or shows tasks that are already locked by their owning workpackage.
MRO Organisational Status Indicator (WinX)
MRO Workpackage Confirmed or Task Locked Indicator (WinX)
Work Progress
The work progress is shown on all objects that represent the current work progress or receive the work progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.
MRO Work Progress Indicator (WinX)
MRO Objects
A set of specific objects can be used to provide the needed structure of MRO jobs:
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.
MRO Workpackage confirm button (WinX)
MRO Workpackage revoke confirmation button (WinX)
Task
A MROCLS MRO TASK is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called "VALUE" in common. It is very important, that this property has is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.
 | The MetaProperty "VALUE" has to use an ATTRIBUTE in order to be validated. Otherwise, the calculation of work progress will not be possible. |
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. If no value was entered before, an empty line will be shown. Once a value has been entered, 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). An additional small value indicator below the main value can report e.g. the previously entered value. The behaviour of this previous value indicator has to be specified separately in the customizing of UBIK.
MRO Measurement Task without a reported value (WinX)
MRO Measurement Task with a reported value (WinX)
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".
MRO Progress Task with a reported work progress (WinX)
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).
Unfinished MRO CheckTask (WinX)
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.
Finished MRO InspectionTask (WinX)
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)