Searching Outside the Spec - Intergraph Smart Reference Data - Help - Hexagon PPM

Intergraph Smart Reference Data Help Classic (2020)

Intergraph Smart Reference Data
2020 (10.0)

Having the data in the spec is a design paradigm, but there are always exceptions from the rule.

In some cases, it is not known during creation of the spec which item will be used in a special case of branch, or the exact wall thickness of an item is unavailable. These problems can be solved by reading the missing information from the Smart Materials Process Line List (PLL).

Looking up the Process Line List (PLL)

The following is needed to use information in the PLL for FIND_IDENT:Creating a reference from BOM to PLL

First, a PLL reference is needed for the node in the BOM. To create such a reference, the BOM node must be of the node type that is given in the ZB_LS_LINE project default. The parent node must be of the node type given in the ZB_LS_UNIT project default. Additionally, the name of the BOM node must match the name of the line in the PLL, and the name of the parent node in the BOM must match the name of the unit in the PLL.

Consider the following example:

Project defaults:



BOM Hierarchy:

+- Some_Node (list type: IRRELEVANT)

+- Unit_Node (list type:UNIT)

+- Line Node (list type:LINE)

PLL Hierarchy:


Line in this Unit: "Line Node"

This configuration enables PLL lookup for material in the "Line Node". Note that the "Unit Node" in the BOM does not have to be a root node, but can be somewhere in the tree. Also, note that it is possible to apply the same reference for sub-nodes in the BOM. Searching idents for the "Here is my material" BOM node is valid and would refer to the same PLL node as in the above example:

BOM Hierarchy:

+- Some_Node (list type: IRRELEVANT)

+- Unit_Node (list type:UNIT)

+- Some other Node (list type: CHOOSEFREELY)

+- Line Node (list type:LINE)

+- Here is my material (list type:SOMETHING)

Note that the unit/line reference nodes in the BOM can be in a direct parent/child relation but it is not necessary, The node containing the material can also be somewhere higher in the tree.

Calculating the Branch Item

In the case that the item for a distinct header/branch size combination is not yet known, the branch filter table of the spec should contain a part that is in a commodity group with the name "CALC". This indicates that the information about which item to take should be derived from the PLL. FIND_IDENT will first find the referenced PLL node. Then it compares the nominal size of the FIND_IDENT call with the "Nominal Diameters" that are available in this PLL node. If a matching size is found, FIND_IDENT searches the "Branch" that matches with the second size in the parameter of FIND_IDENT (You maintain all this information on L 20.01).

If a match is found, FIND_IDENT takes the "Branch Type" for this branch and tries to find a "Short Code" (L 10.06). This short code will be the new short code to continue the search for an ident. For that, the short code has to be in the specification.

Calculating schedules

There are two ways to let the schedule be looked up from the PLL:

  1. Defining the schedules as ‘CALC’ in the BOM. This will force FIND_IDENT to refer to the PLL for schedule information.

  2. Defining ‘CALC’ in the filter tables instead of schedule or wall thickness. This will cause a lookup to the PLL for schedule information.

If the branch item was calculated (See the "Calculating the branch item" section), the wall thickness of the header and/or branch will be taken from the branch record on L.20.01 that also contained the information about the branch type.

Otherwise, the wall thickness is taken from the "Nominal Diameters" defined on L.20.01.