iTwin Services Ideas

I've recently set up a workflow for our clash forms and I noticed in the Attachments tab it doesn't let you attach any files or documents from ProjectWise. This is a really big problem for a number of reasons.

• Breaks workflow continuity: If your team uses ProjectWise as the CDE, not being able to link directly to relevant documents (e.g. drawings, RFIs, specs) limits traceability.

• Manual workarounds: Users may have to download and re-upload files, which introduces version control risks.

• Missed integration potential: Bentley owns both platforms — this should be seamless.

Benefits:

• Maintains a single source of truth by linking directly to the latest documents in ProjectWise

• Eliminates the need to download and re-upload files, reducing duplication and errors

• Ensures that every clash issue is backed by relevant, version-controlled documentation

• Supports audit trails and compliance by linking to formally managed records

• Allows stakeholders to access supporting documents (e.g., drawings, specs, RFIs) without leaving the iTwin environment

• Reduces miscommunication by ensuring everyone is referencing the same files

• Cuts down on manual steps and file handling

• Speeds up clash resolution by providing immediate context to the issue

• Keeps all attachments within the approved CDE (ProjectWise), ensuring security and access control policies are upheld

• Avoids the risk of storing sensitive documents in unapproved or unmanaged locations

• Enables more complex workflows like automated issue tracking, reporting, and dashboards that rely on linked documentation

• Future-proofs your clash management process for larger or more regulated projects

• Demonstrates a fully integrated Bentley stack (iTwin + ProjectWise), showcasing the value of using their ecosystem end-to-end

Enabling this functionality would bridge a critical gap between issue management and document control, unlocking a more efficient and traceable clash resolution workflow.