MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. They all implement [[MROCLS_MRO_TASK#Task]] an [[MROCLS SEQUENTIALTASK]] classification. Value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

==== Switch Start Task ====
MetaClass Name: aaa | MetaClass UID: 123

Asdfdfg dfh dfg

Extra Classifications: MROCLS_SWITCH_START_TASK 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| EXPRESSION || {{String}} || Condition that will be evaluated by the client
|-
| EVALUATION_STATUS || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| BRANCH_TRUE || {{Guid}} || Link to another task or task owner for the case the expression is evaluated as true
|-
| BRANCH_FALSE || {{Guid}} || Link to another task or task owner for the case the expression is evaluated as false
|-
| DISPLAYSTRING_TRUE || {{String}} || DisplayString for the case the expression is evaluated as true
|-
| DISPLAYSTRING_FALSE || {{String}} || DisplayString for the case the expression is evaluated as false
|}

==== Switch End Task ====
MetaClass Name: aaa | MetaClass UID: 123

Asdfdfg dfh dfg

Extra Classifications: MROCLS_SWITCH_END_TASK 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|-
| VALUE || {{Boolean}} || Value to mark the task as finished or NA
|}

==== Numeric Task ====
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215

A Numeric Task records a numeric double value (e.g., from a temperature sensor). Once a value is entered (including Not Applicable), the task is considered complete.
An acceptability range and measurement unit can be defined. If the value falls outside the acceptable range, a red alert and/or a technical status update can be triggered.
The behaviour of the previous value indicator must be defined separately.

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Double}} || Recorded double numeric value
|-
| VALUE_MAX || {{Double}} || Upper limit of acceptable range
|-
| VALUE_MIN || {{Double}} || Lower limit of acceptable range
|-
| VALUE_UNIT || {{String}} || Measurment unit
|}

==== Inspection Task ====
MetaClass Name: INSPECTION_TASK | MetaClass UID: 08571b05-a093-479a-a10a-9d03c435b1b5

An Inspection Task captures a binary decision. Once a value is selected (including Not Applicable), the task is complete. 
Custom labels can override the default icons: Checkmark (✔) and Cross (✘).
Label behavior must be defined separately in the customization settings.

Extra Classifications: [[MROCLS_MRO_INSPECTION_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LABEL_FALSE || {{String}} || Label for negative outcome
|-
| LABEL_TRUE || {{String}} || Label for positive outcome
|}

==== Text Task ====
MetaClass Name: TEXT_TASK | MetaClass UID: 7298d038-003a-41d5-bc24-c97018ca7e85

A Text Task allows entry of free-form text. Once a value is entered (including Not Applicable), the task is complete.

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{String}} || Entered text
|}

==== Picture Task ====
MetaClass Name: PICTURE_TASK | MetaClass UID: bee0b281-7da1-470e-9838-46724d47b621

A Picture Task confirms whether a photo has been taken. The task is only complete once a value is entered (including Not Applicable). 
A button must be available to add a photo as a child object. Task confirmation is blocked unless at least one photo is attached.
The behavior for photo addition and confirmation blocking must be defined in customization.

Extra Classifications: [[MROCLS_MRO_CHECK_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|}

==== Dynamic List Task ====
MetaClass Name: DYNAMIC_LIST_TASK | MetaClass UID: 78651014-f41e-4254-987f-6cf55c687d35

A Dynamic List Task allows selection from a list of options. Once a value is selected (including Not Applicable), the task is complete. 
Selection behaviour must be defined in the data model and requires implementation of [[SYSCLS_DYNAMIC_SELECTIVE_LIST|Dynamic Selective List]].

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Guid}} || Selected item
|}

==== Supervisor Check Task ====
MetaClass Name: SUPERVISOR_CHECK_TASK | MetaClass UID: 76910d64-5bc0-4674-9c43-108959119846

A Supervisor Check Task confirms task completion by a supervisor. The task is complete once a value is selected. 
Confirmation is only possible after NFC recognition of the supervisor and PIN entry.

