Usage and Costs
Usage and Costs
Understanding Allocations
Trimble Cloud Core Platform is funded through internal Trimble allocations in partnership with Trimble’s business areas. The Core Platform team has validated the following cost recovery model with sector leads and controllers, utilizing our Horizontal QBR governance.
The allocation model for Trimble Cloud For Platform has two parts to it:
-
Baseline allocations are allocated to businesses based primarily on their software revenue. e.g. a business with primarily software revenue takes on a larger allocation than a business with primarily hardware revenue.
-
Usage-based allocations are allocated to businesses based on their usage rates of the Trimble Cloud Core Services. Businesses that use the services more pay more.
This model aims to:
-
Provide transparency into Trimble Cloud Core Platform usage and costs.
-
Provide simple billing models to allow sectors to measure and forecast costs versus the complex bills of public cloud providers.
-
Recapture Production costs. Activities in pre-production environments are not cost-recovered on a usage basis. Pre-production costs are covered within the baseline allocations.
-
Encourage best practices and cost efficiency of Trimble Cloud services.
This model ensures that the Core Platform can scale its cloud provider costs along with Trimble’s growth without tying our hands operationally through a fully fixed budget.
Allocation Summaries
To promote transparency, we publish monthly usage reports on a per-business area and per-service basis.
2025 Cost Recovery & Allocations
Methodology
-
For each Core Service, we’ve identified a Key Metric that is closely aligned to the value that the service provides.
-
Measure the usage of this Key Metric per business area.
-
Multiply the total cost to run the service in Production by the ratios of usage by business area.
API Cloud
Key Metric: Count of API transactions per month
Events Service
Key Metric: Count of events consumed per month
File Service & Data Ocean
Key Metric: Storage cost per application.
This accounts for intelligent tiering, where data that is accessed infrequently costs less to store.
IoT
Key Metric: Count of IoT messages per month
Processing Framework
Key Metric: CPU and Memory usage in seconds per month
Profiles & ProfileX
Key Metric: Count of Profiles and ProfileX API transactions per month
Trimble Identity
Key Metric: Count of sign-in events (all OAuth grant types) per application per month