0405 Presentation Froehlich Jaekel

Standardized Library Components for ECAD/MCAD Collaboration

ProSTEP iViP Symposium 200912.05.2009, Berlin

Dr. Volker Jkel, Continental Automotive GmbHDr. Arnulf Frhlich, PROSTEP AG

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

Agenda

ProSTEP iViP Project Group ECAD/MCAD CollaborationStandardized Library Components for ECAD/MCAD Collaboration

Use Cases3D Dimensioning Concept

Continental Corporate PresentationHistory of ECAD LibrariesRequirements3D Component Generator and Editor ExOPaMo

Outlook and Conclusion


ProSTEP iViP Project: ECAD/MCAD-CollaborationEnabling mandatory collaboration between ECAD and MCAD domains

Process-oriented Standard-based

Based on requirements/definitions from ECAD/MCAD-Workshops in 2005Definition of a STEP affiliated collaboration modelFirst data model based on STEP AP210 and AP214 entities has beendesigned in 2006

Made available as XML schema for implementationPSI 5 Recommendation 1.0 published 8th of May 2008

www.prostep.org/en/downloads/recommendations-standards.html(V1.2 April 2009)


Participants 2008/2009

UsersDelphiContinental

Service Providers:em

PDTecPROSTEPxPLMVendors

Mentor GraphicsPTCSiemens PLM

ResearchFU Hagen

ContactsChairman: Steve Hughes, Mentor Graphics Corp.Coordinator: Arnulf Frhlich, PROSTEP AG


4 project phases (2006 - 2009)Key activities 2006

Consolidation RequirementsAnalysis STEP AP210, AP212 and AP214

1st Milestone: Specification of initial data model for ECAD/MCAD-CollaborationKey activities 2007

Functional enhancements of data model for ECAD/MCAD-Collaboration2nd Milestone: PSI 5 Recommendation V1.0 for ECAD/MCAD-Collaboration

Key activities 2008System and Process IntegrationStandardization of 3D Components in Libraries

3rd Milestone: Updated PSI 5 Recommendation V1.2Key activities 2009

Certification GuidelinesEmbedding 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 typesThe 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 modelsInstantiated models may be modified/enriched by librarian informationInstantiated models should be used as simplified placeholder

Specification of 3D Master Models in standard formatUsers/Vendors could implement the master model concept in any CAD-System

Out of ScopeDetailed, exact geometry or technology information

Type & Parameter3D Master Models Library ComponentInstances


Use Cases

Use Case 1"Using library information within collaboration"

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"

Standardized Use Case Documentation

Standardized Use Case Documentation


UC1: Using library information within collaboration

ECAD Lib.

ECAD

MCAD Lib.

MCADC

o

l

l

a

b

o

r

a

t

i

o

n

M

o

d

u

l

e

C

o

l

l

a

b

o

r

a

t

i

o

n

M

o

d

u

l

e

3Standard-Types

3Standard-Types

EDMDCommunication

Explicit Component Information

Library Information (Type & Parameter)

+


UC2: Cross domain library to library data exchange

EDMDCommunication



+ECAD 2

ECAD Lib. 2

3Standard-Types

ECAD 2ECAD Lib. 2

3Standard-Types

ECAD 1ECAD Lib. 1

3Standard-Types

ECAD 1ECAD Lib. 1

3Standard-Types

MCAD 1MCAD Lib. 1

3Standard-Types

MCAD 1MCAD Lib. 1

3Standard-Types

MCAD 2MCAD Lib. 2

3Standard-Types

MCAD 2MCAD Lib. 2

3Standard-Types


UC3: Provision of library data from supplier

ECADECAD Lib.

3Standard-Types

Component Supplier

Customer

Componentdata sheet

MCADMCAD Lib.

3Standard-Types

EDMDCommunication



+


UC4: Creation of packages based on similar parameter values

ECADECAD Lib.

3Standard-Types

MCADMCAD Lib.

3Standard-Types

EDMDCommunication



+

Packages with instantiated

components with similar parameter

values


Main characteristics of three Master Model Types

2 straight pins2 pins Angled by 90

Any number of pinsType C, L, I or ZContact (Pin)

Block with radial chamfer or cylinder

CylinderBlock with chamfersAdd. body on topHoleCut

Basic Body

Diagram

Type CType BType AType

Characteristic


3D Dimensioning Concept

Represented in 3D PDF

Orientation of Coordinate System

Dimensions are on viewsACS_XY, ACS_ZX Body_XY, Body_YZChamfer_XYHole_XY, Hole_XZPin_XYCut_XY, Cut_ZX

Dimensions

Views

Type_A.pdf

xyz

xyz


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 MCADand will be finished in ECAD

3D master model of PCB Re-Import in 3D after finishing in ECAD


