using agileplm in msi - motorola...

GNL1147.00E - Using AgilePLM in MSI August 2013

Managing Products 1

Motorola Solutions Internal

USING AgilePLM IN MSI MANAGING PRODUCTS

GNL1147.00E MOTOROLA, MOTO, MOTOROLA 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 Products 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

• Discuss how AgilePLM supports MGates and PLM.

• Describe the lifecycle of products.

• Discuss how to develop models and options.

• Discuss how to use the Product Readiness Report with products.


Managing Products 3


Module Map

How AgilePLM Supports

MGates/PLM Models and

Options Product

Readiness Report

Costing for Products

Sales Waivers Product Cancellation Summary


Managing Products 4


How AgilePLM Supports MGates/PLM Items, BOMs, 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 Bill of Material

• Some items with Bills of Material may be a Product


Managing Products 5


How AgilePLM Supports MGates/PLM PBT High Level Processes

Create Items Develop & Mature Item / Attributes

Prepare for

Release

Production Release & MOL End of Life

Item Lifecycle Processes

Preliminary Development & Prototype Pilot Production Pending Obsolete & Obsolete

Design Lock-Down

Create BOMs,

Models & Options

Develop & Mature Product / Attributes

Prepare for

Release


Products & Bill of Materials


Product Lock-Down

Engineering Processes

ECAD Interface

MCAD Interface

Software Interface

Partner & Supplier Collaboration Component

Design & Fab Collaboration

Component Qualification

Contract Manufactures

Product Outsourced or Joint Design

Environmental Compliance

Product Change Notices

AgilePLM


Managing Products 6


Create BOMs,

Models & Options

Develop & Mature Product / Attributes

Prepare for

Release


Products & Bill of Materials


Product Lock-Down

How AgilePLM Supports MGates/PLM AgilePLM Lifecycle Phase: Alignment with PLM and MGates

Business Case

Portfolio Planning

Project Definition

Launch & Closeout

Phase II Plan

Phase III Development

Phase IV Product Acceptance

Phase V Launch & Customer

Sat

Phase VI Sustain

Phase VII End of Life

Execute Plan Execute Continuous Improvement

EOS Plan

PRD Complete

Detailed Design

Complete

General Avail-ability

Proc’t Volume Prod’n Auth.

Vendor Selection

Initiate Beta Test

Last Book

Rev A EOS DN/ PMB

MRD Complete

Engineering Feature

Complete End of

Serv

End of Serv

Comm

Phase I Concept

Implementation

Review PAC

1 Kickoff

Program

0 Review PAC

2 Review PAC

3 Review PAC

5 Review PAC

4 Review PAC

6

M15 Project

Initiation

M13 Solution Selected

PAC Review

M13

M11 Commit

ment

M7 Commit

ment Reaffirmed

M5 System

Test Readiness

M2 Regional

Ship Acceptance

FCSMC Book/Ship

M0 End of

Life

PAC Review

M7

M8 System Rqmts

Allocated

PAC Review

M11 PAC

Review

M3

M4 Ready

for Field Test

M3 Product / System

Readiness

Approval

Milestones

PLM


Managing Products 7


How AgilePLM Supports MGates/PLM Product Lifecycle Concepts (Applies to Product Items)

LC Phase-> Concept

Preliminary Develop- ment

Prototype Pilot Production Pending Obsolete

Obsolete

Purpose Initial Product creation

Release to ERP system

Prototype Build Ready

Product lock-down, engineering complete

Product ready for production release

Build Quantities

Not Applicable

Not Applicable

Prototype quantities only

Pilot runs for manufacturing validation

Ramp to production quantities

Ramp down to support phase out

Not Applicable

PLM / MGATEs

PLM only All subitems at production (Rev A / M3)

Order Readiness (GS)

Not Applicable

Not Applicable

Not Applicable

Paper Pilot to verify order readiness (OMAR / COF / MOL)

Not Applicable Not Applicable

Not Applicable

First Customer Ship

Not Applicable

Not Applicable

Not Applicable

Sales waivers if required

Change order initiated to document readiness (ES)

Not Applicable

Not Applicable


Managing Products 8


Item Lifecycle Phase vs. Product


Prepare for

Release

Production Release &

MOL Preliminary Development & Prototype Pilot Production

Design Lock-Down

New Items for Product

Items should be advanced into the Pilot phase well in advance of the higher level BOM or product moving to Pilot.


Prepare for

Release


Product Lifecycle


Design Lock-Down


Managing Products 9


How AgilePLM Supports MGates/PLM Item Lifecycle vs. Product Lifecycle

• In general, item lifecycles should run well in advance of the Product Lifecycle.

• All items on the Bill of Materials and sub-assemblies should be at the “Production” lifecycle phase prior to the Product being promoted to the “Pilot” lifecycle phase.

