Why exchanging all design data to collaborate in cross domain environments? Hans-Ulrich Heidbrink Director Future Market Development Collaboration Projects

Why exchanging all design data to collaborate in cross domain environments?

Hans-Ulrich HeidbrinkDirector Future Market Development Collaboration ProjectsChairman ECAD-MCAD Collaboration at ProStep

NASA ESA Workshop Santa Barbara 2007

Agenda

Motivation— Starting point— Need to improve the Design Process

Why collaboration instead of Data exchange— History of the ProStep Project group "ECAD/MCAD-

Collaboration"— Objectives and project goals— Overview of current Collaboration Model — Proof of concept with representative Use Case

Applications— Architecture— Integration level

Future plans


Starting point

What are today’s most used Collaboration Methods in Engineering and Design?


Globalization

— “Follow the sun” design teams

— Outsourcing and subcontracting with IP protection

— Increasing Mechatronic integration needs

But how are globalization trends addressed ?

— Collaboration must be more than data transfer, view and mark up and visualization


Fire Wall

Future Design Process

MechanicalMechanical

ElectricalElectrical

LayoutLayout

Out SourceOut Source

SourcingSourcing

ManufacturingManufacturing

Project ManagerProject Manager

SchematicSchematic

Phone Mail/Paper based meetings

Another ECO, we have already spent 2 weeks with the last one!

I’m already late and I need to get back on schedule.

I will call everyone and organize a meeting.

I can’t change this logical block otherwise I

need to rework my

IO’s

I found signal

integrity errors.

I will move components to get better

access

I have collision with

the actual component placement

I need more test

points

We can’t use these

obsolete components

I don’t understand why we are using such pad stack


Another ECO, we have already spent 2 weeks with the last one!

I’m already late and I need to get back on schedule.

I will call everyone and organize a meeting.

I can’t change this logical block otherwise I

need to rework my

IO’sFire Wall

Future Design Process

MechanicalMechanical

ElectricalElectrical

LayoutLayout

Out SourceOut Source

SourcingSourcing

ManufacturingManufacturing

Project ManagerProject Manager

SchematicSchematic

I found signal

integrity errors.

I will move components to get better

access

I have collision with

the actual component placement

I need more test

points

We can’t use these

obsolete components

I don’t understand why we are using such pad stack

Phone Mail/Paper based meetings

Design Collaboration

Viewing, Redlines, Comments, Know how


Project History

Kick-off at ProStep iViP conference 2005 by Henry Potts Mentor Graphics

Workshops at ProStep in 2005 to establish the requirements based on recognized use cases

Mentor-PTC-Customer use case seminar with requirement review

Start of the evaluation of existing standards and of the data modeling activity begin 2006

Decision to apply to XML AIM Model mid 2006 Definition of proof of concept use cases Q1 2007


Objectives for Collaboration 1

Selective usage of common collaboration objects rather than file transfer

Ownership definition on object level Recognition of change impact related to the native

designs Change notification (self awareness) Traceability for approval, rejection and pending

changes (suspects) within the collaborative change request

Protection of IP during collaboration process Peer to peer and Proxy multi point solution required


Objectives for Collaboration 2

Multiple application levels or integrations enabled by collaboration model standard

Methodology that fits for global time shifted collaboration processes with asynchronous and synchronous application support

High user identification by reuse of existing GUI paradigms

Support of “What –if” Scenarios in a Sandbox Object Compare and validation functions Work authorization with versioning embedded in

Collaboration Process


Evaluation of existing standards

Current standards have been established for File transfer (IDF, IGES, DXF)

STEP provides standards (AP 210, Ap212, AP214, AP233…)

— Optimized for product data exchange — Performance critical in collaboration— Data volume very high— IP Protection critical— CAD systems are not supporting all APs— MCAD systems cannot represent electrical functions, as

ECAD system missing mechanical features But AP214 with AP 210 extensions as aim model can

build background for ECAD-MCAD Collaboration (with XML communication)


Scope of the 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

www.prostep.org/en/projektgruppen/ecad-mcad

http://www.prostep.org/en/projektgruppen/ecad-mcad


Project goals at ProStep Extend the ECAD or MCAD model with a cross domain

collaboration model that allows recourse to the full capabilities of the used CAD system

Establish a XML based collaborative data model to allow cooperation between ECAD and MCAD tools.

