2024 Trimble Cloud Core Platform Concise Long Range Plan (LRP)
3-year Strategic Plan Narrative (2024)
Author(s): David Kohler and Jared Bloch
Prior LRP: 2022 Trimble Core Platform LRP
Cloud Core Platform’s mission for Trimble has remained the same since its inception years ago. It continues to provide the functional layer required for Trimble’s Connect and Scale strategy to be successful. Cloud Core Platform is composed of many individual services. While many of these services can be individually adopted, the potential is fully realized by adopting the ecosystem these services support. To better communicate the ecosystem view, this LRP will focus on the intersection between the four missions the Cloud Core services are organized under: Enterprise Identity and Access Management, Customer and Enterprise Data, Functionality and Devices, and Robust Platform.

Strategy: Trimble is in the middle of an evolution as a company. The technologies, procedures, and practices that have made Trimble successful are being examined to determine if they meet the needs as Trimble embarks on this new chapter. This evaluation is disruptive but necessary. However, with a well-understood view of the desired end state, any challenges can be managed.
Trimble wants to be recognized first and foremost as a data company. This desire is a standard leadership message and is the central focus of the Segments’ 2024 LRP messaging.
But what kind of data company?
Trimble’s legacy was founded on the quality of its hardware portfolio and the precision with which it could measure the physical world. Fully leveraging this legacy is Trimble’s single most significant opportunity. Measuring the world generates a lot of data. However, supplying the hardware and software alone does not make Trimble a data company. Data must be discoverable, access-controlled, translatable, and secure to be actionable and valuable.
Cloud Core’s four primary missions provide the foundation to support this evolution.
Actionable information requires data to be discoverable.
The Data Strategy portfolio provides the foundational services for capturing data and making it discoverable. IoT is a significant data pipeline, File Service is an enterprise data lake for data storage, and Data Operations (warehouse, catalog, BI) make data queryable.
Data is of little value if it can not be access-controlled or sharable.
The Enterprise IAM portfolio is Trimble’s foundation for data access control. Our customers expect Trimble to be good stewards of their data, which means access is authorized only when it is supposed to be. Further, the context for access control is in the mission of IAM: How are users, devices, and their data contextually related to customer accounts, licensing, and entitlements? This data is being made available within the services within the Data Strategy portfolio.
Valuable data outcomes require translatable data.
Trimble’s solutions generate a significant amount of raw data. This data almost always requires some data transformation (ETL) to extract meaningful value or build downstream more valuable data. Cloud Core’s Functionality and Devices portfolio allows Trimble and its customers the foundation to create insights from this raw data at scale.
Data must be secure to be relevant.
Broken trust is hard to repair, and it only takes one incident to cause irreparable harm. Making the investments required to deliver a secure platform is rarely considered the top priority, However, a secure data platform is an advantage. As Trimble embarks on challenging but rewarding security and compliance programs, including FedRAMP, it opens its door to exclusive opportunities.
The interplay between these missions cannot be understated. Each depends on the others. Discoverable data requires access control, data transformation (ETL), and robust controls. IAM requires enterprise data, such as customer 360 data, to provide context for access control. Data translation requires access to discoverable data as input, and its output is a new and even more valuable asset.
This interplay is the foundation of an ecosystem.
An ecosystem is characteristic of our platform strategy.
The next pinnacle of our platform strategy is our data strategy.
The Cloud Core Platform teams are putting this into action. Understanding that Trimble’s unique advantage is bridging the physical and digital worlds, the Field to Cloud initiative is focused on making the data from the field actionable and valuable. This begins with field connectivity so that devices natively send data to the cloud. From there, the Field to Cloud initiative will direct its focus on creating workflows that deliver derivative and downstream value. Further, the Core Platform underpins Trimble Connect. Terabytes of project data are stored in Connect’s file services backed by the Core Platform. Connect’s data transformation runs on top of Core Platform’s processing services. Finally, the Core Platform team emphasizes workflow orchestration as we combine the powerful data transformation capabilities across Trimble, including App XChange, our strategic partnership with Safe Software FME, and moving Trimble’s decades of intellectual property into cloud-enabled functionality.
Specifically, Cloud Core Platform will achieve this by delivering the following services to Trimble sectors:
-
Enterprise Identity and Access Management - This mission is supported by the following services: Customer Data Hub (CDH), Trimble Identity (TID), Profiles, Invitation Service, Transactional Email Service, and Trimble Access Management (TAM). This mission is mutually dependent on Entitlement (EMS) and Account Portal (AXP). Both of these are managed under the Digital Transformation organization.
- Vision:
- Managing access to Trimble’s portfolio’s entire suite of capabilities will be frictionless from both the individual users’ and account owners’ perspectives.
- Strategy:
- Major progress was made in consolidating the capabilities that make up this experience, but more still needs to occur. The consolidation provides the ability to present a unified experience to the user/account. This effort also allows Trimble to generate the foundational data to drive Customer 360 analysis.
- Strategic Value:
- This mission is crucial for any platform-focused company. By consistently managing access, users will be able to orchestrate their own experience with Trimble’s portfolio.
- Cost Model:
- The base funding is direct allocation. Significant extra usage is charged to the business/division that incurs it.
- Current Users/Adoption Plans:
- All of Trimble. See Collaboration Agreements for more information.
- Vision:
-
Data Strategy: Customer Data and Enterprise Data - This mission is supported by the following services: Business Intelligence (Domo), Data Hub, and Trimble File Service (next-gen Data Ocean). This mission is foundational to much of Trimble’s portfolio. However, it is valuable to specifically call out how critical it is to Trimble Connect, DX/Corp Finance, and MX (AECO Marketing).
- Vision:
- Customers trust Trimble to store their mission-critical data and can access it anywhere across its portfolio. Trimble can find and trust the integrity of customer interaction data across the portfolio to make educated decisions about our future direction.
- Strategy:
- Reconciling divergent customer data storage efforts is a significant win for Trimble. However, more work is needed to achieve the desired end state. Additionally, leveraging the infrastructure and expertise of the Core Platform team has helped ensure the early success of the AECO Marketing (MX) efforts.
- Strategic Value:
- This mission is foundational for an enterprise-wide data vision. A consistent way to manage customer and enterprise data will make achieving the discoverability and compliance requirements governing these assets easier.
- Cost Model:
- The base funding is direct allocation. Significant extra usage is charged to the business/division that incurs it.
- Current Users/Adoption Plans:
- All of Trimble. See Collaboration Agreements for more information.
- Vision:
-
Functionality and Devices —The following services support this mission: API Cloud, Cloud Console, Processing Framework, Events and IoT. This mission is foundational to much of Trimble’s portfolio. However, it is valuable to specifically call out how critical it is to Trimble Connect, AppXChange, Central AI, and Field Systems.
- Vision:
- Harnessing the limitless potential of seamless data movement to and from the field to the cloud is unlocked. Generating actionable insights efficiently from our and our customers’ data, regardless of where it was generated, is performed in a scalable (horizontally and vertically) way.
- Strategy:
- Converging Core Platform services and the AppExchange interface is an active effort. The combination will provide the accessibility, breadth of capabilities, and scalability that Trimble and its customers require in a workflow solution. To complete the Trimble connected ecosystem vision, the emerging field-to-cloud efforts will utilize this workflow solution and the data storage, IoT Gateway, and IAM services that the Core Platform provides.
- Strategic Value:
- Data connectivity and data transformation are instrumental to moving from data to information. By doing this in a consistent and re-usable way, we can speed up this transformation.
- Cost Model:
- The base funding is direct allocation. Significant extra usage is charged to the business/division that incurs it.
- Current Users/Adoption Plans:
- All of Trimble. See Collaboration Agreements for more information.
- Vision:
-
Robust Platform - Cloud Core Platform’s value is directly tied to the trust associated with its services. To address this, our development and operational procedures and policies are governed and structured to ensure high availability, deployability, resiliency and risk management standards are met. This governance is implemented via investment into the Cloud Core Platform Operations team to support four strategic governance pillars: Site Reliability Engineering (SRE), Compliance, Cloud Platform Support, and Sustainability.
The operational side of the Core Platform traditionally has little direct stakeholder value; the Services portfolio is the primary interface. So, the breakout for this mission has been culled. However, this team is leading significant Trimble-wide efforts: GeoIsolation Strategy, FedRAMP, and Data Retention Policy.
Three-year roadmap
| 2025 | 2026 | 2027 | |
|---|---|---|---|
| Identity and Access Management | Powering a rich AXP - account management of Users profiles and access Trusted, mastered data (with easy onboarding), enabling cross-product data sharing as the foundation of Customer 360 Support FedRAMP efforts (gov cloud deployable) | Customer Digital Experience Customer Analytics (for customers) IAM at the Edge (field to cloud) | Powering Trimble’s Marketplace (a Developer Community that sells) Enabling customer-defined, seamless cross-product workflows and analytics Enabling seamless external IAM (i.e. Azure AD) full integration (not just user authentication but roles, permissions etc) |
Leverage our Data:
| 2025 | 2026 | 2027 | |
|---|---|---|---|
| File Management (Connect File Service / Data Ocean) | Establish Connect File Service by doubling adoption in 2025 Fully integrated experience with Enterprise IAM Service Provide big data processing (AI/ML/DL) capabilities via the File Service. | Establish best practices and smooth collaboration when integrating products as bundles. Target End of life of DataOcean for cost/resource optimization | File Service is the default service to leverage in all Next Gen and greenfield initiatives across Trimble. |
| Data Operations | Establish data warehouse for Trimble MX Customer Data Platform (CDP) Product Data Domain data quality process enforce. Account Data Domain data quality process enforced. | ||
| IoT/Field to Cloud | Establishment of Field to Cloud (F2C) Standard Improvements to IoT Bootstrap Workflow and Documentation. Strategy for device data sharing e.g., wrt EU Data Act. | Adoption of F2C Standard within the sector. Acceleration of device onboarding within the sector (using Bootstrap) Execution items around device data sharing strategy. | Adoption and deeper integration of device data within sector products and services. |
Extend our Platform:
| 2025 | 2026 | 2027 | |
|---|---|---|---|
| Cloud Console and API management | Internal APIs and Events are available from one console. Console rationalization. Align Connectors as an additional integration type alongside APIs and Events. | APIs, Events, and Connectors available alongside each other to Trimble customers (Developer Program re-launch) | |
| Workflow Orchestration and Processing Framework | Combine AppExchange and Processing framework to generate a rich GTM offering. Full suite of Central AI functionality Expose Safe FME functionality. | Service serviceability to author workflows | Full Trimble IP functionality is available (i.e., Symphony). |
Enhance Cloud Operations and Governance for Products:
| 2025 | 2026 | 2027 | |
|---|---|---|---|
| Availability & Reliability | File Service DR regions available for -ALL- File Service regions. Customer Data Back-up for Connect supported for File Service. Distinct incident management for Processing Framework engines. Auto Recovery implemented for top service failure modes for three services. | AWS GovCloud PaaS portfolio for Federal account utilization implemented. (FedRAMP ATO for Core Platform) Auto Recovery implemented for top service failure modes for six services. Consolidation to a single observability platform | Auto Recovery implemented for top service failure modes for all services. |
| Compliance | ISO 27001:2022 Renewal SOC2 Type 2 Core Platform will achieve SOC2 Type 1 external attestation in 2024 and SOC2 Type 2 certification in 2025. NIST 800-171 Renewal Data Protection Framework Standards implemented in Core Platform EU Data Act Controls defined FedRAMP 2025: Trimble is initiating a corporate program cooperatively executed with the ATO Advisory firm Coalfire in Q3 2024. The program will drive to a core Authorization to Operate (ATO) for Trimble Core Platform. Within the same span, Trimble Connect will be the first FedRAMP Marketplace application inclusive within the Core ATO. The initial forecast for this ATO ATO span is 18-24 months following the start of the engagement (2H 2026). | ISO 27001:2022 Renewal ISO 27701:2019 Data Privacy SOC2 Type 2 Renewal FedRAMP 2026: Core Platform ATO w/Connect. | ISO 27001:2022 Renewal ISO 27701:2019 Renewal SOC2 Type 2 Renewal FedRAMP 2027: Another outcome of the Core ATO will be establishment of a FedRAMP common control and ATO inclusion managed service whereby other Trimble products may join the FedRAMP marketplace following the initial core authorization. |