Using AgilePLM in MSI - Motorolalearningmedia0.motorolasolutions.com/services/edu/...GNL1147.00E -...

GNL1147.00E - Using AgilePLM in MSI August 2013

Using AgilePLM – Electrical Engineers

1

Motorola Solutions Internal

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


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

Module Objectives

• Describe the processes involved in the ECAD design.

• Show where the processes stand in the context of end-to-end item processes.

• Describe the ECAD interface that transfers information between Cadence and AgilePLM.

• Create AgilePLM objects (create item and change requests) in order to release an ECAD design.

• Perform the walkthrough of the approval processes involved to release an ECAD design.



3


SAP

ERP Systems Agile

PDM Systems Engineering CAD

Systems

PRO-E / Intralink 9

Cadence Suite

External Partner Collaboration

To/from Vendors, ODM,

JDM & CM

SW CM Systems

Trilogy

Oracle R12 (Was SAP) Global Oracle

PBT Scope is • Elimination of PDM1, WebNiR, ICCS, eMARS, and MCMS. • Deployment of a single PLM System for MSI. • Development of a Global standard set of unified processes

and data set across MSI. • Organizational changes supporting the process and system

changes.

Data / Product Migration

from PDM1, ICCS,

MCMS, eMARS & related systems

Agile PLM-EBS Interface

Regional Oracle Systems Data

Migration & OMAR

Integration

EDA Connector

Target PLM System Environment



4


Module Map

Create Library Model

ECAD Design

Workflow

Design to

Manufacture (DTM)

Comprehensive Bill of Materials (CBOM)

AgilePLM for Legacy Data and

Documentation



5


Introduction

• AgilePLM is used to manage requests for library models. • This aligns the process for ECAD and MCAD library models for

Enterprise Solutions and Government Solutions. • Fewer multiple forms used (WebNIR, LRS) for Government

Solutions.

• The addition of the TOP approval process during library part creation or revision (if and when needed).



6


Create Library Models Workflow Context

The Library Models workflow is triggered in these situations:

• Create a new item which requires CAD Libraries.

• Change library data only (with no change in AgilePLM revision).

• Request for new document number, e.g. copper features.

• Request simulation model (SI/RF/MML) for an existing AgilePLM item.



7


Process Map of the Create Library Models Workflow



8


Create New Library Model Items: Engineering Create New Item Part Number Which Requires CAD Libraries The requestor (Engineering) creates a new item in AgilePLM and indicates that new CAD library models are required.

The requestor also includes the data required to support symbol creation and to request any additional RF and/or SI models.

The Library Team will then be notified and create CAD Library Request (CLR) to begin the Create Library Models workflow.

The CAD Library Request (CLR) will go thru manufacturing team and requestor approval.

The next set of slides describes the procedure performed by the Engineering Team to create a new part and document item with new library models required.



9


1. Click Create New > Items > Parts from the drop-down list.

Create New Library Model Items: Engineering Create New Item Number Which Requires CAD Libraries



10


2. Select the Type of Parts to create. In this example, Capacitor was selected.

Create New Library Model Items: Engineering New Item Part Number with CAD Libraries Required



11


3. Enter the attributes of the new part in all the mandatory fields and click Save.

Design Source: Off-The-Shelf

Create New Library Model Items: Engineering Create New Item Part Number with CAD Libraries Required



12


4. Enter the remaining attributes for Part Details and under CAD Libraries Required, select ECAD, RF, and SI. Click Save.




13


5. Select the Attachments tab and attach any required files (print/datasheet) for library models creation using the Add button.




14


6. Once complete, a new item part number will be created in Preliminary status.


7. Select the Manufacturers tab and enter the Manufacturer Name and Manufacturer Part Number.

Note: For more information on entering, refer to the Managing Manufacturers and Manufacturer Parts for Creators module.



15



Enter the attributes of the new part in all the mandatory fields (denoted by *) and click Save. Number: Click the 123 button and select Hardware Number Shield. Design Source: MSI Custom



16


Note: For CAD Libraries Required, select ECAD. The remaining steps are similar to Steps 4 to 6.

Create New Library Model Items: Engineering Create New OTS Item Part Number with CAD Libraries Required



17


Note: Steps 1 to 6 can also be repeated to create a new document. Ex. copper features. Replace step 1 with Create New > Items > Documents.

Create Library Models Request: Engineering Create New OTS Item Part Number with CAD Libraries Required



18


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

Type: Document

Number: Click the 123 button and select Copper Features.

Document Details Type: Copper Features

Create Library Models Request: Engineering Create New Item Document Number



19


Create Library Models Request: Engineering Create New Item Document Number For Copper Features, the item description shall be as follows:

• Board mounting hole item description: Board mounting hole, plated

• Board contacts item description: Contact general use

• Edge Connectors item description: Connector, edge of board

• Hotbar item description: Contact hotbar

• Shorting Bar item description: Shorting bar

• Test point item description: Surface mount test point or Thru hole test point

Please provide the size needed for these copper features requests.



20


1. To clone an existing CAD Library item, enter the Capacitor part number that was created earlier into the Search box and press Enter.

Create New Library Model Items: Engineering Clone an Existing CAD Library Item



21


2. Click the Actions drop-down and select Save As to create a duplicate of the item.




22


3. In the Number field, click the 123 button to auto generate the new item number or edit the item number if it is part of a series.

4. Click Save.




23


5. Update the remaining attributes to match the new item and click Save to create the new item.




24


Create Library Models Workflow Introduction 1. Once the Library team receives the item create which needs ECAD model from

the requestor, a CAD Library Required (CLR) to begin the workflow to build the part library will be created.

2. A librarian is assigned and validates the data provided. A librarian may hold/reject/cancel the CLR if it does not meet the necessary requirements.

3. If the MCL physical symbol does not exist in the library, the CLR is routed to the Technical Operations (TOP) team for approval.

4. After the physical symbol is approved, the Library team performs the QC and releases the Cadence symbol to the Production Part Browser (Cadence).

5. AgilePLM notifies the requestor when the item is released.

6. The requestor reviews the symbol in Cadence and provides the final approval. The Library Team will close the CLR if it is in Requestor Approval more than 48 hours.

Note: If MCAD Model Library (MML), Radio Frequency Model (RF), and/or Signal Integrity Model (SI) models are needed, the information for these models will be added to the item after the CLR is closed.



25


Create Library Models Workflow: Engineering Approval Workflow

1. The requestor will be notified and will then log into AgilePLM and search for the created CLR.

2. After reviewing the part in Cadence, click the Workflow tab and select Approve.



26


Create Library Models Workflow: Engineering Approval Workflow

3. The Approve for Requestor Approval window will appear.

Note: Add any Comments if necessary and click Approve.



27


