PCN Process User Guide Part No.
4401 Great America Parkway Santa Clara, CA 95054 8 Federal Street Billerica, MA 01821 Copyright © 1998 Bay Networks, Inc. All rights reserved. This is an unpublished document meant for internal use only. The information in this document is proprietary to Bay Networks, Inc., and subject to change without notice. The software described in this document is, unless otherwise trademarked in the text, the property of Bay Networks and may only be used as such.
Contents About This Guide Before You Begin Reading ...............................................................................................xiii Conventions .....................................................................................................................xiv Acronyms .........................................................................................................................xiv Reading This Guide with Adobe Acrobat .......................................................
Managing a Project’s Majordomo Email List ...................................................................2-4 Setting up the Initial Email List .................................................................................2-4 Using Majordomo Commands ..................................................................................2-4 Chapter 3 Using and Getting Part Numbers Finding Parts ..................................................................................................................
Chapter 5 Creating and Updating BOMs Overview .........................................................................................................................5-2 BOM Generating Programs ......................................................................................5-2 Configuration Files ...................................................................................................5-2 Input and Output directories ...........................................................................
Part List ..................................................................................................................5-26 Part and Assembly Cost File ..................................................................................5-27 Part Cost File .........................................................................................................5-27 Profile File ..............................................................................................................
Appendix C FAQ Appendix D Error Messages partmgr Error Messages ................................................................................................ D-1 bn_bomprocess Messages ............................................................................................ D-2 Errors ...................................................................................................................... D-2 Warnings ........................................................................................
Appendix F References Glossary Index viii
Figures Figure 1-1. Figure 5-1. SAP, BOM, PCN Process Overview .......................................................1-11 Excel Spreadsheet Template for xcelbom .............................................
x
Tables • EDA East Engineering Support ...............................................................xvii • EDA West Engineering Support ...............................................................xvii Table 2-1. Commonly Used Majordomo Commands ................................................2-5 Table 3-1. Summary of Initial Parts to Take Out for a New Project ...........................3-7 Table 4-1. Object Types for Programmable Parts .....................................................
xii
About This Guide This guide is for people who generate, read, or use PCNs and BOMs. PCNs track changes to a Bay Networks PCB’s electrical, mechanical, or programmed components prior to the first production build. They eliminate the paper ECO process at prototype and pilot stages. An HTML version of this guide is available at http://bayweb.baynetworks.com/engserv/procedures/pcnguide.
Conventions Conventions angle brackets (< >) Within output from text-based UNIX tools, these indicate that you supply the text to enter based on the description inside the brackets. For example: if command syntax is ping , you enter ping 192.32.10.12. bold text Indicates path names, text that you need to enter, command names, and buttons in menu paths. Example: Enter wfsm & Example: Use the dinfo command. brackets ([ ]) Indicate optional elements.
Reading This Guide with Adobe Acrobat CSM Commodity Supplier Management EDA Engineering Data Administration ICT In-Circuit Testing IS Information Systems MRP Materials Resource Planning—a generic term NPI New Product Integration PCB Printed Circuit Board PCN Prototype Change Notice PPM Product Purchasing Management Pro/E Pro/Engineer CAD Software PDF Portable Document Format SAP Systems, Applications, Products in Data Processing X The X Window System Reading This Guide with Adobe A
Internal Support To use the bookmarks (Ctrl+7) along the left margin: click the page icons to go to that page, or the triangles to open or close nested sections in the book’s outline. To follow a cross reference or a link to a web page: move your cursor to the reference or link so the cursor changes to a pointing hand, then click.
Internal Support Getting Help for BOM and SAP Processing For help, see the following tables. Also see http://bayweb.baynetworks.com/ engserv/info/contact.htm for possible updates to this information.
Internal Support xviii: About This Guide
Chapter 1 Getting Started (An Overview) This chapter gives a quick overview of the PCN/BOM process so you can find what you need to do next and so you can understand the context.
Executive Overview Executive Overview PCNs (Prototype Change Notices) track changes to a Bay Networks PCB assembly’s electrical, mechanical, or programmed components prior to the first production build. The PCNs provide data on which parts make up the assembly; how much they cost and who sells them; and what lead time is involved in buying them. The PCN process coordinates, controls, and tracks the additions, deletions, or changes of these parts.
Starting Work on a Project Starting Work on a Project Whether you’ve been with your project since its kick-off meeting, have joined in mid-project, or are new to Bay Networks engineering projects altogether, you need to set up your environment, get on the email list, and perhaps start the project. To start work on a project: 1. Set up your UNIX environment: a. Get a UNIX engineering account and telnet ability to caps in the engeast domain, or to supremes in the engwest domain.
Using Recognized Parts Using Recognized Parts If you’re adding parts to a schematic, they come from Viewlogic libraries. Each part has an associated symbol and a Bay Networks part number. To find parts: 1. See your application for help on specifying parts within it. (There is a small note about finding parts In ViewLogic on page 3-1.) 2. See Part Numbers on page E-1 for a description of the Bay Networks common part number, legacy numbers, etc. The common part number is something like 300123-A. 3.
Getting New Parts Getting New Parts To pull new part numbers: 1. Consider if you need a new number. See When to Pull a New Number on page E-6. 2. Collect any information you may need if the part is new to Bay Networks: vendor information, part number, vendor’s URL, availability, etc. may be determined in consultation with a component engineer. 3. Use the Part Manager to get the new part number: run /bayeast/dra/utils/ partmgr or /baywest/dra/utils/bnw_partmgr. See Getting New Part Numbers on page 3-4.
Using EDA Data Servers Using EDA Data Servers The EDA data servers provide a structured, trackable, reliable, and safe mechanism for tracking project changes. You are responsible for putting the appropriate files into the following directories: • /dra/2brel/programs/PartNumber.nn/— device files, diagnostic programs. • /dra/2brel/mech/PartNumber.nn/—AutoCAD files or Pro/E files such as .prt, .drw, and .asm. • /dra/2brel/docs/PartNumber.
Creating and Updating BOMs Creating and Updating BOMs A project’s first BOM needs to be created only once. After that, you’re basically just updating the BOM from rev to rev, so that its number changes from minor revision 00, e.g., 300123-A.00 to minor revision 01, e.g., 300123-A.01, and so on. Creating an Initial BOM To create a project’s first BOM: 1. Determine the high-level components and the reporting structure, i.e., which component reports to which.
Creating and Updating BOMs d. 4. Run bn_bomprocess in /hw/tools/scripts or /swi/tools/scripts/. If you’re using mechbom (see Creating an Initial Mechanical BOM on page 5-8), it creates a config file for you, but first you have to: a. Create a mechanical include file called assembly.lst. b. Provide supporting mechanical data files. c. Run /baydir/dra/utils/mechbom.
Uploading a BOM Uploading a BOM You, as an engineer, can only request that a BOM be uploaded. The EDA analyst actually uploads it by entering data from it into the SAP database. You both run the bom_upload utility, though with different options. To upload a BOM: 1. 2. Be sure that you have: a. Prior to bn_bomprocess, placed all supporting files (schematics, mechanicals, binaries, documentation) in the /baydir/dra/2brel directories. See Using EDA Data Servers on page 1-6. b.
Reading PCNs Reading PCNs The PCN notice that you receive in email contains the PCN number, the originator, the product and board information, revision information, and a summary of: • Functional changes • Informational changes • Detailed changes The example PCN listed below has been greatly abstracted and edited.
Understanding the PCN/BOM Process Understanding the PCN/BOM Process The PCN/BOM process is outlined in Figure 1-1. This process involves data files, EDA server data, two interactive scripts, several engineers and analysts, and three processing activity “threads.” ❶ SAP Schematic (optional) Periodic SAP Extract SAP BOM Upload Option 2 Schematic BOM Extract (optional) ❷ BOM & PCN Gen Tool Changes Depops Includes .data_files. SAP _proto.
Finding BOMs on the Web 3. b. Individual engineers who request a BOM upload based on BOM processing and data storage files, running bom_upload to request an upload (Option 1) c.
Chapter 2 Starting a Project This chapter tells you how to: • Set up your UNIX account and environment • Create a project • Manage a project’s majordomo email list Procedures explained in this chapter: To create a new project: on page 2-3 To add yourself to a majordomo list: on page 2-4 Obtaining Appropriate Accounts The BOM and PCN process is essentially a set of UNIX-based scripts, utilities, data files, and directories.
Setting up Your Environment • Access to the system that supports BOM processing for your site, for example: • caps for BNE and BNIRE (East Coast and Ireland) • supremes for BNW (West Coast) (See Appendix A for more detail.
Creating a New Project • sym—for symbols needed for your schematics • wir—for wire files Note: For some groups, the following directory structure is used: /hw/slf/project/01, 02, etc., containing directories for defines, schematics, PALs, models, stubs, and monitors. Within schematics, there may be additional hierarchy depending on the structural blocking of the project.
Managing a Project’s Majordomo Email List This generates the initial BOM, which should be structured for your project according to the guidelines given in Structuring a BOM on page 5-4. 6. Run bom_upload when you’re ready to issue your first PCN for the project. See Chapter 6. Managing a Project’s Majordomo Email List Majordomo is a mailing list manager that lets you subscribe, unsubscribe, show which lists you are on, etc.
Managing a Project’s Majordomo Email List b. If the reply includes your email address as in (b), you can use the unsubscribe command with just the name of the list, e.g., unsubscribe pcn_asn. Otherwise, you must include your user ID, as in unsubscribe pcn_asn bhenders. Table 2-1. Commonly Used Majordomo Commands Command Description subscribe pcn_list [address] Subscribe yourself (or address if specified) to the list. unsubscribe pcn_list [address] Unsubscribe yourself (or address if specified).
Managing a Project’s Majordomo Email List 2-6: Starting a Project
Chapter 3 Using and Getting Part Numbers When you place components on a schematic using Viewlogic, they come from libraries such as wf_flashmem, wf_dcdc, wf_bus_logic_misc, and wf_diode. If you create BOMs and generate PCNs, you may also specify parts in ASCII files, and/or allow parts lists to be generated from schematics or other files. These components always have Bay Networks part numbers and usually have associated symbols.
Finding Parts In UNIX Directories The Part Manager, /bayeast/dra/utils/partmgr or /baywest/dra/utils/ bnw_partmgr, is the primary tool to do part lookup, part number requesting, part cancellation, part printing, etc., via its menu options. It has slightly different versions on the East and West coasts. Using Part Manager to Find Part Numbers EDA encourages you to use the docmgr interface in /bayeast/dra/utils/docmgr or /baywest/dra/utils/bnw_docmgr to run partmgr and other EDA tools.
Finding Parts • get_pm_data_by_pnum—Lets you enter a part number and get the part’s description, class code, rev, and release status. • get_pm_mfg_data—Part number search of AVL database, followed by a printout of the last time the database was dumped in UNIX-readable format from SAP: get_pm_mfg_data part_number Note: If you expected a part to be in the SAP list by this point, and it isn’t, see Appendix B for a description of how often the database is updated.
Using partmgr to Update or Get a New Part Number • Part Lookup by Part Number. Enter the part number. These buttons confirm the existence of the part (or parts), and supply the class code, description, release status, and rev. If the part exists, you can use it in the BOM upload process.
Using partmgr to Update or Get a New Part Number 4. Specify whether the part is off the shelf (i.e., purchased), custom made, or documentation only. Documentation includes assembly drawings, schematic drawings, specifications, revision registers, board modification history, and rework instructions. Basically, documentation includes part numbers that do not represent a physical material that can be purchased, stocked, or assembled into a unit.
Using partmgr to Update or Get a New Part Number • You need not provide a URL or printed, hardcopy documentation, unless these are needed by the component engineer to identify and locate the part. Note: For BNE users requesting new off-the-shelf parts, you will be asked if you need a symbol. This is the symbol that will be used in Viewlogic. 8.
Using partmgr to Update or Get a New Part Number The following list identifies parts to pull, the class codes, and how to name the parts. Table 3-1.
Using partmgr to Update or Get a New Part Number Updating Part Numbers All common part numbers contain what is known as an “embedded rev” number, which is the major rev portion, e.g., the “-A” in the part number, for example: 300123-A To update or rev a part number: 1. Run /baydir/dra/utils/docmgr or bnw_docmgr and select the option: 1). Run PARTMGR (Part Management) 2. Choose the following option when the Part Manager appears: 3). Add/update an embedded rev to an existing part number 3.
Using partmgr to Update or Get a New Part Number Note: The Aspect system in use from March 9, 1998, standardizes the part descriptions for all off-the-shelf parts, so you will not have to enter a description. 7. Approve the new part when asked: OK to issue this part? [y/n] The Part Manager logs the transaction and emails you and relevant EDA team members.
Part Number Availability Printing Part Requests You can print a part request provided that the Part Manager has been used to request the part. To print or display information about a part request: 1. Run /baydir/dra/utils/docmgr or bnw_docmgr and select the option: 1). Run PARTMGR (Part Management) 2. Choose the following option when the Part Manager appears: 5). Print a Part Request 3. Enter the part number to be displayed. 4. Specify whether to print the information or display it to the screen.
Chapter 4 Putting Data on EDA Servers This chapter tells you how to put data on the EDA servers to support your PCNs.
Introduction The nn number should match the minor_rev level that will result when you run bom_upload, the EDA analyst completes the BOM upload, and the files are moved to the /baydir/dra/rel release area (see below). For example, if the part had been 300123-A.04, the directory would be 300123-A.05. The PCN “Release” Area EDA scripts allow you to use the /baydir/dra/2brel area to submit data that will eventually be placed into the /baydir/dra/rel area.
Data Storage for Programmed Parts Data Storage for Programmed Parts You should provide programmed part data files when they change and the change is to be processed for a PCN. Until these files are in place, a PCN will not reflect any checksum changes. Note: Programmed devices report to the PCB assembly and no longer to a “program kit.” Your object code type must be listed in the following table. If it is not, please contact EDA support.
Data Storage for Programmed Parts Table 4-1. Object Types for Programmable Parts Class Code Object Code Extension Extractable Checksum 119 .obj No 119 .pof Yes Altera 119 .rom Yes Binary 119 .s No Motorola S Record 119 .s2 No 119 .s3 No 119 .ss No 119 .svf No 119 .sym File Type Serial vector file * The .i file is used to program flash SIMMs (designated by the 930 class code) in a mass production environment. You should also submit a .
Data Storage for Programmed Parts The example below shows the contents of the device 305299-A as it would appear in the /baydir/dra/2brel/programs directory: caps% ls -l 305299-A.00 total 8 -rwxr-xr-x 1 jryan 3482 Jul 28 1998 305299.abl -rwxr-xr-x 1 jryan 1686 Jul 28 1998 305299.jed 3. Issue a PCN to update the BOM. (See Chapter 6.) Scripts run by cron every 12 hours (at BNE) or by an EDA analyst twice a day and on request (at BNW) examine the programs directories.
Mechanical Data Mechanical Data Using Pro/E for Mechanical Revisions To make a revision change to SAP for a mechanical component: 1. Place the data to support the change in the /baydir/dra/2brel/mech directory: a. Use Pro/Engineer’s DBMS->Backup menu selection and direct the output to /baydir/dra/2brel/mech/component.nn. The backup command stores all of the required Pro/E files and will ensure that they are sent to our suppliers in a complete and retrievable form.
Mechanical Data 5. • B-size HPGL2 component.hp2 • B-size PostScript component.ps • DXF component.dxf if a .drw file exists • A wireframe IGES component.igs if a .prt file exists. If a PostScript file is created successfully: a. It is translated into a PDF format file and copied to the Electronic Print Room web page, http://bayweb.baynetworks.com/engserv/pdf/ mainpdf.html. b. The resulting output files are moved into the /baydir/dra/rel/mech/ ppp000/component.nn directory, e.g.
Mechanical Data Bay Networks makes an incoming ftp site, wfltlink (“Wellfleet link”) available to its contract layout houses, which ftp Allegro layout files to it, in the form of .tar.Z files. You can use /dra/utils/get_pcb to retrieve the PCB tar file from the layout house and put it in an outgoing directory where a fab house can get to it via ftp. To send layout files: 1. Run the get_pcb script.
Mechanical Data For a full description of the procedure, see the references to document SPECIFICATION PCB DELIVERABLES, Rev 02 (117291-A) and the Hardware web page for back annotating a board in Appendix F. The schematic.tel file that you send to the PCB layout designer contains an “F number” followed by a number representing each component instance on the schematic (e.g., F0234). This is what Allegro uses to keep track of components.
Doc Data 4. Issue a PCN to update the BOM with the new drawing revision. (See Chapter 6.) This allows the EDA process to move the file(s) from the /baydir/dra/2brel/ mech area to the /baydir/dra/rel/mech area, and to place them in the EDA Electronic Print Room. Doc Data You should supply the following types of documents for a PCN: • Rework instructions • Board modification histories • Specifications • Other instructions, procedures, etc. To supply documentation for a PCN: 1.
Chapter 5 Creating and Updating BOMs A BOM (Bill of Materials) is essentially a list of parts, some of which may be BOMs themselves. • The BOM that contains parts is their parent. They are said to report to that BOM. • A BOM contained as a part number within another BOM is called a nested, or indented BOM. The BOM process’s main purposes are to: • Generate a BOM (and associated files) • Compare a BOM with a previous one When you create a BOM, you create data files that are required to create a PCN.
Overview Overview BOM Generating Programs The three basic Engineering programs that create BOMs are: • bn_bomprocess—Used for schematics produced by Viewlogic and run from a UNIX command line, or from within Viewlogic’s Workview panel, to create Material Group 920 BOMs. (See BOM Structures on page E-9.) • mechbom—Used to create BOMs not associated with the 920 material group; runs bn_bomprocess internally.
Overview • Running bn_bomprocess • Eventually running bom_upload (see Chapter 6), which causes the files related to bom_upload to be moved into a post-release area under /baydir/ dra/rel and owned by root The bn_bomprocess script generates a number of files in one or more of the following directories: • Your working directory • The directory you specify in the configuration file for bn_bomprocess (see The Configuration File on page 5-16) • /baydir/dra/common/assembly if you run bn_bomprocess indir
Creating BOMs Creating BOMs The whole point of creating a BOM is to generate a PCN telling other people about it and to inform EDA to upload the BOM data into the SAP database. You may create many BOMs, using bn_bomprocess, mechbom, or xcelbom, but they’re only sets of potential input files that don’t have any effect until you run bom_upload to generate the PCN so EDA can upload the BOM data into the SAP database (see Chapter 6).
Creating BOMs Example The project was called STRANGELOVE. Its PCB assembly part number was 115769-A, belonging to class code 920. All of the other parts, as shown in the following table, reported to this part. Notice that most of them were from documentation-only classes (sub, mec, sch, and mod). Table 5-2.
Creating BOMs Therefore, you will end up with a unique directory for each BOM in your project. The directory for the main BOM, which is usually a 920-class BOM, is typically given the project name. The other directories are given the names of their parent parts, e.g., 115779-A. Creating a BOM with bn_bomprocess All Engineering BOMs are created via bn_bomprocess, as even mechbom and xcelbom set up for this script and call it after their specialized processing.
Creating BOMs 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 /baydir/dra/2brel directories to support your changes (see Chapter 4), for example into: /baydir/dra/2brel/docs/PartNumber.nn/ /baydir/dra/2brel/mech/PartNumber.nn/ /baydir/dra/2brel/mech/pwahdw/PartNumber.lst /baydir/dra/2brel/programs/PartNumber.nn/ 5.
Creating BOMs Creating an Initial Mechanical BOM The only way to create an initial mechanical BOM is to create a mechanical include file, PartNumber.lst, and run mechbom. In the following procedure, you may have to copy data files into a subdirectory in /baydir/dra/utils/mech. You will then run mechbom. To create a mechanical BOM: 1. Create a directory for your part or project: cd /baydir/dra/common mkdir assembly For example, your assembly directory might be 300123-A, or 980-12345-A.
Creating BOMs To download a SAP list for a mechanical BOM: 1. Log in to SAP. 2. Specify the transaction codes /NSRET JOBS. 3. Specify the following report: MATERIALS MANAGEMENT- ENGINEERING-PCN SAPLIS BOM 4. 5. Provide the following information in the resulting dialog box: • Assembly number plant 0100 or 200 • Usage 2, single-level BOM • Suppress headers for download • Menu path SYSTEM-LIST-SAVE-FILE • Save option: Unconverted • Filename: assembly.saplis Place the resulting assembly.
Creating BOMs 5. If a component on your BOM requires a rev change, create directory /baydir/dra/2brel/mech/component.nn, e.g., 300123-A.01, and copy data files into that directory to support the change. 6. Run /baydir/dra/utils/mechbom from your /baydir/dra/common/assembly directory. 7. Enter the assembly (part) number and the target manufacturing plant. 8. Review the asembly_proto.diff file as displayed by mechbom to make sure it correctly lists the differences. 9.
Creating BOMs • Do not change any of the fields containing vertical bars (“pipes”). • Do not add any headers to the columns. • Do not add any information other than the Part Number, Qty, and Ref Designator fields. • Make sure that reference designators are separated by commas. • Make sure there are no blank rows. 3. Save the file as a text (tab-delimited) file named PartNumber.txt. (See /baydir/dra/2brel/mech/boms/xcelbom_info/sample_xcel_BOM.txt for an example.) 4.
The Input Files The Input Files The various input files are specified by the configuration file. In this section, the configuration file parameter is listed below the file name (or file extension). See The Configuration File on page 5-16 for all the config file’s parameters. BOM Files bn_bomprocess.ini VL_SCHEM_PARTLISTER_INI_FILE bne_bomprocess.ini The Viewlogic Part Lister’s init file. This is required if a BOM is to be generated from a schematic.
The Input Files 3. The parts listed in the change file(s) are substituted by the parts as directed in the change file(s). Include Files INCLUDE_FILE /Full_PathName/Project.lst How many include files you have, where they are, and what you name them are your option, subject to any other guidelines. On the East Coast, the file is typically named Project.lst or PCB_Assy_Number.lst. It contain lists of mechanical parts that do not appear in a schematic.
The Input Files Depop Files DEPOP_FILE Project_depoped.lst A depop file contains a list of parts and quantities to remove from a BOM. This is useful if the schematic that you use to generate the BOM contains parts that you do not want on the BOM. You can not depopulate a part below 0. On the West Coast, you can automatically create “depop per page” files and schematic attributes.
The Input Files The SAP List File OLD_BOM Part_Number.saplis The current BOM for the project you are working on appears in your engineering directories as a text file named project.saplis, which is automatically used as the old BOM to which your new changes will be compared. Note: This needs to be specified even for the first time you run bom_upload.
The Configuration File The Configuration File The config file determines where bn_bomprocess finds the current BOM; the include, change, and depop files; what types of information to generate, etc. Many of the command-line switches previously used have been replaced (for most users) by settings that you make in the configuration file.
The Configuration File Specifying Configuration File Parameters The config file can be confusing, as it contains combinations of supported, unsupported, and obsolete options. In general, keep in mind that the main point is either to: • Create a BOM using include files managed by a mechanical engineer and kept in subdirectories under /baydir/dra/2brel/mech, /baydir/dra/2brel/ programs, and /baydir/dra/2brel/docs.
The Configuration File Table 5-3. Config File Parameters Statement (Optional Ones Shaded) Explanation ADD_CHECKSUM_INFO YES Add checksum info to new BOM. ADD_REFERENCE_INFO_FOR_ DOWNLOADS YES Add ref des info to new BOM. BUILD_ASSM_COST_FILE NO Not implemented. BUILD_LEAD_TIME_FILE YES Generate a new lead-time file. BUILD_MANMAN_FILE NO MANMAN is no longer supported. BUILD_NEW_PARTSLIST YES Generates a _parts.lst file (and a _depoped.lst file for any removed parts). Build a new _proto.
The Configuration File Table 5-3. Config File Parameters Statement (Optional Ones Shaded) Explanation INCLUDE_FILE filename Use filename for a file in your working directory, or specify the full pathname, or a pathname relative to the working directory. Include files add mechanical parts to a BOM. You may use multiple statements. NEW_BOM PartNumber.sap Ignored if extracting from schematics; can be used to compare two SAP .lis files.
The Output Files The Output Files The BOM process generates several output files and renumbers the previous set(s) of output files, saving only as many revisions as are specified in the configuration file. For example, the newest to oldest .sap files might be .sap, .sap.1, .sap.2, and so on; when a new .sap file is generated, it will be .sap, the previous will now be .sap.1, the old .sap.1 will become .sap.2, and the old .sap.2 will disappear if the SAVE_NUMBER value is 2.
The Output Files AVL Update File The Part_avl_update file lists the parts (number, description, plant code) that need to have AVLs assigned in other plants. For example: # # New AVL Update file # # File generate by: # BN BOMprocess [X0.
The Output Files Changes File The Part_changes.rev file contains extensive data on all the changes, including design identification, revs, target plant, part numbers, description, and revisions for parts, etc. For example: # New Revision file File generated by: # BN BOMprocess [X0.
The Output Files # Part Number New Rev Server Rev MRP Rev Last Bom Rev #------------------++-------++----------++-------++-----------300267-A 10 09 300267-A 10 09 ############### BOM input file: ############### /sapdata/interfaces/XXX/viewlogic/in/300267-A.10 -rw-rw-rw- 1 pweaver 3646 May 6 15:31 /tmp_mnt/bne/home/pweaver/projects/ddb/rev10/boms/300267-A.sap -rw-rw-rw- 1 pweaver 7380 May 6 15:31 /tmp_mnt/bne/home/pweaver/projects/ddb/rev10/boms/300267-A_proto.
The Output Files Lead Time File BUILD_LEAD_TIME_FILE YES Part_leadtime.lst is used to report the lead time for parts for the BOM, this file contains, for every part: number, description, quantity, and lead time, i.e.
The Output Files Using schematic input file 118026-A_bne_bp.lst Using Include file : 118026-A.lst Using Old BOM : /bayeast/dra/rel/pcn_data/118000/118026-A.08/118026-A_08.saplis Targeting BNE manufacturing ------------------------------------------Parsing Partslist Data file: 118026-A_bne_bp.lst Using include file: 118026-A.lst Parsing ECO Date file: /bayeast/dra/utils/eco_track/.ecodates Parsing ECO Log file: /bayeast/dra/utils/eco_track/ecologfile Searching Servers for updated data ...
The Output Files New BOM File NEW_BOM The BOM process by default generates a new BOM file, part.saplis, to list the parts in this BOM and to be used as a previous BOM file the next time the process is run. For example: see The SAP List File on page 5-15. Part List BUILD_NEW_PARTSLIST YES This Part_parts.lst file lists all the parts and extensive information about them. (Default is No.
The Output Files Part and Assembly Cost File BUILD_ASSM_COST_FILE YES Generate Part_cost_assm.lst, a new part and assembly cost file, sorted by highest cost. (Default is No.) Part Cost File BUILD_PART_COST_FILE YES Part_cost.lst is used to report the total cost of the BOM. It lists, for each part number, its description, quantity, and unit cost and full cost for the project. The cost values come from the Dilbert purchasing database. If there is a cost associated with a part, it is accurate.
The Output Files Profile File Part.profile is automatically generated, with information about the project, new revision number, working directory, user ID of the person who ran bn_bomprocess, etc. For example: # # Profile file # # File generate by: # BN BOMprocess [X0.
The Output Files # Number of Unique Parts Deleted: 0 # Number of Unique Parts Added: 5 # Number of Part Rev changes: 0 # # Informational changes # Total Number of parts: 71 # Number of Released parts: 38 # Number of Unreleased parts: 33 # Number of Obsolete parts: 0 # Number of Parts Marked for Deletion: 0 # Number of Parts with Single AVL sources: 16 # Number of Parts with NO AVL in target plant: 0 # Number of Parts with NO AVL sources: 6 # Number of Parts with ECO’s Pending: 0 # ==========================
The Output Files ========================================================================== (NO AVL source in target plant - reference plant identified) part # description Plant w/AVL -------------------------========================================================================== (NO AVL source) part # description ---------------118366-A REV REG IIG3 MAIN LOGIC BD 118367-A DWG ASSY IIG3 MAIN LOGIC BD New SAP Upload File BUILD_SAP_FILE YES Project.
The Output Files Schematic Output EXTRACT_FROM_SCHEMATIC YES The Part_bne_bp.lst file is produced by Viewlogic’s Part Lister running against the schematic in your working directory. (Default is No.) For example: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 117994 | RP8S.PRT 111-200 | HC14D.PRT 109291 | CC0805C.PRT | | 103171 | | 550-003 | CC0805C.PRT 109677 | CC0805C.PRT | | | | | | | | | | | 117999 | MHROSC.
Summary Overview of BOM Files Summary Overview of BOM Files The following table lists the major BOM-related files and briefly describes their usage. Table 5-4. File Table of BOM Processing Files Usage bn_bomprocess.log Output file from bn_bomprocess, including when run via mechbom or xcelbom. project_avl_update Output file. A list of parts (number, description, plant code) that need to have AVLs assigned in other plants project_bne_bp.lst Output.
Summary Overview of BOM Files Table 5-4. Table of BOM Processing Files File Usage project.profile Output file. Generated information about the project: design part number, description, new revision number, working area, and the user ID of the person who ran bn_bomprocess to generate the file. project_proto.diff Output file.
Summary Overview of BOM Files 5-34: Creating and Updating BOMs
Chapter 6 Generating PCNs and Uploading BOMs This chapter tells you how to upload the BOM that you created in previous chapters. Uploading a BOM means that: • You run the bom_upload program that packages various files that you have already created using bn_bomprocess. • A PCN number is issued for the BOM. • An EDA analyst reviews your files and enters the new information into the SAP database.
Understanding What a PCN Is Design Purpose of PCNs PCNs are like ECOs, except they apply to prototype assemblies instead of those in quantity production for a released product. This implies that PCNs are designed to: • Control the components, subassemblies, mechanical and schematic drawings, etc., of products that will eventually be released into full production. • Publicize any changes to these components.
Understanding What a PCN Is Component Engineering When you issue a PCN, the information goes to many groups, but CE is very much in the middle of issues between vendors and those groups. For example, NPI and Manufacturing might read your PCN and then contact CE regarding component availability. Or, someone in CE reading your PCN might update the Approved Vendor List (AVL), involve a commodity manager, or get back to you, depending on the vendor source(s) you have specified.
Understanding What a PCN Is ❑ Did bn_bomprocess complete with the message “Please review bn_bomprocess.log for parts IGNORED”? You probably ran bn_bomprocess after creating new parts but before they were included in the downloaded database from SAP. In this case, rerun bn_bomprocess later. ❑ Did you read all the error messages displayed by bn_bomprocess? You don’t want any error messages, and it won’t help to ignore them. Check the bn_bomprocess.
Understanding What a PCN Is # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # New Design: PCB ASSY IIG3 MTR BRD New Design Part Number: 118026-A Rev: 09 Old Design: PCB ASSY IIG3 MTR BRD Old Design Part Number: 118026-A Rev: 08 Summary Section: File generate by: BN BOMprocess [X0.
Running bom_upload ❑ Have you looked at the .profile file to check that you ran bn_bomprocess from the correct working directory? . . .
Running bom_upload Getting the PCN Number To obtain a PCN number and request a BOM upload: 1. Change to your working directory containing the .profile file that was created when you ran bn_bomprocess. 2. Run /baydir/dra/utils/docmgr or bnw_docmgr and select the option: 6). Run BOM Upload 3. Choose the following option when the Upload Requester appears: 1). Request a BOM Upload 4. Select your project by entering its name and confirming it, or by listing all the projects and entering its number.
Running bom_upload 7. Enter your description of the change, one line at a time, and press Return on a line by itself when you’re finished. Caution: bom_upload is a C-shell script, and it currently quits for a variety of input characters. It may leave some files in temp directories. Be informative. Remember, you’re telling many people about the change. Some people may be looking at higher-level parts in the BOM structure, so use this chance to tell them that the change affects them, too. Be reasonable.
Appendix A Computer Infrastructure and Tools This appendix: • Briefly describes the use of computer systems and directory structures to support the PCN process. • Presents an alphabetical list of tools, utilities, and commands relevant to the PCN/EDA process, with a brief description for each, some with pointers to additional information. Computer Infrastructure The PCN process is supported by: • EDA data servers • General-purpose EDA login systems • Tool servers • Web server Table A-1.
Computer Infrastructure Table A-1. EDA Servers System.Domain Purpose swifs1.engwest West tools server web1.engwest West engineering web server Table A-2.
Tools Tools Note that /hw/tools and /swi/tools are complementary mount points on the East and West coast, respectively. Also, the footnotes “*” and “**” mark tools that are available from within docmgr and partmgr, respectively, as well as individually. Table A-3. BOM-Related Tools and Utilities FILE NAME Location DESCRIPTION bn_bomprocess /hw/ & /swi/ tools/scripts Generates a BOM. You may also run this utility from within build_lst, mechbom, pcbbom, xcelbom: bn_bomprocess options.
Tools Table A-3. BOM-Related Tools and Utilities FILE NAME Location DESCRIPTION get_files /bayeast /dra/utils Retrieves released mechanical files for suppliers. get_files_2brel /bayeast /dra/utils Retrieves 2brel mechanical files for suppliers. get_files_all /bayeast /dra/utils Retrieves released mechanical Pro/E files for suppliers. getinfo* /bayeast & /baywest /dra/utils Gets part information from files in current release and /2brel directories.
Tools Table A-3. BOM-Related Tools and Utilities FILE NAME Location DESCRIPTION partmgr* /bayeast /dra/utils Part lookup, part number requesting, part cancellation, and part printing. protomgr /bayeast /dra/utils Builds and prints a PCN; summarizes all PCNs for a board; finds a specific part on a PCN.
Tools A-6: Computer Infrastructure and Tools
Appendix B Behind the Scenes This appendix explains more about the PCN process: • What happens when you begin a new project • How the programmable parts directory gets processed • What types of processing happen, and when, behind the scenes Beginning a New Project When you begin a new project by contacting EDA, the EDA engineering support coordinator takes the following steps: 1. Sends email to enghelp to request a new majordomo list from IS.
Processing of the Programmable Parts Directory Processing of the Programmable Parts Directory BNE cron scripts (and BNW manual scripts) periodically scan /baydir/dra/2brel/ programs for new subdirectories, e.g., 302690-A.00. If they find one, the scripts send you email, and they try to transfer the program parts to the same subdirectory in /baydir/dra/rel/programs/PPP000, where PPP is the first three digits of the part number. If that new subdirectory already exists in the /rel area, e.g.
Timing and cron Scripts Timing and cron Scripts The PCN/EDA process depends on a number of cron scripts, which are scripts run by the cron process according to certain schedules that determine when processing takes place and when files are updated. Other scripts are run manually on a regular basis, or are run in a non-UNIX environment by a scheduler program. Note: The scripts in this section are for EDA’s use in moving information into /baydir/dra/rel.
Note: The create_arch_mv script does not move files if there is already a part.minor_rev directory in existence, or if the filename for the .ps file contains a lower-case letter, as the “a” in 300123-a.ps. Scheduled Processes Processes running in the environment that support the bn_bomprocess database files include one that is run every even-numbered hour (East Coast time) to extract BOM information relevant to PCNs and ECOs from the SAP database.
Appendix C FAQ This appendix lists commonly asked questions, with answers. 1 I have to get the BOM uploaded today and have taken out a new part number for an item on the BOM. The system will not let me upload the BOM. Why? How can this be expedited? ANS: When you take out a new part, or increment the embedded revision (e.g., the “A” in 123456-A.01), the change has to be manually processed to be put on SAP.
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.
13 If a part you’ve used on your design is marked for deletion, what does that mean, and what does that do? ANS: You may read a PCN and find a part marked REL,UNR, or OBS. The “OBS” means that this part is marked in SAP as obsolete. You have to remove the part from your design. 14 How will I know when the PCN is completed? ANS: You receive notification in email, and files are moved into /dra/rel/ pcn_data.
21 My PCN reports that an off-the-shelf part that was previously unreleased by the ECO/PCN process is now released. How did that happen? Your PCN didn’t cause this change. Component Engineering released the off-the-shelf part. 22 Can I change part item numbers in a BOM? ANS: Yes, you can use an include file to control the item number for the 900-level types of mechanical parts not abstracted from the schematics.
1. In SAP, select Materials-Management->Engineering->BOM Component detail report. 2. Enter BOM details. 3. Select “Sort by Item” and “Single Line Download.” b. Download the Excel macro at http://edmse.corpeast.baynetworks.com/ bom_import.html and run this to import the file (from Step A) into Excel. Edit the part number that has changed. c.
C-6: FAQ
Appendix D Error Messages This appendix lists most of the error messages from the partmgr and bom_upload scripts. It also lists many of the severe error and warning messages from bn_bomprocess, but keep in mind that this script is over 150 pages long and contains many self-explanatory messages. This appendix displays the messages and explanations in the following format: Text of Error Message. Explanation of error. The messages are arranged alphabetically.
bn_bomprocess Messages Class Code not found on this class code list. You entered a non-existent class code. Contact Engineering Services immediately! Part number log file may be corrupt. The part log is corrupt. Option 4 is not implemented in east. The wfps script that runs when you select Option 1 and then Option 4 in the partmgr is not implemented in Bay East. Option 6 is not implemented in west.
bn_bomprocess Messages . Refdes issues listed above have %s issues. Because of this, Processing has stopped. Essentially, you have multiply-defined reference designators, or some other mismatch. See the files that bn_bomprocess lists for log file, schematic source, include, and depop files. CFG file required file of type . File is of type . You said the new BOM had a specific type, e.g.
bn_bomprocess Messages NEW_BOM_TYPE keyword not specified in CFG file This is a required parameter, specified as NEW_BOM_TYPE VL_SCHEM_EXTRACT. If you’re not an expert, make sure it’s spelled VL_SCHEM_EXTRACT. See The Configuration File on page 5-16. OLD_BOM_TYPE keyword not specified in CFG file You need to specify OLD_BOM_TYPE SAP_REPORT in your configuration file. Partslist tool did not complete successfully The Viewlogic Part Lister reports a number of non-zero completion status values.
bom_upload Error Messages Directory
specified but does not exist [however exists] There is a mismatch in part directories. No unreleased server directory exists for part number for rev . Expected to find server data and did not. Part number ’s current rev is too high. The current rev has reached 99. You need to bump the major rev of the part, e.g., from 300123-A to 300123-B.bom_upload Error Messages Can't overwrite in the rel area! If you enter a part and rev to process, and the combination is already in the /dra/rel area, bom_upload exits. Check that @get_bom has been run. $CNTL.lis does not exist. If @get_bom has been run, contact Engineering Services! The bom_upload checks for the existence of the .lis file generated from your BOM and exits if the file does not exist. Directory /dra/rel/pcn_data/xxx000/. already exists.
bom_upload Error Messages Part appears to be a top level assembly. The bom_upload script reports that the first entry of the .sap file is a top-level number, and it gives you the choice of continuing. Part to upload this BOM against not found in profile file. Please contact Mike Shannon. If bom_upload cannot determine from the .profile file which BOM to upload, it cannot continue. Contact Mike Shannon or EDA. Please enter a rev greater than .
bom_upload Error Messages Unable to find a .diff file with the name . Your _proto.diff file must have the same name as your .profile file. There must be a _proto.diff file with the same base name as the .profile file in the working directory. Unable to find a project containing the string . The bom_upload script checks that the input string you have entered for the project name is in the list of bom_upload projects. Unable to find a revs file with the name .
Appendix E Parts and Part Numbers This appendix provides summary information for the following topics: • Part numbers: the common part number format; legacy part numbers; tabbed part numbers • When to update the minor rev of a part number for different types of parts: programmed parts, PCB assemblies, custom parts, purchased components • BOM structures • Class codes Part Numbers Common Part Number Format Bay Networks now uses a new common part number format in the form: Number-Letter or 123456-A A
Part Numbers • The letter portion of the part number (A to Z, but not I, O, Q, or X) is used for all major versions, including standard parts, custom parts, and purchased parts. A new part number needs to be pulled to update a Z-level major version. • An internally visible, two-digit, numeric code (00 - 99) is used for all minor revisions; this code is contained in an attribute field in SAP and is not embedded in the part number. A new part number needs to be pulled to update a 99-level minor revision.
Part Numbers The class code is continued today, but it is not embedded in the part number. When you create a part using partmgr, you re prompted to provide one (see Table Class Codes for Off-the-Shelf and Custom-Made Parts on page E-13). • 900-193, where there was no embedded major rev. • 119-00423-A, where an extra two digits were added to accommodate numbers greater than 1,000 (and 900-12345, when there was no embedded major rev). • 119-00223-A-1.2.4, where they added versioning for software.
Part Numbers Searching for and Revving Legacy Part Numbers You can still get the next embedded rev of an old-style part, as long as the part is in SAP. When you search for a part number, you may notice these variations, as shown in the following table. Table E-2.
When to Change Part Numbers The tabbed parts have the format 123456-A-00, 123456-A-01, 123456-A-02, . . . 123456-A-99 The tabbed part number is the two-digit number from 00 to 99. The core number is the part number without the tab. Table E-3.
When to Change Part Numbers Revisions are distinguished by whether they are major or minor. See Part Numbers on page E-1 for how these are expressed in the various numbering schemes in use at Bay Networks. When to Pull a New Number You need a new part number: • For any custom component whenever there is a plan to diverge in a product’s application, regardless of whether your pre-released product reports into single or multiple objects or products.
When to Update the Minor Rev of a Part Number PCB Assemblies A major revision is required for the following types of changes: • Changes that are not backward compatible, that is, where rework cannot bring old units up to the latest revision: function, form, or fit (e.g., different physical package or dimensions). • Artwork spins that result in renumbering the reference designators. Note: Old assembly should not be planned for future production or redesign—in these cases, you need a new part number.
When to Update the Minor Rev of a Part Number The information in this section is extracted from PROC CHNGING PART REVS, Rev B (115067-A). (See Appendix F for this document’s location.) Programmed Parts For single-product reporting, a minor revision change is required if the description changes, or the raw device changes for functional reasons but stays in the same physical package, or for program or speed changes.
BOM Structures • When a new artwork spin is released and previous revs can be reworked to be functionally equivalent to the new spin. Custom Parts (Cables, Sheet Metal, Fabs, Labels, etc.) A minor rev is needed if there are description changes or there are changes to drawings or documentation that do not affect the purchased part. Custom Parts (Manuals and Software) A minor rev is needed if the part reports to an order number and is forward- and backward-compatible.
BOM Structures Table E-7 and Table E-8 on the following pages provide the full list of class codes for documentation, made-to-order parts, and off-the-shelf parts. Table E-4. Reporting Relationships for BOMs Level Reports To Description Order Number N/A Listed in the price list and used by the customer to order products from Bay Networks. 980 N/A Required for all products that have a build-to-stock process.
BOM Structures Table E-4. Reporting Relationships for BOMs Level Reports To Description 785 920, 960, or 980 A bezel kit that is a buy level. Typically used to group a number of mechanical parts together as an assembly that could be procured by internal manufacturing or external manufacturers. 650 775, 795, 968, 980, or Order Number Document software kits that are typically buy items. 610 900, 920, 960, 980, or Order Number A label kit.
Class Codes (Material Groups) The following table shows the BOM structure for a typical build-to-order product Table E-6.
Class Codes (Material Groups) Table E-7.
Class Codes (Material Groups) Table E-8.
Class Codes (Material Groups) Table E-8.
Class Codes (Material Groups) Table E-8.
Class Codes (Material Groups) Table E-8.
Class Codes (Material Groups) Table E-8.
Class Codes (Material Groups) Table E-8.
Class Codes (Material Groups) Table E-8. Class Codes for Off-the-Shelf and Custom-Made Parts Code Description of Code Template for Describing the Part 880 SHIPPING GOODS (CARTONS FOAM ETC) KIT PKG SET NAME 881 CUSTOM SHIPPING GOODS (INSERT ETC.) 888 MANUFACTURING PLANNING BOM 893 TECH PUBS MANUAL INSTALL INSTRUC.
Class Codes (Material Groups) Table E-8. Class Codes for Off-the-Shelf and Custom-Made Parts Code Description of Code 992 OEM LITERATURE 993 TECH PUB PUB ASSY. 994 SYNOPTICS LIT.
Class Codes (Material Groups) E-22: Parts and Part Numbers
Appendix F References This appendix provides a list of pathnames and/or URLs for important online documents concerning part numbers, revision criteria, etc. “Back-Annotating.” http://taichi/designing_a_board/laying_out_a_board/ supplying_layout_data/back_annotating.html. A brief description of the process of back annotating a board and verifying the annotation. “DATA PACKAGE REQUIREMENTS: Allegro Designs.” http://bayweb/ess/ edso/pcb/dfm/DESIGN/allegrodesign.html.
“Revision Schemes.” http://bayweb.baynetworks.com/engserv/info/rev.htm. This document describes the revision schemes for East and West Coasts, including legacy and current issues, released; unreleased parts, etc. “SPECIFICATION PCB DELIVERABLES,” Rev 02 (117291-A). D. Hardy. /dra/rel/ docs/ or http://bayweb.baynetworks.com/engserv/pdf/102000/102877.pdf. This documents the procedure for placing schematics on the server, including ftp access.
Glossary .include The project.include file, containing part numbers for parts not on the schematic, containing the part numbers, descriptions, and class codes .profile The project.profile file, containing general information on a project, is generated by bn_bomprocess and contains the design part number and description, the new revision number, the working directory from which the bn_bomprocess was run, e.g., /tmp_mnt/hw/fx/hardware/mantaray/ 14/boms/, and the name of the engineer who ran bn_bomprocess.
_cost.lst The project_cost.lst file, saved in the project working directory, contains, for all parts in the project, the part number, description, quantity, unit cost per part, and full cost for the project. _depoped.lst The project_depoped.lst file, also saved in the project working directory, defines parts to be removed (depopulated) from the BOM, by part number, revision, description, quantity, and reference designator (where applicable). _leadtime.lst The project_leadtime.
BOM Bill of Materials—a list of all parts that make up an assembly, including part numbers, descriptions, class codes, and quantities. BOM number BOM#—the BOM number for the assembly. class code A three-digit part code that places a part within a part category. docmgr An interactive program that provides access to all engineering services programs. EDA Engineering Data Administration—the people who manage the Bay Networks part numbers, PCNs, and ECOs. EDA Analyst Uploads BOM data into SAP.
order number A customer-level number that can be used to order a Bay Networks product. parent assembly The assembly to which a part or sub-assembly reports, as determined by how the BOM is structured. For example, the parent assembly number of a PCB is the board number. part number A number in SAP, or in the ECO/PCN/BOM system, that specifies a particular part, component, or assembly.
top-level assembly The highest assembly level for the product, typically including the PCB assembly, product documentation, the shipping carton, and any other items required to ship the product. UNR The status (unreleased) of a part that is in the PCN system but not yet released by an ECO into production. uploader The EDA person who actually uploads information from the BOM into SAP. Viewlogic A schematic design tool.
GL-6
Index Symbols .abl, 4-4 .ps, 4-7, 6-5, B-3, B-4 .afm, 4-3 .rom, 4-4, 4-5 .apt, 4-8 .s, 4-4 .bin, 4-3, 4-4 .s2, 4-4 .brd, 4-8 .s3, 4-4 .cfg, 5-6, 5-11, 5-16 .sap, 5-30, GL-1 .def, 4-3 .saplis, 5-9, 5-12, 5-15, 5-26, 5-28 .doc, 4-10 .ss, 4-4 .drw, 4-7, 6-5 .svf, 4-4 .dxf, 4-7 .sym, 4-4 .fus, 4-3, B-2 .tar.Z, 4-8 .hex, 4-3 .xls, 5-10 .history, B-2 .xmt, B-2 .hp, 4-6 /bayeast/dra, 5-3 .hp2, 4-6, 4-7 /baywest/dra, 5-3 .i, 4-3 /dra/2brel, ii, 5-7, GL-1 .
/dra/rel/docs/PPP000/component, 6-6 acronyms, xiv /dra/rel/mech, 4-10 Actel, 4-3, 4-5 /dra/rel/mech/PPP000/component.nn, 6-6 ADD_CHECKSUM_INFO, 5-18 /dra/rel/pcn_data/PPP000/Part_number, 6-6 add_pcn_proj, B-1 /dra/rel/pcn_data/PPP000/PartNumber.nn, 5-7 ADD_REFERENCE_INFO_FOR_ DOWNLOADS, 5-18 /dra/rel/programs, 6-6, B-2 /dra/trans/PCN, 6-6 /dra/utils, ii, GL-1 /dra/utils/mech_bn_bom.
overview, 5-2 schematic output, 5-31 using to create a BOM, 5-6 structure for build-to-order, E-12 structure for build-to-stock, E-11 structuring, 5-4, E-9 table of files, 5-32 updating, 1-8 updating with mechbom, 5-9 uploading, 6-1 to 6-8 uploading to SAP, B-1 bn_bomprocess.ini, 5-12 bn_bomprocess.
functional, E-7 minor or major, C-3 cron script, 4-2, A-2, B-3 csh, 2-2, C-4 changes file, 5-17 CSM, xv checksum, 4-3, 4-4, B-2 change count, 6-4 checksum.fus, B-2 computed, 4-5 for all devices, 6-4 info to new BOM, 5-18 current BOM, 5-15 class codes, 1-5, 3-5, 5-4, E-10, E-12, GL-3 documentation, E-12 D classcode.
print room, ii support coordinator, xvii, B-3, GL-3 tools engineer, xvii, GL-3 Electronic Print Room, see EDA electronic print room emacs, 2-2 ftp, B-4 functional changes, E-7 part, GL-3 fuse, B-2 G email and editing tools, 2-2 daily reminder, 1-9 list, 1-3, 2-4 subscribing, 2-4 to enghelp, B-1 unsubscribing, 2-4 Gerber file, GL-3 embedded rev, 3-8, E-6, GL-3 get_files, A-4 environment project, 1-3 setting up, 2-2 UNIX, 1-3 get_files_2brel, A-4 EPROMs, 4-5 Excel spreadsheet, 5-10 extension (file na
log locations, C-2 librarian, GL-3 HPGL, 4-6 load sharing, 2-2 http //bayweb.baynetworks.com/engserv/procedures/ pcnguide, xiii //bayweb.baynetworks.com/engserv/procedures/ pcnguide/pcn_guide.
changes, C-3 number, 1-6 updated by bom_upload, E-7 when to update, E-7 parent assembly, GL-4 bumping, C-1 number, C-1 NEW_BOM_TYPE, 5-17, 5-19 part and assembly cost file, 5-27 cancellation, 3-2 changing released, C-2 cost file, 5-27 custom, E-7, E-9 description, 3-5 documentation files, 5-3 finding, 3-1 getting new, 1-5 information on Web, 3-3 list file, 5-26 manufacturing data, A-4 parent, 5-1 Part Manager, 3-2, 3-4 Part Manager errors, D-1 to D-2 printing, 3-2, 3-10 reporting to BOM, 5-1 using recogn
part.saplis and previous BOM, 5-12 PC accounts, 2-2 PCB, xv, GL-4 assembly, E-7, GL-4 design service, GL-4 vendor, GL-4 when to rev assemblies, E-8 when to rev, E-8 project environment, 1-3 multiple, E-5 parts for new, 3-7 single, E-5 starting, 1-3 PCN, xv, GL-4 completion notification, C-3 defined, 6-1 documentation, 4-10 frequency, 6-3 PCN-lite, C-2 rework instructions, 4-10 specifications, 4-10 project.
reporting structure, 1-7, 5-1, E-9 searching for part numbers, 3-2, E-4 resistors, E-7, E-9 setup environment, 2-2 X Window System, 2-2 rev custom part, E-9 embedded, 3-8, E-6 major, 3-8 mechanical, 4-6 minor, 1-6, 4-2 part number, E-6 PCB assembly, E-8 programmable parts, E-8 purchased components, E-9 revision register, GL-4 rework instructions, 1-6 PCN, 4-10 rlogin, 2-1 ROH, GL-4 sheet metal, E-7, E-9 SIMMs, 4-4 single projects, E-5 software, E-7, E-9 specifications for PCN, 4-10 Speedview Windows, 4
updating BOM, 1-8 minor rev, E-7 part numbers, 3-8 upper revisions, C-2 uploader, B-1, GL-5 uploading a BOM, 6-1 to 6-8, C-1 X X Window System setup, 2-2 xcel_BOM_template.xls, 5-10 xcelbom, 1-7, 5-3, A-5 creating BOM, 5-10 overview, 5-2 xcelconfig.
