Alerts

Definition

Create e-mail and work order alerts to notify users when data in Hexagon EAM (e.g. equipment) does not meet a specified criteria.

First, create a grid to query data in the system and then use alert management to determine if the results need to be measured against a min/max setting or if the results alone will trigger an email and/or work order. An alert management record can be created to monitor readings that are being imported into Hexagon EAM for chillers.

Example: The alert record may monitor to see if the difference between supply air temperature and the return air temperature is >22 degrees when chilled water temperature is <46 degrees and chilled water valve is open >50%. If all this criteria is met for a chiller then a work order would be created indicating that a belt could be slipping or the filters may be plugged.

Note: Use the new R5ALERTDATAOBJ table to import records into Hexagon EAM. Then use alert management to analyze the records and create alerts when deviations occur. R5ALERTDATAOBJ was specifically designed for analyzing data imported from another system related to Infor EAM equipment records. This table can be accessed through web services or using the Hexagon EAM Import Utility. Once records are created in R5ALERTDATAOBJ, use this table in Grid Designer when creating the alert management grid query.

Create an active alert management grid on the Grid Designer page before setting up an alert on the Alerts page (see this article on Grids).

Create a new Alert

To create e-mail and work order alerts for specific equipment (see screenshot below):

Select Administration > System Configuration > Alert Management.
Click "New Record" ([+] icon).
Enter a description for the alert.
Specify this Alert Definition Details information:
- "Grid Name": Enter the grid name defined for the Alerts form on the Grid Designer form, e.g. XUDUMM and XUDUM1.
- "Dataspy": Select the Dataspy for the grid, e.g. "All Records"
- "Exception Entity": Enter the exception entity.
- "Grid Key Field 1": Enter the mapping to the corresponding grid column that should be used as a key field in the grid, e.g., if analyzing equipment this would map to the equipment column in the grid.
- "Grid Key Field 2": Enter the mapping to the corresponding grid column that should be used as a key field in the grid, e.g., if analyzing equipment this would map to the equipment column in the grid.
- Note: Grid key fields are populated on the History page, and used for reviewing data when a delay period is entered for an alert on the Work Order Alerts, Exceptions, or E-mail Alerts pages.
Click "Save Record" (floppy disc icon). The system automatically populates Alert, Created By, and Date Created.

Note: To preview the grid query results, click Preview Grid. To activate alert management, enable the ALRT driver on the Job Setup form.

Schedule an Alert

To create e-mail and work order alerts for specific equipment (see screenshot below):

Select Administration > System Configuration > Alert Management.
Select to Alert to edit.
"Active": Select to set this alert to active. This makes the following fields editable.
Specify this Scheduling information:
- "Frequency": Enter the frequency of the analysis in a numerical amount, e.g. 10
- "UOM", e.g., Days -> the system will perform an analysis every 10 days.
- Note: Although the analysis may process every 10 days, the system does not generate alerts unless the analysis meets the specified criteria.
- "Next Evaluation Date": Enter the next date to evaluate the alert. The system automatically populates Last Evaluation Date and Last Alert Date.
Specify this Active Alert Types information:
- "Work Order": Select to create a work order alert based on specific parameters.
- "E-mail": Select to create an e-mail alert based on specific parameters.
- "ION Pulse": Select to create an ION Pulse based on specific parameters.
Click "Save Record" (floppy disc icon).

Define trigger values

To define trigger values for an alert, indicate the following information (see screenshot below):

Select Administration > System Configuration > Alert Management.
Select the alert to edit.
Specify this Min/Max Definition information:
- "Use Min/Max": Select to use a minimum and maximum range for this alert.
- "Min/Max Value Field": Enter the mapping to the corresponding grid column. During the alert process the system analyzes the result of the field for each row in the grid and compares it to the min/max selections.
- "Min Value": Enter the minimum value for the alert. The system produces alerts when the result of Min/Max Value Field is less than or equal to the minimum value.
- "Max Value": Enter the maximum value for the alert. The system produces alerts when the result of Min/Max Value Field is greater than or equal to the maximum value.
- "Trigger within Min/Max Values": Select to trigger alerts when the result value is within the Min Value and Max Value.
- Note: Triggering within min/max will generate alerts when the result has values equal to or greater than the Min Value and less than or equal to the Max Value. Enter the user-defined fields.
Click "Save Record".

Define before SQL statements for Alerts

WARNING: This feature, if implemented incorrectly, could alter or delete data. Hexagon recommends that these features be enabled only by experts who have received training on these features.

Define SQL statements that the system will execute prior to executing the defined grid for an alert. Before SQL statements can be used to prepare data or structures being used by the grid, e.g., purge records.

To define before SQL statements for alerts (see screenshot below):

Select Administration > System Configuration > Alert Management.
Select the alert for which to define the before SQL statement, and then click the "Before SQL" tab.
"SQL Statement": Enter the SQL statement that will be executed before the grid query will produce a result set. The system automatically populates Abort on Failure.
- Note: Unselect Abort on Failure to enable the system to continue executing the grid query if the SQL statement fails.
"Comments": Enter comments regarding the SQL statement.
"Execute when Previewing Grid": Select to execute the SQL statement when Grid Preview is selected.
"Active": Select to set this SQL statement record to active.
- Note: To process the before SQL statement when the alert job is run or Grid Preview is selected on the Record View page of the Alerts form, you must select Active.
Click on "Test SQL" to check the validity of the SQL statement.
- If the test is successful, a message appears "The SQL statement is OK.".
- Note: a successful test does not imply a "correct" SQL statement that fulfills the business logic. It only means that the statement is "grammatically" valid. A valid statement can still damage the database integrity.
- If the statement is not valid, an error message appears, indicating the type of error, e.g.: "The SQL Statement is invalid: ORA-00900: invalid SQL statement."
Click "Save Record" (floppy disc icon).