Implement CAD-object ownership in the design and change process

Ensure that changes are possible only by the owner of the objects

Allow synchronous and asynchronous collaboration with delta update capabilities for changes

Use the same methodology that establishes a collaboration baseline to substitute IDF based data exchanges


Workshops in 2005

Use Cases

Process

Collaboration Objects


Global Collaboration


ECAD/MCAD-Collaboration: Data Model Domains

property and material definition

person and organization information

constraint defintion

shape dependant information

item classificatio

n and grouping

item definition

and product structure

2d geometry model

3d geometry model

ECAD shape information


Summary Use Cases 2006 Definition of a board base line, Placement under mechanical constraints Placement under electronic constraints, Change of board elements Change of placement locations, Change of technology Replacement of components Panelization Component Change in existing design and Layout (SVDO) ECAD 2D integration into 3D MCAD product assembly (Delphi) Electronic Component integration into 3D MCAD product assembly (Delphi) MCAD Creation of Board Outline and transfer to ECAD (Delphi) ECAD 2.5D (complete Board) integration into 3D MCAD product assembly

(Conti) 3D MCAD Component integration into 2.5D ECAD (e.g. connectors) (Conti) MCAD Creation of 3D installation space (incl. Board Outline, Cutouts, ...) and

transfer to ECAD (Conti)

first GOAL: Definition of collaborationuse cases using the EDMD Schema


Use Case: Moving a mounting hole

Engineer John

Engineer Paula

I want to move this

hole…

… to this new

position



Engineer John

Engineer Paula

This new position is

not suitable …

… what is about this

one.



Engineer John

Engineer Paula

This new position

is suitable for me.

Thank you!


Use case preconditions

A design of the mechanical surrounding is available (major mechanical/electrical elements were placed (plugs, connections, LEDs etc.))

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

communicate through another channel.— In asynchronous mode the information is stored and the designers can

update 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.


MCAD Collaboration EDMDService Collaboration Layout Schematic

1

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. This components need to be marked within the 3D CADmodel in order to distinguish between the pure 3D geometry like a hole and the semantic information that this hole represents a "mounting hole"



1MCAD starts the design of the 3D geometry in the MCADsystem. 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. This components need to be marked within the 3D CADmodel in order to distinguish between the pure 3D geometry like a hole and the semantic information that this hole represents a "mounting hole"

Starts the schematic design based on the functional requirements.



1MCAD starts the design of the 3D geometry in the MCADsystem. 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. This components need to be marked within the 3D CADmodel in order to distinguish between the pure 3D geometry like a hole and the semantic information that this hole represents a "mounting hole"

Starts the schematic design based on the functional requirements.



2

After finishing the first version of the design a 2D boardoutline with position information about the components with mechanical/electrical interface function needs to be generated



2After finishing the first version of the design a 2D boardoutline with position information about the components with mechanical/electrical interface function needs to be generated

Schematic generates the netlist with the components and their interconnection.



2After finishing the first version of the design a 2D boardoutline with position information about the components with mechanical/electrical interface function needs to be generated

Schematics generates the

netlist with the components and

their interconnection.



3MCAD sends board outline to the Collaboration Space

MCAD sends board outline to the Collaboration Space




Collaboration Space includes all collaboration relevant parts of the design.






The synchronization of components IDs is done within the communication







A 1 2 3 3B 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 and net list from Schematic, so layout can be done.



4

Due to additional mechanical requirements (blue element). The position of a mounting hole needs to be updated. MCAD opens the 3D-model and modifies the hole-feature with the semantic "mounting hole" (an ID mapping already exist, see step 3)



5

Due to the fact that the electrical designer has done a PCB layout based on the first version the mechanical designer wants see if the placement modification is OK from the PCB point of view. He starts to send the changes to the collaboration space.



5Due to the fact that the electrical designer has done a PCB layout based on the first version the mechanical designer wants see if the placement modification is OK from the PCB point of view. He starts to send the changes to the collaboration space.

The collaboration model for the change request is initialized with reduced information (released information) and the new position of the mounting hole.





The change request is send via EDMDService.






Message is received and the user is asked if he wants to collaborate.







After accepting the collaboration request the model will be retrieved and opened in collaboration mode, the changes are loaded to the ECAD-System. How changes are visualized and shown to the user is up to the special application (e.g. integrated in the CAD-System, special collaboration viewer, …).