History of the plant WetzlarNachdem 1997 der Philips Konzern seine Sparte Philips Car Systems an Mannes-mann VDO verkauft, fusio-nieren 2001 Siemens Automotive und Mannes-mann VDO zur Siemens VDO Automotive AG.

Das erste Autoradio mit Kassetten-laufwerkwird produziert

Produktion der ersten Navigations-systeme

Die Continental AGbernimmt die Siemens VDO Automotive AG. Jetzt zhlt das Unternehmen 150.000 Mitarbeiter an 200 Standorten in 34 Lndern.

Der RNS (Radio Navigation System) fr VW wird von der Presse gefeiert.

1946

1953

1974

1988

1993 2001

Das erste Auto-Radio mit CD wirdIn Serie produziert. Start Navigations-Entwicklung

Das erste UKW Autoradio wird in Wetzlar produziert. Die Stationstasten waren aus Patronenhlsen

Mannesmann VDO bernimmt Philips Car SystemsDie Marke VDO Daytonentsteht

Philips erffnet in Wetzlar eineProduktionsstttefr Trafos und Rundfunkgerte(Philetta)

1998 2005

1/2008: ber 1 Million Multimedia-Systeme fr BMW produziert

2007

Der CCC fr BMW geht in Serie

2008


Continental Corporate Presentation

ContiTech

Air Spring Systems

Benecke-Kaliko

Group

Conveyor Belt Group

Elastomer Coatings

Fluid Technology

Power Transmission

Group

Vibration Control

Other Operations

Pkw-Reifen

Erstausrstung

Ersatzgeschft

Europa & Afrika

Ersatzgeschft

The Americas

Ersatzgeschft

Asien

Zweiradreifen

Nfz-Reifen

Lkw-Reifen

Europa

Lkw-Reifen

The Americas

Lkw-Reifen

Ersatzgeschft

Asien

Industriereifen

Chassis & Safety

Electronic

Brake Systems

Hydraulic

Brake Systems

Sensorics

Passive Safety

& ADAS

Chassis

Components

Powertrain

Engine Systems

Transmission

Hybrid Electric

Vehicle

Sensors &

Actuators

Fuel Supply

Interior

Body & Security

Commercial

Vehicles &

Aftermarket

Infotainment &

Connectivity

Instrumentation &

Displays,

Interior Modules

Continental Corporation

Automotive Group Rubber Group


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.

But this is history. Today in Continental Automotive AG 5 different ECAD systems and 6 different ECAD libraries have to be merged.

Lib 1Lib 2

Lib 3

Lib 4

Lib

Lib 6

Lib 5

2007 2008 2009


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 lecture3. 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)

Examples forECAD parameter sets

7.000 components are represented by 100 ECAD parameter setsThe values inside the ECAD para-meter sets differs, so that 250 ECAD packages had to be defined for the 7.000 compo-nents



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 mayresult in a short circuit although both components are represented by the same package)

Nominal Dimension

Acceptable Tolerance



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


Requirements for Case 3 (Maximum of synergy during the creation process of new ECAD and MCAD representation)

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

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

Following tasks has to be done, if an ECAD and a MCAD representation of the same new component should be created

sot23sot23_m01b5a000456



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

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

Without copper information With copper area informationContact surface Copper area



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


3D Component Generator and Editor ExOPaMo2 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.


3D Component Generator and Editor ExOPaMoDefinition of parametrical 3D ModelsToday 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 GeneratorFor each ECAD Parameter Set a XML File with equationsinstead of values were written


3D Component GeneratorA TCL script was used to translate the values of 7000 components into the 7000 XML Files with 3D parameter sets

A link to a 3D projection and a 3D PDF Files. Both has to be created later.

Adobe Acrobat Document


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 ExOPaMoThe 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

Wireframemaximummaterialmodel

wireframemaximummaterialmodel

3D shape ofnominalmaterialmodel

combinedwith


Editor ExOPaMo to create a Zuken Text File, which can be imported by Zuken as library

component

Dimensions added manually


Editor ExOPaMoA 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 connectorin 2 positions


Outlook and ConclusionThe 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 numberof 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 forcomplex 3D models


Outlook and Conclusion 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.

Example: Pin shape with angles and radius or without both

l

l1t h

Prosopal ofProSTEP iViP Project Group ECAD/MCAD Collaboration

D

e

g

r

e

e

o

f

d

e

t

a

i

l

s

n

o

t

R

e

q

u

i

r

e

d

!

?

Contacts

Dr. Volker JkelCAD SupportHardware Development

Continental Automotive [email protected]

Dr. Arnulf FrhlichManager CA-Processes

PROSTEP [email protected]

... thanks a lot for you attention !

0405 Presentation Froehlich Jaekel

Documents

Transcript of 0405 Presentation Froehlich Jaekel