USING AGILE – SOFTWARE ENGINEERSlearningmedia0.motorolasolutions.com/services/edu/meridian/Employee... · linkage or information in VTRACK 3PSA and proceed to make any BOM changes

GNL1147.00E - Using AgilePLM in MSI August 2013

Using Agile PLM– Software Engineers

1

Internal

Using AgilePLM in MSI USING AGILE – SOFTWARE ENGINEERS

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.



2

Internal

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

Objectives

• Create a new software part.

• Discuss when sourcing requirements would be required for a Software Part and what AgilePLM Item attributes would indicate the need for AML.

• Create a new software license.

• Create a new software BOM.

• Create an EC to release the new software part to ERP.

• Create an EC to PRODUCTION Release and add new Software Item to overall Product Structure.



3

Internal

Module Map

Introduction

Create Software

Software License and SW BUY Items

Software Parent Item

BOM

EC to RELEASE TO ERP

Structure/Modify

PRODUCT BOM and Update SW ITEM to Production Release



4

Internal

Introduction Software Release Process Architecture



5

Internal

Module Map

Introduction

Create Software



BOM


Structure/Modify




6

Internal

Process Flowchart

First, determine if this should be a new software release or a

software update.



7

Internal

Software Topics Overall Process Steps

1. Create a new software part.

2. Determine the sourcing requirements (if required).

3. Create a new software license (if required).

4. Create a new software BOM (if required).*

5. Prepare the software binaries and create any relevant documents. (Outside AgilePLM).

6. Create an EC to release the new software part to ERP (if required).

7. Create an EC to PRODUCTION RELEASE and add new Software to Product.

* NOTE – If in LEGACY O11i – Push the ITEM to ERP on an EC PRIOR to adding BOM.



8

Internal

Creating New Software Create a new software part number

