using agileplm in msi - motorola...

GNL1147.00E - Using AgilePLM in MSI August 2013

Procurement 1

Motorola Solutions Internal

USING AgilePLM IN MSI PROCUREMENT

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.


Procurement 2


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

Objectives

• Discuss the unified component item number structure.

• Discuss activities performed during item Lifecycle phases.

• Discuss Commodity Codes.

• Discuss Procurement User Groups.

• Discuss Sourcing Requirement activities.

• Discuss Sourcing Project activities.

• Perform Procurement searches.

• Run Procurement reports.


Procurement 3


Module Map

Item Create Sourcing Requirements

Sourcing Project

Searches and Reports Summary


Procurement 4


Item Create Introduction

• Item Part Numbering Strategy & Item Classification

• Lifecycle Definitions & Management

• Commodity Code Assignment & Maintenance

• Procurement User Groups


Procurement 5


Item Create Introduction Implementing a combined item type classification

The new item classification structure moves common information from the description into searchable attribute fields.

Some benefits of the new item classification structure include:

• Improved search and reuse capabilities in AgilePLM (primarily in the electrical family)

• Higher visibility to critical part-type specific attributes (such as capacitance and number of conductors)

• Item auto-numbering and auto-description generation

• Descriptions are auto-generated based on item field selections


Procurement 6


Item Create Introduction Part Subclasses At Item Create the creator selects the subclass and part type for each new item. There are currently 52 subclass items that are created in AgilePLM.

– Example of Subclass: Battery or Capacitor

– Example of Part type: Battery Pack or Fixed Capacitor

AgilePLM will generate auto-numbering and auto-description of the item. – Example: Battery (BTnnnnnn) or Capacitor (CAnnnnnn).

Each Part subclass comes with its own unique Parametric Attributes that should be completed if the information is available.

– Example: Battery > Type (Coin/Non-Coin)

> Chemistry (Lithium Ion)

Note: Parametric Attributes are additional attributes that further define each Part subclass. Parametric Attributes are specific to the particular Part subclass.


Procurement 7


Item Create Item Numbering Structure for PBT Introduction to the unified component item number structure

• Prefix: Consists of two alpha characters based on component subclasses. For example, AY is used for Accessories, BT is used for Batteries

• Body: Consists of six numeric digits in sequence

• Suffix: Consists of one alpha character for the expander separator two numeric digits for the expander number

Note: If the expander number exceeds 99 tabs, we will use alpha digits after 99, such as AA up to AY. (for example, BT000001A01, BT000001A02, … , BT000001A99, BT000001AAA, BT000001AAB, … , BT000001AAY, BT000001ABA, BT000001ABB, … , and so on.)

Example: BT000001A01 BT is used to represent the Battery subclass, 000001 is the base number, A is the

expander separator, and 01 indicates that this is the first tab Item in the series.

PPNNNNNNSEE

P = Prefix S = Expander Separator E = Expander Number N = Base Number


Procurement 8


Item Create New Item Numbering Structure for PBT Examples of the component subclasses and the prefixes

Component Subclass

• The table on the right shows examples of the component subclasses and their prefixes.

• By default, AgilePLM will auto-generate the item numbering based on the subclass of the item, however, you can also manually input the item numbering as required.

COMPONENT SUBCLASS

PREFIX START NUMBER

Accessory AY000001A01

Antenna AN000001A01

Battery BT000001A01

Capacitor CA000001A01

Display DM000001A01

Equipment EQ000001A01

Hardware HW000001A01


Procurement 9


Item Create Item Numbering Structure for PBT (cont.) Examples of the document subclasses and the prefixes

Document Subclass

• Items in the Document class also have unique prefixes.

• The table on the right shows examples of the document subclasses and their prefixes.

• Documents can be attached to either a family or an item.

DOCUMENT DETAILS TYPE

PREFIX START NUMBER

Artwork AR000001A01

Test Results PD000001A01

Schematic SD000001A01

Part Note PN000001A01

MSI Global Spec GS000001A01

CAD Database DB000001A01


Procurement 10


Item Create Item Lifecycles

There are seven lifecycles associated with an item:

• Preliminary

• Development

• Prototype

• Pilot

• Production

• Pending obsolete

• Obsolete

The following slides show the activities included in each lifecycle.


Procurement 11


Item Create AgilePLM Item Lifecycle: Preliminary Phase

Purpose Initial Item Creation Change Control No Change Control in AgilePLM and items are not in ERPs

AML Not Required

Cost Not Required

Build Not Applicable

Purchase Must be purchased by Engineering

Qualification Not Applicable

Notes Preliminary item can have a BOM associated with it Commodity Code assigned at Part Create


Procurement 12


Item Create AgilePLM Item Lifecycle: Development Phase

Purpose Allow Proof of Concept BOM Change Control • Release to ERP

• EC/MC objects for change control AML Not Required Cost Not Required Build Engineering Builds Purchase May be purchased by Engineering or through ERP with Eng

Approval Qualification Possible early Supplier Engagement


Procurement 13


Item Create AgilePLM Item Lifecycle: Prototype Phase

Purpose Builds that verify designs and manufacturability

Change Control • Item in ERP • EC/MC objects for change control

AML • Proposed Manufacturer(s) • Working on Tooling/Manufacturing commitments

Cost Preliminary cost required in ERP

Build Engineering Builds

Purchase All parts purchased through ERP for prototype quantities

Qualification Possible early Supplier Engagement

Notes Item Enrichment is Complete


Procurement 14


Item Create AgilePLM Item Lifecycle: Pilot Phase

Purpose Builds that demonstrate Supply Chain Readiness

Change Control • Item in ERP • EC/MC objects for change control

AML Selected manufacturer(s)

Cost Standard cost required

Build Pilot runs for manufacturing validation

Purchase All parts purchased through ERP

Qualification PAF, Qual Data and W18 info gathered

Notes • Item cannot be shipped in volume to external customers • Sales Waiver required in order to ship to external customers


Procurement 15


Item Create AgilePLM Item Lifecycle: Production Phase

Purpose Build Item in volume for external customers Change Control • Item released in ERP

• EC/MC objects for change control

AML Qualified manufacturer(s) Only

Cost Standard

Build Mass production for external shipment


Qualification Qual & W18 activities complete


Procurement 16


Item Create AgilePLM Item Lifecycle: Pending Obsolete

Purpose Stop Using in New Designs Change Control • Item released in ERP

• EC/MC objects for change control

AML Qualified manufacturer(s) Only

Cost Standard

Build Mass production for external shipment or Ramp down to support phase out


Qualification Not Applicable

Notes Possible LTB Activity


Procurement 17


Item Create AgilePLM Item Lifecycle: Obsolete

Purpose No Longer in Use Change Control • No changes necessary unless reverting to a prior Lifecycle

AML Not Applicable

Cost Not Applicable

