0405 Presentation Froehlich Jaekel

Standardized Library Components
for ECAD/MCAD Collaboration

ProSTEP iViP Symposium 2009
12.05.2009, Berlin
Dr. Volker Jkel, Continental Automotive GmbH
Dr. Arnulf Frhlich, PROSTEP AG
Agenda
ProSTEP iViP Project Group ECAD/MCAD Collaboration

Standardized Library Components for ECAD/MCAD Collaboration
Use Cases
3D Dimensioning Concept
Continental Corporate Presentation
History of ECAD Libraries
Requirements
3D Component Generator and Editor ExOPaMo
Outlook and Conclusion
2 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009
ProSTEP iViP Project: ECAD/MCAD-Collaboration

Enabling mandatory collaboration between ECAD and MCAD domains
Process-oriented
Standard-based
Based on requirements/definitions from ECAD/MCAD-Workshops in
2005
Definition of a STEP affiliated collaboration model
First data model based on STEP AP210 and AP214 entities has been
designed in 2006
Made available as XML schema for implementation
PSI 5 Recommendation 1.0 published 8th of May 2008
www.prostep.org/en/downloads/recommendations-standards.html
(V1.2 April 2009)
Participants 2008/2009
Service Providers
Users
Delphi
:em
Continental
PDTec
PROSTEP
Vendors
xPLM
Mentor Graphics
Research
PTC
Siemens PLM
FU Hagen
Contacts
Chairman: Steve Hughes, Mentor Graphics Corp.
Coordinator: Arnulf Frhlich, PROSTEP AG
4 project phases (2006 - 2009)

Key activities 2006
Consolidation Requirements
Analysis STEP AP210, AP212 and AP214
1st Milestone: Specification of initial data model for ECAD/MCAD-Collaboration
Key activities 2007

Functional enhancements of data model for ECAD/MCAD-Collaboration
2nd Milestone: PSI 5 Recommendation V1.0 for ECAD/MCAD-Collaboration
Key activities 2008

System and Process Integration
Standardization of 3D Components in Libraries
3rd Milestone: Updated PSI 5 Recommendation V1.2
Key activities 2009

Certification Guidelines
Embedding ECAD/MCAD-Collaboration into PDM Processes
4th Milestone: State-of-the-art Recommendation V2.0 for ECAD/MCAD-Collaboration
Requirements for standardized 3D library components

Defining parametric 3D master models for standard electrical component types
The data exchange of a component instances takes place based on the
component type and the parameter information
Instantiation by XML-File, which contains the parameters to feed the 3D
master models
Instantiated models may be modified/enriched by librarian information
Instantiated models should be used as simplified placeholder
3D Master Models
Type & Parameter
Library Component
Instances
Specification of 3D Master Models in standard format

Users/Vendors could implement the master model concept in any CADSystem
Out of Scope
Detailed, exact geometry or technology information
Use Cases
Use Case 1
"Using library information
within collaboration"
Standardized
StandardizedUse
UseCase
Case
Documentation
Documentation
Use Case 2
"Cross domain library to
library data exchange"
Use Case 3
"Provision of library data
from supplier"
Use Case 4
"Creation of packages based
on similar parameter values"
EDMD
Communication
Explicit
Component Information
Library Information
(Type & Parameter)
Collaboration Module
ECAD
Collaboration Module
UC1: Using library information within collaboration
ECAD Lib.
MCAD
MCAD Lib.
3
Standard-Types
3
Standard-Types
UC2: Cross domain library to library data exchange

ECAD 1
ECAD Lib. 1
MCAD Lib. 1
3
Standard-Types
3
Standard-Types
EDMD
Communication
MCAD 1
Explicit
+
ECAD 2
ECAD Lib. 2
Library Information
(Type & Parameter)
3
Standard-Types
MCAD Lib. 2
3
Standard-Types
MCAD 2
UC3: Provision of library data from supplier

Customer
ECAD Lib.
ECAD
Component Supplier
EDMD
Communication
Component
data sheet
3
Standard-Types
Explicit
+
Library Information
(Type & Parameter)
MCAD Lib.
3
Standard-Types
MCAD
UC4: Creation of packages based on similar parameter values
ECAD Lib.
3
Standard-Types
ECAD
EDMD
Communication
Explicit
MCAD Lib.
MCAD Library Information