Log in to the AgilePLM system (https://agileplm.motorolasolutions.com).

https://agileplm.motorolasolutions.com/



9

Internal


Click Create New > Items > Parts.



10

Internal


Select Software as the part Type.



11

Internal


Enter the attributes of the new part in all the mandatory fields (denoted by *) and click Save.

Note: The SW ITEM Number can be manually entered.

Note: Clicking Save will result in an error if any of the mandatory fields are left blank. IMPORTANT! Utilize Caps Lock when manually entering item attributes. UPPER CASE entries are mandatory for the description fields.



12

Internal


FROZEN In AgilePLM – NO ALWAYS NO



13

Internal

Create a new software part number

Creating New Software

Other SW Fields that are CRITICAL:

U of M: Use FR for SW Loaded by Factory -- EA for SW that needs to be "Counted" in inventory.

General Description: This text field (CAPS REQUIRED) is where you record the VERBAL Description of the SW.

Contains Encryption: For SW will not DEFAULT - the Item Creator must set this field.

Software Type: Please set this field to the appropriate value.



14

Internal


When successful, a new software part number is created.



15

Internal

The attribute values are dependent on the Software Type selected.

For example:

Software Type: Royalty Software Type: Firmware

U of M: EA U of M: EA

Design Source: Off-the-Shelf Design Source: MSI Custom

Oracle Item Type: Buy Oracle Item Type: For Reference

Legacy Attributes:

AF UOM = FR

OT UOM = FR




16

Internal

The most commonly used Software Types are listed below.

1. Software – For MSI developed application software

2. Firmware – For MSI developed firmware

3. Royalty – Often tied to purchased software and licenses

4. Purchased Software

The least commonly used Software Type is Development. Selecting Development as the Software Type should be avoided if the part would later be added to a shipping product.

For more information on the attribute values and software types, please see your site coordinator.




17

Internal

Creating New Software Cloning an existing software part number

1. Search for a current software item using the search text box. You can use the part number or description for the search criteria.

2. The result will appear in the Search Results window. Click the Item Number to open and view the current item. Ensure the item is similar to what you need.

WARNING! Do not use an item that is not similar to what you desire if you choose to clone.

3. In the items page, select Actions > Save As. The software attributes page will appear with the attributes of the existing item will be filled in.

4. Modify the attributes where necessary. Click 123 > Software Number to auto-generate a new software part number, If desired type your own number. Click Save.

IMPORTANT! Ensure that all tabs and fields of the cloned item are checked and modified to prevent the wrong information from being submitted.

5. When successful, a new software part number is created.



18

Internal

DEMO – Creating a Software Item

Now let’s take a look at the AgilePLM tool:

https://agileplm.motorolasolutions.com




19

Internal

Module Map

Introduction

Create Software



BOM


Structure/Modify




20

Internal

Process Flowchart

Next, check if any software license or royalty is required.

The sourcing requirements of the new software part has

been determined.



21

Internal






5. Prepare the software binaries and create any relevant documents. (Outside AgilePLM)


7. Create an EC to PRODUCTION RELEASE and add new Software to Product

* NOTE – If in LEGACY O11i – Push the ITEM to ERP on an EC PRIOR to adding BOM



22

Internal

If the SW is a BUY ITEM TYPE Determine the sourcing requirements

• For purchased software parts, ensure that the following attributes are correct: U of M = EA, Design Source = Off-the-Shelf (typical), Oracle Item Type = Buy.

• If the new software part is a purchased software, we will need to determine its sourcing requirements.

• Follow the procedures shown in the Creating Manufacturer and Manufacturer Parts module to determine the sourcing requirements of your purchased software.

• ALM Information will need to be added for any BUY Software Item



23

Internal

Creating New Software License/Royalty If there is a License/Royalty requirement - Create a new software license/royalty or update an existing software license/royalty. The initial Item Create Process is the same – the values are different

U of M = EA, Design Source = Off-the-Shelf, Oracle Item Type = BUY

Commodity Code = Software - License or Royalties



24

Internal

Creating Software License/Royalty In the Title Block tab, complete all the necessary and mandatory attributes in the SOFTWARE DETAILS section and click Save.

If a license key is required, select Yes.

Then proceed to update VTRACK 3PSA with the information required.



25

Internal

Cloning Software License/Royalty

If you wish, you may also clone the attributes of an existing software license/royalty in AgilePLM.

WARNING! Do not use a part that is not similar to what you desire if you choose to clone — if you are cloning to make a software royalty, only use another software royalty — preferably one from the same product line as the one you need.

1. Search for the existing software license/royalty using the search text box. The Search Results will result in the page of the software license/royalty queried.

2. Select Actions > Save As. The software license/royalty attributes page will appear with the attributes of the existing software license/royalty.



26

Internal

Cloning Software License/Royalty

3. Modify the attributes of the existing software license/royalty where necessary. Click 123 > Software Number Royalty to auto-generate a new software license/royalty part number. Click Save.

4. When successful, a new software license/royalty is created.

IMPORTANT! Ensure that all tabs and fields of the cloned item are checked and modified to prevent the wrong information from being submitted.



27

Internal

If you want to update the attributes of a software license/royalty item that is no longer in the Preliminary phase of its lifecycle, you will need to raise an EC or an MC.

Once the EC has been submitted, you may then proceed to update VTRACK 3PSA with the information required.

Updating the License Key Attributes - Software License/Royalty



28

Internal

1. On the item page, click Edit to update the item attributes. Click Save when you are done.

2. Click Back or click the EC link in your Recently Visited list to return to the EC or MC.

Updating the License Key Attributes Creating a New Software License/Royalty



29

Internal

Reusing an Existing Software License/Royalty To reuse an existing software license, you may immediately update the linkage or information in VTRACK 3PSA and proceed to make any BOM changes if required.

An EC is required to add the current software licenses to other product BOMs if required.

For the details on updating an ERP released BOM with an EC refer to the information in the section Structure/Modify Product BOM and Update SW Item to Production Release.



30

Internal

Module Map

Introduction

Create Software



BOM


Structure/Modify




31

Internal

Process Flowchart

The BOM and the software binaries are

ready.

Prepare any relevant documents such as

release notes, factory checklist, and

specification sheets.

Determine if the created software part is in ERP.



32

Internal












33

Internal

Creating a New Software BOM Once the new software part has been completed, determine if you need to structure a BOM on that new Software Item. (Child items that are under the new SW parent item)

Concurrently, you can also begin to prepare the software binaries (that is, for the silver and archive binaries).

See the Managing BOM module for additional information related to BOMs overall.



34

Internal

For LEGACY O11i items – Add the BOM child items AFTER the initial EC has made the item exist in the Legacy ERPs

1. From inside a New EC, HIGHLIGHT the Affected Item ROW

2. Select the BOM TAB at the bottom of the screen

3. Ensure the View is showing the following fields: ERP Org Mfg Sites/DC QTY

Creating a New Software BOM



35

Internal

For LEGACY O11i items

4. DRAG and DROP or ADD the child items

5. Add appropriate VALUES the following fields: ERP Org -- Where you want the part to exist as a CHILD for this

parent QTY

6. Look closely at Mfg Sites/DC – IF you are adding an ERP Org that is not already on the Mfg Sites/DC list – STOP. The child must already exist at the site before you add it to a BOM for that site. Do an additional EC to set the child up at the site prior to proceeding to create the BOM.

Creating a New Software BOM



36

Internal

Creating a New BOM or Updating an Existing BOM For Trilogy – (Item not yet on an EC and still in Preliminary State)

1. Select the BOM TAB on the ITEM.

2. DRAG and DROP or ADD the child items.

3. Add appropriate VALUES the QTY field. In Trilogy the BOM will be added to ERP at the same time the item is.



37

Internal

Creating a New BOM 5. From the new Software Item - Click on the BOM tab.

6. Click Add and search for the part number(s) you wish to add to the BOM.

Tip: You can also use the Drag and Drop function or the Copy and Paste function described in the tips section.



38

Internal

Creating a New BOM Repeat steps 4 and 5 until all the required part number(s) are added to the BOM structure.



39

Internal

Creating a New BOM Remember to verify the item quantity for each child item you add to the BOM. Double-click the Qty field to change the value.



40

Internal

DEMO – Building a Software BOM






41

Internal

Module Map

Introduction

Create Software



BOM


Structure/Modify




42

Internal

Process Flowchart

.

The EC has been approved and completed.



43

Internal









* Note – If in LEGACY O11i – Push the ITEM to ERP on an EC PRIOR to adding BOM.



44

Internal

EC Releasing the Item to ERP To release an item to the ERP system, we will need to promote the item to at least the Development phase of its Item Lifecycle.

This promotion can be accomplished by raising an EC.

Once the EC is approved and completed, the software part will automatically exist in the ERP system.



45

Internal

EC Releasing the Item to ERP Create an EC and promote the software part to either the Development, Prototype, Pilot, or Production phase (Trilogy Only to Production).

Prior to the completion of the EC - the ERP specific Information must be added to the New Software Item.

Note:

• If the Software is to be built and used in the LEGACY O11i Systems the following fields are required:

APC, Legacy 11i Item Type, Legacy Item Status, Legacy U of M, Mfg Sites/DC, Responsible Location, Class Code, Global BOM

• Release the ITEM without BOM to Legacy ERP then ADD the BOM on a SECOND EC once the first is COMPLETE.



46

Internal

EC Releasing the Item to ERP Locate your Software item number.

Recommended step: Click on the Changes tab. Ensure that there are no open EC(s) in the Pending Changes section. Any EC(s) listed here should be completed before you proceed.

Note: Contact the PLM Team / Change Analyst if you see an EC that is not listed as complete. That EC MAY be blocking the EC you now are doing and special processes may be needed to resolve this.



47

Internal

Select: Actions>Create New> Changes. Select EC Process as the change order Type.

Note: Using this method instead of the Create New > Changes > Change Orders method will ensure that the EC is created with the item automatically included in the Affected Items tab of the EC.

EC Releasing the Item to ERP



48

Internal

Enter the attributes of the EC work order in all the mandatory fields (denoted by *).

Enter/Select the appropriate Change Category, Description of Change, and Reason For Change and click Save.




49

Internal

Note: If you are in Government: Product Line = GOVT

For Non Ship Accepted PRODUCTS or MAIN LINE RELEASES: Change Category = New Product Introduction

For Ship Accepted PRODUCTS: Change Category = Maintenance of Line

The field Project Name: It will help the reviewers determine change context --

**Project Name Field Example: A7.16 or FCCB 123 or SS4456 will be helpful to quickly give approvers information that is valuable to them.




50

Internal

Product Family- Locate the Product Family by selecting from the list.

Affected Design Function – This is another palette button.

** You can select multiple choices from both of these fields.

Note: Approvers will be added according to these choices.




51

Internal


Select the remaining attribute fields and click Save. (Workflow – EC Process, Affected Design Function(s) – Software)



52

Internal

Click on the Affected Items tab. • Lifecycle Phase field - Change to

Development, Prototype, Pilot, or Production. The software part needs to be promoted to at least the Development phase of its lifecycle to be released to the ERP system.

• New Rev field – For pre-Production (DEV, PROTO, PILOT), use the next available double digit number (01, 02, 03). For Production release, use the next available alphabet (A, B, C).

• Previous Rev Valid to Date field - Set to the next day.

• Effective Date field - Set to the next day.

• Shift Date field - Set to Yes if it is not.

Click the Number link of the Software Item to get to the new version of the Item.




53

Internal

EC Releasing the Item to ERP - Attachments Attachments are REV SPECIFIC

You will need to RE-ADD attachments each time you do an EC.

For the FIRST EC going to Legacy O11i - the SPEC and RRR attachments for Software Items are NOT Required.

You need to add them when you are changing the REV to PRODUCTION.

For all ENCRYPTED SW:

Either add an attachment related to the type of Encryption

Or fill in the NOTES Section in the IMPORT/EXPORT section of the ITEM to assist the ECCN Classifiers



54

Internal

From the EC click the Software Item in the Affected Item section. This opens the new revision of the software.

In the Software Items page, click on the Attachments tab. Upload or hyperlink the latest version of the software and its supporting documents (if any).

EC Releasing the Item to ERP - Attachments



55

Internal

Recommended step: Before submitting any EC work order to the Change Analyst, run the Audit Status and Audit Release to check for any errors.




56

Internal

Click Next Status to send the EC to the Change Analyst and invoke the workflow for the EC.

Note: PCM from user to user groups. Then type change into the search criteria and you will get the change analyst user group.

Click Continue to proceed.




57

Internal

The Change Status to Submitted window appears with the default Change Analyst notified. Note: This step does not add approvers for your EC work order. Add comments for any special instructions to the Change Analyst(s). Click Finish to submit the EC to the Change Analyst(s) for approval.




58

Internal

Select the Workflow tab to follow the progress of your EC work order. Once it has been approved by all approvers, the Item will be released, and the EC is completed.




59

Internal

DEMO – EC






60

Internal


Once the Initial EC is approved and completed, the software part will exist in the ERP system.

• We can then proceed to

– Add BOM for Legacy O11i Items and Change Legacy Item Status Fields

– Perform any Required Factory Software validations, RRR Preparation, etc.

– Perform the PRODUCTION RELEASE EC

Note: If the software part is already in at least the Development phase (i.e. already in ERP), you may proceed.



61

Internal

Module Map

Introduction

Create Software



BOM


Structure/Modify




62

Internal












63

Internal

Introduction • A software item can be loaded into a physical product in different ways.

For example, Test Systems can add it, a PROM programmer can add it, A CD-ROM can be inserted into a disk drive, and some software can be downloaded over the Internet.

• If a factory is going to load it, it needs to be on a BOM.

• A simple example of a software BOM could be the software itself, a CD-ROM, and a polycarbonate clear CD sleeve. That CD-ROM part number could be a sub-part in a larger product BOM.

• A Software part can be structured to the level of the overall product BOM where a Test System loads it.

• A blank PROM and the software could be part of a software assembly that is a part in a larger shipping BOM structure.



64

Internal

Process Flowchart

This demonstrates the New Software Item full release and adding this software to the overall product structure.



65

Internal

Structuring the Software to the Product BOM If the software BOM affects the product BOM, we will need to structure the software BOM to the product BOM.

This can be done in the same step as Production Lifecycle for the new Software item.

Follow the procedures shown in the Managing BOM module for additional information.



66

Internal

Structure a Software to an Existing Product BOM At times you will need to make changes to a BOM that has already been released to ERP.

To modify any BOM that has already been released to ERP, you will need to raise an EC.

There are two methods to modify a BOM in an EC. You can either add the affected items manually, or use the BOM Bulk Change Wizard. The next few slides will illustrate the BOM Bulk Change Wizard method.



67

Internal

Structuring Software to an Existing Product BOM The steps illustrated in the next few slides are summarized below.

1. Find the part you are replacing (typically the software part that needs to be replaced).

2. Find the replacement part (typically the new software part that you had just created).

3. Note down the part numbers in a separate document, or click on the part numbers so that they appear in the Recently Visited list.

4. Create a new EC.

5. Open the BOM Bulk Change Wizard from the EC.

6. Copy and paste the part numbers into the appropriate fields in the Wizard.

7. Complete the Wizard and verify the changes in the EC.



68

Internal

Structuring Software to an Existing Product BOM Search for your new software item and the part you are replacing. Take note of the two part numbers in a separate document or click on each part to list them in the Recently Visited list.



69

Internal

Select Create New > Changes > Change Orders.

Structuring Software to an Existing Product BOM



70

Internal

Select EC Process as the change order Type. Fill up the attributes of the EC work order in all the mandatory fields (denoted by *). Ensure that the appropriate Change Category, Description of Change, and Reason For Change are selected (see the example on the right) and click Save.

Structuring Software BOM to an Existing Product BOM



71

Internal

In the Cover Page tab, verify the attributes shown and ensure that the appropriate Reason Code is selected (see the example below). Once done, click Save.




72

Internal

Select the Affected Items tab. Click Bulk Change > BOM to run the BOM Bulk Change Wizard.




73

Internal

In this example, we will be replacing an item on multiple assemblies. Select Replace an item on multiple assemblies and click Next.

Copy the part numbers saved into the Item to Remove and the Replacement Item fields and click Next.




74

Internal

The Wizard will display all assemblies that the item to be replaced exists on. Select the assembly(ies) on which to replace the item and click Finish.

Note: If you obtain a WARNING, you will need to return to the BOM parent item and verify that there are no pending changes. Click the Pending Changes tab. Any ECs not listed as Complete must be closed before you proceed any further.




75

Internal

The Wizard will close and return to the Affected Items tab. Select the BOM parent item and click BOM in the table below. Verify that the changes (redlines) have been made.




76

Internal

Tips and Reminders Structure a Software BOM to an Existing Product BOM

Click the Redlined Icon ( ) to get the items that were redlined to appear at the top of the list



77

Internal


Remember to update the quantity(ies) of the item(s) you are replacing in the BOM. The BOM Bulk Change Wizard assumes that there are no changes to the item quantity(ies).



78

Internal


If the item you are adding is not in a correct lifecycle phase for the BOM you are adding it to, you can update the lifecycle phase on the same EC. Ensure that it is also added to the Affected Items section of the EC as a separate line with the updated lifecycle phase.



79

Internal


If the item you are adding is also getting a lifecycle change — ensure that the attachments are on this new revision.



80

Internal


If the item you are removing should also be turned pending obsolete/obsolete — you can update the lifecycle phase on the same EC. Ensure that it is also added to the Affected Items section of the EC as a separate line with the updated lifecycle phase.



81

Internal

Recommended step: Before submitting any EC work order to the Change Analyst, run the Audit Status and Audit Release to check for any errors. Also run PRE PIP for Trilogy and PRE MOI for LEGACY. Submit your EC as demonstrated earlier.




82

Internal

Updating Released Software In certain product non-mission critical products (e.g. PCR), if the software change is a minor non-functional change, those team opt to for an update of the released software instead.

The released software update procedure is very similar to the release new software procedure, except that you will skip the create new software part, determine the sourcing requirements, and create new software license steps.

The next slide summarizes the steps required to update a released software in a flowchart.



83

Internal

Updating Released Software Process flowchart

First, determine if this should be a new

software release or a software update.

If it is a minor non-functional change, skip the create item,

determine sourcing requirements, and software license steps and proceed straight to prepare the

software binaries.

Proceed with the same steps as discussed earlier in the Release a New Software section.



84

Internal

Updating Released Software • A new updated Rev may also be required if for some reason the

attachments are not added to the software item correctly or if prior to the RRR Release/Factory Cutover an additional build is done that would change the software item specification.

• If this is required, you may follow the steps discussed here as well.



85

Internal

Modifying a Released Software Item • The steps to modify a released software BOM is similar to the steps to

discussed earlier.

• You will need to raise an EC, and Add the affected Software item to the Affected Items tab.

• Make whatever changes are required to the Software Item – Update Fields – Values BOM – Attachments, etc.

• Submit the EC.



86

Internal

Updating Released Software Create an EC to Release the Updated Software Part to ERP

When you are creating an EC to release the updated software part to ERP remember to uprev the item revision in the Affected Items tab.



87

Internal

Click on the Attachments tab. Upload or hyperlink the latest version of the software and its supporting documents (if any).

Updating Released Software Create an EC to Release the Updated Software Part to ERP



88

Internal

Tip: Adding Attachments from Previous Revisions by Drag and Drop

When updating a released software, remember to also attach or hyperlink the RRR document and approvals. If the RRR document and approvals are still applicable for this release, you can add the attachment from the previous revision.

On the item page, click Rev to see a drop down list of the previous revisions. Click on the last complete revision.

On the item page, click Rev to see a drop down list of the previous revisions. Click on the last complete revision.



89

Internal


In the Attachments tab, click on the Folder Number link. The folder number will be automatically listed in the Recently Visited list.



90

Internal


Click Back to return to the software item.

3. Click Rev again and return to the latest revision of the software object.



91

Internal

Drag the folder from the Recently Visited list and drop them into the latest revision of the software item.

The cursor becomes a number, indicating the number of objects you are dragging. Click just to

the left of an object link to select it.

Drag the selected objects onto the table in the content pane.




92

Internal

Note: You can also use this method (drag and drop) if the attachment covers multiple software items. To speed up your work and reduce errors, ensure that all the affected software items are in the Recently Visited list first.

Tip: Adding Attachments to Multiple items by Drag and Drop



93

Internal

You can also choose to bookmark items that you return to frequently. Bookmarked items will appear in the My Bookmarks list. You can click an item bookmark to quickly display that item.

1. Open the item.

2. From the Actions menu, choose Bookmark.

3. You can change the Name and/or select a folder to store the Bookmark.

4. Click Save to save the bookmark in the highlighted folder.

Tip: Using the My Bookmarks List



94

Internal

Tip: Adding Items by Drag and Drop

You can then drag child items from My Bookmarks and Recently Visited lists and drop them into the BOM item.

The cursor becomes a number, indicating the number of items you are dragging.

Click just to the left of an object link to select it.

Drag the selected items onto the table in the content pane.



95

Internal

Tip: Adding Items by Using Copy and Paste

You can copy child items to paste from the My Bookmarks and Recently Visited lists, or you can copy child items to paste from any items tab table.

In the tab More menu, choose Copy or Paste to use this function or just use the shortcuts Ctrl + C or Ctrl + V.



96

Internal

Structuring a Software BOM BOM Mass Load

• There are two methods to structure a BOM in AgilePLM — Manually (Drag and Drop/Add) or using the BOM Mass Load Template/Tool.

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

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

• Typically there are only two fields to update on a child of a software BOM - the child item and the quantity for the child item.

Note: For more information on the BOM Mass Load Template/Tool see the Managing BOM Module. This typically does not happen for a Software Item.



97

Internal

Software License Additional Info ENS-ES

Documents

USING AGILE – SOFTWARE ENGINEERSlearningmedia0.motorolasolutions.com/services/edu/meridian/Employee... · linkage or information in VTRACK 3PSA and proceed to make any BOM changes