Create Library Models Workflow Submit Library Item Change for an Existing Library Item 1. There are scenarios where an item number that is already in Cadence

Library is required to be updated.

2. The steps are very similar to Create New Library Model Request which involves submitting a Change Request followed by approving the Change Request by the Library and Tech Ops Team.

3. The requestor would be required to submit a Library Item Change Request for an existing item in the library if it does not uprev the item.

4. The Library Team and Tech Ops Team will be notified as needed, based on the Approval Workflow.

5. If EC submitted by requestor has ECAD model attached to the item number, the library team will create a CLR.

6. The next set of slides will describe the procedure to submit a Change Request followed by approving the Change Request by Approvers.



28


Create Library Models Request: Requestor Submit Library Item Change Request for an Existing Library Item

1. To make changes to an existing Library Item, select Create New > Changes > Change Requests.



29


2. Select the Type as CAD Library Request (CLR).

3. Set Library Type to ECAD and enter the remaining attributes marked by an * and click Save.




30


4. Set Workflow as ECAD Library Item Change. Enter the other fields as necessary. Click Save.


Note: Library team will enter "Part released in Common Library" or "Part released in EMb Legacy Library" in the Description of Change field.



31


5. Select the Affected Items tab and click Add to add the Item Part Number that is required to be changed.

6. Select the Workflow tab and verify that the workflow is in Assign status.




32


7. Once the form is promoted to Requestor/Tech Ops Approval state, the Requestor and/or TOP will need to review and approve.




33


1. Requestor/Tech Ops will be notified and log in to AgilePLM. Select the Workflow Routings tab. Ensure that the CLR number is listed and select it.

2. Click the Attachments tab to review the attachments.

Create Library Models Request: Requestor/Tech Ops Submit Library Item Change Request for an Existing Library Item



34


3. Once reviewed, Click at the Approve button. A new screen “Approve for Requestor/Tech Ops Approval” will be prompted, click Approve.




35


4. Once all have approved, the request will now be at QC & Release.




36


Note: Library team will QC and approve the change. The workflow will then be completed and closed. The changes will be in the Cadence library.

Create Library Models Request: Library Team Submit Library Item Change Request for an Existing Library Item



37


This workflow will be done by the library team once the ECAD has been released into the Cadence library. MML model will be created by default. RF/SI model is generated if it was requested during item create.

Create MML/RF/SI Workflow Create MML/RF/SI Request



38


1. Select Create New > Changes > Change Requests.




39


2. Select the Type as CAD Library Request.

3. Set Library Type as either MML, SI or RF and enter the remaining attributes marked by an *. Click Save.

Note: The MML model will be created, once the ECAD part has been released into Cadence library.




40


4. Enter the remaining fields such as Change Category, Reason Code and Workflow. For Workflow, choose MML/SI/RF Model. Click Save.




41


5. The workflow is in Assign status and the library team will proceed and closed the form.




42


Module Map


ECAD Design

Workflow

Design to

Manufacture (DTM)



Documentation



43


Introduction: Capabilities Enabled EDA Connector

• The EDA Connector software is an interface tool bridging the gap between the Cadence ECAD Tools and the PLM system.

• The EDA Connector implements automation with previously manual tasks in the new ECAD design workflow such as:

• PLM Part and Document record creation and attribute selection.

• ECAD BOM data exports, file attachment search, identification ,and uploads.

• Creation of the CBOM (merging ECAD and AgilePLM items) utilizing attributes specified during the data and documentation uploading process.

• PLM EC record creation and affected item attachment.



44


Introduction: Capabilities Enabled (cont.) • The EDA Connector is invoked within the Cadence Flow Manager, the

user selects the Project Folder, the Connector identifies the part number structure data/documentation, compares it with the current Agile PLM system, presents upload options to the user for selection, displays current PLM status, creates records for preliminary documents and parts, or presents EC options to initiate a release to start the document / parts lifecycle status or execute a change to previously released records.

• The EDA Connector extracts BOM information from the Cadence schematic, design files and supporting documents from the Allegro board file, creates/identifies the appropriate AgilePLM records and uploads the BOM(s), Assembly Drawing, Schematic Diagram, Printed Circuit CBOM inclusive of the Fabrication Data and Documentation.



45


Introduction: Capabilities Enabled

ECAD Design Data & Document Requirements

Item Data / Document Item AgilePLM Part Number & Record Class

Attachment Format

Raw Board

Fabrication Drawing PC123456A 01 (PF123456A01 for Flex Circuit) Part Subclass

PDF Panel Drawing

Artwork ODB++ (zip)

Assembled Circuit

Assembly BOM PA123456A01 Part Subclass NA

Assembly Drawing PA123456A Document Subclass PDF

Functional Schematic Schematic Diagram SD123456A01 Document Subclass PDF

Project Data ECAD Project Data Base Folder DB123456A01 Document Subclass Zip File



46


Introduction: Capabilities Enabled Project Data Archival The ECAD Data will be archived by zipping up the Project Folder form the Work In Progress (WIP) are and importing it into in the AgilePLM system via an EDA Connector upload to the respective archive document record. Once the items associated to the Project Folder are released, the WIP area will be removed and the Archived version of the Database will be locked.

When the Schematic, BOM Items (components), PC or PF CBOM Data or Documentation objects requires a change, the updated must originate from the Cadence database Project folder. This change will be executed by exporting the latest version of the Project Folder from the Database Archive record, copying and renaming it to the next version while placing it in the WIP area.

The respective files are generated and the revisions of the corresponding document and part records in Agile PLM are incremented.



47


Introduction: Capabilities Enabled Raw Printed Circuit and the implementation of a Comprehensive Bill Of Materials (CBOM) • The CBOM concept removes the Materials, Manufacturing Processes and MSI

qualification requirements off the fabrication drawing (.pdf document) associated with the Cadence board file (.brd) and places them as items on the AgilePLM CBOM part record.

• The PC or PF CBOM is comprised of items generated from the Cadence board file (.brd) and additional AgilePLM Document records.

• ECAD items attached to the CBOM include: • Fabrication Documentation in a PDF format, which is inclusive of the Fabrication and Panel

Drawing.

• Fabrication Data in a ODB++ format which is inclusive of circuit artwork, netlist information, DTM/DFM data, and SMT placement data.

• AgilePLM items on the CBOM include: • Materials inclusive of Metals, Non Metals, Composites …

• Manufacturing Processes inclusive of Plating's, Finishes, Masks, Coatings ….

• MSI Part Notes inclusive of Part Qualification Specifications, Part Marking Requirements ….



48


Introduction: Capabilities Enabled

Vendor Collaboration using AgilePLM Discussion Objects • Vendors on the AML will have an account granting them the

