AU 2015: Enterprise, Beam Me Up: Inphi's Enterprise PLM Solution (PPT)

Join the conversation #AU2015

Enterprise, Beam Me Up:

Inphi’s Enterprise PLM Solution

Dr. Robb JohnsonInphi – Director of Technology

Rodney CoffeyRazorleaf – Sr. PLM Consultant

Your Instructor

Rodney CoffeySr. PLM Consultant, Razorleaf Corporation

10+ Supporting the Autodesk Manufacturing Channel

Extensive Experience with Autodesk PLM 360 Services including

Enterprise Implementation & Integration

His team has been partnered with Autodesk Consulting to provide

customers with PLM 360 services since the product was

launched

Discover how to use Autodesk PLM 360 to capture diverse business

processes and bridge a global organization

Learn how to manage product development processes among

suppliers, vendors, and all departments within your organization

Learn how to capitalize on Autodesk PLM 360 to accommodate

complicated approval processes

Discover the benefits of integrating Autodesk PLM 360 with other

business systems such as Oracle EBS and Autodesk Vault

Class Summary

About Inphi

Why PLM?

Map It Build It Use ItLessons Learned

Agenda

Your Instructor

Dr. Robb JohnsonDirector of Technology, Inphi Corporation

15+ years of experience in semiconductor process development and

management of semiconductor suppliers

Technical face to Inphi’s semiconductor suppliers

New supplier and semiconductor process selection

Responsible for enterprise business solutions including SharePoint

and PLM

We Move Big Data Fast “Data is the new oil” – Clive Humby

We design semiconductor chips for high speed communications 80% of all internet traffic will go through an Inphi chip

About Inphi

Inphi Leads in Data Movement Interconnects

$250M Fabless semiconductor company

Founded in Nov. 2000, IPO in Nov. 2010

Optical, networking, memory interconnect leader for service providers, data centers

460+ employees worldwide, 75% engineering

Focused on success of system and module customers worldwide

Innovative breakthroughs, solid execution resulting in many industry’s firsts

How Fast?

12.6 Terabits per second

396 uncompressed HD movies per second

How Big?

5 Zettabytes

700 Gigabytes of data for every human

1.2 trillion high definition movies

How Far?

Optical

3,000km

Networking

100s meters

Memory

Millimeters

For Whom?

Carrier and Service Providers

Data Centers

Long-Haul Metro

Cloud Enterprise

About Inphi

Why PLM?

Map It Build It Use ItLessons Learned

Our customers demand high quality Inphi products go into expensive systems which are expected to be in use

for >10 years

Inphi grew from a small company in a single location to

a 460+ employee company with world wide locations Processes and procedures became harder to manage and enforce

Things done differently at each location

Needed better visibility to data in the form of data mining and reporting

Why PLM?

We had “PLM” via many different methods that were not

scalable nor providing the desired results Email, spreadsheets, network drives, SharePoint

Ineffective / unenforced processes and procedures

Drive-by communication

With scattered information and lack of control, people were

uninformed of a change – when or why it happened

Inphi’s “PLM” Problem

Identifying the problem – Business Solutions

Quality Management

Return Material Authorization

Failure Analysis

Corrective Actions

Change Management

Supplier Management

Product Management

Items & BOMs

Project Management

Issue Tracking

Document Management

We identified key areas that needed addressing

We knew that existing Business Systems had to be

taken into account – This meant Integration

Finance utilizing Oracle EBS

Sales utilizing salesforce

Engineering utilizing Autodesk Vault

Identifying the problem – Integration

We evaluated a number of PLM systems

Customer demos and references

Requirements:

Limited IT support

Easy to administer, configure and support

Low cost of entry and 5 year cost of ownership

Strong technical support

Able to address all the business issues (and more) we identified

Secure

Why We Chose Autodesk PLM 360

The World of PLM at Inphi

Product Management

Quality

Management

Foundry

Management

Customers

Supplier

Management

