MROCLS MRO SUPERVISOR TASK

MRO Supervisor Task Classification Object
Name	MROCLS_MRO_SUPERVISOR_TASK
Inheritance	MROCLS_MRO_TASK
Namespace	System.MRO
ID	{C63511FA-4852-4FE7-B5BC-4247136B8B8E}
Purpose	Classify a task as a Supervisor Task to let only Supervisors approve this task.
Version	4.8.1+

If a task object is classified as Supervisor Task, it will mark a task as supervisor - task. This means, that this task may only be edited by a supervisor who has to identify himself using a RFID token and a PIN based verification. This task fullfills the requirements of a device based/shared 4-eyes acceptance workflow.

"This section provides detailed instructions for configuring and using Supervisor Tasks in UBIK."

Overview

The MROCLS_MRO_SUPERVISOR_TASK classification enables tasks that require elevated privileges to be completed by a designated supervisor. This feature is part of the MRO Supervisor Task functionality in UBIK and becomes available once the MRO Plugin is applied to the database.

Supervisor tasks enforce controlled execution of critical steps in a workpackage, ensuring that only authorized personnel can complete them using RFID and PIN verification.

Prerequisites

• MRO Plugin must be applied to the target database.
• A SUPERVISOR object must be created or configured.
• A custom MetaClass must implement both:
  • MROCLS_MRO_TASK
  • MROCLS_MRO_SUPERVISOR_TASK

SUPERVISOR Object Details

The SUPERVISOR MetaClass is derived from LOGIN and automatically implements MROCLS_MRO_SUPERVISOR. It includes the following MetaProperties:

• RFIDTAG (string): RFID code assigned to the supervisor’s card.
• PIN_HASH (string): Unlocking code required after RFID scan.
• PERMISSION (string): Semicolon-separated list of permission keywords (e.g., WELDING;INSPECTION;APPROVAL).

You can locate the default SUPERVISOR object using UID: 2938671d-4578-414f-9c44-8f37a7d0f689.

Task Configuration Steps

1. Apply the MRO Plugin to the database.
2. Create or configure a SUPERVISOR object:
   1. Set RFIDTAG, PIN_HASH, and PERMISSION.
3. Create a custom MetaClass implementing both required classifications.
4. Add MetaProperties:
   1. SUPERVISOR (Guid): Reference to a SUPERVISOR object.
   2. PERMISSION (string): Required permissions for the task.
5. Define permissions for each task using the PERMISSION field.
6. Deploy and test using a tablet and RFID device.

Permission Matching Logic

To authorize a supervisor:

• The system compares the task’s required permissions with the supervisor’s.
• All required keywords must be present in the supervisor’s PERMISSION string.
• Matching is done via simple string comparison.

RFID Setup

• The RFID card must match the RFIDTAG of a SUPERVISOR object.
• It does not need to match anything in the task itself.

Typical Workflow

1. Subordinate executes a workpackage.
2. Upon reaching a Supervisor Task, they locate a supervisor.
3. Supervisor scans their RFID card.
4. If permissions match, they enter their PIN_HASH.
5. If permissions do not match, access is denied.
6. Supervisor completes the task.
7. Subordinate continues with the workpackage.

• Supervisor
• MRO Objects (Client)