Alarm enrichment does not modify or update the values of the attributes being configured, or new custom fields are created that cannot be used.
Customer had setup an Alarm Enrichment policy
The policy has Message Contains "is inactive"
It sets the attribute category to the value "Robot is inactive"
From reviewing the alarms that matches enrichment policy we can tell that the policy got triggered by reviewing the Life Cycle of those alarms but for some unknown, the policy is setting the value to either "Robot is inactive" or System
This is working as designed.
O2 first try to get the value from the Inventory attribute "category", this is where "System" came from. Only if this fails, then O2 will use the default value.
The value "System" is being use if the Alarm has an inventory that already has a category field with the a value. If an Alarm has an inventory without the category field, it will use the value from the enrichment rule.
If Customer wants to make sure the enrichment works with the selected, they will need to use a custom attribute.