Autodesk Forma vs ACCA usBIM.platform: a comparison of CDE platforms for the digital management of BIM processes

Before comparing Autodesk Forma and usBIM.platform in detail, it is important to understand the context in which these two BIM platforms operate. While both solutions are designed to support Building Information Modeling (BIM) workflows, they are based on fundamentally different approaches. Autodesk Forma is part of a tightly integrated proprietary ecosystem, whereas usBIM.platform is built around open standards and interoperability, enabling greater flexibility across diverse software environments.

Within this open ecosystem, tools such as usBIM.sync facilitate the seamless synchronization of models and data between different applications and project teams, improving collaboration, coordination, and information consistency throughout the project lifecycle.

Understanding these differences is essential for selecting the platform that best aligns with project objectives, operational requirements, and the desired level of collaboration among stakeholders.

IN SUMMARY

The comparison is not simply between two individual tools, but between two different BIM platform strategies. Autodesk Forma is part of a proprietary, tightly integrated ecosystem that works seamlessly with Revit and other Autodesk solutions, whereas usBIM.platform is an openBIM, vendor-neutral ecosystem built on a modular platform with a wide range of integrated applications.

Autodesk’s main strengths lie in its native integration with Revit, Civil 3D, and Navisworks, as well as its widespread enterprise adoption and strong alignment with North American design and construction workflows. By contrast, usBIM.platform distinguishes itself through its commitment to openBIM standards, multi-software interoperability, and comprehensive support for construction execution, facility management, IoT, GIS, and digital twin workflows.

The adoption of open standards is not a regional or market-specific characteristic, but a strategic advantage for public authorities, infrastructure owners, engineering firms, contractors, asset managers, and organisations that require interoperability, long-term data accessibility, and vendor independence. These benefits extend across markets where IFC-based workflows are mandated—such as the Nordic countries, Spain, Singapore, and Italy—as well as private-sector projects involving multidisciplinary teams and heterogeneous software environments.

Ultimately, the right choice depends on the project context. For organisations operating within a predominantly Revit-based environment, the Autodesk ecosystem offers a highly integrated workflow with minimal friction. For projects requiring vendor-neutral collaboration, multi-software data exchange, and information management across the entire asset lifecycle, usBIM.platform provides a more open, interoperable, and future-proof approach.

Autodesk Forma and usBIM.platform: what are we comparing? Definition of CDE and BIM tools

In 2026, the comparison between Autodesk and ACCA’s offerings must be reconsidered in light of a major change: the rebranding of “Forma Industry Cloud”. Until 2023, “Autodesk Forma” mainly referred to the cloud-based early-stage design tool focused on site analysis, conceptual massing studies and environmental analysis.

With the official announcement of 24 March 2026, Autodesk extended the Forma brand to the entire AECO industry cloud ecosystem:

• Autodesk Construction Cloud (ACC) becomes Autodesk Forma;
• Autodesk Docs becomes Forma Data Management;
• BIM Collaborate Pro becomes Forma Design Collaboration;
• Build, Takeoff and Estimate become Forma Build, Forma Takeoff and Forma Estimate;
• the pre-design tool becomes Forma Site Design.

Autodesk states that this transition does not require mandatory migrations or changes to existing projects, permissions or workflows. Therefore, it is essential to distinguish between the individual components, because the term “Forma” may refer either to the entire Autodesk cloud ecosystem or to specific tools available within it.

The Autodesk ecosystem:

The following section lists the main components that make up Autodesk’s offering in the context of BIM and data management:

• Forma Site Design: an early-stage design tool for geolocated site analysis, massing studies and environmental assessments related, for example, to sunlight, shadows, wind and noise. It is not a CDE: it is a pre-design/schematic design tool positioned before BIM authoring, with connections to Revit and Rhino;
• Forma Data Management: formerly Autodesk Docs, it is the document-based CDE of the Forma ecosystem. It manages storage, visualisation, versions, issues, approval workflows, metadata, naming conventions and document exchanges, with different capabilities available across the Essentials and Full levels;
• Forma Build, Takeoff, Estimate and Design Collaboration: cover design collaboration, construction management, quantity takeoff, cost estimation and coordination workflows;
• AEC Collection: includes authoring and coordination applications such as Revit, Civil 3D, AutoCAD, Navisworks and InfraWorks;
• Autodesk Tandem: supports the creation and management of operational digital twins.

