ProSTEP iViP Use Case ECAD MCAD Collaboration 1.0

8/3/2019 ProSTEP iViP Use Case ECAD MCAD Collaboration 1.0

1/46

Establishing Leadership in IT-Based Engineering

2007, ProSTEP iViP e.V. 07-08-09

ECAD/MCAD-Collaboration

General, underlying Use Case

"Moving a mounting hole

May 2007

Chairman: Hans-Ulrich Heidbrink, Mentor GraphicsProSTEP Contact: Dr. Arnulf Frhlich, PROSTEP AG


2/46



ECAD/MCAD-Collaboration: Project Aim

Aim of the ProSTEP iViP Associations

ECAD/MCAD-Collaboration is to

facilitate collaboration between the ECADand MCAD domains in such a way that

users in one domain have access to all

relevant information in the other domain.


3/46



Current Project Participants

Delphi

Siemens VDO

:em

Mentor Graphics

PDTec

PROSTEP PTC

UGS

xPLM

FU Hagen


4/46



Use Case: Moving a mounting hole 1/3

Engineer Knut

Engineer Paula

I want tomove this

hole

to thisnew

position


5/46




Engineer Knut

Engineer Paula

This newposition is

not suitable

what isabout this

one.


6/46




Engineer Knut

Engineer Paula

This newposition is

suitablefor me.

Thankyou!


7/46



Use case preconditions

A design of the mechanical surrounding is available (majormechanical/electrical elements were placed (plugs, connections, LEDsetc.))

The PCB board outline is defined within the

mechanical CAD-system The use case can be done in synchronous or asynchronous mode:

In synchronous mode the changes are shown while designers communicatethrough another channel.

In asynchronous mode the information is stored and the designers canupdate the models on demand.

There are there spaces, where data is stored: ECAD: Represents the ECAD-System including the collaboration module

MCAD: Represents the MCAD-System including the collaboration module Collaboration Space: Represents the shared data, where all relevant data

is stored.


8/46



1

SchematicLayoutCollaborationEDMDServiceCollaborationMCAD

MCAD starts the design of the 3D geometry in the MCAD system.Designs also components with electrical/mechanical function(plugs, LEDs, switches) or big mechanical impact (big ICs,capacitors). Also the mounting holes of the PCB are defined. Thiscomponents need to be marked within the 3D CADmodel in order

to distinguish between the pure 3D geometry like a hole and thesemantic information that this hole represents a "mounting hole"


9/46



MCAD starts the design of the

3D geometry in the

MCADsystem. Designs also

components withelectrical/mechanical function(plugs, LEDs, switches) or bigmechanical impact (big ICs,

capacitors). Also the mounting

holes of the PCB are defined.This components need to bemarked within the 3D

CADmodel in order to

distinguish between the pure3D geometry like a hole and thesemantic information that this

hole represents a "mounting

hole"

1


Starts the schematic design based on the functionalrequirements.


10/46



Starts the schematic design

based on the functional

requirements.

MCAD starts the design of the

3D geometry in the

MCADsystem. Designs also

components withelectrical/mechanical function(plugs, LEDs, switches) or bigmechanical impact (big ICs,

capacitors). Also the mounting

holes of the PCB are defined.This components need to bemarked within the 3D

CADmodel in order to

distinguish between the pure3D geometry like a hole and thesemantic information that this

hole represents a "mounting

hole"

1



11/46



2


After finishing the first version of the design a 2Dboardoutline with position information about thecomponents with mechanical/electrical interfacefunction needs to be generated


12/46



After finishing the first version

of the design a 2D boardoutline

with position information about

the components withmechanical/electrical interfacefunction needs to be generated

2


Schematic generates the netlist with the componentsand their interconnection.


13/46



Schematics generates the

netlist with the components and

their interconnection.

After finishing the first version

of the design a 2D boardoutline

with position information about

the components withmechanical/electrical interfacefunction needs to be generated

2



14/46



MCAD sends board outline to

the Collaboration Space3


MCAD sends board outline to the Collaboration Space


15/46



Collaboration Space includes all

collaboration relevant parts of

the design.




Collaboration Space includes all collaborationrelevant parts of the design.


16/46



The synchronization of

components IDs is done within

the communication



the design.




The synchronization of components IDs is done withinthe communication


17/46





the communication



the design.




A 1 2 3 3

B 2 3 5 4C 3 4 5 4D 3 4 5 4E 2 3 4 4

A 1 2 3 3B 2 3 5 4C 3 4 5 4D 3 4 5 4E 2 3 4 4

ECAD reads base line from collaboration space andnet list from Schematic, so layout can be done.


18/46



ECAD reads base line from

collaboration space and net list

from layout, so layout can bedone.



the communication



the design.




A 1 2 3 3

B 2 3 5 4C 3 4 5 4D 3 4 5 4E 2 3 4 4

A 1 2 3 3B 2 3 5 4C 3 4 5 4D 3 4 5 4E 2 3 4 4


19/46



4


Due to additional mechanical requirements (blueelement). The position of a mounting hole needs to beupdated. MCAD opens the 3D-model and modifies thehole-feature with the semantic "mounting hole" (an ID

mapping already exist, see step 3)


20/46



Due to additional mechanical

