Predefined Alerts Explained

@ Order 1 and 3

The "ZONE TEMPERATURE DEAD" alert looks for the currentTemp point in the zone and compares it with the building tuner, building LimitMax value, and generates an alert when the currentTemp > building LimitMax 

@ Order 5

The "ZONE TEMPERATURE DEAD" alert looks for the euipStatus  point generates an alert when the euipStatus = "3"

The "CO ABOVE THRESHOLD WARN"alert looks for the co point in the zone and compares it with the applicable zoneCOThreshold and generates an alert when the co point value is 10% > zoneCOThreshold for more than15 minutes preset interval.

(We do not support a CO sensor as of now.)

@ Order 1

The "ABNORMAL CUR TEMP" alert looks for the currentTemp point in the zone and generates an alert when the difference between the last two historized values of the currentTemp is > 5 degrees Fahrenheit, and it remains the same for an offset of 5 mins

@ Order 3

The "ABNORMAL CUR TEMP" alert looks for the currentTemp point in the zone and generates an alert when the difference between the last two historized values of the currentTemp is <- 5 degrees Fahrenheit, and it remains the same for an offset of 5 mins.

The "CONSTANT CUR TEMP" alert looks for the currentTemp point in the zone and generates an alert when the difference between the last two historized values of the currentTemp is = 0 degrees Fahrenheit, and it remains the same for an offset of 45 mins.

KEY WORDS

USAGE

Conditionals

Main Key for all the data point variables check which will need to be fetched before an Alert is raised

Order

This order "number"  will specify the placement of the JSON section within the "conditionals" key

Key

This forms the main part of the conditional which will be made up of numerous or a single tag to filter out point or points, else it can also be a pointref trying to reference a point. This will become part of the main query that will be sent for points fetch wrt to the Equip, Floor, System, Tuner . This can be used on either side LHS and RHS of the condition. Example :

"key" : "desired and temp and cooling", / "key": "id == @c11a6ceb-0bf2-4580-9925-afbe663fb534",

"value" : "tuner and temp and cooling",

               "condition": "=="

Value

"value" can  be a verifiable number which will be used for verifying a key fetched data point.

Value can also be a query which will give points against which the point results from Key will be verified against.

"value" : "tuner and temp and cooling",

Condition

Conditions are different comparison operators like "<", ">", "<=", ">=", "==", "!="

Operator

This key "operator" is used to join two condition blocks together like "AND","OR"

Grpoperation

This defines the group operation. It can be equip, delta, min max or avg.

* ""         : run the key query system wide and fetch the matching point for evaluation with condition and value.

* "equip"    : fetch all zone equips matching key query for individual evaluation with condition and value.

* "delta"    : fetch all zone equips matching key query. For each equip, find the difference between the last two history values and use that for evaluation with condition and value.

* "min" or "max" or "avg"   : find all points matching the key query system wide, and take their min/max/ave for evaluation with condition and value.

* "bottom NN" or "top NN"  : (where NN is a percentage) find the values of all points matching the key query system wide. Take the bottom or top NN percent of the points. Use the closest value to that percentage and evaluate with condition and value.

* "oao"      : fetch all zone equips matching key query with the "oao" tag. For each, evaluate with condition and the history value of the point for the same equip matching the value query.

* "security" : Special logic evaluating the number of password attempts against value with condition.

* "alert"    : Special hard-coded logic on the CCU defines these alerts

Offset

The Time interval after which the alerts needs to be generated.

Alert

Alert Key section will contain

mAlertType

This can be of two types : INTERNAL and CUSTOMER VISIBLE

mTitle

This will need to be unique set of alphanumeric characters[Space also included] which will differentiate one Alert to another alert.

mMessage

A short description that will sent when Alerts are sent out to CCU, FAC apps

mNotificationMsg

A detailed Message that can be seen when the Short Alert messages are clicked. These messages also are sent for notification alerts options like the emails, Push Notifications.

mSeverity

Severe

Moderate

Low

Internal_Severe

Internal_Moderate

Internal_Low

Internal_Info

mEnabled

TRUE/FALSE :  This will be set to TRUE only if this has been enabled for a site by the Support Personnel in Internal portal in the Alerts Configuration Section

Messages To follow #defined nomenclature for dynamic inclusion of variable names and values

#equipname

substituted by the equipRef of  the shortlisted alertable points

#zonename

substituted by the roomRef of  the shortlisted alertable points

#floorname

substituted by the floorRef of  the shortlisted  alertable points

#systemname

substituted by the systemRef of  the shortlisted alertable  points

#sitename1

Obtained from the siteRef of  the shortlisted alertable  points

#pointVal1

pointVal1 is obtained when we evaluate the #condval1 , and pick its value

#pointVal2

pointVal2 is obtained when we evaluate the #condval2 , and pick its value

#pointVal3

pointVal3 is obtained when we evaluate the #condval3 , and pick its value

#pointVal4

pointVal4 is obtained when we evaluate the #condval4 , and pick its value

#pointName1

pointName1 is obtained when we evaluate the #condval1 , and pick its name

#pointName2

pointName2 is obtained when we evaluate the #condval2 , and pick its name

#pointName3

pointname3 is obtained when we evaluate the #condval3 , and pick its name