boeing proprietary rocketdyne propulsion and power cad data translation - past, present and future...
TRANSCRIPT
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
CAD Data Translation - Past, Present and Futurefrom consumers’ point of view
The 7th NASA-ESA Workshop on Product Data Exchange
Atlanta, GA
April 21, 2005
T. Charles Chen, Boeing – Canoga Park, CA
[email protected] (818) 586-8670
&
Terry McGowan, Boeing – St. Louis, MO
[email protected] (314) 479-3980
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
Why does Boeing need CAD data translation?
• Boeing uses many non-native design tools and many different design methods.
• Data Translation is essential to leveraging enterprise resources and interoperability.
• Suppliers require accurate model formats that can be ingested easily into their systems (iges,STEP).
• MBD requires the exchange of Engineering Intent (EI) along with geometry to suppliers. No open format can accommodate that presently.
• Boeing needs to migrate up legacy program data.
• Regulatory requirement for long term retention of data in an open and neutral format for 50+ years.
• Adoption of a native toolset (DS V5) environment vs standardizing data formats (open, neutral, or universal) was implemented.
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
MBD or Model Based Definition
• 3D model is the sole data authority
• No more 2D drawings
• The 3D model should contain everything needed from design to manufacturing, in particular, GD&T (Geometry Dimensions and Tolerance).
• Therefore we need GD&T in data translation
• STEP 203 E2 implementation will help
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
MBD – Model Based Definition
• Boeing is transitioning rapidly to a model based environment.
• Data Delivery to supplier must be formatted robustly and efficiently and in a standard open format.
• Data must be “purposed” to the downstream activity to protect IP and KBE.
• Relational design chains must be preserved for interoperability.
• Attribute and Meta data must be passed in a Xlation and purposed.
• New materials will bring new requirements for data exchange.
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
The Design Cycle
PROCESSPROCESS
DATADATAFORMATFORMAT
RREEQQ’’ss
TTOOOOLLSS
Process drives out requirements
Requirements are accommodated by data
structure
Data format enables the tool
Tools accomplish the process
INNOVATIOINNOVATION!N!
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
IGES & STEP history
IGES v.1
IGES v5.3
STEP AP203
STEP AP203 E2
1980
2010
2000
1990
Multiple definitions for the same entity. Many IGES flavoring tools
Hot not heard any STEP flavoring tools
CAD system tolerance issues
Need construction history, GD&T
Many commercial direct translators
A very successful application of IGES/STEP is long term data retention.
Full interoperability?
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
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.
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
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
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
Factors influence the quality of data translation
• Design standards• Design methodology• Design quality control• Release process with a model quality check
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
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)
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
CAD Data Translation Challenges
• CAD systems were design for CAD, not data translation• Data translation is a step-child of a CAD system• Do CAD vendors care about data translation?
• No, this is a step-child.• Yes, make sure it does not work well to export my data.
• STEP AP203 E2 implementation – How to get all major CAD vendors involved?
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
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.
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
Thank You !
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
Backup charts
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
How does Boeing perform data translation?
• Point solution Xlators tailored for specific native formats are utilized at Boeing
• Healthy use of iges and STEP for exchange of data.
• Validation shares equal priority with Xlation
• Boeing has adopted a common native toolset from Dassault Systems’ as a go forward strategy.
• Process>Requirements>DataStructure>Tool,----} Paradigm
• Single source master definition, vaulted data, distributed and repurposed for the target downstream activity.
• Highly reusable data sets.
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
A brief history
• IGES V1.0 was released in 1981, the current version V5.3 was released in 1996
Geometry-based standard
Non-unique definition for many entities
Many IGES flavoring tools for repair
• STEP v1.0 was released in 1994Product-based
Have not heard about “step flavoring” tools
An issue in both IGES and STEP: different CAD systems have different tolerance, therefore a trim surface may become untrimmed after translation.
A very popular application of IGES/STEP is not data translation, it is long term data retention.
BOEING PROPRIETARY
BOEING PROPRIETARYRocketdyne Propulsion and Power
Introduction
• Past – STEP expectations not met, what has accomplished, weak areas, work arounds, etc.• Present – New standards evolving, current capabilities, limitations, work arounds, etc. • Future – Full relational design expectations, dreams,