requirements (blue element).

The position of a mounting holeneeds to be updated. MCAD

opens the 3D-model andmodifies the hole-feature withthe semantic "mounting hole"

(an ID mapping already exist,

see step 3)

4



21/46



5


Due to the fact that the electrical designer has done aPCB layout based on the first version the mechanicaldesigner wants see if the placement modification isOK from the PCB point of view. He starts to send the

changes to the collaboration space.


22/46



Due to the fact that the

electrical designer has done a

PCB layout based on the firstversion the mechanical

designer wants see if theplacement modification is OKfrom the PCB point of view. He

starts to send the changes to

the collaboration space.

5


The collaboration model for the change request isinitialized with reduced information (releasedinformation) and the new position of the mountinghole.


23/46



The collaboration model for the

change request is initialized

with reduced information(released information) and the

new position of the mountinghole.







5


The change request is send via EDMDService.


24/46



The change request is send via

EDMDService.











5


Message is received and the user is asked if he wantsto collaborate.


25/46



Message is received and the

user is asked if he wants to

collaborate.


EDMDService.











5


After accepting the collaboration request the modelwill be retrieved and opened in collaboration mode,the changes are loaded to the ECAD-System. Howchanges are visualized and shown to the user is up to

the special application (e.g. integrated in the CAD-System, special collaboration viewer, ).


26/46



After accepting the

collaboration request the model

will be retrieved and opened incollaboration mode, the

changes are loaded to theECAD-System. How changesare visualized and shown to the

user is up to the special

application (e.g. integrated inthe CAD-System, specialcollaboration viewer, ).



collaborate.


EDMDService.











5


Remark:There could be some components with nocorrespondence in the MCAD world and vice versa.


27/46



After accepting the

collaboration request the model

will be retrieved and opened incollaboration mode, the

changes are loaded to theECAD-System. How changesare visualized and shown to the

user is up to the special

application (e.g. integrated inthe CAD-System, specialcollaboration viewer, ).



collaborate.


EDMDService.











5


Remark:There could be somecomponents with no

correspondence in the

MCAD world and vice versa.


28/46



6


The ECAD designer checks the change request, in thiscase the new position of the mounting hole. ECADsystem will provide assistance. In this sample themounting hole color turns to red. If there is a special

collaboration viewer it checks the change against thenative data.

LMCAD


29/46



The ECAD designer checks the

change request, in this case the

new position of the mountinghole. ECAD system will provide

assistance. In this sample themounting hole color turns tored. If there is a special

collaboration viewer it checks

the change against the nativedata.

6


L tMCAD


30/46



7


On recognizing the problem the ECAD-System sendsa reject to the collaboration space.

L tMCAD


31/46



On recognzing the problem the

ECAD-System sends a reject

to the collaboration space.7


The changed version is marked as rejected in thecollaboration space.

S h tiLa o tC ll b tiEDMDS iC ll b tiMCAD


32/46





to the collaboration space.

The changed version is marked

as rejected in the collaboration

space.7


The reject mark is transfered via EDMDService.

SchematicLayoutCollaborationEDMDSer iceCollaborationMCAD


33/46








space.

The reject mark is transfered

via EDMDService.7


The MCAD designer is informed about the rejection.



34/46








space.

The reject mark is transfered

via EDMDService.

The MCAD designer is

informed about the rejection.7




35/46



8


ECAD designer moves the mounting hole to validposition based in the routing. ECAD supports ECADdesigner by checking the new position against hislayout.



36/46



ECAD designer moves the

mounting hole to valid position

based in the routing. ECADsupports ECAD designer by

checking the new positionagainst his layout.

8


The new position is loaded to the collaboration space.



37/46







The new position is loaded to

the collaboration space.8


The new position is send as change request byEDMDService



38/46








the collaboration space

The new position is send as

change request by

EDMDService8

Sc e at cLayoutCo abo at oSe ceCo abo at oMCAD

The new position is loaded to MCAD and shown to theuser. It is up to the application in which way this isdone.



39/46








the collaboration space

The new position is send as

change request by

EDMDService


MCAD and shown to the user.

It is up to the application inwhich way this is done.

8

LayoutMCAD



40/46



9

LayoutMCAD

The MCAD designer checks the change request, inthis case the new position of the mounting hole.MCAD system will provide assistance. If there is aspecial collaboration viewer it checks the change

against the native data.



41/46



The MCAD designer checks the

change request, in this case the

new position of the mountinghole. MCAD system will provide

assistance. If there is a specialcollaboration viewer it checksthe change against the native

data.

9

y



42/46



10

y

After checking the new data was successfull theMCAD designer accepts the new position of themounting hole.



43/46



After checking the new data

was successfull the MCAD

designer accepts the newposition of the mounting hole.

10

y

The changed version is marked as accepted in thecollaboration space.



44/46




as accepted in the

collaboration space.




10

The accept mark is transfered via EDMDService.



45/46



The accept mark is transfered

via EDMDService.


as accepted in the





10

The ECAD designer is informed about the acceptance.



46/46



The ECAD designer is informed

about the acceptance.

The accept mark is transfered

via EDMDService.


as accepted in the





10

ProSTEP iViP Use Case ECAD MCAD Collaboration 1.0

Documents