Pre-Release Phase
Constraints
- Active device design, development, and procurement
- NO sales
Policies
✅ Every Trimble Device MUST use a tamper-proof secure hardware element for storage of confidential and cryptographic data (e.g. keys, credentials, and personal information).
❓Every Trimble Device MUST use the common Platform API for the registration and rotation of operational certificates (currently, the Bootstrap Service).
❓Devices MUST support over-the-air (OTA) firmware updates. Where not possible, devices MUST support local firmware updates through appropriate mechanisms.
✅ Every Trimble Device MUST support firmware updates on any firmware responsible for connectivity with Trimble.
✅ Every Trimble-Enabled Device SHOULD streamline its software integration footprint through use of shared libraries (e.g., Bedrock, “Side Car” agent, as appropriate for the use case).
❓Every Trimble Device SHOULD use components that have been validated by at least one Trimble development team and entered into a common “Trimble Certified” Hardware Component database.
✅ Every Trimble-Enabled Device with a user interface that carries the Trimble brand MUST follow the UX guidelines set by the Trimble UX Board.
❓Every Trimble Device MUST rotate device certificates in compliance with Trimble’s cybersecurity policy