Enable the ability for end-user to manage custom severity levels for event frames, to allow for better communications across response teams and business unit functions.
Exposing EF severity levels within a PI Notifications messages is very helpful in providing quick context to an issue. However, it can create confusion when those severity levels do not map well to a specific company's internal standard for incident reporting in either the severity level namings or qty of severity levels.
EXAMPLE MAPPING PROBLEM:
Event Frame = None, Information, Warning, Minor, Major, Critical
Cust 1 = Normal, SEV5, SEV4, SEV3, SEV2, SEV1
Cust 2 = Good, Information, Warning, Major, Critical, Fatal
Cust 3 = Clear, Indeterminate, Warning, Error, Fatal
Cust 4 = Normal, Low, Medium. High, Critical
In many of the above cases a Customer would be challenged in sending the EF severity level in a notification given with their internal mapping is either in conflict or has no context. Below is my specific mapping issue/challenge.
EF Level to Cust Level Mapping:
Critical = Fatal
Major = Critical
Minor = Major
Warning = Warning
Information = Data Issue
None = Normal
good idea