BOM

I have the same issue, I am interested in if one could give us an idea how

should we do this professionally.

Thank you,

Z.

"Amer Abufadel" <amer.abufadel@gmail.com> wrote in message

news:gqc339$r4i$1@cheetah.cadsoft.de...

Hello all,

  In my designs, I keep a spreadsheet that has all the components that I

used along with the manufacturer's part number and the vendor and the part

number there as well.  I am pretty sure everyone here has something

similar, but what I was wondering is if there is a way I can do this

within Eagle and not go back and forth between Eagle, Firefox and Excel.

 

Thank you,

 

A

On Fri, 27 Mar 2009 00:59:09 -0700, Zoly wrote:

I have the same issue, I am interested in if one could give us an idea

how should we do this professionally.

Thank you,

Z.

 

"Amer Abufadel" <amer.abufadel@gmail.com> wrote in message

news:gqc339$r4i$1@cheetah.cadsoft.de...

Hello all,

  In my designs, I keep a spreadsheet that has all the components that

  I

used along with the manufacturer's part number and the vendor and the

part number there as well.  I am pretty sure everyone here has

something similar, but what I was wondering is if there is a way I can

do this within Eagle and not go back and forth between Eagle, Firefox

and Excel.

 

Thank you,

 

A

Here is my 2 cents.  In well constructed professional systems there is

one control point for design data, the schematic, and one control point

for the parts in the schematic, the library.  The common disconnect that

occurs within companies is between the MRP system data and the part

library.  Companies spend much time and money trying to control this

connection.  A good example is ORCAD & ORACAL.  Invariably, part database

control is an endless frustration. 

All part data must be kept in one place and revision controlled (ie.

SVN).  Eagle does not have an automated method of checking parts in the

schematic with the library to make sure all is in compliance.  However,

if the data to control ordering is entered as an attribute in the part

library, that data will automatically go into the schematic.  Eagle will

indicate if the user overrides this information (attribute view) but it

would be a good suggestion to add that to the DRC.  A ULP can be written

to promote VALUES from an attribute to the VALUE field for the part.  The

BOM with attributes ULP can be used to output the part data to a CSV so

it can used to upload to an MRP system.

Greg