(Type & Parameter)
3
Standard-Types
Packages with
instantiated
components with
similar parameter
values
Main characteristics of three Master Model Types

Type
Type A
Type B
Type C
Characteristic
Diagram
Block with chamfers

Basic Body
Cylinder
Block with radial

chamfer or cylinder
Any number of pins
2 pins
2 straight pins
Type C, L, I or Z
Angled by 90
Add. body on top

Hole
Cut
Contact (Pin)
3D Dimensioning Concept
Represented in 3D PDF
Orientation of Coordinate System
z
y
Type_A.pdf
Dimensions are on views

Dimensions
ACS_XY, ACS_ZX
Body_XY, Body_YZ
Chamfer_XY
Hole_XY, Hole_XZ
Pin_XY
Views
Cut_XY, Cut_ZX
Example for the products designed by Continental in Wetzlar,

a development center of the business unit Infotainment & Connectivity
Example for a PCB

The postioning of PCB components starts in our Business Unit in MCAD
and will be finished in ECAD
3D master model of PCB
Re-Import in 3D after finishing in ECAD
History of the plant Wetzlar

Philips erffnet in
Wetzlar eine
Produktionssttte
fr Trafos und
Rundfunkgerte
(Philetta)
1946
Das erste
Autoradio
mit Kassettenlaufwerk
wird produziert
Produktion der
ersten Navigationssysteme
1974
1953
Das erste UKW

Autoradio wird in
Wetzlar produziert. Die
Stationstasten waren
aus Patronenhlsen
Nachdem 1997 der Philips

Konzern seine Sparte Philips
Car Systems an Mannesmann VDO verkauft, fusionieren 2001 Siemens
Automotive und Mannesmann VDO zur Siemens VDO
Automotive AG.
2001
1993
1988
1998
Das erste AutoRadio mit CD

wird
In Serie
produziert.
Start NavigationsEntwicklung
Mannesmann VDO
bernimmt Philips
Car Systems
Die Continental AG
bernimmt die Siemens
VDO Automotive AG. Jetzt
zhlt das Unternehmen
150.000 Mitarbeiter an 200
Standorten in 34 Lndern.
2008
2005
Der CCC fr BMW geht in

Serie
Die Marke VDO

Dayton
2007
Der RNS (Radio
Navigation System) fr
VW wird von der Presse
gefeiert.
entsteht
1/2008: ber 1 Million
Multimedia-Systeme fr
BMW produziert
Continental Corporate Presentation

Continental Corporation
Automotive Group
Chassis &
Safety
Rubber Group
Powertrain
Interior
Pkw-Reifen
Nfz-Reifen
Electronic
Brake Systems
Engine Systems
Body & Security
Erstausrstung
Transmission
Hydraulic
Brake Systems
Hybrid Electric
Vehicle
Commercial
Vehicles &
Aftermarket
Ersatzgeschft
Europa & Afrika
Lkw-Reifen
Europa
Sensors &
Actuators
Infotainment &
Connectivity
Fuel Supply
Instrumentation &
Displays,
Interior Modules
Sensorics
Passive Safety
& ADAS
Chassis
Components
Ersatzgeschft
The Americas
Lkw-Reifen
The Americas
ContiTech
Air Spring Systems
Benecke-Kaliko
Group
Conveyor Belt Group
Elastomer Coatings
Ersatzgeschft
Asien
Lkw-Reifen
Ersatzgeschft
Asien
Zweiradreifen
Industriereifen
Power Transmission
Group
Fluid Technology
Vibration Control
Other Operations
History and ECAD libraries

As result of a lot of fusions 3 different ECAD systems and 4 different ECAD
libraries were in use in Siemens VDO in 2007.
Together with the decision to switch to a common ECAD system the decision
was taken to create one common ECAD library.
Lib 5
Lib 1
Lib 2
Lib
Lib 3
Lib 6
Lib 4
2007
2008
2009
But this is history. Today in Continental Automotive AG 5 different ECAD

systems and 6 different ECAD libraries have to be merged.
Requirements
To create 3D Library figures linked to a new ECAD library with ~ 10.000
components
1. Round about 7.000 components are represented by nearly 250 ECAD
packages.
A 3D MCAD librrary has to be created linked to the existing ECAD
packages
2. All other components have more or less complex 3D shapes like
connectors. Often one packages represents only one component.
The workload of this item is out of scope of this lecture
3. New components, which requires a new ECAD package.
A maximum of synergy should be archived during the creation
process of the ECAD and the MCAD representation
Let start with item 1.
Requirements for Case 1

