using agileplm in msi - motorola solutionslearningmedia0.motorolasolutions.com/services/edu/... ·...

GNL1147.00E - Using AgilePLM in MSI August 2013

Using AgilePLM – Mechanical Engineers

1

Motorola Solutions Internal

Using AgilePLM in MSI Using AgilePLM – Mechanical 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


Introduction Objectives, Enhancements, & Process Map



3


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

Objectives:

• Synchronize Windchill drawings to AgilePLM Document objects using the new AgilePLM-Windchill Interface.

• Rename Windchill drawings through the new AgilePLM-Windchill Interface.

• Publish secondary content from Windchill to AgilePLM using Windchill Baseline functionality.

• Manage an open EC, triggered by the new AgilePLM-Windchill Interface using Windchill Baseline functionality.

• Release a Windchill Drawing using a Windchill Promotion Request to publish secondary content to AgilePLM using new AgilePLM-Windchill Interface.



4


Enhancements:

– Reduces the effort required of Windchill Product Managers to rename Creo databases.

– Centralizes the storage location of intercommunications between suppliers and MSI.

– Tooling iterations are archived and under revision control in AgilePLM.

– Greatly reduces the effort required of Windchill Promotion Approvers to manage Windchill Promotion requests.

– Important PLM attributes are now available within Windchill

– Important Windchill attributes are now available within AgilePLM.



5


Process Flow: SUPPLIER COLLABORATION



6


USE CASES Use Case Descriptions / Overview



7


Use Case Descriptions/Overview USE CASE 1

• Users will be guided to create new Part and Document numbers in AgilePLM, similar to Item Creation process.

USE CASE 2

• Users will be guided to synchronize AgilePLM Documents to Windchill Drawings. Users will also be shown how to rename the Windchill Drawing with the proper nomenclature.

USE CASE 3

• Users will be guided to publish secondary content through Windchill baseline functionality.



8


Use Case Descriptions/Overview USE CASE 4

• Users will be guided to manage open ECs triggered by a Windchill baseline (as shown in Use Case 3).

USE CASE 5

• Users will be guided to perform design iterations using the approach taught in Use Case 3 and 4 in Pre-Production.

USE CASE 6

• Users will be guided to create a Windchill Promotion Request to release Windchill Drawings to AgilePLM for the introduction into Production and Post-Production.



9


USE CASE 1 Create AgilePLM Part and Document Objects



10


UC1: Create AgilePLM Objects Pre-requisite for test environments

• Register a new server in Windchill to execute all PBT MCAD trainings

• Server address: https://intralinkdev.mot-solutions.com/Windchill

• Log into Windchill Development server and create a new workspace named PBT_Test. Select the folder specified by your test lead as your context folder.

• Create a new part and drawing in Windchill. You will use these Windchill items throughout the entire testing.

• Checked-in Drawing into the Commonspace (in the Development Server).



11


UC1: Create AgilePLM Objects Creating Required Part Number(s) in Preliminary Phase

1. To create a new part in AgilePLM, click on Create New > Items > Parts.

2. Select the type of parts to create from the drop-down list > Housing.

3. Subsequently, complete all the required fields. Under the Number field, try clicking on the 123 button. There are two options; Housing Number or Housing Number Chassis. Select Housing Number.



12



4. Fill in the remaining fields per your Design Center recommended values. For example:

• Product Line (s): GOVT • Classification Code: Plastics – 1 Shot • Owner: ASTRO Subscriber ME DE NPI Portable • Design Source: MSI Custom • APC: 455 • Housing Type: Housing Type: (MSI) > Assembly, Housing

Click on SAVE once completed.

5. A new AgilePLM Part number has been created – HNxxxxxxA01

(e.g. HN000097A01) • As duplicate object numbers are not allowed in AgilePLM, each tester will create their own unique part number. •Highlight and copy the family number of the part number that was just created. i.e. HNxxxxxxA. (e.g. HN000097A)



13



6. To create a new Document number in AgilePLM for the above part, click on Create New > Items > Documents.