Legal

Contracts

Equipment

Document

Management

About Inphi

Why PLM?

Map It Build It Use ItLessons Learned

Building the Right Team for the Job &

Identifying a Process that will get Success

Defined group of Subject Matter Experts (SME)

Core Team

Map it, Build It, Use It…..Build It, Use It…

Conference Room Pilots (CRP)

User Acceptance Testing (UAT)

What is the Iterative Design Process

Map It Build It Use It

CR

PU

AT

Why PLM 360 worked for the Iterative Design Process

Quickly build and show the foundation of the processes

Easily change and iterate the design and process

Facilitated functional design meeting

Helped capture many requirements real time

PLM 360 and the Iterative Design Process

Mapping It

Identifying our NPI Needs

Sitting down with the Core Team we identified key

areas that we knew Autodesk PLM 360 could help with

around NPI / PD

Identifying the NPI / PD Needs of Inphi

Document Management

Change Management

Project Management

Item & BOMs Management

NPI Tasks

Approvals

Workflow

Revision Control

Key to Mapping:

Identify what “NPI” really meant

to Inphi

Identify the individual business

applications within PLM 360

Workspace Architecture

Mapping out our solution

Change Management

Items & BOMs

Document Management

NPI / Product Management

Project Management

The biggest requirement

Pulling it all together

Identifying the NPI / PD Needs of Inphi

We gathered requirements and data from:

Existing Procedures

Workflows

Fields

Out of the Heads of our Core Team:

Tasks

Document Types

Approval Protocol

Gathering Requirements

About Inphi

Why PLM?

Map It Build It Use ItLessons Learned

We knew from the beginning each

piece was part of a bigger solution

The process needed to hold

everyone accountable

Information coming from other

systems – Integration

Facilitate 12 – 16 month Product

Development Cycle

Building out our solution

Engineering Projects

Operations Projects

NPI Engineering

NPI Operations

NPI Marketing

Items & BOMs / ECO

Document Libraries

Products - NPI

Building out our solution

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

We began by building the individual workspaces with

the common PLM 360 Capabilities:

Workspace Architecture

Item Details AttachmentsWorkflow

Bill Of Materials

Change Log

MilestonesGrid Relationships

Building It

Document Management

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

Document Management

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

Document Management

Revision Controlled Documents

Documents

Document Change Order

Engineering Documents – Rev Controlled

Engineering Documents

Document Type

Supporting Workspaces

Document Libraries

Document Sequencers

Non-Revision Controlled Document Workspaces

Attachments WorkflowRelationshipsDocument Libraries

State for documents that do

not require approval

Revision Controlled Document Workspaces

Document Libraries Attachments Assoc. WorkflowRelationships

Revision controlled

documents for documents

sent to customers and

suppliers and for ISO

procedures

Ensure that only the latest

copy is available

Document Change Order Workspaces

Document Change Order Affected Items Attachments

Workflow

Relationships

Documents Automation

Document Type

Division

Type

Sub-Type

3 Letter Acronym

Approval (Yes, No)

Approval Tiers (1,2,3)

Documents Automation

Document Type

Document Sequencers

Revision Controlled Docs

Document Picklist {}

Our executives did not want to approve until others had approved

We wanted the system to determine who should approve, not the users

Multi-Tier Approval

4 serial tiers

Parallel approval within tier

Documents Automation

Document Type

Approval Lists Approval Group Lists Document Change Order

Ensure the latest released version is

available to everyone

Pre-defined document types and numbering

creates consistency

Multiple document libraries allow us to

better control access permissions

Multiple tier approval allows details to be

sorted out before asking executives to

approve

Pre-set list of approvers ensures the right

people are approving and ensures

compliance with ISO procedures

Document Libraries – Benefit to the Business

Building It

New Product Introduction

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

New Product Introduction / Product Management

Products - NPI

Products - NPI BOM Relationships Workflow

Automatically “spawned” items

Workflow dates recorded in item details