ability to access AgilePLM. • Utilization of an AgilePLM discussion object will:

• Standardize the method of communication so that there is less confusion for engineering and manufacturers.

• Improve documented collaboration between engineering and fabrication vendors and assembly manufacturers.

• Enable the communication and attachments (of the related documents) to be easily tracked in AgilePLM by revision for historical purposes. This ensures the documentation is complete, accurate, and consistent.



49


Process Map of the ECAD Design Workflow 1

2

3



50


Prepare and Post an ECAD Package in AgilePLM ECAD BOM Release Process Workflow



51


Prepare and Post an ECAD Package in AgilePLM Standard Naming Convention for Database and Project Folder Directory Database Part Number Format in AgilePLM All Projects Databases shall begin by retrieving a CAD Database (DB) part number from AgilePLM. This part number is required for creating the Flow Manager Directory Structure.

Project Folder Directory Format in the Cadence Flow Manager All Flow Manager Project Directories shall be named using the following format.



52


Prepare and Post an ECAD Package in AgilePLM Standard Naming Convention for Allegro Database and Manufacturing Data ECAD Allegro Board File Database Part Number Format All Printed Circuit Boards (PC) and Flex (PF) Allegro board files shall adhere to the specified database format, using standard prefixes and current revision levels.

CAD - Fabrication Data File Naming Format All Printed Circuits (PC) and Flex (PF) ODB++ manufacturing data files shall adhere to the specified data file format, using standard prefixes and current revision levels.



53


Prepare and Post an ECAD Package in AgilePLM Standard Naming Convention for Drawing Title Block Part Numbers Schematic Diagram and Fabrication Drawing Title Block Part Number Format All Schematic Diagram (SD) and Fabrication (PC or PF) drawings for Printed Circuit part numbers shall adhere to the following format in the title block.

Assembly Drawing Title Block Part Number Format All Assembly (PA) drawings for Printed Circuits shall represent of all assembly variants. The title block is number shall be the standard part number format with the appropriate prefix and no suffix since the drawing represents all of the variants.



54


Prepare and Post an ECAD Package in AgilePLM Standard Naming Convention for ECAD Documentation PDF Files

ECAD Part Number Format for Drawing PDF Files All Schematic Diagram (SD), Assembly (PA) and Fabrication (PC or PF) drawing for Printed Circuits part numbers shall adhere to the following format.



55


Prepare & Post an ECAD Package in AgilePLM Overview of the workflow The ECAD Design workflow starts with the creation of a database document (DB) in AgilePLM.

1. Create a new document part number in AgilePLM for a CAD Database (DB).

2. In Flow Manager, create a Project Folder WIP area using the new part number by using a designated Project Folder template or copying an existing Project Folder.

3. The user prepares the schematic, layout of the printed circuit, supporting data, and documentation. The Project Database filenames must match the six numeric digits of the document part number created earlier. Examples of the naming requirements:

Note: Users cannot create part numbers for PA, SD, PC and PF in Agile PLM System. The part numbers of these documents are assigned from the EDA Connector.

Data / Document Type Filename in Flow Manager Part Number in AgilePLM

Project Archive db001000a01_01_compress.zip DB001000A01 (Document)

Schematic (SD) sd001000a01_01.pdf SD001000A01 (Document)

Assembly Drawing (PA) pa001000a_01.pdf PA001000A (Document)

Fabrication Drawing (PC) pc001000a01_01.pdf PC001000A01 (Part)

Manufacturing Data (PC) pc001000a01_01.zip



56


Prepare & Post an ECAD Package in AgilePLM Overview of the workflow

4. Once the schematic, BOM or design files are completed and the package files are ready for release, the EDA Connector is used to push the data and documentation objects into the corresponding AgilePLM records.

5. The creator then confirms that the data and documentation objects are properly imported into the appropriate Agile PLM document and part records.

6. From the EDA Connector, the user can also create a Engineering Change object (EC), add the design file documents / parts, and submit the EC. This will initiate the item lifecycle and revision control for the AgilePLM part or document records for the BOM(s), Raw printed Circuit CBOM, CAD Database, Schematic Diagram, and Assembly Drawing.



57


Prepare and Post an ECAD Package in AgilePLM Creating a New a CAD Database Part Number in AgilePLM Before ECAD design begins, the design engineer creates a new document part number in AgilePLM for the CAD database.

1. Log in to AgilePLM.

2. Create a new document object using the Create New > Items > Documents action.



58


Prepare and Post an ECAD Package in AgilePLM Creating a New a CAD Database Part Number in AgilePLM 3. The Create New Documents

window appears.

4. For Type, select Document.



59


5. Click the 123 button and select CAD Data Base from the drop-down list.

Prepare and Post an ECAD Package in AgilePLM Creating a New a CAD Database Part Number in AgilePLM



60


6. Complete the remaining fields. Required fields are indicated by a red asterisk.

7. Click Save to proceed.

Prepare and Post an ECAD Package in AgilePLM Creating a New a CAD Database Part Number in AgilePLM



61


Prepare and Post an ECAD Package in AgilePLM Creating a new CAD Database part number in AgilePLM 8. In the Title Block tab, complete the

remaining fields and click Save to commit your changes.

Note: For the General Description, use capital letters without any returns.

Once the part number for the CAD Database is created, the Design Engineer proceeds to create the Project Folder in the WIP area for schematics creation, printed circuit design layout and the supporting data and documentation in the Cadence Concept and Allegro tools respectively.



62


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector The following slides demonstrate the transfer the Preliminary ECAD data and documentation files from the ECAD Cadence Project Directory into AgilePLM using the EDA Connector.

(The filenames of the design files must follow the base number of the CAD database object created in AgilePLM at the start of the ECAD design workflow.)

1. Access the EDA Connector from the Design Archive item in the Flow Manager window.



63


Prepare & Post an ECAD Package in AgilePLM Using the EDA Connector 2. The EDA Connector Dashboard

appears.

3. Perform this procedure:

a) Click PLM Login and select the AgilePLM server to connect (only applicable during the first time you run the connector if you check the box to remember your information).

b) Click Project Editor and add an ECAD project (.cpm file).

c) Click Checkin Design to begin the process to transfer ECAD design files to AgilePLM.

a b

c



64


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 4. The Checkin Wizard appears.

Select the following attributes.

Template: Make sure to select Cadence release MFG data to AgilePLM (16.5).

Project: Select a project from the drop-down list. This list is populated with the projects added using the Project Editor.

5. Click Next to proceed.



65


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 6. Select the BOM Variant, which is

used to create a BOM of the PCA.

For this example, choose PA000xxxA01.

Click OK to proceed.

7. Select the CBOM Templates, which is used to create the CBOM of the PCB materials.