The ACCA software ecosystem

The following section lists the main components of the usBIM ecosystem and their role in managing BIM processes:

• usBIM.platform: the cloud-based Common Data Environment of the usBIM ecosystem. It supports the implementation of information management processes compliant with UNI EN ISO 19650 and openBIM principles and is the first IFC-certified CDE by buildingSMART International. The platform acts as the central environment for data management and sharing, where specialised applications within the usBIM ecosystem can be activated and used in an integrated way;
• usBIM: the BIM management system hosting dozens of integrated applications. Specialised applications and platforms can connect with the information environment and expand its use cases.

The ecosystem includes, among others, applications for:

• IFC model viewing with usBIM.browser;
• model federation with usBIM.federation;
• point cloud management with usBIM.pointcloud;
• model checking with usBIM.checker;
• clash detection with usBIM.clash;
• IFC editing with usBIM.editor;
• issue and non-conformity management with usBIM.resolver;
• BCF management with usBIM.BCF;
• definition and validation of information requirements with usBIM.IDS;
• connection to bSDD with usBIM.bsdd;
• comparison between models and point clouds with usBIM.compare;
• synchronous collaboration with usBIM.chat and usBIM.meet;
• GIS and geospatial digital twin management with usBIM.gis and usBIM.geotwin;
• sensor data and monitoring system management with usBIM.IoT;
• facility management with usBIM.maint and usBIM.facility;
• 4D planning with usBIM.gantt;
• quantity takeoff and 5D cost management with PriMus online;
• synchronisation between different CDE environments with usBIM.sync;
• digital signatures, blockchain, virtual reality and other functionalities.

Conceptual differences between Autodesk Forma and usBIM.platform in the BIM and CDE context

To correctly establish the comparison, it is useful to distinguish four increasingly structured approaches to information management.

• collaborative environment or file sharing: stores and exchanges documents asynchronously. Solutions such as Dropbox, Google Drive and SharePoint, when used simply as repositories, do not necessarily manage semantic relationships, approval processes or formal information states;
• BIM cloud platform (BIM collaboration platform): adds 3D viewers (IFC, RVT, DWG), markups, issues and model-based collaboration features, but does not necessarily implement the complete process for managing information states and approvals;
• Common Data Environment/ACDat: is not simply a software solution, but a governed process based on people (roles), processes (review, approval, publication) and technology, including state management, unique naming conventions, immutable audit trails and metadata that prevent the use of non-validated information (ISO 19650-1);
• integrated data management system: the most advanced level, where the platform does not only store file containers but manages data granularity, allowing users or AI systems to query and modify individual parameters (for example, the thermal transmittance of a window across an entire building complex) without opening the native authoring software. This is the paradigm both vendors are moving towards — Autodesk with the AEC Data Model API (GraphQL), and ACCA with usIFC.server technology and #TagBIM.

Forma Data Management and usBIM.platform perform the role of CDE within their respective ecosystems; Forma Site Design, on the other hand, is a pre-design tool and not a Common Data Environment.

Autodesk Forma vs usBIM.platform: comparison table

The table summarises the main differences between Autodesk Forma and ACCA usBIM, comparing architecture, CDE capabilities, interoperability, operational tools and application fields, in order to provide an immediate evaluation of the two platforms according to different BIM scenarios.

CDE functionalities: features and benefits for BIM management

Both platforms provide functionalities that support the implementation of information management processes aligned with the ISO 19650 series, but they adopt different architectures and operational approaches.

Document management and versioning

Forma Data Management manages documents, sheets and models with versioning and status codes. It treats files and folders as information containers.

usBIM.platform provides a customisable CDE with automatic versioning, project-based environment structuring, naming rules, recycle bin functionality and document events. A distinctive feature is the use of #TagBIM, metadata and keywords that classify and retrieve documents across the folder structure, together with the direct connection between documents and IFC objects.

The configurable modules of usBIM.resolver also allow users to associate model elements with data sheets, requests, issues, non-conformities, checklists and related management and resolution workflows.

This approach extends information management beyond simple document handling, allowing processes and information connected to BIM objects to be managed throughout the model lifecycle.

Permissions and roles

