Support for overrides would be a big productivity booster.

Overlaps with Ideas / worflows for:

1. Penetration Object level rules / configs.

Progressive refinement of low LOD rules into higher LOD rules via a 'parent - children' sub-classing workflow. The children rules would override parent rules but still be grouped under the parents, allowing the children to be bulk selected by selecting their parents.

2. Locking or freezing Penetrations.

This would override the default where the PO will be processed by any PM updates or Clash Detection runs.

3. De/Re-coupling Penetration objects to the Penetration Manager / Clash detection run.

a. Currently the PO can not be modified at all. There needs to be a way to de-couple the PO for manual mods without losing all the benefits of the PM, including tracking changes to the cutting / cut elements.

b. Overriding specific parameters / attributes would also be very useful. One example would be to overide the size of the PO whilst allowing the PM to position of the PO.

4. Bulk editing in Excel and re-synch.

Overlaps with use case 2 and 3b. Bulk editing in Excel needs to be managed for synching back to the PM and the model updates. Any overrides that do not align witn the assigned rules/configs need to be marked accordingly e.g. in blue, similar to Rendering convesion for local materials ?

5. Ad hoc Penetration Objects (instance not class type). A lot of users will end up just modifiying the PO to suit and will not bother changing the rule / config set defined at project level. The PM needs to be able to handle this graceful, allow controled de/re-coupling.