7. Select the type of documents to create > Document. 8. Fill in the remaining fields per your Design center

recommended values. For example: • Product Line(s): GOVT • Owner: ASTRO Subscriber ME DE NPI

Portable • Document Type: Drawing

9. Click on SAVE once completed. • A new AgilePLM Document number had been

created using the family number i.e. HNxxxxxxA (your Part No. without the expander).



14



10. Lastly, Create a relationship between the part object and the document object. This is required to eliminate the need to search in AgilePLM for the drawing when you are viewing the part object.

• Open the relationship tab of either the document object or the part object.

• Click the ADD button • Search for the housing object or the

document object respectively and double Click to make the relation.



15


USE CASE 1 Exercise



16


USE CASE 2 Synchronize and Resynchronize

AgilePLM Documents and Windchill Drawings



17


• AgilePLM-Windchill Synchronization is required to keep the revisions of items in AgilePLM correlated to the corresponding Windchill item’s revisions.

• Synchronization is required to provide a path for the secondary content from the Windchill drawing to be published to the associated AgilePLM document.

• Synchronization is required so attributes can be passed from Windchill to AgilePLM and vice versa.

UC2: AgilePLM-Windchill Synchronization Synchronization Details



18


UC2: AgilePLM-Windchill Synchronization AgilePLM Document and Windchill Drawing

1. Search for your new Document object in AgilePLM • Enter your Document object name

in the Quick Search window located at the top right corner.

• In the Search Results window, Double click on your document object.

2. Synchronize the AgilePLM Document

object to the Windchill Drawing: • Click the Windchill Sync Link

under the Actions menu



19



3. In the AgilePLM-Windchill Synchronization window, search for your Creo drawing that you would like to have synchronized. Remember the asterisk (*) is a wildcard search.

4. Select on the Windchill drawing to be synchronized. Click on the hyperlink under the search results to launch the Synchronization tool on the Selected Item.



20



5. A new window will appear to confirm the AgilePLM/Windchill objects to be synchronized. • Verify that AgilePLM object and the Windchill item are correct. • If not, Click Cancel and repeat steps 3&4, If they are correct

go to the next step.



21



6. Rename the Windchill Drawing: • Check the Rename Windchill Item box

7. To match both the part name and the part Number to the Part File name, as per MSI Windchill Naming convention: • Check the Keep New Fields In Sync with File Name box

8. Enter the new file name in the Windchill File Name window. 9. Click on Confirm. Reminder: The MSI Windchill convention for family prints is

<FamillyNumber>_<Description>.drw e.g. HN000097A_MAIN-HSNG.drw. Note: maximum of 31 characters



22



10. A new popup window, Agile-Windchill Synchronization Results, will appear to display the outcome of the Synchronization. • Close this popup by clicking the x-box icon in the upper right corner. • Close the Agile-Windchill Synchronization window by clicking the close

button

11. In AgilePLM, click on the Refresh icon to retrieve the updated details of your part.



23



12. Click on the Title Block tab 13. Click on the Windchill Hyperlink to take you to the Windchill section in

the Title Block tab. Note: The information that was pulled from Windchill and now available be viewed in AgilePLM. This information validates that the document object and the Winchill drawing was synch’ed



24


UC2: AgilePLM-Windchill Synchronization AgilePLM Document and Windchill Drawing 14. In Commonspace, search for your original “.prt” file and rename it

following the MSI Windchill naming convention. NOTE: Users may not have privileges to rename in Windchill, contact the

Windchill Product Manager to have the remaining files renamed.

15. Type in the correct file name in all three name fields.



25



16. In your workspace, you will find an error icon on your drawing and part files because of the renames. • Click on Tools > Synchronize to synchronize the names as shown

below.



26


USE CASE 2 Exercise



27


USE CASE 3 Create Baselines in Windchill

to Publish Data during Pre-Production for new Part/Family/Assembly



28


UC3: Publish Data During Pre-Production Introduction to Baselines in Windchill

