UBIK Wiki Test / Augmensys - User contributions [en]

Import Runs

2025-11-28T10:28:07Z

LMA:

= Naming Convention =

'''General file naming convention:'''
All import Excel files must follow the pattern:

xxxx.<import-type>.xlsx

Where xxxx can be any project- or customer-specific identifier.

Supported import types:

* Equipment Import
xxxx.equipment.xlsx

* Workorder Import
xxxx.workorder.xlsx

* Progress Operation Import
xxxx.progress-op.xlsx

* QRF Operation Import
xxxx.qrf-op.xlsx

* Check Operation Import
xxxx.check-op.xlsx

* Joint Operation Import
xxxx.joint-op.xlsx

* Blinding Operation Import
xxxx.blinding-op.xlsx

* Scheduling Import
xxxx.scheduling.xlsx

* User Import
xxxx.user.xlsx

* Company Import
xxxx.company.xlsx

* Material Import
xxxx.material.xlsx

* Preparation Document Import
xxxx.preparation-document.xlsx

* Joint Location Import
xxxx.joint-location.xlsx

* Blinding Location Import
xxxx.blinding-location.xlsx

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Joint Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Blinding Operation Import =

To import Blinding Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* BlindingLocation (Text)
* Type (Text)
* BlindingPackage (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

= Joint Location Import =

To import joint locations following columns are required:
* Joint_ID (Text)

Columns that can be imported additionally:
* Joint_Location_Number (Text)
* Name (Text)
* Remark (Text)
* Tag_Number (Text)
* Gasket_Type (Text)
* Flange_Spec (Text)
* Flange_Size (Text)
* Flange_Rating (Text)
* Bolt_Size (Text)
* Bolt_Number (Text)
* Bolt_Material (Text)
* Torque_Value (Text)
* Pressure (Text)
* Assembled_By (Text)
* Assembled Date (TT/MM/JJJJ hh:mm)
* Inspected_By (Text)
* Inspected_Date (TT/MM/JJJJ hh:mm)
* Equipment (Text)

= Blinding Location Import =

To import joint locations following columns are required:
* BlindingLocation_ID (Text)

Columns that can be imported additionally:
* No (Text)
* Equipment (Text)
* SOP (Text)
* Description (Text)
* BlindingNumber (Text)
* PID (Text)
* Size (Text)
* Type (Text)
* LocationType (Text)
* NormalPosition (Text)
* OnSite (Text)
* ICCNumber (Text)
* BlindSapNumber (Text)
* BlindQuantity (Number)
* GasketSAPNumber (Text)
* GasketQuantity (Number)
* Stage (Text)
* Height (Text)
* Scaff (Text)
* Insul (Text)
* Crane (Text)
* Remarks (Text)

[[Category:MaTaP|Import Runs]]

Entry Points & Use Cases (Admin Tool)

2025-11-19T13:15:38Z

LMA:

== Entry Points ==

To display various data in the Admin Tool, we have the following Entry Points with Use Cases under them:

<tabs>
<tab Name="00 - All Important">
Under Entry Point 00 - All Important are the following Use Cases:
* All Icons: Displays all icons that have already been created / set up.”
* Job Runs: Displays all jobs that have been initialized for all turnaround projects.
* Project: Shows all Turnaround Projects in the database. It is important for the execution of jobs.
</tab>
<tab Name="01 - All Other">
For the 01 - All Other Entry Point, its Use Cases show all Data, regardless of whether instances are Templates or belong to a Project or not. Under Entry Point 01 - All Other, there are the following Use Cases:
* Activity Codes
* All Locations
* Blinding Location
* Blinding Operation
* Commissioning Codes
* Commissioning Packages
* Commissioning Tasks
* Companies
* Company Icons
* Daily HSE
* Daily Meetings
* Equipment Groups
* Equipment Types
* Equipment’s
* Execution Documents
* Joint Locations
* Joint Operations
* Functional Locations
* Functionalities
* Material
* Media
* Notifications
* Progress Operations
* QRF Operations
* Check Operations
* Plants
* Plot Plans
* Predefined Filters
* Predefined Views
* Preparation Documents
* Punchpoint Attachments
* Punchpoints
* Quick Access Items
* Reports
* Scope Change attachments
* Scope Changes
* Subsystems
* Systems
* Timesheets
* Users
* Workorders
* Zones
</tab>

<tab Name="02 - Templates">

The Use Cases under this entry point are for displaying data that is only marked as a template. By default, there are already pre-made Use Cases for displaying template data, which are the following:
* Activity Codes
* Commissioning Codes
* Equipment Group
* Equipment Type
* Functionalities
* Users
</tab>

<tab Name="Project">
===Project-specific Entry Points===
These entry points display data that belongs to the respective project. For example, if the TurnaroundProjectCreationJob is executed for a Turnaround Project, there will be a new Entry Point created for this Turnaround Project. All Use Cases under such an entry point only display instances belonging to this specific project. There is also a difference between the TA Project Entry Points and the 01 - All Other, in that the TA Project Entry Point has one more use case, the Turnaround Project Use Case. This use case displays only the Turnaround Project in which it has been opened.

</tab>
</tabs>

== Use Cases ==

<tab Name="All Icons" collapsed>

Under this use case, it is possible to create icons, which can then be assigned to Contractors / Companies.

[[File:MatapIcons.png]]

To be able to upload a photo, the name and description properties must be filled out and press “Enter”. Then a double click has to be made on the instances "Icon" property (without a sign on the left side) and then on the button with the three dots. After that a Windows Explorer will open and a selection can be made for the desired image. When the selection is uploaded the icon field will be filled automatically and the last step is to save everything. The icon is now successfully created and could now be assigned to a contractor/company.

</tab>

<tab Name="Companies" collapsed>

With the "Companies" use case we display all Companies/Contractors that are created in total (Entry Point 01 - All Other) or are linked to a specific project (Entry Points Project).

[[File:Companies_MATAP_Picture.png]]

The assigning of custom icons to the company/contractor is also done here. This will be done by double-clicking on the "Icon" property shown in the picture below. After pressing the "three dots" button, a pop-up window will open and one of all available icons can be selected. Operations will automatically get the same custom icon after the selection is made.

[[File:Company_Icon_query.png]]

</tab>

<tab Name="Functionalities" collapsed>
Under this use case, you can view and edit the root items (tiles) that are delivered to the clients.

The following Functionalities are displayed:

* Commissioning Wallpaper
* Communication
* Daily HSE
* Daily Meetings
* Plant Layouts
* Precom
* Punchpoints
* Quick access
* Reports
* Scope Changes
* Turnaround Wallpaper
 
You can also change the default Branch Download Configruation for every functionality. The corresponding properties are "Branchdownload Levels" and "Offline Sync Configuration". By default the auto branch download for Turnaround Wallpaper and Commissioning Wallpaper is enabled.

 
[[File:Functionalities.png|alt=Functionalities|Functionalities]]

== ORDERID & GROUPID ==
With these two properties, you can set the order (sorting) of the Functionalities (RootItems) on the client.
See the [[SYSCLS SORTEDITEM]] and [[HowTo:Sort_Objects_on_Mobile_Client]] articles for instructions on how to set up the sorting.

 

== Visibility on Client ==
With this property, you can set the visibility of individual functionalities for the UWP and Mobile client.
There are 5 options available that can be chosen:

 

* Undefined
undefined
 
* Fully Visible
UWP and Mobile users can see this functionality
 
* Only Desktop
Only Desktop (UWP) users can see this functionality
 
* Only Mobile
Only mobile users can see this functionality
 
* Hidden
No one can see this functionality

 

Based on these options you can control and change the visibility of the functionalities for different clients depending on the application use. If this property changes for a functionality, the user group rights are adjusted in the background, and only users who are in the groups that have the rights can then see the functionality on the client.
The users must be added to one of the following groups in order to make the visibility of the functionalities applicable to them:
* G1 General WallpaperWrite Group (UWP)
* G30 General ReadProject Group (Mobile).

</tab>

<tab Name="Project (Use Case)" collapsed>

For the "Project" use case, we either display all projects ( [[#Entry Points|See Entry Points => 00 - All Important]] ) or only the project for which replication has been performed ( [[#Entry Points|See Entry Points => Project]] ).
In both cases, the following properties are displayed in the columns:

* Archived
* Backup Export Path
* Create Timestamp
* Critical delay buffer
* Cultural Settings
* Description
* Document Export Path
* Handover to Contractor Activity Code
* Handover to Contractor Activity Code Order
* Handover to Contractor Commissioning Code
* Handover to Contractor Commissioning Code Order
* Icon
* Interface is active
* Location
* Name
* Planned Project End
* Planned Project Start
* Planning Plant
* Precom ready Activity Code
* Precom ready Activity Code Order
* Precom Ready Commissioning Code
* Precom Ready Commissioning Code Order
* Primavera Export Path
* Project ID
* Project Status
* Project System Status
* Project Type
* Revision Codes
* SAP Interface Is Active
* SAP System
* Scheduling Option
* Show On Wallpaper
* System
* Show on Wallpaper
* Timesheet decline limit
* Update timestamp

 
[[File:Turnaround_Project_Use_Case_Columns_Admin_Tool.png|1200px]]
 

== Project Status ==
This property allows you to define the status of the project.

It is important to note that the preparations for the Project must be completed before changing the value of this property. Once all preparations are finalized (all jobs have been executed), the Admin Tool user must manually change this value to "Execution"; otherwise, the push will not work.

In the case of the Recalculate Project Job, the [[#SAP Interface Is Active|SAP Interface Is Active]] is also important.

There are 4 options available that can be chosen:
 
* Preparation (initial value)
- Here, the Excel files are imported, and the project is prepared.
- The current scheduling from Primavera is retrieved and also imported.
- Then the project can be assigned to a slot for testing. (Doesn't have to be live eg. push not active)
 
* Execution
- The project remains on the slot and can then be executed live on the wallpaper.
- Changes are only allowed outside of service hours.
 
* Aftercare
- The project is removed from the slot but remains in the current MaTaP database for possible discussions, reports, etc.
 
* Ready For Archive
- The project can be moved to an archive database—it is no longer assigned to any slot.
- If there is a backup of the database, it is stored in parallel to PROD with a .archive extension and can still be analyzed with the admin tool.

== Show On Wallpaper ==
This property allows you to assign the project to a slot, which is displayed on the wallpaper at the client depending on the Matap context.

== SAP Interface Is Active ==
This property allows you to control whether the SAP interface is active, i.e., whether SAP imports are enabled.
As long as this property is set to active (true), the Recalculate Project Job cannot be executed.

</tab>

== Whitelist ==

Using the whitelist relation (REL_COLUMN_WHITELIST), the customizer can configure, which columns (properties) will be seen for each use case in the Bulk Editor. Moreover, it is possible/necessary to edit the order, editability and info text of a column (property). For the Use Cases provided via the system definitions, we already have defined whitelists that can be adapted when needed.

Now we come to the configuration of the whitelist for a use case: 
1. Open your UBIK.Studio. 
2. Navigate to the following point: System => System.Matap => System.Matap.AdminTool => USE_CASE_ADMIN_TOOL_QUERY. 
3. Open the USE_CASE_ADMIN_TOOL_QUERY in the Bulk Editor. 
4. Open the use case whose columns you want to change in the Relation Editor. 
5. Drag and drop the Meta Property that you want to have shown into the REL_COLUMN_WHITELIST Section. 
6. Click on the MetaProperty that is now under the relation. 
7. On the left side you can define the order (COLUMN_ORDER), if it is locked (LOCKED), the information text (INFORMATION_TEXT) and if it should be preloaded (MP_PRELOAD). 

== MP_PRELOAD ==

There is also the possibility to preload properties, and this can be set with “MP_PRELOAD”. Just check this, and the property where the “MP_PRELOAD” was set will be preloaded. This can be set individually for each property.

== COLUMN_ORDER ==

COLUMN_ORDER stores the column position order of a UseCase's property that is shown in the Admin Tool.

== LOCKED ==

LOCKED defines if a property will be editable or not in the Admin Tool.

== INFORMATION_TEXT ==

INFORMATION_TEXT stores the additional text shown for a column in the Admin Tool.

 

[[Category:Admin Tool|Entry Points & Use Cases (Admin Tool)]]
[[Category:MaTaP|Entry Points & Use Cases]]

MaTaP

2025-08-26T12:22:33Z

LMA: /* MaTaP Functionality */

= MaTaP: Management Tool for Turnaround and Project Management =
MaTaP is a management tool for Turnaround and Project management, applicable across various industries.

The front-end user can access MaTaP on Desktop (UWP), as well as iOS and Android mobile platforms. Projects are administrated using the desktop Admin Tool.

=== Key Features ===
* '''Wallpaper Task Overview'''
* '''Reports'''
* '''Daily HSE
* '''Plant Layouts'''
* '''Scope Changes'''
* '''Punch Points'''

[[Category:Admin Tool|MaTaP Admin Tool]]
[[Category:MaTaP|MaTaP]]
[[Category:MaTaP UWP|MaTaP UWP App]]

=== Products ===
{| class="wikitable"
|-
|'''Desktop (UWP) Client'''
|A comprehensive desktop application that provides full access to all MaTaP features for in-office use.
|-
|'''Mobile Client'''
|Offers on-the-go access to critical project information, ensuring managers and team members can stay updated anywhere, anytime.
|-
|'''AdminTool'''
|A specialized tool designed for system administrators to manage user accounts, configure system settings, and perform maintenance tasks.
|}

== MaTaP Admin Tool ==

* [[Entry_Points_%26_Use_Cases_(Admin_Tool)]]
* [[Project Page]]
* [[Import Runs]]
* [[User Rights for MaTaP Users]]
* [[Quick Information]]
 

[[Category:Admin Tool|MaTaP Admin Tool]]
[[Category:MaTaP|MaTaP]]
[[Category:MaTaP UWP|MaTaP UWP App]]

= MaTaP Desktop (UWP) Client =
MaTaP (Management tool for Turnarounds and Projects) is a holistic solution for the progress reporting of Turnaround and maintenance projects.

== General Client Information ==
* [[Login Page MaTaP UWP App]]
* [[Home Page]]

== MaTaP Functionality ==
* [[Turnaround Wallpaper]]
* [[Punch Points]]
* [[Scope_Changes]]
* [[Commissioning Wallpaper]]
* [[Reports]]
* [[Daily HSE]]
* [[Plant Layouts]]
* [[Communication]]
* [[Quick Access]]
* [[Daily Meetings]]

[[Category:Admin Tool|MaTaP Admin Tool]]
[[Category:MaTaP|MaTaP]]
[[Category:MaTaP UWP|MaTaP UWP App]]

= MaTaP Server =

== General Information ==
* [[How to set up a database for MaTaP]]

== MaTaP Server Functionality ==
* [[SubSystem Assignment]]
* [[PublishCommissioningWallpaperJobOrchestrator]]
* [[RecalculateProjectJobOrchestrator]]
* [[RecycleAppPoolJobOrchestrator]]

[[Category:Admin Tool|MaTaP Admin Tool]]
[[Category:MaTaP|MaTaP]]
[[Category:MaTaP UWP|MaTaP UWP App]]

UBIK Active Lists

2025-08-08T13:36:32Z

LMA: /* Who-Bert Example */

{{UBIK}} ActiveLists provide the possibility to configure instance-specific lists for integer MetaProperties.

= Purpose =
In some cases it is required to define a list of selectable values for an integer MetaProperty that is specific to a single instance rather than globally defined at the MetaClass level. For example, two instances of the same MetaClass can offer different selectable values for the same MetaProperty.

{{UBIK}} ActiveLists are the representation of such lists. They update dynamically on the client side without requiring an ACM rebuild and can be maintained per instance through server methods.

If a MetaProperty has both a SelectiveList and an ActiveList, the SelectiveList takes precedence when data is displayed on the client, and the ActiveList is ignored.

= Client Behavior =
When an integer MetaProperty has an ActiveList defined, the property is displayed using the existing icon (the same icon applied to properties with a SelectiveList), followed by the property's display string and the label of the currently selected list item in a closed drop-down component{{Version/ServerSince|5.0.0.0}}.

For editing, the client uses a dropdown menu UI component. The dropdown menu enables users to select exactly one value for the MetaProperty from the ActiveList.
When the user opens the dropdown:

* All available options from the ActiveList are displayed as text labels.
* The label for each option is shown in the language configured on the web service. If a translation for the configured language is unavailable, the label is displayed in the default language.
* Each option in the ActiveList has an associated unique integer value that is set to the MetaProperty when selected.
* Only one option can be selected at a time. Selecting an option updates the MetaProperty value immediately.

Sorting of items in the dropdown:

* If all options in the ActiveList have unique sort order values, they are displayed in ascending order of these sort order values.
* If sort orders are not unique, options with the same sort order are sorted in ascending order by their label.

= Server-Side Concept =
ActiveLists are stored in serialized JSON form in the '''ACTIVE_LISTS''' property of the instance.

* Each list is associated with exactly one integer MetaProperty of the instance.
* An instance can have multiple ActiveLists, one for each integer MetaProperty.
* ActiveLists can be viewed in UBIK.Studio in the Object Explorer under “ActiveLists” for the instance, but they cannot be edited there.

= Managing {{UBIK}} ActiveLists =
ActiveLists are managed entirely through server methods. The most relevant methods are:

=== AddOrUpdateActiveList(metaProperty, value, labels, sortOrder) ===
Adds a new list item or updates the labels of an existing one. Optionally repositions the item according to sortOrder.

=== SortActiveList(metaProperty, orderedValues) ===
Reorders the items of a list according to the specified sequence. Items not included in '''orderedValues''' are appended in their current order.

=== RemoveActiveListItem(metaProperty, value) ===
Removes a single list item by its integer value.

=== RemoveActiveList(metaProperty) ===
Removes the entire list for the given MetaProperty.

=== GetActiveLists() ===
Returns all ActiveLists defined on the instance as '''UbikActiveList''' objects, each containing the MetaProperty name and its list items.

= Who-Bert Example =
The following Who-Bert snippet demonstrates how to work with an ActiveList for a MetaProperty named "'''MP_INT_A'''":

<syntaxhighlight lang="csharp">
using System;
using System.Windows.Forms;
using System.Linq;
using System.Collections.Generic;
using UBIK.Kernel;
using UBIK.Runtime;
using UBIK.Runtime.Sys;
using UBIK.Compiler;
using UBIK.Content;

namespace Studio
{
public class ObjectTest
{
public void TestObject(params BaseClass[] InVariables)
{
Debugger.Output(this, "*** Started ActiveList Example");
foreach (BaseClass obj in InVariables)
{
ContentClass c = obj as ContentClass;

var labels1 = new Dictionary<string, string> { { "en", "One" }, { "de", "Eins" } };
var labels2 = new Dictionary<string, string> { { "en", "Two" }, { "de", "Zwei" } };
var labels3 = new Dictionary<string, string> { { "en", "Three" }, { "de", "Drei" } };

// Add items
c.AddOrUpdateActiveList("MP_INT_A", 1, labels1);
c.AddOrUpdateActiveList("MP_INT_A", 2, labels2);
c.AddOrUpdateActiveList("MP_INT_A", 3, labels3);

// Update labels and move item 3 to index 0
var labels3Updated = new Dictionary<string, string> { { "en", "Three Updated" }, { "de", "Drei Aktualisiert" } };
c.AddOrUpdateActiveList("MP_INT_A", 3, labels3Updated, 0);

// Sort items: 2, 1, 3
c.SortActiveList("MP_INT_A", new int[] { 2, 1, 3 });

// Remove item 1
c.RemoveActiveListItem("MP_INT_A", 1);

c.Save();
}
Debugger.Output(this, "*** Finished ActiveList Example");
}
}
} </syntaxhighlight>

[[Category:ActiveList|UBIK Active Lists]]
[[Category:Server|UBIK Active Lists]]

= Further Notes =

* ActiveLists are designed for lightweight, instance-specific value lists that can be updated without ACM rebuilds.
* They are ideal for use cases where list content varies between instances of the same MetaClass.
* When both an ActiveList and a SelectiveList are defined for the same MetaProperty, the SelectiveList overrides the ActiveList on the client.

[[Category:Server|UBIK Active Lists]]
[[Category:ActiveList|UBIK Active Lists]]

UBIK Active Lists

2025-08-08T13:25:47Z

LMA:

{{UBIK}} ActiveLists provide the possibility to configure instance-specific lists for integer MetaProperties.

= Purpose =
In some cases it is required to define a list of selectable values for an integer MetaProperty that is specific to a single instance rather than globally defined at the MetaClass level. For example, two instances of the same MetaClass can offer different selectable values for the same MetaProperty.

{{UBIK}} ActiveLists are the representation of such lists. They update dynamically on the client side without requiring an ACM rebuild and can be maintained per instance through server methods.

If a MetaProperty has both a SelectiveList and an ActiveList, the SelectiveList takes precedence when data is displayed on the client, and the ActiveList is ignored.

= Client Behavior =
When an integer MetaProperty has an ActiveList defined, the property is displayed using the existing icon (the same icon applied to properties with a SelectiveList), followed by the property's display string and the label of the currently selected list item in a closed drop-down component{{Version/ServerSince|5.0.0.0}}.

For editing, the client uses a dropdown menu UI component. The dropdown menu enables users to select exactly one value for the MetaProperty from the ActiveList.
When the user opens the dropdown:

* All available options from the ActiveList are displayed as text labels.
* The label for each option is shown in the language configured on the web service. If a translation for the configured language is unavailable, the label is displayed in the default language.
* Each option in the ActiveList has an associated unique integer value that is set to the MetaProperty when selected.
* Only one option can be selected at a time. Selecting an option updates the MetaProperty value immediately.

Sorting of items in the dropdown:

* If all options in the ActiveList have unique sort order values, they are displayed in ascending order of these sort order values.
* If sort orders are not unique, options with the same sort order are sorted in ascending order by their label.

= Server-Side Concept =
ActiveLists are stored in serialized JSON form in the '''ACTIVE_LISTS''' property of the instance.

* Each list is associated with exactly one integer MetaProperty of the instance.
* An instance can have multiple ActiveLists, one for each integer MetaProperty.
* ActiveLists can be viewed in UBIK.Studio in the Object Explorer under “ActiveLists” for the instance, but they cannot be edited there.

= Managing {{UBIK}} ActiveLists =
ActiveLists are managed entirely through server methods. The most relevant methods are:

=== AddOrUpdateActiveList(metaProperty, value, labels, sortOrder) ===
Adds a new list item or updates the labels of an existing one. Optionally repositions the item according to sortOrder.

=== SortActiveList(metaProperty, orderedValues) ===
Reorders the items of a list according to the specified sequence. Items not included in '''orderedValues''' are appended in their current order.

=== RemoveActiveListItem(metaProperty, value) ===
Removes a single list item by its integer value.

=== RemoveActiveList(metaProperty) ===
Removes the entire list for the given MetaProperty.

=== GetActiveLists() ===
Returns all ActiveLists defined on the instance as '''UbikActiveList''' objects, each containing the MetaProperty name and its list items.

= Who-Bert Example =
The following Who-Bert snippet demonstrates how to work with an ActiveList for a MetaProperty named "'''MP_INT_A'''":

<syntaxhighlight lang="csharp">
using System;
using System.Windows.Forms;
using System.Linq;
using System.Collections.Generic;
using UBIK.Kernel;
using UBIK.Runtime;
using UBIK.Runtime.Sys;
using UBIK.Compiler;
using UBIK.Content;

namespace Studio
{
public class ObjectTest
{
public void TestObject(params BaseClass\[] InVariables)
{
Debugger.Output(this, "\*\*\* Started ActiveList Example");
foreach (BaseClass obj in InVariables)
{
ContentClass c = obj as ContentClass;

var labels1 = new Dictionary<string, string> { { "en", "One" }, { "de", "Eins" } };
var labels2 = new Dictionary<string, string> { { "en", "Two" }, { "de", "Zwei" } };
var labels3 = new Dictionary<string, string> { { "en", "Three" }, { "de", "Drei" } };

// Add items
c.AddOrUpdateActiveList("MP_INT_A", 1, labels1);
c.AddOrUpdateActiveList("MP_INT_A", 2, labels2);
c.AddOrUpdateActiveList("MP_INT_A", 3, labels3);

// Update labels and move item 3 to index 0
var labels3Updated = new Dictionary<string, string> { { "en", "Three Updated" }, { "de", "Drei Aktualisiert" } };
c.AddOrUpdateActiveList("MP_INT_A", 3, labels3Updated, 0);

// Sort items: 2, 1, 3
c.SortActiveList("MP_INT_A", new int[] { 2, 1, 3 });

// Remove item 1
c.RemoveActiveListItem("MP_INT_A", 1);

c.Save();
}
Debugger.Output(this, "*** Finished ActiveList Example");
}
}
} </syntaxhighlight>

= Further Notes =

* ActiveLists are designed for lightweight, instance-specific value lists that can be updated without ACM rebuilds.
* They are ideal for use cases where list content varies between instances of the same MetaClass.
* When both an ActiveList and a SelectiveList are defined for the same MetaProperty, the SelectiveList overrides the ActiveList on the client.

[[Category:Server|UBIK Active Lists]]
[[Category:ActiveList|UBIK Active Lists]]

Category:ActiveList

2025-08-08T13:25:26Z

LMA: Created page with "Category:Server"

[[Category:Server]]

UBIK Active Lists

2025-08-08T13:23:57Z

LMA: Created page with "{{UBIK}} ActiveLists provide the possibility to configure instance-specific lists for integer MetaProperties. = Purpose = In some cases it is required to define a list of sel..."

{{UBIK}} ActiveLists provide the possibility to configure instance-specific lists for integer MetaProperties.

= Purpose =
In some cases it is required to define a list of selectable values for an integer MetaProperty that is specific to a single instance rather than globally defined at the MetaClass level. For example, two instances of the same MetaClass can offer different selectable values for the same MetaProperty.

{{UBIK}} ActiveLists are the representation of such lists. They update dynamically on the client side without requiring an ACM rebuild and can be maintained per instance through server methods.

If a MetaProperty has both a SelectiveList and an ActiveList, the SelectiveList takes precedence when data is displayed on the client, and the ActiveList is ignored.

= Client Behavior =
When an integer MetaProperty has an ActiveList defined, the property is displayed using the existing icon (the same icon applied to properties with a SelectiveList), followed by the property's display string and the label of the currently selected list item in a closed drop-down component{{Version/ServerSince|5.0.0.0}}.

For editing, the client uses a dropdown menu UI component. The dropdown menu enables users to select exactly one value for the MetaProperty from the ActiveList.
When the user opens the dropdown:

* All available options from the ActiveList are displayed as text labels.
* The label for each option is shown in the language configured on the web service. If a translation for the configured language is unavailable, the label is displayed in the default language.
* Each option in the ActiveList has an associated unique integer value that is set to the MetaProperty when selected.
* Only one option can be selected at a time. Selecting an option updates the MetaProperty value immediately.

Sorting of items in the dropdown:

* If all options in the ActiveList have unique sort order values, they are displayed in ascending order of these sort order values.
* If sort orders are not unique, options with the same sort order are sorted in ascending order by their label.

= Server-Side Concept =
ActiveLists are stored in serialized JSON form in the '''ACTIVE_LISTS''' property of the instance.

* Each list is associated with exactly one integer MetaProperty of the instance.
* An instance can have multiple ActiveLists, one for each integer MetaProperty.
* ActiveLists can be viewed in UBIK.Studio in the Object Explorer under “ActiveLists” for the instance, but they cannot be edited there.

= Managing {{UBIK}} ActiveLists =
ActiveLists are managed entirely through server methods. The most relevant methods are:

=== AddOrUpdateActiveList(metaProperty, value, labels, sortOrder) ===
Adds a new list item or updates the labels of an existing one. Optionally repositions the item according to sortOrder.

=== SortActiveList(metaProperty, orderedValues) ===
Reorders the items of a list according to the specified sequence. Items not included in '''orderedValues''' are appended in their current order.

=== RemoveActiveListItem(metaProperty, value) ===
Removes a single list item by its integer value.

=== RemoveActiveList(metaProperty) ===
Removes the entire list for the given MetaProperty.

=== GetActiveLists() ===
Returns all ActiveLists defined on the instance as '''UbikActiveList''' objects, each containing the MetaProperty name and its list items.

= Who-Bert Example =
The following Who-Bert snippet demonstrates how to work with an ActiveList for a MetaProperty named "'''MP_INT_A'''":

<syntaxhighlight lang="csharp">
using System;
using System.Windows.Forms;
using System.Linq;
using System.Collections.Generic;
using UBIK.Kernel;
using UBIK.Runtime;
using UBIK.Runtime.Sys;
using UBIK.Compiler;
using UBIK.Content;

namespace Studio
{
public class ObjectTest
{
public void TestObject(params BaseClass\[] InVariables)
{
Debugger.Output(this, "\*\*\* Started ActiveList Example");
foreach (BaseClass obj in InVariables)
{
ContentClass c = obj as ContentClass;

var labels1 = new Dictionary<string, string> { { "en", "One" }, { "de", "Eins" } };
var labels2 = new Dictionary<string, string> { { "en", "Two" }, { "de", "Zwei" } };
var labels3 = new Dictionary<string, string> { { "en", "Three" }, { "de", "Drei" } };

// Add items
c.AddOrUpdateActiveList("MP_INT_A", 1, labels1);
c.AddOrUpdateActiveList("MP_INT_A", 2, labels2);
c.AddOrUpdateActiveList("MP_INT_A", 3, labels3);

// Update labels and move item 3 to index 0
var labels3Updated = new Dictionary<string, string> { { "en", "Three Updated" }, { "de", "Drei Aktualisiert" } };
c.AddOrUpdateActiveList("MP_INT_A", 3, labels3Updated, 0);

// Sort items: 2, 1, 3
c.SortActiveList("MP_INT_A", new int[] { 2, 1, 3 });

// Remove item 1
c.RemoveActiveListItem("MP_INT_A", 1);

c.Save();
}
Debugger.Output(this, "*** Finished ActiveList Example");
}
}
} </syntaxhighlight>

= Further Notes =

* ActiveLists are designed for lightweight, instance-specific value lists that can be updated without ACM rebuilds.
* They are ideal for use cases where list content varies between instances of the same MetaClass.
* When both an ActiveList and a SelectiveList are defined for the same MetaProperty, the SelectiveList overrides the ActiveList on the client.

MROCLS PICK LIST TASK

2025-07-15T07:18:39Z

LMA: Created page with "{{ClassificationInfoBox | title = Pick list classification object | name = {{PAGENAMEE}} | inheritance = MROCLS_MRO_TASK | namespace = MRO.Classification | purpose = Clas..."

{{ClassificationInfoBox
| title = Pick list classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as pick list tasks
| version = 5.0.0
| id = {AC61934E-DDFD-4FAE-A28F-2F19EE70E0EE}
}}

Classifies an object as a Pick List Task.
A Pick List Task needs a predefined List to pick from for its value property. The task counts as finished as soon as a list item has been selected. Each List item needs an integer value assigned to it. The value 0 is reserved for the server since it is used to provide a reopening functionality for the task.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Integer}} || Selected item (Undefined = 0)
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS PICK LIST TASK]]
[[Category:Plugin|MROCLS PICK LIST TASK]]

MROCLS CALCULATION TASK

2025-07-15T07:07:22Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Calculation classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as calculation tasks
| version = 5.0.0
| id = {7A23F6C1-11B4-48A1-AB98-374E01C727BA}
}}

Classifies an object as a Calculation Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Calculation Task needs a predefined condition/expression, which can be evaluated by the client, to determine a result. The Task also needs a target property name and target property type to be able to write the result to the owner.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| EXPRESSION || {{String}} || Condition that will be evaluated by the client
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_PROPERTY_NAME || {{String}} || Name of Target Property
|-
| TARGET_PROPERTY_TYPE || {{Integer}} || Type of Target Property (Undefined = 0, Bool = 1, Int = 3, Double = 4)
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_PICK_LIST_TASK#Pick List Task]] (Classification)

[[Category:Classifications|MROCLS CALCULATION TASK]]
[[Category:Injecting|MROCLS CALCULATION TASK]]

Version 5.0.0 (Server)

2025-07-02T07:40:39Z

LMA: /* Features */

= Kernel (initial release)=
== Features ==
* String MetaProperties marked as multilingual are now automatically classified as multilingual.

== Bug Fixes ==
*

== Enhancements ==
*

== Known Issues ==
*

MRO (Plugin)

2025-06-24T08:21:55Z

LMA: /* Calculation 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 implement necessary classifications.

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

=== Check Task ===
A [[MRO_Implemented_Objects|Check Task]] allows the user to check the task as completed or Not Applicable.

=== 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 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 ==
* [[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_START_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

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

MRO Implemented Objects

2025-06-24T08:20:48Z

LMA: /* Calculation Task */

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

== Workpackage ==

=== Procedure Workpackage ===
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

== Task ==

=== Switch Start Task ===
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

=== Check Task ===
MetaClass Name: CHECK_TASK | Metaclass UID: A360287D-2979-4D91-8B1A-6086FC1BEDA1 
MetaClass Name: CUSTOM_CHECK_TASK | Metaclass UID: DF61A1DB-5238-4A87-85A6-B9C09B54B242

A Check Task confirms task completion. The task is complete once a value is selected (including Not Applicable). 

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

=== Numeric Task ===
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215 
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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 
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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 
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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 
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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 
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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 
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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 
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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 
MetaClass Name: CUSTOM_CALCULATION_TASK | Metaclass UID: e2b24a28-2382-46d2-8f4b-5f52168a9e27

Currently under development.

Extra Classifications: [[MROCLS_CALCULATION_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
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_PROPERTY_NAME || {{String}} || Name of Target Property (on owner)
|-
| TARGET_PROPERTY_TYPE || {{Integer}} || Type of Target Property (Undefined = 0, Bool = 1, Int = 3, Double = 4)
|}

[[Category:Plugin|MRO Implemented Objects]]

=== Signature Task ===
MetaClass Name: SIGNATURE_TASK | Metaclass UID: 66D6A529-E233-4CE2-9E11-B65984D5B0DA 
MetaClass Name: CUSTOM_SIGNATURE_TASK | Metaclass UID: ECE1E20F-2BA3-4BC4-A0DD-9AFFDBB23790

A Signature Task captures a sign-off action to confirm the completion of a procedure. The task is complete once a written signature is provided. 

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

== Procedure Tasks ==
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_CHECK_TASK | MetaClass UID: 63D68EA4-E78C-4A33-A35A-301A01A2568E 
MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa 
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81 
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c 
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f 
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c 
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5 
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c 
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5 
MetaClass Name: PROCEDURE_SIGNATURE_TASK | Metaclass UID: 202CDB9D-BEEB-4E5A-A333-5235A9E6FF94 

== File Documents ==

=== JSON File Document ===
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

=== Picture Task File document ===
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

== 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)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Plugin|MRO Implemented Objects]]

MROCLS CALCULATION TASK

2025-06-24T08:18:19Z

LMA:

{{ClassificationInfoBox
| title = Calculation classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as calculation tasks
| version = 5.0.0
| id = {7A23F6C1-11B4-48A1-AB98-374E01C727BA}
}}

Classifies an object as a Calculation Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Calculation Task needs a predefined condition/expression, which can be evaluated by the client, to determine a result. The Task also needs a target property name and target property type to be able to write the result to the owner.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| EXPRESSION || {{String}} || Condition that will be evaluated by the client
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_PROPERTY_NAME || {{String}} || Name of Target Property
|-
| TARGET_PROPERTY_TYPE || {{Integer}} || Type of Target Property (Undefined = 0, Bool = 1, Int = 3, Double = 4)
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)

[[Category:Classifications|MROCLS CALCULATION TASK]]
[[Category:Injecting|MROCLS CALCULATION TASK]]

MROCLS CALCULATION TASK

2025-06-24T07:55:03Z

LMA: /* MetaProperties */

{{ClassificationInfoBox
| title = Calculation classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as calculation tasks
| version = 5.0.0
| id = {7A23F6C1-11B4-48A1-AB98-374E01C727BA}
}}

Classifies an object as a Calculation Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Calculation Task needs a predefined condition/expression, which can be evaluated by the client, to determine a result. The Task also can have a predefined target expression that contains the instruction that defines what should happen with the result of the evaluated expression.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| EXPRESSION || {{String}} || Condition that will be evaluated by the client
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_PROPERTY_NAME || {{String}} || Name of Target Property
|-
| TARGET_PROPERTY_TYPE || {{Integer}} || Type of Target Property (Undefined = 0, Bool = 1, Int = 3, Double = 4)
|}

[[Category:Classifications|MROCLS CALCULATION TASK]]
[[Category:Injecting|MROCLS CALCULATION TASK]]

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)

[[Category:Classifications|MROCLS CALCULATION TASK]]
[[Category:Injecting|MROCLS CALCULATION TASK]]

MRO Implemented Objects

2025-06-23T14:41:45Z

LMA: /* Calculation Task */

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

== Workpackage ==

=== Procedure Workpackage ===
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

== Task ==

=== Switch Start Task ===
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

=== Check Task ===
MetaClass Name: CHECK_TASK | Metaclass UID: A360287D-2979-4D91-8B1A-6086FC1BEDA1 
MetaClass Name: CUSTOM_CHECK_TASK | Metaclass UID: DF61A1DB-5238-4A87-85A6-B9C09B54B242

A Check Task confirms task completion. The task is complete once a value is selected (including Not Applicable). 

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

=== Numeric Task ===
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215 
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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 
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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 
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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 
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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 
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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 
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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 
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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 
MetaClass Name: CUSTOM_CALCULATION_TASK | Metaclass UID: e2b24a28-2382-46d2-8f4b-5f52168a9e27

Currently under development.

Extra Classifications: [[MROCLS_CALCULATION_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
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_EXPRESSION || {{String}} || Instruction for applying the result
|-
| TARGET_TYPE || {{Integer}} || Type of Target Property
|}

[[Category:Plugin|MRO Implemented Objects]]

=== Signature Task ===
MetaClass Name: SIGNATURE_TASK | Metaclass UID: 66D6A529-E233-4CE2-9E11-B65984D5B0DA 
MetaClass Name: CUSTOM_SIGNATURE_TASK | Metaclass UID: ECE1E20F-2BA3-4BC4-A0DD-9AFFDBB23790

A Signature Task captures a sign-off action to confirm the completion of a procedure. The task is complete once a written signature is provided. 

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

== Procedure Tasks ==
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_CHECK_TASK | MetaClass UID: 63D68EA4-E78C-4A33-A35A-301A01A2568E 
MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa 
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81 
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c 
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f 
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c 
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5 
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c 
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5 
MetaClass Name: PROCEDURE_SIGNATURE_TASK | Metaclass UID: 202CDB9D-BEEB-4E5A-A333-5235A9E6FF94 

== File Documents ==

=== JSON File Document ===
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

=== Picture Task File document ===
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

== 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)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Plugin|MRO Implemented Objects]]

MRO (Plugin)

2025-06-23T14:39:20Z

LMA: /* Calculation 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 implement necessary classifications.

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

=== Check Task ===
A [[MRO_Implemented_Objects|Check Task]] allows the user to check the task as completed or Not Applicable.

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

[[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 ==
* [[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_START_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

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

MRO Implemented Objects

2025-06-23T14:35:15Z

LMA: /* See also */

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

== Workpackage ==

=== Procedure Workpackage ===
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

== Task ==

=== Switch Start Task ===
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

=== Check Task ===
MetaClass Name: CHECK_TASK | Metaclass UID: A360287D-2979-4D91-8B1A-6086FC1BEDA1 
MetaClass Name: CUSTOM_CHECK_TASK | Metaclass UID: DF61A1DB-5238-4A87-85A6-B9C09B54B242

A Check Task confirms task completion. The task is complete once a value is selected (including Not Applicable). 

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

=== Numeric Task ===
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215 
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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 
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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 
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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 
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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 
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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 
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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 
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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 
MetaClass Name: CUSTOM_CALCULATION_TASK | Metaclass UID: e2b24a28-2382-46d2-8f4b-5f52168a9e27

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
|}

=== Signature Task ===
MetaClass Name: SIGNATURE_TASK | Metaclass UID: 66D6A529-E233-4CE2-9E11-B65984D5B0DA 
MetaClass Name: CUSTOM_SIGNATURE_TASK | Metaclass UID: ECE1E20F-2BA3-4BC4-A0DD-9AFFDBB23790

A Signature Task captures a sign-off action to confirm the completion of a procedure. The task is complete once a written signature is provided. 

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

== Procedure Tasks ==
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_CHECK_TASK | MetaClass UID: 63D68EA4-E78C-4A33-A35A-301A01A2568E 
MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa 
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81 
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c 
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f 
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c 
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5 
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c 
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5 
MetaClass Name: PROCEDURE_SIGNATURE_TASK | Metaclass UID: 202CDB9D-BEEB-4E5A-A333-5235A9E6FF94 

== File Documents ==

=== JSON File Document ===
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

=== Picture Task File document ===
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

== 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)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Plugin|MRO Implemented Objects]]

MROCLS PROCEDURE

2025-06-23T14:34:34Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Procedure Workpackage classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_WORKPACKAGE]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as task owners for sequential tasks
| version = 5.0.0+
| id = {DDA685D6-EDDB-4746-BFF6-E8E8F153F11B}
}}
An {{UBIK}} Procedure Workpackage is a specialized form of a [[MRO_Objects_(Client)#Work_Package|Workpackage]] designed to handle complex workflows. It consists of sequential tasks that may include nested procedures and branching logic. Switch tasks allow the workflow to follow different paths based on conditions or user input. This makes Procedure Workpackages suitable for advanced scenarios requiring modularization and dynamic process control.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''ISTEMPLATE'' || {{Boolean}}|| Defines whether the procedure is a template
|-
| ''JSON'' || {{String}}|| Store the Procedure Model
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

MRO (Plugin)

2025-06-23T14:34:27Z

LMA: /* See also */

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 implement necessary classifications.

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

=== Check Task ===
A [[MRO_Implemented_Objects|Check Task]] allows the user to check the task as completed or Not Applicable.

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

=== 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 ==
* [[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_START_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

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

MRO Objects (Client)

2025-06-23T14:34:06Z

LMA: /* See also */

[[File:UI_WinX_MRO_ChildList.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]
[[File:Android_mro_ui.jpg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.

== Basic User Interface ==
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators 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 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.

<gallery>
File:UI_WinX_MRO_TechnicalStatusIndicator.png|thumb|Technical Status Indicator (WinX)
File:Android_tech_status.PNG|thumb|Technical Status Indicator (Android)
</gallery>

=== 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 a work package to be already confirmed or show tasks that are already locked by their owning workpackage.
<gallery>
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)
File:UI_WinX_MRO_WPConfirmedIndicator.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)
File:Android_orga_status.PNG|Organisational Status Indicator (Android)
File:Android_orga_status_finished.PNG|MRO Workpackage Confirmed Indicator (Android)
</gallery>

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

<gallery>
File:UI_WinX_MRO_WorkProgressIndicator.png|thumb|MRO Work Progress Indicator (WinX)
File:Android_finished_overlay.PNG|thumb|MRO Work Progress Indicator (Android). The finished overlay is shown once the progress of a MRO object is 100%
</gallery>

{{Clear}}

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

<gallery>
File:UI_WinX_MRO_WPConfirmButton.png|MRO Workpackage confirm button (WinX)
File:UI_WinX_MRO_WPRevokeConfirmButton.png|MRO Workpackage revoke confirmation button (WinX)
File:Android_finish_workpackage.PNG|MRO Workpackage confirm button (Android)
File:Android reopen workpackage.PNG|MRO Workpackage revoke confirmation button (Android)
</gallery>

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

On both clients, a Task can be reverted by clicking twice on the Not Applicable button.

{{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). Therefore, clicking the value on the shown task opens an editor to enter the desired value. 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.
{{Clear}}

<gallery widths=497px heights=69px>
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)
</gallery>

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

There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}
{{Clear}}

<gallery widths=497px heights=69px>
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)
</gallery>

==== Check Task ====

A [[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.
{{Clear}}

<gallery widths=497px heights=69px>
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)
</gallery>

==== Inspection Task ====

[[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).
{{Clear}}

<gallery widths=497px heights=69px>
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)
</gallery>

==== Sequential Task ====
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.

A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.

The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.
The state of each sequential task is evaluated the following way:

# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.
# Check if the task has any predecessors.
# Try to load each predecessor task.
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.

The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.

'''Example'''

As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.

==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====
Sometimes, not all tasks have to be finished. More specifically, there might be a predefined condition where you only need to finish a certain number of tasks among a group of them. These are known in {{UBIK}} as [[MROCLS_GROUPEDTASK|grouped tasks]].

The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.

{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}

{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}

{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}

A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.

For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.

==== Supervisor Task {{Version/XamarinSince|4.8}} ====
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.

<gallery widths=300px heights=300px>
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Xamarin)
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Xamarin)
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Xamarin)
</gallery>

A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].

{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}
{{Hint|A setting controls [[RFID_tags#Choose_which_information_to_use_from_a_tag|which information in a scanned tag is used]] during this process.}}

[[Category:Android|MRO Objects (UBIK WinX)]]
[[Category:Client|MRO Objects (Client)]]
[[Category:Pages with broken file links|MRO Objects (Client)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]
[[Category:Xamarin|MRO Objects (Client)]]

=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.
{{Clear}}

== Locking ==
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].

== See also ==
* [[MRO (Plugin)]]
* [[MROCLS_PROJECT]]
* [[MROCLS_PROJECTINFORMATION]]
* [[MROCLS_SEQUENTIALTASK]]
* [[MROCLS_GROUPEDTASK]]
* [[MROCLS_MRO_CHECK_TASK]]
* [[MROCLS_MRO_INSPECTION_TASK]]
* [[MROCLS_MRO_MEASUREMENT_TASK]]
* [[MROCLS_MRO_PROGRESS_TASK]]
* [[MROCLS_MRO_TASK]]
* [[MROCLS_MRO_TASKOWNER]]
* [[MROCLS_MRO_WORKPACKAGE]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Android|MRO Objects (UBIK WinX)]]
[[Category:Client|MRO Objects (Client)]]
[[Category:Pages with broken file links|MRO Objects (Client)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]
[[Category:Xamarin|MRO Objects (Client)]]

MROCLS SWITCH END TASK

2025-06-23T14:33:56Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Switch End Task classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_SEQUENTIALTASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as switch end tasks
| version = 5.0.0
| id = {875090F4-FCF9-4A5D-A978-9ACD1FF2829C}
}}

Classifies an object as a Switch End Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Switch End Task is a sequential task used to close a branching structure initiated by a Switch Task. It marks the point where all branches defined by the Switch Task converge and the unified workflow continues.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| SWITCH_TASK || {{Guid}} || Link to Switch task
|-
| VALUE || {{Boolean}} || Value to mark the task as finished or NA
|}

[[Category:Classifications|MROCLS SWITCH END TASK]]

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS SWITCH END TASK]]

MROCLS SEQUENTIALTASK

2025-06-23T14:33:40Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Sequential Task classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as sequential tasks
| version = 2.6.3+
| id = {AAC6D6F6-7554-4FEF-B3D3-602B69F85B45}
}}

Classifies an object as [[MRO_Objects_(Client)#Sequential_Task|Sequential Task]].
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PREDECESSOR_IDS|| {{Guid}} || List of predecessor Tasks for the given task
|-
| STATE|| {{Integer}} || Sequential task state (Locked, Open, Finished)
|}

== See also ==
{{Category/Version|2.6.3}}
* [[MRO_Objects_(Client)#Sequential_Task]]
* [[MRO_(Plugin)]]
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:2.6.3|MROCLS SEQUENTIALTASK]]
[[Category:Classifications|MROCLS SEQUENTIALTASK]]

MROCLS MRO WORKPACKAGE

2025-06-23T14:33:28Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Workpackage classification
| name = {{PAGENAMEE}}
| inheritance =
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as task owners
| version = 2.5.2+
| id = {716567C4-5C79-4E67-BB9E-4F5678772C43}
}}
An {{UBIK}} [[MRO_Objects_(Client)#Work_Package|Workpackage]] ist an object that can contain children of type MRO Task, Task Owner or Workpackages to determine the work progress by technical and organisational aspect. Workpackages can be confirmed by the user, once the work items inside have been finished. This means in terms of finished work progress as well as confirmed sub-workpackages. Workpackages also represent the technical state of the underlying MRO items to indicate branches containing technical issues.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''WEIGHT'' || {{Double}}|| The weight of the objects progress
|-
| ''TECH_STATUS'' || {{Double}}|| The technical status
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS MRO WORKPACKAGE]]
[[Category:Injecting|MROCLS MRO WORKPACKAGE]]

MROCLS MRO INSPECTION TASK

2025-06-23T14:33:19Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Inspection Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_INSPECTION_TASK#Measurement Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Inspection Tasks
| version = 2.5.2+
| id = {836F4D58-A466-4BB4-8D34-1B056077A431}
}}
An [[MRO_Objects_(Client)#Inspection_Task|Inspection Task]] object is an {{UBIK}} content object which is used to document the inspection that has to be done in a task. The reported value documents the inspection as positive (true) or negative (false). Once an inspection result has been documented, the task is finished.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Boolean}}|| The reported inspection result (inherited from [[MROCLS_MRO_TASK#Task]])
|-
|}

[[Category:Classifications|MROCLS MRO INSPECTION TASK]]
[[Category:Injecting|MROCLS MRO INSPECTION TASK]]

== See also ==
* [[MROCLS_MRO_TASKOWNER#Tas Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK#Progress Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MRO_Objects_(Client)#Inspection_Task]]
* [[MRO_(Plugin)#Inspection_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS MRO INSPECTION TASK]]
[[Category:Injecting|MROCLS MRO INSPECTION TASK]]

MROCLS MRO CHECK TASK

2025-06-23T14:33:12Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Check Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK#Measurement Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Progress Tasks
| version = 2.5.2+
| id = {2F020D90-05D4-42FD-A069-81EF72FC3029}
}}
A [[MRO_Objects_(Client)#Check_Task|Check Task]] object is an {{UBIK}} content object which is used to document work as finished or not finished.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Bool}}|| The reported progress (inherited from [[MROCLS_MRO_TASK#Task]]), whether finished (true) or not (false)
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Tas Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK#Progress Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Check_Task]]
* [[MRO_(Plugin)#Check_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS MRO CHECK TASK]]
[[Category:Injecting|MROCLS MRO CHECK TASK]]

MROCLS MRO PROGRESS TASK

2025-06-23T14:32:45Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Progress Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Progress Tasks
| version = 2.5.2+
| id = {C8A53169-BAD2-436A-AC5D-563DCF15DA61}
}}
A [[MRO_Objects_(Client)#Progress_Task|Progress Task]] object is an {{UBIK}} content object which is used to document work by its progress.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Double}}|| The reported progress (inherited from [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]])
|-
| ''PREVIOUS_VALUE'' || {{Double}}|| The previously reported progress (inherited from [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]])
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Tas Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Progress_Task]]
* [[MRO_(Plugin)#Progress_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS MRO PROGRESS TASK]]
[[Category:Injecting|MROCLS MRO PROGRESS TASK]]

MROCLS CALCULATION TASK

2025-06-23T14:32:35Z

LMA:

{{ClassificationInfoBox
| title = Calculation classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as calculation tasks
| version = 5.0.0
| id = {7A23F6C1-11B4-48A1-AB98-374E01C727BA}
}}

Classifies an object as a Calculation Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Calculation Task needs a predefined condition/expression, which can be evaluated by the client, to determine a result. The Task also can have a predefined target expression that contains the instruction that defines what should happen with the result of the evaluated expression.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| EXPRESSION || {{String}} || Condition that will be evaluated by the client
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_EXPRESSION || {{String}} || Instruction for applying the result
|-
| TARGET_TYPE || {{Integer}} || Type of Target Property
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)

[[Category:Classifications|MROCLS CALCULATION TASK]]
[[Category:Injecting|MROCLS CALCULATION TASK]]

MROCLS MRO MEASUREMENT TASK

2025-06-23T14:32:08Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Measurement Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK#Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Measurement Tasks
| version = 2.5.2+
| id = {94F39932-E08C-4153-A9B8-D3D49788B597}
}}
A [[MRO_Objects_(Client)#Measurement_Task|Measurement Task]] object is a {{UBIK}} content object which is used to document work by a numeric value. As soon as the required value is reported, the task will be finished.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Double}}|| The reported value (inherited from [[MROCLS_MRO_TASK#Task]])
|-
| ''PREVIOUS_VALUE'' || {{Double}}|| The previously reported value
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK# Progress Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Measurement_Task]]
* [[MRO_(Plugin)#Measurement_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS MRO MEASUREMENT TASK]]
[[Category:Injecting|MROCLS MRO MEASUREMENT TASK]]

MROCLS MRO TASK

2025-06-23T14:31:54Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Task classification
| name = {{PAGENAMEE}}
| inheritance = -
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as tasks
| version = 2.5.2+
| id = {671AA34C-B6CA-4B64-8B87-ECAAFB7B9A1C}
}}
A [[MRO_Objects_(Client)#Task|Task]] object is a {{UBIK}} content object which is used to document a working task.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Undefined}}|| A value used to document the task
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (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)
* [[MRO_Objects_(Client)#Task]]
* [[MRO_(Plugin)#Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS MRO TASK]]
[[Category:Injecting|MROCLS MRO TASK]]

MROCLS MRO TASKOWNER

2025-06-23T14:31:42Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Task Owner classification
| name = {{PAGENAMEE}}
| inheritance = SYSCLS_UPDATEONCHILDCHANGED (Version 3+)
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as task owners
| version = 2.5.2+
| id = {d23567bb-f6b2-4b29-bfc4-b13a79640237}
}}
A [[MRO_Objects_(Client)#Task_Owner|Task Owner]] object is a {{UBIK}} content object which owns MRO work relevant children like Tasks, Work Packages or other Task Owner objects.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''PROGRESS'' || {{Double}}|| Overall work progress accumulated from all tasks existing in the branch
|-
| ''ORGA_STATUS'' || {{Double}}|| Overall organisational status
|-
| ''WEIGHT'' || {{Double}}|| The weight of the objects progress
|-
| ''TECH_STATUS'' || {{Double}}|| The technical status
|}

== See also ==
* [[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)
* [[MRO_Objects_(Client)#Task_Owner]]
* [[MRO_(Plugin)#Task_Owner]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

[[Category:Classifications|MROCLS MRO TASKOWNER]]
[[Category:Injecting|MROCLS MRO TASKOWNER]]

MROCLS CALCULATION TASK

2025-06-23T14:27:45Z

LMA: /* MetaProperties */

{{ClassificationInfoBox
| title = Calculation classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as calculation tasks
| version = 5.0.0
| id = {7A23F6C1-11B4-48A1-AB98-374E01C727BA}
}}

Classifies an object as a Calculation Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Calculation Task needs a predefined condition/expression, which can be evaluated by the client, to determine a result. The Task also can have a predefined target expression that contains the instruction that defines what should happen with the result of the evaluated expression.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| EXPRESSION || {{String}} || Condition that will be evaluated by the client
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_EXPRESSION || {{String}} || Instruction for applying the result
|-
| TARGET_TYPE || {{Integer}} || Type of Target Property
|}

[[Category:Classifications|MROCLS CALCULATION TASK]]

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)

[[Category:Classifications|MROCLS CALCULATION TASK]]

MROCLS CALCULATION TASK

2025-06-23T14:27:28Z

LMA: Created page with "{{ClassificationInfoBox | title = Calculation classification object | name = {{PAGENAMEE}} | inheritance = MROCLS_MRO_TASK | namespace = MRO.Classification | purpose = Cl..."

{{ClassificationInfoBox
| title = Calculation classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as calculation tasks
| version = 5.0.0
| id = {7A23F6C1-11B4-48A1-AB98-374E01C727BA}
}}

Classifies an object as a Calculation Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Calculation Task needs a predefined condition/expression, which can be evaluated by the client, to determine a result. The Task also can have a predefined target expression that contains the instruction that defines what should happen with the result of the evaluated expression.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| EXPRESSION || {{String}} || Condition that will be evaluated by the client
|-
| VALUE || {{Integer}} || Evaluation state (Undefined = 0, Ongoing = 10, Finished = 20, Error = 30)
|-
| TARGET_EXPRESSION || {{String}} || Instruction for applying the result
|-
| TARGET_TYPE || {{Int}} || Type of Target Property
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)

[[Category:Classifications|MROCLS CALCULATION TASK]]

MROCLS SEQUENTIALTASK

2025-06-23T14:25:59Z

LMA:

{{ClassificationInfoBox
| title = Sequential Task classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as sequential tasks
| version = 2.6.3+
| id = {AAC6D6F6-7554-4FEF-B3D3-602B69F85B45}
}}

Classifies an object as [[MRO_Objects_(Client)#Sequential_Task|Sequential Task]].
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PREDECESSOR_IDS|| {{Guid}} || List of predecessor Tasks for the given task
|-
| STATE|| {{Integer}} || Sequential task state (Locked, Open, Finished)
|}

== See also ==
{{Category/Version|2.6.3}}
* [[MRO_Objects_(Client)#Sequential_Task]]
* [[MRO_(Plugin)]]
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Start Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:2.6.3|MROCLS SEQUENTIALTASK]]
[[Category:Classifications|MROCLS SEQUENTIALTASK]]

MROCLS SWITCH START TASK

2025-06-23T14:13:40Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Switch Task classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_SEQUENTIALTASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as switch tasks
| version = 5.0.0
| id = {FE4C6189-DD7D-4B42-83C6-7594CCB91D00}
}}

Classifies an object as a Switch Task.
This classification is an [[AutonomousClassification|Autonomous Classification]] where the defined properties are autonomously added to the MetaDefinitions. A Switch Task is a sequential task used within Procedure Workpackages to introduce branching logic. It evaluates a predefined condition/expression, which can be evaluated by the client, to determine which branch of the workflow to execute. Each branch represents a different path of tasks. Every Switch Task must be followed by a Switch End Task, where the two branches merge again and the procedure continues.

== MetaProperties ==
{| 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
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (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_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_SEQUENTIALTASK#Sequential Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)
* [[MRO_Objects_(Client)#Work_Package]]
* [[MRO_(Plugin)#Work_Package]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)

[[Category:Classifications|MROCLS SWITCH TASK]]

MRO Implemented Objects

2025-05-28T13:14:27Z

LMA:

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

=== Workpackage ===

==== Procedure Workpackage ====
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

=== Task ===

==== Switch Start Task ====
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

==== Numeric Task ====
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215 
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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 
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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 
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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 
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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 
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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 
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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 
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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 
MetaClass Name: CUSTOM_CALCULATION_TASK | Metaclass UID: e2b24a28-2382-46d2-8f4b-5f52168a9e27

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
|}

=== Procedure Tasks ===
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa 
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81 
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c 
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f 
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c 
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5 
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c 
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5 

=== File Documents ===

==== JSON File Document ====
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

==== Picture Task File document ====
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

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

MRO Implemented Objects

2025-05-28T13:13:43Z

LMA: /* Procedure Tasks */

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

=== Workpackage ===

==== Procedure Workpackage ====
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

=== Task ===

==== Switch Start Task ====
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

==== Numeric Task ====
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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 
MetaClass Name: CUSTOM_CALCULATION_TASK | Metaclass UID: e2b24a28-2382-46d2-8f4b-5f52168a9e27

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
|}

=== Procedure Tasks ===
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa 
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81 
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c 
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f 
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c 
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5 
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c 
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5 

=== File Documents ===

==== JSON File Document ====
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

==== Picture Task File document ====
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

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

MRO Implemented Objects

2025-05-28T13:12:48Z

LMA: /* Calculation Task */

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

=== Workpackage ===

==== Procedure Workpackage ====
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

=== Task ===

==== Switch Start Task ====
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

==== Numeric Task ====
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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 
MetaClass Name: CUSTOM_CALCULATION_TASK | Metaclass UID: e2b24a28-2382-46d2-8f4b-5f52168a9e27

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
|}

=== Procedure Tasks ===
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5

=== File Documents ===

==== JSON File Document ====
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

==== Picture Task File document ====
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

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

MRO Implemented Objects

2025-05-28T13:10:49Z

LMA: /* Calculation Task */

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

=== Workpackage ===

==== Procedure Workpackage ====
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

=== Task ===

==== Switch Start Task ====
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

==== Numeric Task ====
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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 ====
{| class="wikitable" width=50%
|-
! width=30% | MetaClass Name !! width=20% | Metaclass UID
|-
| CALCULATION_TASK || 3ec9d0f2-9d0f-4c1b-80bd-1efeaf010fa0
|-
| CUSTOM_CALCULATION_TASK || e2b24a28-2382-46d2-8f4b-5f52168a9e27
|}

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
|}

=== Procedure Tasks ===
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5

=== File Documents ===

==== JSON File Document ====
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

==== Picture Task File document ====
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

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

MRO Implemented Objects

2025-05-28T13:07:58Z

LMA:

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. For most tasks, value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

=== Workpackage ===

==== Procedure Workpackage ====
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

=== Task ===

==== Switch Start Task ====
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

==== Numeric Task ====
MetaClass Name: NUMERIC_TASK | MetaClass UID: b1789da3-bd67-4f93-b14b-22fd41afb215
MetaClass Name: CUSTOM_NUMERIC_TASK | MetaClass UID: 047d05f3-a876-4f9d-a40e-2a098e9ba49b

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
MetaClass Name: CUSTOM_INSPECTION_TASK | MetaClass UID: a0123b54-ddcf-49be-8c66-7ca86c4c5277

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
MetaClass Name: CUSTOM_TEXT_TASK | MetaClass UID: c0a95da8-8e32-4036-8db4-ef438deb14de

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
MetaClass Name: CUSTOM_PICTURE_TASK | MetaClass UID: e58c6957-ecb2-4e3f-a4b7-6953b917d7d4

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
MetaClass Name: CUSTOM_DYNAMIC_LIST_TASK | MetaClass UID: 83551c77-554e-4715-b327-16f0a6ee196a

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
MetaClass Name: CUSTOM_SUPERVISOR_CHECK_TASK | MetaClass UID: 1e4a5506-0c6f-4447-bd0a-d5c87282a0e9

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
MetaClass Name: CUSTOM_INTERFACE_TASK | MetaClass UID: e437ef02-d49b-4f23-9ab8-9a9836366c3d

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
MetaClass Name: CUSTOM_CALCULATION_TASK | Metaclass UID: e2b24a28-2382-46d2-8f4b-5f52168a9e27

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
|}

=== Procedure Tasks ===
The following tasks are specialized versions intended for use within procedures. They implement both the [[MROCLS_SEQUENTIALTASK]] and [[MROCLS_GROUPEDTASK]] classifications.

MetaClass Name: PROCEDURE_NUMERIC_TASK | MetaClass UID: f578f50b-eecd-4734-929b-43e1f1f246fa
MetaClass Name: PROCEDURE_INSPECTION_TASK | MetaClass UID: 9369b841-c5bf-43df-909f-3a5063763f81
MetaClass Name: PROCEDURE_TEXT_TASK | MetaClass UID: 4dd8fee2-9d3e-4fa1-9a61-d580f5d4201c
MetaClass Name: PROCEDURE_PICTURE_TASK | MetaClass UID: 4c0db9da-dfcc-48ad-9d89-6c958a5ac39f
MetaClass Name: PROCEDURE_DYNAMIC_LIST_TASK | MetaClass UID: 241a2248-36f6-44ab-9c8d-0357b7cbe24c
MetaClass Name: PROCEDURE_SUPERVISOR_CHECK_TASK | MetaClass UID: 9bb8e1b1-04f8-46f0-a9c9-0bb2960a49e5
MetaClass Name: PROCEDURE_INTERFACE_TASK | MetaClass UID: 8d9ff119-510b-425c-b917-f72783e4570c
MetaClass Name: PROCEDURE_CALCULATION_TASK | Metaclass UID: ed31735c-c807-40e9-b9a4-254e77445dd5

=== File Documents ===

==== JSON File Document ====
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

==== Picture Task File document ====
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

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

MRO Implemented Objects

2025-05-26T09:40:54Z

LMA:

MRO Implemented Objects are pre-configured standard MRO objects enhanced with additional logic and features. All tasks implement [[MROCLS_MRO_TASK#Task]] and [[MROCLS SEQUENTIALTASK]] classification. All tasks except the switch tasks (start/end) also implement the [[MROCLS_GROUPEDTASK]] classification. Value properties are pre-set, and many of them also implement additional MRO-relevant classifications.

=== Workpackage ===

==== Procedure Workpackage ====
MetaClass Name: PROCEDURE_WORKPACKAGE | MetaClass UID: 007c78f8-fafd-4bde-8add-e11990625e7a

A Procedure Workpackage serves as a container for tasks and other procedures. It stores its entire structure in a JSON format, which is predefined using a workflow editor. When a specific state is triggered, the corresponding sub-tasks and procedures are created or updated accordingly.

Extra Classifications: [[MROCLS_PROCEDURE]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| PROCEDURE_STATUS || {{Integer}} || Represents the current state: Draft = 10, ReadyToUse = 20, Published = 30, Open = 40, Executing = 50, Completed = 60, Approved = 70, Rejected = 80
|-
| JSON || {{String}} || JSON representation of the procedure
|-
| ISTEMPLATE || {{Boolean}} || Indicates whether the procedure is a template
|}

=== Task ===

==== Switch Start Task ====
MetaClass Name: SWITCH_START_TASK | MetaClass UID: 3c3614e2-635f-4e07-b02a-a72c81b9e328

A Switch Start Task confirms task completion by the system after an expression calculation. The task is automatically marked as complete once the calculation finishes successfully. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_START_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| 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: SWITCH_END_TASK | MetaClass UID: 261a3e63-2b8e-4f3e-ab22-295bbe421e7a

A Switch End Task confirms task completion by the system. The task is invisible to the user and is always automatically marked as complete. No user input is required. 

Extra Classifications: [[MROCLS_SWITCH_END_TASK]] 
Implemented Properties:
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| VALUE || {{Boolean}} || Task completion
|-
| LK_SWITCH_START_TASK || {{Guid}} || Link to Switch task
|}

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

=== File Documents ===

==== JSON File Document ====
MetaClass Name: FILEDOCUMENT_MRO_JSON | MetaClass UID: 016e57d5-37b3-42e0-a753-f675d4cbf338

File Document for JSON file of a Procedure Workpackage.

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

==== Picture Task File document ====
MetaClass Name: FILEDOCUMENT_MRO_PICTURE_TASK | MetaClass UID: 2488fd79-4729-4090-9587-82103a9869e0

File Document for image files of a Picture Task.

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

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

MRO (Plugin)

2025-05-14T06:09:44Z

LMA:

MRO (Plugin)

2025-05-14T06:01:31Z

LMA: /* See also */

MROCLS GROUPEDTASK

2025-05-14T06:01:07Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Grouped Task classification object
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK]]
| namespace = MRO.Classification
| purpose = Classify tasks as grouped tasks
| version = 3.7.1+
| id = {4130333A-93A2-4F35-AFBC-B4AB7AC7856E}
}}

Sometimes, not all tasks of one work package have to be finished. More specifically, there might be a predefined condition where you only need to finish a certain number of tasks among a group of them. These are known in UBIK® as [[MRO_Objects_(Client)#Grouped_Task|Grouped Tasks]].

The Grouped Task classification classifies an object as Grouped Task.

This Grouped Task classification is an [[AutonomousClassification|Autonomous Classification]] where some of the required properties are autonomously added to the MetaDefinitions (ACM).

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| SIBLING_IDS|| {{Guid}} || List of sibling Grouped Tasks. This property is autonomous. It must not be added to the Task - Metaclass. It is managed by the MRO Kernel.
|-
| NOT_NECESSARY|| {{Boolean}} || Identifies a Grouped Task as Not Necessary as its siblings tasks are already finished. This Property is NOT autonomous. It is necessary to add it to the Task MetaClass.
|-
| GROUP_LIMIT|| {{Integer}} || Defines the number of Grouped Tasks that must be finished until its siblings tasks are considered as "Not Necessary". This Property is NOT autonomous. It is necessary to add it to the Task MetaClass.
|}

== Interface and Custom Code ==

The MRO Grouped Task Classification necessitates knowledge about all the tasks in a group. From the point of view of one task, we can call the other tasks "siblings". These siblings are all other tasks that are in the same group as the current one.

As an engineer, you are free to choose how these siblings are evaluated, but we have to tell UBIK about the result.
Therefore, the classification requires an implementation of the following method:

<syntaxhighlight lang="csharp">
public IEnumerable<UBIK.MRO.IGroupedTask> Siblings();
</syntaxhighlight>

It can be added in the respective MetaClass's custom code using UBIK.Studio's Code Editor.

== See also ==
* [[MRO_Objects_(Client)#Grouped_Task]]
* [[MRO_(Plugin)]]
* [[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_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Classifications|M]]

MRO Objects (Client)

2025-05-14T06:00:50Z

LMA: /* See also */

[[File:UI_WinX_MRO_ChildList.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]
[[File:Android_mro_ui.jpg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.

== Basic User Interface ==
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators 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 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.

<gallery>
File:UI_WinX_MRO_TechnicalStatusIndicator.png|thumb|Technical Status Indicator (WinX)
File:Android_tech_status.PNG|thumb|Technical Status Indicator (Android)
</gallery>

=== 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 a work package to be already confirmed or show tasks that are already locked by their owning workpackage.
<gallery>
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)
File:UI_WinX_MRO_WPConfirmedIndicator.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)
File:Android_orga_status.PNG|Organisational Status Indicator (Android)
File:Android_orga_status_finished.PNG|MRO Workpackage Confirmed Indicator (Android)
</gallery>

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

<gallery>
File:UI_WinX_MRO_WorkProgressIndicator.png|thumb|MRO Work Progress Indicator (WinX)
File:Android_finished_overlay.PNG|thumb|MRO Work Progress Indicator (Android). The finished overlay is shown once the progress of a MRO object is 100%
</gallery>

{{Clear}}

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

<gallery>
File:UI_WinX_MRO_WPConfirmButton.png|MRO Workpackage confirm button (WinX)
File:UI_WinX_MRO_WPRevokeConfirmButton.png|MRO Workpackage revoke confirmation button (WinX)
File:Android_finish_workpackage.PNG|MRO Workpackage confirm button (Android)
File:Android reopen workpackage.PNG|MRO Workpackage revoke confirmation button (Android)
</gallery>

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

On both clients, a Task can be reverted by clicking twice on the Not Applicable button.

{{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). Therefore, clicking the value on the shown task opens an editor to enter the desired value. 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.
{{Clear}}

<gallery widths=497px heights=69px>
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)
</gallery>

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

There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}
{{Clear}}

<gallery widths=497px heights=69px>
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)
</gallery>

==== Check Task ====

A [[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.
{{Clear}}

<gallery widths=497px heights=69px>
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)
</gallery>

==== Inspection Task ====

[[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).
{{Clear}}

<gallery widths=497px heights=69px>
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)
</gallery>

==== Sequential Task ====
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.

A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.

The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.
The state of each sequential task is evaluated the following way:

# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.
# Check if the task has any predecessors.
# Try to load each predecessor task.
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.

The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.

'''Example'''

As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.

==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====
Sometimes, not all tasks have to be finished. More specifically, there might be a predefined condition where you only need to finish a certain number of tasks among a group of them. These are known in {{UBIK}} as [[MROCLS_GROUPEDTASK|grouped tasks]].

The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.

{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}

{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}

{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}

A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.

For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.

==== Supervisor Task {{Version/XamarinSince|4.8}} ====
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.

<gallery widths=300px heights=300px>
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Xamarin)
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Xamarin)
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Xamarin)
</gallery>

A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].

{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}

[[Category:Android|MRO Objects (UBIK WinX)]]
[[Category:Client|MRO Objects (Client)]]
[[Category:Pages with broken file links|MRO Objects (Client)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]
[[Category:Xamarin|MRO Objects (Client)]]

=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.
{{Clear}}

== Locking ==
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].

== See also ==
* [[MRO (Plugin)]]
* [[MROCLS_PROJECT]]
* [[MROCLS_PROJECTINFORMATION]]
* [[MROCLS_SEQUENTIALTASK]]
* [[MROCLS_GROUPEDTASK]]
* [[MROCLS_MRO_CHECK_TASK]]
* [[MROCLS_MRO_INSPECTION_TASK]]
* [[MROCLS_MRO_MEASUREMENT_TASK]]
* [[MROCLS_MRO_PROGRESS_TASK]]
* [[MROCLS_MRO_TASK]]
* [[MROCLS_MRO_TASKOWNER]]
* [[MROCLS_MRO_WORKPACKAGE]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Android|MRO Objects (UBIK WinX)]]
[[Category:Client|MRO Objects (Client)]]
[[Category:Pages with broken file links|MRO Objects (Client)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]
[[Category:Xamarin|MRO Objects (Client)]]

MROCLS MRO CHECK TASK

2025-05-14T06:00:36Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Check Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK#Measurement Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Progress Tasks
| version = 2.5.2+
| id = {2F020D90-05D4-42FD-A069-81EF72FC3029}
}}
A [[MRO_Objects_(Client)#Check_Task|Check Task]] object is an {{UBIK}} content object which is used to document work as finished or not finished.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Bool}}|| The reported progress (inherited from [[MROCLS_MRO_TASK#Task]]), whether finished (true) or not (false)
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Tas Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK#Progress Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Check_Task]]
* [[MRO_(Plugin)#Check_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Classifications|MROCLS MRO CHECK TASK]]
[[Category:Injecting|MROCLS MRO CHECK TASK]]

MROCLS MRO PROGRESS TASK

2025-05-14T06:00:20Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Progress Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Progress Tasks
| version = 2.5.2+
| id = {C8A53169-BAD2-436A-AC5D-563DCF15DA61}
}}
A [[MRO_Objects_(Client)#Progress_Task|Progress Task]] object is an {{UBIK}} content object which is used to document work by its progress.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Double}}|| The reported progress (inherited from [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]])
|-
| ''PREVIOUS_VALUE'' || {{Double}}|| The previously reported progress (inherited from [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]])
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Tas Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Progress_Task]]
* [[MRO_(Plugin)#Progress_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Classifications|MROCLS MRO PROGRESS TASK]]
[[Category:Injecting|MROCLS MRO PROGRESS TASK]]

MROCLS MRO MEASUREMENT TASK

2025-05-14T06:00:10Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Measurement Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK#Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Measurement Tasks
| version = 2.5.2+
| id = {94F39932-E08C-4153-A9B8-D3D49788B597}
}}
A [[MRO_Objects_(Client)#Measurement_Task|Measurement Task]] object is a {{UBIK}} content object which is used to document work by a numeric value. As soon as the required value is reported, the task will be finished.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Double}}|| The reported value (inherited from [[MROCLS_MRO_TASK#Task]])
|-
| ''PREVIOUS_VALUE'' || {{Double}}|| The previously reported value
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK# Progress Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Measurement_Task]]
* [[MRO_(Plugin)#Measurement_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Classifications|MROCLS MRO MEASUREMENT TASK]]
[[Category:Injecting|MROCLS MRO MEASUREMENT TASK]]

MROCLS MRO TASK

2025-05-14T05:59:53Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Task classification
| name = {{PAGENAMEE}}
| inheritance = -
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as tasks
| version = 2.5.2+
| id = {671AA34C-B6CA-4B64-8B87-ECAAFB7B9A1C}
}}
A [[MRO_Objects_(Client)#Task|Task]] object is a {{UBIK}} content object which is used to document a working task.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Undefined}}|| A value used to document the task
|-
|}

== See also ==
* [[MROCLS_MRO_TASKOWNER#Task Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (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)
* [[MRO_Objects_(Client)#Task]]
* [[MRO_(Plugin)#Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Classifications|MROCLS MRO TASK]]
[[Category:Injecting|MROCLS MRO TASK]]

MROCLS MRO TASKOWNER

2025-05-14T05:59:39Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Task Owner classification
| name = {{PAGENAMEE}}
| inheritance = SYSCLS_UPDATEONCHILDCHANGED (Version 3+)
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as task owners
| version = 2.5.2+
| id = {d23567bb-f6b2-4b29-bfc4-b13a79640237}
}}
A [[MRO_Objects_(Client)#Task_Owner|Task Owner]] object is a {{UBIK}} content object which owns MRO work relevant children like Tasks, Work Packages or other Task Owner objects.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''PROGRESS'' || {{Double}}|| Overall work progress accumulated from all tasks existing in the branch
|-
| ''ORGA_STATUS'' || {{Double}}|| Overall organisational status
|-
| ''WEIGHT'' || {{Double}}|| The weight of the objects progress
|-
| ''TECH_STATUS'' || {{Double}}|| The technical status
|}

== See also ==
* [[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)
* [[MRO_Objects_(Client)#Task_Owner]]
* [[MRO_(Plugin)#Task_Owner]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Classifications|MROCLS MRO TASKOWNER]]
[[Category:Injecting|MROCLS MRO TASKOWNER]]

MROCLS MRO INSPECTION TASK

2025-05-14T05:59:29Z

LMA: /* See also */

{{ClassificationInfoBox
| title = Inspection Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_INSPECTION_TASK#Measurement Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Inspection Tasks
| version = 2.5.2+
| id = {836F4D58-A466-4BB4-8D34-1B056077A431}
}}
An [[MRO_Objects_(Client)#Inspection_Task|Inspection Task]] object is an {{UBIK}} content object which is used to document the inspection that has to be done in a task. The reported value documents the inspection as positive (true) or negative (false). Once an inspection result has been documented, the task is finished.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Boolean}}|| The reported inspection result (inherited from [[MROCLS_MRO_TASK#Task]])
|-
|}

[[Category:Classifications|MROCLS MRO INSPECTION TASK]]
[[Category:Injecting|MROCLS MRO INSPECTION TASK]]

== See also ==
* [[MROCLS_MRO_TASKOWNER#Tas Owner]] (Classification)
* [[MROCLS_MRO_WORKPACKAGE#Work Package]] (Classification)
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_PROGRESS_TASK#Progress Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MRO_Objects_(Client)#Inspection_Task]]
* [[MRO_(Plugin)#Inspection_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)

[[Category:Classifications|MROCLS MRO INSPECTION TASK]]
[[Category:Injecting|MROCLS MRO INSPECTION TASK]]