CAD Model Validation

ITI TranscenData's product data validation solutions combine ITI's leading expertise in interoperability improvement consulting with innovative validation technology. ITI helps customers put processes in place that help identify and manage the correction of problems stemming from design quality and product data interoperability issues. Resolution of these challenges is critical in order to improve downstream product data re-use.

Examples of validation include:

• Geometry which impedes reuse of models in Analysis and Manufacturing processes
• Unrealistic modeling features requiring changes during CAE/CAM model reuse and divergence
  between the master product model and downstream CAx models
• Unacceptable changes introduced during translation, migration, archiving or manual remastering.
• Undocumented changes arising between design revisions or for engineering change orders
• Changes caused by complex parametric relationships unknown to CAD users
• Changes to Assembly Product Structure models that were unanticipated

To learn more, please visit our CAD Model Validation Solution Page.

Long Term Data Archival

Document any quality defects in the design model to set appropriate expectations for the reusability of the archive data. Verify that any derived forms of the design model, e.g. STEP, are equivalent in quality and shape to the master model. If using STEP, add validation properties to the STEP model which can be used by a future recipient to validate that a future translated (imported STEP) CAD model is equivalent to the master model. These validation properties could also be used to verify the equivalence of any archive data format conversions which are required to maintain the archive over time.

Data Certification

CADIQ verifies that the design model has no quality defects which will impede anticipated downstream use of the model. It will also verify that any derived forms of the design model (IGES, STEP, CAD translations…) are equivalent in quality and shape to the master model. When using STEP, you can add validation properties to the STEP model which can be used by the recipient to validate that a translated (imported STEP) CAD model is equivalent to the master model.

While CADIQ has always promoted Native System Interfaces as the most robust approach for validation, not all scenarios allow access to native CAD systems. This is especially the case with smaller suppliers that must adhere to typical OEM partner mandates or quality specifications. These procedures often specify that converted forms of original CAD Master Models be properly validated to confirm that the original product design intent was not altered.

MBD Model Validation

Model Based Design (MBD) Model Validation includes Model-Based Engineering, Model-Based Manufacturing and Model-Based Sustainability. With the objective of the model being the master, you can minimize the use of drawings, and integrate into all phases of the product lifecycle. A model-based Definition (MBD) Model includes:

• Structure
• Geometry
• Annotations (aka 3D PMI, GD&T, FT&A, etc.)
• Model attributes
• Domain-specific data

Why MBD Model Validation?

If “the model is the master” then downstream modifications must be reconciled with the product design model. If you “integrate all phases of the product lifecycle” then the design model must be reusable in simulation, manufacturing, support, etc. There is a need for MBD validation in the following scenarios:

• Engineering changes
• Legacy data migration
• Supplier integration
• Certified data delivery
• Long-term archival
• Product lifecycle sustainment

Support/Specs

Key Features of CADIQ V6.4

CADIQ compares CAD models of various formats to identify geometric shape and quality differences introduced by engineering changes, translation or manual remodeling. It highlights shape differences in form, mass properties, surface geometry and topology. Quality defects that impede analysis, manufacturing or data exchange processes are clearly identified with no extraneous information. CADIQ analysis uses the native programming interface of each CAD system to maximize accuracy and robustness. Excel statistics are automatically generated to support process quality control. All functionality is available in a command line interface for integration into PLM systems.

Native File Interfaces

The CADIQ Analyzer works with a mixture of either Native System Interfaces or Native File Interfaces. The validation and business requirements drive the type of solution that makes the most sense for customers. CADIQ can also be more simply packaged for customers that need to quickly validate and document standalone Native CAD files without needing the original CAD system. With this new capability, interface options for CADIQ could include:

• CATIA V4 System and File Interfaces
• CATIA V5 System and File Interfaces
• Pro/ENGINEER System and File Interfaces
• NX System and File Interfaces
• CADDS5i System Interface
• NX I-deas System Interface
• SolidWorks File Interface
• JT Interface
• STEP File Interface
• IGES File Interface
• Parasolid File Interface
• ACIS File Interface

Supported Platforms (CADIQ V6.4, August 2011)

• AIX
• HP HP-UX
• SUN Solaris
• Windows

For CADIQ support, FAQ's, troubleshooting and detailed release documents, please go to the CADIQ Support Page.