Spec Items Type and CMS Idents - Intergraph Smart Reference Data - Version 10.1 - Training - Hexagon

Intergraph Smart Reference Data Training (10.1)

Language
English
Product
Intergraph Smart Reference Data
Search by Category
Training
Smart Materials/Smart Reference Data Version
10.1

Each specification has the Spec Items Type drop-down list on the Cover page. This list is enabled only for non-template specifications; it specifies the type of items that can be created for this specification. You can select Both, Classic Only, or CMS Only for this indicator.

For more information about the Component Management System (CMS), refer to Component Management System.

Spec Items Grid on the Components Page

For non-template specifications, the Specification Items grid displays the Class Code and Ident columns on the Components page. If the Spec Items Type indicator is set to Both on the spec header, the grid also displays the Type column, which indicates whether that specification item is of the classic type or CMS type.

In the Components page, you can enter the corresponding items (commodity codes) for a previously defined specification header. This means that for a previously defined pipe class you now enter the parts that are valid within that pipe class. You enter a part in a pipe class using the same three dimensions (Group, Part, Code) that were required when forming the commodity codes. In addition to the previously defined keys such as Group, Part, Code etc., you can enter a short code for each part in the pipe class to make it easier to locate an object in a pipe class.

After you define the short code for the new pipe class parts, you enter the commodity group, commodity part, and commodity code. All these values can be selected from a list of valid values. You can also enter an option to distinguish between identical commodity codes with different nominal size ranges. You can specify up to five nominal size ranges which indicates that all parts with nominal sizes x1 to x2 are valid parts for this pipe class.

When user enters TAG Information in the Additional TAG Info page, the TAG Numbers are visible in Components page so that user can enter the TAG Number along with Commodity Code in the Components page.

TAG number field has list of values so that user can select a TAG Number corresponding to the Commodity Code. The validations, for number of Sizes in this page, for Rule Based Idents depend on the Project Default ZS_ITA_CHK.

You must select a geometric for each nominal size range. Define the geometrics where you can specify the dimensions which describe the geometric properties of a commodity code.

You can define the Item level attributes in the Specification Rules so that for each pipe class you can determine whether additional attributes are required to describe an item of a pipe class. These fields appear on the Spec Item grid.

To insert new master commodity codes for assemblies from spec item line, refer to the project default ZS_INS_CC SRD in Project Defaults.

By project default ZS_DESC you can define whether the layout short or the layout long value will be displayed in the LOV on commodity code and in the commodity code layout item. Values of the project default ZS_DESC are (LONG, SHORT), default value being SHORT.

Assemblies

For assemblies, an enhanced validation is implemented. The fields, Size 1 (From 1, To 1) and Size 2 (From 2, To 2) must have values otherwise a message MAR-15924 is displayed.

For Assemblies, the rule is that the Commodity Code must be available, and the assigned object-parameter has the following settings in the columns:

No.

Input

Name

Ident

Option

1

Select the checkbox

Attr_1

Select the checkbox

Select the checkbox

2

Select the checkbox

Attr_2

Select the checkbox

Select the checkbox

5

Select the checkbox

Attr_3

Here, you can also select TAG Number through LOV on the TAG Number field. When TAG Number field is not empty then the Build Ident (through Build Ident button) logic will be based on the Project Default ZS_RBICB (Ident Code can be Rule Based or custom Ident). If TAG Number is empty, then the existing logic of building the Idents will be applied. If Rule Based Ident exists corresponding to a Spec Item, then you cannot update the TAG Number field.