Build Not Applicable

Purchase Not Applicable

For more information on the Item Numbering Strategy and Lifecycle Phases refer to the Managing Items Module also available through the Learning Management System.


Procurement 18


Item Create Commodity Codes

Before PBT After PBT

>1950 Commodity Code Combinations Approximately 250 Commodity Codes ICCS Codes are 3 levels (Commodity, Device, Category). AgilePLM Commodity Code will be one value.

Engineering selects codes, but is not a stakeholder in the process. Incorrect selections are frequently not caught until after material is received.

SCT Teams will be notified weekly of new parts created and will verify the AgilePLM Commodity Code selected for the part through AML Workflow Objects.

Codes are not defined by Category Strategies. AgilePLM Commodity Codes will be aligned with Category Strategies and used in the maintenance of the CRIS ASL.

Limited Search Capability for Approved Suppliers for Engineering

Extended Search capabilities will allow Engineering to search in AgilePLM for Approved Manufacturers by Commodity Code.

Lack of consistent collaboration on part AML AML assignment and changes will require Procurement approval or notification at various lifecycle phases.

Manual ASL Compliance Metrics ASL rating as an attribute to parts allows an automated Compliance metric and BOM Reporting.

Procurement Contacts mapping is difficult to manage and not related to attributes on a part.

Fewer Commodity Codes aligned to Strategies allow the maintenance in AgilePLM of Commodity User Groups enabling workflow/notifications and identification of the Procurement contact (User Group).


Procurement 19


Item Create Commodity Codes • Two-step Approach to Data Migration:

– Mapped ICCS codes to new Commodity Codes for all items

• Example: HDWR.WASHR.MISC = Metals - Hardware

– Additional mapping for select parts that couldn’t easily be mapped code to code

• Example: SEMI.MEM.MISC = Legacy - Semiconductor

• Updated Commodity Code structure, processes and reports for multiple systems including SAP, R12, 11is, Schedule Sharing, GIM, TPC and CRIS

• MCIS was not updated, and conversion from the new code back to an ICCS code occurs in Schedule Sharing.


Procurement 20


Item Create Commodity Codes in AgilePLM

• Commodity Codes are mastered and under change control in AgilePLM.

• Procurement users will have the ability to both initiate and approve the Change Object required to update a Commodity Code.

• Mass changes can be performed with the help of AgilePLM IT, if needed.

• New commodity codes that need to be added for business processes and reporting must be added in AgilePLM first via an AgilePLM IT Help Desk ticket.

• New Commodity Code requests during post Go-Live period should be routed to Susan Brauner (JGM734) for execution.

• New Commodity Code requests need to be coordinated with the process owners in R12, SAP, Schedule Sharing, TPC, MCIS, 11i and GIM.


Procurement 21


Item Create Commodity Codes Updating a Commodity Code

To create an MC:

1. Select Create New > Changes> Manufacturer Orders.

2. Enter Number (Mfr. Orders Number), Change Category (Maintenance of Line), Description and Reason, Division and Affected Design Functions and click Save.

3. Enter the Reason Code (MC_14 Commodity Code Change), Workflow, Change Analyst, and the Product Line (0 for none) and click Save.


Procurement 22


Item Create Commodity Codes Updating a Commodity Code (cont.)

4. Go to the Affected Items Tab and add item(s).

5. For single item, enter code change details to the description field; for multiple items attach the list of parts with the old code and new code on the Attachments Tab.


Procurement 23


Item Create Commodity Codes Updating a Commodity Code (cont.)

6. For Mass changes, the Affected Item does not need to be added; the Change Analyst will import the items for change.

7. Go to the Workflow Tab and click on Submitted.

The Change Analyst will update the parts and route the change for Approval.

Once the MC is approved, the MC auto-releases.

NOTE: Andy Kayton will be the Change Analyst supporting Procurement for Commodity Code changes at Go-Live.


Procurement 24


Item Create Procurement User Groups • Procurement user groups have been created for each commodity code object.

• Category managers and category analysts can maintain themselves as a user on each commodity code object that they manage or support.

• Notifications and change objects for AML and Commodity Code changes will be routed automatically based on the Procurement User Group.

• Staffing changes within the procurement organization must be maintained for Procurement User Groups to be effective.

• For Commodity Codes where there is no Procurement User, Approvers will need to be manually added.

• Note: Category Analysts can only maintain themselves as a user for commodity objects when there is also a Category Manager assigned. The Analyst cannot be the sole user on a Commodity Code object.


Procurement 25


Item Create Procurement User Groups Updating Procurement User Groups

1. Select Custom Search.

2. Select User Groups and Procurement Commodity for search criteria.

3. Select Search.

4. Click on hyperlink to user group, select users tab and add name.


Procurement 26


Module Map


Sourcing Project



Procurement 27


Sourcing Requirements Introduction

• Determine Sourcing Requirements Process

• Modifications to CRIS ASL

• New Manufacturer Request/Manufacturer Maintenance

• Maintaining the AML

• ASL Ratings/Compliance & PPL Process

• MSI Relationship Attribute


Procurement 28


DETERMINE SOURCING REQUIREMENTS


Procurement 29


Determine Sourcing Requirements Determine Sourcing Requirements Workflow


Procurement 30


Determine Sourcing Requirements Search for Approved Manufacturers by Commodity • The process begins with the initial search for Approved Manufacturers

by Commodity.

• AgilePLM Manufacturers that appear on the CRIS ASL are populated with the Approved Commodities to allow Designers to see the Approved Manufacturers.


Procurement 31


Determine Sourcing Requirements Searching for Approved Manufacturers by Commodity • The Approved Manufacturers by Commodity Search is found in the

Procurement Searches in the Global Search menu.


Procurement 32


Determine Sourcing Requirements Searching for Approved Manufacturers by Commodity

1. Click on the Search box to search for the Commodity Code.

• Use * for a wildcard search.


Procurement 33



2. Once Commodity Code(s) are selected click Run.


Procurement 34



Approved Manufacturers appear.

3. To Export, click More and export to the desired file format


Procurement 35


Determine Sourcing Requirements Manufacturer Selection • Designers will collaborate with the SCT (Strategic Component Team)

representative or Category Manager to potentially narrow the list of Approved Manufacturers for any given sourcing opportunity.

• If Designers are unable to use one of the manufacturers that are approved, they will be able to escalate inside AgilePLM to the SCT through the use of a Discussion Object for a recommended alternate. Refer to Module 3 Managing Discussion Objects.

• Once the DO is received by the SCT team they may contact the requestor for additional data and then either approve a Designer selected alternate or provide additional options.

• The SCT representative or Category Manager may opt to create a Sourcing Project and RFI with on-boarded partners to assist the Designer with Manufacturer/Manufacturer Part selections.

• The SCT representative or Category Manager may also invite the Designer to be a user within the Sourcing Project to provide input or observe the Partner collaboration on the item.


