MRO (Plugin) - Revision history

ARU at 15:47, 2 March 2026

2026-03-02T15:47:22Z

ARU: /* Basic Features */

2026-02-10T08:31:40Z

‎Basic Features

ARU: /* Technical Status */

2026-02-10T08:14:03Z

‎Technical Status

LMA: /* Calculation Task */

2025-06-24T08:21:55Z

‎Calculation Task

LMA: /* Calculation Task */

2025-06-23T14:39:20Z

‎Calculation Task

LMA: /* See also */

2025-06-23T14:34:27Z

‎See also

MMA: /* MRO Implemented Objects */

2025-06-12T13:35:50Z

‎MRO Implemented Objects

MMA: /* MRO Implemented Objects */

2025-06-02T15:29:12Z

‎MRO Implemented Objects

MMA: /* MRO Implemented Objects */

2025-05-22T12:05:23Z

‎MRO Implemented Objects

MMA at 08:59, 21 May 2025

2025-05-21T08:59:27Z

@@ Line 1: / Line 1: @@
 The MRO plugin provides a set of {{UBIK}} objects which allow to represent and document maintenance, repair and operations work on the mobile client. An respective implementation of this set of features is available on {{UBIK WinX}}.
 == Basic Features ==
@@ Line 15: / Line 13: @@
 For detailed information, see [[MRO Objects (Client)#Work Progress|Work Progress]]
 == MRO Objects ==
@@ Line 85: / Line 80: @@
 A [[MRO_Implemented_Objects|Calculation Task]] is used to evaluate a predefined expression and apply its result to a predefined property on its owner. It supports logical or numerical expressions. The result type is defined explicitly to ensure correct handling and validation by the client.
-[[Category:Module|MRO (Plugin)]]
 === Signature Task ===
 Signature Task prompts the user to provide a written signature to confirm task completion. The task is marked complete once the signature is submitted.
-[[Category:Module|MRO (Plugin)]]
 == See also ==

@@ Line 1: / Line 1: @@
 The MRO plugin provides a set of {{UBIK}} objects which allow to represent and document maintenance, repair and operations work on the mobile client. An respective implementation of this set of features is available on {{UBIK WinX}}.
 == Basic Features ==
@@ Line 6: / Line 8: @@
 === Technical Status ===
 For detailed information, see [[MRO Objects (Client)#Technical Status|Technical Status]]
 === Organisational Status ===
-The organisational status indicates the amount of confirmed work done in the data branch. It can include a work package already confirmed or tasks that are already locked by their owning workpackage.
+For detailed information, see [[MRO Objects (Client)#Organisational Status|Organisational Status]]
 === Work Progress ===
-The work progress is calculated from the current work progress and from the progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.
+For detailed information, see [[MRO Objects (Client)#Work Progress|Work Progress]]
 == MRO Objects ==

@@ Line 5: / Line 5: @@
 === Technical Status ===
-The technical status indicates whether all tasks on this or on subsequent objects in the underlying data branch have been finished. Also other information is included in this status, e.g. if a inventory object is reported as damaged, its parent objects will receive a certaub status indicating that a problem was reported in the child items.
+For detailed information, see [[MRO Objects (Client)#Technical Status|Technical Status]]
 === Organisational Status ===

@@ Line 77: / Line 77: @@
 === Calculation Task ===
-A [[MRO_Implemented_Objects|Calculation Task]] is used to evaluate a predefined expression and apply its result dynamically within the MRO environment. It supports logical or numerical expressions and can interact with other objects or properties via a target expression. The result type is defined explicitly to ensure correct handling and validation by the client.
+A [[MRO_Implemented_Objects|Calculation Task]] is used to evaluate a predefined expression and apply its result to a predefined property on its owner. It supports logical or numerical expressions. The result type is defined explicitly to ensure correct handling and validation by the client.
 [[Category:Module|MRO (Plugin)]]

@@ Line 77: / Line 77: @@
 === Calculation Task ===
-A [[MRO_Implemented_Objects|Calculation Task]] is automatically confirmed if a predefined logical or mathematical expression—based on the values of previous tasks—evaluates to a positive result. This allows for conditional automation and validation within the workflow.
+A [[MRO_Implemented_Objects|Calculation Task]] is used to evaluate a predefined expression and apply its result dynamically within the MRO environment. It supports logical or numerical expressions and can interact with other objects or properties via a target expression. The result type is defined explicitly to ensure correct handling and validation by the client.
 === Signature Task ===

@@ Line 101: / Line 101: @@
 * [[MROCLS_SWITCH_START_TASK#Switch Start Task]] (Classification)
 * [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
 [[Category:Module|MRO (Plugin)]]

@@ Line 41: / Line 41: @@
 == MRO Implemented Objects ==
 A set of specific objects extending functionalities of existing MRO elements.<br />
-For Task Objects, Value properties are assigned by default and they all implement [[MROCLS_SEQUENTIALTASK]] classification.
+For Task Objects, Value properties are assigned by default and implement necessary classifications.
 === Procedure Workpackage ===
@@ Line 51: / Line 51: @@
 === Switch End Task ===
 A [[MROCLS_SWITCH_END_TASK|Switch End Task]] marks the end of a branching structure initiated by a [[MROCLS_SWITCH_TASK|Switch Task]]. It is a sequential task that connects the different branches back into a single workflow path. Each Switch End Task is directly linked to its respective Switch Task and ensures that, regardless of which branch was taken, the overall procedure continues in a consistent and controlled manner.
 === Numeric Task ===

@@ Line 47: / Line 47: @@
 === Switch Start Task ===
-A [[MROCLS_SWITCH_TASK|Switch Start Task]] is a type of sequential task used within a Procedure Workpackage to define branching logic. It evaluates a predefined (boolean) condition, which can be checked by the client, to determine which branch (true or false) of the workflow will be followed. Each branch represents a different execution path composed of its own set of tasks. A Switch Start Task always requires a corresponding [[MROCLS_SWITCH_END_TASK|Switch End Task]], where all branches converge and the unified procedure continues.
+A [[MROCLS_SWITCH_START_TASK|Switch Start Task]] is a type of sequential task used within a Procedure Workpackage to define branching logic. It evaluates a predefined (boolean) condition, which can be checked by the client, to determine which branch (true or false) of the workflow will be followed. Each branch represents a different execution path composed of its own set of tasks. A Switch Start Task always requires a corresponding [[MROCLS_SWITCH_END_TASK|Switch End Task]], where all branches converge and the unified procedure continues.
 === Switch End Task ===
@@ Line 78: / Line 78: @@
 A [[MRO_Implemented_Objects|Calculation Task]] is automatically confirmed if a predefined logical or mathematical expression—based on the values of previous tasks—evaluates to a positive result. This allows for conditional automation and validation within the workflow.
-[[Category:Module|MRO (Plugin)]]
 == See also ==
@@ Line 95: / Line 95: @@
 * [[MRO_Implemented_Objects]]
 * [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
-* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
+* [[MROCLS_SWITCH_START_TASK#Switch Start Task]] (Classification)
 * [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
 [[Category:Module|MRO (Plugin)]]