1. STEP and Scriptable CAx Tool Integration Doug Cheney Senior Software Engineer International TechneGroup Incorporated

2. qData integration : Exchange product data via a STEP model representation mComplete, 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 CADScript--a neutral application programming interface mOnly data and behavior needed by applications mRequires access to licensed installations of CAD systems mNative model stays in native system Complimentary Interoperability Approaches Local System Local Model CADScript Remote Model CADScript Remote System Native Model Neutral Model Target Model Native System Target System Systems Engineer Component Engineer

3. CADScript Overview Multi-CAD data and algorithm access with scripting ease and platform independence www.python.org www.iti-oh.com/pdi IGES & STEP CATIA Pro/ENGINEER I-DEAS UG and Parasolid

4. Complimentary Usage Scenarios qData integration using STEP mMulti-disciplinary repository of all product data mLong-term data retention mLegacy data migration qSystems integration using CADScript mMulti-CAD application mCollaborative engineering mCross-platform application mMulti-system assembly design

5. Multi-CAD Application Example qApplication Domain mCAD Model Quality Control qKey CAD Interface Requirements mSupport for each of the major CAD applications (e.g., CATIA, I-DEAS, Pro/E and UG) and formats (IGES, STEP, Parasolid) mAccess to native CAD data and algorithms (no data exchange) mIdentical diagnostic algorithms for all systems mFocus on diagnostic development, not system integrations qApplication Integration Success Metrics mCADScript V2.0 – 130K lines of C++ CADScript V3.0 – 29K lines of Python mCADScript V3.0 – 19 Diagnostics CADScript V4.0 – 40 Diagnostics

6. Multi-CAD Application Architecture CADScript Pro/ECATIA UG I-DEAS PDE/Lib Application Algorithms Menu Callbacks Application User Interface Customer Software ITI Software CAD Vendor Software

7. Collaborative Engineering Example qApplication Domain mCAD Model View and Mark-up qKey CAD Interface Requirements mSupport for each of the major CAD systems (CATIA, I-DEAS, Pro/E and UG) mModel query using precise measurements (i.e., no translation) mAssembly based queries mWeb based client/server architecture mHigh performance and large scalability qApplication Integration Success Metrics mVery short time-to-market for “production-ready” (multi-CAD) visualization product (less than 6 months)

8. Collaborative Engineering Architecture Web Browser class PartSession: def demo(self) def demoStep2(self, partFile, tesTol, edgeTol) def display(self) def area(self, uniqId) def length(self, uniqId) def modifyParameter(self, uniqId, rhs, type) … URL Call Mapper CADServer HTTP (URL) requests Calls Example browser request: http://host.iti.com:8085/demoStep2?partFile=TJ_SOLE.model&tesTol=.01&edgeTol=.01 Customer Software ITI Software CAD Vendor Software CADScript Pro/ECATIA ClientServer Java Applet UG I-DEAS PDE/Lib Application Server

9. Cross-Platform Application Example qApplication Domain mCoordinate Measuring Machine (CMM) qKey CAD Interface Requirements mAccess UNIX-only CAD (CATIA V4) data from an NT client mThe application requests a tessellated version of the CAD model from the server, the precise CAD geometry/topology is never sent to the client qApplication Integration Success Metrics mRealization of NT-only solution with access to UNIX data

10. Cross-Platform Application Architecture CMM Application class ApplSession: def displayPart() def gridFace() def projectPoints() … Application Server URL Call Mapper CADServer class CadModel: def displayPart() def gridFace() def projectPoints() … C++ Proxy Layer (automatically generated from PartSession.py) Menu Callbacks Customer Software ITI Software CAD Vendor Software CADScript Pro/ECATIA UG I-DEAS PDE/Lib Application Client NT ClientUNIX Server HTTP (URL) requests

11. Multi-CAD Assembly Design Example qApplication Domain mParametric Assembly Design qKey CAD Interface Requirements mDynamic access to the latest version of component models in any supported CAD system (CATIA, I-DEAS, Pro/E and UG) mInteract with all components within a single CAD system user interface mModel query using precise measurements (i.e., no translation) mParametric modification of remote components driven by local parameters qApplication Integration Success Metrics mEnabling true multi-CAD assembly design!

12. Multi-CAD Assembly Design Architecture Unigraphics class PartSession: def openModel() def parameters() def modifyParameter() … Application Server URL Call Mapper CADServer class PartClient: def cmdAddExtPart() def cmdExtPartMass() … ClientServer Python Proxy Layer (automatically generated from PartSession.py) Menu Callbacks CADScript Customer Software ITI Software CAD Vendor Software CADScript Pro/ECATIA UG I-DEAS PDE/Lib Application Client HTTP (URL) requests

13. Summary qSystem integration is a complimentary approach to data integration using STEP qSystem integration empowers dynamic usage scenarios mInstant access to the latest versions of native CAD models mPrecise measurements performed by native CAD systems mConsistent parametric modifications across CAD systems mFlexible software architecture enabling remote CAD system control via URL calls mRapid application development without software integration nightmares (no build problems) mSimple, concise, and intuitive application logic  Multi-CAD assembly design example: client is only 570 lines of Python code, server is only 551 lines