USING AgilePLM IN MSI

Transcription

1 USING AgilePLM IN MSI MANAGING PRODUCTS GNL E MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark GNL E Holdings, - Using LLC AgilePLM and are in used MSI under license. All Motorola other trademarks Solutions are the property of their respective Managing owners. Products 2013 Motorola Solutions, Inc. All rights reserved. 1

2 Module Objectives At the end of this module, you will be able to: 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. 2

3 Module Map How AgilePLM Supports MGates/PLM Models and Options Product Readiness Report Costing for Products Sales Waivers Product Cancellation Summary 3

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 4

5 How AgilePLM Supports MGates/PLM PBT High Level Processes Item Lifecycle Processes Create Items Develop & Mature Item / Attributes Design Lock-Down Prepare for Release Production Release & MOL End of Life Preliminary Development & Prototype Pilot Production Pending Obsolete & Obsolete Engineering Processes ECAD Interface MCAD Interface AgilePLM Partner & Supplier Collaboration Component Design & Fab Collaboration Contract Manufactures Component Qualification Environmental Compliance Software Interface Product Outsourced or Joint Design Product Change Notices Products & Bill of Materials Create BOMs, Models & Options Develop & Mature Product / Attributes Product Lock-Down Prepare for Release Production Release & MOL End of Life Preliminary Development & Prototype Pilot Production Pending Obsolete & Obsolete 5

6 How AgilePLM Supports MGates/PLM AgilePLM Lifecycle Phase: Alignment with PLM and MGates Products & Bill of Materials Create BOMs, Models & Options Develop & Mature Product / Attributes Product Lock-Down Prepare for Release Production Release & MOL End of Life Preliminary Development & Prototype Pilot Production Pending Obsolete & Obsolete PLM MRD Complete Phase I Concept Program PAC Kickoff Review 0 1 Milestones PRD Vendor Complete Selection Execute Plan Execute Continuous Improvement Phase II Plan PAC Review 2 Detailed Design Complete Engineering Feature Complete Phase III Development PAC Review 3 Initiate Beta Test Rev A Phase IV Product Acceptance FCSMC Book/Ship PAC Review 4 Proc t Volume Prod n Auth. General Availability Phase V Launch & Customer Sat PAC Review 5 Phase VI Sustain EOS Plan EOS DN/ PMB End of End Last Serv of Book Comm Serv Phase VII End of Life PAC Review 6 Approval M13 PAC Review M11 PAC Review M7 PAC Review M3 PAC Review M15 Project Initiation M13 Solution Selected M11 Commit ment M8 System Rqmts Allocated M7 Commit ment Reaffirmed M5 System Test Readiness M4 Ready for Field Test M3 Product / System Readiness M2 Regional Ship Acceptance M0 End of Life Business Case Portfolio Planning Project Definition Implementation Launch & Closeout 6

7 How AgilePLM Supports MGates/PLM Product Lifecycle Concepts (Applies to Product Items) LC Phase-> Concept Preliminary Development Prototype Pilot Production Pending Obsolete Obsolete Purpose Initial Product creation Release to ERP system Prototype Build Ready Product lockdown, 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 7

8 Item Lifecycle Phase vs. Product New Items for Product Create Items Develop & Mature Item / Attributes Design Lock-Down Prepare for Release Production Release & MOL Preliminary Development & Prototype Pilot Production Items should be advanced into the Pilot phase well in advance of the higher level BOM or product moving to Pilot. Product Lifecycle Create Items Develop & Mature Item / Attributes Design Lock-Down Prepare for Release Production Release & MOL End of Life August Preliminary 2013 Development & Prototype Pilot Production Pending Obsolete 8 & Obsolete

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 9

10 Module Map How AgilePLM Supports MGates/PLM Models and Options Product Readiness Report Costing for Products Sales Waivers Product Cancellation Summary 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 10

11 High level process Create Item Create Product BOM Create Sales BOM Promote Lifecycle Complete the Item Request Form May create in AgilePLM if model / option number(s) are known Product Planner completes BOM structure worksheet Submit EC to PCM Build BOM using appropriate spreadsheet Submit EC to PCM or PDC&MT Review Product Readiness Report Submit MC or EC Submit CR (for item request to preliminary) to PCM EC (for item requests >= Development) to PCM PCM assigns items to inventories and creates structures in AgilePLM PCM / PDC&MT create structures in AgilePLM and push to OMAR R12 11

12 Create Item Create Item Create Product BOM Create Sales BOM Promote Lifecycle 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) 12

13 Sales / Product BOM Relationships S-BOM (L2 - OMAR) MFG/DC-BOM (L3 - ERP) Line transfer from L2 to L3 only Part Number 13

14 BOM Example in AgilePLM 14

15 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. 15

