USING AgilePLM IN MSI - Motorola...

GNL1147.00E - Using AgilePLM in MSI August 2013

Managing BOMs 1

Motorola Solutions Internal

USING AgilePLM IN MSI MANAGING BOMS

GNL1147.00E MOTOROLA, MOTO, MOTOROA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners. © 2013 Motorola Solutions, Inc. All rights reserved.


Managing BOMs 2


At the end of this module, you will be able to: At the end of this module, you will be able to:

Module Objectives

• Describe where the Bill of Material (BOM) processes fit in the overall process map.

• Create a BOM.

• Use for the Product Readiness Report.

• Discuss AgilePLM-PDM1 Validation Steps and Considerations.

• Describe Global and Composite BOMs.


Managing BOMs 3


Module Map

Introduction BOM Creation Reports AgilePLM-

PDM1 Validations

Global and Composite

BOMs Tips and

Tricks Summary


Managing BOMs 4


PLM PBT High Level Process


Managing BOMs 5


Introduction High Level Process Map Walkthrough


Managing BOMs 6


Introduction Items, BOMs, and Products

Universe of Items

Items

Items with BOMs

Products

Items in AgilePLM • Parts, assemblies, kits,

models, options, documents etc. are all items

• Items can be an individual item or may have a BOM

• Some items with BOM may be a Product/Model/Option Class/Option (Product level BOMs)


Managing BOMs 7


Introduction What’s a BOM

What is a BOM?

• Per Wikipedia-

– A bill of materials (sometimes bill of material or BOM) is a list of the raw materials, sub-assemblies, intermediate assemblies, sub-components, parts and the quantities of each needed to manufacture an end product.

• For MSI and AgilePLM purposes

– A BOM (Bill of Material) is any Parent Item that has relationships with one or more Child Items. The Child Item in a BOM can be a Parent Item to other Child Items


Managing BOMs 8


Introduction AgilePLM Icons

Icon Description

A part that has Child Items (BOM)

A part that has Child Items (BOM) (sellable)

A part that has Child Items (BOM) (non-sellable)

A part that does NOT have Child Items

A part that does NOT have Child Items (sellable)

A document

Manufacturing Change (MC) Notice

Engineering Change (EC) Notice

Folder (Contains attachments)

Manufacturer Part Number

Manufacturer Note: Icons update when you or someone else makes changes.


Managing BOMs 9


Introduction BOM Introduction Some terms Used to Describe BOMs of Different Types

• Sales Model BOM (Ordered Product Offering)

• Supermodel (can contain models and option classes)

• Model (can contains option class)

• Options Class (contains options)

• Option (Ordered as part of Model)


Managing BOMs 10


Introduction BOM Introduction Some terms Used to Describe BOMs of Different Types (cont.)

• SKU BOM (ES typical)

• JDM/ODM (ES typical)

• FRU

• Assembly

• Kit

• Phantom

• TANAPA

- AgilePLM Subclasses/Item Types “Product”, “Model”, and “Option Class” will typically have a BOM

- Models and Option Classes have additional BOM fields

- BOMs are not limited to these AgilePLM Subclasses/Item Types – Others will have BOMS too.


Managing BOMs 11


Introduction BOM Tab Extended Display Button

On a BOM, select the Extended Display button to:

• View detail information in a separate window

• On the Extended Display window:

– Click More to change content on main screen.

– Information sorted by order of pending changes.


Managing BOMs 12


Introduction Example: Typical Model BOM Assemble to Order (ATO)


Managing BOMs 13


Introduction Example: Typical Option Class BOM


Managing BOMs 14


Introduction Example: Typical BOM


Managing BOMs 15


Introduction BOM Lifecycle Concepts (Applies to all Items with a BOM)

LC Phase-> Concept

Preliminary Develop- ment

Prototype Pilot Production Pending Obsolete*

Obsolete**

Purpose Initial BOM creation

Release to ERP system

Indicates prototype build ready

Indicates pilot build ready

Indicates production build ready

Indicates that a part will stop being used for a variety of reasons.

Indicates that a part is no longer transactionable