• Initial required parts qualification and environmental compliance activities at least 30 days prior to the product entering the “Pilot” lifecycle phase.

• Product Readiness Report can be used to monitor the status of all items on the Bill of Materials for a product.

8/9/2013


Managing Products 10


Module Map



Options Product

Readiness Report



Purpose of this section: • How to request an item using the worksheet template (item

template & how to submit a CR) • High level process for structuring models & options (no change

from today) • Submit an MC for lifecycle promotion




Models and Options High level process

Create Product BOM

Create Sales BOM

Promote Lifecycle

• Complete the Item Request Form

• May create in AgilePLM if model / option number(s) are known

• Submit CR (for item request to preliminary) to PCM

• EC (for item requests >= Development) to PCM

• Product Planner completes BOM structure worksheet

• Submit EC to PCM

• PCM assigns items to inventories and creates structures in AgilePLM

• Build BOM using appropriate spreadsheet

• Submit EC to PCM or PDC&MT

• PCM / PDC&MT create structures in AgilePLM and push to OMAR R12

• Review Product Readiness Report

• Submit MC or EC

Create Item




Models and Options Create Item

1. Identify new items from your BOM structure – Sales BOM (L2 - OMAR R12) & Product BOM (L3 - 11i and Trilogy)

2. Complete Part Number Request Excel Template 3. Complete Create Request (CR or EC) in AgilePLM

– Attach Excel Template to Change Request (CR) if requesting part number in prelim lifecycle

– Attach Excel Template to Engineering Change (EC) if requesting part number in development or further lifecycle

– Submit to PCM

Note: Can also create parts directly in AgilePLM (see Managing Items for detailed instructions)

Create Product BOM

Create Sales BOM

Promote Lifecycle Create Item




Models and Options Sales / Product BOM Relationships

S-BOM (L2 - OMAR) MFG/DC-BOM (L3 - ERP)

Line transfer from L2 to L3 – only Part Number




Models and Options BOM Example in AgilePLM




Models and Options Part Number Request Template

• Excel template can be used to request multiple parts at a time.

– Each row contains the information required to create a single part.

• Columns are color-coded to indicate what information is provided by each role.

– The requester only needs to fill in the orange columns.




Models and Options Part Number Request Template

• The amount of information required increases the further along the lifecycle you request…

• Prelim Life Cycle

– Part number only

• Development (send to Legacy ERPs)

– Makes internally orderable by purchasing through ERPs (“01N”)

• Pilot / Proto

– Makes test orderable through ERPs (“01C”)

• Production

– Orderable by customer through ordering system

• Use the chevrons to identify which columns to complete

Prelim Development

(send to Legacy ERPs)

Pilot / Proto / Production




Models and Options Part Number Request Template – Required for Prelim

Type SubClass Type

Description

Model Sales Model. Supports options and configurations.

Option Class Used in Sales Model. A grouping of related options.

Product Option A potentially needed internal item, or a potential item ordered to a model. The option could be only assembled and shipped in combination with a model.

Product Model Used for non-configurable models. Does not allow options. (SKU). Standalone products. WARNING: A type of Product can not contain options.

Product Kit An accessory to a product. Does not support options.

Product Phantom Phantom items are BOM items that are not transactable, stockable, or sellable (that contain a logical grouping of parts).

Product Tanapa An intermediate level of structure between a model and a kit.





Field Description Type Model, Option Class, Product

SubClass Type (Model/Option Class Type)

Define the ATO, PTO, CTO for Item (regardless of target system) • If you need assistance determining which item type to use,

contact your local NPI or PCM contact. SubClass Type (Product Type)

Define Model, Option, Kit, Phantom, or Tanapa

Orange color denotes columns filled in by the

Requestor




Models and Options Model Subclass Type Definitions

Type Subclass Type

Description

Model / Option Class

ATO Assemble To Order. Used in MFG site where the product is made. This is used in AgilePLM to 11i.

PTO Pick To Order. Used in DC site. This is used in AgilePLM to 11i.

CTO Configure To Order. Used to define sales model for order management in OMAR R12. Note: This is used for PTO models and option classes in OMAR R12.





Field Description General Description Description of item. MUST USE CAPITAL LETTERS

APC Account Product Code Enterprise Solutions – Use “ENTP”





Field Description Commodity Code To identify the Commodity of the Part

N/A for Model, Option & Option Class Only used for “Buy” Items

Owner Closely aligned with “Product Family” but also has elements of affected design function (e.g. electrical, mechanical) as well as site for product groups that have development in multiple global locations.

UoM Unit of Measure Usually use EA (Each) for Models & Options other values FR = For Reference MON = Month