Procurement 36


Determine Sourcing Requirements Manufacturer Selection (cont.)

• If the agreed-upon Manufacturer is new, the Designer or Category Manager will need to request that the new Manufacturer be added to AgilePLM per the Create Manufacturer Request process.

• If the DE creates the New Manufacturer Request, the Category Manager contact must be notated on the request object for the appropriate approval routing.

• Once Manufacturers are selected for a part the Design Engineer will maintain the AML per the Create/Update AML process.

• AML creation and change will include approvals by the Procurement Category Manager based on the Commodity Code assigned to the MSI Part and the lifecycle of the item.


Procurement 37


MODIFICATIONS TO ASL


Procurement 38


Sourcing Requirements Modifications to CRIS ASL

• CRIS ASL is now managed using the AgilePLM Manufacturer rather than the Supplier.

– AgilePLM is the master for MSI Manufacturers and the manufacturer table is interfaced to CRIS and maintained in the ASL.

– New manufacturers must be added to AgilePLM before they can be added to the CRIS ASL.

• The subcategory or description is replaced by the applicable commodity codes/category strategy.

– Commodity codes are mastered in Agile PLM, interfaced to CRIS and maintained in the ASL table.

– New commodity codes must be added to AgilePLM before they can be added to the CRIS ASL.


Procurement 39


Sourcing Requirements Modifications to CRIS ASL (cont.)

• Commodity codes (category strategies) selected for each manufacturer are interfaced to AgilePLM and populated on the Manufacturer Object in the Approved Commodities field.

• The Approved Commodities fields allow the search for Approved Manufacturers by Commodity Code.

• The Approved Commodities field in AgilePLM is used in the calculation of ASL ratings on the AML and the ASL Compliance for MSI Items.


Procurement 40


Sourcing Requirements CRIS ASL Report

• To run the CRIS ASL Report go to the ASL, select ASL Report.

• Enter report criteria such as Category Lead, CRIS Commodity, Change Date criteria, Order By, and Output Results.

• Click Run Report.


Procurement 41


Sourcing Requirements ASL Report Modifying the CRIS ASL

1. To Modify the ASL select Add/Modify ASL.

2. Select the CRIS Commodity and click Continue.

3. To remove a Manufacturer click Remove next to the Manufacturer Name.

4. Enter the Justification and click Submit Change Request.


Procurement 42


Sourcing Requirements ASL Report Modifying the CRIS ASL (cont.)

1. To Edit an existing ASL Manufacturer select Add/Modify ASL.


3. To edit a Manufacturer click on Edit next to the Manufacturer Name.

4. Enter the Justification and click Submit Change Request.


Procurement 43



1. To Add a new Manufacturer to the ASL select Add/Modify ASL.


3. Select Add a Manufacturer To This CRIS Commodity.

4. Enter Justification and click on Manufacturer Lookup.

5. Enter partial or full manufacturer name in the search box and click Search.


Procurement 44



1. Select the manufacturer you want to add.

2. Add the Commodity Codes (Approved Strategies) for the Manufacturer.

3. Click Submit Change Request.


Procurement 45


MANUFACTURER MAINTENANCE


Procurement 46


Sourcing Requirements Manufacturer Maintenance Create/Edit/Consolidate Manufacturer Workflow Uses

The Create/Edit/Consolidate Manufacturer workflow is used when:

• A new manufacturer is requested

• Existing manufacturers cannot provide the required technical requirements

• When a Request is made to edit or consolidate manufacturers


Procurement 47


Sourcing Requirements Manufacturer Maintenance Create/Edit/Consolidate Manufacturer Workflow


Procurement 48


Sourcing Requirements Manufacturer Maintenance Searching for a Manufacturer

AgilePLM accepts two wildcards that can be used in any of the searches.

- The question mark (?) finds matches with any single character.

- The asterisk (*) finds matches with more than one character.

Important Note: When executing a search that would yield more than 3000 values, it is critical to export the results to see the full list of returned values.


Procurement 49


Sourcing Requirements Manufacturer Maintenance Searching for a Manufacturer

1. Select Custom Search.

2. In the Search Criteria, select Manufacturers from the drop-down list.

3. Enter the name of the manufacturer and click Search.

If the manufacturer is not found, create a New Manufacturer Request.


Procurement 50


Sourcing Requirements Manufacturer Maintenance Add/Edit/Consolidate a Manufacturer

• Users create a Manufacturer Request.

- Users cannot add/edit/consolidate a manufacturer directly.

• Only the Manufacturer Administrator can add, edit, or consolidate manufacturers.

• The Manufacturer Request goes through:

Change Analyst Procurement Quality (Manufacturer Administrator) (Approver) (Observer)


Procurement 51


Sourcing Requirements Manufacturer Maintenance Reasons to Submit an Edit Manufacturer Change Request

Reasons to edit manufacturer’s details include:

• A manufacturer name change

• One company acquires another

• A manufacturer address, e-mail, or URL change

• A manufacturer product line is sold off


Procurement 52


Sourcing Requirements Manufacturer Maintenance Add/Edit/Consolidate a Manufacturer Role Functions

• (Submitter) Creating a Manufacturer Request

• (Change Analyst) Processing the Manufacturer Request

• (Approver) Approving the Manufacturer Request

• (Manufacturer Administrator) Creating a New Manufacturer

• (Manufacturer Administrator) Editing Manufacturer Information

• (Manufacturer Administrator) Consolidating Manufacturers

• (Change Analyst) Completing the Manufacturer Request


Procurement 53


Sourcing Requirements Manufacturer Maintenance (Submitter) Creating a Manufacturer Request

Use the Change Request workflow to create/edit/consolidate manufacturers.

1. Select Create New > Changes > Change Requests.

The Create New Change Requests window appears.

2. For the Type of Change Request, select Manufacturer Request from the drop-down list.


Procurement 54


Sourcing Requirements Manufacturer Maintenance (Submitter) Creating a Manufacturer Request (cont.)

3. Enter information in the Change Category field.

4. For Reason Code, select the appropriate code:

– MR_01 – New Manufacturer Request

– MR_02 – Edit Manufacturer

– MR_03 – Consolidate Manufacturers

5. Enter information in the Product Line(s), Change Request Priority, Division, Manufacturer Name and Manufacturer Type fields.

6. Click Save.


Procurement 55



7. For consolidation requests only:

a) Select the Attachments tab.

The Add Files window appears.

b) Browse for any files from the manufacturer to add to the change request.

c) Click Add to attach the files to the change request.

Note: A Consolidate Manufacturers change request requires an attachment. The attachment can be a letter from the company with notification of the consolidation.


Procurement 56



8. Review the details and make any necessary changes.

9. Under Change Analyst, select Manufacturer Admin and click Save.

Note: The status of the Manufacturer Request is Unassigned.


Procurement 57