For this example, choose Class,4101-24_Half-OZ-CU_ENIG_GRN-MASK_NO-MRK.


Note: If the CBOM already exists, click Cancel to proceed.



66


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 8. The Design Structure page appears.

• Use the checkboxes next to the items to select which files to import the data and documentation into AgilePLM.

Note: • Review the “Item Numbers” to

make sure the base number and revision are correct. (In the case of a preliminary upload the EDA Connector will be Creating the new AgilePLM records.)

• The EDA Connector will display the part or document current AgilePLM rev and lifecycle status in the “Old Revision” and “Old Lifecycle Phase” fields. This is Introductory when creating a new project.




67


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 10. When presented with options for

Change Order: • Update Existing Change Order:

Select this option to modify a previously created / existing change order to update data and documentation on an unreleased EC.

• Create New Change Order: Select this option to create a new EC for the purpose of releasing a part and/or document and initiate lifecycle and revision control.

• Update Preliminary Item (no Change Order): a. Select this option to initiate the creation

of parts and/or documents and import the data and documentation.

b. Or to modify / update a previously created part and/or document record still in the Preliminary phase of the lifecycle.

Note: For this example, the items are still in the preliminary phase. Select the option Update Preliminary Item (no Change Order), and click Next.



68


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 11. The BOM Page displays the items to be

imported on the BOM in AgilePLM. Review these items for content to be reflected on the Printed Circuit Assembly. The CBOM Page displays the items to be imported on the CBOM in AgilePLM. Review these items for content to be reflected on the Printed Circuit Fabrication.

12. Use the checkboxes next to the items to select which items to transfer to AgilePLM.

Note:

• The blue checkmark next to the items indicates that the items exist in AgilePLM.

• A red X next to an item indicates the item is not in AgilePLM and will not be imported onto the BOM or CBOM in AgilePLM. (You will be able to continue but you will see the Red X again during your review of the results.)

• Currently, a generic CBOM will be created. Further automation is planned for future releases.




69


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 14. The Files Page has a series of

tabs which will show the Data and document attachments that will be transferred to AgilePLM.

Verify the attachments and review each of the four tabs:

• Project Database • PCB Assembly Drawing • CBOM • Functional Schematic Drawing

15. Use the checkboxes next to the

items to select which attachments to import into AgilePLM.




70


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 17. The Results screen appears

when the items have been imported (published) into AgilePLM.

Click each item below to show the published items and their links to AgilePLM.

• Project Database • PCB Assembly Drawing • CBOM • Assembled Printed Circuit

Board • Functional Schematic Diagram Any errors in the transfer are indicated by a red X.



71


Prepare and Post an ECAD Package in AgilePLM Using the EDA Connector 18. For any item, you can select the

File Checkin icon and then click Open in PLM browser. This will open a browser window with a login screen for AgilePLM.

19. Once the user is in AgilePLM, you can navigate within the Parts and Documents created to validate the data and documentation were imported correctly and log out of AgilePLM.

20. To dismiss the wizard, click Finish.

21. Click the Exit icon in the EDA Connector Dashboard to dismiss the window and return to Flow Manager.



72


Post an ECAD Package in AgilePLM on an EC Using the EDA Connector 1. Once you launch Agile from the EDA

Connector, clicking the Open in PLM browser link will launch the Web browser and load AgilePLM in the Document or Part Record selected.

For this example we have selected the BOM Open PLM Browser link.

After logging in to AgilePLM, the Title Block tab of the item is shown.

2. Click the BOM tab to view the items in the BOM. The screenshot shows that the EDA Connector has created the BOM and added the items into it.



73


Post an ECAD Package in AgilePLM on an EC Using the EDA Connector

3. Navigate to each of the items imported at a Preliminary lifecycle status and on the Title Block tab, click Edit and complete all the required attributes.

• Required document and part records attributes are: • General Description • Product Lines • Commodity Code • Owner • Design Source • Contains Encryption • APC • PCB Type • Document Details Type

4. Click Save to commit your changes.

Note: Before initiating lifecycle and revision control for any items such as Document or Part record, ensure that all the required attributes for the items are complete.



74


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control using the EDA Connector An Engineering Change (EC) is required in order to promote the lifecycle status of an Agile Document or Part record.

A numeric revision is used with EC releasing from Preliminary to Development, Prototype or Pilot lifecycle status An alpha revision is used with EC releasing from either Development, Prototype or Pilot

For Document or Part records that require a drawing (.pdf) to be attached, the EC number must be pulled during the EDA Connector uploading Process and the drawings need to be updated with the new EC number prior to performing the upload of the documentation. Note: Before you can promote a Document or Part on an EC and submit the EC for lifecycle and revision control you required to ensure: • All the require attributes on the individual AgilePLM records are complete for the

items designated for release. • All of the children (items listed) on a BOM or CBOM are at a life cycle status other

than preliminary. • If the child (item) is new you can add it to the EC that you are promoting the parts and documents

on.



75


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control The following procedure is to promote the lifecycle of the project from preliminary to development phase.

The recommended method is to use the EDA Connector to create an EC.

1. Access the EDA Connector from the Flow Manager window.



76


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 2. The EDA Connector Dashboard

appears.



b) Click Project Editor and select an ECAD project for transfer.


a b

c



77


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 4. The Checkin Wizard appears.

Select the following attributes:

Template: Make sure to select “Cadence release MFG data to AgilePLM (16.5)”.

Project: Select the project from the drop-down list.




78








Click OK to proceed




79


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 7. The Design Structure page appears.

Because we are only pulling the EC number to place on the documentation, unselect all of the item checkboxes except the Project Database.

Note: Only the Project database is highlighted.




80


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 9. When presented with options for

Change Order, select Create New Change Order.

10. Complete the highlighted attributes:

• Attribute Value: double-click and type.

• Lifecycle Phase: double-click and select from the drop-down list. For this example, select Development.

• New Rev: double-click and type. Use sequential numbers or capital letters (1, 2, 3 or A, B, C…) depending on you life cycle phase and the applicable criteria.




81


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 12. The File Page displays the

Project Database only.




82


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 14. The Results screen displays the EC

number to be used on the documentation prior to uploading into AgilePLM.


Note: The EC number is included in this screen is the EC that is created in AgilePLM and it has to go through the approval process before the project and the associated data and documentation is released and promoted to the appropriate phase of the lifecycle.



83


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control Once the design is complete, the data and documentation is created and the EC number pulled in the previous steps is placed in the appropriate drawing format revision control block, follow the following steps to initiate the release and lifecycle promotion.

1. Access the EDA Connector from the Flow Manager window.



84


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 2. The EDA Connector Dashboard

appears.



b) Click Project Editor and select an ECAD project for transfer.


a b

c



85


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 4. The Checkin Wizard appears.

