Configuration Items - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Integration (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Construction Version
8
Smart Materials/Smart Reference Data Version
10.1

The Item field contains the name of the configuration item that you want to supply with parameters. The available items can be selected from the LOV. The LOV automatically fills some of the other fields with defaults, so you can easily achieve a default configuration.

The configuration items in detail are as follows:

  • LINE_NUM - You can define the horizontal location of the line number. In the Value field, you can enter your line number title, which can differ from the literal 'LINE NUMBER' (the default). This information is used to identify a physical line in the report as line number information. If you do not use this configuration item, the standard PDS defaults are used. This configuration item is not used with "ISOGEN"-like formats.

  • LINE_TYPE - The line type defines which node type the line will have in the Smart Materials BOM. Choose from the available node types with the LOV in the Value field. The node type code is stored, not the internal ID. So the node type for every project can be the same. You must define this configuration item. There is no default by the software. This configuration item is not used with "ISOGEN"-like formats.

  • LINE_ATTR - You can have the interface interpret your line number and make node attributes of it. Specify the name of the attribute in the Value field (an LOV on attributes is provided), and enter the location in the Digit from/to fields. You can have more than one usage of LINE_ATTR by selecting this item for more than one row in the block. If you do not use this configuration item, the line number is stored in the short description and description of the node, and no node_attributes are generated. The attribute code is stored, not the internal ID. So the attribute code for every project can be the same. This configuration item is not used with "ISOGEN"-like formats.

  • LINE_SEP - If you choose to define relative locations, you can define the separator symbol within the line number in the Value field. If you omit this configuration item, the dash is taken by default. Refer to the description of the Type field for more information on defining relative or fixed locations. This configuration item is not used with "ISOGEN"-like formats.

  • POS_LEVxN - This configuration item is the name of the node level x where the material is to be stored. You can create up to ten levels (beginning from 0 to 9) from the start node defined on B.40.01. If the node does not exist in the BOM, it will be created. This configuration item is normally not used with "piping_g"-like formats.

  • POS_LEVxT - This configuration item is the type of the node level x where the material is to be stored. You can create up to ten levels (beginning from 0 to 9) from the start node defined on B.40.01. The node type is necessary when new nodes must be created within the BOM tree. This configuration item is normally not used with "piping_g"-like formats.

  • POS_CC - Enter the location of the commodity code in the Digit from/to fields. Trailing and leading blanks are cut off automatically. If you omit this configuration item, the defaults from PDS piping are used. Idents can be found with the commodity code and sizes. However, if the spec code (POS_SPEC) is supplied together with the commodity code and no short code is supplied, PDS BOM import will try to find a short code for this commodity code.

  • POS_IDENT - Enter the location of the ident code in the Digit from/to fields. Trailing and leading blanks are cut off automatically.

  • POS_OPTION - Enter the location of the option in the Digit from/to fields. Trailing and leading blanks are cut off automatically. If you omit the option, it defaults to 1.

  • POS_SHORT - Enter the location of the short code in the Digit from/to fields. Trailing and leading blanks are cut off automatically. If you do not have a short code in your file, the software will search for one with the spec code, option code, and commodity code. If there is nothing found, the software will receive an error. It is a good idea to define a short code "ERROR" on S.10.08. The software will then assign this short code to the item when no short code is found, and the import will succeed. You will be informed which line was not imported because ERROR was not in the spec.

  • POS_SPEC - Enter the location of the specification code in the Digit from/to fields. Trailing and leading blanks are cut off automatically.

  • POS_RTYPE - Enter the location of the record type in the Digit from/to fields. Trailing and leading blanks are cut off automatically. The record type influences the interpretation of the POS_QTY. This configuration item is normally not used with "piping_g"-like formats.

    If the RTYPE is PIPE or BOLT, missing quantities do not default to 1. If you do not specify an RTYPE, it defaults to BOLT. If the RTYPE is PIPE, the software appends a ".0" to integer quantities if no unit is specified. This ".0" makes the software assume a length unit for the quantity because of the decimal point.

    If the RTYPE is BOLT and the software fetches the commodity code with sizes from Smart Materials, the bolt also receives a second size (the bolt length) if input2 is numeric – regardless of whether the bolt is marked as a one-size or two-size item. Additionally, if there is an input2 (bolt length) in the ASCII file, the software will compare the input2 from the ident with the input2 from the ASCII file. If they are different, the software will try to find another ident within the same commodity code that matches the bolt diameter and length. If an ident is found, it will be used instead of the one originally coming from the ASCII file. If no ident is found, an error message is written to the job logfile, and the ident is erased. Instead, the BOM position will contain the commodity code, input1 (bolt diameter), and the new bolt length.

    If the RTYPE is COMP, the software converts the quantity to a number, if no unit is specified. This conversion cuts trailing zeros and makes the software assume a piece unit for the quantity because of the decimal point.

    To make the RTYPE noticeable to the software (which reads the lines left to right), the RTYPE must be defined to the left of the quantity or size2 in the ASCII file.

  • POS_QTY - Enter the location of the position quantity in the Digit from/to fields. Trailing and leading blanks are cut off automatically. If the record type (as far as the existing) is BOLT or PIPE, the quantity is set to zero if none is found on the line. If the record type is different, the missing quantity is defaulted to 1. If there is no record type, the missing quantities are left out. If you omit this configuration item (POS_QTY), the defaults from PDS piping_g are used.

  • POS_UNIT or POS_LUNIT - The OMI preprocessor does not know if a quantity is a piece unit (POS_UNIT) or if it is a length unit (POS_LUNIT).

    If the RTYPE is PIPE or BOLT, missing quantities do not default to 1. If you do not specify an RTYPE, it defaults to BOLT.

    If the RTYPE is PIPE, the software appends a ".0" to integer quantities if no unit is specified. This ".0" makes the software assume a length unit for the quantity because of the decimal point.

    If the RTYPE is COMP, the software converts the quantity to a number if no unit is specified. This conversion cuts trailing zeros and makes the software assume a piece unit for the quantity because of the decimal point.

    To make the RTYPE noticeable to the software (which reads the lines left to right), the RTYPE must be defined to the left of the quantity in the ASCII file.

    1) If the quantity is blank:

    • If the RTYPE is blank (for example, it is set to PIPE or BOLT), the quantity is set to 1 and the unit defaults to 'EA'.

    • MM is used if POS_LUNIT is blank.

    • EA is used if POS_UNIT is blank.

      2) If the quantity is not blank:

    • Any unit is used if it is appended to the quantity in the ASCII file. You can also use " to get the unit IN. Note that the unit is case sensitive.

    • POS_LUNIT is used if the quantity contains a decimal point as a separator (delimiter).

    • POS_UNIT is used if the quantity does not contain a decimal point as a separator (delimiter).

  • POS_SIZE1 - Enter the location of the 1st size in the Digit from/to fields. Trailing and leading blanks are truncated. If you omit this configuration item, the defaults from PDS piping_g are used.

  • POS_SIZE2 - Enter the location of the 2nd size in the Digit from/to fields. Trailing and leading blanks are cut off automatically. If you omit this configuration item, the defaults from PDS piping_g are used. This field is used for diameters, not for schedules. If you transfer schedules for some reason, and you supply a commodity code (POS_CC), the PDS BOM import will erase the schedule depending on the Zydex table in Smart Materials. (If an asterisk is on attr_char1 for the associated Zydex, the item is considered to have one nominal size, and size2 is set to zero.)

    If the RTYPE is BOLT, and the software fetches the commodity code with sizes from Smart Materials, the bolt also receives a second size (the bolt length) if input2 is numeric – regardless of whether the bolt is marked as a one-size or two-size item. To make the RTYPE to be noticed, the RTYPE must be defined left from the size2 in the ASCII file.

    Additionally, if there is an input2 (bolt length) in the ASCII file, the software will compare input2 from the ident with input2 from the ASCII file. If they are different, the software will try to find another ident within the same commodity code that matches the bolt diameter and length. If an ident is found, it will be taken instead of the one originally coming from the ASCII file. If no ident is found, an error message is written to the job logfile, and the ident is erased. Instead, the BOM position will contain the commodity code, input1 (bolt diameter), and the new bolt length.

  • POS_SIZE3 - Enter the location of the 3rd size in the Digit from/to fields. Trailing and leading blanks are cut off automatically. You only need this item to find idents for material that has more than one end and is to be found by commodity code and sizes.

  • POS_SIZE4 - Enter the location of the 4th size in the Digit from/to fields. Trailing and leading blanks are cut off automatically. You only need this item to find idents for material that has more than one end and is to be found by commodity code and sizes.

  • POS_SEP - If you choose to define relative locations, you can define the separator symbol within the position line in the Value field. If you omit this configuration item, the blank is taken by default. Refer to the description of the Type field for more information on defining relative or fixed locations.

  • POS_ATTR - You can transfer an unlimited number of position attributes for each position of the Smart Materials BOM structure. Enter the location of the position attribute in the Digit from/to fields, and the name of the attribute in the Value field.

  • POS_SUM_ID - If you want to summarize material that has the same ident within the same node/list status/issue status, set this item to the value Yes, Y, True, 1, or ON. If you do not want to sum up, you can omit this configuration item. Summarizing will only take place for material that is characterized by the same parameters. For example, if one position has only the ident code while the other has no ident but spec, short code, and size information, these cannot be added, even if they refer to the same ident. They will remain as two separate positions. Summarizing will only supply the correct values if they are of the same unit. The units of identical idents will not be converted to each other by the software. If you add 1 meter pipe to 3000 mm pipe, the result will be unpredictable.

  • POS_TAG_NU - Enter the location of the tag number in the Digit from/to fields. If a tag number occurs without an ident on an ASCII line, it is treated as item rule TWM. (One item type on A.10.15 with rule TWM must be checked as the default.) Users can submit the commodity code layout short/long to create the commodity code. If a tag number occurs together with an ident, the item rule will be considered to be SWT. (One item type on A.10.15 with rule SWT must be checked as the default.)

  • POS _TAG_SH - Enter the location of the tag number short layout in the Digit from/to fields. This setting is only of interest if you are working with POS_TAG_NU and creating tags with item rule TWM. (One item type on A.10.15 with rule TWM must be checked as the default.)

  • POS _TAG_LO - Enter the location of the tag number long layout in the Digit from/to fields. This setting is only of interest if you are working with POS_TAG_NU and creating tags with item rule TWM. (One item type on A.10.15 with rule TWM must be checked as the default.)

  • POS_CC_MAP - You can receive commodity codes in an interface- or company-specific translation. You choose from three characters to indicate what translation should be used: "M" for original Smart Materials, "I" for interface specific, and "C" for company-specific commodity codes. The order of these characters specifies the search order. The value "CIM" would mean: first look for a commodity mapping, if none found, look for an interface mapping. If none found, assume the normal commodity code from S.30.01. In this example, you could have omitted "M", because the normal commodity code is looked up by default, if nothing else is found. You do not have to use all three characters: "C" is also a valid example value for POS_CC_MAP. The interface code for interface mappings is "PDS". The company code for company mappings is taken from the PDS 10.01 Configure PDS screen, or if no configuration was done, from the Company entry on B.40.01. POS_CC_MAP will replace company or interface commodity codes with Smart Materials commodity codes to be processed by the standard OMI.

    Note that POS_CC_MAP will not work if you chose to select the Map Commodity Codes/Idents check box on B.40.01. Selecting this check box will cause the PDS OMI transfer to stop processing.

    For company ident codes, you also need to set POS_CC_MAP to indicate that you want to map, although the value of POS_CC_MAP is not relevant. Company ident codes are always looked up first. If not found in the project/product group, a Smart Materials ident code is assumed. Interface ident codes are not supported.

    If you plan to use only Smart Materials codes in your OMI load, do not include the POS_CC_MAP configuration item in your config, to save time spent looking up company and interface mapping tables.

  • POS_NATTR - You can specify an arbitrary number of node attributes for each node of the Smart Materials BOM structure. Enter the location of the position attribute in the Digit from/to fields and the name of the attribute in the Value field. To transfer the attributes correctly, the first position row that is on another (or on the very first) node must contain the node attributes with their values. The node attribute information on all following position rows for the same node in the import file will be ignored.

  • POS_IATTR - You can specify an arbitrary number of ident attributes for each position of the Smart Materials BOM structure. Enter the location of the ident attribute in the Digit from/to fields and the name of the attribute in the Value field. Using ident attributes will cause the preprocessor to relate the material to the item rule TAB, unless you specify otherwise with POS_ITR.

  • POS_ITR - You can specify the item rule explicitly in the ASCII file. Enter the location of the item rule in the Digit from/to fields.

    If you don’t specify the item rule, the following rule applies: If a tag number occurs without an ident on an ASCII line, it is treated as item rule TWM. If a tag number occurs together with an ident, the item rule is considered to be SWT. If there is no tag number specified, the item rule will be SOT.

    One item type on A.10.15 of each item rule you want to apply must be checked as the default.

  • POS_CG - The commodity group can be submitted in the ASCII file. Enter the location of the commodity group in the Digit from/to fields.

  • POS_CP - The commodity part can be submitted in the ASCII file. Enter the location of the commodity part in the Digit from/to fields.

  • POS_MODEL - Model code from PDS. This value will not be inserted by the standard procedure into the BOM. You can use it, for example, for any customized code in m_pck_pds_bom_custom. See the example function CREATE_OR_SUM_SPECIAL_ITEMS. When the return value from this function is ‘1’, the standard insert in m_import_interfaces will be replaced by the insert in the CIP.

  • POS_CIP1 – 3 - This value will not be inserted by the standard procedure into the BOM. You can use it, for example, for any customized code in m_pck_pds_bom_custom. See the example function CREATE_OR_SUM_SPECIAL_ITEMS. When the return value from this function is ‘1’, the standard insert in m_import_interfaces will be replaced by the insert in the CIP.

  • POS_NUM - The position number can be submitted in the ASCII file. Enter the location of the position number in the Digit from/to fields. To transfer position numbers, you must set the project default ZI_OMI_POS to DATA.