10. Select the Workflow tab and click Submitted on the workflow summary diagram to submit the Manufacturer Request for approval.


Procurement 58



A user/requestor cannot promote the workflow to Approval or Released.

11. In the Comments field enter the name of the category manager.

The Manufacturer Administrator adds these names as Approvers.

12. Click Finish.

The selected Change Analyst is notified of the change request.

IMPORTANT! Add a comment if working with an Administrator.


Procurement 59


Sourcing Requirements Manufacturer Maintenance The Change Analyst Processes the Manufacturer Request 1. From the home page, select the

change request from the Workflow Routings tab.

2. Review the request and in the Workflow tab, select Approval from the workflow summary diagram.

The Change Status to Approval window appears.

3. Add the Approvers (Procurement) and persons to Notify (Quality) and click Finish.

The Approvers are notified.


Procurement 60


Sourcing Requirements Manufacturer Maintenance Procurement Approves the Manufacturer Request

1. From the home page, select the Workflow Routings tab.

2. Click the hyperlink for the New Manufacturer Request waiting for approval.


Procurement 61


Sourcing Requirements Manufacturer Maintenance (Approver) Approving the Manufacturer Request (cont.)

The selected New Manufacturer Request page appears.

3. Review the request and click Approve.


Procurement 62


Sourcing Requirements Manufacturer Maintenance (Approver) Approving the Manufacturer Request (cont.)

The Approve for Approval window appears.

4. Add any comments additional comments and click Approve.

The Change Analyst (in this case the Manufacturer Administrator) is notified.

Note: Comments may also be added from the Approval window for clarification purposes. Requests may also be rejected when appropriate.


Procurement 63


Sourcing Requirements Manufacturer Maintenance The Manufacturer Administrator Creates the New Manufacturer

1. From the home page select the Workflow Routings tab.

2. Select the approved change request.

3. Select Create New > Manufacturers.

The Create New Manufacturers window appears.

4. Select the Type and Name of the new manufacturer.

5. Click Save.

6. Enter the general information of the manufacturer and click Save.

A new manufacturer is created.


Procurement 64


Sourcing Requirements Manufacturer Maintenance (Manufacturer Administrator) Editing Manufacturer Information

Note: This procedure can only be performed by a Manufacturer Administrator. 1. From the home page, select the Workflow Routings tab. 2. Select the approved change request. 3. Review the change request and select the manufacturer for edit. 4. In the manufacturer page click Edit. 5. Make the changes to the manufacturer and click Save. 6. Select Continue and click Finish. 7. Review the changes.

The manufacturer details have been edited.

IMPORTANT! A change in Oracle R12 (via manual process) must be made in parallel. If the change is not made in Oracle R12, the next time a workflow object that uses the manufacturer is released, a fail will result.


Procurement 65


Sourcing Requirements Manufacturer Maintenance (Change Analyst) Consolidating Manufacturers

1. From the home page select the Workflow Routings tab. 2. Select the approved change request.

3. Review the approved change request and select the manufacturers for consolidation.

4. Select the first manufacturer to update its lifecycle phase to Obsolete. 5. In the manufacturer page click Edit and update the Lifecycle Phase to Obsolete.

The manufacturer’s page indicates the status is Obsolete.

6. Select the Where Used tab to identify all the items from the obsoleted manufacturer that are in the AML.

7. Redline all items from the obsoleted manufacturers to another manufacturer.

IMPORTANT! A change in Oracle R12 (via manual process) must be made in parallel. If the change is not made in Oracle R12, the next time a workflow object that uses the manufacturer is released, a fail will result.


Procurement 66


Sourcing Requirements Manufacturer Maintenance (Change Analyst) Completing the Manufacturer Request


2. Select the new manufacturer request.

3. Select the Workflow tab.

4. Click Released on the workflow summary diagram.

The Change Status Released window appears.

5. Click Finish.

Note: The requestor receives notification that the new manufacturer has been created.


Procurement 67


Sourcing Requirements Manufacturer Maintenance Relationship Between Supplier and Manufacturer Objects

• AgilePLM distinguishes the Manufacturer and the Supplier as two separate objects.

• AML management uses the Manufacturer object.

• Partner Access uses the Supplier object.

• Supplier user information is maintained on the Supplier object.

• Upon creation of a new manufacturer a corresponding supplier is created.

• The corresponding Supplier object is linked to the Manufacturer.

• The Supplier Access field on the Manufacturer object is populated with the corresponding Supplier name.


Procurement 68


Sourcing Requirements Manufacturer Maintenance Relationship Between Supplier and Manufacturer Objects (cont.)

• The Supplier Access field on an item is populated with the Supplier Name(s) of the corresponding Manufacturer(s) that appear on the AML of the item.

• AgilePLM process extensions also populate supplier attributes on BOM items and documents reporting to an item where the manufacturer appears on the AML.

• Partner access relies on the supplier attributes for supplier visibility for the parts and products that they supply.


Procurement 69


PARTNER ACCESS


Procurement 70


Sourcing Requirements Partner Access Request to Grant Partner Access

• Internal MSI users determine whether a Partner requires access

• Once confirmed, the user will verify that the affected manufacturer object exists in AgilePLM.

• If it does not exist, the user identifies the Category Manager Approver and creates a request to add the Manufacturer to AgilePLM based on the Managing Manufacturers and Manufacturer Parts for Creators training module.

• Once the manufacturer object exists in AgilePLM the user creates a Partner Access Request (PAR) object that is routed to the appropriate Category Manger for approval.

• For more information on the partner access process refer to the Supplier Onboarding Request Processing training module.


Procurement 71


MAINTAINING THE AML


Procurement 72


Sourcing Requirements Maintaining AML AML Maintenance Tasks

• Maintenance of the AML can include:

– Deleting manufacturer parts from the AML

– Adding manufacturer parts to the AML

• Category Managers will be Approvers for AML changes in the Prototype, Production and Pending Obsolete lifecycles.

• Category Managers will be Observers to AML changes in Development.

• Category Managers will be Approvers for lifecycle promotions to Prototype.

• Category Managers will be Observers on lifecycle promotions to Development, Pilot and Production.


Procurement 73


Sourcing Requirements Maintaining AML AML Approval Routings

Design Preliminary Development Prototype

Manufacturing Validation Pilot Production

End of Life

Pending Obsolete Obsolete

SC

T A

ctiv

ity (P

re-P

art

Cre

atio

n) Part Create: Get initial

MSI Part #, Commodity Code

Assigned

Commodity Code determines User

Group (Procurement + SCT) assigned

User Group alerted to new MSI parts

created via report

Observer Workflow (EC/MC Only) – Approval not Required – No Cycle-time impact

Approval Workflow (EC/MC Only)

Review Comment on Reason

Reject? End

Approve or No Response

Review Comment on Reason

Reject? End

Approve

Escalate to Procurement Mgr

