User guide

Creating BOMs
PCN Process User Guide (301945-A)
Creating and Updating BOMs: 5-7
Note:
The mechanical engineer for the project may be in charge of this include file.
4.
Copy any files that you need into the appropriate /bay
dir
/dra/2brel
directories to support your changes (see Chapter 4), for example into:
/bay
dir
/dra/2brel/docs/
PartNumber.nn
/
/bay
dir
/dra/2brel/mech/
PartNumber.nn
/
/bay
dir
/dra/2brel/mech/pwahdw/
PartNumber
.lst
/bay
dir
/dra/2brel/programs/
PartNumber.nn
/
5.
Re-run
bn_bomprocess
to create the various files that show the
differences between this and the previous minor revision level of this
project or part:
bn_bomprocess
SchematicName
-config
ConfigFile
.cfg
The
bn_bomprocess
should generate a number of output files (
.profile
,
_changes.rev
,
.sap
,
_proto.diff
,
_cost.lst
,
_leadtime.lst, parts.lst
,
bne_bp.lst
,
bn_bomprocess.log
) that it places in (a) your working directory
or a directory specified in the config file’s
REPORT_DIR_NAME
statement; and
(b) when the PCN is done, in
/bay
dir
/dra/rel/pcn_data/
PPP
000/
PartNumber.nn
, where
PPP
is the first three digits of the part number.
Caution:
Be sure to examine the resulting
_proto.diff
file to make sure it represents the changes
that you have made, for example, to see that it shows an appropriate rev number change, and the
correct numbers of changes (functional and descriptive).
6.
Run bom_upload (as described in Chapter 6).
This will start the (not entirely automatic) process that will result in moving
your files from
/bay
dir
/dra/2brel
to
/bay
dir
/dra/rel
, in issuing a PCN, and in
providing the data for EDA to update the SAP records.
Using mechbom to Create or Update a BOM
The
mechbom
script was designed to create initial and early BOMs for
assemblies that have not been created as part of the normal process of starting a
new project and running
bn_bomprocess
as explained in
Creating a BOM with
bn_bomprocess
on page 5-6.
You need to use the
mechbom
process described here if you create or update
recent BOMs for mechanical, i.e., non-schematic, parts.
Note:
Do not use
mechbom
for 920-level BOMs because it does not support multi-line lists of
reference designators.