Lost in Translation? Compare CATIA V5 with SMG and JT easier
February 23, 2016
xCompare keeps you ahead of changes
In many industries CATIA data is translated into different neutral formats to provide downstream processes with the right data. For most processes, it is important to ensure no changes are caused by the conversion itself. Unacceptable differences must be revealed before the model is used in the following process step.
No conversion process is 100% accurate
CAD conversion represents an action of transforming a relatively complex mathematical description into a totally different one, trying to maintain the same outcome for the user and process but under the hood, things can get messy. While in many cases the converter is delivering exactly what we need to handle our tasks, it might become crucial for us to be that 99% sure that everything we have done in CATIA V5 is processed into the new format or the other way round. All elements shall be there, have the same measurements, nothing should be missing and nothing should have been added unintentionally - geometrically we want to have the models equally.
How do you track unexpected changes after data conversion?
Sure, in many cases we just want to provide a JT or SMG model, plainly to give someone else the possibility of viewing the data but...
...what if that someone actually takes decisions on that basis or uses the data in his process?
...what if we want to use the data for long term archiving and need to access the model years after we have faded out our current CAD system?
Typically we ask:
Do my models meet the minimum quality and methodology requirements?
Has a partner modified models from the last release interchanged, and what?
We need to follow legal requirements! Are those translated models really accurate?
B-Rep must be transformed accurately (same measurements)
PMIs must be transformed correctly (same values)
Data must be ready for the downstream process
LODs in JT data must represent geometry of CATIA V5 model
Okay but how will xCompare help me?
xCompare V5 / SMG verifies the conversion process from CATIA V5 to SMG (3DVIA Composer). Multiple criteria of a CATIA V5 model are compared to an SMG model. For the comparison, xCompare directly uses the models to analyze the features as well as the geometry.
xCompare V5 / JT is used for the comparison of geometric data – potential nonconformities will be shown graphically. By using xCompare, comparisons of CATIA V5 B-Rep with JT B-Rep (JT or XT B-Rep), V5 B-Rep with individual JT LODs (Level of Detail) and V5 CGR data with JT LODs can be performed. The presentation of results is available in CATIA V5 and differences in geometry can be displayed.
When comparing two models of different format, the approach of choice is to convert either both different formats in a third one or at least one into the other, to gain a basis for the comparison. This process unfortunately, is adding another one or two conversions to the bill - maximizing the chances that we may compare apples with oranges.
xCompare overcomes this known issue and directly accesses the native CATIA V5, SMG or JT data for the comparison. The data is not transformed whatsoever and the user never has to leave CATIA V5.
How it works?
xCompare accesses CATIA V5 and SMG data through the respective API and the JT Data through Transcat PLM’s own toolkit. The toolkit, developed on basis of JT ISO/PAS specification, is also used for viewing and checking JT data in the supplier package of the DAIMLER AG.
Arnd has 15 years of PLM experience working within TechniaTranscat software division in various positions in pre-sales, consulting and support. He currently works as Product Manager for TechniaTranscats xCompare and Lite3D portfolio.