Issue link: https://iconnect007.uberflip.com/i/446087
40 The PCB Design Magazine • January 2015 TRuE MCAD-ECAD ARCHITECTuRE: A COMMON-SENSE APPROACH continues of a more integrated design environment than what was currently commercially available. When I approached a major EDA tool ven- dor at that show about what they were work- ing on to integrate this standard, I was greeted with a stern, "We will never consider it, because we cannot expose our proprietary IP!" Although I understood the IP argument made complete business sense, I still believed at some point in the future that the engineering masses, the merging EDA companies, and the power of com- puters and networks would be at a state where all of these current barriers would be gone. In the 2000s, all of these barriers did erode. Even the claim that EDA proprietary IP was sa- cred is no longer valid, as major companies have switched from one EDA vendor to another on multiple tools. Companies have recreated their IP on to their new EDA systems, and have now gone forward design- ing products with their new EDA vendors' tools and their IP. But despite all of this progress, a true MCAD- ECAD collaborative inte- grated design process tool environment has never materialized. In the sim- plest Dr. Phil terminology, EDA vendors still don't get it. I have tried to use some of these tools. I've sat down with these companies' inte- gration experts, and I've of- fered them insights of a design process system architect. Later, after they tell me that they have listened, I've gone back to their developers who now want to show me their new roadmaps. I still leave these meetings looking at a giant Error 404 expres- sion on their faces. I am not alone in my beliefs, as other senior industry experts have privately confided to me that they feel and see the same non-direction. So, rather than talking to more experts, go- ing into more technology meetings, or read- ing press clippings on these new collaborations just to be disappointed yet again, I am willing to offer the following solution on behalf of all engineers who have been waiting for a true MCAD-ECAD tool over these years. The goal of the following roadmap is to create a complete bi-directional, fully integrated tool within the next five years. By 2020, a true cost-affordable MCAD-ECAD tool needs to be available to every project engineering team. I can already hear the naysayers of the exist- ing EDA tool vendors raising their voices. But, for those of you who have not ever watched a single episode of Star Trek, remember how the Starship Enterprise and all of its technology came about: They just did it. So, here is my 10-step stra- tegic roadmap to create this MCAD-ECAD collaboration environment tool: 1) There needs to be a declaration by every EDA tool company within a month explaining whether they are in this initiative or out. It's that simple. Companies' strategic busi- ness leaders, the CEOs and CFOs, need to know who is willing to join this coali- tion, and who still thinks that they can do this inde- pendently (or isn't even in- terested in MCAD-ECAD). PS: You must remain com- mitted throughout its en- tirety, and not back out be- cause you and your company may not benefit directly. This initiative is for the majority of the engineering user community and NOT your egos. 2) There needs to be an independent lead- er who will drive the development of a true MCAD-ECAD standard built on a consensus for commonality. "Independent" means a per- son who is not tied to an EDA vendor in any way, shape, or form. The EDA vendors partici- pating in this standard creation will be allowed to provide many of their SMEs (subject matter the town crier I can already hear the naysayers of the existing eda tool vendors raising their voices. But, for those of you who have not ever watched a single episode of star trek, remember how the starship enterprise and all of its technology came about: they just did it. " "