Parts on BOM Can be at any LC phase (except Obsolete)

Must be Development or higher (except Obsolete)

Must be Development or higher (except Obsolete)

Must be Pilot or higher (except Obsolete)

Must be Production or higher (except Obsolete)

Must be Production or higher (except Obsolete)

Any child part can remain on an Obsolete BOM

Internal Manufacture

Not Applicable

Engineering Builds

Prototype Builds

Pilot Builds

Production Builds

Production Builds

Not Applicable

* Parts on a BOM that is PENDING OBS can be any Lifecycle except Obsolete ** An Obsolete child item can not be on a Non-Obsolete BOM. Parts or the Obsolete BOM can be any Lifecycle


Managing BOMs 16


Module Map


PDM1 Validations


BOMs Tips and

Tricks Summary


Managing BOMs 17


BOM Creation Different Ways to Create a BOM

Create BOMs,

Models, and Options

Develop and Mature Product /

Attributes

Prepare for

Release

Production Release and MOL End of Life

Bill of Materials

Preliminary Development and Prototype Pilot Production Pending Obsolete and Obsolete

BOM Lock-Down

Different ways to create a

BOM

Change Request to Create BOM in

Preliminary

Eng. Change Order to create BOM beyond

Preliminary

Clone an existing BOM using “Save As”

Create a new BOM directly in AgilePLM

BOM Created in AgilePLM

Can load bulk items from a template

Done directly in AgilePLM

Create an Electrical BOM through ECAD Interface


Managing BOMs 18


BOM Creation Ways to Create a BOM

• Creating a BOM Manually

• Cloning an Existing BOM

• Manually Creating a BOM Parent Then Child (Legacy)

• Importing a BOM

• ECAD interface

• (Joint Design Manfacturer) JDM Import (ES typical)


Managing BOMs 19


BOM Creation Manually Creating a BOM

From Main Menu:

1. Select Create New Items Parts

2. Select the kind of item needed from the Type dropdown list

3. Fill out all required fields and click Save. (* indicates required fields)

This creates the Parent Item for the BOM – It is not yet ready for RELEASE but the Child items can be added next if the part is going to Trilogy

4. Click on the BOM tab, and add items by:

– Typing

– Drag and Drop the item

5. Once the parts are added, type Quantity, Ref Designator (if applicable), and click Save.


Managing BOMs 20


BOM Creation Releasing or Changing a BOM on EC

From Main Menu:

1. Select Create New Changes Change Order.

2. Complete all fields and click Save. (* indicates required fields)

3. Change Order is created at Unassigned Step.

4. Fill out all fields and click Save.

5. On the Affected Items tab, select Add Button and enter the affected BOM.

6. Complete the required information.

7. Select Affected Item to display the BOM Structure at the bottom.


Managing BOMs 21


BOM Creation Releasing or Changing a BOM on EC (cont.)

8. Add, remove, or update as needed. Changes are displayed at the bottom and click Save.

9. When updates are completed, select Actions Audit Status.

10. Perform the necessary validations and select Next Status.

11. If necessary, add Approvers, Observers, Notifications. Ensure that they are added at Analysis or Approval status.

12. Click Finish.

Once all approvals were completed Change Order is Released.


Managing BOMs 22


BOM Creation Manually Creating a BOM Parent Release Then Add Children (Legacy)

1. Create the Parent Item

2. Create and submit an EC to put the Parent item into the Destination ERPs – Legacy Items Status at ASSIGNED

3. Add the Child Items (must also be in the Destination ERPs) to the Parent Item on a EC

4. Create and submit an EC to add the Child Items to the BOM in ERP

Note: If not in a LEGACY O11i – The child items can be added at any time prior to the EC that will send the BOM to Trilogy R12 ERP – Or can be added later on an additional EC


Managing BOMs 23


BOM Creation Cloning an Existing BOM

Note: Clone one level at a time, clones the original information and attachments.

1. Perform a General Search from an existing BOM Number.

2. Select Actions Save As.

3. In the 123 dropdown list, select the kind of item needed and the system assigns a New BOM number. (Or enter a specific BOM number, if known).

