Standards For CAD Data Exchange: S.Balamurugan
Standards For CAD Data Exchange: S.Balamurugan
Exchange
S.BALAMURUGAN
ASST.PROF (Sr.G)
DEPARTEMENT OF MECHANICAL ENGINEERING
SRM UNIVERSITY
CONTENTS
DEFINITION
CLASSIFICATION
FUNCTIONAL FEATURES
DESIGN FEATURES
MANUFACTURING FEATURE
Engineering
and Analysis
(CAE)
Neutral I/F
Product
Information
Management
Product
Databases
Neutral I/F
Supply Management
Manufacturing
Engineering
Process
Planning
Manufacturing
Databases
Materials
Planning
Procurement
Suppliers
Customer
Installation
and
Distribution
Typical Situation
Major supplier
uses I-DEAS
Partner uses
Unigraphics
Major company
uses CATIA
Small supplier
uses AutoCAD
Small supplier
uses Solid Edge
The Problem
Every CAD system uses its own proprietary
data format
Design data must be converted from one
format to the other
Unigraphics
CATIA
Pro/Engineer
PDES
Standardization Organization
National & European
ANSI (USA)
SET
AFNOR (France)
VDA/FS
DIN (Germany)
CAD*I
ESPRIT (EEC)
CIM-OSA
ESPRIT (EEC)
EDIF
International ISO
STEP
( A full data model)
Current Situation
Translation using IGES is unreliable
geometry is corrupted
much cleanup required after translation
Translation using STEP is not widespread
STEP translators only recently available
Existing translators lose information
parametrics and constraints
features and history trees
Short-term Solutions
To avoid data translation problems, many companies
Chrysler
all suppliers must use CATIA
General Motors
all suppliers must use Unigraphics
A Better Solution
A better solution is development of reliable
Neutral Interface
CAD 1
CAD 2
CAE 1
CAE 2
Neutral Interface
CAPP
PP&C
CAM
CAQ
Requirements of an Interface
The interface must be capable of handling all
manufacturing data
There should be no information loss (maintain the
semantics during conversion)
The system must be efficient to be capable of
handling the realtime requirements of
manufacturing
The system should be open-ended to permit
extensions or contractions
Requirements Continued
The system should be adaptable to other standards
The system must be independent of the computer and
architecture used
It must be possible to form application-oriented
subsets of the standard to reduce costs
The interface must be upward and downward
compatible in a hierarchical control structure.
Test procedures must be provided to verify effectivety.
1980
Widely supported
complex geometry
No formal information modelling basis
Insufficient support for conformance testing
STEP
(Standard for the Exchange of Product Model Data)
Uses a formal model for data exchange
Information is modelled using the EXPRESS language
EXPRESS has elements of Pascal, C, and other
languages
It contains constructs for defining data types and
structures, but not for processing data
EXPRESS describes geometry and other information
in a standard, unambiguous way
Physical files
Conformance testing
& test suites
STEP Architecture
Status of STEP
STEP has been under development for
Other Standards
Standards for technical documents
Standards for images
Internet and Web standards
of technical data
Technical publications an important focus
Thank you