Both platforms implement role-based permissions and allow users to define access levels for folders, subfolders and documents, with permission inheritance throughout the Common Data Environment structure.

In ACC/Forma, authorisations ranging from view-only to full control are managed through the centralised user and organisation infrastructure of the Autodesk ecosystem.

usBIM.platform also enables differentiated permissions to be assigned and inherited across workspaces, folders, subfolders and individual documents, with user, group and organisation profiling.

In addition to document management, it provides the ability to configure specific permissions within workflows, distinguishing roles, responsibilities and permitted actions during the different verification, review and approval phases.

Traceability (audit trail) and data security

Both platforms record and retain a history of user actions, making changes made to content fully traceable.
The platform complies with security and privacy requirements, which are particularly relevant when managing large-scale assets, sensitive data, and critical infrastructure.

Approval workflows

ACC/Forma implements review and approval workflows (single-step and multi-step), issue tracking and transmittals, namely formal transmission records providing evidence of receipt.

usBIM.platform manages workflows through Quality Gate and document workflows that operationally implement the ISO 19650-2 CRA process (Check–Review–Approve), with sequential steps, assigned responsibilities, associated forms, notifications and historical records.

ISO 19650 information states

ISO 19650 structures the flow of information containers through the following states:

• Work in Progress (WIP);
• Shared;
• Published;
• Archived.

The granularity of these states can be valuable for any public or private client requiring formalised processes for information verification, approval and publication.

To understand how these aspects are applied in practice, it is useful to analyse the operational plan and compare how the two software solutions manage their workflows.

Autodesk Construction Cloud obtained the BSI Kitemark certification for compliance with the ISO 19650 framework (assessing Autodesk Docs, Autodesk Build and Model Coordination against the software-enabled requirements of the standard). The certification confirms that the platform provides functionalities capable of supporting ISO 19650-compliant processes; however, effective compliance depends on environment configuration, governance models and procedures adopted by the organisation.

usBIM.platform manages information states through active workflows with controlled transitions and complete traceability, supporting information review, approval, publication and archiving processes in accordance with ISO 19650 principles.

BIM ecosystem and software integrations

This section analyses how the two ecosystems manage integrations between authoring tools, cloud environments and connected applications.

Autodesk integration between authoring and cloud

The main value of the Autodesk ecosystem is the native integration between authoring tools and cloud services, reducing friction for users who already work with Revit, Civil 3D and AutoCAD.

Revit acts as a “Forma Connected Client”, while Forma Design Collaboration enables co-authoring through Revit Cloud Worksharing. Navisworks remains the tool for model aggregation and clash coordination, while Tandem uses models and data to support the operational digital twin.

Two recent technologies are particularly relevant:

• Autodesk Bridge: enables data sharing between Autodesk hubs belonging to different organisations. A subcontractor publishes content in its own hub and the model is synchronised via “push” to the general contractor’s hub, while preserving security policies and data ownership — providing a concrete response to the issue of data sovereignty;
• AEC Data Model API: uses GraphQL to make cloud-based data derived from authoring files queryable. Instead of simply transferring monolithic files, developers, analysts and artificial intelligence systems can query information at a more granular level and use it within dashboards or management systems.

Integration of usBIM applications

ACCA software’s approach follows a logic based on an integrated platform and application ecosystem.

usBIM.platform represents the CDE core, to which dozens of applications (both free and paid) can be added according to project requirements. These applications share the same cloud environment and IFC standard. A design firm can start with only the free viewer/CDE and later add clash detection, model checking, 4D, 5D, FM, GIS or digital twin functionalities when required.

Collaboration includes synchronous tools (usBIM.chat, usBIM.meet) that allow teams to navigate and work together on the same federated cloud model.

From a data management perspective, usIFC.server technology enables direct cloud-based editing, validation and federation of IFC attributes without returning to the native authoring environment.

usBIM also interoperates with proprietary file formats (RVT, DWG, SKP) in addition to IFC.

A particularly relevant recent technology is usBIM.sync, a bidirectional and cross-platform synchronisation service that keeps files, IFC models and metadata aligned (side-by-side version comparison, synchronisation status per file, alignment/conflict messaging) between CDE environments from different vendors. It can connect:

• Autodesk Forma/Autodesk Construction Cloud;
• Bentley ProjectWise;
• Trimble Connect;
• usBIM/usBIM.platform;
• cloud storage environments (Google Drive, Dropbox, OneDrive, Microsoft SharePoint);
• local PCs;
• Dassault 3DEXPERIENCE is included in the roadmap.

The underlying principle of this technology is not simply to “move files between CDEs”, but to bring openBIM functionalities (IFC/BCF/IDS/bSDD, clash detection, code checking, data quality) and GIS integration with Esri ArcGIS into the CDE and authoring environments already used by teams, synchronising governed openBIM data when collaboration extends beyond the WIP boundary of a single discipline.

Operational impact of BIM CDE platforms: differences between Autodesk Forma and usBIM.platform

Within the Autodesk ecosystem, users work with separate but strongly integrated modules:

• Forma Data Management for the CDE;
• Forma Design Collaboration for co-authoring;
• Model Coordination and Navisworks for coordination;
• Forma Build for RFIs, submittals and construction activities;
• Tandem for the operational digital twin.

This results in a vertical workflow chain that is particularly efficient for processes based on Autodesk tools.

In usBIM, the experience is organised as a system of web applications integrated within the same environment, activated from the app store around the central usBIM.platform CDE. The approach is therefore based on a horizontal and modular platform, open to different software solutions, formats and use cases throughout the entire asset lifecycle.

For designers, Autodesk reduces friction in Revit-centred workflows, while usBIM facilitates multi-software collaboration and the coexistence of multiple CDE environments within the same project through usBIM.sync.

For contractors, ACC/Forma provides an established construction management system; usBIM, instead, integrates openBIM-based construction management, issues and non-conformities, 4D planning, quantity surveying and cost management with PriMus, as well as safety management with CerTus.

For public and private clients, contracting authorities and asset managers adopting openBIM processes, usBIM is structured around a governed ACDat and enables the connection between information requirement validation through IDS and semantic standardisation through bSDD.

During the operational phase, the entire ecosystem must be considered:

• Autodesk Tandem supports the creation and management of the digital twin within the Autodesk environment;
• usBIM combines usBIM.maint and usBIM.facility for asset management, maintenance activities and operational indicators;
• usBIM.IoT connects sensor data and monitoring system information to the model;
• usBIM.geotwin integrates BIM information, territorial data and GIS.

The comparison concerns two different architectures for digital twin and asset management: one integrated within the proprietary Autodesk technology stack, the other modular, openBIM-based and oriented towards interoperability with heterogeneous systems and information sources.

IFC, openBIM and BIM data management

This section explores the role of open standards and data management approaches within BIM processes.

Open formats and IFC

The philosophical difference between the two ecosystems emerges most clearly in the management of data formats.

IFC is an open and vendor-neutral standard (ISO 16739), BCF is an open format for model-based issue communication, IDS enables the definition of automatically verifiable information requirements, and bSDD supports shared classifications and meanings.

ACCA uses IFC, BCF, IDS and bSDD as structural components of its ecosystem. usBIM.platform is IFC-certified by buildingSMART International, and usBIM applications cover IFC data visualisation, editing, checking, validation and federation. According to buildingSMART, ACCA has the highest number of IFC-certified software solutions worldwide, became an official member in October 2018 and a Multinational Member on 7 February 2022.

Autodesk supports IFC through visualisation, import, export and Data Exchange capabilities, while the RVT format maintains a central role in Revit-based workflows. In some markets, RVT format is also required as a contractual deliverable, leading to operational standardisation around the same software environment.

openBIM process, IFC, IDS, bSDD, BCF

Interoperability and federation

Both ecosystems enable the aggregation of multidisciplinary models:

• usBIM.federation: federates IFC models from different disciplines and applications directly in the browser;
• Navisworks and Model Coordination: aggregate and coordinate models within the Autodesk environment.

Model checking and information requirements

Within the usBIM ecosystem, QA/QC activities are distributed among complementary tools:

• usBIM.checker performs quality checks on BIM and IFC models, verifying properties, Property Sets and data consistency;
• usBIM.clash identifies geometric interferences, including hard clashes, tolerance-based clashes and clearance clashes, and supports their management through BCF;
• usBIM.ids is dedicated to managing information requirements according to the buildingSMART IDS standard. It allows users to define, in a structured and machine-readable format, which information must be included in the IFC model and automatically verify compliance.

