FBDI Equipment & Systems Resources

The page provides information about how to implement business logic for File-based Design Import (FBDI) of Piping & Tubing parts from V5 to V6.

This page discusses:

Business Logic Intent

The intent is to allow customized valuation of attributes and parameters of V5 Piping & Tubing parts when migrating to V6.

This business logic is implemented through business rules, written in Enterprise Knowledge Language (EKL). These rules are assigned to PLM Openings based on different criteria.

PLM Opening Definition

This section describes the objects defining the PLM Opening: its global information, input objects, and context object parameters.

Input Object

The business logic can be invoked for VPMReference.

The two openings discussed in this section are:

PLMEnsFBDIUserAttribute

PLM Opening IDPLMEnsFBDIUserAttribute
IntentMigration of unmapped system and user attributes
LocationDatabase pointed by Data Setup
Customization IntentExecution

Context Object Parameters

NameTypeFilterIn/OutDescription
V5ApplBaseTypeStringYesInSystem class. A list of valid values is as follows:
  • PipingPart
  • TubingPart
  • Equipment
  • TubingNozzle
  • PipingNozzle
  • HgrSupportPart
V5ApplUserTypeStringYesInV5 customer Class Type (Internal Name) in CATfct. Refer Report generated in V5 Feature Dictionary Editor.
V5AttributesFeatureNoInV5 Attribute depends on the V5 object data model. This includes unmapped system and all user defined attributes. Example: MaterialCode, PartCode, etc.
Note: V5 attributes, such as Nominal Size and Commodity Type will be accessed by corresponding internal names with no spaces.

PLMEnsFBDIApplicationAttribute

PLM Opening IDPLMEnsFBDIApplicationAttribute
IntentMigration of application attributes
LocationDatabase pointed by Data Setup
Customization IntentComputation

Context Object Parameters

NameTypeFilterIn/OutDescription
V5ApplBaseTypeStringYesInSystem class. A list of valid values is as follows:
  • PipingPart
  • TubingPart
  • TubingNozzle
  • PipingNozzle
V5ApplUserTypeStringYes InV5 customer Class Type (Internal Name) in CATfct. Refer Report generated in V5 Feature Dictionary Editor.
V5AttributesFeatureNoInV5 Attribute depends on the V5 object data model. This includes unmapped attributes. Example: MaterialCode, PartCode, etc.
Note: V5 attributes, such as Nominal Size and Commodity Type will be accessed by corresponding internal names with no spaces.
V6ApplAttributesFeatureNoIn/OutThese are V6 application attributes.

Implementation Sample

You can create a business rule by using Enterprise Knowledge Language (EKL). Business rules are assigned to PLM openings by using Data Setup.

Create a Business Rule

You need to create a business rule by using Enterprise Knowledge Language (EKL). For more information, see Quality Rules Reuse User's Guide : PLM Customization by Rules : Creating a Business Rule.

Samples of business rules are located in:

...\intel_a\resources\samples

The sample business rule PLMProductDSFBDISomeUserAttrMigration.CATRule shows you how to:

  • Declare variables used by the rule
  • Retrieve application extension and Representation Instance
  • Retrieve RepReference and Part Feature
  • Migrate V5 attributes to V6 PLM attributes or create parameters on 3D part

Associate Business Rule to PLM Opening

Business rules are assigned to PLM openings by using Data Setup.

When a V5 concentric reducer is migrated to V6 using the business rule PLMProductDSFBDISomeUserAttrMigration.CATRule, attributes such as Material Code, Material Category, Schedule, and Weight Dry are created as parameters on the V6 part. In addition, V5 Material Category is also migrated to Description attribute on the part reference.

Similarly, system attributes can be migrated by assigning an appropriate business rule to PLMEnsFBDIApplicationAttribute opening.

References

For more information about PLM Openings, business rules and their association with openings using Data Setup, see Quality Rules Reuse User's Guide: PLM Customization By Rules.