No Response (2 days)

Promote to “Dev” “Proposed” AML exists

ECMC EC = General Engineering Change, MC = Material Change (Used for Life-cycle or AML changes)

EC MC

EC MC

EC MC

Breadboards: Experimentation and preliminary

evaluation of Design

alternatives

Possible AML modifications “Proposed”

AML additions or changes

EC MC

Initial Mfg Builds: System / sub-

assembly evaluation

Possible AML modifications “Proposed”

Final Mfg Builds

Product Qual

Environmental Data Collection

Qualified AML Parts moved from

“Proposed” -> “Qualified” via Qual

object

EC MC

Promote to “Production”

Product Change Notices from Suppliers (PCNs)

EC MC

Last Time Buys

EC MC

Yes Yes

EC MC

EC MC Proposed

Approval Flow


Promote to “Pilot”


AML additions or changes EC

MC

Ensure contract terms & volume commitments

Possible initial AML entry “Proposed” for

OTS

EC MC

EC MC EC MC

EC MC

Promote to “Prototype”


Procurement 74


Sourcing Requirements Maintaining AML Approving an AML Maintenance Request

Log into AgilePLM.


2. Select the MC that is awaiting approval.

3. Click the MC hyperlink, and review the affected items.

4. If there are no issues, click Approve.


Procurement 75


5. The Approve for Approval window appears.

6. Add any comments and click Approve to approve the MC.

The MC is now approved. The Change Analyst will be notified by AgilePLM to complete processing the change.

Sourcing Requirements Maintaining AML Approving an AML Maintenance Request (cont.)


Procurement 76


ASL RATINGS/COMPLIANCE AND PPL PROCESS


Procurement 77


Sourcing Requirements ASL Ratings/Compliance & PPL Process ASL/PPL Attributes

• Three new attributes in AgilePLM related to the ASL

– ASL Ratings (Approved/Blank) – Calculated on the item AML based on the manufacturer, it’s Approved Commodities and the commodity code assigned to the item

– ASL Compliance (Approved/Blank) – Calculated as “Approved” on the item if at least one manufacturer on the AML has an ASL rating of “Approved”

– PPL Rating (Approved/Not Approved/Not Scored)

• Management of the PPL Ratings is moving from CRIS to AgilePLM

– Changes to the ASL Compliance trigger changes and alerts for the PPL attribute

• Example: If an item has an ASL Compliance of “Approved” and a PPL Rating of “Approved”, and an AML change occurs to change the ASL Compliance to blank, the PPL Rating will be updated to Not Approved.


Procurement 78


Sourcing Requirements ASL Ratings/Compliance & PPL Process Where to view the ASL Rating

Manufacturer Object Where Used AML View


Procurement 79


Sourcing Requirements ASL Ratings/Compliance & PPL Process Where to view the ASL Compliance & PPL Attributes

Item View Search View


Procurement 80


MSI RELATIONSHIP PROCESS


Procurement 81


MSI Relationship Process Overview Process Flow for Enterprise


Procurement 82


MSI Relationship Process Overview

• The MSI Relationship attribute is located on the title block page of the item. The values are: – Buy/Sell – Indicates the part is purchased by MSI through the TMC – MSI Relationship Pricing – Indicates the part is not purchased by MSI

through the TMC, but pricing is still managed by the appropriate Category Manager

– Blank – Indicates the part is neither Buy/Sell nor MSI Relationship Pricing

• Attribute is under change control within AgilePLM – Updates to be managed by Procurement BOM Analyst through an MC – Change object routes to Category Manager(s) for approval – Attribute will be interfaced to CRIS on Item feed and to R12 through the PIP

interface


Procurement 83


MSI Relationship Process MSI Relationship Attribute


Procurement 84


MSI Relationship Process MSI Relationship Attribute Searching for Parts by MSI Relationship Attribute

Log into AgilePLM.

1. From Home page go to Custom Search.

2. Select Advanced Search.

3. Select Item, Parts, MSI Relationship and select search value from drop down menu.

4. Click Search.

Results display.


Procurement 85


6. To Export, go to More and select file type.

The file is exported.

MSI Relationship Process MSI Relationship Attribute Searching for Parts by MSI Relationship Attribute


Procurement 86


MSI Relationship Process MSI Relationship Attribute Oracle View


Procurement 87


Module Map


Sourcing Project



Procurement 88


Sourcing Project Introduction

• The Sourcing Project tracks data required to perform data analysis for effective pricing.

• The project data includes Items and Assemblies, BOMs, and AML.

• Multiple users can work as a team to complete sourcing activities.

• RFQs can be executed directly from the Sourcing Project.

• Project Lifecycle Phases:

– Draft – edit cover page attributes, item component data, attachments

– Open – the RFQ creation and supplier responses occur in the open state

– Closed – set by the Project Manager when tasks are complete


Procurement 89


Sourcing Project Specify the Price Scenario

• The two types of project price scenarios are Quantity Breaks and Effectivity Periods.

– Specify Quantity Breaks to capture prices based solely on quantities with up to six quantity breaks.

– Specify Effectivity Periods to capture prices based on future dates. The Effectivity Periods scenario also supports quantity breaks per period. Allows up to 20 price periods and six quantity breaks per period.

• Period Type values are Monthly, Quarterly, Semi-Annually, Yearly and Variable.

• The Variable Period Type requires specifying the start and end dates for each period.


Procurement 90


Sourcing Project Cover Page Fields

• Project Number (read-only)

• Description (optional)

• Lifecycle Phase

• Ship to Location (required) – MSI Global

• Project Currency (required) – USD

• Product Lines (optional)

• Number of Periods (read-only)

• Number of Quantity Breaks (read-only)


Procurement 91


Sourcing Project Cover Page Fields (cont.)

• Data to Share (optional) – includes data elements to be shared with Suppliers in RFQs generated from the project

– Settings at the project level can be overridden at the RFQ level

• Response Required Fields (optional) – includes the information required from the Suppliers in RFQs generated from the project

– Settings at the project level can be overridden at the RFQ level

• Supplier Instructions (optional)

• Owner (required) – owner responsible for the project

• Creator (read-only)

• Created Date (read-only)


Procurement 92


• Last Modified (read-only)

• Project Type (read-only)

• Authorized Users (optional) – Users authorized to work with the project

• Disallow AML Statuses (optional) – Specifies AML statuses for parts that you don’t want brought into the project

• Require RFQ Terms and Conditions – Specifies terms and conditions associated with the project

Sourcing Project Cover Page Fields (cont.)


Procurement 93


Sourcing Project Creating a Sourcing Project

1. To Create a Sourcing Project choose Create New > Sourcing Projects.

2. Select the Pricing Scenario fields, the start (effective) date and click Save.

3. Enter Sourcing Project Information and click Save.

4. Click the Edit button on the General Info tab if modification of the fields is necessary.