In the Autodesk environment, model checking is managed through Navisworks and Model Coordination. Based on the functions analysed in this article, no native Forma module specifically dedicated to the creation and validation of IDS specifications equivalent to the complete usBIM.IDS toolset has been identified, although validation tools and partner applications can be used.

The BIM-GIS information layer

The value of BIM–GIS integration does not depend only on the geometry transferred into the geographic environment, but also on the quality and standardisation of the data associated with objects.

A spatial query, for example “which buildings within 200 m of a school have a fire resistance rating lower than R60”, can only provide reliable results if each object contains consistent and comparable attributes.

IDS enables users to specify which properties must be included in IFC models, while bSDD can support their shared semantic interpretation.

usBIM.sync and usBIM.geotwin represent the point where territorial data is validated against a common IDS and made “GIS-ready”, with continuous updates as source models change. This represents the operational implementation of the data-over-geometry principle.

Data accessibility throughout the lifecycle

This is perhaps the most significant difference, as it concerns the moment when the model stops serving designers and starts serving those who manage the asset.

ISO 19650-3 formalises the transition from the PIM (Project Information Model), produced during design and construction, to the AIM (Asset Information Model), which supports operational management and is updated throughout the asset lifecycle following events such as repairs, replacements and refurbishments.

The usBIM ecosystem is designed to support this entire lifecycle with data always accessible in open formats, while Autodesk covers the journey from concept, through Forma Site Design, to the operational phase with Tandem.

Long-term data persistence in proprietary formats remains an open issue. Two technical aspects are particularly relevant:

• IFC export from proprietary authoring software is a translation process that may result in the loss or transformation of certain information;
• open formats guarantee long-term reusability independent of the supplier, which is why an increasing number of governments require IFC delivery in public procurement processes.

Areas of use: BIM use cases and applications

This section analyses the main application areas of the two platforms, highlighting how they fit into the different stages of the BIM process.

Design

Autodesk provides a significant advantage in the design phase thanks to Revit, Civil 3D and the continuity between Forma Site Design and its authoring tools.

ACCA offers software solutions such as Edificius and EdiLus, but the value of usBIM.platform mainly lies in its ability to operate as a CDE regardless of the authoring software adopted.

BIM coordination

Both ecosystems provide mature tools for BIM coordination.

When the workflow is centred around Revit and Navisworks, Forma reduces the number of steps between authoring and cloud collaboration. When the project involves models produced with different applications, usBIM makes coordination more explicit through IFC federation, clash detection, model checking and BCF-based workflows.

Site supervision and construction management

usBIM.resolver manages construction site issues and non-conformities through traceable processes linked to BIM objects.

usBIM.compare compares the as-is condition using point clouds, including those generated through drone photogrammetry surveys, enabling comparisons between:

• point cloud and point cloud;
• point cloud and design model.

Integration with usBIM.gantt makes it possible to objectively measure construction progress and verify the as-built condition against the design.

PriMus-IFC allows quantities to be automatically extracted from the model, significantly improving progress monitoring and the management of construction payment certificates (SAL) during execution.

On the Autodesk side, Forma Build, Takeoff, Estimate and BuildingConnected provide a mature and widely adopted construction management environment, particularly in North America, covering RFI, submittals, daily logs and cost management.

The two ecosystems are strong in different areas:

• usBIM in openBIM, data-centric execution workflows, connecting models, surveys, quantity takeoff and construction processes;
• Autodesk in the breadth and adoption of enterprise construction management solutions.

BIM and construction analysis dashboard

Facility management and asset management

During the operational phase, facility managers, maintenance teams and asset owners mainly work with CAFM/CMMS platforms, ERP systems, BMS and asset management solutions rather than with the authoring software used during design. Therefore, the value of the BIM model depends on the ability to transfer and maintain structured, updated and interoperable data across these systems.

Handover should not simply consist of delivering the coordination model used during design and construction. It is preferable to create an Asset Information Model optimised for operations, streamlined by removing unnecessary geometric information and enriched with data useful for maintenance, such as asset identifiers, manufacturer, model, serial number, warranty information, technical documentation, maintenance schedules and intervention history.

Data exchange with management systems can be performed through open formats and structures such as IFC and COBie, avoiding dependence on the native format of the authoring software.

