Issue link: https://iconnect007.uberflip.com/i/1533085
a point on our list: "Provide a clear, concise, single-sourced specification." Kolar: It's fine to have the PDFs, as long as they are generated from the final source data. If you're generating an ODB++ package, your fab layers and assembly nodes are in there. As long as they're all in your package as the proper layers, you can make PDFs of them. is can speed up quoting because there are some fab vendors who, at the front end of people quot- ing, can't work with the actual data. Dack: What about our really advanced think- ers who argue that everything should be con- tained in the project or the design data? Can it be? Kolar: Maybe. It's an awesome idea, and nice to have. For a simpler design, it probably can work if you are careful and accurate. If you're working with some of the really cheap com- modity fabrication services, you don't even talk to a human being. You upload your data, interpret it, and off it goes. We need to have a capability and process approach, especially with offshore suppli- ers and larger volumes and the different ways things are done compared to working with a proto shop in the U.S. Again, this is another area where communication is so important. e customer needs to tell the designer, "By the way, this will ultimately be manufactured in volume offshore." Dack: at's right, and if it's outlined up front, then we don't have to worry about it. Let's get the end game defined. Let's plan before we fin- ish. Let's start with the end in sight. Kolar: Communication upfront is key, and a design kickoff checklist and design review pro- cess are really helpful. Thank you all for sharing your input on this. Kolar: It's always a pleasure, Andy. DESIGN007 16 DESIGN007 MAGAZINE I MARCH 2025