Alert management - HxGN EAM - 11.7.1 - Administration & Configuration - Hexagon

EAM System Overview

Language
English (United States)
Product
HxGN EAM
Search by Category
Administration & Configuration
HxGN EAM Version
11.7.1

Alert Management is a function in HxGN EAM that can search the database for specific data and then send email or create work orders based on the analysis and interpretation of that data. You can use Alert Management to notify you of high energy consumption, equipment conditions like vibration or temperatures, and you can use it to support your workflow (notify an approver there are work request awaiting approval), escalation (notify a supervisor the that same request has been waiting for approval for more than a week), etc. Alerts run at a predefined frequency, so they are ideal for anything that does not need immediate action.

This way Alert Management is complementing the E-Mail Messenger function of HxGN EAM that only supports event driven (synchronous) emails.

Module features

Module feature

Description

User Defined Grids

The alert management function uses the user defined grid function of HxGN EAM and as such can search for any data available in or accessible to the EAM database, whether native or not.

Alert Management

Define an alert using any of your predefined user defined grids. Specify a frequency in which you want the alert to run, e.g., once a week, twice an hour, etc. Once you have defined the grid to be used on the alert you can create additional Dataspies (queries) to further limit the data you want to alert on. Other features of the Alert Management function include:

  • Create a work order for every alert record found, based on an assigned standard work order.

  • Send an email for every alert record found, based on an assigned email template. Note that you can have an alert do both actions: create a work order and send an email.

  • Before and after the alert you can run specific logic. For example, before the alert runs, prepare records for the alert by populating a temporary table with data. Then after the alert has run, remove the records from this temporary table. There are obviously lots of other uses for this powerful feature.

  • Build in a delay feature. If an alert finds a condition that requires an email or a work order, obviously the next time that alert runs, it may find the same condition, especially if the interval between runs is short. To avoid repetitive emails or work orders for the same issue a delay can be configured that stops the alert from issuing for a defined amount of time.

  • On the history tab you can find the history of email and work orders created by the alert.