Knowledge Basics File-based Design Import

File-based Design Import (FBDI) enables content migration from V5 to 3DEXPERIENCE.

Note: Some Knowledge parameters and relations may have been created inside applicative containers located in a CATProduct. The application used to create the applicative container is responsible for migrating the data.

This page discusses:

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
Parameters and Relations (formula, equivalent dimension, law, design table) inside a CATPart or CATDrawing. Identical Fully Imported
Relations (formula, equivalent dimension, law, design table) inside a CATProduct referencing user parameters at the Product level and parameters inside Parts Identical Fully Imported
Parameters inside a CATProduct Identical Fully Imported
External parameters:
  • directly pointing another parameter whatever its location
  • pointing a parameter through a publication
  • pointing a parameter through an assembly contextual link.
IdenticalFully Imported
URLs added to objects i.e. geometric, bodyIdenticalFully Imported
Catalog of Knowledge resources-- (the catalog is migrated)

Considerations

You should take the following considerations into account:

A CATpart Containing Knowledge Data in its product
If a part CATIA file imported into 3DEXPERIENCE contains a relation at the product level that drives parameters located in the mechanical part, the model changes. In the 3DEXPERIENCE, there is no way to drive parameters upon relations that are not located in the same component. The relation must drive a parameter locally and the parts have to recover the output value using an external parameter. During the import, the correct 3DEXPERIENCE model is automatically generated.


When importing, a warning message appears meaning that some output parameters of the relation are located in some external components and that these particular components have been replaced by local ones.
The relation was in the product and is imported in the 3DEXPERIENCE, into the Knowledge Engineering Specification representation. This particular relation drives a local parameter (in the Knowledge Engineering Specification representation).
A formula and an external parameter have been created in the part to recover the output value of the formula and to drive the initial output parameter.
Isolate Relations
You can find information about the isolation of formulas, rules and checks links.
If at least one parameter of the Formula is located in the CATPart or CATProduct document that cannot be loaded or if parameters are missing, the formula is imported and the lost parameter is replaced by a cloned parameter and a warning appears.
For data anterior to V5R11 (V5R11 excluded), parameters are lost. For data posterior to V5R11 (V5R11 included), a clone parameter is created.
You can migrate data anterior to V5R11 using the CATAsmUpgradeBatch batch available from the Tools section.
Notes:
  • if the Isolation setting is unchecked, the migration is stopped.
  • If the Isolation setting is checked, see the behavior of the various relations below.
Isolate Design Table Links
You can find information about the isolation of design tables links.
Classic Design Table
If a design table pointing to a .txt or . xls file cannot be loaded, it is not imported in the 3DEXPERIENCE. A warning appears to indicate which design table was not imported and which file prevents you from importing the design table. The parameters pointed by the design table keep their last values.
Embedded Design Table
If a design table pointing to a .txt or .xls file cannot be loaded but if it is embedded, it is imported in the 3DEXPERIENCE without the link.
Others
  • Relations (Formulas, Equivalent Dimensions, Laws, Design Tables) inside a CATProduct referencing parameters in other CATProducts or parameters inside CATParts. If these parameters are output parameters of the relation, the link is no longer valid. The behavior is the same as in the case above and it creates a valid structure in the 3DEXPERIENCE (see CATpart Containing Knowledge content in its Product).
  • Relations (Formulas, Equivalent Dimensions, Laws, Design Tables) inside a CATProduct referencing component activities or product properties: These links are no longer valid.
    Important: When a link to a parameter is no more valid in a 3DEXPERIENCE environment the parameter is replaced by local clones created during the FBDI process.
  • Knowledge Constraint Parameter Valuation: If the Knowledge relation is not located in the same document as the constraint which parameter is in input or output of the relation, the link is lost during the FBDI process. A deleted_Parameter will be created to replace the lost link on the relation.

    These models can be repaired in the 3DEXPERIENCE by editing or re-creating the relation to link the new parameter.

  • Valuation of constraint offsets from parametric relationships: If you created a formula that valuates a constraint parameter in V5, in the 3DEXPERIENCE, a Knowledge Engineering Specification is created, the formula is imported into this Knowledge Engineering Specification, a local copy of the parameter (valuated by the formula) is created, an external parameter is created, and a formula is created in the constraint to retrieve the Knowledge Engineering Specification value.

    If the constraint parameter is the input of a relation, the imported formula points to the constraint parameter.