HVAC 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
HVAC Type and Sub-types
HVAC Part	HVAC Part	Fully imported HVAC_Part
Sub-class of HVAC Part	NLS name of the class Type
HVAC Nozzle	HVAC Nozzle
HVAC Part Attributes	Mapped Attributes	Mapped Attribute Value
Height Height2 Height3 Height4	-	- In New Typing mode, this attribute does not exist any more: the height is imported only at port object.
Width Width2 Width3 Widtht4	-	- In New Typing mode, this attribute does not exist any more: the width is imported only at port object.
Shape	Shape	Fully Imported
Equivalent Diameter	Equivalent Diameter	Fully Imported
Round Corner Radius	Round Corner radius The value is set to 0 if the shape is circular.	Fully Imported
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.
Diameter Diameter2 Diameter3 Diameter4	-	- In New Typing mode, this attribute does not exist any more: the diameter is imported only at port object.
Run Attributes
Equivalent Diameter	Equivalent Diameter	Fully imported Note: If the equivalent diameter is not found, the value is retrieved from the line ID the run belongs to.

V5 to 3DEXPERIENCE Data Import Table: Connectors/Ports

The following table describes import correspondences between V5 file-based HVAC part connectors, HVAC hole connectors and spec attributes and 3DEXPERIENCE content.


V5 Data Type	3DEXPERIENCE Content Type	Import Result
Connector Type(HVAC Part and Hole)	Mapped Port Name	Discipline
Published HVAC Part Connector	Name of Publication	HVAC
Unpublished HVAC Part Connector	Name of Connector	HVAC
HVAC Connector Spec Attributes	Mapped Port Attributes	Mapped Port Attribute Value
Height Height2 Height3 Height4	Height	Connector Height is mapped to port Height.
Width Width2 Width3 Widtht4	Width	Connector Width is mapped to port Width.
Shape	Shape	Connector Shape is mapped to port Shape.
Equivalent Diameter	Equivalent Diameter	Connector Equivalent Diameter is mapped to port Equivalent Diameter.
Round Corner Radius	Round Corner radius	Connector Round Corner Radius is mapped to port Round Corner Radius.
End Style End Style2 End Style3 End Style4	End Style	Connector End Style is mapped to port End Style.
Standard	Standard	Value is migrated.
Diameter Diameter2 Diameter3 Diameter4	Height is used to store the diameter if shape is circular.	Partially Imported For circular shapes, Diameter will be set as Height and Width.

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, its corresponding 3DEXPERIENCE port attributes are taken from the part.


V5	3DEXPERIENCE	Import Result
Equipment/Hanger Support Type and Sub-types	Mapped Type and Sub-types	Discipline
Equipment	Equipment	SharedEquipmentPart
Sub-class of Equipment	NLS name of the class Type	SharedEquipmentPart
Support Part	Support Part	SharedSupportPart
Support Part	NLS name of the class Type	SharedSupportPart

Note: V5 Equipment parts having HVAC part connectors are migrated to 3DEXPERIENCE Equipment with HVAC Ports.

Considerations

Business Logic Intent

The intent is to allow customized valuation of attributes and parameters of V5 HVAC 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: HVACPart Equipment HVACNozzle HgrSupportPart HVACPart
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: HVACPart HVACNozzle
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 using Enterprise Knowledge Language (EKL). For more information, see Quality Rules Capture User's Guide : Managing 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.