4. Fill out all the fields and click Save. (* indicates required fields)

BOM is cloned. (BOM Structure, Quantities, Reference Designators, Attachments, etc.) have been included.


Managing BOMs 24


BOM Creation Cloning an Existing BOM (cont.)

5. Update the info as needed.

For Legacy Parents

– REMOVE the parts from the BOM Prior to Initial EC

For Legacy Parents with LOTS of parts

– Export the Original BOM and Import it after the initial EC that Releases to ERP

For Legacy Parents with FEW parts

– Prior to Manually adding – put the BOM original into the Navigator


Managing BOMs 25


BOM Creation Importing BOM Child Items Introduction

• There are two methods to structure a BOM in AgilePLM: Manually ( Drag and Drop/Add)

- The manual method is recommended (simple and fast) for a small number of items, six to eight or less.

BOM Mass Load Template/Tool (Import a BOM)

• The BOM Mass Load Template/Tool is best suited for BOMs with lots of child items that have many fields or complex fields to update.

• For Trilogy

• Typically there are only two fields to update on a child of a software BOM - the child item and the quantity for the child item. For Legacy O11i there are more BOM Fields that need to be added


Managing BOMs 26


BOM Creation Importing BOM Child Items (cont.)

• In the object page, first verify if the object is still in the Preliminary stage.

• If the object is already in Production, you must create an EC if you want to add or remove child items to the BOM list. Follow the steps in Managing Change Module to create an EC to modify the BOM list.


Managing BOMs 27


BOM Creation Importing BOM Child Items Structuring a BOM using the BOM Mass Load Template Tool

1. Prepare a Microsoft® Excel spreadsheet with the following fields as columns:

- Parent Number

- Child Number

- Quantity

2. Populate the spreadsheet with the part numbers to be added to the BOM.

• Notes:

• You may add additional fields (columns) as required.

• The Import Wizard support files created with MS Excel 2000, 2002, and 2003 (“.xlsx” files are also supported).

• If multiple parts, enter in the same field with comma delimiter.


Managing BOMs 28


BOM Creation Importing BOM Child Items Structuring a BOM using the BOM Mass Load Template Tool (cont.)

3. Browse for the spreadsheet populated earlier in steps 1 and 2. Select the spreadsheet file and click Open. Click Next to proceed to the next step.

4. Accept the default values shown and click Next to proceed to the next step.

5. In the Item section, select the Bill of Material radio button. Click Next to proceed to the next step.

6. In the Data Mapping, Data Transformation, and Redline Options sections, select the following radio buttons.

- Define attribute mapping in the next step

- No transformations are necessary

- Updates do not require redlining


Managing BOMs 29


BOM Creation Importing BOM Child Items Structuring a BOM using the BOM Mass Load Template/Tool (cont.)

7. Click Next to proceed to the next step. 8. To map the entries:

• In the Import Fields box, click on the Parent Number field.

• In the Agile Fields box, click on Title Block > Number.

9. Continue mapping the rest of the Import Fields entries to the AgilePLM Fields entries. • Parent Number Title Block > Number

• Child Number BOM > Part Number

• Quantity BOM > Qty

10. Click Next to proceed to the next step.


Managing BOMs 30



11. Recommended step: Click Validate to ensure that there are no errors reported before you import.

12. Click Import to import the spreadsheet into AgilePLM.

13. Search for the item that you structured.


Managing BOMs 31



14. Click on the BOM tab. Verify that the child items are imported correctly in the BOM structure.


Managing BOMs 32


BOM Creation Prepare an ECAD BOM Package Process Flow


Managing BOMs 33


BOM Creation BOM Import MCAD/ECAD

• MCAD

– No connector/tool to extract the mechanical BOM from Pro-E/Windchill

– Must manually populate using the BOM Loader spreadsheet.

• ECAD

– EDA connector to generate an electrical BOM from schematics in Cadence.


Managing BOMs 34


BOM Creation Possible Errors

• Adding an Item at Preliminary LCP into a Released Assembly

• Adding an Obsolete Item into a BOM

• Mismatch Quantity vs Reference Designators

