IN THIS ARTICLE

  • Asset notifications: Overview
  • Monitored asset notification listing
  • Monitoring asset notification listing

Asset notifications: Overview


Notifications are alerts that can be communicated to users, highlighting important asset events. These notifications can be communicated via SMS, email and bulletin board immediately, daily, weekly and monthly basis. 


The asset notifications are divided into:

  • Monitored asset notifications: These are notifications that are linked to the status of a monitored asset i.e., the condition/temperature of the asset and lack of the such data
  • Monitoring asset notifications: These are notifications that are linked to the physical condition of the monitoring asset i.e., the battery status, power availability, sensor disconnection & device disconnection from it's transmitter.


Monitored asset notification listing


The temperature recorded for the monitored asset is the basis for all monitored asset notifications. The notifications can be triggered based on each of these status and per sensor. The list of monitored asset events for which notifications are triggered are listed below.



A. Temperature Excursion: As soon as a monitored asset goes beyond the temperature threshold, it is known as an excursion state. It should be the first notification to ensure that asset owners are on alert and take preventive measures to avoid any damage to the materials. Excursion can be of two types as listed below:

  1. High excursion: When an asset registers data which is higher than the pre-defined temperature threshold, a notification can be triggered. The pre-defined temperature range is based on the high temperature threshold that has been defined for it's associated monitoring asset. This notification will be triggered for every sensor and can be customized on the following basis:
    • Minutes of excursion after which this notification should be triggered
    • Entity tags
  2. Low excursion: When an asset registers data which is lower than the pre-defined temperature threshold, a notification can be triggered. The pre-defined temperature range is based on the low temperature threshold that has been defined for it's associated monitoring asset. This notification will be triggered for every sensor and can be customized on the following basis:
    • Minutes of excursion after which this notification should be triggered
    • Entity tags


B. Temperature Warning: When a monitored asset goes beyond the temperature threshold for a period it of time, it is known as a warning state. The asset owners are expected to take immediate action to avoid any further damage to the materials. Warning can be of two types as listed below:


  1. High Warning: When an asset continues to be in a pre-defined high temperature threshold for a pre-defined period, a warning notification can be triggered. The pre-defined temperature range is based on the high warning temperature threshold & period that has been defined for it's associated monitoring asset. This notification will be triggered for every sensor and can be customized on the following basis:
    • Minutes of high warning after which this notification should be triggered
    • Entity tags
  2. Low Warning: When an asset continues to be in a pre-defined low temperature threshold for a pre-defined period, a warning notification can be triggered. The pre-defined temperature range is based on the low warning temperature threshold & period that has been defined for it's associated monitoring asset. This notification will be triggered for every sensor and can be customized on the following basis:
    • Minutes of low warning after which this notification should be triggered
    • Entity tags


C. Temperature Alarm: When a monitored asset goes beyond the temperature threshold for a period it of time, typically after warning, it is referred to as an alarm state. The material at this state might not be usable/potent. Hence asset owners are expected to confirm damage to the material and take necessary action. Alarm can be of two types as listed below:

  1. High Alarm: When an asset continues to be in a pre-defined high temperature threshold for a pre-defined period, a high alarm notification can be triggered. The pre-defined temperature range is based on the high alarm temperature threshold & period that has been defined for it's associated monitoring asset. This notification will be triggered for every sensor and can be customized on the following basis:
    • Minutes of high alarm after which this notification should be triggered
    • Entity tags
  2. Low Alarm: When an asset continues to be in a pre-defined low temperature threshold for a pre-defined period, a low alarm notification can be triggered. The pre-defined temperature range is based on the low warning temperature threshold that has been defined for it's associated monitoring asset. This notification will be triggered for every sensor and can be customized on the following basis:
    • Minutes of low alarm after which this notification should be triggered
    • Entity tags


D. Temperature Incursion: 

  1. Incursion: When an asset returns from a temperature excursion to the pre-defined temperature threshold, an incursion notification can be triggered. The pre-defined temperature range is based on the high & low excursion temperature threshold that has been defined for it's associated monitoring asset. This notification will be triggered for every sensor and can be customized on the following basis:
    • Entity tags


E. Temperature unknown

  1. No data from device: When a monitored asset does not register temperatures from any sensor for 3 continuous push intervals, this notification is triggered. The push interval is based on the pre-defined minutes when temperatures are expected to be received per monitoring asset. This can be customized on the following basis:
    • Days since which the device has been inactive
    • Entity tags




 NOTE
  1. Temperature thresholds can be customized per sensor and push interval per monitoring asset.
  2. Temperature ranges & duration for excursion, warning & alarm can be different for each sensor of a monitoring asset


Monitoring asset notification listing


The physical status recorded of the monitoring asset is the basis for all monitoring asset notifications. Some of the notifications are sensor specific. The list of monitoring asset events for which notifications are triggered are listed below.


A. Sensor connection

  1. Sensor disconnected:  When a sensor is disconnected from it's monitoring asset, a sensor disconnected notification can be triggered. This notification will be triggered for every sensor and can be customized on the following basis:
    • Minutes of disconnection after which this notification should be triggered
    • Entity tags
  2. Sensor connected: When a sensor is connected back to it's monitoring asset after a disconnected state, this notification can be triggered. This notification will be triggered for every sensor and can be customized on the following basis:
    • Entity tags


B. Device connection

  1. Device disconnected: When a monitoring asset is disconnected from it's transmitter, this notification can be triggered. This notification will be triggered for every monitoring asset and can be customized on the following basis:
    • Minutes of disconnection after which this notification should be triggered
    • Entity tags
  2. Device connected: When a monitoring asset is is connected back to it's transmitter after a disconnected state, this notification can be triggered. This notification will be triggered for every monitoring asset and can be customized on the following basis:
    • Minutes of disconnection after which this notification should be triggered
    • Entity tags


C. Battery status

  1. Low battery warning: When a monitoring asset is below a pre-defined warning battery threshold, this notification can be triggered. The pre-defined battery threshold is based on the low battery warning percentage that has been defined for the asset. This can be customized on the following basis:
    • Minutes of battery warning after which this notification should be triggered
    • Entity tags
  2. Low battery alarm: When a monitoring asset is below a pre-defined alarm battery threshold, this notification can be triggered. The pre-defined battery threshold is based on the low battery alarm percentage that has been defined for the asset. This can be customized on the following basis:
    • Minutes of battery alarm after which this notification should be triggered
    • Entity tags
  3. Normal battery: When a monitoring asset is back to a pre-defined battery threshold from a low warning state, this notification can be triggered. The pre-defined battery threshold is based on the low battery warning percentage that has been defined for the asset. This can be customized on the following basis:
    • Entity tags


D. Power status

  1. Power outage:  When a monitoring asset is not being charged using a power source, a power outage notification is triggered. This notification can be used as a proxy to understand if the monitored asset has power availability, as the entity where both the assets are kept would usually have the same source. This can be customized on the following basis:
    • Minutes of power outage after which this notification should be triggered
    • Entity tags
  2. Power available: When a monitoring asset is being charged using a power source after an outage, a power available notification is triggered. This notification can be used as a proxy to understand if the monitored asset has power availability, as the entity where both the assets are kept would usually have the same source. This can be customized on the following basis:
    • Entity tags



To configure these asset notifications, refer to this article under the configurations section.