Electrical Raceway Design File-based Design Import: Attributes

V5 to 3DEXPERIENCE Data Import Table

The following table describes import correspondences between V5 file-based data and 3DEXPERIENCE content.

The statuses for import results are fully imported, partially imported, and not imported (-).


V5 Data Type	3DEXPERIENCE Content Type	Import Result
Raceway Type and Sub-types
Raceway Part	Raceway Part	Fully imported Raceway_Part
Sub-class of Raceway Part NLS name of the class Type		Fully imported Raceway_Part
Raceway Part Attributes
Nominal Size Nominal Size_2 Nominal Size3 Nominal Size4	Nominal Size	Fully imported Values are concatenated with X delimiter. For example. 2in X 4in
End Style End Style2 End Style3 End Style4	End Style	Fully imported Values are concatenated with X delimiter.
Standard	Standard	Fully imported Value is migrated.
Wall Thickness	-	- In New Typing mode, this attribute does not exist any more: the wall thickness is imported only at port object.
Height and Width	-	- In New Typing mode, this attribute does not exist any more: the height and width are imported only at port object.

V5 to 3DEXPERIENCE Data Import Table: Connectors

The following table describes import correspondences between V5 raceway part connectors, raceway hole connectors and spec attributes and 3DEXPERIENCE content.


V5 Data Type	3DEXPERIENCE Content Type	Import Result
Connector Type(Raceway Part and Hole)	Mapped Port Name	Discipline
Published Raceway Part Connector	Name of Publication	Raceway
Unpublished Raceway Part Connector Name of Connector		Raceway
Conduit connector	Raceway connector
Raceway Connector Spec Attributes	Mapped Port Attributes	Mapped Port Attribute Value
Nominal Size Nominal Size_2 Nominal Size3 Nominal Size4	Nominal Size	Connector Nominal Size is mapped to port Nominal Size.
End Style EndStyle2 EndStyle3 EndStyle4	End Style	Connector End Style is mapped to port End Style.
Standard	Standard	Value is migrated.
Wall Thickness	Wall Thickness	Connector Wall Thickness is mapped to port Wall Thickness.
Height and Width	Height and Width	Connector Outside Diameter is mapped to port Outside Diameter.

Important: If an attribute is not set in V5, it remains as such in 3DEXPERIENCE after FBDI process.

If V5 connector spec attributes are not defined, their corresponding 3DEXPERIENCE port attributes are taken from the part.


V5	3DEXPERIENCE
Hanger Support Type and Sub-types	Mapped Type and Sub-types	Discipline
Support Part	Support Part	SharedSupportPart
Support Part	NLS name of the class Type	SharedSupportPart

Note: V5 equipment parts having raceway part connectors are migrated to 3DEXPERIENCE equipment with raceway ports.

Considerations: Managing V5 Attributes Using Business Logic

Business Logic Intent

The intent is to allow customized valuation of attributes and parameters of V5 Raceway parts when migrating to 3DEXPERIENCE. This business logic is implemented through business rules, written in Enterprise Knowledge Language (EKL). These rules are assigned to Openings based on different criteria.

Opening Definition

This section describes the objects defining the 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
PLMEnsFBDIApplicationAttribute

PLMEnsFBDIUserAttribute


Opening ID	PLMEnsFBDIUserAttribute
Intent	Migration of unmapped system and user attributes
Location	Database pointed by Data Setup
Customization Intent	Execution

Context Object Parameters


Name	Type	Filter	In/Out	Description
V5ApplBaseType	String	Yes	In	System class. A list of valid values is as follows: RacewayPart
V5ApplUserType	String	Yes	In	V5 customer Class Type (Internal Name) in CATfct. Refer Report generated in V5 Feature Dictionary Editor.
V5Attributes	Feature	No	In	V5 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


Opening ID	PLMEnsFBDIApplicationAttribute
Intent	Migration of application attributes
Location	Database pointed by Data Setup
Customization Intent	Computation

Context Object Parameters


Name	Type	Filter	In/Out	Description
V5ApplBaseType	String	Yes	In	System class. A list of valid values is as follows: RacewayPart
V5ApplUserType	String	Yes	In	V5 customer Class Type (Internal Name) in CATfct. Refer Report generated in V5 Feature Dictionary Editor.
V5Attributes	Feature	No	In	V5 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.
V6ApplAttributes	Feature	No	In/Out	These are 3DEXPERIENCE app attributes.

Implementation Sample

You can create a business rule using Enterprise Knowledge Language (EKL). Business rules are assigned to openings 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:

...\win_b64\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 3DEXPERIENCE attributes or create parameters on 3D part

Associate Business Rule to Opening

Business rules are assigned to Openings using Data Setup.

When a V5 concentric reducer is migrated to 3DEXPERIENCE using the business rule PLMProductDSFBDISomeUserAttrMigration.CATRule, attributes such as Material Code, Material Category, Schedule, and Weight Dry are created as parameters on the 3DEXPERIENCE 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 Openings, business rules and their association with openings using Data Setup, see Quality Rules Capture User's Guide: Managing Customization By Rules.