I've said it before on this forum, and I'll say it again. The premise of using Revit Published Views in Model Coordination is flawed.
In this instance, the flaw is when creating and reviewing Issues.
Because Model Coordination treats Revit Published Views as unique 'Models' (that's ACC terminology, not mine), elements that are found across multiple Revit Published Views from the same Revit model are also considered as unique.
e.g. A Revit model may contain three Published Views: 'All Levels', 'Level 1', and 'Level 2'. Levels 1 and 2 may have some deliberate view sectioning overlap between the views, and so an element may exist in both level views, and also in the all levels view.
The issue creator may be working with discipline model/views for an individual level. e.g. arch level 1, mech level 1, etc.
When they raise an issue, they are placing it on elements found within level 1 published views.
The issue reviewer may be working with discipline model/views for all levels.
When they review the issues list, they won't see the issues because they are technically viewing different models that has different unique elements.
In both of the above use cases, from a Revit perspective the element exists in both published view as a single unique instance.
But ACC Model Coordination treats them as multiple unique instances.
This disparity introduces a reasonable amount of design process risk into Model Coordination, whereby there is a reasonably chance that issues could be missed by the reviewer.
For this to function correctly, issues must be pinned to the originating Revit model element, not the published view element. This would ensure that issues are always visible regardless of which published view was used.