• A Windchill baseline is a functionality in Windchill that captures as a snapshot in time a set of databases as checked in.

• Baselines are used for numerous purposes such as to capture and protect the databases of a project’s formal Gate Review, a key program milestone. Baselines ensure complete history, traceability and status accounting for such milestones.

• A baseline having a name ending with “_AGL” triggers a publish of the secondary content from the Windchill drawing to its associated AgilePLM Document.

• Baselines can be created directly in the common space or conveniently during a checkin process.

• Baselines does not require an approval.



29


UC3: Publish Data During Pre-Production From Windchill to AgilePLM for New Parts/Assembly/Family

1. To perform interactions between WindChill and AgilePLM, JAVA must be installed. Both the 32 bit and the 64 bit versions must be installed. • Hit the keys Windows+R on your keyboard at the same time to open the

run window. • Type CMD and click OK • In the command Window Type “java –version” • If you do not have Java version Java 1.6.31 installed, it is recommended to

upgrade or downgrade to this version. Note: PTC only supports JAVA version 1.6.31 however later versions of java are

available that have been running and utilized in MSI with Creo and Windchill.

2. The Java 1.6.31 installer can be downloaded from P: drive (apps > mcad > image > Java_1.6_31_X64 > jre-6u31-windows-x64.exe).

Note: A machine reboot is required once installation is complete



30



3. Create a PDF of your Pro-E drawing and save the file on your desktop. Name the PDF file using the MSI supplier drawing/database file Nomenclature: • <FamilyName>_<Revision>-<Iteration>.pdf for example: • HN000097A_2-1.pdf; Family name= HN000097A; Revision=2;

Iteration = 1, 4. Create a STEP file of the Part file and save the file on your desktop.

Name the step file as using the MSI supplier drawing/database file Nomenclature: • <PartNumber>_<Revision>-<Iteration>.stp for example: • HN000097A01_2-1.stp; Part Number= HN000097A01;

Revision=2; Iteration = 1, 5. Create a 3D PDF “File” use the same nomenclature as step 4.



31



6. Create a Pro/E part file and save the file on your desktop. Name the Pro/E file as using the MSI supplier drawing/database file Nomenclature: • <Part Number>_<Revision>-<Iteration>.prt for example: • HN000097A01_2-1.prt; Part Number= HN000097A01;

Revision=2; Iteration = 1, 7. In Windchill, Check-out your Drawing.

8. Click on the Information icon of your Pro/E drawing in your workspace as shown.



32



9. Click on Actions > Edit Attachments> Add Attachment to attach any or all of the files just created in steps 3-6 as secondary content to the Windchill drawing.

10. Browse to your desktop and select the pdf of the drawing to add as secondary content.



33



11. Repeat Step 10 to add any or all other file types. 12. Click on OK once all the files had been selected. 13. Under Content tab > Attachments, you will be able to

find all of the files that was added as secondary content. NOTE: This is only seen in the workspace version until the

drawing is checked in.



34



14. Check in the drawing and part to Commonspace prior to creating a baseline. You will NOT be able to create baselines if the parts are still checked out.

15. To create a Baseline and publish the secondary content to AgilePLM. • Search for your drawing in Commonspace.

16. Under Actions, click on Add To > Add to Baseline



35



17. Click on New Baseline as shown below.

18. A New Baseline windows appears • Enter the name of the baseline: (see note) • Leave the options for Protection and Location fields as it is.

NOTE: Baseline nomenclature: <Part Number>_<Revision>-<Iteration>_AGL.

For example; HN000079A01_2-1_AGL. The baseline name must end with “_AGL” in order to publish the data to AgilePLM.



36


UC3: Publish Data during Pre-Production From Windchill to AgilePLM for New Parts/Assembly/Family

hn000097a_1-1_AGL

19. Set the drawing item as the primary object and click OK.

hn000097a_1-1_AGL



37



20. Optional Method: Create a baseline during check-in of the Windchill drawing. • Select the drawing in the workspace • Click Checkin • Click the next button