On Specification Items there is a unique key defined on Short Code, Option Code, Size Range, and TAG Number which should be complied with the following:

  • Seq: Order sequence for the specification items. If you use unique value for this field, the spec copy can use the information from this field to update the correct item.

  • Short Description: A short description for the item of this pipe class. Double-click to open the menu associated with this spec. The menu entries are shortcuts to additional functionality, like I-Sketch, SKey Mapping.

  • Group: The commodity group from Commodity/Ident Management page.

  • Part: The commodity part from Commodity/Ident Management page.

  • Option: Distinguishing characteristic for identical commodity codes with different geometrics. Following verification applies for users of PDS/SP3D.

  • Interface: If No, the option among the allowed values defined in Short Code Management for the given short code is verified. If it is not defined, if there is any option code defined for the given short code will be verified. If it is also not defined, then the option is accepted. If yes, validation will fail.

    The LOV on the item retrieves the allowed values from Short Code Management. It will show only those option codes whose usage in Short Code Management contains the appropriate string "SP3D" or "PDS" in the project default ZS_LOV_OC (If the usage contains both "SP3D" and "PDS", this option code will be displayed in both cases). If the project default is not set, the LOV will display all option codes assigned to this short code with an empty value in the 'Usage' field.

  • Commodity Code: The commodity code from Commodity Code page. You can insert new CCs, if you set project default ZS_INS_CC to Y. Double-click on this item to navigate to Commodity Code page. If ZS_INS_CC is set, a check is performed to see if spec, short_code, group, part, and option fits to an assembly master definition. If yes, the CC field is filled with "spec code short code" on entry.

  • TAG Number: This field represents the TAG Number corresponding to the selected Commodity Code.

    If user doesn't specify Group, Part, and Commodity Code, then by pressing LOV on this field will list all these fields also along with the TAG Number.

    • If user has specified Group and Part, then LOV on this field will list all Commodity codes and corresponding TAG Numbers defined for that Group and Part.

    • If user specified Group, Part, and Commodity Code then LOV on this field will list all the TAG Numbers corresponding to that Commodity Code.

    After you fill the TAG Number value and press 'Build Idents', the system will create Idents based on the Project Default ZS_RBICB (Ident Code can be Rule Based or custom Ident). If user doesn't fill the TAG Number, then building Idents will follow the existing way of creating Idents when you press the 'Build Idents' button.

  • Document Code: Specifies name (code) of the Document.

  • Rev: Specifies revision of the Document.

  • Commodity Code Layout: Layout of the commodity code.

  • Geometric 1: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules.

    If the project default ZS_INS_CC is set and the commodity code was identified to be a master assembly, the LOV on this field is used to determine the number of sizes, the commodity code will have. For each number of sizes, there is an appropriate project default holding a geometric and an object parameter. The project defaults are called ZS_OP_ID1-4 and ZS_GN_ID1-4. By choosing from the LOV the correct geometric and object parameter are picked e.g. the value stored in ZS_GN_ID3 for three size commodities.

  • From 1: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • To 1: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • Unit 1: The unit of measure that applies to the nominal size ranges. The units are defined in Units page. You can set the project default ZS_UNIT_SI to automatically retrieve a unit from the Units page.

  • Geometric 2: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • From 2: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

    For Assemblies only:

    This range must be entered if the object parameter is defined for an Assembly. The Pos 1 and Pos 2 fields are defined by selecting the Ident and Optional checkboxes. Additionally, at Pos 5 the assigned Attribute is called ASS_NO and the checkboxes Ident and Optional being selected.

  • To 2: Nominal size ranges and a subset of geometric series from Standard Geometrics page. This subset is defined in Geometric Rules page.

  • Unit 2: The unit of measure that applies to the nominal size ranges. The units are defined in Global Setup > Units.

    For Assemblies only:

    This Unit must be entered if the object parameter is defined for an Assembly. The Pos 1 and Pos 2 fields are defined by selecting the Ident and Optional checkboxes. Additionally, at Pos 5 the assigned Attribute is called ASS_NO and the checkboxes Ident and Optional being selected.

  • Geometric 3: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • From 3: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • To 3: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • Unit 3: The unit of measure that applies to the nominal size ranges.

  • Geometric 4: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • From 4: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • To 4: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • Unit 4: The unit of measure that applies to the nominal size ranges. The units were defined in Global Setup > Units.

  • Geometric 5: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • From 5: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules page.

  • To 5: Nominal size ranges and a subset of geometric series from Other Geometrics page. This subset is defined in Geometric Rules.

  • Unit 5: The unit of measure that applies to the nominal size ranges.

  • Bolt Commodity Code: This field is used to tie a bolt commodity code to a part. For example, a flange when working with the I-Sketch interface.

  • Ctrl: Control status as defined Control Status page. The control status is a user-definable control function to either allow or prohibit further use of a record.

  • Size Filter: Indicates whether nominal size/nominal reducer filters on spec header level are active for the selected spec item. A nominal size filter applies only to spec item with one nominal size, while a nominal reducer filter applies only to spec items with 2 nominal sizes.

What do you want to do?