Select the following attributes:

Template: Make sure to select “Cadence release MFG data to AgilePLM (16.5)”.

Project: Select the project from the drop-down list.




86








Click OK to proceed




87


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 8. The Design Structure page appears.

Use the checkboxes next to the items to select which files to transfer to AgilePLM. If necessary, unselect an item so that it will not be transferred to AgilePLM.

9. Take note of the Part and Documents current lifecycle phase of the item. The current AgilePLM Revision and Lifecycle Phase is displayed in the “Old Revision” and “Old Lifecycle Phase” fields.




88


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 11. When presented with options for

Change Order, select Update Existing Change Order.

12. Verify the proper EC number is present.

13. Complete the highlighted attributes:

• Lifecycle Phase: double-click and select from the drop-down list. For this example, select Development.

• New Rev: double-click and type. Use sequential numbers or capital letters (1, 2, 3 or A, B, C…) depending on you life cycle phase and the applicable criteria.




89


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 15. The BOM Page displays the items to be

imported on the BOM in AgilePLM. Review these items for content to be reflected on the Printed Circuit Assembly. The CBOM Page displays the items to be imported on the CBOM in AgilePLM. Review these items for content to be reflected on the Printed Circuit Fabrication.

Note:

• Use the checkboxes next to the items to select which items to transfers to AgilePLM.

• The blue checkmark next to the items indicates that the items exist in AgilePLM.

• A red X next to an item indicates the item that does not currently have a record in Agile and will not be transferred to AgilePLM during the upload process.




90


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 17. The Files Page has a series of tabs which will show the Data and document

attachments that will be transferred to AgilePLM.

Verify the attachments and review each of the four tabs:

• Project Database • PCB Assembly Drawing • CBOM • Schematic Drawing Note: You can unselect the item so that it will not be transferred to AgilePLM.

16. Click Next to continue.



91


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 18. The Results screen shows the

status of the items transferred to AgilePLM.

19. Click each item to show the published items and their links to AgilePLM.

A red X indicates an error in the upload.

Note: The EC number is included in this screen. This is the EC that is created in AgilePLM and it has to go through the approval process before the project is promoted to the Development phase of the lifecycle.



92


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 20. For the EC or any item listed, you

can select the File Checkin icon and then click Open in PLM browser. This will open a browser window with a login screen for AgilePLM.

21. Once the user is in AgilePLM, you can navigate within the EC, Parts, and Documents created to validate the data and documentation were imported correctly and log out of AgilePLM.


23. Click Exit in the EDA Connector Dashboard to dismiss the window and return to Flow Manager.



93


Prepare ECAD BOM Package Initiating Lifecycle and Revision Control From the EDA Connector, by clicking the Open in PLM browser link will launch the Web browser and load AgilePLM. Note: The destination in the AgilePLM will

be determined by the selection on the Results screen in the EDA Connector.

For this example we have selected the EC Open PLM Browser link. After logging in to AgilePLM, the Coverage of the EC is shown.

1. Click Edit and complete the attributes

in the EC.



94


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 3. Enter the following information:

• Product Family

• Change Category

• Reason Code

• Change Analyst



95


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 4. Scroll down to Change Order

Details and enter the following information:

• Project Name

• Affected Design Function(s)

5. Click Save.



96


Post an ECAD Package in AgilePLM on an EC Using the EDA Connector 1. Click the Affected Items tab.

2. Navigate to each of the items added to the affected items to ensure:

• Data and documentation is accurate.

• All of the part or document records attributes when required are complete such as:

• General Description • Product Lines • Commodity Code • Owner • Design Source • Contains Encryption • APC • PCB Type • Document Details Type



97


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 7. From the Actions drop-down list,

select Audit Status to ensure the EC is ready for submission.



98


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 8. The Audit Status Results window

appears. If there are errors, click Close and resolve the errors in the EC. If there are no errors, click Close and proceed to the next step.



99


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 9. Select the Workflow tab to view the

workflow phase of the EC.

10. Click Submitted on the workflow summary diagram to submit the EC for analysis by the Change Analyst.



100


Post an ECAD Package in AgilePLM on an EC Initiating Lifecycle and Revision Control 11. The Change Status to Submitted

window appears.

12. Enter the names of the users to notify.

13. Add any additional comments.

14. Click the Finish Button. The EC is now submitted and waiting for approval.



101


Module Map


ECAD Design

Workflow

Design to

Manufacture (DTM)



Documentation



102


Execute DTM: CAD Upload Introduction After the ECAD BOM package is prepared, the next stage of the ECAD design is Fabrication and Manufacturing Review.

This section describes the process to upload CAD data in order to validate that a design is prepared for manufacturing.

The processes are performed by Engineering and Technical Operations/Manufacturing Process teams.



103


CAD Upload Process Map



104


CAD Upload Process

The CAD data created during the ECAD Design workflow needs to be validated in order to prepare the design for manufacturing.

The process for CAD upload is shown below.



105


Execute DTM: CAD Upload Process The process to upload the CAD data is described below:

1. Engineering uploads the CAD data (zip) created during the ECAD design workflow at dtm.mot.com.

2. The data is validated in the DTM system.

• Manufacturing intermediate files are created.

• DFM analysis is initiated and a DFM report is generated.

3. Technical Operations/Manufacturing Process team reviews and updates the DFM report.

• Any corrections require the Engineering to implement the fix and resubmit the CAD data.



106


Execute DTM: CAD Upload Process 4. For NPIs (new product introduction), the Technical

Operations/Manufacturing Process team creates a discussion object in AgilePLM and attaches the DFM (design for manufacturing) report URL.

Note: The CAD data has been validated for DTM and the DFM report has been attached to the printed circuit board item.

To initiate the fabrication and manufacturing of the board and assembly, an EC/MC (engineering change/manufacturing change) object is created in AgilePLM to drive the request.



107


Execute DTM: DTM Kit Creation Process Map



108


Execute DTM: DTM Kit Creation Printed Circuit Assembly Manufacturing (Manufacturer)

1. The manufacturer retrieves the ECAD data for SMT build and post assembly.

2. The ECAD data is validated for DFM. If further collaboration with engineering is required, the manufacturer uses the AgilePLM discussion object to begin the discussion.



109


Execute DTM: DTM Kit Creation 3. If no further collaboration is needed, the manufacturer begins the DTM

Kit Creation workflow.

The DTM Kit Creation workflow is shown below.



110


Execute DTM: Procedure for DTM Kit Creation

Note: This is run by NPI Process Engineers. To drive the kit creation process in DTM, a flat BOM (formatted for CIMBridge) needs to be pulled from AgilePLM.

Accomplishing this requires the following:

• Run the AgilePLM Global DTM BOM report. This exports the DTM BOM report into a CSV file.