5. Click Save.


Procurement 94


Sourcing Project Selecting Data to Share with Suppliers

Use the Data to Share with Suppliers palette to restrict the visibility of information to the supplier.

Types of data to share include Project fields, Item and AML fields, BOM view, RFQ attachments and AML.

1. To select or modify data to share with suppliers, go to the General Information tab and click Edit.

2. Click the palette next to the Data to Share field

3. Select the checkboxes next to the fields and click Apply.


Procurement 95


Sourcing Project Requesting and Requiring Data From Suppliers

Use the Response Required Fields to request or require data. Types of data to require include Lead Time, Inventory Available, Min & Mult values, Transportation Terms, COO, EOL Date, NCNR, Valid to & from dates, Material Price and NRE 1. To select or modify response data from

suppliers, go to the General Information tab and click Edit.

2. Click the palette next to the Response Required Fields.

3. Select the checkboxes next to the fields and click Apply.


Procurement 96


Sourcing Project Sharing a Sourcing Project

Sharing is how you define the people who have access to a project. When you share, you grant one or more roles to another AgilePLM user that define the actions permitted for that project only. 1. Select Actions > Sharing and click Add. 2. Using the search palettes, select the user

names and one of the two Sourcing roles for each user.

3. To see objects which have been shared with you, click the My Settings button in the Courtesy Controls area in the left pane.

4. Click the Share tab.


Procurement 97


Sourcing Project Adding Items to a Project

1. You can add items to a project using several methods:

– Search and add items from the Item Master – Drag and drop items from your Navigator

Drawer – Copy items from a search window and paste

them into the table on the tab – Import items from an external document

such as an Excel Workbook or text file. – Note: You cannot create a BOM structure

directly in the Sourcing Project.

2. Select the Items tab or Analysis tab. 3. Click Add > Search for Items. Note: Use a wildcard, partial, or full part for the quick or custom search.


Procurement 98


Sourcing Project Importing Items to a Project

1. To import items to a Sourcing Project Items tab, select Import from the More menu.

2. Click Browse and select the Excel Worksheet you want to import

3. Select the Template Type and Worksheet. Note: Location of Header Row defaults to 1 and Location of Last Row defaults to N/A.


Procurement 99


Sourcing Project Importing Items to a Project (cont.)

4. Click Next. 5. Specify the File Content and click on

Preferences. Go to the Business Rule Tab.

6. Select “Accept Objects” for the Smart Rules Warning Violation Behavior and “All items onto the change” for the Redline Mode Behavior. Save and Click Next.


Procurement 100



7. On the Select Content Options page, select “Define attribute mapping in next step”, and “No transformations are necessary”. Click Next.

8. Specify the Attribute Mapping by highlighting the attribute in the Import Field column and clicking on the corresponding AgilePLM Field.


Procurement 101



9. Click Import and Close the Import Log.

10.When import is successful, Items from the worksheet appear on the Items tab in the Sourcing Project.


Procurement 102


Sourcing Project Updating from the Item Master

1. The content update modifies the attributes of objects from the Item Master as follows:

– BOM – updates the BOM structure – AML – resets all attributes to Item

Master values – Item attributes – updates by selected

attributes including description, commodity, UoM, as well as any flex fields

– Manufacturer part attributes – updates description and any flex fields that appear

2. Go to Items tab or Analysis tab. 3. Choose Edit > Update from Item

Master.


Procurement 103


Sourcing Project Updating from the Item Master

4. Click OK to update the content.

5. Select the All Content radio button to update all the objects or select the Selected Content radio button and select attributes manually.

6. Click Update.


Procurement 104


Sourcing Project Configuring Project Tabs

On some tabs you can select the fields to view to meet your specific needs. The default view appears when you open the tab.

1. Click Personalize to reconfigure the tab display.

– On the Sort tab you can select up to three fields by which the rows should be sorted.

– On the Filter tab you can filter information based on specific criteria.


Procurement 105


Sourcing Project Configuring Project Tabs (cont.)

You can also lock a particular column to ensure that it is always visible as you use the horizontal scroll bar.

2. Click Apply to apply the new display.

Note: Once you click Apply and go away from the current page, the applied view will be lost unless you save it. You must click Save and then Save As to save the view as a new view.

3. To format, on the Format tab select the fields that you want to view on the tab from the Hidden Fields list.


Procurement 106


Sourcing Project Configuring Project Tabs (cont.) 4. Click the arrow keys to move fields

from Hidden to Displayed and from Displayed to Hidden.

5. Use the up/down arrows to change the order of appearance of the columns.

6. To filter, on the Filter tab click the field dropdown list to select an attribute for the filter criteria. Click the search palette for a list of available values.

7. To add additional filters, click the + button.

8. Click Apply.

Note: If you want to save this filter for future use, click Save. You must then click Save As to save the settings as a new filter.


Procurement 107


Sourcing Project Modifying Price Scenarios

When a project uses the Effectivity Periods price scenario, you can remove old price periods, add new ones and reset the current period.

1. From any tab, choose Actions > Modify Price Scenarios. The Modify Periods dialog appears.

– To delete a price period, click the Delete Row - button to the right of a period’s end date.

– To insert a new price period, click the Insert Row + button to the right of the last period’s end date. Although the period is added after the last period in the project, you can specify any start or end date.


Procurement 108


Sourcing Project Modifying Price Scenarios (cont.)

2. To make a price scenario required, check the Response Required box.

3. Click OK to confirm the changes.

Note: If you delete a price period, it is deleted from the corresponding RFQ as well. If you add a price period, you have to manually add it to the RFQ.


Procurement 109


Sourcing Project Modifying Item Quantities

You can edit item quantities or quantity breaks on the Items tab or Analysis tab.

1. Select the rows of items or click the All Rows Selection cell to select all rows.

2. Choose Edit > Quantities. The Edit Item Quantities dialog appears.

3. Double-click in the field for each Quantity Break in each Effectivity Period that you want to modify and enter the new quantity.


Procurement 110


Sourcing Project Modifying Item Quantities (cont.)

Note: You can click the Fill Up or Fill Down buttons to copy the value of a Quantity Break to several selected cells in the column.

4. Click Save to update the quantities in the project.

Note: Once your changes are saved, the quantities are automatically updated through sub-assemblies and components in the project.


Procurement 111


Sourcing Project Quote as Cost Attribute

The Sourcing Project is currently configured for material price quoting only. The quoting process for non-material price is custom and may be addressed post Go-Live. Any item to be included on an RFQ should be quoted as a “Component”. 1. To change the Quote As attribute for a

single item, go to the AML tab and double-click on the item. Click on Edit, and update the Quote As attribute to Component.


Procurement 112


Sourcing Project Quote as Cost Attribute (cont.)

2. To change the Quote As attribute for multiple items, highlight the rows for the items you want to change.