From an operational perspective, usBIM.maint and usBIM.facility allow users to manage assets, requests and maintenance activities directly on 2D drawings, BIM models and maps, associating tasks, documents, SLAs and KPIs with building elements. Integration with usBIM.IoT also makes it possible to connect assets with data coming from sensors, building systems and monitoring solutions, updating the digital twin with real operational information.

Building project lifecycle

Autodesk Tandem follows a similar approach focused on the operational digital twin, aggregating BIM, MEP and IoT data within the Autodesk ecosystem.

The comparison therefore concerns two different approaches to digital asset management: usBIM prioritises a modular and openBIM structure, capable of integration with heterogeneous systems; Tandem enhances continuity with models and services within the Autodesk environment.

Advantages and limitations of Autodesk Forma and usBIM.platform: a complete comparison

The main advantages of the Autodesk ecosystem include:

• native and seamless integration with widely adopted authoring tools (Revit, Civil 3D, Navisworks);
• widely adopted construction management solutions, especially in the USA and English-speaking markets;
• enterprise architecture, security controls and user management extended across the entire Forma platform;
• Autodesk Bridge for data sharing between hubs while maintaining data ownership and governance;
• BSI Kitemark ISO 19650 certification related to software functionalities supporting ISO 19650 processes;
• evolution towards cloud-based data models queryable through the AEC Data Model API.

The main limitations of the Autodesk ecosystem include:

• the RVT format maintains a central role, resulting in stronger vendor dependency and potential lock-in risks;
• maximum value is achieved by adopting an ecosystem distributed across different modules and licences;
• access to the complete set of tools may be challenging for smaller organisations;
• the “Forma” rebranding may initially create confusion between the name of the entire cloud environment and individual applications;
• openBIM coverage is not uniform across all modules and operational workflows.

The main advantages of the ACCA software ecosystem include:

• openBIM vendor-neutral approach and buildingSMART IFC certifications (the highest number of certified software solutions worldwide);
• IFC/BCF/IDS/bSDD as structural components of the ecosystem;
• coverage of design, construction, quality control, facility management, IoT, GIS and digital twin workflows;
• issue and non-conformity management through usBIM.resolver;
• construction progress monitoring through model and point cloud comparison with usBIM.compare;
• 4D planning with usBIM.gantt;
• quantity takeoff and construction progress control with PriMus-IFC;
• synchronisation between CDE platforms from different vendors through usBIM.sync;
• connection between documents, data and IFC objects;
• information management through #TagBIM, workflows and integrated applications.

The main limitations of the usBIM ecosystem include:

• lower international adoption and a smaller presence in enterprise construction management outside Europe compared with ACC/Forma;
• a proprietary authoring ecosystem (Edificius/EdiLus) that is less widespread;
• the wide range of available functions requires careful selection and activation of the applications best suited to each use case;
• enterprise pricing available upon request.

Which platform is best suited to your scenario?

The following table summarises the main guidelines to support the choice between the two platforms:

Autodesk Forma and usBIM.platform throughout the asset lifecycle

There is no absolute winner between Autodesk Forma and usBIM.platform. The two ecosystems represent two different approaches, and the right choice is not determined once and for all at organisational level, but according to the objective — who the stakeholders are — and the specific stage of the asset lifecycle. This is the criterion that reconciles all the comparisons analysed so far.

During the design phase, with a homogeneous Revit-based team, closedBIM is often the most rational choice. When all disciplines work within the same authoring environment, consistency eliminates conversion steps: real-time co-authoring (Revit Cloud Worksharing / Forma Design Collaboration) operates at element and workset level, allowing teams to work in the native format that preserves parametric constraints, families and relationships.

When a project involves different authoring software, openBIM becomes particularly important for federating models, coordinating disciplines and establishing a shared information foundation.

In construction management and especially during the operational phase, the logic changes. With the transition from the Project Information Model (PIM) to the Asset Information Model (AIM), the model must stop being an authoring file and become an information source that remains active for decades throughout the asset lifecycle, updated after each maintenance event. The stakeholders involved in this phase (owners, facility managers, asset managers, maintenance teams, inspectors and public authorities) use CRM, ERP, administration and accounting software, warehouse management systems, cost management solutions, CAFM/CMMS platforms for maintenance, IoT/BMS platforms and GIS systems. Linking the AIM exclusively to the design authoring environment would impose licensing costs, modelling skills and dependency on project professionals who are no longer involved in daily asset management.