38



21. The Set Options tab now appears. • Select the Create Baseline box • In the Name Field use the same nomenclature to name the

baseline as described in Step 18 • Click Finish.



39



Note: You will receive an e-mail indicating that publish was completed, and the Windchill drawing has been published to AgilePLM item under a newly created EC. Email notifications should arrive within three (3) minutes.

22. If the Document object is not attached to an open EC, it will be loaded onto a newly created EC and all of the Winchill Drawing’s secondary content will be attached to Document object’s Attachments Tab. If the Document object is already loaded onto an EC, then the only operation is to attached all of the Winchill Drawing’s secondary content to the attachments tab.

23. In AgilePLM, click on the Refresh icon to update the part object’s details.



40


24. Click on the Title Block tab 25. Click on the Windchill Hyperlink to take you to the Windchill section in

the Title Block tab.

Note: More information was pulled from Windchill and now available to be viewed in AgilePLM. This new information shows the time stamp of the last publish occurred and by whom.




41


USE CASE 3 Exercise



42


USE CASE 4 Managing open ECs for new Part/Family/Assembly



43


UC4: Managing Open EC from Baseline Creation 1. After data has been published to AgilePLM, you will find that a new EC

has been created. Click on the Revision drop down menu and select the proposed revision indicated in parenthesis.

Note: Do NOT close the EC until you have received an e-mail saying that the data has been published to AgilePLM.

2. Click on the Attachments tab and you will be able to download any of the attached files which were published to AgilePLM.



44


UC4: Managing Open EC from Baseline Creation 3. To save the attachment to your desktop, left click on the files, if you see

Open or Save select Save to download the selected file to your desktop and proceed to step #10 below.

4. If you do not see the Open or Save options when you left click on the attachment, then prior to downloading the step file, you will need to register file types for download from hyperlink in Internet Explorer.

5. Right click on any step file and click on Properties.

6. Click on Change to initiate file type registration.

7. Click on Internet Explorer as the recommended programs (or CAD such as Creo 2.0 if shown).

8. Select Apply followed by OK to complete step.



45


UC4: Managing Open EC from Baseline Creation 9. Select the files (make sure selection is highlighted Gray – click on

CTRL to select multiple files) and click on “GET” to download the files.



46


UC4: Managing Open EC from Baseline Creation 10. Click on the Changes tab. Under Pending Changes, you will be able

to see your EC number for the data that was just published to AgilePLM. Click on the EC number.

11. You will be brought to the Cover Page of the EC. To edit the Description of Change field, under Change Order Details. Select the Edit button located at the bottom right hand corner of that section.



47


UC4: Managing Open EC from Baseline Creation 12. Edit the details of the Change Order as follows:

Product Line(s): GOVT (or per Design Center recommendation) Change Category: New Product Introduction Description of Change > COMPLETE CHANGE DESCRIPTION: Release PBT Housing v1 d/base Reason for Change: Request for new quote

Save the form once this is completed.

13. Under Affected Items, click on Add to add the AgilePLM Part (HNXXXXXXA01) into the EC. Change the values of the “New Rev” fields to “1”. • Save the form.



48


UC4: Managing Open EC from Baseline Creation Special Note Due to Current system errors, If the items need to go to legacy ERPs, you must first get the items in ERP prior to setting a revision higher than “1”. To send an item to Legacy ERPs you must select the “Engineering Change Order” and change all affected items’ lifecycle phase from Preliminary to Development. If all items are already in the Legacy ERPs the ZWS Workflow can be used. ZWS Workflow is a approval less workflow, developed for this MCAD process, to enable revision tracking of supplier communications without placing a part or document object editing restrictions.



49


UC4: Managing Open EC from Baseline Creation 14. Observe the default Originator and Workflow in this EC.

15. Click on Actions > Audit Status to identify unresolved errors that will prevent the notice from proceeding to the next status. You have to resolve all errors before submitting the notice.



50


