Design components

1
Design components

• Mikhail KAZAKOV
• Open CASCADE S.A. (An EADS Matra Datavision
  company)
• Toronto, 11 September 2001

2
Open Cascade S. A.
EADS Matra Datavision
Open CASCADE S.A.
100
Open CASCADE Russia

• 110 persons worldwide
• 130 customers worldwide
• Collaboration with educational and research
  organizations

3
Open Cascade activity

• Turn key applications
• Customer application development and deployment
• Customer support and consulting
• Consulting, training, technical support,
  helpdesk, development manpower, packaged support
• Open Cascade - first open source 3D modeling
  object libraries
• Maintenance, RD activity
• March 2001 - joining OMG for standardization
  activity

4
Motivation

• We faced many problems to reuse algorithmic
  engineering components
• How to decrease time to implement Customer
  solutions?
• How to integrate easily multi-disciplinary
  engineering components and applications?
• CAD Services specification gives Top-Geom data
  interoperability - what is after?
• Its necessary to come to common basis and
  standardize behavioral aspect

5
Draft white paper posted

• Open Cascade has posted the draft of Design
  Components Whitepaper
• Mfg document mfg/2001-09-01
• Goals
• To start the discussion about the future of
  Component oriented engineering software within
  the OMG MfgDTF
• To issue the final Design Component WP with the
  common vision
• To build a team, which will be interested to work
  out this topic
• To define and start several RFPs

6
General idea of Design Components

• Specification of reusable algorithmic components
• Data interoperability as basis (CAD Services)
• Coverage of multi-disciplinary engineering
• To specify the set of services, which will create
  the grounds for multi-disciplinary engineering
  solutions
• These services shall conform to model-driven
  approach

7
Domains

• 3D modeling
• Mechanical design
• Rapid prototyping
• Optics
• Geophysics
• Numerical analysis
• Measurement
• Electrical engineering
• Many others, which need algorithms

8
3D modeling domain (CAD)

• Basic step of engineering
• Quite the same functionality among vendors
• High reuse possibilities
• CAD Services provides data interoperability
• Its time to start standardization of
  algorithmic components

9
General view onto specifications
Clients
Middleware platforms
3D modeling
Analysis
Electrical engineering
NC
Others
PDM Enablers
KBE
Process planning
Interconnection services (Behavior
interoperability)
CAD Services
Other data interoperability services
10
Main goals of Design Components

• Creation of a set of engineering
  interconnection services
• Standardization of algorithmic (behavioral)
  aspect of 3D modeling domain
• Future standardization of other domains

11
Interconnection services

• Main goal - to make multi-disciplinary
  engineering components working together
• Supporting behavioral interoperability
• 3 main approaches applicable
• Standardizing IDL interfaces
• Using of semanticdescriptions and logical
  inference
• Model-driven approach
• Thats the topic to discuss and standardize

12
3D modeling components

• Low level components (algorithms)
• Intermediate level components (algorithms)
• High level components (algorithms)
• Composite components (algorithms)

13
Example of decomposition and reuse
Client
May use
or
either
70 of computation time
Boolean operation
Interference computation
100 of computation time
20 of computation time
State propagation
Sequence of
Consist of
10 of computation time
Shape construction
Difference, Union and Intersection differ only in
last stage
14
Low level components

• Examples
• Intersect line with other line
• Find common point of two edges
• Project point on surface
• Not necessary to standardize
• Bad performance with direct use
• Will require re-implementation. No legacy concept
• But its necessary to describe possible
  decomposition. For clarity

15
Intermediate level components

• Examples
• Intersection of shapes (with complete result)
• Splitting of faces (Zones)
• Here many layers may exist
• Necessary to standardize
• Acceptable performance during direct use
• Needs for reuse in multi-engineering
• Intersection is needed for CAD and CAM for
  instance
• May be used as decomposition of high level
• May produce composite algorithms

16
High level components

• Examples
• Boolean operations (Union, Difference, )
• Fillets
• Protrusion/Extrusion (Sketch is required)
• Offset shape
• Its necessary to standardize
• Very high performance during direct use
• May be implemented either with intermediate level
  or directly
• Very high opportunities for reuse in
  multi-engineering
• High opportunities for composition

17
Composite components

• Examples
• Hole for a bolt
• Patterns
• Not necessary to standardize
• Too many possible variations
• Less opportunities for reuse
• May be achieved by composition of high and
  intermediate level algorithms
• Almost no composition
• This level (and in fact all levels) requires
  runtime extension mechanism to connect new
  algorithms

18
Benefits

• Distribution of algorithmic components
• Reuse of algorithmic components in
  multi-engineering
• Runtime construction of composite algorithms
• Openness (Extensibility, etc.) - saving time
• Good opportunity to apply MDA

19
Some results already achieved

• First feedback from PPE group is received
• It was decided to provide the joint MfgDTF
  whitepaper
• Publishing - 3 weeks before Dublin meeting
• To start the preparation of 3D modeling RFP
• To start building a team, working for 3D modeling

20
Do You want to join the team?