X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-UW-Orig-Sender: fpm AT homer11 DOT u DOT washington DOT edu Date: Mon, 4 Dec 2017 08:42:54 -0800 (PST) From: "Frank Miles (fpm AT u DOT washington DOT edu) [via geda-user AT delorie DOT com]" To: "James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] Including parts in a BOM that are not on the board In-Reply-To: Message-ID: References: User-Agent: Alpine 2.01 (LRH 1302 2010-07-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 6.3.3.2656215, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.12.4.163617, AntiVirus-Engine: 5.43.0, AntiVirus-Data: 2017.12.4.5430003 X-PMX-Server: mxout22.s.uw.edu X-Uwash-Spam: Gauge=X, Probability=10%, Report=' TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1200_1299 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, IN_REP_TO 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, NO_URI_HTTPS 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __NO_HTML_TAG_RAW 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0' Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, 1 Dec 2017, James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com] wrote: > Hi folks, > > Do you have recommendations for how to incorporate components into a BOM that > are not part of the netlist or board layout? > > For example, I'd like my BOM to include jumpers, specialized cabling, and the > crimp pins and connector required to mate with an on-board header. > > I was thinking of creating a separate .sch file, e.g. "peripherals.sch" and > including it in the BOM generation but not when I "import schematics" in the > layout. But am curious to know how others handle this. > > Thanks, > James Our solution adds considerable flexibility at the cost of added complexity. We use a database that is the real BOM master. Schematic-origin BOMs are automatically updated, adding parts (hardware, heat sinks, sockets,...), sometimes deleting or overriding part values for specific applications, and adding assembly notes. It also is used in generating netlists (including deleting pins or whole parts; altering footprints). It is integrated with with our ordering (tracks part costs) and cost evaluation processes. I too would be interested to hear how others manage these inevitable entanglements. -Frank