Scribd
Upload
20 views7 pages

Iges - PDD

The document discusses the history and evolution of IGES and STEP standards for CAD data translation, highlighting the challenges and needs for feature-based translation and validation. It emphasizes the importance of design standards, methodologies, and quality control in influencing data translation quality. Additionally, it addresses concerns about protecting intellectual property during data exchange between CAD systems, particularly with suppliers using native CAD files.

Uploaded by

Berihu Girmay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
20 views7 pages

Iges - PDD

The document discusses the history and evolution of IGES and STEP standards for CAD data translation, highlighting the challenges and needs for feature-based translation and validation. It emphasizes the importance of design standards, methodologies, and quality control in influencing data translation quality. Additionally, it addresses concerns about protecting intellectual property during data exchange between CAD systems, particularly with suppliers using native CAD files.

Uploaded by

Berihu Girmay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

IGES -PDD

IGES & STEP history

STEP AP203 E2
2010
Full interoperability?

IGES v5.3 Need construction


history, GD&T
2000
STEP AP203
Hot not heard any STEP flavoring tools
A very successful application of IGES/STEP is long term
data retention.
1990 Many commercial direct translators
IGES v.1
CAD system tolerance issues
Multiple definitions for the same entity. Many IGES flavoring tools
1980
Feature-based translation

• Users expect translated model to be modifiable at the receiving site


• Feature-based translation or construction history or STEP AP203 E2
• Feature-reconstruction bypasses CAD system tolerance issues, however, it
brings in another set of problems –
• There are many incompatible features between CAD systems
• There are many construction methods for the same feature on the same
CAD system (e.g.hole)
• Different CAD system employs different algorithms to computer
intersection curves, therefore, we need translation validation.
CAD Data Translation Validation

• Users have been asking for it since Day 1.


• What to validate? Do you care about these changes?
• geometry or shape
• topology – one sphere becomes two semi-spheres
• entity count
• math – exact representation of a circle by a NURBS spline
• mass property
• color changes
• layer changes
• Challenges
• Need to recognize that this is a new field
• How to communicate changes to a general user in a “general”
language?
• Need a tool developed for this purpose
Factors influence the quality of data translation

• Design standards
• Design methodology
• Design quality control
• Release process with a model quality check
Design processes influence data translation needs

• paper drawing – no need for data translation


• 2D CAD drawing – dxf or IGES
• 3D CAD design – IGES or STEP
• 3D CAD solid design - STEP
• PLM – Product Lifecycle Management
• Data management is the center of the universe
Designers must go to PDM to get appropriate CAD models
• CAD is one of many tools within PLM
• CAD data translation must go with PDM
(CAD model + data maturity level + BOM + relational design…+etc)
What we do not want to translate

• Company intellectual property embedded in CAD models


• KBE (Knowledge Based Engineering) data
• Specific math formulas to create curves and surfaces
• Third party application software data - engineering notes
• in-house developed macros
• This is not a problem with current IGES, STEP or other direct translators. However, we
are concerned with data exchange with suppliers in native CAD files such as CATIA V5
via a PDM system.

You might also like