1 / 16

CAD Data Translation - Past, Present and Future from consumers point of view

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

royal
Download Presentation

CAD Data Translation - Past, Present and Future from consumers point of view

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. CAD Data Translation - Past, Present and Future from 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 charles.chen@boeing.com (818) 586-8670 & Terry McGowan, Boeing – St. Louis, MO terrence.j.mcgowan@boeing.com (314) 479-3980

    2. 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.

    3. MBD or Model Based Definition

    4. MBD – Model Based Definition

    5. The Design Cycle

    6. IGES & STEP history

    7. 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.

    8. 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

    9. Factors influence the quality of data translation Design standards Design methodology Design quality control Release process with a model quality check

    10. Design processes influence data translation needs

    11. CAD Data Translation Challenges

    12. 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.

    13.

    14. Backup charts

    15. 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.

    16. 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 1994 Product-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.

    17. 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,

More Related