Theorem Updates The Multi-CAD
Theorem's Multi-CAD V5 product removes the cost and complexity of working with CATIA V5 data and non-CATIA data on a single project. Allowing the operator to access the data seamlessly from within CATIA eliminates the translation bottlenecks that add costs to product designs. It also removes the need to import data from UGNX and/or Pro/E into CATIA.
Multi-CAD reduces design costs by enabling the CATIA V5 user to incorporate non-CATIA V5 parts and assemblies, simply, within the CATIA V5 environment. This approach contrasts favourably with the traditional time-intensive and costly process of translating non-CATIA V5 data to CATIA V5 using a standard such as STEP AP203, or a direct database translator.
A major drawback with the above processes is recognising when a design change takes place in non-CATIA V5 data and managing the process of updating the CATIA V5 representation to take into account the changes once the initial translation process is completed. A further issue is that the designer has no control over when the data is translated, if it is carried out as a separate process.
Theorem's Multi-CAD V5 solution overcomes these problems, enabling CATIA V5 users to incorporate non-CATIA V5 parts and assemblies within the CATIA V5 environment, without external translators. Working within CATIA V5, the user simply selects the 'insert' tab at the top of the CATIA screen and moves to the 'existing component' selector on the ensuing drop-down menu. However, rather than selecting an existing CATIA design, the user selects a non-CATIA V5 part or assembly; this then appears on the CATIA V5 design tree.
What has happened is that the 'insert existing component' command has selected the non-CATIA V5 part/assembly and has run the Theorem Multi-CAD V5 application, which has drawn the data into the CATIA design tree. Multi-CAD V5 is more secure than a traditional translate and import process, in which there is never a link between source and translated files. This separation between CATIA V5 and imported, non-CATIA V5 data, when employing external translators, has always been a major problem for users, in that any changes to the non-CATIA V5 data would not be updated in the CATIA V5 design.
However, with Theorem's Multi-CAD product, CATIA V5 maintains and manages the links with the original files. Consequently, if there are changes within the non-CATIA V5 components or assemblies, these will be automatically reflected in CATIA V5 itself.
Theorem's Multi-CAD V5 product removes the cost and complexity of working with CATIA V5 data and non-CATIA data on a single project. Allowing the operator to access the data seamlessly from within CATIA eliminates the translation bottlenecks that add costs to product designs. It also removes the need to import data from UGNX and/or Pro/E into CATIA.
Multi-CAD reduces design costs by enabling the CATIA V5 user to incorporate non-CATIA V5 parts and assemblies, simply, within the CATIA V5 environment. This approach contrasts favourably with the traditional time-intensive and costly process of translating non-CATIA V5 data to CATIA V5 using a standard such as STEP AP203, or a direct database translator.
A major drawback with the above processes is recognising when a design change takes place in non-CATIA V5 data and managing the process of updating the CATIA V5 representation to take into account the changes once the initial translation process is completed. A further issue is that the designer has no control over when the data is translated, if it is carried out as a separate process.
Theorem's Multi-CAD V5 solution overcomes these problems, enabling CATIA V5 users to incorporate non-CATIA V5 parts and assemblies within the CATIA V5 environment, without external translators. Working within CATIA V5, the user simply selects the 'insert' tab at the top of the CATIA screen and moves to the 'existing component' selector on the ensuing drop-down menu. However, rather than selecting an existing CATIA design, the user selects a non-CATIA V5 part or assembly; this then appears on the CATIA V5 design tree.
What has happened is that the 'insert existing component' command has selected the non-CATIA V5 part/assembly and has run the Theorem Multi-CAD V5 application, which has drawn the data into the CATIA design tree. Multi-CAD V5 is more secure than a traditional translate and import process, in which there is never a link between source and translated files. This separation between CATIA V5 and imported, non-CATIA V5 data, when employing external translators, has always been a major problem for users, in that any changes to the non-CATIA V5 data would not be updated in the CATIA V5 design.
However, with Theorem's Multi-CAD product, CATIA V5 maintains and manages the links with the original files. Consequently, if there are changes within the non-CATIA V5 components or assemblies, these will be automatically reflected in CATIA V5 itself.
Comments