DABACON Elements Matching

DAtaBAse CONtrol Program (DABACON) elements are matched for mapped types. Design and schematic types are fixed for each source group. Type mapping for UDETs is as per their basetype.

Engineering types are all UDETs with basetype ENGITEM. Each source group can have one or more UDETs mapped against it. For example, the Engineering Equipment group may have :ELECEQUIP and :MECHEQUIP both mapped.

Note:
For valves and piping specials, only named elements are compared. Unnamed elements are considered to be bulk items.

Note:
Compare/Update is not able to insert Valves and Piping Specials as the insertion point for such items should be considered carefully and appropriate items created using the relevant application, for example: Design Pipework.

By default, matching of all elements is by Name.

The recommended alternative for matching of pipelines to pipes is by key attributes, to support the one to many relationships where one pipeline (schematic or engineering) may be modelled in 3D as multiple pipes. Key attribute matching uses a combination of several attribute values to identify matching 3D pipes for a source schematic or engineering line. For example, several pipes may be matched to a single line according to their values for line number, bore, pipe specification and duty. Key attribute matching must be set up using Options.

Note:
When working with many to one matches (such as would occur in Tags using key attribute matching to compare engineering lines against Design Pipes), Compare/Update is not able to insert or update elements. The only permitted operations are link and unlink.

Note:
If elements have been linked, this takes precedence over the rules for matching. Linked elements will be treated as matched even if, for example, their names have been changed so they no longer match. For further information, refer to Linking.

Has Parts Creation

If parts information is supplied using a parent-child configuration, parts are created using this information. If not, by default has parts is created.

When a parts configuration or group configurations with association information are explicitly created, no duplicate has parts is created.

Note:
Has parts can be created in conceptual model enabled/not enabled Projects.

If a tag that is a child in a parent/child configuration (and that has a value for HasParts or CanHaveParts), is moved to a different parent, then that movement is reflected when Compare/Update is re-run. However, before updating the database, you are prompted to remove from the configuration the association between the child and its original parent. Otherwise, you cannot proceed.