Fracttal One uses a hierarchical model to record failures in unplanned tasks, based on the relationship between failure type and cause, ensuring an organized and consistent record. When creating an unplanned task with a failure, the system dynamically filters options according to selections, showing only related failure causes, and automatically removes dependencies if any selection is changed to maintain consistency.
Activation of Auxiliary Catalogs with dependency
To use the hierarchical structure of failures, it is necessary to first enable the corresponding option in the Work Orders configuration.
Configuration → Modules → Work Orders
Within the options and permissions section, activate the setting: Assign auxiliary catalogs with dependency
Failure hierarchy configuration
The definition of hierarchical relationships is done from:
Configuration → Auxiliary Catalogs → Failure Catalogs
Within this section, there are two main levels for configuring dependencies:
Failure Types
Failure Causes
To configure the hierarchy, follow this procedure:
Select the (+) icon to create a new record in the catalog.
Enter a description corresponding to the failure type or failure cause.
Save the record so it becomes available in the system.
Once the record is created, it is possible to define its hierarchical dependencies:
Select the hierarchy icon on the corresponding item.
- In the case of Failure Types, please associate the failure causes you want to relate.
In the case of Failure Causes, associate the corresponding detection methods.
Save the configuration to apply the defined relationships.
After completing this process, the system correctly records the hierarchical structure, allowing its use in the operational workflow for failure registration.
Recording failure information in Tasks
During the creation or editing of an unplanned task marked as a failure:
Select the corresponding failure type while filling out the task in the "failure information" option and check "Did the asset fail?".
Select the corresponding failure type.
Select the cause of the failure as appropriate.
* The system will only show causes associated with that type *
This behavior corresponds to dynamic filtering, guiding the user in the registration and preventing invalid combinations.