• Forgetting to add the ERP ORG for each child on a BOM that will go to a LEGACY ERP (AF, CX, OT, etc)

• Adding the same child Item twice for the SAME ERP ORG

• Using a CHILD ITEM that is not already IN the ERP ORG that the parent is in or going to be in


Managing BOMs 35


BOM Creation Considerations Related to BOM

• Prior to Lifecycle Production, the following criteria must be met:

– All children should be in Production

– The BOM will rollup for compliance and ECCN

– BOM Readiness Report can be run


Managing BOMs 36


BOM Creation Preparing an ECAD BOM Package Process Flow

For more information see the Using AgilePLM – Electrical Engineers module.


Managing BOMs 37


Module Map


PDM1 Validations


BOMs Tips and

Tricks Summary


Managing BOMs 38


Reports BOM Related Reports

• Product Readiness Report (NPI Programs)

• Standard Reports (Used at any time)

– Legacy BOM Comparison Report - Single Level Only --Shows the differences between two or more bills of material.

– BOM Explosion Report --Displays the bill of material for a specified assembly up to the desired number of levels

– Consolidated BOM Report --Consolidates the bill of material for a specified assembly into a single-level bill, computing the total quantity of each item.

– Where Used Report --Shows where the component or subassembly is used, up to any practical number of levels.


Managing BOMs 39


Reports Product Readiness Report Prior to Production Phase

Can be used to:

• Monitor the status of all items on the BOM for a product

• Track lifecycle phases, environmental compliance status, and the parts qualification for individual parts on a BOM.

• Provides Procurement additional information on costing – actual and estimates – for the parts.


Managing BOMs 40


Reports Product Readiness Report (cont.)

What’s requested at the time when the report is executed:

• Project Name

– Used for the title of the report.

• Release Date

– The M3 date for the program/project.

– Used to calculate when qualification for parts needs to be started to ensure that the M3 date for the program is met.

• Project Name and Release Date are not “fields or attributes” in AgilePLM used for searching.

• Project Name and Release Date only used for reporting purposes for the Production Readiness Report.


Managing BOMs 41


Reports Product Readiness Report Running a Product Readiness Report

1. Search for the BOM.

2. Select Actions > Product Readiness Report from dropdown list.

3. Provide information in the following fields: - Program Name - Production Date

4. Click Submit.

The report is scheduled. When run, the report is sent to your email account.


Managing BOMs 42


Reports Product Readiness Report Product Readiness Report Key Fields • Change Pending Indicator • BOM Items • Description of Part • Quantity • Motorola Part # • Revision # • Manufacturer • Manufacturer Part • Part Class • Commodity Code • Lifecycle Status • Design Lockdown Date • W18’s info • Compliance • ECCN • Part Approval Status • Std Cost Status


Managing BOMs 43


Reports Running Standard Reports

1. Select Reports from the Navigator Pane

2. Click Execute.

3. Choose a layout.

4. Add items.

5. Accept the default item types.

6. Add additional parameters.


Managing BOMs 44


Module Map


PDM1 Validations


BOMs Tips and

Tricks Summary


Managing BOMs 45


AgilePLM-PDM1 Validations Item Attributes for Legacy ERPs

AgilePLM Section: Part Details • Destination ERP

– Legacy ERPs – Trilogy R12 – AgilePLM – SAP

AgilePLM Section: PDM1/Legacy Radio ERP Specific • Legacy 11i Item Type

– Location Code and Item Type • Legacy Item Status

– Item Location Code and Status • Legacy Item U of M

– Item Location Code and UoM


Managing BOMs 46


AgilePLM-PDM1 Validations Item Attributes for Legacy ERPs

Item Destination ERP Legacy : 11i Item Type / Item Status / UoM

H60PCN6TZ6AN Legacy ERPs; Trilogy R12 IT: PTO Model / IT: Full Release / IT: EA OM: Base Model Option / OM: Full Release / OM: EA

CLSANT0890AC Legacy ERPs; Trilogy R12 IT: PTO Option Class / IT: Full Release / IT: EA