3. Choose Edit > Bulk Edit Items. The Bulk Edit dialog appears.

4. Change the attribute and click OK. Note: you can change these attribute values from Items and Analysis tabs as well.


Procurement 113


Sourcing Project Adding Partners to Project Items

Partners (Suppliers) can be added to Items in the Sourcing Project or in the resulting RFQ.

1. To add partners to projects, go to the Items tab or Analysis tab.

2. Select the row of the item to which you want to add the partners.

3. Choose Edit > Partners. The Assign Partners dialog appears. Click Add.

4. Search for and select the suppliers that you want to add.


Procurement 114


Sourcing Project Adding Partners to Project Items (cont.)

5. Click Next Record to continue to edit partners for remaining items.

Note: Select the Apply to all Remaining Selected Items checkbox to assign the partner to all the selected items in the project.

6. Click Finish. The partners appear in the Partner/Supplier list.

7. To remove partners follow the same menu path and click Remove instead of Add.


Procurement 115


Sourcing Project Adding Alternate AML to a Project

The Sourcing Project allows the tracking of alternate or additional manufacturers/manufacturer part numbers that do not appear on an MSI part in the item master.

1. To add a manufacturer part to an AML in the Project (only), click on the AML tab.

2. Click on the number of the item to which you want to add an AML. The quick view window appears.

3. Select the AML tab and click Add. The Add AML to Item dialog appears.


Procurement 116


Sourcing Project Adding Alternate AML to a Project (cont.)

4. Search for the manufacturer name and add the manufacturer by double-clicking the row you want to add.

5. Enter the manufacturer part number and description. Select Alternate Status and click Finish.

Note: Select the Apply to all Remaining Selected Items checkbox to assign the partner to all the selected items in the project.


Procurement 117


Sourcing Project Setting the Target Price

You can set a target price for an item and share that price with the supplier. The target price can be different for each price scenario and/or price break.

1. To set the target price go to the AML tab or Analysis tab.

2. Select the rows of the items for which you want to set the target price.

3. Choose Edit > Target Costs. The Set Target Price dialog appears.


Procurement 118


Sourcing Project Setting the Target Price (cont.)

4. Enter the target cost for each item.

5. Click Apply. The target price is updated on the AML tab of the project.

Note: These target prices will be reflected in new RFQs. To apply these target prices to existing RFQs choose More > Update RFQ Targets.


Procurement 119


Sourcing Project Create a Request for Quote (RFQ)

• Using RFQs, you can request quotes for any items in a project and the suppliers can respond to your requests.

• There are several tabs on the RFQ:

– Cover Page – Displays general details about the RFQ

– Responses – Displays response details

– Response Status – Displays a summary of the RFQ and supplier response

– Changes – Displays item or response changes

– Discussion – Displays the discussion objects related to the RFQ

– Attachments – Displays a list of file attachments

– History – Displays a list of actions performed during the life of the RFQ


Procurement 120


Sourcing Project Creating Request for Quote (RFQ)

There are prerequisites for the Supplier object selected for an RFQ. • Required fields on the AgilePLM Supplier Object