The model data, on the other hand, must integrate with these heterogeneous systems: open formats (IFC, together with COBie, bSDD and IDS) make information interpretable by different applications, while proprietary formats can create data silos requiring conversions or middleware solutions.

At this stage, it is often more practical and cost-effective to modify or enrich the model directly in IFC — updating attributes, property sets, classifications, maintenance data and as-built information can also be managed through cloud-based IFC editors such as usBIM.editor, rather than returning to the native authoring environment and relying on design specialists. Returning to Revit remains justified mainly for substantial geometric or parametric modifications.

The key question for the BIM manager is therefore not “which software is better”, but rather “what phase am I in, who will actually use the model, and how much independence from proprietary formats is required throughout the lifecycle”. The most mature answer is almost always a hybrid approach, defined from the beginning: native authoring and collaboration within the Autodesk ecosystem during design, combined with the use of an openBIM CDE for multi-software coordination, handover and operations.

usBIM.sync is designed to support coexistence between different CDE environments and to use IFC, BCF and IDS as exchange and validation tools.

FAQ

What is the difference between Autodesk Forma and ACCA usBIM.platform?

Autodesk Forma is a proprietary, Revit-centric industry cloud (with Forma Data Management acting as a document-based CDE); usBIM.platform is a vendor-neutral openBIM CDE, IFC-certified by buildingSMART. Both cover the main pillars of an ISO 19650-compliant CDE; Forma Site Design, however, is a pre-design tool and not a CDE.

Is usBIM.platform an alternative to Autodesk Forma?

Yes. As a Common Data Environment, usBIM.platform can be considered an alternative to Forma Data Management. The choice depends on the operational context: a homogeneous Revit-based workflow benefits more from the Autodesk ecosystem, while a vendor-neutral environment focused on data governance and the management of the entire asset lifecycle may find a more suitable solution in usBIM.platform.

What is the best openBIM CDE?

For openBIM workflows, usBIM.platform is a reference solution: it is the first IFC-certified CDE by buildingSMART and supports the entire family of open standards (IFC, BCF, IDS, bSDD), with ACCA holding the largest number of IFC-certified software solutions worldwide.

Does Autodesk Forma support IFC and openBIM?

Yes, Forma provides IFC viewing, IFC Data Exchange and BCF import/export for issues. However, its core remains the proprietary RVT format and openBIM coverage is not uniform across all workflows.

Can Autodesk and usBIM coexist in the same project?

Yes. usBIM.sync enables bidirectional synchronization of files, IFC models and metadata between CDEs from different vendors (Autodesk Forma/ACC, Bentley ProjectWise, Trimble Connect, usBIM), as well as SharePoint, Google Drive, Dropbox, OneDrive and local PCs, using open standards as the common foundation for data exchange and interoperability.

Is closedBIM or openBIM better?

It depends on the project phase and stakeholders involved. During design, with a homogeneous Revit-based team, closedBIM reduces friction and avoids potentially lossy IFC exports. During construction and especially in the operational phase — when transitioning from PIM to AIM (ISO 19650-3) — openBIM is more practical because facility stakeholders do not use authoring tools and data must integrate with CAFM/CMMS, ERP, IoT and GIS systems.

What is the best CDE for public administrations and openBIM projects?

For public clients adopting openBIM processes, usBIM.platform is designed around the ACDat concept and open standards, with native ISO 19650 states, multi-level audit trails and GDPR/CISPE compliance. This represents a structural advantage wherever openBIM is adopted instead of closedBIM.

Are usBIM.platform and Autodesk Docs compliant with ISO 19650?

Autodesk Docs/Forma Data Management has obtained BSI Kitemark certification for ISO 19650, with full adherence to the Full tier.

Glossary of acronyms and sources

openBIM — a collaborative approach based on open and vendor-neutral standards (IFC, BCF, IDS, bSDD) for exchanging data between different software solutions.

closedBIM — a workflow based on proprietary formats and tools from a single provider (e.g. RVT within the Autodesk ecosystem).

CDE (Common Data Environment / ACDat) — a data-sharing environment governed by people, processes and technology to manage information states, revisions and approvals (ISO 19650).

PIM (Project Information Model) — the information model produced during design and construction phases (handover stage).

