Skip to content

Mandate 7: Common Customer Data Management

All customer data assets—files, objects, and big data—must be stored in or referenced by Trimble File Service and Trimble Connect.

  • A “Single Pane of Glass” is provided to customers, allowing them to see all their Trimble-managed data in one place.
  • Data Gravity is established, making Trimble the primary hub for construction information.
  • Cross-portfolio workflows are unlocked, as data is no longer “locked” within a specific application.
  • Customers can opt-in to applying Advanced AI (RAG) across their Trimble-hosted data, allowing customers to prompt against their entire project history.
  • Facilitates comprehensive data security, governance, and compliance by enforcing them uniformly and effectively.
  • Establishes clear, consistent data ownership and streamlines maintenance.
  • Adopt Trimble File Service for any customer blob data.
  1. Are your customer-facing data assets stored in or linked to the File Service?
  2. Does your application utilize the File Service for data ingress and egress?
  3. Can your unstructured data be discovered and referenced within Trimble Connect?

Currently, only 45% of Trimble Construction’s unstructured data resides in Connect/File Service. This means customers who use multiple Trimble solutions have data stored in separate, unrelated cloud file systems.

Read the File Service documentation to get started adopting the Trimble File Service.

Q: When should I use File Service vs. when should I use the Trimble Connect File APIs?

A: Use Trimble Connect when: Data is end-user facing, especially for the purpose of collaboration. If your product is part of the Trimble Construction ecosystem, and uses broader Connect collaboration features including Projects, BCF Topics, Unified Viewer, and Data experience, you should integrate via Connect APIs.

Use File Service APIs when data is hidden from end users (system or transient data). If you have a use case that does not integrate into the Trimble Connect ecosystem (for example, ERP).

Both use cases are supported today and will be consolidated under the Connect brand during 2026.