{"id":839,"date":"2018-07-31T13:13:43","date_gmt":"2018-07-31T20:13:43","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Teamcenter-Blog\/Design-Collaboration-ECAD-MCAD-Co-design\/ba-p\/512868"},"modified":"2026-03-26T08:44:17","modified_gmt":"2026-03-26T12:44:17","slug":"design-collaboration-ecad-mcad-co-design","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/teamcenter\/design-collaboration-ecad-mcad-co-design\/","title":{"rendered":"Design Collaboration: ECAD-MCAD Co-design"},"content":{"rendered":"

ECAD-MCAD Co-design \u2026 where design collaboration is optimal!<\/FONT><\/SPAN><\/H1>
\n

Learn more by watching this webinar, “Cross-domain design collaboration<\/A>,” as part of our webinar series on strategies to streamline product innovation<\/A>.<\/EM><\/FONT><\/SPAN><\/STRONG><\/P><\/p>\n

When we think about today\u2019s high tech products they typically involve a collaborative ECAD-MCAD design process between the Mechanical and Electronic design teams. This is important because <\/FONT><\/SPAN>ECAD-MCAD co-design<\/FONT><\/SPAN><\/A> processes can be spread out across multiple geographically dispersed locations. To be effective, each domain must work closely with one another in the timely exchange of design information to ensure the product can be designed, will function as the requirements dictate and will meet both the mechanical and electrical constraints.<\/FONT><\/SPAN><\/P>
\n

\"ECAD-MCAD-Co-design.png\"<\/span>Operating in their PLM environment ECAD and MCAD design teams can keep their designs in sync while sharing information on the initial design or collaborating on changes as the design evolves. Changes, or updates to the design can be shared on an incremental basis (verses having to pass the entire design). Both the ECAD and MCAD designer can accept or reject changes, as well as incorporate change notes or comments into the information being shared.<\/FONT><\/SPAN><\/P>
\n

To facilitate true ECAD-MCAD co-design and support the sharing, collaborating and cross-probing between the ECAD-MCAD design data requires the establishment of a common ECAD\/MCAD part library definition. The <\/FONT><\/SPAN>Siemens PLM ECAD<\/FONT><\/SPAN><\/A> and <\/FONT><\/SPAN>MCAD tool integrations<\/FONT><\/SPAN><\/A> support \u201citems as a part type\u201d which enables a single item definition for all representations of the part including the ECAD footprint and symbol and the MCAD 3D view (i.e., PRT and JT), as well as any common or specific ECAD and MCAD attributes. <\/FONT><\/SPAN><\/P>
\n

\"ECAD-MCAD-CAE-Design-Collaboration2.png\"<\/span>In addition to sharing the information across the ECAD and MCAD design processes, the same design information can be shared with the CAE engineer who needs it to perform a variety of simulation and analysis functions, such as evaluating thermal, vibration, shock, dust, and humidity effects.<\/SPAN><\/P>
\n

As a part of the \u201cissue management\u201d process where you reference the specific design, track the exchange of design data, and issue status throughout the product lifecycle, you can also receive notifications when changes are proposed and\/or accepted by the other team members.<\/SPAN><\/P>
\n

Watch ECAD-MCAD Collaboration for Co-design of Smart Products<\/A> and Eliminating ECAD-MCAD Domain Barriers with Siemens NX<\/A> to discover some of the benefits of true ECAD-MCAD Co-design.<\/SPAN><\/P>
\n

<\/p>\n