QA00026AA Legacy ERPs; Trilogy R12 IT: PTO Option / IT: Full Release / IT: EA IE: MCIL-Acc-Buy / IE: Full Release / IE: EA OM: Option / OM: Full Release / OM: EA

QA01037AA Legacy ERPs; Trilogy R12 OM: Option / OM: Full Release / OM: EA

GMBN4235B Legacy ERPs; Trilogy R12 IT: PTO KIT / IT: Full Release / IT: EA

5485930Y01 Legacy ERPs AF: EXPENCE / AF: Full Release / AF: EA OT: BUY Item / OT: Full Release / OT: EA


Managing BOMs 47


AgilePLM-PDM1 Validations Viewing Legacy BOMs

Use the View and Personalize fields to create a BOM view


Managing BOMs 48


AgilePLM-PDM1 Validations Things to Remember - Item Create and Update Required Fields

Ensure the following Item fields are populated while creating AgilePLM Items for Legacy ERPs:

– 1. ClassCode – 2. Mfg site DC – 3. APC Code – 4. Responsible Location – 5. Legacy Item Status – For

each Mfg site DC – 6. Legacy UofM – For each Mfg

site DC – 7. Legacy ERP Item Type - For

each Mfg site DC

Most frequently used ClassCodes are:

C Systems

D Sales Model

F TANAPA-Not scheduled in Front-Back End

H Kit

J Subassembly

L Piece Part-Finished

P Drop Shipped Items

X Option

Z Non Material Item (Prod Aid, 12M, etc)


Managing BOMs 49


AgilePLM-PDM1 Validations Legacy BOMs Child Item considerations

• Before adding a child to a BOM, the child must exist in all the destination organizations that the Parent BOM is in.

• Item work must take place before the BOM work.

• If the item is currently not in a destination,

1. Create a EC or MC to make that item exist in the “Assigned” Status in the new Destination Organization.

2. Create a EC or MC to update the Child items status to match the AgilePLM Lifecycle.

3. Create a EC or MC to Add (now usable) Child to Parent Item BOM.


Managing BOMs 50


AgilePLM-PDM1 Validations Legacy ERP

• The effectively date for PDM1 needs to be at least one day later than today’s date. Otherwise, the BOM Update will fail.

• PDM1 does not allow BOM Update in Assigned status. Item status must be at least pilot in AgilePLM, else EC will fail.

• User can not release New Item and its BOM create thru same EC. • Validation Error in AgilePLM – Affected Item is not present in PDM1

– User can not release New item and BOM thru same EC. User needs to release Item first then can add BOM below it.

• When user creates/structures BOM outside of an EC and then adds to an EC OR BOM structuring without any red lining in EC - it will fail into PDM1.

• Suggested Approach: For new BOM creations, add parent part to an EC and then add new components to it using red-lining feature.


Managing BOMs 51


AgilePLM-PDM1 Validations Legacy ERP (cont.)

• For valid values for these attributes for Legacy ERPs, see the Managing BOMS – Valid Attribute Values for Legacy ERPs Job Aid.

• For new item being created, the legacy Item Status for all Manufacturing DC must be “Assigned”.


Managing BOMs 52


• Validate AgilePLM EC. Check Validation messages and status (MOI Validation Status) on AgilePLM EC.

• Additionally, an email will be sent to EC originator with the details of validation in case of failed validations.

• In case of successful Validation. The MOI status will change to “Validated”

• Statuses should be monitor before releasing the EC— • MOI Status - Validated • Transfer status - Validated • JDM/ODM validation - Validated

• Release the EC and wait for scheduled job to run which will automatically push EC information to PDM1.

• The EC, item and BOM information, as applicable will be transferred to PDM1 within an hour and then to ERP by MOI in another half an hour.

AgilePLM-PDM1 Validations Legacy ERP (cont.)


Managing BOMs 53


The monitoring tool is used to review what occurs when an EC is pushed to the MOI interface. It also is used to determine which BMX is attached to each EC.

To check if EC, item and BOM information correctly reached ERP (or to implement BOM in ERP), click on the following link of the monitoring tool.

