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

1. Why exchanging all design data to collaborate in cross domain environments? Hans-Ulrich Heidbrink Director Future Market Development Collaboration Projects Chairman ECAD-MCAD Collaboration at ProStep

2. 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 NASA ESA Workshop Santa Barbara 2007

3. Starting point • What are today’s most used Collaboration Methods in Engineering and Design? NASA ESA Workshop Santa Barbara 2007

4. 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 NASA ESA Workshop Santa Barbara 2007

5. Fire Wall Future Design Process Schematic 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. Out Source I can’t change this logical block otherwise I need to rework my IO’s I don’t understand why we are using such pad stack Project Manager Electrical Sourcing We can’t use these obsolete components I found signal integrity errors. Phone Mail/Paper based meetings Manufacturing Layout Mechanical I have collision with the actual component placement I need more test points I will move components to get better access NASA ESA Workshop Santa Barbara 2007

6. Fire Wall Future Design Process Schematic 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. Out Source I can’t change this logical block otherwise I need to rework my IO’s I don’t understand why we are using such pad stack Project Manager Electrical Sourcing We can’t use these obsolete components I found signal integrity errors. Phone Mail/Paper based meetings Design Collaboration Viewing, Redlines, Comments, Know how Manufacturing Layout Mechanical I have collision with the actual component placement I need more test points I will move components to get better access NASA ESA Workshop Santa Barbara 2007

7. 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 NASA ESA Workshop Santa Barbara 2007

8. 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 NASA ESA Workshop Santa Barbara 2007

9. 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 NASA ESA Workshop Santa Barbara 2007

10. 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) NASA ESA Workshop Santa Barbara 2007

11. 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 NASA ESA Workshop Santa Barbara 2007

12. 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 NASA ESA Workshop Santa Barbara 2007

13. Workshops in 2005 Use Cases Process Collaboration Objects NASA ESA Workshop Santa Barbara 2007

14. Global Collaboration NASA ESA Workshop Santa Barbara 2007

15. ECAD/MCAD-Collaboration: Data Model Domains person and organization information item definition and product structure item classification and grouping ECAD shape information shape dependant information constraint defintion 3d geometry model property and material definition 2d geometry model NASA ESA Workshop Santa Barbara 2007

16. 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 NASA ESA Workshop Santa Barbara 2007

17. Use Case: Moving a mounting hole Engineer John I want to move this hole… … to this new position Engineer Paula NASA ESA Workshop Santa Barbara 2007

18. Use Case: Moving a mounting hole Engineer John This new position is not suitable … … what is about this one. Engineer Paula NASA ESA Workshop Santa Barbara 2007

19. Use Case: Moving a mounting hole Engineer John This new position is suitable for me. Thank you! Engineer Paula NASA ESA Workshop Santa Barbara 2007

20. 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. NASA ESA Workshop Santa Barbara 2007

21. 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" NASA ESA Workshop Santa Barbara 2007

22. Starts the schematic design based on the functional requirements. NASA ESA Workshop Santa Barbara 2007

23. NASA ESA Workshop Santa Barbara 2007

24. 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 NASA ESA Workshop Santa Barbara 2007

25. Schematic generates the netlist with the components and their interconnection. NASA ESA Workshop Santa Barbara 2007

26. NASA ESA Workshop Santa Barbara 2007

27. MCAD sends board outline to the Collaboration Space NASA ESA Workshop Santa Barbara 2007

28. Collaboration Space includes all collaboration relevant parts of the design. NASA ESA Workshop Santa Barbara 2007

29. The synchronization of components IDs is done within the communication NASA ESA Workshop Santa Barbara 2007

30. A 1 2 3 3 B 2 3 5 4 C 3 4 5 4 D 3 4 5 4 E 2 3 4 4 A 1 2 3 3 B 2 3 5 4 C 3 4 5 4 D 3 4 5 4 E 2 3 4 4 ECAD reads base line from collaboration space and net list from Schematic, so layout can be done. NASA ESA Workshop Santa Barbara 2007

31. 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) NASA ESA Workshop Santa Barbara 2007

32. 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. NASA ESA Workshop Santa Barbara 2007

33. The collaboration model for the change request is initialized with reduced information (released information) and the new position of the mounting hole. NASA ESA Workshop Santa Barbara 2007

34. The change request is send via EDMDService. NASA ESA Workshop Santa Barbara 2007

35. Message is received and the user is asked if he wants to collaborate. NASA ESA Workshop Santa Barbara 2007

36. 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, …). NASA ESA Workshop Santa Barbara 2007

37. Remark: There could be some components with no correspondence in the MCAD world and vice versa. NASA ESA Workshop Santa Barbara 2007

38. 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. NASA ESA Workshop Santa Barbara 2007

39. On recognizing the problem the ECAD-System sends a ‚reject‘ to the collaboration space. NASA ESA Workshop Santa Barbara 2007

40. The changed version is marked as ‚rejected‘ in the collaboration space. NASA ESA Workshop Santa Barbara 2007

41. The ‚reject‘ mark is transfered via EDMDService. NASA ESA Workshop Santa Barbara 2007

42. The MCAD designer is informed about the rejection. NASA ESA Workshop Santa Barbara 2007

43. 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. NASA ESA Workshop Santa Barbara 2007

44. The new position is loaded to the collaboration space. NASA ESA Workshop Santa Barbara 2007

45. The new position is send as change request by EDMDService NASA ESA Workshop Santa Barbara 2007

46. The new position is loaded to MCAD and shown to the user. It is up to the application in which way this is done. NASA ESA Workshop Santa Barbara 2007

47. 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. NASA ESA Workshop Santa Barbara 2007

48. After checking the new data was successfull the MCAD designer accepts the new position of the mounting hole. NASA ESA Workshop Santa Barbara 2007

49. The changed version is marked as ‚accepted‘ in the collaboration space. NASA ESA Workshop Santa Barbara 2007

50. The ‚accept‘ mark is transfered via EDMDService. NASA ESA Workshop Santa Barbara 2007