No Data – When No Consumable/Service Alert Events are active and No Consumable/Service data was fed from Onsite for the Device;

  All Ok – When No Consumable/Service Alert Events are active for a Device but it has Consumable/Service data fed from Onsite;

  Alert – When the Alert Overdue time did Not elapsed for its Actions and does Not Require Approval (the first Action was already Approved or it does Not Require Approval), or if it was Already Triggered but the Overdue time did Not elapse;

  Waiting for Approval – When the first action Requires Approval and it was not yet approved or cleared;

  Submitted – When the Alert does Not Require Approval or is Already Approved and further Actions have been processed, i.e. an email is sent to to the Dealer; and Overdue Time has NOT Elapsed;

  Overdue – When the Alert does Not Require Approval or is Already Approved and the Overdue Time Has Elapsed, and there are Overdue Actions that are Not Yet Performed. Overdue Time is measured from the moment when the Alert Triggered to the Moment when the User looks at the data in the UI;

  Submitted & Overdue – When at least the one Action of the Alert has been already Submitted and the Overdue Time Has Elapsed;

  Dismissed Alert – When  the alert is manually Dismissed by the user in Device Status or Active Alerts pages;

  Stale – When the Stale time has Elapsed. Stale Time is measured from the moment when the Alert Triggered to the Moment when the User looks at the data in the UI;

Archived – When the Alert is Archived because it became Stale, or as a result of Internal ASM processing, or when the current state of the device/supply no longer satisfies the Alert Definition Triggering Conditions.