How Do I Connect Asite and Autodesk Forma?

You connect Asite and Autodesk Forma with a CDE integration that moves documents, models and metadata between an Asite project and a Forma project on rules you set. CDE Syncâ„¢ links both platforms through secure API connections, maps Asite fields to Forma attributes and keeps the chosen folders aligned, so each organisation keeps its own platform while working from the same current information.

Why Asite and Forma end up on the same project

Asite is common among owners, developers and contractors, particularly in the UK and on public sector work. Autodesk Forma is common among design teams and contractors using Autodesk tools. When a client or principal mandates Asite and the delivery team works in Forma, documents have to be transferred and re-tagged constantly.

Doing that by hand means downloading from one platform, renaming files, re-entering metadata and uploading to the other. Transmittals have to be rebuilt, and reviewed documents have to be carried back. Every manual step adds time and the risk of a version mismatch.

What carries across

CDE Syncâ„¢ synchronises documents, models and metadata between Asite and Forma. Metadata fields are mapped automatically against the target platform's schema, and transmittal and version history are preserved across the sync. ISO 19650 naming and status fields are handled where the project uses them. Every transfer is logged for audit and compliance.

The connection can run one way, such as issued deliverables from Forma into the client's Asite workspace, or both ways so reviewed documents return to Forma with their outcome. The Asite and Autodesk Forma integration pages describe each connector.

How to connect Asite and Forma, step by step

  • Agree the exchange: which document types move from Forma into Asite, and what should come back.

  • Obtain the Asite workspace's metadata requirements and numbering rules from the client's document controller.

  • Arrange API access to Asite with your Asite administrator, and a Forma service account added to the delivery project.

  • Connect both platforms in the CDE Syncâ„¢ wizard and choose the folders on each side.

  • Map Forma attributes to Asite fields, including revision, status and document number.

  • Set the direction and schedule, then run a test exchange.

  • Review the results with the client and extend to the full scope.

When the goal is to leave Asite

Some organisations connect Asite and Forma because they are moving from one to the other. If the aim is a permanent move, an ongoing sync is not the right fit. CDE Migrateâ„¢ moves the whole record once, with version history, folder structure, metadata and audit trails intact, and brings issues, RFIs and defects across as part of the migration. Many teams run a sync during a transition period so live projects keep working, then complete the move with CDE Migrateâ„¢. Our article on migration or sync explains how to decide.

Agreeing the exchange with the client

Clients that mandate Asite usually publish an information protocol that sets out naming, mandatory metadata and review statuses. Reading that protocol alongside the delivery team's Forma setup shows where values need translating. A short session with the client's document controller to walk through a few real documents confirms the mapping before the first exchange. It is also worth agreeing what happens when a submission fails validation, who is notified, and how resubmissions are handled. With those decisions recorded, the configuration in CDE Syncâ„¢ reflects the client's requirements and stays easy to update when the protocol changes.

Security

CDE Syncâ„¢ streams files directly between Asite and Forma without storing them. Data is encrypted in transit and processed in the Azure region you choose. Utopia Digital holds SOC 2 Type II and Cyber Essentials, and the detail is on the Security Trust Portal. Available regions are on the global data region map.

Asite, Forma and the Utopiaverseâ„¢

An Asite to Forma connection is part of the Utopiaverseâ„¢, Utopia Digital's connected record across every platform. CDE Syncâ„¢ keeps both aligned, CDE Backupâ„¢ keeps an independent copy in your own Azure, CDE Migrateâ„¢ handles platform changes and CDE Archiveâ„¢ captures the record at completion. AI Insights then searches Asite and Forma content together, with answers that cite the source files. See also CDE Sync for Asite and How Do I Connect Oracle Aconex and Autodesk Forma?

See Asite and Forma connected in the monthly live demo, or talk to the team about your project.

Previous
Previous

Supply Chain CDE Integration: Managing Contractor Data Across Platforms

Next
Next

Automated Client Submissions: Eliminating Handover Risk in Infrastructure Projects.