Extra Classifications: [[MROCLS_MRO_SUPERVISOR_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| SUPERVISOR || {{Guid}} || Supervisor
|-
| PERMISSION || {{String}} || Supervisor permissions
|}

==== Interface Task ====
MetaClass Name: INTERFACE_TASK | MetaClass UID: d9a80e3d-02f6-4f0c-b243-7ece9ad82849

Currently under development.

Extra Classifications: [[MROCLS_MRO_SUPERVISOR_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|}

==== Calculation Task ====
MetaClass Name: CALCULATION_TASK | Metaclass UID: 3ec9d0f2-9d0f-4c1b-80bd-1efeaf010fa0

Currently under development.

Extra Classifications: [[MROCLS_MRO_SUPERVISOR_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| EXPRESSION || {{String}} || Expression
|}

== See also ==
* [[MRO_(Plugin)]]
* [[MRO_Objects_(Client)]]
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_SEQUENTIALTASK]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

2025-05-21T08:10:58Z

MMA:

MRO (Plugin)

2025-05-21T08:10:23Z

MMA: /* Switch Task */

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 ==
Objects classified as MRO objects in general provide a technical and organisational status as well as the overall work progress based on the underlying data branch.

=== 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.

=== 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.

=== 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.

== MRO Objects ==
A set of specific objects can be used to provide the required structure for MRO:

=== Task Owner ===
A [[MROCLS_MRO_TASKOWNER|Task Owner]] 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 information. 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|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 ===
A [[MROCLS_MRO_TASK|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 is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.

{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}

==== Measurement Task ====
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). 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).

==== Progress Task ====
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and 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 ====
[[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.

==== Inspection Task ====
A [[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).

== MRO Implemented Objects ==
A set of specific objects extending functionalities of existing MRO elements. 
For Task Objects, Value properties are assigned by default and they all implement [[MROCLS_SEQUENTIALTASK]] classification.

=== Procedure Workpackage ===
A [[MROCLS_PROCEDURE|Procedure Workpackage]] is a specialized type of [[MROCLS_MRO_WORKPACKAGE|Work Package]] designed to model complex workflows. It consists of sequential tasks that can include branching logic, modular structures, and references to linked data. Procedure Workpackages allow the execution of structured processes that may adapt dynamically depending on conditions. They support both online and offline execution, with certain steps (e.g. data exchange) triggered once connectivity is available.

=== Switch Start Task ===
A [[MROCLS_SWITCH_TASK|Switch 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 Task always requires a corresponding [[MROCLS_SWITCH_END_TASK|Switch End Task]], where all branches converge and the unified procedure continues.

[[Category:Module|MRO (Plugin)]]

=== 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 ===
A [[MRO_Implemented_Objects|Numeric Task]] allows the user to input a numeric value (double). It includes a defined value range, and if the entered value falls outside this range, the task is visually marked as problematic.

=== Inspection Task ===
An [[MRO_Implemented_Objects|Inspection Task]] presents the user with two customizable buttons representing different inspection outcomes, along with a Not Applicable option. The labels of the buttons can be defined during the procedure creation.

=== Text Task ===
A [[MRO_Implemented_Objects|Text Task]] provides a text input field for the user to enter free-form information. This task is useful for capturing qualitative data or comments during the procedure.

=== Picture Task ===
A [[MRO_Implemented_Objects|Picture Task]] enables the user to take and attach one or more photos. It includes a button to initiate the camera and another to confirm the task. The confirmation button remains disabled until at least one picture has been successfully captured.

=== Dynamic List Task ===
A [[MRO_Implemented_Objects|Dynamic List Task]] presents a button that, when clicked, displays a list of selectable options. These options are defined by the procedure creator and can vary depending on the context. This task is ideal for scenarios requiring user selection from a predefined but flexible set of choices.

=== Supervisor Task ===
A [[MRO_Implemented_Objects|Supervisor Task]] includes a button for NFC reading. If a supervisor successfully authenticates, it enables confirmation buttons, input fields, or other interactive elements.

=== Interface Task ===
An [[MRO_Implemented_Objects|Interface Task]] performs a REST API request automatically when it becomes active. It does not include any visible buttons or user interaction. Once the server responds, the task is automatically confirmed based on the response.

=== 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.

[[Category:Module|MRO (Plugin)]]

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK# Progress Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MROCLS_SEQUENTIALTASK]] (Classification)
* [[MROCLS_GROUPEDTASK]] (Classification)
* [[MROCLS_PROJECT]] (Classification)
* [[MROCLS_PROJECTINFORMATION]] (Classification)
* [[MRO_Objects_(Client)]]
* [[MRO_Implemented_Objects]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Module|MRO (Plugin)]]

MRO (Plugin)

2025-05-21T08:07:49Z

MMA: /* MRO Implemented Objects */

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 ==
Objects classified as MRO objects in general provide a technical and organisational status as well as the overall work progress based on the underlying data branch.

=== 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.

=== 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.

=== 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.

== MRO Objects ==
A set of specific objects can be used to provide the required structure for MRO:

=== Task Owner ===
A [[MROCLS_MRO_TASKOWNER|Task Owner]] 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 information. 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|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 ===
A [[MROCLS_MRO_TASK|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 is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.

{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}

==== Measurement Task ====
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). 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).

==== Progress Task ====
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and 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 ====
[[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.

==== Inspection Task ====
A [[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).

== MRO Implemented Objects ==
A set of specific objects extending functionalities of existing MRO elements. 
For Task Objects, Value properties are assigned by default and they all implement [[MROCLS_SEQUENTIALTASK]] classification.

=== Procedure Workpackage ===
A [[MROCLS_PROCEDURE|Procedure Workpackage]] is a specialized type of [[MROCLS_MRO_WORKPACKAGE|Work Package]] designed to model complex workflows. It consists of sequential tasks that can include branching logic, modular structures, and references to linked data. Procedure Workpackages allow the execution of structured processes that may adapt dynamically depending on conditions. They support both online and offline execution, with certain steps (e.g. data exchange) triggered once connectivity is available.

=== Switch Task ===
A [[MROCLS_SWITCH_TASK|Switch 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 Task always requires a corresponding [[MROCLS_SWITCH_END_TASK|Switch End Task]], where all branches converge and the unified procedure continues.

=== 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 ===
A [[MRO_Implemented_Objects|Numeric Task]] allows the user to input a numeric value (double). It includes a defined value range, and if the entered value falls outside this range, the task is visually marked as problematic.

=== Inspection Task ===
An [[MRO_Implemented_Objects|Inspection Task]] presents the user with two customizable buttons representing different inspection outcomes, along with a Not Applicable option. The labels of the buttons can be defined during the procedure creation.

=== Text Task ===
A [[MRO_Implemented_Objects|Text Task]] provides a text input field for the user to enter free-form information. This task is useful for capturing qualitative data or comments during the procedure.

=== Picture Task ===
A [[MRO_Implemented_Objects|Picture Task]] enables the user to take and attach one or more photos. It includes a button to initiate the camera and another to confirm the task. The confirmation button remains disabled until at least one picture has been successfully captured.

=== Dynamic List Task ===
A [[MRO_Implemented_Objects|Dynamic List Task]] presents a button that, when clicked, displays a list of selectable options. These options are defined by the procedure creator and can vary depending on the context. This task is ideal for scenarios requiring user selection from a predefined but flexible set of choices.

=== Supervisor Task ===
A [[MRO_Implemented_Objects|Supervisor Task]] includes a button for NFC reading. If a supervisor successfully authenticates, it enables confirmation buttons, input fields, or other interactive elements.

=== Interface Task ===
An [[MRO_Implemented_Objects|Interface Task]] performs a REST API request automatically when it becomes active. It does not include any visible buttons or user interaction. Once the server responds, the task is automatically confirmed based on the response.

=== 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.

[[Category:Module|MRO (Plugin)]]

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK# Progress Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MROCLS_SEQUENTIALTASK]] (Classification)
* [[MROCLS_GROUPEDTASK]] (Classification)
* [[MROCLS_PROJECT]] (Classification)
* [[MROCLS_PROJECTINFORMATION]] (Classification)
* [[MRO_Objects_(Client)]]
* [[MRO_Implemented_Objects]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Module|MRO (Plugin)]]

MRO Implemented Objects

2025-05-21T08:07:14Z

MMA:

2025-05-19T17:23:17Z

MMA:

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features.
Value properties are pre-set, and many objects also implement additional MRO-relevant classifications.

==== Numeric Task ====

A Numeric Task records a numeric double value (e.g., from a temperature sensor). Once a value is entered (including Not Applicable), the task is considered complete.
An acceptability range and measurement unit can be defined. If the value falls outside the acceptable range, a red alert and/or a technical status update can be triggered.
The behaviour of the previous value indicator must be defined separately.

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Double}} || Double Number
|-
| VALUE_MAX || {{Double}} || Upper limit of acceptable range
|-
| VALUE_MIN || {{Double}} || Lower limit of acceptable range
|-
| VALUE_UNIT || {{String}} || Measurment unit
|}

==== Inspection Task ====
An Inspection Task captures a binary decision. Once a value is selected (including Not Applicable), the task is complete.

Custom labels can override the default icons: Checkmark (✔) and Cross (✘).
Label behavior must be defined separately in the customization settings.

Extra Classifications: [[MROCLS_MRO_INSPECTION_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LABEL_FALSE || {{String}} || Label for negative outcome
|-
| LABEL_TRUE || {{String}} || Label for positive outcome
|}

==== Text Task ====
A Text Task allows entry of free-form text. Once a value is entered (including Not Applicable), the task is complete.

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{String}} || Entered Text
|}

==== Picture Task ====

A Picture Task confirms whether a photo has been taken. The task is only complete once a value is entered (including Not Applicable).

A button must be available to add a photo as a child object. Task confirmation is blocked unless at least one photo is attached.
The behavior for photo addition and confirmation blocking must be defined in customization.

Extra Classifications: [[MROCLS_MRO_CHECK_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|}

==== Dynamic List Task ====
A Dynamic List Task allows selection from a list of options. Once a value is selected (including Not Applicable), the task is complete.

Selection behaviour must be defined in the data model and requires implementation of [[SYSCLS_DYNAMIC_SELECTIVE_LIST|Dynamic Selective List]].

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Guid}} || Selected Item
|}

==== Interface Task ====
Currently under development.

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task is Done
|}

==== Calculation Task ====
Currently under development.

Extra Classifications: none 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|}

==== Supervisor Check Task ====
A Supervisor Check Task confirms task completion by a supervisor. The task is complete once a value is selected.

Confirmation is only possible after NFC recognition of the supervisor and PIN entry.

Extra Classifications: [[MROCLS_MRO_SUPERVISOR_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| SUPERVISOR || {{Guid}} || Supervisor
|-
| PERMISSION || {{String}} || Supervisor permissions
|}