• http://pdmtest.am.mot.com:9002/AgilePDM1MOIMonitorCAT

• In the ECO Number field, enter the EC number.

AgilePLM-PDM1 Monitoring Legacy ERP

http://pdmtest.am.mot.com:9002/AgilePDM1MOIMonitorCAT


Managing BOMs 54


AgilePLM-PDM1 Monitoring (cont.)

• The first table presents status of BOM affected thru that EC. It shows Notices (if a BOM update) or BMX (if a BOM Create) for all affected items across different Manufacturing sites.

• The Second table presents status of items created and updated thru that EC. • This information can be used to provide BMX number or New Rev in ERP. • Note: There are multiple ECNs for a single EC in AgilePLM, one per site and

affected item.


Managing BOMs 55


AgilePLM-PDM1 Validations and Monitoring

• In case of any failure during creation of ECN, Item or BOM in PDM1, a notification is send to Support team (Build team in this case). The status in the monitoring tool against item will be Failed.

• In case If you do not see an item released in two hours or ECNs status “Failed”, contact IT team for investigation.


Managing BOMs 56


Module Map


PDM1 Validations


BOMs Tips and

Tricks Summary


Managing BOMs 57


Global and Composite BOMs Introduction

Global BOM definition • BOMs with global content that can be used in different locations (all or specific)

without modifications on:

– Parent/Child combination

– BOM attributes (Qty, Optional, ME, Min/Max Qty, RefDes)

Composite BOM definition (temporary situation for legacy ERPs) • BOMs that exist in multiple ERPs (NA, EIA, MIL and OMAR) including Trilogy

R12 are composite BOMs.

• BOM content can be different but not necessary.

– If BOM content is equal across all Orgs, than BOM is marked with Global BOM = Yes but every Org is listed separately.


Managing BOMs 58


Global and Composite BOMs Introduction (cont.)

Rules for legacy BOM setup and maintenance (temporary)

• Global BOMs stay Global

• Any new BOMs are created as Global

• Globalize existing non-global BOMs

– Restructure BOM

– Cancel

– Setup Local specific BOM


Managing BOMs 59


Global and Composite BOMs Legacy ERPs

Prerequisite for legacy BOM setup and maintenance (temporary)

For legacy ERP All items must first be available in target ERP.


Managing BOMs 60


Global and Composite BOMs Important BOM information

– Destination ERP (multi-value field) Pulled from Item Master – Main information to identify System (R12 Trilogy, Legacy ERP, SAP, Agile)

– Mfg Sites/DC (multi-value field) Pulled from Item Master – Detailed information to Identify target ERP for Legacy system

– ERP Org (single-value field) BOM attribute to define target system for each BOM line


Managing BOMs 61


Global and Composite BOMs Important BOM information (cont.)

Destination ERP (multi-value field)

Manufacturer sites/DC (multi-value field)

ERP Organization (single-value field)


Managing BOMs 62


Global and Composite BOMs Important BOM information (cont.)

Scenario 1: Composite BOM with Global BOM content • BOM marked as Global BOM = Yes

• BOM available in 2 locations (Composite) e.g., R12 Trilogy and Tau DC

Scenario 2: Composite BOM with non Global BOM content

• BOM marked as Global BOM = No

• BOM available in 2 locations (Composite) e.g., 12 Trilogy and Tau DC


Managing BOMs 63


Global and Composite BOMs Scenario 1

Scenario 1: Composite BOM with Global BOM content • 2 lines (same items)

– 1x Tau DC

– 1x R12 Trilogy


Managing BOMs 64


Global and Composite BOMs Scenario 2

Scenario 2: Composite BOM with non Global BOM content • BOM content between locations is different

• 9x Tau DC

• 12x R12 Trilogy


Managing BOMs 65


Global and Composite BOMs Scenario 2 (cont.)

ERP Org information is the trigger to push the BOM lines to a defined ERP and Org.

Red Box Push to Tau DC in EA 11i

Green Box Push to R12 Trilogy


Managing BOMs 66


Global and Composite BOMs Change Management (EC) Process

• Based on EC the interface push Note to R12 and legacy ERP

