Missing Asset rules overview

The Axeda Platform looks for newly missing assets based on a predefined time interval. For assets running Axeda Agents or wireless assets running AWP agents that are  set up to poll the Platform, a  missing asset is defined as not having contacted the Platform, on a ping or otherwise, within the expected period of time for that asset. For wireless assets enabled for shoulder tap messaging, an asset is considered missing if the Platform has exhausted the maximum number of retries specified in the delivery method descriptor of the Model Profile.

For assets running Axeda IDM Agents that are Occasionally Connected, the MissingDevicesTask detects when these assets are offline and changes their status to Missing. When the assets reconnect, their status returns to Online.

Use this rule to execute actions when an asset becomes missing from the Axeda Platform  (that is, misses a scheduled contact). This rule would be able to detect when a missing asset is found, and then execute any actions associated with that rule. For example, if the Platform is configured to look for missing assets every 30 seconds and in that time an asset does not contact the Platform as expected (based on its individual ping interval), the Platform would evaluate any missing asset rules defined for that asset as true, and then execute any actions for those rules.

Note: If you are running the Axeda® Platform in redundant-gateways mode, Axeda recommends that you use the Connectivity rule instead of this rule. Refer to Rule wizard - Select Connectivity State Changes for more information about setting up the Connectivity rule.

Example of using asset missing and returned rules

You can use the asset-returned rule in conjunction with the asset-missing rule for an asset. For example, you can assign two rules to an asset: an asset-missing rule that executes a Set asset condition action (to put the asset in a bad or offline condition), and then an asset-returned rule that executes a Set asset condition action (to put the asset in a good or online condition) .

Tips

o        A ping rate of 0 indicates that either than an asset has been created in the Platform but not yet registered with the Platform. For a wireless asset it can also indicate that the asset is configured to use the Shoulder Tap delivery method and NOT to poll the Platform.

o        In the Axeda® Service application, Asset dashboard Rules module, you can view and enable or disable the rules configured for a specific asset.

o        In the Service application home page, Missing Assets module, you can view assets that are currently missing.