• Run the DTM Kit Creation utility. This imports the AgilePLM CSV BOM file.



111


PBT process flow shows two areas for DTM/NPI where the AgilePLM record should be updated with appropriate information.

This can be accomplished with Agile discussion objects instead of generating an EC which results in a new item revision.

Create Discussion Objects in Agile Send Feedback and Provide Attachments after DFM/Mfg Review Between Engineering and NPI



112


Create Discussion Objects in AgilePLM

Overview

In order to add attachments to an AgilePLM item without having to generate an EC, the following should be used:

Create an AgilePLM Discussion Object and give it a description including the AgilePLM item number for the attachments along with revision specific information.

Relate the desired AgilePLM item to the Discussion Object.

Add attachments to the Discussion Object as needed.

Send notifications or set action items if desired.

Change status of Discussion Object to Closed when activity complete.

Refer to the Managing Discussion Objects module for more information.



113


Module Map


ECAD Design

Workflow

Design to

Manufacture (DTM)



Documentation



114


Definitions of the CBOM

The Comprehensive Bill Of Materials (CBOM) concept is implemented in MSI prints for Government Solutions.

Similar to a BOM, which is the Bill of Materials for an Assembly, a CBOM is a Comprehensive Bill of Materials for a Part. • CBOM’s are created in AgilePLM by Electrical/Mechanical Engineers

and Designers at MSI. • CBOM’s items consist of materials used across all of the MSI product

lines such as Metals, Non Metals, Composite Materials, Manufacturing Process, and generic Part Notes.

• The items on a CBOM will have individual part numbers and will have an associated PLM lifecycle as any other part in the AgilePLM system.



115


Definitions of the CBOM As an example, the CBOM (an AgilePLM part object) for a Printed Circuit board would consist of the following items (AgilePLM document records):

Document Record Type Prefix Description (For This Example) Material Metal AM Copper Foil

Non-metal NM • FR Base Laminate • FR Prepreg

Composite CM Copper Clad Laminate Process Manufacturing MP • Copper Plating

• Surface Finish • Solder Mask

Part Note Part notes PN • Vendor Part Mark • Workmanship Standards



116


Advantages of Using CBOM

• CBOMs give the Program Teams the ability to identify and update materials used on MSI custom parts without looking at or editing a drawing in support of emerging Environmental Regulations.

• Materials, substances, and processes are contained on the CBOM instead of drawings. Thus, no drawing changes are required if there are any changes to those three items.

• Eliminates the manual task of viewing every drawing in an effort to identify if materials, substances, and/or processes are used.

• AgilePLM creates a repository for these items, which eliminates duplications and allows for quick searches in AgilePLM to find out if similar materials exist before creating new materials.

• Increases SCT buying intelligence for preferred status, reduces costs through bulk procurement, reduces overall inventory, promotes recycling initiatives, and provides notice of obsolescence.



117


Advantages of Using CBOM

• A CBOM will have the ability to quickly do a Where Used search in AgilePLM to:

• Identify and locate MSI custom parts with non-compliant materials and create an EC to replace them.

• Identify and locate MSI custom parts with obsolete materials and create an EC to substitute them.

• Identify and locate MSI custom parts affected by any AML changes.

• The drawing of the MSI custom part will be an additional item listed on the CBOM. The drawing will be used as a visual aid and will contain the physical or dimensional attributes and unique performance characteristics of the part.

• The individual CBOM’s Base configurations will be a series of numeric suffixes which can be easily generated within AgilePLM by doing a search for the A01 configuration and doing a Save As (Clone) followed by manipulating the unique attributes of the items.



118


Before structuring a CBOM, several AgilePLM document objects need to be created first. This section shows the procedures to create part numbers for the following document objects:

Create an AgilePLM CBOM Part Object CBOM for a Printed Circuit Board

Document Record Type Prefix Description (For This Example) Material Metal AM Copper Foil

Non-metal NM • FR Base Laminate • FR Prepreg

Composite CM Copper Clad Laminate Process Manufacturing MP • Copper Plating

• Surface Finish • Solder Mask

Part Note Part notes PN • Vendor Part Mark • Workmanship Standards



119


1. Click Create New > Items > Documents from the drop-down list.

Create New CBOM Document Objects Composite Material Part Number



120


2. Select Document from the Type drop-down list.




121


3. Click the 123 button on the right side of the Number attribute, and select Composite Materials.




122


4. Under the Document Details Type drop-down list, select CBOM Composite Materials.




123


5. Enter the remaining attributes of the new document in all the mandatory fields (denoted by *).

• Document records attributes required: • Product Lines • Owner • Document Details Type

6. Click Save.




124


7. Click Save. You have successfully completed Item Create for a Composite Material on an Agile document record.


6. Scroll down to the Document Details section and enter the General Description with the necessary Composite Material note.



125


1. The procedure for creating new Metals part number is similar to the previous procedure.



4. Click the 123 button and select Metals.

Create New CBOM Document Objects Metals Part Number



126


5. Under the Document Details Type drop-down list, select CBOM Metals.


6. Fill up the remaining attributes of the new document in all the mandatory fields (denoted by *) and click Save.



127


6. Scroll down to the Document Details section and enter the General Description with the necessary Metal note.


7. Click Save. You have successfully completed Item Create for a Metal on an Agile document record.



128


1. The procedure for creating new non-metals part number is similar to the previous procedure.



4. Click the 123 button and select Non Metals.

Create New CBOM Document Objects Non-Metals Part Number



129


5. Under the Document Details Type drop-down list, select CBOM Non Metals.

Create New CBOM Document Objects Non-Metals Part Number




130


Create New CBOM Document Objects Non-Metals Part Number 6. Scroll down to the Document Details section and enter the General

Description with the necessary Non Metal note.

7. Click Save. You have successfully completed Item Create for a Non Metal on an Agile document record.



131


1. The procedure for creating new Manufacturing Process part number is similar to the previous Create Item steps.



4. Click the 123 button and select Manufacturing Process.

Create New CBOM Document Objects Manufacturing Process Part Number



132


5. Under the Document Details Type drop-down list, select Manufacturing Process.

Create New CBOM Document Objects Manufacturing Process Part Number




133


Create New CBOM Document Objects Manufacturing Process Part Number 7. Scroll down to the Document Details section and enter the General

Description with the necessary Manufacturing Process note.

8. Click Save. You have successfully completed Item Create for a Manufacturing Process on an Agile document record.



134


1. The procedure for creating new Part Notes part number is similar to the previous Create Item steps.



4. Click the 123 button and select Part Notes.

Create New CBOM Document Objects Part Notes Part Number



135


5. Under the Document Details Type drop-down list, select CBOM Part Notes.

Create New CBOM Document Objects Part Notes Part Number




