Apparently, the PM can do selective updates by allowing the user to select the cutting (or cut ?) element. The PM records the associated elements ElementIDs, presumably. Any callbacks triggered by manipulation by Mstn/OBD tools are recorded by the PM, so a compute intensive Clash Detection run is not required.

Nevertheless, it would be useful to be able to trigger a localised Clash Detection run based on the selected element(s) only. This would pick up any new elements that have been moved and now intersect the selected element, including any elements in newly attached Ref files.... which will often not have stable ElementIDs or GUIDs.

Unusual to have all disciplines on Mstn-based apps, especially in the SME market.