Prior to the implementation of the CDW precedence rules, data published into SmartPlant Foundation from an authoring tool and consolidated was stored in the CDW using a "last in wins" approach. While the latest values for properties of objects published from any single tool were stored safely in that tool's domain, the CDW reflected that last data that was published for that object's property, regardless of which tool published it.
CDW precedence rules allow you to specify priority that each domain has for specific pieces of data. For CDW class definitions, interface definitions, property definitions, relationship definitions, or properties for specific class definitions, you can rank the order of priority to assign to each tool domain.
You can use these rules to specify behavior like the examples below:
-
Published data consolidated onto an SPFCDWBranchPoint object should prioritize data from Intergraph Smart® 3D over the other products that published data about that object.
-
Properties on the ISPFCDWPipingPortComposition interface should prioritize values from Smart Electrical, but all the other properties for the SPFCDWBranchPoint object should prioritize the data from Smart 3D.
-
The SPFCDWInstrGasketRqmt property should prioritize the value from the instrument datasheet over other values for that property. However, other properties on the ISPFCDWPipingPortComposition interface should prioritize values from Smart Electrical, and all the other properties for the SPFCDWBranchPoint object should prioritize the data from Smart 3D.
-
The nominal diameter value for ducts should prioritize the value from Smart 3D, but the nominal diameter for other objects should prioritize values from Smart P&ID.
Precedence rules are applied according to the following criteria:
-
Rules can be applied directly to any CDW class definition, interface definition, property definition, or relationship definition and the rule will apply to all instances of those schema objects.
-
By default, a CDW property definition or interface definition will inherit the precedence rules set on the higher-level schema object (interface definition or class definition, respectively).
-
If you apply a precedence rule to an interface or property definition using a tree to find that object from a higher-level object (such as a class definition or interface definition, respectively), the rules applied to the schema object will override any rule inherited from the higher-level schema object.
-
If you apply a precedence rule to an interface definition or property definition, the rule applies to all instances of that interface or property definition, for all objects. However, you can override the precedence rule on a property definition by applying a different rule to a property for a specific class definition.