Data Transfer Tools

Every transfer is described by a rule. A rule reads documents from a source platform, runs them through a short pipeline, and writes them to a destination platform. Nothing moves until you say so, and you can watch every run.

Connectors are the platforms BIMMONT can read from and write to. Two are live today, with more on the way. Each live connector works in both directions, so either platform can be the source or the destination.

Connections live under Admin Integrations and are set up once per organization. After that, every project and register can use them. Both platforms use secure sign-in (OAuth), so BIMMONT never stores your password, and access can be revoked at any time.

Rules live under Admin Projects [project] Data Transfer. Click New rule and a short wizard walks you through it. A new rule is saved as a draft, so nothing transfers until you are ready.

By default a rule transfers everything in scope. Add filter groups to narrow it down. Each group combines conditions with ALL of (and), ANY of (or), EXCLUDE, or ELSE, so you can build precise “only these, never those” logic.

The Name Redactor reshapes a document’s filename for the destination and pulls structured values out of it at the same time. Mark each part of the name to take, leave, add or remove, and send the parts you take into destination attributes.

Field mapping takes care of the rest: set each destination field from a source attribute or a fixed value, with an optional transform. The mapping UI flags type mismatches before you run.

A rule runs one of three ways:

• Manual, runs only when you click Run now. The safest place to start.
• Schedule, runs on a fixed cadence: every few hours, or once a day at a set time (UTC).
• On change, watches the source and runs when something happens: a new version is uploaded, an attribute changes, a status changes, or a document is modified in a date range.

Every execution is a run, and every document in it is recorded with its outcome. Open a run to see exactly what transferred, what was skipped as a duplicate, and what failed and why.

The Aconex connector reads and writes documents, registers and metadata in Oracle Aconex.

Setup

1. In Admin Integrations, click Connect on Aconex and sign in through the Aconex Lobby.
2. Approve access. BIMMONT detects your region automatically and refreshes the connection in the background.
3. In a rule, choose the Aconex project, and optionally which registers and document types to include.

Good to know

• Aconex is metadata-first: a document is registered with its metadata before the file uploads, so the destination register’s mandatory fields and numbering scheme must be satisfied. Field mapping is where you set those.
• Filters and mapping read the live register schema, so disciplines, document types and statuses come straight from your Aconex project with the right labels and options.
• Re-running is safe: a document number that already exists is treated as a clean skip rather than an error.

The Autodesk connector reads and writes files, folders and custom attributes in Autodesk Construction Cloud (Autodesk Docs).

Setup

1. In Admin Integrations, click Connect on Autodesk and sign in. BIMMONT requests read, write and account access.
2. In a rule, pick the hub, then the project, then browse to a folder.
3. Choose a single folder to narrow scope, or stay at project level to include every subfolder.

Good to know

• Autodesk is file-first: the file uploads, a version is created, then custom attributes are written. Mapping failures on attributes never block the file itself.
• When a rule uses the new-version trigger, BIMMONT registers a real-time webhook so transfers can start within moments of an upload, with scheduled polling as a backstop.
• Writes are self-healing: if a file already exists, BIMMONT versions against it rather than failing, so a re-run never duplicates.

Data Transfer also feeds the Index module. Under Registers [project] Settings Data Transfer, you can bind a register to a transfer rule so that every document the rule moves automatically creates a row in that register. Bindings can be paused and resumed independently of the rule.