I’ve noticed a challenge when creating issues on ACC views that incorporate models from published Revit views. Currently, the issue references the original Revit file, not the specific ACC view where the issue was created.
Context
- Our project—a large train station—uses very big Revit models that are slow to load in the ACC viewer.
- To address this, we rely heavily on coordination spaces and ACC views for efficient navigation and issue resolution.
- However, once an issue is created, it’s not possible to trace back to the specific ACC view used at the time.
Current Workaround
- We can add a custom “URL” field to manually input the ACC view reference, but this is an extra step and prone to user error.
Suggested Enhancement
- Automatically capture and store the ACC view reference (URL) when an issue is created.
This would ensure every issue is directly linked to the exact view context, improving traceability and collaboration.
Benefits
- Saves time: Removes the need for manual entry.
- Increases accuracy: Reduces the risk of incorrect references. Enhances collaboration: Team members can quickly jump to the relevant view for any issue, streamlining the review and resolution process.
This improvement would greatly enhance our workflow and support more effective issue management on large, complex projects.