After accepting the collaboration request the model will be retrieved and opened in collaboration mode, the changes are loaded to the ECAD-System. How changes are visualized and shown to the user is up to the special application (e.g. integrated in the CAD-System, special collaboration viewer, …).

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



6

The ECAD designer checks the change request, in this case the new position of the mounting hole. ECAD system will provide assistance. In this sample the mounting hole color turns to red. If there is a special collaboration viewer it checks the change against the native data.



7

On recognizing the problem the ECAD-System sends a ‚reject‘ to the collaboration space.



7On recognzing the problem the ECAD-System sends a ‚reject‘ to the collaboration space.

The changed version is marked as ‚rejected‘ in the collaboration space.



7The changed version is marked as ‚rejected‘ in the collaboration space.

On recognzing the problem the ECAD-System sends a ‚reject‘ to the collaboration space.

The ‚reject‘ mark is transfered via EDMDService.



7The ‚reject‘ mark is transfered via EDMDService.

The changed version is marked as ‚rejected‘ in the collaboration space.

On recognzing the problem the ECAD-System sends a ‚reject‘ to the collaboration space.

The MCAD designer is informed about the rejection.



8

ECAD designer moves the mounting hole to valid position based in the routing. ECAD supports ECAD designer by checking the new position against his layout.



8ECAD designer moves the mounting hole to valid position based in the routing. ECAD supports ECAD designer by checking the new position against his layout.

The new position is loaded to the collaboration space.



8The new position is loaded to the collaboration space.


The new position is send as change request by EDMDService



8The new position is send as change request by EDMDService

The new position is loaded to the collaboration space


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



9

The MCAD designer checks the change request, in this case the new position of the mounting hole. MCAD system will provide assistance. If there is a special collaboration viewer it checks the change against the native data.



10

After checking the new data was successfull the MCAD designer accepts the new position of the mounting hole.



10After checking the new data was successfull the MCAD designer accepts the new position of the mounting hole.

The changed version is marked as ‚accepted‘ in the collaboration space.





The ‚accept‘ mark is transfered via EDMDService.






The ECAD designer is informed about the acceptance.






The ECAD designer is informed about the acceptance.

End of Collaboration Session


Architecture for Collaboration

The use case should reflect the developed architecture and the usage of the EDMD Schema within this architecture

The collaboration enhancement of the E/MCAD-systems were implemented by the system vendors PTC & Mentor


XML Integration Outside of the Mentor Flow

Server XML Collaboration

ApplicationDatabase

3rd PartyTools

XMLView(s)

XMLEDMD

Adapter

etc.

Neutral

ODB++

GerberFab NPI

Int DataStructure

XMLView(s)

PDF

DATA

BOM

PCB

Collaboration

DOC

3D

SCH

AssyDocs

FabDocs

XMLView(s)

Documentation

Inspect

Assy Test

XMLView(s)

Assy NPI

Non MentorData


Collaboration DM

Expedition Automation Layer

Persistent DBs

MOV – Manufacturing Output ValidationStackup Editor – India or Huntsville?

Persistent IDs

Mes

sag

ing

Bac

kbo

ne

MCAD

Outbound message

Inbound message

Mentor Collaboration Structure


Collaboration Model

Collaboration objects

Expedition Sandbox Design

Object Mapping

Collaboration ModelXML Based

Asynchronous Update Asynchronous Update


Mechanical (Sandbox) Design

Object Mapping


Application View


Expedition Sandbox Design

Expedition Native Design

Copy

Object Mapping


View in separate Layer EDMD elements


Connect to 3D Viewer


Additional communication capabilities Decision support functions,

— Raising the hand, — Giving the opinion, — Chat function — Redlining, view and mark-up capabilities

PLM functions— PLM method support for versioning, revisioning and

change request processes— Notification capabilities and self awareness function for

the object ownership model— Change in progress status — Opinion (sandbox proposal) status— Compare and copy function for sandbox and native

design


Plans for 2007

Proof of concept and validation of pilot applications

ProStep recommendation in Q4 2007 Extension of process model Validation of industrial applications based on

the collaboration model

Thank You

Documents

Why exchanging all design data to collaborate in cross domain environments? Hans-Ulrich Heidbrink Director Future Market Development Collaboration Projects