Field Description Design Source To identify (Off-the-Shelf or MSI Custom)

For Models / Options, use “MSI Custom” PartNumber The prefix for the part number you to be created.

-Or enter the complete part number to be created. -Or leave blank to have PCM assign a part number.

Item Description Description of the Item to be created. USE CAPITAL LETTERS




Models and Options Part Number Request – Required for Development

Field Description Destination ERPs The ERPs where this item will reside:

Trilogy R12 Enterprise Solutions, Govt. Solutions Asia SAP Enterprise Solutions, Government Solutions Legacy ERP* Government Solutions

* Distribution Center, Manufacturing Site, OMAR R12 Responsible Location Legacy owner of the item. Used in PDM1.

Which site is responsible for maintaining the master attributes of the item. This is the same as is used today.





Field Description Mgf Site / DC The Manufacturing Sites / Distribution Centers the product will

reside. Legacy Item Status Same as used in the legacy systems today.

Legacy U of M Use EA for Models / Options.

Legacy 11i Item Type Same as used in the legacy systems today.





• If a part is needed in multiple Manufacturing Site / DCs, simply copy the entire line and modify the below fields.

– Template allows the creation of the part in all the Mfg Site/ DCs at the same time. Separate ECNs are no longer required.




Models and Options Multiple Mfg sites / DC

• Note: Any customer orderable items needs to have OM and either Trilogy or Legacy System(s).

• *McAllen is special case for Government Solutions. Contact PCM for more information.

Mfg Site/DC Up to # Lines Description

DC-CQ Elgin 3 OM, CQ, NS

MFG-AF Schaumburg 3 OM, AF, NS

MFG-CX Berlin 2 OM, CX

DC-IT Taunsstein 2 OM, IT Israel 2 OM, IE CD-MN McAllen 4* OM, AF, MN, NS

MFG-OT Reynosa 1 Government Solutions Parts / BOMs in Reynosa, use OT

MFG Penang 2 OM, Trilogy R12




Models and Options Legacy ERP information in AgilePLM





Field Description Contains Encryption Denotes if the product contains encryption: Yes / No

Notes Required if contains encryption = Yes Describe what kind of encryption is in the product. Provide a link to encryption questionnaire.




Models and Options Create CR or EC in AgilePLM

• If going to prelim only, must use Change Request (CR).

– See following slides for detailed instructions.

• If requesting a part in development or later, use Engineering Change (EC).

– See Managing Changes training module for detailed instructions.




Models and Options Complete Create Request (CR) in AgilePLM

1. Log into AgilePLM.

2. Create >Changes>Change Request.

3. Select value>Creation Request.





• The CR Number is Auto Generated.

• Product Family

– Choose appropriate value.

– Used for workflow routing and approvals.

• Set Request Priority to “Normal” <default value>.

• Click “Save”.





• Mandatory Fields

– Description of change • What you want done

– Reason for change • Why you want it done

– Reason code • CO_05_Create new item

– Workflow • Creation request

– Change Analyst • Choose appropriate PCM

group





• Non Mandatory Fields

– Change Category

– ECCN Comment

– CAD Libraries Required





• Chose attachment tab. • Add Attachment.

• Select your preferred method for

working with files. – Use standard browser upload

and download capabilities. – Use a Java tool to enable bulk

uploads and automated check-ins.

• The Java tool requires that your browser have Java installed and enabled.

• Click OK.





• Add Requester core-id to be notified when the CR is completed.

• Click Next Status to promote to submitted.




Models and Options Create Product BOM

Create Product BOM

Create Sales BOM

Promote Lifecycle

Product BOM (L3 – ERP BOM)

1. Prerequisite – Items are already requested and available in the target system.

2. Product Planner completes BOM structure worksheet.

– Same worksheet using today to define matrix.

Create Item




Models and Options Create Product BOM

Create Product BOM

Create Sales BOM

Promote Lifecycle

3. Construct structure in AgilePLM.

– Create directly in AgilePLM.

– Use BOM upload template using EC.

– See Managing BOMs Module for training.

4. Submit EC to promote BOM to development phase.

– PCM assign items to manufacturing site ERP(s).

– Propagates BOMs to all requested inventories.

Create Item




Models and Options Create Sales BOM

Sales BOM is for Ordering System (L2 - OMAR R12)

1. Prerequisite – Items are already requested and available in order management system.

– Mfg Site/DC = OM & other appropriate mfg/DC site(s)

– AgilePLM OM will create the PDM1/OM1 object.

– Initiates GIM/COF upload.

– Initiates OMAR upload.

– Always available in both order management systems.

Create Product BOM

Create Sales BOM





Models and Options Create Sales BOM

Create Product BOM

Create Sales BOM

Promote Lifecycle

