Download to read offline
Uploaded bySynergis Engineering Design Solutions
Discovering New Product Introduction using Autodesk PLM 360 – Rodney Coffey, Razorleaf & Scott Stortz, Synergis
This document summarizes a presentation about using Autodesk Fusion Lifecycle to manage new product introduction (NPI) processes. It discusses mapping NPI needs to key business applications in Fusion Lifecycle like product management, items and BOMs management, change management, and document management. It also covers building out these applications in Fusion Lifecycle through workspace architecture and functionality. Finally, it discusses lessons learned in using Fusion Lifecycle for NPI processes, including requirements gathering, building iteratively, and training users.
More Related Content
Similar to Discovering New Product Introduction using Autodesk PLM 360 – Rodney Coffey, Razorleaf & Scott Stortz, Synergis
More from Synergis Engineering Design Solutions
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Discovering New Product Introduction using Autodesk PLM 360 – Rodney Coffey, Razorleaf & Scott Stortz, Synergis
- 1. Discovering NPI using FusionLifecycle Rodney Coffey – Razorleaf Corporation Scott Stortz – Synergis Technologies
- 2. Your Session Leader RodneyCoffey Manager – PLM, Razorleaf Corporation • 10+ years Supporting the Autodesk Manufacturing Channel • Extensive Experience with Autodesk PLM 360 Services including Enterprise Implementation & Integration • His team has been partnered with Autodesk Consulting and Partners alike to provide customers with PLM and Integration services since 2011
- 3. Your Session Leader ScottStortz PLM Application Consultant, Synergis • 20+ years engineering experience in a variety of manufacturing companies • Led successful PLM implementation prior to joining Synergis
- 4. • Discover howto use Autodesk Fusion Lifecycle to capture diverse business processes • Learn how to manage your product development processes among all departments within your organization • Learn how to implement Autodesk Fusion Lifecycle and how to integrate with other business systems Class Summary
- 5. Lessons Learned Use ItBuild ItMapit Fusion Lifecycle & NPI Session Agenda
- 6. Why Autodesk FusionLifecycle • Limited IT Support • Low Cost of Entry • Easy to Administer, support • Secure with Limited infrastructure • Cloud Based • Administration & End User Experience • Configurability • Broad Application to Business Cases • Ability to integrate to other business systems • Cost of Ownership Common Customer Issues Fusion Lifecycle 360
- 7. Why Autodesk FusionLifecycle • Improvement #1: Have key suppliers directly involved in Change Notice process. • Roadblocks: • Needed VPN access and active directory account • Purchase additional licenses • Impact: • Continued to use email to loop in the suppliers • Changes were not executed by supplier • How Fusion Lifecycle provides this improvement • All apps included • Cloud based - no VPN required, no active directory account needed • 3rd party licenses are free (for enterprise level customers) Fusion Lifecycle Advantage
- 8. Why Autodesk FusionLifecycle • Improvement #2: Small, incremental improvements to forms and fields (changing fields, rearranging forms) • Roadblocks: • Complex administration and configuration • Consulting fees • Impact: • Stifled user engagement • How Fusion Lifecycle provides this improvement • Administration and configuration functionality much more simple Fusion Lifecycle Advantage
- 9. Why Autodesk FusionLifecycle • Improvement #3: Equipment Calibration (or Field Service Report, or RMA) process. • Roadblocks: • No out of the box functionality • Very complex to create workflows, forms, and fields • Impact: • Continued to use Excel, and paper based processes that were known to be inefficient • How Fusion Lifecycle provides this improvement • Autodesk created an app just for this. Awesome. • Fusion Lifecycle’s ease of use makes it realistic to implement. Fusion Lifecycle Advantage
- 10. Why Autodesk FusionLifecycle • Improvement #4: New Product Costing. • Roadblocks: • ERP remained master for financial information • Integration was too complex • Impact • Continued process of a data dump into Excel spreadsheet • BOM and costing information became less accurate as the project evolved • How Fusion Lifecycle provides this improvement • Fusion Lifecycle’s integration capabilities are much simpler – not only to setup, but also to maintain. • Rodney has a presentation from 3-4 in the Berks room Fusion Lifecycle Advantage
- 11. Companies have manydifferent methods that are not scalable or providing the desired results • Email, Spreadsheets, Network Drives, SharePoint With scattered information and a lack of control people are uninformed of: • Change - when, where, and why it took place • Where to find documentation, reports, product information Why PLM for NPI
- 12. Lessons Learned Use ItBuild ItMapit Fusion Lifecycle & NPI Session Agenda
- 13. Building the RightTeam for the Job & Identifying a Process that will get results People & Process
- 14. Build the RightTeam for the Job
- 15. The Iterative DesignProcess Map, Build It, Use It …. Build it, Use …. • Conference Room Pilots (CRP) • User Acceptance Testing (UAT) Map It Build It Use It CRPUAT
- 16. Why Fusion Lifecycleworks with the Iterative Design Process • Quickly build and show the foundation of the processes • Easily change and iterate the design and process • Facilitate functional design meetings • Helps capture many requirements in real time Fusion LC & the Iterative Design Process
- 17. Identifying your NPINeeds People & Process
- 18. Identifying the keybusiness applications that apply to NPI Identifying NPI Needs: Business Solutions Product Management • Items & BOMS • Project Management • Task Management & Validation Change Management • Change Requests • Change Orders Supplier Management • Business Audit Document Management • Revision Controlled Documents • Non-Revision Controlled Documents
- 19. Identifying the keybusiness system integration that apply to NPI Often times business systems already in place are part of the overall NPI process and must be considered for integration to Fusion Lifecycle in order to complete the NPI process Common Use Cases: Items & BOMs, Suppliers, Customers, etc. Identifying NPI Needs: Integration
- 20. The number onegoal: • Bring data and processes together in a single, easily consumed process Identifying NPI Needs: Data
- 21. Mapping out theSolution Map It
- 22. Key to Mapping: •Identify what “NPI” means to your business • Identify the individual business applications • Workspace Architecture Mapping It: Business Apps Change ManagementBOM Management Document ManagementNPI / Product Management
- 23. Keys to buildingout a solid solution • Each piece (Workspace) is part of a bigger solution • Processes need to hold each department, party accountable • Information will come from numerous systems • Facilitate a long Product Lifecycle (12 months or more) Mapping It: Workspaces Change Orders Items & BOMs DocumentsProducts Documents - Rev Doc Change Order PD - Sales PD - Engineering PD - Manufacturing Product Management I & B Management Change Management Doc Management
- 24. Mapping It: Relationships ChangeOrders Items & BOMs Documents Products Documents - Rev Doc Change Order PD - Sales PD - Engineering PD - Manufacturing PD – Name your Department
- 25. Lessons Learned Use ItBuild ItMapit Fusion Lifecycle & NPI Session Agenda
- 26. Build It: WorkspaceArchitecture Change Orders Items & BOMs Documents Products Documents - Rev Doc Change Order PD - Sales PD - Engineering PD - Manufacturing Begin by building the individual workspaces in Fusion Lifecycle
- 27. Then choose thefunctional areas of a Fusion Lifecycle workspace that are applicable: Build It: Workspace Functionality Item Details AttachmentsWorkflow Bill Of Materials Change Log MilestonesGrid Relationships
- 28. Building It: DocumentManagement Build It
- 29. Document management workspacesare used to capture important revision controlled and non revision controlled data • Documents Rev: Specifications, Data Sheets, Quality Procedures, Work Instructions • Documents: Product Photos, Marketing, Scanned Communication Document Management Documents Documents - Rev Doc Change Order Supporting Workspaces Document Type Document Sequencers
- 30. Document Management: Documents ItemDetails AttachmentsRelationships Change Log
- 31. Document Management: Documents- Rev AttachmentsRelationshipsItem Details Change Log Workflow • This workspace with setup with the proper permissions allow the administrators to show only the pertinent information to end users, vendors
- 32. Document Management: DocumentCO AttachmentsRelationshipsItem Details Change Log Workflow Managed Items
- 33. • Only releaseddata is available for consumption across vendors, and end users • Revision control allows companies to comply with important industry standards like ISO, • Pre-defined document types and numbering creates consistency across documents • Multiple document libraries allow better access control Document Management: Business Benefits
- 34. Building It: ProductManagement / NPI Build It
- 35. Product management workspacesare used to capture important product data and drive the process of taking a product through its complete lifecycle • Documents Rev: Specifications, Data Sheets, Quality Procedures, Work Instructions • Documents: Product Photos, Marketing, Scanned Communication Product Management Supporting Workspaces NPI Templates Products PD - Sales PD - Engineering PD - Manufacturing
- 36. Product Management Item DetailsAttachmentsRelationships Change Log Workflow Bill Of Materials Milestones Grid Pre-Created items Clearly defined product leads Requirements
- 37. Product Management: Workflow ProductSetup Phase 1: Concept Phase 1: DRB Phase 2: Design Phase 3: Realize Phase 4: Service Obsolete Phase 2: DRB Phase 3: DRB Obsolete: DRB Product Management workflows vary from customer to customer but most follow some sort of phase gate process
- 38. Product Management: Workflow Approvalsfor design reviews, or even customer reviews ensure that the process is followed and all parties involved in the process are held accountable. Workflow
- 39. Product Management: TaskManagement During each phase there are tasks that need to be finished in order to seek approval, and move on to the next phase. This allows product owners to hold the team accountable, and insure deliverables are complete, and on time. Grid
- 40. Product Management: Automation P1:Concept P2: Design P3: Realize P4: Service Obsolete Goals of automating the process with scripting • User Experience • Overall Product Management process, and tasks should be connected • Full Proof the process to drive the right activity to occur at the right time • Ensure that the correct people are notified at the right time Process Automation – Scripting and Business Logic
- 41. Product Management: TaskManagement During each phase there are tasks that need to be finished in order to seek approval, and move on to the next phase. This allows product owners to hold the team accountable, and insure deliverables are complete, and on time.
- 42. • Ensure thatall Product Management tasks are completed before moving to the next phase in the process • Notifications, emails, and reports ensure completion of tasks are timely and that managers can easily hold their teams accountable • Automation simplifies the user experience and creates a fuller proof process • Phase gate reporting allows managers to know where to focus resources and improvement initiatives Product Management: Business Benefits
- 43. Building It: Items& BOMs & Change Management Build It
- 44. The Items &BOMs workspace is where the items, bill of materials and all their relationship and pertinent data reside. • Relationships are built between these items and BOMs to the Products workspace to tie everything together • Some supporting documentation, CAD drawings, pdfs may be added to the attachments tab of the item itself Items BOMs & Change Management Change OrdersItems & BOMs Supporting Workspaces I & B Classification I & B Sequencers
- 45. Items BOMs Item DetailsAttachments Change Log Assoc. Workflow Bill Of Materials Where Used
- 46. Change Management: ChangeOrder Item Details Attachments Change Log Grid Managed Items Workflow
- 47. Change Management: ChangeOrder Grid Workflow
- 48. • Manage allthe Items & BOMs in a single repository • Find where all Items are used • Track Inventory of Items across different facilities • Manage the Suppliers, and quotes provided for Items & BOMs • Interconnect Product BOMs with the PLM process • Tie BOM, and document data together Items BOMs & Change Management
- 49.
- 50. Integration: • Items &BOMs • Customers • Suppliers • Products Product Management Integration:
- 51. Lessons Learned Use ItBuild ItMapit Fusion Lifecycle & NPI Session Agenda
- 52. Use it: Processto Successful Adoption Core Team Focus Groups UAT Training
- 53. Fusion Lifecycle usedto 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 Use it: Training
- 54. Lessons Learned Use ItBuild ItMapit Fusion Lifecycle & NPI Session Agenda
- 55. Requirements for MappingPhase • 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: Map It
- 56. Have an agreedupon 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: Build It
- 57. Find capable, enthusiasticadopters 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: Use It
- 58. • What aresome of the advantages of Fusion Lifecycle over traditional PLM? • What is NPI, and what does it mean to you? • What are three of the common business apps that part of or connected to NPI? Gift Cards!
- 59.
- 60. Contact Information Feel freeto follow up: Rodney Coffey Manager - PLM Email: rodney.coffey@razorleaf.com Office: 330.676.0022 x7124 Cell: 937.241.9177