STEP and OMG Standards

InteroperabilityDoug Cheney

Senior Software EngineerInternational TechneGroup Incorporated

Engineering Data Producers and Consumers

Producers : Engineering Design Groups

Consumers : Partner Design Groups, Analysis, Manufacturing, Test, etc.

Design EngineerUsing

CAD System

CADModel

Recreate

Print

Translate

StructuralEngineer

TechnicalIllustrator Systems

Engineer

WiringEngineer Technical

Illustrator

ManyOthers...

Assembly

Data integration : Exchange product data via a neutral model representation “Bottoms-up” approach

Neutral representation is a complete, standalone definition of model

Requires two model conversions: native to standard to target

Native model is duplicated in standard and target system formats

Systems integration : Share product data via a neutral programming interface (API) “Top-down” approach

Abstract representation exposes data and behavior needed by consumers

Requires consumer access to licensed installations of producer systems

Native model stays in native system

NativeSystem

Complimentary Interoperability Approaches

NativeModel

NeutralModel

TargetModel

NativeSystem

TargetSystem

NativeModel

Ne

utra

l AP

I TargetModel

Ne

utra

l AP

I

TargetSystem

Interoperability Approach Challenges

Data integration

Requires access to reliable translators

Translations can cause significant delays

Requires data rework when conversions are not 100% successful

Broad band width required for neutral model file transfer

Loss of design intent information (construction history, features, parameters)

Must manage redundant, derivative model representations

Systems integration

Requires application rework to use abstract interfaces

Requires dynamic access to installed, licensed CAD and PDM systems

Higher security risks

Complimentary Usage Scenarios

Data integration

Building a multi-disciplinary repository of all product data

Long-term data retention

Legacy data migration

‘Loose’ partner/supplier integration

Well-defined, structured and controlled design processes

Systems integration

Collaborative engineering

Real-time, multi-system assembly design

‘Tight’ partner/supplier integration

Dynamic or evolving design processes

Complimentary Standards

Data integration : STEP AP 203

PDM (Class 1)

CAD shape representations (Classes 2 – 6)

Systems integration : OMG MfgDTF

PDM Enablers

CAD Services

STEP influence on OMG standards

Standardized definitions of geometry, B-Rep, assembly and PDM entities and relationships

Concrete data format for serializing objects (via XML)

Expect to incorporate construction history/parametrics model development

OMG Manufacturing Domain Task Force

Web site: www.omg.org/homepages/mfg

PDM Enablers

V2 soon to be approved

CAD Services

Devt web site: www.grc.nasa.gov/WWW/jcad

V1 draft joint submission Dec 2000

V1 workshop @ Boeing Feb 2001

V1 submission June 2001

V1 approval Dec 2001

CAD Services V1

Geometry and B-Rep traversals, evaluations, point projections, mass properties

Non-geometric entity attributes (color, layer, visibility, user-defined attributes)

Assembly structure and component placement

CAD user interactions (primarily 3D graphics subsystem)

Abstract feature properties, parameter queries and modifications, model regeneration

CAD Services V2 (2002)

PDM Enablers interoperability

Explicit geometry and B-Rep creation

Advanced visualization queries

Geometric dimensioning and tolerancing queries

Parametric/feature-based model creation

System Integration Implementations

CADScript is a commercial toolkit from ITI that enables system integrations (www.iti-oh.com/pdi)

The following organizations are using CADScript for system integrations:

Webscope

FIPER GE Aerospace

Parker-Hannifin

BF Goodrich

OAI, ESI, Ohio Univ., Stanford Univ.

NASA Goddard

Glenn

Details in tomorrow’s presentation!