Product leads clearly identified

Products - NPI

Products - NPI Workflow

Product Setup

Concept Phase (C)

Investigation Phase (I)

Development Phase (D)

Engineering Sample Phase (S)

Pre-Prod Phase (P)

Mass Prod Phase (M)

End of Life

C Exit Checkpoint

I Exit Checkpoint

D Exit Checkpoint

S Exit Checkpoint

P Exit Checkpoint

M Exit Checkpoint

New Product Introduction / Product Management

NPI Engineering NPI OperationsNPI Marketing

Supporting Workspace

NPI Templates

Products - NPI

NPI – Marketing, Operations, Engineering

NPI Item Details

When the due date is within 30 days and has not been marked

completed, the “Owner” is e-mailed a reminder every week

NPI – Marketing, Operations, Engineering

NPI Grid (Tasks)

Putting all the pieces together - Process

C I D PS End of LifeM

Process Automation – Scripting & Business Logic

Goals:

People: User Interface, Clicks, One Stop Shop

Process: NPI, Tasks

Technology: Drive the right activity to occur at the right time

Marketing Operations Engineering

NPI Automation – Document Spawning

NPI Docs Action

Phase Documents Exit Presentations

Product Requirement

Division NPI Marketing

Operations

Engineering

NPI Automation - Tasks

Division

Phase

Description

Owner

Document

Complete? (Yes, No)

NPI Templates

NPI Automation – Tasks

NPI Templates Grid

