BS EN ISO 19650 provides a framework for information management that UK project and asset teams can adopt, with UK specific recommendations provided through the National Annex to BS EN ISO 19650-2. BricsCAD helps with drafting and model work, but it is not the CDE. This guide explains how BricsCAD Fits into an ISO 19650 Common Data Environment Workflow in plain UK terms.
A CDE is not just a cloud folder. It is the agreed source of information for a project or asset, supported by a managed workflow and one or more technical solutions used to collect, manage and share information.
It should manage:
In a UK ISO 19650 workflow, the CDE solution supports the agreed process and controlled information record. BricsCAD supports authoring and coordination, while the project’s information requirements, information standard, information production methods and procedures, and assigned responsibilities define how information is managed.
BricsCAD supports an ISO 19650 CAD workflow in four ways.
Make
Check
Share
Coordinate
This is the core of BricsCAD ISO 19650 practice.
WIP is the work zone.
This supports BIM document control in BricsCAD work.
Shared is for team use.
This is where BricsCAD project collaboration helps most.
Published is the state for information that has been authorised for its intended use.
Archive is the state used to retain a record of information development and CDE transactions.
One bad name can break the flow.
Use the information container identification convention agreed for the project. For a UK project following the 2021 National Annex, the identifier fields are:
Keep status, revision and classification as CDE metadata rather than adding them to the information container identifier.
In BricsCAD:
This helps BricsCAD common data environment integration.
In ISO 19650, status metadata communicates how an information container is permitted to be used. It should be assigned as part of the CDE process rather than treated as a BricsCAD export setting.
Good steps are:
Do not place unchecked WIP information in Shared. Information should enter Shared only after the required quality assurance, review and approval for sharin
Version and revision are not interchangeable.
To solve BIM file versioning conflicts:
Also:
These steps help manage BIM information exchange.
These are project authoring controls that can support consistent information production within an ISO 19650 workflow.
Check:
BricsCAD BIM collaboration features can help here.
A good pack may hold:
This is the heart of common data environment BricsCAD work.
IFC can become inconsistent if project teams use different export profiles or model settings.
Use one export set:
Use an agreed BricsCAD IFC export configuration for each required exchange. Define the IFC version and export profile, entity filter and relevant export options, and keep the model’s georeferencing, BIM classifications, IFC property sets and any export mapping consistent with the project requirements. Apply the project’s agreed information container identification, status and revision rules to the exported IFC.
Then:
ISO 19650 needs a clear record.
A strong issue tracking and transmittals workflow should show:
BricsCAD users can help by keeping the pack clean. Do not send a PDF update if the DWG is still old. Keep the title block and the CDE record in step.
Yes. BricsCAD can act as an authoring and coordination application within a wider ISO 19650 information management process. It can create CAD and BIM information, exchange BIM information through IFC in BricsCAD BIM, and connect directly to Bricsys 24/7. BricsCAD itself is not the complete CDE workflow or CDE solution.
It does not replace:
In BricsCAD vs Revit ISO 19650, the main rule is simple: the tool matters less than the process.
The same is true in BricsCAD vs AutoCAD BIM collaboration.
What stays the same:
What changes:
Choose the tool that fits your team, your budget, and your use case.
The best CDE platforms for BricsCAD should have:
Choose platforms that make naming, status, and approval easy. That is where the value sits.
Fix: use status rules and issue only clean work.
Fix: apply the project’s agreed information container identification convention to every deliverable. Related outputs should be traceable to one another, but different information containers may use different identifier values where fields such as Form differ.
Fix: agree on relative paths and pack rules first.
Fix: make the change rule clear to the team.
Fix: use only approved Shared files.
These fixes improve BricsCAD common data environment integration and cut rework.
The best way to use How BricsCAD Fits into an ISO 19650 Common Data Environment Workflow is to treat BricsCAD as a strong authoring node, not as the whole system.
BricsCAD gives you:
The CDE gives you:
When the two work together, teams get better bricscad project collaboration, better BIM information management, and fewer file clashes.
Question: Is BricsCAD itself a CDE?
Short answer: No. BricsCAD is an authoring and coordination application. The CDE workflow and its supporting technical solution or solutions manage controlled information states, access, metadata, review and records according to the project’s agreed information management rules.
Question: What should BricsCAD users do before they send files to Shared?
Short answer: Complete the task team’s quality assurance check, review and approval for sharing, then submit the required information containers to Shared with the agreed status and revision metadata. Include only the formats required by the project’s exchange information requirements.
Question: How can teams cut file clashes in a CDE flow?
Short answer: Use the CDE as the single source of truth, avoid local issue files, and use freeze windows when you compile a pack.
Question: What should a CDE platform offer for BricsCAD teams?
Short answer: It should give clear states, name checks, revision control, audit logs, review tools, transmittals, and support for DWG, PDF, and IFC.
