Telematics Guru provides different billing plans to suit different asset utilization requirements. This provides a great way to get the great features of Telematics Guru, but at a price point that suits the type of asset.


To get more information about the cost of each plan, please email info@digitalmatter.com


TG Plan
Description
Record Count
Considerations
Maps
TG-Classic
Original TG plan. Includes most functionality.
No limit, but fair use applies
This is the default plan.
Google Maps
TG-Pro
Additional advanced features: local speed limit lookup.
No limit, but fair use applies
This plan provides local speed limit lookup using the Google API.
Google Maps
TG-24
TG-Classic features, for devices sending a maximum of 24 records per day
24 per day, averaged over the month
Exceeding the record count will result in a TG-Classic fee being charged in addition to the TG-24 fee.
Google Maps
TG-4
TG-Classic features, for devices sending a maximum of 4 records per day
4 per day, averaged over the month
Exceeding the record count will result in a TG-Classic fee being charged in addition to the TG-4 fee.
Google Maps
TG-ALR
Asset Location and Recovery features: basic live tracking; ALR alerts; ALR reports; no history.
No limit, but fair use applies
Excellent value if a live position is required. No history is presented.
Open Street Maps


TG-Classic, TG-Pro, TG-24 and TG-4 are all plans within 'Regular' TG organisations. 


ALR is it's own Organisation type. 


Assigning plans to assets

  • Use this page in TG to assign plans to assets.
  • The user will need the "Billing Plan Manage" permission to manage billing plans. 
  • It is the Partner's responsibility to  manage billing plans on assets. 
  • On creation, the TG-Classic plan will be assigned by default.


Record count

If the asset plan specifies a record count limit, be aware:

  • It is the partner's responsibility to configure the device to obey this limit. DM can assist with this setup, but the partner must ensure the settings are applied. Device configuration is generally done using the OEM Server, but it varies between device types. Contact your local DM office to get access to the OEM Server. You may want to set Oysters or Remoras to periodic tracking only.
  • The penalty for exceeding the limit is an additional TG-Classic fee being charged on top of the TG-24 or TG-4 fee.
  • Record counts are averaged over the month. For example, the TG-4 plan gives a budget of 4 x 30 = 120 records in a 30 day month. If the device sends 1 record a day for 28 days, and 12 records on the other 2 days, that is a total of 52 records. This is below the 120 record budget, and will not incur a penalty, despite exceeding the 4 record count on 2 days.
  • The count is done for records, not uploads. An upload can contain multiple records. For example, the default Oyster/Remora settings would log 1 GPS record every 2 min while in trip. And upload every 30 min in trip. So 15 records would be sent in 1 upload.


You can view the current message count in the Asset Billing Plan page. This gives the count for the current month. TG will count records only if the asset is set to TG-4 or TG-24.