Electrical Raceway Design File-based Design Import: Objects | ||
| ||
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 Part Data | ||
| Raceway part | In New Typing mode, there is a preference to select the raceway part type. The part type can be a miscellaneous part or a dedicated raceway part type if you set properly the Part Subtype table. |
Following the Preferences selection, it can be either a miscellaneous part or a dedicated raceway part type according to the Part Subtype table content. For more information, see Me |
| Conduit part | Miscellaneous raceway part | Fully imported |
| Part Geometry Data | ||
| Associated CATShapes | - | - |
| Part Attribute Data | ||
| Raceway system attributes | Raceway system attributes | Partially imported Standard, Sub-part type, Nominal Size, End Style, Rating, Wall Thickness, Height, and Width are imported. All other system attributes, such as Material Category are imported using business rules. |
| User defined attributes | User defined attributes | Fully imported Imported using business rules |
| Part Port Data | ||
| Raceway part connectors | Raceway part connectors | Fully imported Migrated to ports and appropriate connector geometry is created and linked. Connector geometry is converted to an axis system. Its position, alignment, and orientation depends on the associated geometrical elements. |
| Trays | ||
| Heavy trays | Rigid trays | Partially imported Instances and references are imported. Instance application attributes are not imported. |
| Conduit | ||
Straight conduit Bendable conduit | Conduits | Fully imported Ports are created at the ends of the conduit. |
| User defined attributes | ||
| User defined attributes | User defined attributes | Imported using business rules |
| Path Reservation and Item Reservation Objects | ||
| Path Reservation | Rigid route or 3D part with representation containing a solid with the V5 shape | Partially or fully imported The behavior is the same as Run objects |
| Item reservation | Rigid route or 3D part with representation containing a solid with the V5 shape | Partially or fully imported The behavior is the same as Run objects |
V5 to 3DEXPERIENCE Data Import Table: Connections
The following table describes import correspondences between V5 connections and 3DEXPERIENCE content.
| V5 Data Type | 3DEXPERIENCE Content Type | Import Result |
|---|---|---|
| Two raceway part instances connected and having 3 constraints 1 Fix and 2 Coincidence. | Engineering connections | New engineering connection of type Rigid is created between the axis systems. |
| Tray connected to part through run. | Contextual design | Route is created from external reference of axis system of part at junction. |
| Tray is created as branch from another route. | Contextual design | Tray is created as branch tray i.e. created through external reference of tray branch port. |
| Conduit connection | Raceway connection | - |
V5 to 3DEXPERIENCE Data Import Table: Spools
The following table describes import correspondences between V5 spools and 3DEXPERIENCE content.
| V5 Data Type | 3DEXPERIENCE Content Type | Import Result |
|---|---|---|
| Spool object | Spool product | Fully imported |
| Objects contained in the spool with a link. | Objects are imported in compliance with their own import rules. | Objects contained in the spool in Preliminary Mode. The object becomes a product and is a typed reference because the discipline is Piping_spool. |
Considerations
You should take the following considerations into account:
- Importing in Replace Mode
The table below lists raceway data that is updated when imported using FBDI in Replace mode.
Data Update Status Raceway Parts Updated Heavy Trays The table below lists Hanger data that is updated/when imported using FBDI in Replace mode.
Data Update Status Hanger Parts Updated Important: You can import a V5 file into 3DEXPERIENCE by using File-based Design Import (FBDI). Now, if you import the same file again into 3DEXPERIENCE, this file replaces the previous one. For more information, see File Coexistence and Migration User's Guide. - Modify Attribute Data
- The table below shows the FBDI (in Replace mode) result when attributes on a
V5 Raceway
part are modified.
Part, Attribute, and Port data Result System attributes, such as Standard, Sub Part Type, Nominal Size, End Style, Wall Thickness, Height, and Width Updated Port geometry Points to axis system Port attributes Updated Unmapped system and user attributes Imported using business rules assigned to PLM Opening PLMEnsFBDIUserAttribute If Raceway sub-type names are modified, the corresponding 3DEXPERIENCE sub-type names are updated; but the discipline (e.g. Raceway_Part, Raceway_Rigid_Tray etc.) remains the same.
V5 Data Type Piping/Tubing Type and Sub-types
3DEXPERIENCE Content Type Mapped Type and Sub-types
Import Result Sub-class of Raceway Part Sub-class of Raceway Part NLS name of the class Type If you modify the geometry of a piping part in V5 and then import the part again into 3DEXPERIENCE, the latest V5 geometry is imported.
If hanger and support type names are modified, the corresponding 3DEXPERIENCE sub-type names are updated; but the discipline remains the same.
V5 3DEXPERIENCE Hanger Support type and Sub-types Mapped Sub-types Support Part NLS name of the class Type - Add, Remove, and Modify a Connector
-
The table below shows the FBDI (in Replace mode) result when a connector is
added, removed, or modified on a V5 Raceway part.
If connector names are modified, the corresponding 3DEXPERIENCE port names are modified but the discipline (Piping_Port) remains the same.Part, Attribute, and Port data Result System attributes such as Standard, Sub Part Type, Nominal Size, End Style, Wall Thickness, Height, and Width Updated Existing Port geometry Point to axis system Port attributes Updated New Connector Migrated to Port and appropriate connector geometry is created and linked. Connector geometry points to the axis system. Removed Connector Corresponding port is removed.