User guide

C-2: FAQ
5
Since the BOM details the component changes, how detailed does the
description field need to be on a PCN? What information should be in this field?
ANS: Use the Description Change field to explain
why
the change was made,
not what the change actually is! It gives some visibility of the problem or fix
and its consequences, e.g., “Device U1 changed to prevent unit failing when
hot,” or “Device U1 changed to alternative as original part is no longer
available.”
6
Can the PCN process be web-based? For small changes it would be faster to
edit a BOM form on the web which could then be submitted to SAP.
ANS: We are looking at moving to web-based tools.
7
How do I change something marked “released.”
ANS: For custom components, write an ECO. (You can use released parts on a
board in development.) For purchased part specs, the Component Engineering
group is responsible for writing the ECO.
8
What differences are there in the processes for the East and West coast?
ANS: There are many differences, including (very briefly): different legacy
part numbers with different ways of expressing the major and minor revs for a
part; separate AVL and CE lists; slight differences in
docmgr
and
partmgr
menus; a slightly different PCN format; the
dra
directory is in /
baywest
vs.
/
bayeast
; the
scripts/utils
directory is in
/swi
vs.
/hw
; different processes are
automated; etc.
9
Who do I talk to, to update upper revisions?
ANS: Ask the owner/creator of the BOM.
10
Can multiple people PCN a BOM?
ANS: Yes, it’s technically possible, but there really should be one owner for a
BOM at any given point in time, and that owner should control the PCN
frequency.
11
Where are history logs stored?
ANS: On
/dra/rel/pcn_data/
component.nn
12
When to use PCN and PCN-lite?
ANS: No one uses PCN-lite any more. Forget about it.