(Create MCAD representation for existing ECAD library figures with none complex shape)
7.000
components are
represented by
100 ECAD
parameter sets
The values inside
the ECAD parameter sets differs,
so that 250 ECAD
packages had to
be defined for the
7.000 components
Examples for
ECAD parameter sets

ECAD packaging and MCAD packaging is not always the same.
Examples:
LEDs of the same type and different colors: ECAD often do not care
about the color, which is important for MCAD
ECAD packages usually merge components with different heights.

It may be, that in special cases the choosen tolernace bandwidth is not
acceptable by MCAD. (Changing from one component to an other may
result in a short circuit although both components are represented by the
same package)
Acceptable Tolerance
Nominal Dimension

The shape for all components of each ECAD package should be the
same, but the height should be individually.
The shape should fullfill MCAD requirements, so that a reuse of the
place keepout of the ECAD library figures should be avoided.
Example for different ECAD and MCAD requirement: In MCAD the
complete shape of a SMD contact should be visible and the height of
the different feature should be closed to the real height .
Place Keepout of
ECAD library figure
Simplified 3D shape

(Maximum of synergy during the creation process of new ECAD and MCAD representation)
Following tasks has to be done, if an ECAD and a MCAD representation of the
same new component should be created
1. To extract parameters twice from specifications of PCB components to
create library figures by ECAD and MCAD librarians
2. To synchronize both libraries by fixing the values of common attributes for
the data exchange between the disciplines like Naming and Origin inclusive
orientation of the coordinate system
b5a000456
sot23
3. To create the shape twice (according different rules)

sot23_m01

4. Maybe to create the area for copper twice (Positioning of components without
copper information by mechanical engineers may result in short circuits)
Without copper information
Contact surface
With copper area information

Copper area
5. To create route and place keepouts with height workload in ECAD, which
can be created much faster in MCAD
6. To check, if the ECAD and MCAD figures fits together, which describes the
same component.
7. Modification of a library figure in one discipline should be easily reuseable

The maximum of synergy can be achieved, if

Parameter extraction and shape generation for both disciplines should be done
one time by one person
This will avoid additional the workload to prepare and to check the
synchronization of both library figures
Copper area defintion of ECAD should be reused by MCAD
Place and route keepout definition should be reused by ECAD
Modification of a master model can be taken over by both disciplines (A
alternative is a direct interface between ECAD and MCAD, which allow to import
modifications of library figures without destroying none modified library figure
information)

Additional requirements outside of the synergy stuff

Support of the task to merge similar components to ECAD packages
Preparation of an easily extraction of all required dimensions from supplier
specification. (It is a blemish, that a lot of supplier specification offer not all
required dimensions for the MCAD library figure creation process and for the
synchronization of ECAD and MCAD library figures. The 3D models offered by
supplieres are often not linked to a specific released specification)
Support of tolerances of 3D models

2 activities were started in Continental to implement tools, which fullfill the
requirements
4 sites in Germany starts to create 7000 MCAD library figures using a 3D
Component Generator
Wetzlar starts additional to achieve the maximum synergy while creating ECAD
and MCAD library figures for new components. This approach is based on the
Library Figure Editor ExOPaMo.
Both approachs are based on the same methodology:
definition of the lowest number of parametric 3D master models,
definition of a parameter set to drive the 3D master models and
which can be extended by a minimum of additional ECAD parameter.
The values of the parameters of each component are stored in separate XML File.

Definition of parametrical 3D Models
Today 2 parametrical 3D models are in use
Both models together allows to create 3D models for all 100 ECAD parameter sets
(for all 250 ECAD packages) mentioned before.
3D Component Generator
For each
ECAD
Parameter
Set a XML
File with
equations
instead of
values were
written
3D Component
Generator
A TCL script was
used to translate
the values of 7000
components into
the 7000 XML Files
with 3D parameter
sets
Adobe Acrobat
Document
A link to a 3D
projection and a
3D PDF Files. Both
has to be created
later.
3D Component Generator
In the next step a Toolkit application imports the parameter of each XML File
into the Pro/ENGINEER parametrical model and creates the 3D model of
each component.
To be independent of Pro/ENGINEER, a 3D PDF File and a STEP File was