– R12 Trilogy follow normal process

– Legacy ERP EC content will be loaded to Staging Table and transferred to PDM1. PDM automatically create ECs and PCM completes by defined process.


Managing BOMs 67


Module Map


PDM1 Validations


BOMs Tips and

Tricks Summary


Managing BOMs 68


Tips and Tricks

• Where Used Tab

• Full Height BOM/Where Used

• BOM Parent Searches

• Export a BOM

• Find Number field


Managing BOMs 69


Tips and Tricks Where Used Tab

Click the Where Used tab to:

• Show where the part is currently used:

– Does not show pending to be used

• Shows one level at a time


Managing BOMs 70


Tips and Tricks Full Height BOM/Where Used

On the BOM Tab

• Go To Tab

– Fast way to get to a part you know is in the BOM

– Easy to find a REF DES

• Extended Display Tab

– Get an additional Window

– Until you close it you can see the structure

• Navigator

– Drag and Drop-able

– Selectable

• Where Used Tab

– Where Used

– Pending Changes Where Used

• More Button

– Exporting Quick and Easy


Managing BOMs 71


Tips and Tricks BOM Parent Searches

• There are currently 52 Subclass items that are created in AgilePLM.

• A few of them will almost always be BOM Parent Items

• Now you can search for an Item Type for these as well

• PCBA

• Product

• Model

• Option Class


Managing BOMs 72


Tips and Tricks Exporting a BOM

1. Perform a general Search from an existing BOM Number.

2. On the BOM Tab select Actions Export.

3. Select the format to download the file and select Export.

The BOM is exported to an Excel file.


Managing BOMs 73


Tips and Tricks Find Number Field

• The Find Number is a BOM Attribute in AgilePLM.

• If the Find Number needs to change, it would change on an EC in AgilePLM.

• Used when creating or redlining a BOM, the Find Number is one of the fields to default to zero in the child item on a BOM.


Managing BOMs 74


Module Map

Introduction BOM Creation Reports Tips and Tricks

AgilePLM-PDM1

Validations


BOMs Summary


Managing BOMs 75


Summary

• Describe where the BOM processes fit in the overall process map

• A BOM can be created:

- New

- An existing BOM can be cloned

- BOM and children can be imported

• The Product Readiness Report is used to:

- Monitor the status of all items on the BOM for a product.

- Track lifecycle phases, environmental compliance status, and part qualification for individual parts on a BOM.

- Provide Procurement additional information on costing (actual and estimates) for parts.


Managing BOMs 76


Summary (cont.)

• AgilePLM-PDM1 Validation Considerations include:

– Certain item fields must be populated when creating AgilePLM Item for Legacy ERPs.

– Before adding a child to a BOM, the child must exist in all the destination organizations that the Parent BOM is in.

– Item work must take place before the BOM work.

– Effectivity date for PDM1 must be at least one day later than today’s date.

– PDM1 does not allow BOM Update in Assigned status. Item status must be at least Pilot in AgilePLM.

• Cannot release New Item and its BOM create thru the same EC.


Managing BOMs 77


Summary (cont.)

• Global BOM

– With global content that can be used in different locations (all or specific) without modifications on Parent/Child combinations or BOM attributes

• Composite BOMs

– Exist in multiple ERPs (NA, EIA, MIL and OMAR) including Trilogy R12. BOM content can be different but not necessary. If BOM content is equal across all Orgs, then BOM is marked with Global BOM = Yes, but every Org is listed separately.


Managing BOMs 78


Backup


Managing BOMs 79


Definitions of the CBOM Similar to a BOM, which is the Bill of Materials for an Assembly, a CBOM is a Compositional Bill of Materials for a Part. • The CBOM concept is implemented in MSI prints for Government

Solutions. • Created in AgilePLM by Electrical/Mechanical Engineers and

Designers at MSI • Can be thought of as a bill of raw materials for a part • Consist of materials used across all of the MSI product lines such

as Metals, Non Metals, Composite Materials, Manufacturing Process, and generic Part Notes

• CBOM items will have individual part numbers and will have an associated PLM lifecycle as any other part in the AgilePLM system


