Issue link: https://iconnect007.uberflip.com/i/1114420
76 DESIGN007 MAGAZINE I MAY 2019 • Electronically accept or reject proposed changes • Electronically add notes to the collaboration file regarding design intent • Retain change history regarding who did what, why, and when The IDX files generated from either the ECAD or MCAD tools are then managed in a "collaboration" folder located on either a local or shared drive. "IDF was a good step in the right direction. We were able to pre-locate components, rep- resent holes and transfer keep-in/-out infor- mation," stated Shawn Larson, senior tech- nical fellow at Zuken. "Today with IDX, we have a much more robust model of the PCB and its structure. Board-level components, trac- es, pads, copper, component heights, rigid/flex support, and more can be passed. We even have the ability to accept or reject changes electroni- cally. The word 'collaboration' fits much better with the way we want to work, and the day- to-day data flow between the mechanical and electronic teams is cleaner and clearer." While IDX may not be perfect, it does pro- vide a better way to more accurately and clear- ly communicate design intent between do- mains and achieve business goals. "Companies today are striving to streamline their design process and reduce the oppor- tunity for introducing errors throughout the product life cycle," said Sandra Humphrey, se- nior consultant at Archer Grey. "Utilizing IDX allows companies to introduce products to market faster and with higher quality by en- abling interdisciplinary collaboration, which provides an efficient method to communicate design intent, initiate change proposals, and ensure these work items are completed in a timely manner irrespective of geographic lo - cation." How Does IDX Data Exchange Work? You can think of IDX as a way to initiate and perpetuate a virtual "conversation" with the person you are collaborating with. Whoev- er initiates that conversation must also be the one that receives the final acknowledgment. Let's take a look at two scenarios: 1. Initial "Baseline" Data Exchange • "Discussion" is initiated by either ECAD or MCAD and sent to the other domain as a "baseline" file that contains all of the data in an initial exchange • The received file is then imported and previewed • A response is sent to initiator acknow- ledging the successful baseline import • The databases are now in sync, and either side is free to make additional updates Figure 2: Typical ECAD/MCAD collaboration flow diagram.