Status & Priority

Overview

Status and Priority are two main meta fields designed for user interaction for Events, Cases and more.

Status operations is designed to provide user interaction capabilities to main items in Bazefield such as Events. For Events this typically means setting this as Acknowledged to track whether or not the event needs to be reviewed by an operations team. A default status for Events is Unacknowledged, however for different types of items, such as Cases or Tasks you will have different status for their general operation “state.”

Priorities help designate how important an Event or other item can be. Priorities can be set on events as a default or starting point, but then can be escalated or deescalated by a user after the fact.

Events also support special Acknowledgement Settings which work together with the Acknowledged status of events. When enabled acknowledgement settings require additional user actions or steps to perform the status change to Acknowledged.

Why Use Status & Priority?

Priority and Status are important and primary workflow management tools that let users track what they have done, what they should look at and control the filters on the screen. Statuses are for whether an operator has seen and reviewed an event.

Priorities are a crucial way for customers to manage clean views of important events coming into Bazefield. Depending on your vendors, you may have hundreds or thousands of events coming in from your inverters or turbines a day but there might only be a few that you wish to manage from the operations side. Pre-organizing your alarm templates for events can allow you to filter out the noise from a real time operations team without impacting the actual data collection, analysis work or availability logic.

Event Automations

Status and Priority changes on events are hooked into Event Automations and can trigger Flows or Event Notifications to perform additional actions for certain situations such as automatically creating a case or sending an email.

Acknowledgement settings are crucial for critical or safety tier level events that require additional user actions by operators. It supports required comments, updating tag values as well as warning message.

How to Use

Event Operations includes columns for Status and Priority by default. Users can edit and view both from their rows or via bulk actions. Combining these with filters helps turn user actions into a help workflow

Priorities can be handled the same way. To set a default priority you can perform an edit from the vent operations page. You may also use the import and export template functionality in Asset/Domain Models page.

Customization

Both priorities and statuses can be customized on each customer instance of Bazefield. Customization however requires Bazefield delivery or support work.

Acknowledgement Settings

These settings are defined under the event definition and can be accessed via the inline action button in Event Operations or on the Asset/Domain Model page as shown in the screenshot below.

If points are updated, there will be an automatic comment creation for historical tracking purposes that will end up in the activity logs as well as the comment section.