UC4: Managing Open EC from Baseline Creation 16. Once all errors are resolved, click on

Next Status > CCB.

17. A Select Workflow pop-up window will appear with ZWS Workflow as default. No Change Analyst is required for this workflow. Click on Continue.

18. This EC does not require any approvals. Click on Finish to proceed to the next status.



51


UC4: Managing Open EC from Baseline Creation 19. The status of the notice has changed from Pending to Released. Click

on the Workflow tab to view a summary of the workflow.

20. The EC is now successfully closed and the AgilePLM Document is released to Revision 1.



52


USE CASE 4 Exercise



53


USE CASE 5 Design Iteration for new Part/Family/Assembly



54


UC5: Design Iteration for Part/Assembly

1. Revise the drawing and part in your workspace from Rev 1 to Rev 2.

2. In your workspace, check out and then open the drawing in Creo. Make a change to your drawing. Record the revision in the revision column and identify all changes in the print with revision balloons.

3. Save the drawing.



55


UC5: Design Iteration for Part/Assembly 4. Create secondary content:

• Make a pdf of the drawing • Make a Step file of the Part file. • Make a copy of the Part file • Use the same nomenclature that was described in USE CASE 3

5. Add all of the file types to the drawing as secondary content. Follow the same procedure set forth in USE CASE 3 • Check out the drawing • Click the info button to get to the Drawing information page • Click Actions > Edit Attachments > Add Attachments > Browse • Add the files one at a time

6. Check in the Drawing and the part files 7. Create a new baseline following the steps shown in USE CASE 3

• Actions > Add To > Add to Baseline



56



8. Name the baseline, use the same nomenclature as shown in USE CASE 3 • Baseline nomenclature: <Part Number>_<Revision>-

<Iteration>_AGL. For example; HN000079A01_2-1_AGL. The baseline name must end with “_AGL” in order to publish the data to AgilePLM.

9. Leave the following fields as shown: • Protected: set to “YES” • Location: set to “Select Folder”

hn000097a_2-1_AGL



57



10. Set the current baseline object as the primary object and click OK.

Note: Objects that are not set as primary object will NOT be published to AgilePLM.

11. You will receive an e-mail indicating that publish was completed, and the Windchill drawing has been published to AgilePLM item under a newly created EC.



58



12. In AgilePLM, click on the Refresh icon to retrieve the updated details of your part.

13. Review the Windchill data in the Windchill section in the Title Block tab of the Document object. Verify that it has gotten updated.

14. Open the New EC

Note: Do NOT close the EC until you have received an e-mail saying that the data has been published to AgilePLM.



59


UC5: Design Iteration for Part/Assembly 15. Fill in the remaining required fields:Click the Edit button

• Product Line(s): GOVT • Change Category: New Product Introduction • Description of Change > COMPLETE CHANGE DESCRIPTION • Reason for Change: Request for revised quote • Click save when done



60



16. Under Affected Items tab, click on Add to add the AgilePLM Part (HNXXXXXXA01) into the EC. Change value of the “New Rev” field to “2”. Save the form.

17. Observe the default Originator and Workflow in this EC.


19. Once all errors are resolved, click on Next Status > CCB. Follow the

steps shown in Use Case 4.



61



20. The status of the notice has changed from Pending to Released. Click on the Workflow tab to view a summary of the workflow.

21. The EC is now successfully closed and the AgilePLM Document is released to Revision 2.



62


USE CASE 5 Exercise



63


USE CASE 6 Promoting new Part/Family/Assembly to Production Release



64


UC6: Promoting Parts to Production Release 1. Now that the design of the parts are final, manufactured, and

evaluated, they are ready to be Promoted to Production Release in Windchill.

2. From Creo generate a pdf file of the drawing and save it on your desktop. Name the file following the current PDM1 naming convention <Family_Name>_<Revision>.pdf (e.g. HN0000201A_A.pdf).

3. Using the same steps shown earlier, check-out the drawing and add the PDF print as attachment into the Windchill drawing (Actions > Edit Attachments > Add Attachments > Browse). This is MANDATORY.

