STEP and OMG Standards Interoperability Doug Cheney Senior Software Engineer International TechneGroup Incorporated

Engineering Data Producers and Consumers qProducers : Engineering Design Groups qConsumers : Partner Design Groups, Analysis, Manufacturing, Test, etc. Design Engineer Using CAD System CAD Model Recreate Print Translate Structural Engineer Technical Illustrator Systems Engineer Wiring Engineer Technical Illustrator Many Others... Assembly

qData integration : Exchange product data via a neutral model representation m“Bottoms-up” approach mNeutral representation is a complete, standalone definition of model mRequires two model conversions: native to standard to target mNative model is duplicated in standard and target system formats qSystems integration : Share product data via a neutral programming interface (API) m“Top-down” approach mAbstract representation exposes data and behavior needed by consumers mRequires consumer access to licensed installations of producer systems mNative model stays in native system Native System Complimentary Interoperability Approaches Native Model Neutral Model Target Model Native System Target System Native Model Neutral API Target Model Neutral API Target System

Interoperability Approach Challenges qData integration mRequires access to reliable translators mTranslations can cause significant delays mRequires data rework when conversions are not 100% successful mBroad band width required for neutral model file transfer mLoss of design intent information (construction history, features, parameters) mMust manage redundant, derivative model representations qSystems integration mRequires application rework to use abstract interfaces mRequires dynamic access to installed, licensed CAD and PDM systems mHigher security risks

Complimentary Usage Scenarios qData integration mBuilding a multi-disciplinary repository of all product data mLong-term data retention mLegacy data migration m‘Loose’ partner/supplier integration mWell-defined, structured and controlled design processes qSystems integration mCollaborative engineering mReal-time, multi-system assembly design m‘Tight’ partner/supplier integration mDynamic or evolving design processes

Complimentary Standards qData integration : STEP AP 203 mPDM (Class 1) mCAD shape representations (Classes 2 – 6) qSystems integration : OMG MfgDTF mPDM Enablers mCAD Services qSTEP influence on OMG standards mStandardized definitions of geometry, B-Rep, assembly and PDM entities and relationships mConcrete data format for serializing objects (via XML) mExpect to incorporate construction history/parametrics model development

OMG Manufacturing Domain Task Force qWeb site: qPDM Enablers mV2 soon to be approved qCAD Services mDevt web site: mV1 draft joint submission Dec 2000 mV1 Boeing Feb 2001 mV1 submission June 2001 mV1 approval Dec 2001

CAD Services V1 qGeometry and B-Rep traversals, evaluations, point projections, mass properties qNon-geometric entity attributes (color, layer, visibility, user-defined attributes) qAssembly structure and component placement qCAD user interactions (primarily 3D graphics subsystem) qAbstract feature properties, parameter queries and modifications, model regeneration

CAD Services V2 (2002) qPDM Enablers interoperability qExplicit geometry and B-Rep creation qAdvanced visualization queries qGeometric dimensioning and tolerancing queries qParametric/feature-based model creation

System Integration Implementations qCADScript is a commercial toolkit from ITI that enables system integrations ( qThe following organizations are using CADScript for system integrations: mWebscope mFIPER  GE Aerospace  Parker-Hannifin  BF Goodrich  OAI, ESI, Ohio Univ., Stanford Univ. mNASA  Goddard  Glenn qDetails in tomorrow’s presentation!