Customer Case:
The customer wants to stop asset charges from increasing after a certain cost limit has been reached. They would like to understand how Cost Capping works in ON!Track and where it can be configured.
The customer wants to stop asset charges from increasing after a certain cost limit has been reached. They would like to understand how Cost Capping works in ON!Track and where it can be configured.
How does ON!Track work?
Cost Capping allows customers to define a maximum chargeable amount for an asset. Once the configured cap is reached, ON!Track stops calculating additional costs for that asset, even if the asset continues to remain at the location.
Cost Capping can be configured at two levels:
Location Level - A cost cap can be applied to a location to control the maximum charges that can be accumulated according to the location's cost settings and rate settings.
Asset Level- Asset-level capping determines whether a specific asset is subject to cost capping and what cap value should be applied to that asset.
When cost capping is enabled, ON!Track continuously calculates asset charges using the configured rate settings. As soon as the accumulated cost reaches the defined cap value:
- Additional charges are no longer applied.
- The asset cost stops increasing.
- The capped amount becomes the maximum chargeable value for that asset.
This feature is useful when customers want to limit the maximum cost that can be charged for an asset, regardless of how long it remains on site.
Note: The exact cap that is applied depends on the cap settings configured at the location and/or asset level. If asset-level capping is enabled, the asset's capping configuration is used to determine when charging should stop.
Case: If the asset cost continues to increase beyond the configured cap value, despite the cap settings being configured correctly, this may indicate an unexpected system issue.
Recommendation and workaround (optional):
If the cap value is not being applied as expected:
If the cap value is not being applied as expected:
- Verify that Cost Capping is correctly configured for the asset and/or location.
- Edit and save the asset's capping settings again.
- Wait a few minutes to allow ON!Track to recalculate the asset charges.
Re-saving the capping configuration often triggers the capping calculation again and may resolve the issue.
If the asset cost still exceeds the configured cap value after re-saving the settings, create a support ticket for the Customer Advocate Team for further investigation and correction.