2. Build up Sales (OM) BOM using the appropriate template.

– North America / Latin America Use Data Collection Template (DCT).

– Europe / Asia Use Product Data Template (PDT).

3. Send spreadsheet to PCM or Product Data Creation & Maintenance Team (PDC&MT).

– Use same process as today.

4. PCM / PDC&MT creates structures in AgilePLM from templates and push structure to OMAR R12.

Create Item




Models and Options Promote Lifecycle

Use MC / EC to promote model through the needed lifecycle phases. When moving to Production: • Use product readiness report to check product readiness.

• All items must be a production before moving top level to production.

• All Part Qualification has been completed.

• ECCNs are processed.

• Environment Compliance has been completed.

• All other criteria defined in the PLM or MGate process have been satisfied. • Submit an EC to promote to production.

– Changing a pre-production numeric revision to a production alphanumeric revision.

Create Product BOM

Create Sales BOM





How AgilePLM Supports MGates/PLM Product Lifecycle Concepts (Applies to Product Items)

LC Phase-> Concept

Preliminary Develop- ment

Prototype Pilot Production Pending Obsolete

Obsolete

Purpose Initial Product creation

Release to ERP system

Prototype Build Ready

Product lock-down, engineering complete

Product ready for production release

Build Quantities

Not Applicable

Not Applicable

Prototype quantities only

Pilot runs for manufacturing validation

Ramp to production quantities

Ramp down to support phase out

Not Applicable

PLM / MGATEs

PLM only

All subitems at production (Rev A / M3)

Order Readiness (GS)

Not Applicable

Not Applicable

Not Applicable

Paper Pilot to verify order readiness (OMAR / COF / MOL)

Not Applicable Not Applicable

Not Applicable

First Customer Ship

Not Applicable

Not Applicable

Not Applicable

Sales waivers if required

Change order initiated to document readiness (ES)

Not Applicable

Not Applicable




Module Map



Options Product

Readiness Report



.




Product Readiness Report

Used to monitor the readiness of a BOM structure for production release.

• Assists product managers, project managers, new product introduction managers, and SDE personnel monitor various attributes on the parts of a BOM.

• A one-stop-shop for detailed status of each item on a BOM activities needing to be completed prior to moving to production.

• Subset of information: – Lifecycle Status – Design Lockdown Date – W18’s info – Compliance – ECCN – Part Approval Status




Product Readiness Report Creating a Report

1. Search from the BOM in which you are interested.

2. Select Actions > Product Readiness Report.




Product Readiness Report Creating a Report (cont.)

A window will pop up.

3. Enter information in the Program Name and Production Date fields.

4. Click Submit.

AgilePLM displays a message indicating that the report is scheduled.

5. Click Close.




Product Readiness Report Creating a Report (cont.)

The report is sent you your email.

6. Select the attachment and open it.




Product Readiness Report Sample Report • 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




Module Map



Options Product

Readiness Report







Costing processes used today have not changed.

• Enterprise Solutions uses Cost Manufacturing Change (CMC) process in AgilePLM.

– For more information refer to the existing CMC process training.

• Government Solutions uses a different costing process external to AgilePLM and will not be covered here.

– For more information refer to the existing costing process training.




Module Map



Options Product

Readiness Report






Sales Waivers Sales Waiver processes used today have not changed.

• Enterprise Solutions uses processes in AgilePLM and Trilogy R12.

– For more information refer to the existing Sales Waiver process training.

• Government Solutions uses processes external to AgilePLM and will not be covered here.

– For more information refer to the existing Sales Waiver process training.




Module Map



Options Product

Readiness Report






Product Cancellation

• Once confirmed that a product will be cancelled and all the other external processes have been done, change the lifecycle.

– Create an MC.

– Change Lifecycle Phase to OBSOLETE.

– Make sure all levels “UP” and “DOWN” are cancelled as appropriate.

– Before cancelling, evaluate items for ongoing service needs.

Note: Processes to determine whether a product will be cancelled are not covered in this training.




Module Map



Options Product

Readiness Report






Summary

• AgilePLM supports MGates/PLM in rough alignment of product lifecycle with program milestones.

• Use the part number request template or AgilePLM to create new part numbers.

• The process and tools to set up Product and Sales BOMs are not changing from today.

• An EC is used to promote a product to Production only after all items in the product are in Production, Part Qualification and Environment Compliance have been completed, and ECCNs have been processed.

• The Product Readiness Report can be used to monitor the readiness of a BOM for production release.




Summary (cont.)

• The cost processes and sales waiver processes used by Enterprise Solutions and Government Solutions are not changing due to the rollout of PBT.

• After all external processes to cancel a product have been completed, an MC is used to change the lifecycle phase to Obsolete.

using agileplm in msi - motorola...

Documents