The client should always own their data in some form. Whatever is implemented as a common data environment (CDE) on the project, there needs to be an end repository on the client side. The design team or the main contractor might own the CDE during the capital part of the project, but the client needs to adopt that data at the end of the day. Either way, the client needs to own it in their own repository.

Autodesk Construction Cloud addresses this using Autodesk Bridge. Your organisation can have its own ACC, and if the client or architect has their own separate ACC, Autodesk Bridge can control when information leaves their WIP area and enters the shared area. This ensures that each organisation can control their data, and both sides must approve the transfer.

Yes, it is possible with custom connections and implementations. If different platforms are used, we can map and align attributions. For example, if one team uses SharePoint and another uses ACC, we can translate data and attributions. However, there are limitations, especially when linking two ACC projects, as the attribution may not come across automatically.

Swim lanes are typically used between designers working on BIM models and are still relevant. Reviews still exist on projects because teams may share information that is not BIM models. It's about planning out workflows and deciding what to use on a project or organization level.

This is a common scenario. ACC can have an unlimited licensing model where clients can provide licenses to their supply chain. To put information into the system, everyone needs a license, and there are different levels of licenses available.

Yes, BIM should be implemented as early as possible in the design stage. Data requirements start at the conceptual design stage and build over time. The idea is to reuse data as the project progresses, ensuring that data is stored and accessible, promoting a single source of truth methodology.

BIM compliance is about structured data delivery, which is a methodology and process rather than technology. While AutoCAD can be used, Revit offers better visual properties for clash detection, coordination, and visualisation. Revit also hosts data better than AutoCAD. For ISO 19650 compliance, delivering a 3D model with interoperable data (IFC) is often required, which may not be achievable with just AutoCAD. Additionally, AutoCAD deliverables are still relevant, I use it for general mapping, site plans, line marking, etc. , things like Ordnance Survey maps still come in DWG format. However, AutoCAD doesn't have parametric capabilities like Revit, and attaching data to objects can be more difficult.

Yes, you can create any naming convention you like. For example, beyond the general ISO 19650 compliant naming, there might be Client specific metadata required such as delivery dates, other classifications, works packages, etc. which users can add in. We have both UK and Irish project examples, this is something we're happy to demonstrate and discuss further.

Who had access to what such as siphoning off commercial data , where is the data stored in terms of the server itself (the Autodesk Construction Cloud has a US, EU, and Australian server).

Yes, we have produced custom integrations to software such as Procore for seamless data transitioning, this is something we can help with.

Good question. I'd say, on it's own, no it isn't a proxy indicator. CDE usage in silo, isn't going to demonstrate aspects such as workflow efficiencies, correct implementation of the EIR, model data requirements aligned to the AIR, verification and validation mechanisms are adopted, etc. Experienced reviewers who are going to correctly scrutinise BIM & IT capability assessments is one gateway towards mitigation, however, there needs to be a level of monitoring between what one says during the tender stage and what one does during mobilisation and delivery. Please reach out for more information.

Fail is a strong word, I'd say "will cause disruption" and the consequence of this might be aspects such as inefficiency. Incorrect siloing of data, problems with accessibility, poorly thought out gateways leading to process bottlenecks, clear definition of where to go for latest published data, etc. are all areas that could be problems, no matter the technology used. It highlights the need to couple technology with process. Stress testing and piloting conforms to ISO 19650 requirements which help mitigate against failing CDE mechanisms and workflows. Please reach out for more information.

It depends on the task and the type of structure. Revit is good for component based items (lighting columns, structural slabs, precast concrete units, etc.) as it can perform activities such as reinforced concrete detailing. Civil 3D is great for surface creation (earthworks, topography, bathymetry, LIDAR) and linear structures such as embankments, roads, and rail. InfraWorks is really good for conceptual design and contextualising detailed design. These are all included in a suite of software call the Autodesk AEC Collection. This is something we can help you with if you'd like to discuss further.