136


Create New CBOM Document Objects Part Notes Part Number 6. Scroll down to the Document Details section and enter the General

Description with the necessary Part Note.

7. Click Save. You have successfully completed Item Create for a Part Note on an Agile document record.



137


Another method to create CBOM document objects is to use the clone (Save As) procedure. The procedures to clone an existing CBOM document object to create a new CBOM document object (materials, processes, and part notes) are similar. Note: You must use the same subclass when cloning. For example, clone an existing Metal part number to create a new Metal part number.

Clone an Existing CBOM Document Object Materials, Processes, or Part Notes



138


The following procedure is to clone an existing CBOM Part Note to create a new CBOM Part Note part number.

1. In AgilePLM, type the part number of an existing CBOM Part Note part number into the search box and press Enter.

Tip: You can use a wildcard search to increase the breadth of a search using the asterisk symbol.




139


2. Select a suitable part note from the search results. Click the part number to display the Agile document record you want to clone.




140


Clone an Existing CBOM Document Object Materials, Processes, or Part Notes 3. In the Title Block page, click Actions and select Save As from the drop-

down list.

The Save As window appears.



141


Clone an Existing CBOM Document Object Materials, Processes, or Part Notes 4. Click the 123 button and

select Part Notes from the drop-down list.

5. Complete all the attributes of the cloned part. A red asterisk indicates a mandatory attribute.

6. Click Save to proceed.



142



7. The Title Block page of the cloned document appears. Modify the General Description using capital letters.

8. Ensure the Product Line information is correct. Also, update any attributes related to the new part note.

9. Click Save to commit your changes.



143


Module Map


ECAD Design

Workflow

Design to Manufacture

(DTM)

Comprehensive Bill of

Materials (CBOM)

AgilePLM for Legacy Data

and Documentation



144


Legacy Data and Documentation

• This module will explain the process to upload the data and documentation into the AgilePLM System

• PLM Part and Document record creation, attribute selection and searches.

• ECAD BOM data imports for creation

• ECAD BOM data imports for changes and redlines

• Document file attachment and uploads

• PLM EC record creation and affected item attachment.

Note: This is a manual process is not ECAD Tool dependent. It will accept various forms of formats for the ECAD data and documentation requirements.

AgilePLM for Legacy Data and Documentation



145



AgilePLM for Legacy Data and Documentation Creating an Agile Document Record

Note: Legacy Agile ECAD Document Records are used for Assembly Drawings, Schematic Diagrams, Artwork, Panel Drawings and Circuit Test Data.



146






147


3. Enter in the Legacy Part Number directly into the number field.

DO NOT use the 123 button to use the auto numbering.


NOTE: Auto numbering will not work for Legacy part numbers. If this is a new requirement, you should be using the new MSI part number schema.



148


4. Fill out the required attribute for Product Line.

5. Fill out the required attribute for Owner.

6. Under the Document Details Type drop-down list, select the appropriate option for the Legacy Data or Document your are creating.

ECAD Data / Document options: • Artwork • Printed Circuit Board Assembly • Printed Circuit Fab Dwg Pkg • Schematic Diagram

7. Click Save.




149


AgilePLM for Legacy Data and Documentation Creating an Agile Document Record 6. Scroll down to the Document Details section and enter the General

Description with the appropriate Document Description.

7. Click Save.



150


AgilePLM for Legacy Data and Documentation Creating an Agile Document Record 8. Select the Attachments tab.

9. Click the Add > Files pulldown.



151



8. Select the Browse button in the Add Files window and navigate to the attachment you would like to add.

9. Click the Description field to the right and enter the title of the attachment you just added.

• Repeat steps 8 and 9 if there are multiple attachments.

10. Click the Add button.

You have successfully completed Item Create for a Legacy Agile document record.



152



AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a Raw Printed Circuit

Note: Legacy Agile ECAD Part Records are used for Printed Circuit BOMs and Printed Circuit Raw Board Documentation.



153


2. Select PCB from the Type drop-down list.


Note: PCB is used for both Raw Printed Circuit Boards and Flexes



154








155


4. Fill out the required attribute for Product Line

5. Under the Commodity Code drop-down list, select the appropriate option for the Legacy Data or Document your are creating

ECAD Commodity Code options • Flex – HDI • Flex - Rigid HDI • Flex - Rigid Standard • Flex Standard • PCB - Rigid HDI • PCB - Rigid Standard

6. Fill out the required attribute for Owner




156


4. Fill out the required attribute for Design Source.

5. Fill out the required attribute for APC.

6. Under the PCB Type drop-down list, select the appropriate option for the Legacy Data or Document your are creating.

ECAD Data / Document options: • PCB • PCB Flex • PCB Rigid Flex

7. Click Save.




157



6. Scroll down to the Document Details section and enter the General Description with the appropriate Part Description



158



7. Scroll down to the Import Export section and select No from the Contains Encryption pulldown.

8. Click Save.



159


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a Raw Printed Circuit 8. Select the Attachments tab.

9. Click the Add > Files pulldown.



160



8. Select the Browse button in the Add Files window and navigate to the attachment you would like to add.

9. Click the Description field to the right and enter the title of the attachment you just added.

• Repeat steps 8 and 9 if there are multiple attachments.


You have successfully completed Item Create for a Legacy Agile part record.



161



AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM

Note: Legacy Agile ECAD Part Records are used for Printed Circuit BOMs and Printed Circuit Raw Board Documentation.



162


2. Select PCB from the Type drop-down list.


Note: PCBA is used for both Printed Circuit Board and Flex BOM Assemblies



163








164


4. Fill out the required attribute for Product Line

5. Under the Commodity Code drop-down list, select the appropriate option for the Legacy Data or Document your are creating

ECAD Commodity Code options • Flex – HDI • Flex - Rigid HDI • Flex - Rigid Standard • Flex Standard • PCB - Rigid HDI • PCB - Rigid Standard

6. Fill out the required attribute for Owner




165


7. Fill out the required attribute for Design Source.

8. Fill out the required attribute for APC.

9. Under the PCB Type drop-down list, select the appropriate option for the Legacy Data or Document your are creating.

ECAD Data / Document options: • Backplane • Flex Assembly • PCBA

10. Click Save.




166



11. Scroll down to the Document Details section and enter the General Description with the appropriate Part Description



167



12. Scroll down to the Import Export section and select No from the Contains Encryption pulldown.

13. Click Save.



168


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 14. Select the Tool and Settings pull

down

15. Click the Import pull down



169


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 16. Select the Browse button and navigate to the BOM Variant

information

17. Select the Next button

Note: The BOM Variant information extracted from the schematic is in the BOM folder in the Project Directory



170


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 18. Select the Bill of Material radio button in the "Item" field




