Use the Missing Assets step of the Model wizard to specify if or when the Platform should consider assets associated with this model as missing. Each application of models and assets is unique: in some cases, the assets should be online constantly; in other cases, it may be acceptable that the assets miss defined contacts with the Platform (based on their ping rate settings). In the latter cases, you can use the settings in this page to specify when the Platform needs to consider assets as missing, and thus post those assets as Missing Assets in the Axeda® Service Application.
For "contactable" assets that communicate through the Axeda Codec Server, whether you want to consider the assets associated with this model as missing depends on the assets and on how the codec handles messaging for the assets. If the codec sends any messages at all to the Platfrom on behalf of the assets, then you may want to define when to consider them as missing. Again, it depends on the assets. Codec developers should refer to the Axeda® Codec Developer's Kit Guide for complete information.
f you do need to track which assets for this model are missing, you can specify when the Platform should consider the assets as missing.
o If it is critical that no assets of this model miss a single contact, you specify that assets be considered missing after one missed ping. In this case, as soon as an asset does not contact the Platform appropriately for its ping rate, the Platform posts that asset as missing.
o If assets of this model should not miss a single expected ping but, in the event they do, they proceed to contact the Platform immediately after that miss (within 10 seconds), you specify that assets be considered missing after one missed ping and 10 seconds. In this case, as soon as an asset misses a single ping and then 10 seconds passes without any contact from the asset, the Platform posts that asset as missing.
o If it is important that assets contact the Platform as expected but that some missed pings (up to 3 successive pings) and a short period of time (5 minutes) is acceptable, you specify that assets are considered missing after 3 missed pings and 5 minutes. In this case, if the asset has missed 3 contacts already and does not contact the Platform before the end of 5 minutes, the Platform posts that asset as missing.
o If it is important that assets contact the Platform at least once a week, you specify that assets be considered missing if they have not contacted the Platform at all (0 pings) in 1 week. In this case, the Platform posts that asset as missing if a week has passed since the last time it contacted the Platform .
o For wireless M2M assets that are configured for the shoulder tap delivery method, you set the poll rate to NULL, which means that the Ping Rate will be 0. A ping rate of 0 typically means that the asset can never be "Missing." However, for M2M shoulder-tap assets, the task that checks for missing assets checks the table of shoulder tap messages to determine if an asset is Missing. If the number of retries for a shoulder tap message for an asset has been exhausted and the asset has not responded to the shoulder tap, the task sets the status of the asset to Missing. If you never want these assets to show a status of Missing, select the option, "Don't consider assets of this model as missing."
Do one of the following:
o If you do not need to track assets for this model that miss contacts with the Platform , select "Don't consider assets of this model as missing".
o If you need to track assets for this model and determine which may be missing, select "Asset of this model go missing after ". Then type the number of pings (contacts) and/or the period of time by which the Platform will calculate if assets are missing.
If you are all done configuring or viewing this model, click Next and the Auto Register Devices step appears, or click Finish and the Model Confirmation wizard step appears. If you click Cancel and continue canceling, all information configured in this wizard is removed and a list of models appears.