Managing BOMs 80


JDM/ODM Benefits of BOM Import

• Large percent of BOM content is imported • More information to better address customers issues

– Component EOL – 2nd source activities – LTB can be more accurate

Note: Discussion objects are not applicable to this process.


Managing BOMs 81


JDM/ODM BOM Import Process

• The BOM is exported, based on predefined data template • In AgilePLM:

– Login in – Create an EC – Attach the BOM file – Notify the PCM

• PCM retrieves BOM file and adds additional default attributes • PCM executes Macro utility to match Manufacturers name • PCM imports in four step process to bring in:

– Parts information – Manufacturer Names and P/N – AML – BOM structure


Managing BOMs 82


JDM/ODM BOM Import – What’s Imported • Import Items

• Import AMLs

• Import Structured BOM


Managing BOMs 83


JDM/ODM BOMS

• ODM BOMS are included in the AgilePLM system

• JDM/ODM Component (SubClass/Type)

• Benefits

– Complete materials declaration

– PCN notices

– Where Used Searches


Managing BOMs 84


Importing a JDM/ODM BOM

1. Log in to the AgilePLM system.

2. Click the Home button, then click the Notifications tab.

A notification is sent regarding the EC raised by the JDM/ODM manufacturer.

3. After you receive the EC notification, click the EC Number link to review the EC.

4. Click the Attachments tab in the EC to download the JDM/ODM BOM file.

5. Import the product content according to the information in the attached files.


Managing BOMs 85


Importing a JDM/ODM BOM (cont.)

5. When importing product content, import data in the following order:

1. Items

2. AMLs

3. Structured BOM


Managing BOMs 86


JDM/ODM Importing Items

1. Click the Tools and Settings button ( ) and select Import.

2. Browse for the JDM/ODM BOM file downloaded earlier. Select the BOM file and click Open and then click Next.

Note: The Import Wizard support files created with MS Excel 2000, 2002, and 2003 (“.xlsx” files are not supported).

3. Accept the default values shown and click Next.

4. In the Item section, select the Item only radio button and click Next.

5. In the Data Mapping section, select Use a saved mapping file. Select the given item mapping file for AgilePLM to automatically map the spreadsheet entries.


Managing BOMs 87


JDM/ODM Importing Items (cont.)

Note: See the Site Coordinator for assistance with the mapping file.

6. In the Data Transformation section, select No transformations are necessary.

7. In the Redline Options section, select Use the following Change for redlining and search for the EC raised by the JDM/ODM manufacturer.

8. Click Next.

9. Optional step: Click Validate to ensure that there are no errors reported before you import.

If necessary, resolve any errors with the JDM/ODM manufacturer.



Managing BOMs 88


Importing AMLs


2. Browse for the JDM/ODM BOM file downloaded earlier. Select the BOM file, click Open then click Next.

Note: The Import Wizard support files created with MS Excel 2000, 2002, and 2003 (“.xlsx” files are also supported).


4. In the Item section, select the Approved Manufacturer List radio button and click Next.

5. In the Data Mapping section, select Use a saved mapping file. Select the given AML mapping file for AgilePLM to automatically map the spreadsheet entries.


Managing BOMs 89


Importing AMLs (cont.)




8. Click Next.


If necessary, resolve any errors with the JDM/ODM.



Managing BOMs 90


Importing a Structured BOM


2. Browse for the JDM/ODM BOM file downloaded earlier. Select the BOM file, click Open then click Next.

Note: The Import Wizard support files created with MS Excel 2000, 2002, and 2003 (“.xlsx” files are also supported).


4. In the Item section, select the Bill of Material radio button then click Next.

5. In the Data Mapping section, select Use a saved mapping file. Select the given BOM mapping file for AgilePLM to automatically map the spreadsheet entries.


Managing BOMs 91


Importing a Structured BOM (cont.)




8. Click Next.


If necessary, resolve any errors, with the JDM/ODM manufacturer.


USING AgilePLM IN MSI - Motorola...

Documents

Transcript of USING AgilePLM IN MSI - Motorola...