X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Virus-Status:	Clean
X-Virus-Scanned:	clamav-milter 0.98.4 at av01.lsn.net
Message-ID:	<55456D1A.3030904@ecosensory.com>
Date:	Sat, 02 May 2015 19:34:34 -0500
From:	John Griessen <john AT ecosensory DOT com>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0
MIME-Version:	1.0
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Automation of non-EDA processes around gEDA
References:	<CALT8Ef51_5-G-w6W1_1q7-XaOQU0UV1wFME9--xwVx=H3bBUjA AT mail DOT gmail DOT com>
In-Reply-To:	<CALT8Ef51_5-G-w6W1_1q7-XaOQU0UV1wFME9--xwVx=H3bBUjA@mail.gmail.com>
Reply-To:	geda-user AT delorie DOT com

On 05/01/2015 07:02 PM, Shashank Chintalagiri wrote:
>   * I work at a company where we build instrumentation in low volume.
> BOMs are constantly in flux, even when the base PCB doesn't change.
> Additionally, we have a few PCBs which can be populated in a wide
> variety of ways by a combination of DNP/DNI and component value
> changes. Manually maintaining these BOMs off-schematic was getting too
> cumbersome.


Sounds like a perfect match for most users of gEDA tools --> niche markets
and able to handle different work styles.


"our input costs can
be significantly affected by optimising upstream orders and exploting
cross-PCB and even cross-Product Line overlaps in BOM"

Yes and yes.

"Estimate financial outlay for a specified production cycle.
      5. Generate various documentation, including schematic PDFs,
reference BOMs per configuration, Assembly Manifests, Purchase Orders,
Gerber Zips, etc."

Yes, yes, yes, yes, yes...

"restrictive naming conventions can be irritating and time consuming to
move to. In essence, I would imagine every Koala implementation could
eventually have it's own naming conventions. Additional features need
extra attributes to be added to gEDA schematics."

NO and sure, and OK for adding extra attributes.

"I've never gotten the
hang of hierarchial schematics, so those aren't in any way supported."

That's incompatible with most users future desires.  But, it might be handled by a subset case
since a hierarchic schematic can be flattened.  It's not a match though, so
suggests creating a separate tool, rather than merging into gschem or PCB.

John Griessen

-- 
Ecosensory  1218 W 39th St.  Austin TX 78756

- Raw text -