V5 to 3DEXPERIENCE Data Import TableThe 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 |
|---|
| Piping/Tubing Type and Sub-types | | Piping Part | Piping Part | Fully imported Piping_Part | | Sub-class of Piping
Part | NLS name of the
class Type | | Tubing Part | Tubing Part | | Sub-class of Tubing
Part | NLS name of the
class Type | | Piping Nozzle | Piping Nozzle | | Tubing Nozzle | Tubing Nozzle | | Piping/Tubing 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. | | Rating
Rating2
Rating3
Rating4 | Rating | Fully imported Mapped to system attribute Schedule
based on a few conditions. For more information, see Mapping Rating to Schedule. | | Wall Thickness
Wall Thickness2
Wall Thickness3
Wall Thickness4 | - | - In New Typing mode, this attribute does not exist any more: the wall thickness is imported only at port object. | | Outside Diameter
Outside Diameter2
Outside Diameter3
Outside Diameter4 | - | - In New Typing mode, this attribute does not exist any more: the outside diameter is imported only at port object. | | Run Attributes | | Nominal Size | Nominal Size | Fully imported Note:
If the nominal size is not found, the value is retrieved from the line ID the run belongs to.
|
V5 to 3DEXPERIENCE Data Import Table: Connectors
The following table describes import correspondences between V5 piping and tubing part connectors, piping and tubing hole connectors and spec attributes and 3DEXPERIENCE content. | V5 Data Type | 3DEXPERIENCE Content Type | Import Result |
|---|
| Connector Type(Piping/Tubing
Part and Hole) | Mapped Port Name | Discipline | | Published Piping
Part Connector | Name of Publication | Piping | | Unpublished Piping
Part Connector | Name of Connector | | Published Tubing
Part Connector | Name of Publication | | Unpublished Tubing
Part Connector | Name of Connector | | Piping/Tubing 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. | | Rating
Rating2
Rating3
Rating4 | Rating | Connector Rating
is mapped to port Rating. | | Wall Thickness
Wall Thickness2
Wall Thickness3
WallThickness4 | Wall Thickness | Connector Wall
Thickness is mapped to port Wall Thickness. | | Outside Diameter
OutsideDiameter2
OutsideDiameter3
OutsideDiameter4 | Outside
Diameter | Connector Outside
Diameter is mapped to port Outside Diameter. | | No Outside Diameter | Outside Diameter | Part Outside Diameter
is mapped to port Outside Diameter depending on the connector Nominal
Size. If Nominal Size exists on connector, value is taken
from part Outside Diameter.
If Nominal Size_2 exists on connector, value is taken from part
OutsideDiameter2.
If Nominal Size_3 exists on connector, value is taken from part
OutsideDiameter3.
If Nominal Size_4 exists on connector, value is taken from part
OutsideDiameter4. |
If V5 connector spec attributes are not defined, their
corresponding 3DEXPERIENCE port attributes are taken from the part.
| V5 | 3DEXPERIENCE |
|---|
| 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 | | Support Part | Support Part | SharedSupportPart | | Support Part | NLS name of the
class Type |
Note:
V5 equipment parts having piping/tubing part
connectors are migrated to 3DEXPERIENCE equipment with piping ports.
Considerations: Mapping Piping and Tubing Parts, Mapping Piping and Tubing Port Attributes
You should take the following considerations into account:
-
Mapping Piping and Tubing Parts
-
The rules for mapping V5 Rating and Schedule to 3DEXPERIENCE Rating attribute on
a part are as follows:
- If Rating has a value, but Schedule has no value; 3DEXPERIENCE
Rating acquires Rating values (Rating, Rating2, Rating3, Rating4) concatenated
with "X"delimiter.
- If Rating has no value, but Schedule has a value; 3DEXPERIENCE
Rating acquires Schedule values (Schedule, Schedule2, Schedule3, Schedule4)
concatenated with "X"delimiter.
- If both Rating and Schedule have values, Rating takes precedence.
On migration 3DEXPERIENCE Rating acquires Rating values (Rating, Rating2, Rating3,
Rating4) concatenated with "X"delimiter.
- If Rating has no value, but Rating2 and Schedule have value;
on migration Rating acquires Schedule values (Schedule, Schedule2, Schedule3,
Schedule4) concatenated with "X"delimiter.
| V5 | 3DEXPERIENCE |
|---|
| V5 Attribute Values | Mapped Rating Attribute Value |
|---|
| Rating="A"Rating2="B"
Schedule="C" | A X B | | Rating="A"
Rating2="B"
Rating3="C"
Schedule="" | A X B X C | | Rating=""
Rating2=""
Rating3=""
Schedule="SchA"
Schedule="SchB" | SchA X SchB | | Rating=""
Rating2="B"
Rating3=""
Schedule="SchA"
Schedule="SchB" | SchA X SchB |
-
Mapping Piping and Tubing Port Attributes
The rules for mapping V5 Rating and Schedule to 3DEXPERIENCE Rating attribute on
a port are as follows:
- If Rating has a value, but Schedule has no value; on migration port
acquires Rating values of the part.
- If Rating has no value, but Schedule has a value; on migration port
acquires Schedule values of the part.
- If both Rating and Schedule have values, Rating takes precedence.
On migration port acquires Rating values of the part.
-
| V5 | 3DEXPERIENCE |
|---|
| V5 Attribute Values | Connector1 Attribute | Connector2 Attribute | Port1 Rating Value | Port2 Rating Value |
|---|
| Rating="A"
Rating2="B"
Schedule="C" | Rating
Schedule | Rating2
Schedule2 | A | B | | Rating="A"
Rating2="B"
Schedule="C" | Rating
Schedule | Rating
Schedule | A | A | | Rating="A"
Rating2="B"
Schedule="C"" | Schedule
| Rating | A | A |
Considerations: Managing V5 Attributes Using Business Logic
- Business Logic Intent
- The intent is to allow customized valuation of attributes and
parameters of V5 Piping & Tubing 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
-
| 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:
- PipingPart
- TubingPart
- Equipment
- TubingNozzle
- PipingNozzle
- 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:
- PipingPart
- TubingPart
- TubingNozzle
- PipingNozzle
- 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 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.
|