Define after SQL statements for Alerts

WARNING: This feature, if implemented incorrectly, could alter or delete data. Hexagon recommends that these features be enabled only by experts who have received training on these features.

Define SQL statements for system to execute after executing the defined grid query and after creating e-mail and work order alerts.

To define after SQL statement for alerts (see screenshot below):

Select Administration > System Configuration > Alert Management.
Select the alert for which to define the after SQL statement, and then click the "After SQL" tab.
"SQL Statement": Enter the SQL statement that will be executed after the grid query and alerts.
"Comments": Enter comments regarding the SQL statement.
"Execute when Previewing Grid": Select to execute the SQL statement when Grid Preview is selected.
"Active": Select to set this SQL statement record to active. The system processes the after SQL statement after the grid query is processed.
- Note: To process the after SQL statement when the alert job is run or Grid Preview is selected on the Record View page of the Alerts form, you must select Active.
Click on "Test SQL" to check the validity of the SQL statement.
- If the test is successful, a message appears "The SQL statement is OK.".
- Note: a successful test does not imply a "correct" SQL statement that fulfills the business logic. It only means that the statement is "grammatically" valid. A valid statement can still damage the database integrity.
- If the statement is not valid, an error message appears, indicating the type of error, e.g.: "The SQL Statement is invalid: ORA-00900: invalid SQL statement."
Click "Save Record" (floppy disc icon).

Alert history

To visualise the Alert history (see screenshot below):

Select Administration > System Configuration > Alert Management.
Select the alert for which to define the after SQL statement, and then click the "History" tab.
The column "Status" indicates the status of the Alert occurrence for a given "Alert Type": Success or Failed
- In case of a failed alert occurrence, the error message indicates the reason of the failure.

Deactivate an Alert

An alert can be deactivated either by deactivating the SQL statement related to the Alert, or by deactivating the alert altogether.

To deactivate the SQL statement:

-> see sections on "Define before / after SQL statements for Alerts", point 6:

Clear the "Active" checkbox

To deactivate the Alert itself:

-> see section above on "Schedule an Alert", point 3:

Clear the "Active" checkbox

Delete an Alert

To delete an Alert permanently (see screenshot below):

Select Administration > System Configuration > Alert Management.
Select the alert to delete.
Click "Delete Record" (litter bin icon)
Confirm by clicking "Yes"; Note: this deletes the Alert permanently.

Current Alerts and Scheduling

As of May 2025, the following alerts are active in the HiSERV-production environment of Hexagon:

Alert Alert Description Active Time of day Frequency UOM Grid Name 10002 Revise contract with automatic renewal YES 05:10 1 Days RUVCCT 10003 Payment date for contract YES 05:20 1 Days DUAL01 10007 Create new invoice revision YES 20 Minutes XUDUMN 10011 Depreciation - Monthly Process 1/2 YES 1st of month, 03:42 1 Months UUDEP1 10012 TrackUnit - TZ+0 CET Berlin, Paris. Vienna YES 23:30 1 Days UUOBJ3 10013 TrackUnit - TZ+1 EET Helsinki, Bukarest YES 23:30 1 Days UUOBJ4 10014 TrackUnit - TZ-1 WET London, Lisbon YES 23:30 1 Days UUOBJ7 10015 TrackUnit - TZ-2 AZOT Azores YES 23:30 1 Days UUOBJ8 10016 TrackUnit Objects - Airport Update YES 04:38 1 Days UUAIR1 10017 Contract Charge Definitions Deactivation YES 12:48 1 Weeks XUDUMM 10021 Recalculate Invoice after Adj.Qty and Dates Update YES 1st of month, 07:30 1 Months XUDUMM 10023 Compute data for Gantt Graph: availability and locations YES 20 Minutes XUDUM1 10025 TrackUnit - Delete Duplicates OH1-2 YES 06:00 1 Days UUDUP2 10026 TrackUnit - Notification process YES 06:30 1 Days UUINT1 10029 Depreciation - Monthly Process 2/2 YES 04:58 1 Months UUDEP1 10033 Smartfleet Sync - Send GSE Information to Smartfleet YES 03:00 1 Days UUSMF1 10036 RES data to update on GSE page YES 8 Minutes XUDUM1 10037 RENT SALE data to update on GSE page YES 8 Minutes XUDUM1 10038 Update GSE Next Action and Planned Location YES 8 Minutes XUDUM1 10042 Fill in missing DN data YES 8 Hours XUDUM1 10043 Inconsistent tax codes in Sales YES 1 Hours XUDUM1 10044 Cancel unapproved RES after end date YES 04:09 1 Days XUDUMM 10047 RES change to fully converted YES 03:52 1 Days XUDUM1 10048 Fill CIT contract item rate from CCD table YES 03:23 1 Days XUDUM1 10049 Update some data; code is adapted each time YES 00:12 and 12:12 12 Hours XUDUM1 10050 Update takeover date in SALE contract items YES 15 Minutes XUDUM1 10051 Remove purchased items in Res after commiss YES 01:44 1 Days XUDUM1 10052 Update details of purchased RES items if changed YES 02:25 1 Days XUDUM1 10053 Update details of active RES items if changed YES 02:43 1 Days XUDUM1 10054 Sale contract to FULF if all DNs are signed YES 23:41 1 Days XUDUM1 10055 Update details of active RENT items if changed YES 01:13 1 Days XUDUM1 10056 Update details of active RENT Charge Def if changed YES 02:19 1 Days XUDUM1 10057 Free hours of Pay-per-Use shown in invoices YES 10:21 1 Hours XUDUM1