Pre-defined set of tasks to be completed at each phase by each organization Documented in our ISO procedures (QSP#)

Owner role identified

NPI Automation – Tasks

NPI Templates NPI Marketing NPI Engineering NPI OperationsAction

Manage Multiple Division Tasks in One Place

Repeat Phase Process if needed

Manage configuration of tasks for change

NPI Automation – Tasks

NPI Tasks ValidationCondition

Ensure that all tasks are completed prior

to each gate approval Ensures compliance with ISO procedures

Ensures quality of Inphi product

Reminder e-mails ensure completion of

tasks is timely

Automation of document creation

(spawning) simplifies user experience

Reporting on time to complete projects

Reporting on non-completed tasks allows

PM to know where to focus resources

NPI – Benefit to the Business

Building It

Project Management

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

Project Management

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

Operations and Engineering organizations can have many

projects and sub-projects that are one checkbox at the NPI level Both organizations have a detailed ISO procedure for each NPI phase

Needed a better way to track all the work being done to

complete the NPI task

Needed a way to easily see all the different development items

Project Management

Engineering Projects

Operations Projects

NPI Engineering

NPI Operations

Document Libraries

Engineering & Operations Projects

Attachments WorkflowRelationshipsEng & Ops Projects

Project type drives different workflow and spawned documents

Team members (informational and used for approvals)

Workflow state recorded for simplified reporting

Link to main NPI for simplified navigation

Engineering & Operations Projects

Workflow

Project Setup

Definition

Design

Implementation

Released

PDR Review

EDR Review

FDR Review

Validation

Design Project

Eng & Ops Projects

Engineering & Operations Projects

Configure workspace view to see project status

Utilize the BOM tab

to show relationships

to Parent NPI, other

projects, and

spawned documents

Display workspace

and status of the item

in the item descriptor

Quick access to file

attachments

BOM for Item Relationships

Action

Quickly find and see the status

of projects, their status and their

spawned documents

Ensure completion of

development tasks such as

design reviews and other

required documents

Know where to focus resources

Eng & Ops Projects – Benefit to the Business

Building It

Items & BOMs

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

Items & BOMs & Change Management

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

Items & BOMs & Change Management

Change ManagementItems & BOMs

Supporting Workspaces

Classification Structure - Products

Items & BOMs Classification

Items & BOMs & Change Management

Attachments Assoc. WorkflowBOMItems & BOMs Where Used

ROB BOM Screen shot

Items & BOMs & Change Management

Affected Items WorkflowGridChange Orders Attachments

Grid tab used to track action items

requested by CCB

Items & BOMs & Change Management

Change Orders Grid

Items & BOMs Automation

Items & BOMs Classification

Building It

Connecting Systems with Integration

Breaking down the Solution Elements – Integration

Items & BOMs / Document Management Integration:

Breaking down the Solution Elements – Integration

Items & BOMs Integration:

Engineering, Operations, and Marketing enter Product data into

PLM 360

Procurement, Planners, Finance add important information to the

Product after development in Oracle EBS

Breaking down the Solution Elements – Integration

Building the Integration

Both Oracle EBS & PLM 360 were steady state environments

All fields and workflow states to be captured as part of this

integration were considered early on in the requirements

gathering phase

PLM 360 business applications were piloted before Integration

Used with out Oracle EBS in production

Jitterbit installed On-Premise

Production

Development

Breaking down the Solution Elements – Integration

Customer Integration

Customer information is needed in PLM 360 to create

relationships to items

Customers are created in Oracle and pushed into PLM 360 and

salesforce via Jitterbit integration

Breaking down the Solution Elements – Integration

Supplier Integration

The supplier on-boarding and review process is managed by PLM

360

Supplier financial information is entered in Oracle

Supplier status is managed in PLM 360 and pushed to Oracle

Breaking down the Solution Elements – Integration

When, who, and why something was changed visible to

all

Information (drawings) easily found in Vault with

integration

Reduce input errors when creating items and BOMs in

Oracle

Items & BOMs & Change Management – Benefits

NPI Solution Development Summary

Engineering Projects Operations Projects

NPI Engineering NPI OperationsNPI Marketing

Items & BOMs / ECO Document Libraries

Products - NPI

About Inphi

Why PLM?

Map It Build It Use ItLessons Learned

Process to Successful Adoption

Core Team

Focus Groups

UAT

Training

PLM 360 used to manage training Dedicated training tenant

Workspaces

Training Courses (agenda, training material)

Training (track who attended training)

Training Item (create items, add attachments, move through workflow)

Training sessions

Initial Roll-out: Multiple large sessions held at every site

On-going: Self-paced training workspace for PLM basics

Prerequisite for production tenant access

Training & Adoption

Adoption by the Numbers

Unique User Logins

Average ~60 per day

300 last 30 days

361 last 90 days

Inphi PLM 360 Usage

Last 90 days

About Inphi

Why PLM?

Map It Build It Use ItLessons Learned

Requirements for Mapping Phase

Core Team + Subject Matter Experts

PLM Software Matter Expert

The Know and No

“Know” the scope of what you are building

Don’t be afraid to say “No”

Have a third party document the requirements

All parties confirm the requirements

Avoid the “I said A, you heard B, then built C” scenario

Lessons Learned – Mapping It

Have an agreed upon plan

Document the foundation

Workspace architecture and workflow first

Automate later. Moving targets are hard to hit.

Integrate last when the workflow is static

Moving targets get even harder to hit when integration is involved

Limit changes as you near the end

Only minor changes past core team acceptance

Stand by what you built

Lessons Learned – Building It

Find capable, enthusiastic adopters for training

Likely to give good, constructive feedback

Likely to play in the system and find things you may have missed

Likely to stay positive and spread the word

Have a wingman in your early training sessions

Allows you to focus on the adopters while they document

changes

Lessons Learned – Using It

The World of PLM at Inphi

Product Management

Quality

Management

Foundry

Management

Customers

Supplier

Management

Legal

Contracts

Equipment

Document

Management

Successful adoption of PLM 360

with a wide variety of business

applications around the globe

Improved:

Compliance to ISO procedures

Accuracy and Efficiency

Product Management Visibility

Document Management Visibility

Autodesk is a registered trademark of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not

responsible for typographical or graphical errors that may appear in this document. © 2015 Autodesk, Inc. All rights reserved.