Bridge Box — the enterprise content cloud for contracts, correspondence and client sharing — and Trimble Connect, where structural and MEP engineers collaborate on models. DMS Sync Manager keeps documents and IFC models flowing both ways on a schedule, no manual download-upload loop.
Three steps to keep Box and Trimble Connect in sync.
Box authenticates with OAuth 2.0 against your Box enterprise. Trimble Connect authenticates with OAuth 2.0 via Trimble Identity (TID). Both connections are project-scoped and stored encrypted at rest.
Pick a Box folder as the source (or destination) and a Trimble Connect project + folder on the other side. Box metadata templates map to Trimble custom attributes, with direction set per sync task.
Filter by file type (IFC, DWG, RVT, PDF), Trimble revision label, label, or last-modified window. Schedule hourly, daily, or on demand. Each sync run produces a full activity log.
A few real-world scenarios.
"Projects rarely fail in design — they fail when teams can't trust they're looking at the latest version."
Yes. IFC 2x3, IFC 4 and IFC 4x3 pass through unchanged — bytes-identical at the destination. The file body is preserved; only metadata mapping is configurable.
Yes. Each sync task lets you map Box metadata template fields to Trimble Connect custom attributes and vice-versa, so both stay searchable on the same fields.
Box uses OAuth 2.0 against your enterprise; Trimble Connect uses OAuth 2.0 via TID with refresh tokens. Tokens refresh automatically; users authenticate once during project setup.
DMS Sync uses Box's chunked upload sessions for files over 50 MB, so multi-gigabyte IFC and RVT models transfer reliably. Throughput depends on your Box enterprise limits.
Sync workers run in eu-west-1 (Ireland). Files transit through the workers but are not retained; only metadata and audit logs are stored. For Box itself, EU data residency is available via Box Zones.
Book a demo and we'll walk you through setting it up for your project.