4. Remove the all of the older attachments so that the Drawing only has latest files as the secondary content. (Edit Attachments > Delete).



65


UC6: Promoting Parts to Production Release 5. Click on Content tab to view the current attachment.

6. Check-in the parts to Commonspace once the PDF print has been added as attachment.

7. Revise both the part and drawing to Revision A. Verify that the lifecycle state is set to In Work.



66


UC6: Promoting Parts to Production Release

8. In Commonspace, create a New Promotion Request to release the part to Production Released.

9. Select the drawing to be promoted, and click on New Promotion Request.



67



11. Click on Next once this is completed.

10. Name the Promotion Request: • Nomenclature: <Drawing Number>_<Revision>-<Iteration> • e.g. HN000097A_A-1. • Select Autoselect Folder for Location • Do NOT check Apply default collection.



68



13. Set Target Promotion State to Production Released.

12. Click on Collect Objects to collect all the dependent Windchill objects related to the drawings to be promoted to Production Released.



69


UC6: Promoting Parts to Production Release 14. Select the two Windchill objects and click on Set Object for

Promotion.

15. Click on Finish once this is all completed. DesignState will publish Windchill objects that have been synced to AgilePLM.

16. You will receive an e-mail indicating that publish was completed, and the Windchill drawing has been published to AgilePLM item under a newly created EC.

17. In AgilePLM, click on the Refresh icon to retrieve the updated details of your item.



70


UC6: Promoting Parts to Production Release 18. You will be able to find all information pertaining to Windchill under Part

Details.

19. After data has been published to AgilePLM, you will find that a new EC has been created. Click on the drop down button under Rev and select the EC. The number in parenthesis indicates the proposed revision in Pending status.



71


UC6: Promoting Parts to Production Release 20. On the Changes tab, click on the pending EC. Observe that the

proposed revision is now (A). 21. You will be brought to the Cover Page of the EC. Edit Description of

Change under Change Order Details to briefly describe the change. 22. Edit the details of the Change Order as follows and save the form once

this is completed. *Product Line(s): GOVT *Change Category: New Product Introduction *Description of Change > COMPLETE CHANGE DESCRIPTION: Full release part to Rev A *Reason for Change: New item release *Reason Code: CO_10 – LCP to Production *Affected Design Function(s): Mechanical



72


UC6: Promoting Parts to Production Release 23. Under Affected Items, click on Add to add the corresponding AgilePLM

Part into the EC. • Change value of the “New Rev” tab to “A”. • Save the form.

24. Observe that the Workflow in this EC is NO longer ZWS Workflow, but Engineering Change Order.




73



26. Select the core ID of your change analyst. Save the changes made to the EC.

27. Click on Next Status > Submitted.

28. After the EC has been submitted, you can push the notice to Analysis. Select the core ID of your change analyst. and click Finish.



74



29. As a change analyst, you will be able to approve the EC. Click on Approve.

30. As a change analyst, you are required to fill up these fields under Affected Items: □ Previous Rev Valid to Date: (Double-click inside the empty column) Select today’s date □ Effective Date: (Double-click inside the empty column) Select today’s date

31. Save the changes made on the EC.



75


UC6: Promoting Parts to Production Release 32. Click on Next Status > Released.

33. A summary of the EC workflow is as below.

34. Once this is done, the approver should proceed to approve the Promotion Request.



76



35. To reject a promotion request, go to the Affected Items tab of the EC, then select reject from drop down and save ECO (for Approvers).



77



36. An approver do not need to go into Windchill to reject the Promotion Request Form. Select the promotion request reject from the Agile Action PX.



78



37. The synchronized item and any items set for promotion will be set back to In Work and the promotion request will be rejected as shown below.



79



38. If the ECO is approved, it is set to be released. The PX will do the following:

• The synchronized item and any items set for promotion will be set to production released

• The promotion request will be approved



80


USE CASE 6 Exercise