Change, create CATIA V5 objects and save modifications in mobile files.Export of CATIA V5 objects stored in ENOVIA VPM V4 or V5 to mobile files containing ENOVIA database identifiers.CATIA - ENOVIAvpm Supply Chain Engineering Exchange 2 - (EWE) is used by the OEM to produce the mobile files to be sent to the subcontractor, and then achieve the save in its ENOVIA VPM V4 or V5 database. Finally, the OEM loads data provided by the supplier in CATIA V5 and imports them in ENOVIA VPM V4 or V5 with CATIA - ENOVIAvpm Supply Chain Engineering Exchange 2 - (EWE). Afterwards, the supplier, thanks to CATIA - ENOVIA Work Exchange Package 1 - (EW1), makes all data modification or creation requested by the OEM and sends back updated mobile files.
Then the OEM generates mobile files and provides them to the supplier. Thanks to CATIA - ENOVIAvpm Supply Chain Engineering Exchange 2 - (EWE), the OEM defines a work context in ENOVIA VPM V4 or V5 and loads all associated data in CATIA V5. Theorems Universal CATIA CADverter is a specifically designed translator supporting both 32bit and 64bit processing to CATIA V5 R21 and all versions of JT.CATIA - ENOVIAvpm Supply Chain Engineering Exchange 2 (EWE)ĬATIA ENOVIAvpm Supply Chain Engineering Exchange 2 (EWE) allows an OEM to create a comprehensive CATIA V5 work environment for a sub-contactor that is not connected to the OEM ENOVIA database.ĬATIA - ENOVIAvpm Supply Chain Engineering Exchange 2 - (EWE) supports the ability to Export/Import CATIA V5 product data and associated CATIA V5 links from the OEM site to the subcontractor site, which is disconnected from the OEM ENOVIA database. They can then move on to other tasks while the Universal CATIA CADverter for JT translates the target files without the need for any further operator interaction. For example, when working on a batch of files via the command line interface, users simply direct Theorem’s new translator at a folder containing mixed CATIA models and assemblies indicate the translation parameters to be applied specify the destination folder and press enter. Operation of the new CADverter could not be easier or more effective. It not only identifies and converts mixed native CATIA V5 and V4 files automatically, but also recognizes and translates CATIA V5 assemblies that include embedded V4 data – all without operator input.īecause most single version translators are unable to accommodate such shared format assemblies, Theorem’s new Universal CATIA CADverter more than exceeds the capabilities of separate products – as even a combination of stand-alone V5 and V4 translators will fail to meet all user requirements. Providing a complete solution within a single product, Theorem’s Universal CATIA to JT CADverter eliminates the need for users to identify which version of CATIA the target data is supplied in. A further complication is that CATIA V5 assemblies may incorporate embedded CATIA V4 files – a fact that might not become apparent until there is a need to undertake data translation. Other supply chain partners may operate JT, resulting in collaborative projects that can involve a mix of two CATIA file formats as well as JT data. Theorem’s latest Universal CATIA translator for JT both streamlines and simplifies data translation and collaborative working, by automatically differentiating between CATIA V5 and V4 data files and converting them to JT in a single operation.ĬATIA and JT are widely used in many long-term design projects and it is not unusual for design and manufacturing companies to employ both CATIA V4 and CATIA V5 on production work. Native and Mixed CATIA V5 and V4 Data Automatically Converted to JT format
0 kommentar(er)