AIM (Asset Information Model) — the information model that supports asset operation, updated throughout the entire asset lifecycle (ISO 19650-3).

IFC — an open and standardized format (ISO 16739) for describing BIM data across different software solutions.

BCF — an open format for communicating model-based issues and comments.

IDS — a machine-readable standard for expressing and automatically verifying information requirements.

bSDD — the buildingSMART Data Dictionary that provides semantic meaning to classifications and properties.

COBie — a standard format for delivering asset data from BIM models to facility management systems.

Sources and references consulted

Official Autodesk documentation:

• “Autodesk Forma: the AECO Industry Cloud”.
• “Autodesk Forma Data Management, Formerly Autodesk Docs”.
• “Autodesk Forma Site Design”.
• “Autodesk Construction Cloud becomes Autodesk Forma”, Autodesk News, March 2026.
• “Document Management for Construction”.
• “Revit Becomes a Forma Connected Client”, official communication.
• “Announcing the General Availability of the Data Exchange Cloud Connector for IFC”.
• “Autodesk AEC Data Model API”, Autodesk Platform Services documentation.
• “Autodesk Tandem”.
• Autodesk University, “ISO 19650, the Common Data Environment and Autodesk Construction Cloud”.
• “Driving Digital Standards: Autodesk Construction Cloud Achieves BSI Kitemark Certification for ISO 19650”, Digital Builder.

Official ACCA software documentation

• “Common Data Environment: usBIM.platform”.
• usBIM.platform CDE User Manual, ed. 2.
• “BIM Management System: usBIM”.
• “IFC Viewer: usBIM.browser”.
• “IFC Checker and BIM Validation: usBIM.checker”.
• “Facility Management: usBIM.maint”.
• “usBIM.sync”, documentation relating to bidirectional synchronization, supported CDEs, GIS integration, ArcGIS, IDS, bSDD and ISO 19650.
• Official documentation relating to usBIM.resolver, usBIM.compare, usBIM.gantt.
• “PriMus-IFC”.
• BibLus, technical contributions relating to ISO 19650, Check–Review–Approve workflows, CDE, IFC and the role of the VDC/BIM Coordinator.

buildingSMART International:

• IFC Software Certification.
• “BIM Collaboration Format – BCF”.
• “Information Delivery Specification – IDS”.
• “buildingSMART Data Dictionary – bSDD”.
• buildingSMART International documentation relating to ACCA software membership, member since 2018 and Multinational Member since 2022.
• Global openBIM Mandates 2025 Edition.

Technical standards and regulatory references

• ISO 19650-1, Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) – Information management using building information modelling – Part 1: Concepts and principles.
• ISO 19650-2, Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) – Information management using building information modelling – Part 2: Delivery phase of the assets.
• ISO 19650-3, Organization and digitization of information about buildings and civil engineering works, including building information modelling – Information management using building information modelling – Part 3: Operational phase of the assets.
• ISO 19650-5, Organization and digitization of information about buildings and civil engineering works, including building information modelling – Information management using building information modelling – Part 5: Security-minded approach to information management.
• ISO 22057, “Sustainability in buildings and civil engineering works — Data templates for the use of environmental product declarations (EPDs) for construction products in building information modelling (BIM)”.
• UNI EN ISO 16739-1:2024, “Industry Foundation Classes (IFC) for data sharing in the construction and facility management industries – Part 1: Data schema”.
• UNI EN 15978, “Sustainability of construction works – Assessment of environmental performance of buildings – Calculation method”.
• UNI EN 15804, “Sustainability of construction works – Environmental product declarations – Core rules for the product category of construction products”.
• COBie, Construction Operations Building Information Exchange.
• UK BIM Framework, guidelines on the Common Data Environment and the application of ISO 19650-3 to the operational phase.
• Regulation (EU) 2016/679, General Data Protection Regulation – GDPR. CISPE, Code of Conduct for Cloud Infrastructure Service Providers in Europe.

Studies, specialist contributions and application cases

• AEC Magazine, “Autodesk Forma: one platform to rule them all?”, specialist article.
• AEC Magazine, “BIM by ACCA”.
• AUGI, “Myth Buster: Revit & IFC”, technical contribution.
• Autodesk and IFMA, Optimizing Building Management with a Lifecycle Approach, report.