ENOVIA SmarTeam V5 Coexistence and Migration Data Transition | |||
| |||
SmarTeam V5 to 3DEXPERIENCE Coexistence
| SmarTeam V5 Data | Transferable | Description |
|---|---|---|
| CATAnalysis of CATPart/CATProduct | Yes | Transfer of a CATAnalysis document based on a CATPart or CATProduct document |
| CATAnalysis of exposed assembly | - | Transfer of a CATAnalysis document based on an exposed structure |
| CATDrawing of CATPart/CATProduct | Yes | Transfer of a CATDrawing document based on a CATPart or CATProduct document. |
| CATDrawing of exposed assembly | - | Transfer of a CATDrawing document based on an exposed structure |
| CATDrawing (as CGM) | - | Transfer of the CGM of a CATDrawing document |
| CATMaterial | Yes | Transfer of a CATMaterial definition |
| CATPart (as CGR) | Yes | Transfer of the CGR of a CATPart document. This mode allows you to fully use the 3D Accuracy capabilities without completely migrating the source document. The V5 CATPart is also transferred without any change for further use. |
| CATPart (as Spec) | Yes | Transfer of a CATPart document as spec |
| CATProcess | - | Transfer of a CATProcess |
| CATProduct (blackbox) | Yes | Transfer of a CATProduct document (blackbox) |
| CGM | - | Transfer of a CGM document |
| CGR | Yes | Transfer of a CGR document |
| Catalog | Yes | Transfer of Catalog |
| Configuration dictionary | - | Transfer of a configuration dictionary |
| Configuration effectivities | - | Transfer of configuration effectivities |
| Configuration handler | - | Transfer of configuration handler |
| Constraints of exposed assembly | - | Transfer of assembly constraints created on an exposed structure |
| Constraints on Publications | Yes | Transfer of constraints on publications |
| Contextual link in CATProduct | Yes | Transfer of a contextual link contained in a CATProduct document |
| Contextual links exposed | - | Transfer of contextual links created on an exposed structure |
| Customize attributes with Business Logic | Yes | Possibility to customize the attributes transferred through Business Logic |
| Design table | Yes | Transfer of a design table |
| GCO | - | Transfer of a Generic Component |
| Instance deletion | Yes | If an instance is deleted in the source system the instance will be seen as deleted in 3DEXPERIENCE. |
| Maturity | Yes | Transfer of maturity information |
Me  > Preferences | Yes | Transfer of Me > Preferences settings. See Coexistence and Migration: ENOVIA SmarTeam V5. |
| Multivaluated attributes | - | Transfer of multivaluated attributes |
| Non-CAD documents | Yes | Transfer of a non-CAD document such as xls |
| Ownership | Yes | Transfer of ownership information |
| Product Structure exposed | Yes | Transfer of a Product Structure |
| Product View Result (PVR) | - | Transfer of PVR (applicative data: only the PVR object itself is not transferred) |
| Product View Specification (PVS) | - | Transfer of a Product View Specification |
| Publication exposed | - | Transfer of a Publication that is exposed in the database |
| Publication in CATPart | Yes | Transfer of a CATPart document containing a Publication |
| Publication in CATProduct | Yes | Transfer of a CATProduct document containing a Publication |
| Ref-Ref link | Yes | Transfer of a reference-to-reference link (for example the import of a solid) |
| TP | - | Transfer of a Technological Package |
| V4 model | Yes | Transfer of a CATIA V4 model |
| Versioning | Yes | Transfer of versioning information |
| XCAD (as CGR) | Yes | When XCAD is in place and the CGR is computed on a document then CGR is transferred |
Note:
"-" signifies Not Supported or Not Applicable.
3DEXPERIENCE to SmarTeam V5 Coexistence
Warning:
Transferring 3DEXPERIENCE
data to SmarTeam V5 Coexistence is no longer possible by default. To do so, the variable Coexistence_EnableExportToLegacyProvider=1 must be set.
|
| 3DEXPERIENCE Data | Transferable | Description |
|---|---|---|
| 3D rep (to a CATPart as a result) | - | Transfer of a 3D representation as a result |
| Drawing | - | Transfer of a Drawing document |
| Material | - | Transfer of a Material definition |
| 3D rep (to a CATPart as a specification) | - | Transfer of a 3D representation as a specification |
| 3DShape | - | Transfer of a 3DShape (CATIA V5 CGR) |
| Customized attributes | - | Transfer of a 3DEXPERIENCE customized attribute mapped to the source system |
| Customize attributes with Business Logic | - | Possibility to customize the attributes transferred using Business Logic |
| Instance deletion | - | If an instance is deleted in 3DEXPERIENCE the instance will be seen as deleted in the source system. |
| Maturity | - | Transfer of maturity information |
| Multi-instantiated rep | - | Transfer of a multi-instantiated representation |
| Multirepresentation | - | Transfer of multiple representations |
| Ownership | - | Transfer of ownership information |
| Product Structure | - | Transfer of a Product Structure |
| Publication at assembly Ref level | - | Transfer of a 3DEXPERIENCE Publication located at assembly reference level |
| Publication at leaf Ref level | - | Transfer of a 3DEXPERIENCE Publication located at leaf reference level (integrated in the generated CATPart) |
| V4 model | - | Transfer of a CATIA V4 model |
| Versioning | - | Transfer of versioning information |
Note:
"-" signifies Not Supported or Not Applicable.
General Considerations:
- SmarTeam V5 -> 3DEXPERIENCE instances can be replaced or deleted.
- X-CAD updates are not supported.
- Coexistence does not support checked-out objects but if transferred to 3DEXPERIENCE then last checked-in or released objects will be transferred to 3DEXPERIENCE. Using these objects will create inconsistency.
- The transfer of different Parts pointing to different revisions of the same Part is supported.
- The transfer of data created with the CATIA.ExposeMode option set to YES on the SmarTeam side is not supported. The results of such an operation are unpredictable.
Particular Considerations
- Neither instances nor internal component metadata information are transferred.
- For SmarTeam V5 > 3DEXPERIENCE transition, only embedded material is supported.
- Cyclic links are not supported by link resolution.
- If the option is activated in Me > Preferences > General > File-based Design Import, a CATDrawing is transferred together with associated CATPart/CATProduct. Otherwise, the CATDrawing must be explicitly selected for transfer.
- When a Part or Product is transferred, CATDrawings are activated in the Product Structure by default. If you do not want such "reverse links" (i.e. the pointed CATDrawings) to be extracted and included in the transfer, use the variable DO_NOT_USE_REVERSE_LINK. Remember that you can use the appropriate CATSettings option to deactivate instantiation of a CATDrawing representation under each reference of a Product Structure it points to (or has a view of). If you do use that option, the variable DO_NOT_USE_REVERSE_LINK has no useful purpose.
- If different revisions of an assembly are created in SmarTeam with the CATIA.ExposeMode option set to YES then the simultaneous carrying-over of such revisions is not supported.
- Visualization only: The corresponding Product Structure is created and the corresponding CATParts or CATDrawings are transferred when the Visualization only option is selected. Note that:
- only CGMs and CGRs are transferred and that an assembly structure containing such CATParts or CATDrawings can therefore be expanded at node level only
- CGM and CGR files containing the visualization information must first be generated using the MultiCAD server (XCAD) on the SmarTeam side
- selecting the Visualization Only option creates the corresponding Product Structure.
- Versioning
- Versioning is only supported on major SmarTeam V5 objects (released objects).
- The release operation in SmarTeam V5 should be propagated to the whole assembly. For other objects, transfer will not manage versioning.
- You are not allowed to delete the last transferred release object. Otherwise, it will create an inconsistency elsewhere. If the last revision is deleted then the latest revision is transferred to 3DEXPERIENCE, there may be some versioning conflicts.
- A default customization is provided based on PLMDB release policy (a, b, c, d, ...). If the SmarTeam policy for released objects is different, you need to edit the SMT_Versioning.CATRule Business Logic.
- You are allowed to transfer multiple versions of the same object/structure at the same time.
- SMT_Versioning.CATRule enables you to map SmarTeam REVISION to 3DEXPERIENCE platform Major Order. For more information, see Major Order Mapping Opening ID.
- ACADEMIA projects
- You can use industrial data for ACADEMIA projects.
- Using ACADEMIA data for industrial projects is not permitted.