Catenda Hub ↔ Dalux synchronization

Bridge Catenda Hub — the openBIM-native CDE — and Dalux — the construction-site DMS — without breaking the IFC openBIM workflow. DMS Sync Manager moves IFC models, drawings and metadata between the owner / coordination side and the site execution side on a schedule you control.

How it works

Three steps to keep Catenda Hub and Dalux in sync.

01

Connect Catenda Hub and Dalux

Catenda Hub uses OAuth 2.0 via Catenda accounts (REST API at api.catenda.com). Dalux uses an API key issued by your Dalux tenant administrator. Both connections are project-scoped and stored encrypted.

02

Map Catenda project to Dalux document area

Pick a Catenda project as the source (or destination) and a Dalux project + document area on the other side. Direction is per task; multiple parallel tasks support two-way behaviour with explicit anti-loop rules.

03

Filter by IFC + status

Rules filter by file type (IFC variant, PDF, DWG), Catenda revision, Catenda status (e.g. Approved), or last-modified. Schedule hourly, every 6 hours, daily or on demand. Each model push is logged with file size, source version and destination version.

What customers do with it

A few real-world scenarios.

  • Mirror Catenda-approved IFC models to Dalux so site teams open the latest coordination model on the iPad.
  • Push Dalux-issued site drawings back to Catenda so the owner team's openBIM coordination always reflects what's built on site.
  • Maintain a Dalux archive of every Catenda issued revision for handover and ISO 19650 information delivery.

"Projects rarely fail in design — they fail when teams can't trust they're looking at the latest version."

— BUCC

Frequently asked questions

Is IFC version preserved through the sync?

Yes. IFC 2x3, IFC 4 and IFC 4x3 pass through unchanged — bytes-identical at the destination. No conversion, no re-export, no loss of geometry or property sets.

Are BCF (BIM Collaboration Format) issues synced?

Not in this release. Catenda BCF issues stay in Catenda; Dalux Field issues stay in Dalux. The file / model layer is the scope of this sync.

How does this interact with Dalux Box vs Dalux Field?

This pair targets Dalux Box / Document — the document storage layer. Dalux Field (issues, snags, inspections) is independent of the sync.

Is this ISO 19650 / EN 17412 friendly?

Yes. The activity log records every file move with timestamp, source, destination and status — the audit trail an information management plan requires. End compliance depends on your Catenda and Dalux configuration.

Performance with large IFC files?

Catenda and Dalux both handle large IFC files natively. DMS Sync uses chunked upload where the destination API supports it; multi-gigabyte IFC models complete reliably within a single sync run.

Ready to sync Catenda Hub and Dalux?

Book a demo and we'll walk you through setting it up for your project.

  • Tailored to your Catenda ↔ Dalux setup
  • 30-minute session, no commitment
  • We handle the setup, you just show up
Book a Demo