Tracker profiles

The configuration of a tracker controls its behavior and can be adapted by applying a new or updated tracker profile.

The behavior of a tracker is controlled by many configuration settings.

A tracker profile specifies the appropriate values for the vast majority of a tracker's configurable settings, and optionally allows the user to specify custom values for some particular settings.

The idea is that each tracker product type, use case and/or asset type will have its own tracker profile.

The following examples illustrate the concept of a tracker profile:

  • Applying a "Trailer profile" on a tracker will configure the tracker in such a way that the typical movements of a trailer are correctly detected, will make sure that the tracker uses outdoor geolocation technologies such as GPS and will limit the number of location updates while the trailer is moving in order to prevent the tracker battery to run low too soon. The frequency with which the tracker sends location updates during movements may be offered as a configurable setting for the user.
  • Applying a "Returnable Transport Unit (RTP) profile" on a tracker will configure a tracker in such a way that the battery autonomy will be more than 5 years because RTP maintenance is not a frequent task, and will combine both outdoor and indoor geolocation technologies to make sure that the RTPs can be geolocated at any time and any place. The time-out for the tracker to conclude that it has arrived at a new location may be offered as a configurable setting for the user.
  • Note that some trackers models are not remotely configurable; they are not configurable using tracker profiles.
There are two types of standard tracking profiles:
  • Domain-specific profiles = predefined profiles that are tailored for a specific use case with configurable parameters that should cover 90% of the cases of this use case.
  • Tracker specific profiles = all option profiles = profiles that contain all meaningful options for a specific tracker type or family of trackers. There exists one tracker specific profile per tracker or family of trackers.

Best is to always use a domain-specific profile. They will cover 90% of all use cases. For the remaining percentages you can use the tracker specific profiles (also called "all option profiles".

Domain-specific tracker profiles

Sensolus provides following domain-specific tracker profiles:

Tracker-specific tracker profiles

Sensolus provides following tracker-specific tracker profiles:
  • All options TRACK 1000/1010
  • All options TRACK 1001
  • All options TRACK 1020
  • All options TRACK 1100

Tracker profile composition

Every tracker profile is a combination of:

  • Active tracker services
  • A default configuration of a set of tracker profile parameters.
  • A set of other configurations of the tracker profile parameters to fine-tune the profile.