16 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 Prelim Development (send to Legacy ERPs) Orderable by customer through ordering system Use the chevrons to identify which columns to complete Pilot / Proto / Production 16

17 Part Number Request Template Required for Prelim Type Model Option Class SubClass Type Description Sales Model. Supports options and configurations. 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. 17

18 Part Number Request Template Required for Prelim Field Type SubClass Type (Model/Option Class Type) SubClass Type (Product Type) Description Model, Option Class, Product 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. Define Model, Option, Kit, Phantom, or Tanapa Orange color denotes columns filled in by the Requestor 18

19 Model Subclass Type Definitions Type Model / Option Class Subclass Type ATO PTO CTO Description Assemble To Order. Used in MFG site where the product is made. This is used in AgilePLM to 11i. Pick To Order. Used in DC site. This is used in AgilePLM to 11i. 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. 19

20 Part Number Request Template Required for Prelim Field General Description APC Description Description of item. MUST USE CAPITAL LETTERS Account Product Code Enterprise Solutions Use ENTP 20

21 Part Number Request Template Required for Prelim Field Commodity Code Owner UoM Description To identify the Commodity of the Part N/A for Model, Option & Option Class Only used for Buy Items 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. Unit of Measure Usually use EA (Each) for Models & Options other values FR = For Reference MON = Month 21

22 Part Number Request Template Required for Prelim Field Design Source PartNumber Item Description Description To identify (Off-the-Shelf or MSI Custom) For Models / Options, use MSI Custom 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. Description of the Item to be created. USE CAPITAL LETTERS 22

23 Part Number Request Required for Development Field Destination ERPs Responsible Location Description 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 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. 23

24 Part Number Request Required for Development Field Mgf Site / DC Legacy Item Status Legacy U of M Legacy 11i Item Type Description The Manufacturing Sites / Distribution Centers the product will reside. Same as used in the legacy systems today. Use EA for Models / Options. Same as used in the legacy systems today. 24

25 Part Number Request Required for Development 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. 25

26 Multiple Mfg sites / DC 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 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. 26

27 Legacy ERP information in AgilePLM 27

28 Part Number Request Required for Development Field Contains Encryption Notes Description Denotes if the product contains encryption: Yes / No Required if contains encryption = Yes Describe what kind of encryption is in the product. Provide a link to encryption questionnaire. 28

29 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. 29

30 Complete Create Request (CR) in AgilePLM 1. Log into AgilePLM. 2. Create >Changes>Change Request. 3. Select value>creation Request. 30

31 Complete Create Request (CR) in AgilePLM 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. 31

32 Complete Create Request (CR) in AgilePLM 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 32

33 Complete Create Request (CR) in AgilePLM Non Mandatory Fields Change Category ECCN Comment CAD Libraries Required 33

34 Complete Create Request (CR) in AgilePLM 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. Click OK. The Java tool requires that your browser have Java installed and enabled. 34

35 Complete Create Request (CR) in AgilePLM Add Requester core-id to be notified when the CR is completed. Click Next Status to promote to submitted. 35

36 Create Product BOM Create Item 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. 36

37 Create Product BOM Create Item 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. 37

38 Create Sales BOM Create Item Create Product BOM Create Sales BOM Promote Lifecycle 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. 38

39 Create Sales BOM Create Item 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. 39

40 Promote Lifecycle Create Item Create Product BOM Create Sales BOM 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. 40

41 How AgilePLM Supports MGates/PLM Product Lifecycle Concepts (Applies to Product Items) LC Phase-> Concept Preliminary Development Prototype Pilot Production Pending Obsolete Obsolete Purpose Initial Product creation Release to ERP system Prototype Build Ready Product lockdown, 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 41

42 Module Map How AgilePLM Supports MGates/PLM Models and Options Product Readiness Report Costing for Products Sales Waivers Product Cancellation Summary. 42

43 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 43

44 Product Readiness Report Creating a Report 1. Search from the BOM in which you are interested. 2. Select Actions > Product Readiness Report. 44

45 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. 45

46 Product Readiness Report Creating a Report (cont.) The report is sent you your Select the attachment and open it. 46

47 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 47

48 Module Map How AgilePLM Supports MGates/PLM Models and Options Product Readiness Report Costing for Products Sales Waivers Product Cancellation Summary 48

49 Costing for Products 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. 49

50 Module Map How AgilePLM Supports MGates/PLM Models and Options Product Readiness Report Costing for Products Sales Waivers Product Cancellation Summary 50

51 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. 51

52 Module Map How AgilePLM Supports MGates/PLM Models and Options Product Readiness Report Costing for Products Sales Waivers Product Cancellation Summary 52

53 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. 53

54 Module Map How AgilePLM Supports MGates/PLM Models and Options Product Readiness Report Costing for Products Sales Waivers Product Cancellation Summary 54

55 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. 55

56 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. 56