An OpenBuildings Civil Structural user may need to reference an iTwin model of a bridge design. The OpenBuildings user may need to represent the concrete of the bridge in section with a concrete hatch including unification of separate concrete objects. The iTwin has no concept of Parts and Families and therefore cannot write this information to the iTwin model in order to resymbolise the objects, and in turn cannot represent the bridge from the iTwin in the correct way in drawings.

Mining / Plant needs to reference a piping model together with structural model for drawing production. By default, structural objects have Parts and Families applied to them, because they are produced in OpenBuildings, but piping models are produced in other software such as OpenPlant, which has no concept of Parts and Families. The user cannot apply Parts and Families to OpenPlant objects (it’s not their right to do this to the data of others or its different formats) plus its constantly changing and this process over and over again is too time consuming. An override feature where like Display Rules, which overrides the appearance, is required.

An architect references a Rhino or IFC file and needs to resymbolise concrete objects so in section or plan, the concrete is resymbolised with a concrete hatch that uses unification. Since the Rhino or IFC files are constantly changing or being delivered and referenced, the Architect needs an override, and cannot write to the Rhino or IFC file.