– Maximum Number of Contact Users (entered by On-Boarding team) – Maximum Number of Licensed Contact Users (entered by On-Boarding team – Maximum Number of Named Contact Users (entered by On-Boarding team – Default RFQ Recipient (entered by Supplier Admin but can be edited by

Procurement) • Required fields on the AgilePLM Supplier User Object – General Info Tab

– Home Ship To – (MSI Global) – Authorized Ship To – (MSI Global) – User Category – (Named)

• Required fields on the AgilePLM Supplier User Object – Preferences Tab – Response Edit Mode – Advanced Table Edit (entered by the Default RFQ

Recipient User)


Procurement 121


Sourcing Project RFQ Terms and Conditions

• Users can make RFQ Terms & Conditions mandatory at the sourcing project level by selecting Yes for the Require RFQ Terms and Conditions field upon creation.

• This setting automatically applies to all RFQs created from the project.

• When a supplier opens an RFQ, the Terms and Conditions form opens with Accept and Decline buttons. If the Supplier declines, the RFQ will not open and all avenues to the RFQ are blocked.


Procurement 122


Sourcing Project RFQ Status and Symbols


Procurement 123


Sourcing Project RFQ Status and Symbols


Procurement 124


Sourcing Project Creating a Request for Quote (RFQ)

1. To create an RFQ, go to the Items, AML or Analysis tab of the Sourcing Project.

2. Select the rows of the items for which you want to create the RFQ.

3. Choose Quote > Create. The Create RFQ window appears. Click Next.


Procurement 125


Sourcing Project Creating a Request for Quote (RFQ)

4. The Enter RFQ Information page appears. Enter mandatory information:

– RFQ Description

– Due Date

5. Enter optional information:

– Data to Share

– Response Requirements

– Supplier Instructions

– Owner

– RFQ Type

– Authorized Users


Procurement 126


Sourcing Project Creating a Request for Quote (RFQ) (cont.)

6. Click Next. The Select Part Addition Rule page appears. Choose one of three options:

– Add selected items and all sub-components

– Add selected items only, without sub-components

– Add only sub-components of selected items

7. Click Next. The Select Suppliers page appears. The partners associated with the items appear under Select Partners. You may clear the checkboxes of those you don’t want to receive the RFQ.


Procurement 127


Sourcing Project Creating a Request for Quote (RFQ) (cont.)

8. Click the button next to the Suppliers field to open the search palette and add the Suppliers to receive the RFQ. Set the dissemination method to All and remove check boxes (Approved, Strategic, Manufacturer). Click Next.

9. Add attachments and click Finish.


Procurement 128


Sourcing Project Adding Items to an RFQ

After you create an RFQ you can add more items even if you have already sent the RFQ for quote. 1. Select the Items tab of the Sourcing

Project. 2. Select the rows of the items you want to

add. 3. Choose Quote > Add Items. 4. The Add items to RFQ window appears.

Select the RFQ to which you want to add the items and click Next.

5. Select the Part Addition Rule and click Next.

6. Select the suppliers and the dissemination method.

7. Click Finish.


Procurement 129


Sourcing Project Sending RFQs

RFQs are sent to Suppliers when the status is changed to Open. 1. In the Price Scenarios field, choose All

Price Scenario when there are multiple price scenarios.

2. To change the status choose Change Status > Open. The RFQ notification will be sent to the Web Suppliers. You can send out specific line items that are ready for quoting.

3. To send line items in an RFQ select the rows of the items you want to send out from the Responses tab of the RFQ.

4. Choose Response > Send Requests to Suppliers.


Procurement 130


Sourcing Project Exporting RFQs to Non-Web Suppliers

To send RFQs to non-Web suppliers, you need to export the RFQ and send it in an attachment in email.

1. To export RFQs go to the Response Status tab.

2. Select the row of the non-Web supplier to whom the RFQ should be sent.

3. Click Export > Export (.csv) or Export > Export (.xls) depending on the file type you want to export.

4. Click the Save button to download the file.


Procurement 131


Sourcing Project Supplier Responding to RFQs

Once the RFQ is changed to the Open status, the selected Supplier will receive the notification in their Notifications tab.

1. To access the RFQ the Supplier clicks on the hyperlink of the RFQ. The RFQ opens to the cover page.

2. Supplier selects the Responses tab and double clicks on each field for which a response is requested.

3. Supplier enters responses.

4. Supplier clicks Save to save entries.

5. Supplier can submit the quote by selecting the Submit button, or clicking on Responses > Submit.


Procurement 132


Sourcing Project Supplier Responding with Alternate Proposals

The Supplier has the option to offer an alternate part through the RFQ process.

1. To enter an alternate part, go the Responses tab and select Propose Alternate Part.

2. Supplier enters the alternate part number, description and manufacturer and clicks Continue.

3. Supplier enters requested data such as lead time, inventory available, cost data, etc.

4. Supplier clicks Save to save entries.

5. Supplier submits the quote.


Procurement 133


Module Map


Sourcing Project



Procurement 134


Searches and Reports Introduction

There are several Custom Searches and Reports available to Procurement.

Benefits of the Searches and Reports include:

• Elimination of Steps to execute custom searches

• Push of information useful to the SCT and Procurement teams without having to run reports ad hoc

• Reports are customized to contain just the information relevant to the user.

• Improved collaboration with Engineering teams when information is readily available to the user


Procurement 135


Searches and Reports Introduction (cont.)

• Custom Searches

• Item Search by Commodity Code – Used to obtain a list of parts for one or more commodity codes

• Approved Manufacturers by Commodity – Used by multiple functional organizations to obtain of list of ASL (CRIS) Manufacturers by Commodity (covered in Determine Sourcing Requirements)

• Request for Information Search – Used to obtain a list of RFIs by Supplier within a specified date range

• Product Readiness Report – Used by multiple functional organizations to assess Product Readiness associated with a New Product Introduction


Procurement 136


Searches and Reports Introduction (cont.)

• Reports:

• Weekly PPL/ASL Changes Report – Pushed to Procurement teams to alert them to item updates associated with PPL and ASL Ratings and Compliance

• Released to Production Report – Pushed to Procurement teams to alert them to items that have been released to the Production lifecycle status

• New Parts Created/Lifecycle Changes Report – Pushed to Procurement teams to alert them to new parts that have been created and a summary of lifecycle changes to the parts within their Commodity


Procurement 137


Searches and Reports Custom Searches Performing an Item Search by Commodity Code

1. To search for items by Commodity Code, go to Procurement Searches under Global Searches.

2. Select Item Search by Commodity Code.

3. Click in the entry box to search for the Commodity Code. Double click on the selected Commodity Codes.

4. Select Run.

5. To export results, select More and choose the export format.


Procurement 138


Searches and Reports Custom Searches Performing a Request for Information Search

1. To search for RFQs, go to Procurement Searches under Global Searches.

2. Select Request for Information Search.

3. Enter the Suppliers and Due Date range that you’re searching.

4. Select Run.

5. To export results, select More and choose the export format.

6. Click on the hyperlink to the RFI to access it directly from the search screen.


Procurement 139


Searches and Reports Product Release Readiness Report Running a Product Readiness Report

To run the Product Release Readiness Report:

1. Go to the item record for which you want to run the report.

2. Choose Product Readiness report from the Actions menu.

Results are sent to the requestor via email.


Procurement 140


Searches and Reports Product Release Readiness Report Example


Procurement 141


Searches and Reports Product Release Readiness Report Example (cont.)


Procurement 142


Searches and Reports Product Release Readiness Report Example (cont.)


Procurement 143


Searches and Reports Product Release Readiness Report

• ASL Rating % = (Unique Supplier Count for ASL Rating = “Approved”)/((Unique Supplier Count for ASL Rating = “Approved”) + (Unique Supplier Count for ASL Rating = “Not Approved”)), and it would only count “Not Approved” suppliers if they are the only supplier for that given part.

• PPL Rating % - Total # of Unique items = “Approved”/Total # of Unique items “Approved” + # of Unique items “Not Approved”. (Not scored parts are not included in the calculation).

• ASL Compliance % - Calculated as the number of Unique “Approved" items divided by the total number of Unique items where the commodity code is not = to N/A or internally manufactured.


Procurement 144


Searches and Reports Product Release Readiness Report (cont.)

• Single Source % - Total # of Unique items that = Y (single Source) divided by total # of Unique items where the commodity code is not = N/A or internally manufactured.

• End of Life % - Total # of Unique items without an active mfr part on the AML divided by total # of Unique items where the commodity code is not = N/A or internally manufactured.


Procurement 145


Searches and Reports Weekly PPL/ASL Changes Report


Procurement 146


Searches and Reports Released to Production Report


Procurement 147


Searches and Reports New Parts Created/Lifecycle Changes Report


Procurement 148


Searches and Reports New Parts Created/Lifecycle Changes Report


Procurement 149


Module Map


Sourcing Project



Procurement 150


Summary • A unified item numbering strategy and parametric attributes offer the

following benefits:

- Consolidated, unified part numbering schemes across MSI promotes commonality and reuse.

- Item sub-class driven auto-numbering capability offers a semi-significant part number scheme.

- Finer granularity classification moves common information from the description into searchable parametric attribute fields.

• Procurement activities are performed during specific Project Lifecycle Phases

• Aligning Commodity Codes to Category Strategies provides visibility and allows collaboration with Engineering on the Manufacturer Table and AML Maintenance.


Procurement 151


Summary (cont.) • Commodity Code objects in AgilePLM provide capability for automated

notifications and approvals through the use of Procurement User Groups.

• AgilePLM Manufacturer requests ensure Procurement is notified of collaboration between Engineering and new Manufacturers.

• AgilePLM Discussion Objects help to manage communications between MSI engineers, Procurement and Suppliers when gathering information about specifications.

• Relationships created between the Items and Discussion Objects are stored in AgilePLM.

• Supplier Objects enable Partner Access to AgilePLM.

• A Supplier Administrator will be created for each partner / supplier, who will manage the individual supplier user accounts for his/her company.


Procurement 152


Summary (cont.)

• Suppliers and MSI users can email [email protected] for assistance with Partner Access to AgilePLM.

• Sourcing Requirements include the CRIS ASL, AML Maintenance, Manufacturer Maintenance, Partner Access, ASL Ratings/Compliance, PPL process, and the MSI Relationship Attribute.

• The Sourcing Project provides a vehicle for performing data analysis for a New Product and for executing Requests for Quote (RFQ) to ensure effective pricing.

• Searches and reports for Procurement use are available for ad hoc use and group distribution.

mailto:[email protected]