ThingWorx Model Definition and Composer > Thing Templates > Remote Templates > Thing Presence > Thing Presence: Reporting Strategies
  
Thing Presence: Reporting Strategies
The ThingWorx platform comes with default reporting strategies to handle various existing use cases. In some cases, a customer may want to create a custom strategy to handle their unique situation. This section describes the default reporting strategies.
* 
No platform-provided out-of-the-box polling Reporting Strategy is provided with ThingWorx platform 8.4. It is provided only with the Axeda Compatibility Extension (ACE).
The polling ReportingStrategy thing to be used by Axeda customers for Axeda devices conforms to the Axeda Compatibility Extension's model of Axeda Assets. For details on the entities of the Axeda Compatibility Extension (ACE), see http://support.ptc.com/help/thingworx_hc/axeda_compatibility_package/en/#page/latest%2Fextensions_reference%2Face%2Fc_ace_ref_intro.html%23.
AlwaysOn
The default reporting strategy is named AlwaysOnReporting. This strategy is applied to all existing remote things upon platform upgrade, or creation of a new RemoteThing.
This strategy is used on all remote things representing devices that bind to the platform and continuously maintain their connection. For example, most devices that directly use WebSocket SDKs (the ThingWorx Edge SDKs all use the WebSocket protocol) use the AlwaysOnReporting strategy.
For all devices with this default reporting strategy, evaluation occurs:
When the device binds, in which case the device is considered reporting and isReporting is set to true.
When the device unbinds, in which case the device is considered not reporting and isReporting is set to false.
Polling Strategy (ACE)
The polling strategy is used on all things representing devices that periodically connect to the platform to 'poll' for egress and/or deliver ingress (property updates, for example). These devices are not expected to maintain their connection to the platform continuously under normal operating conditions. Examples of polling devices include Axeda's eMessage Agent and Questra Service Agent (Axeda IDM) devices, which use HTTP/HTTPS for communications and protocol adapters to convert to/from the ThingWorx native WebSocket-based protocol.
The Axeda Compatibility Extension (ACE) captures this strategy in the ReportingStrategy Thing.. This thing provides some customization options to allow you to configure the strategy to your needs. See the reference for the ACE in the Axeda Compatibility Help Center for details.
For all polling devices, reporting evaluation occurs:
When the device contacts the platform, more specifically on bind events, in which case a device is considered reporting
On a timed interval with a default of evaluating once every five minutes, in which case a device may be considered not reporting if it fails to meet the missed pings and missed time criteria.