created at the end.
The XML File is used additional as document for the component.
Editor ExOPaMo
The Editor ExoPaMo allows
to read a parameter set to

drive the 3D master model
to modify value by value of

the parameter set
to visualize a 2D projection
of the 3D parametrical
model with the actual values
to save the modified XML

File
Editor ExOPaMo
to create a DXF File with 3D wireframe information of the parametrical model

Wireframe
maximum
material
model
3D shape of
nominal
material
model
combined
with
wireframe
maximum
material
model
Editor ExOPaMo
to create a Zuken Text File, which can be imported by Zuken as library

component
Dimensions added manually
Editor ExOPaMo
A self written toolkit application integrated in Pro/ENGINEER is able to read the
XML File and modify the 3D parametrical model according the values stored in the
XML File.
Pro/ENGINEER Feature can be added
to the 3D geometry without destroying
the possibility to drive the 3D
component by the XML File
Flap of ZIF connector
in 2 positions

The two examples 3D Component Generator and ExOPaMo
demonstrate, that it is possible to drive a small number of parametric 3D
master models by standardized parameter sets to create a large number
of 3D PCB library parts.
The tool ExOPaMO demonstrate additional, that the same standardized
parameter set can be used to create (and modify) ECAD library figures.
The work with both tools points up,
that a lot of specifications delivered by the suppliers describes not enough
dimensions to satisfy the requirements of the ECAD and MCAD library
creation process.
That it is possible to create a standardized (digital) format, which allows the
supplieres to deliver geometrical library information for many PCB
components, which can be completed by additional 3D geometry for
complex 3D models

Master models and parameter sets exists, which satisfy the 4 use cases of the
ProSTEP iViP Project Group ECAD/MCAD Collaboration
A pre-released freeware program exists which allows to play with the proposed
parameter set (http://ecad-mcad-lib.v-jaekel.info)
Let start a discussion, if the proposed parameter set fits the requirements of
most users or if additional details are necessary.
Degree of
details not
Required !?
Example: Pin shape with angles and radius or without both
l1
l
Prosopal of
h ProSTEP iViP
Project Group
ECAD/MCAD
Collaboration
Contacts
Dr. Volker Jkel
Dr. Arnulf Frhlich
CAD Support
Manager CA-Processes
Hardware Development
Continental Automotive GmbH
PROSTEP AG
Volker.Jaekel@continental-corporation.com
arnulf.froehlich@prostep.com
... thanks a lot for

you attention !

0405 Presentation Froehlich Jaekel

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

0405 Presentation Froehlich Jaekel

Загружено:

Авторское право:

Доступные форматы

Standardized Library Components

for ECAD/MCAD Collaboration

ProSTEP iViP Project Group ECAD/MCAD Collaboration

2 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

ProSTEP iViP Project: ECAD/MCAD-Collaboration

4 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

4 project phases (2006 - 2009)

Key activities 2007

Key activities 2008

Key activities 2009

5 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Requirements for standardized 3D library components

Type & Parameter

Specification of 3D Master Models in standard format

7 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

UC1: Using library information within collaboration

8 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

UC2: Cross domain library to library data exchange

9 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

UC3: Provision of library data from supplier

10 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

UC4: Creation of packages based on similar parameter values

MCAD Library Information

11 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Main characteristics of three Master Model Types

Block with chamfers

Block with radial

Any number of pins

Add. body on top

12 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Dimensions are on views

13 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Example for the products designed by Continental in Wetzlar,

14 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Example for a PCB

Re-Import in 3D after finishing in ECAD

15 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

History of the plant Wetzlar

Das erste UKW

Nachdem 1997 der Philips

Das erste AutoRadio mit CD

Der CCC fr BMW geht in

Die Marke VDO

16 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Continental Corporate Presentation

Body & Security

17 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

History and ECAD libraries

But this is history. Today in Continental Automotive AG 5 different ECAD

19 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Requirements for Case 1

20 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Requirements for Case 1

ECAD packages usually merge components with different heights.

21 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Requirements for Case 1

22 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Requirements for Case 3

3. To create the shape twice (according different rules)

Requirements for Case 3

With copper area information

24 / A. Frhlich (PROSTEP AG), V. Jkel (Continental Automotive GmbH) / 12.05.2009

Requirements for Case 3

The maximum of synergy can be achieved, if