171


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 20. Select the Use a saved

mapping file radio button in the "Data Mapping" field.

21. Select the Browse button in the "Data Mapping" field and navigate to the saved "NewMapFile.xml file.

22. Select the Updates do not require redlining radio button in the "Redline Options" field.

23. Select the Next button.



172


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 24. Review the Attribute Mapping in the Import fields




173



26. Review the File Information on the Review Import Definition page

27. Select “Import” button

28. Close the Import Log

You have successfully completed Item Create for a Legacy Agile BOM part record



174


1. Click Create New > Changes > Change Orders from the drop-down list.

AgilePLM for Legacy Data and Documentation Creating an EC to Release Legacy Parts and Documents



175


2. Under the Type field, select EC Process from the drop-down menu.

3. Enter the remaining attributes of the new document in all the mandatory fields (denoted by *).

• Product Family • Change Category • Description of Change • Reason for Change • Affected Design Functions

4. Click Save.




176


AgilePLM for Legacy Data and Documentation Creating an EC to Release Legacy Parts and Documents 5. Enter the following attribute

information: • Reason Code • Workflow • Change Analyst

6. Click Save.



177



7. Select the Affected Items tab.



178


AgilePLM for Legacy Data and Documentation Creating an EC to Release Legacy Parts and Documents 8. Click the Add button.

9. Type in the existing part number of a Part or a Document record that you want to add to the EC as an effected item.

Tip: When you start typing in the field, the window will populate with options that match the character you are entering.

10. Click the part number to add it.

(You can repeat this step in the search window to add multiple part numbers.)

11. Press “enter” on your keyboard and all of the part numbers will be added to the EC.



179


Note: in order to release an EC with a BOM all of the children on the BOM must be at a released lifecycle status. If there are any items at a Preliminary lifecycle status then you will have to add them as an Affected Item on the EC in order to release it. 12. For each of the Affected Items Double-click the Lifecycle Phase cell to

activate the drop-down menu, and select the next phase of the lifecycle. For this example, select Development.




180


13. Define the new revision for the Affected Items. Double-click the New Rev field to activate it, and set the new revision.

In this example, the new revision value is set to 1.

14. Click Save.




181


15. Select the grey box to the left of the BOM part number, and review the items under the BOM tab.




182


16. Select each of the additional Affected Items, then navigate to the Attachments tab and attach the appropriate data and documentation objects of each record. • Raw Printed Circuit – part record • Printed Circuit Assembly Drawing – document record • Schematic Diagram – document record




183


Tip: Prior to submitting the EC, check to see if you will have any errors on the EC or with the Affected Items by doing an Audit Status.

17. Click the Actions pull down and select Audit Status.

18. If there are no errors on the Audit Status Results you are ready to proceed to Submit the EC for approval




184


19. Click Next Status pull down and select Submitted to proceed.




185


20. Enter any additional associates to notify in addition to the Change Analyst

21. Add comments to the notification as to what the EC is doing

22. Select the Finish button


You have successfully completed an EC in AgilePLM to release Legacy Data and Documentation



186


1. Click Create New > Changes > Change Orders from the drop-down list.

AgilePLM for Legacy Data and Documentation Creating an EC to Revise Legacy Parts and Documents



187


2. Under the Type field, select EC Process from the drop-down menu.

3. Fill up the remaining attributes of the new document in all the mandatory fields (denoted by *).

• Product Family • Change Category • Description of Change • Reason for Change • Affected Design Functions

4. Click Save.




188


Post an ECAD Package in AgilePLM on an EC Creating an EC to Revise Legacy Parts and Documents 5. Enter the following attribute

information: • Reason Code • Workflow • Change Analyst

6. Click Save.



189


AgilePLM for Legacy Data and Documentation Creating an EC to Revise Legacy Parts and Documents 7. Select the Tool and Settings pull

down.

8. Click the Import pull down.



190


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 9. Select the Browse button and navigate to the BOM Variant

information you want to redline the existing BOM with


Note: The BOM Variant information extracted from the schematic is in the BOM folder in the Project Directory



191


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 11. Select the Bill of Material radio button in the "Item" field




192


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 13. Select the Use a saved

mapping file radio button in the "Data Mapping" field.

14. Click the Browse button in the "Data Mapping" field and navigate to the saved "NewMapFile.xml file.

15. Select the Use the following Change for redlining radio button in the "Redline Options" field.

16. Click Next.



193


AgilePLM for Legacy Data and Documentation Creating an Agile Part Record for a BOM 17. Review the Attribute Mapping in the Import fields




194



19. Review the File Information on the Review Import Definition page

20. Select “Import” button

21. Close the Import Log

You have successfully completed a redline for a Legacy Agile BOM part on an EC record.



195



22. Select the Affected Items tab.



196



24. Type in the existing part number of a Part or a Document record that you want to add to the EC as an effected item.

Tip: When you start typing in the field the window will populate with option that match the character you are entering.

25. Click the part number to add it.

(You can repeat this step in the search window to add multiple part numbers.)

26. Press “enter” on your keyboard and all of the part numbers will be added to the EC.




197


Note: in order to release an EC with a BOM all of the children on the BOM must be at a released lifecycle status. If there are any items at a Preliminary lifecycle status then you will have to add them as an Affected Item on the EC in order to release it. 27. For each of the Affected Items Double-click the Lifecycle Phase cell to

activate the drop-down menu, and select the next phase of the lifecycle. For this example, select Pilot.




198


28. Define the new revision for the Affected Items. Double-click the New Rev field to activate it, and set the new revision.

In this example, the new revision value is set to 2.

29. Click Save.




199


30. Select the grey box to the left of the BOM part number, and review the redline items under the BOM tab.




200


31. Select each of the additional Affected Items, then navigate to the Attachments tab and attach the appropriate data and documentation objects of each record. • Raw Printed Circuit – part record • Printed Circuit Assembly Drawing – document record • Schematic Diagram – document record




201


Tip: Prior to submitting the EC, check to see if you will have any errors on the EC or with the Affected Items by doing an Audit Status.

32. Click the Actions pull down and select Audit Status.

33. If there are no errors on the Audit Status Results you are ready to proceed to Submit the EC for approval




202


34. Click Next Status pull down and select Submitted to proceed.




203


35. Enter any additional associates to notify in addition to the Change Analyst

36. Add comments to the notification as to what the EC is doing

37. Select the Finish button


You have successfully completed an EC in AgilePLM to revise Legacy Data and Documentation

Using AgilePLM in MSI - Motorolalearningmedia0.motorolasolutions.com/services/edu/...GNL1147.00E -...

Documents

Transcript of Using AgilePLM in MSI - Motorolalearningmedia0.motorolasolutions.com/services/edu/...GNL1147.00E -...