The document summarizes an Autodesk PLM 360 Success Story presentation about how Inphi implemented PLM 360 to improve its quality management processes. It describes how Inphi grew and needed a scalable solution to manage quality incidents, returns, failures, corrective actions and other processes across locations. It details how Inphi mapped its needs, built out the various quality workspaces using an iterative design process, and integrated with other systems like Salesforce. The implementation helped Inphi improve visibility, reporting, and resolution of quality issues.
The document is a presentation on lessons learned from over 12 years of implementing DriveWorks. It discusses the importance of having a flexible process and tool. Other key lessons include planning for the unexpected, focusing on the start, end, and middle phases of a project, letting DriveWorks automate repetitive tasks, prioritizing user needs, and realizing that SOLIDWORKS is just one program in the workflow. Standards are important but not a reason to avoid automation. The presentation provides several "Sherpaisms" or quotes summarizing the lessons.
This SolidWorks World 2007 presentation from Paul Gimbel of Razorleaf Corporation focuses on preparing your company, your engineering design process, and your SolidWorks models for design automation.
AU 2015: Enterprise, Beam Me Up: Inphi's Enterprise PLM Solution (PPT)Razorleaf Corporation
In this course you will learn how Inphi Corporation has capitalized on the Autodesk PLM 360 tool to
manage its enterprise business processes; including new product introduction, items and BOMs, change
management, quality management, supplier management and much more. Share Inphi’s excitement
about improved visibility of organizational performance to project managers, executives, and indeed the
entire global organization by incorporating all of these business applications onto a single platform.
Understand how Inphi has improved compliance to their NPI and Quality processes by implementing task
management with workflow validation and a tiered approval process. Learn how Inphi tracks their
development process through the use of connected, but dedicated, workspaces for Engineering,
Marketing and Operations. See how Inphi leverages Jitterbit to integrate with several other business
systems such as salesforce.com, Oracle EBS, and Autodesk Vault. By attending this class, you will go on a
tour of how Autodesk PLM 360 has transformed Inphi’s business and could potentially transform yours as
well.
Discovering New Product Introduction (NPI) using Autodesk Fusion LifecycleRazorleaf Corporation
In this session you will learn how to capitalize on Autodesk Fusion Lifecycle to manage your enterprise business processes; including new product introduction, items and BOMs, change management, document management and many more. We will discuss how to improve your organizations performance and product data visibility throughout your organization by incorporating different business applications onto a single platform. Understand how to improve compliance to your NPI and Quality processes by implementing task management with workflow validation. Learn how to track your development process through the use of connected, but dedicated, workspaces for different departmental tasks. Our hope is that attending this class will give you a tour of how Autodesk Fusion Lifecycle can transform your business, and prepare you for the next steps in implementing Fusion Lifecycle for NPI.
This document discusses moving from a document-centric to item-centric approach for managing products and bills of materials. Some key challenges of change include keeping multiple revisions of drawings, models, and items in sync and giving up control of the product structure. However, benefits include reducing CAD modeling efforts, enabling cross-discipline collaboration early, and allowing non-geometric items in bills of materials. Following configuration management standards and starting with small beneficial changes can help avoid issues when making the transition.
The document discusses tweaking 3DLive on ENOVIA SmarTeam. It provides an overview of 3DLive and its system architecture, including how it connects to applications like CATIA, ENOVIA, and DELMIA. It then covers hands-on demonstrations of working with 3DLive through semantic searching, navigation, and exploration. The document also discusses tweaking client customizations like search types and tree colors. Advanced topics covered include scripting, collaboration tools, and licensing.
Design communication used to be about telling a story - communicating the how's and why's of a design to multiple audiences. SolidWorks does a great job of providing all of the actors (no pun intended), but 3DVIA Composer makes the story come alive!
Science got really interesting when we broke chemicals down to the atomic level – it drove a new level of understanding and opened up new possibilities. This session will discuss how breaking up traditional engineering deliverables (drawings, for example) into their atomic parts (geometry, BOMs, rev history, etc) can open up some interesting possibilities for optimizing processes. This session takes a practical look at what Dassault means when they talk abut a “data-driven” architecture.
Presented by Jonathan Scott
The document is a presentation on lessons learned from over 12 years of implementing DriveWorks. It discusses the importance of having a flexible process and tool. Other key lessons include planning for the unexpected, focusing on the start, end, and middle phases of a project, letting DriveWorks automate repetitive tasks, prioritizing user needs, and realizing that SOLIDWORKS is just one program in the workflow. Standards are important but not a reason to avoid automation. The presentation provides several "Sherpaisms" or quotes summarizing the lessons.
This SolidWorks World 2007 presentation from Paul Gimbel of Razorleaf Corporation focuses on preparing your company, your engineering design process, and your SolidWorks models for design automation.
AU 2015: Enterprise, Beam Me Up: Inphi's Enterprise PLM Solution (PPT)Razorleaf Corporation
In this course you will learn how Inphi Corporation has capitalized on the Autodesk PLM 360 tool to
manage its enterprise business processes; including new product introduction, items and BOMs, change
management, quality management, supplier management and much more. Share Inphi’s excitement
about improved visibility of organizational performance to project managers, executives, and indeed the
entire global organization by incorporating all of these business applications onto a single platform.
Understand how Inphi has improved compliance to their NPI and Quality processes by implementing task
management with workflow validation and a tiered approval process. Learn how Inphi tracks their
development process through the use of connected, but dedicated, workspaces for Engineering,
Marketing and Operations. See how Inphi leverages Jitterbit to integrate with several other business
systems such as salesforce.com, Oracle EBS, and Autodesk Vault. By attending this class, you will go on a
tour of how Autodesk PLM 360 has transformed Inphi’s business and could potentially transform yours as
well.
Discovering New Product Introduction (NPI) using Autodesk Fusion LifecycleRazorleaf Corporation
In this session you will learn how to capitalize on Autodesk Fusion Lifecycle to manage your enterprise business processes; including new product introduction, items and BOMs, change management, document management and many more. We will discuss how to improve your organizations performance and product data visibility throughout your organization by incorporating different business applications onto a single platform. Understand how to improve compliance to your NPI and Quality processes by implementing task management with workflow validation. Learn how to track your development process through the use of connected, but dedicated, workspaces for different departmental tasks. Our hope is that attending this class will give you a tour of how Autodesk Fusion Lifecycle can transform your business, and prepare you for the next steps in implementing Fusion Lifecycle for NPI.
This document discusses moving from a document-centric to item-centric approach for managing products and bills of materials. Some key challenges of change include keeping multiple revisions of drawings, models, and items in sync and giving up control of the product structure. However, benefits include reducing CAD modeling efforts, enabling cross-discipline collaboration early, and allowing non-geometric items in bills of materials. Following configuration management standards and starting with small beneficial changes can help avoid issues when making the transition.
The document discusses tweaking 3DLive on ENOVIA SmarTeam. It provides an overview of 3DLive and its system architecture, including how it connects to applications like CATIA, ENOVIA, and DELMIA. It then covers hands-on demonstrations of working with 3DLive through semantic searching, navigation, and exploration. The document also discusses tweaking client customizations like search types and tree colors. Advanced topics covered include scripting, collaboration tools, and licensing.
Design communication used to be about telling a story - communicating the how's and why's of a design to multiple audiences. SolidWorks does a great job of providing all of the actors (no pun intended), but 3DVIA Composer makes the story come alive!
Science got really interesting when we broke chemicals down to the atomic level – it drove a new level of understanding and opened up new possibilities. This session will discuss how breaking up traditional engineering deliverables (drawings, for example) into their atomic parts (geometry, BOMs, rev history, etc) can open up some interesting possibilities for optimizing processes. This session takes a practical look at what Dassault means when they talk abut a “data-driven” architecture.
Presented by Jonathan Scott
You will learn about the key aspects of the DevOps cycle including:
Continuous Business Planning
Collaborative Development
Continuous Testing
Continuous Release & Deployment
Continuous Monitoring
Continuous Customer Feedback & Optimization
Whether you are Business Analyst, Program Manager, Process Specialist or Tool Specialist, this will be a great session to help you learn about building better solutions.
This presentation outlines how Suncorp has adopted Agile scrum and Lean kanban to effectively and efficiently deliver IT Service Management. This presentation was given at the BMC Remedy User Group forums in Sydney & Melbourne, Australia in November 2013.
The document discusses how DevOps can help transform enterprises from traditional slow and siloed software development processes to more agile and collaborative processes. It introduces a "Sonar model" to visualize how DevOps establishes feedback loops between development, testing, operations, and business users to continuously improve products and give businesses a competitive advantage. The model shows how Agile development, DevOps practices like continuous integration and delivery, and incorporating long-term business feedback can work together to achieve project, product, and business goals.
This presentation attempts to apply the missing science behind being successful with DevOps. Many DevOps practitioners are missing the science of Organizational Behavior and Organizational Development that are critical in the bringing about the desired DevOps change they are seeking
Agile and Continuous Delivery for Audits and Exams - DC Continuous Delivery M...Simon Storm
The document provides tips for auditors and examiners to better prepare for audits when using agile and continuous delivery practices. It recommends socializing plans for process changes to avoid surprises. It also suggests demonstrating expertise in agile and continuous delivery through training and certifications. Continuous delivery practices like infrastructure as code, static code analysis, automated testing, and repository management make the development process more auditable. The tips emphasize digitizing documentation, logging pipeline activity, and capturing metrics to demonstrate maturity. Ensuring quality practices like keeping QA involved, logging deployments, and code reviews with pull requests can help pass audits. Finally, it recommends getting ahead of outstanding risks like access controls and separation of duties when using tools like Jenkins and Git
The Business Analysts Role in Agile Software Developmentallan kelly
The document discusses the role of business analysts in agile software development. It argues that the product owner role is often filled by a business analyst. While business analysts take a backseat in early agile adoption, their role becomes more important as teams become more effective in delivering business needs. Specifically, business analysts are key to reducing unnecessary work through improved analysis and requirements. The document recommends a ratio of one business analyst for every 3-7 developers, depending on how stable the product is and how rapidly requirements change.
Agile Scrum Master is an advanced level Agile Project Management course that is ideal for individuals and enterprises that are looking to gain a comprehensive understanding of Agile methodologies and Scrum practices and covers Scrum Master role with regards to facilitating the Scrum team that adheres to Scrum theory, practices, and rules.
Agile and Scrum Master Certification training course accredited by EXIN is ideal for software developers, project team members, team leads, architects, project managers, scrum team members, scrum managers, scrum masters, teams transitioning to scrum, and any one who is part of IT and project management teams working on projects.
To know more about Agile Scrum Master Certification training worldwide,
please contact us at -
Email: support@invensislearning.com
Phone - US +1-910-726-3695,
Website: https://www.invensislearning.com
by Brad Appleton,
Presented August 2006 at Architecture & Design World 2006; Chicago, IL USA
Software Configuration Management Patterns for Agile Software Architectures.
The document provides an agenda for a presentation on the role of a business analyst on Agile projects. The agenda includes an overview of Agile, the role of a business analyst on traditional and Agile projects, why business analysts are important for project success, and a question and answer session. The presenter is Bill Gaiennie who has 17 years of software development experience and has trained over 500 teams on Agile.
This document discusses agile adoption in real world contexts. It emphasizes that agile adoption takes time, typically 3-5 years, and requires executive commitment. Common pitfalls include terminology abuse and an overreliance on user stories without considering other requirements. Automating processes through continuous integration is important for agile development. While agile principles have remained relevant, some argue the manifesto could be updated to reflect a greater focus on learning and customer empathy over just responding to change. The presentation concludes with questions about bringing change to companies, encouraging reluctant employees, and measuring agile maturity.
The document provides an overview of Agile development methods. It discusses what Agile is, why it is important, and how difficult it can be to implement. Specifically, it defines Agile as an iterative approach that emphasizes adaptation, incremental delivery, and collaboration. It then summarizes the Scrum framework, noting its core roles, meetings, and iterative process for completing work in short cycles.
Scrum is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to deliver increments of a product. Scrum roles include the Product Owner who represents stakeholders, the Development Team who does the work, and the Scrum Master who facilitates the process. Scrum ceremonies like daily stand-ups, sprint reviews and retrospectives provide visibility and opportunities to inspect and adapt the process as needed.
This document outlines the seven steps to developing a successful Office 365 roadmap: 1) Define organizational goals and strategy, 2) Identify current user issues, 3) Group issues into addressable problem areas, 4) Evaluate Office 365 technologies to address problems, 5) Create the roadmap, 6) Develop success criteria, and 7) Revisit the roadmap regularly. The presenter emphasizes starting with goals and current problems, mapping issues to technologies like OneDrive and Teams, and creating measurable success criteria to guide the roadmap.
Adam Ochs presented at the March 2018 Sharepoint Fest D.C. on developing an Office 365 roadmap. He discussed that an Office 365 roadmap should communicate an organization's strategy and path for productivity technologies over major steps. The seven steps to building a successful roadmap included: 1) defining goals and strategy, 2) identifying current user issues, 3) grouping issues into problem areas, 4) evaluating Office 365 technologies, 5) creating the roadmap, 6) developing success criteria, and 7) regularly revisiting and updating the roadmap. Developing a comprehensive roadmap is important for strategic planning and communicating an organization's path for Office 365.
Agile is a philosophy for delivering solutions that embraces and promotes evolutionary change throughout the life-cycle of a product. Many teams and organizations have been using Agile to, deliver software more timely, increase quality, and ultimately increase customer satisfaction.
These planning levels were originally described by Hubert Smits in the whitepaper "5 Levels of Agile Planning: From Enterprise Product Vision to Team Stand-up".
The document discusses how ITIL and DevOps approaches can work together at a large bank, ING. It describes how ING transitioned to more agile development methods over time from 2011-2015. There was initially a divide between risk management wanting to use full ITIL and DevOps teams finding ITIL too administrative. However, the document proposes ways to make ITIL processes more lean and integrated with agile approaches. For example, reserving sprint capacity for incidents, minimizing technical debt, and automating configuration management. The conclusion is that ITIL and agile/DevOps are not in conflict and both provide value when the processes are made lean and both sides understand each other's expertise.
How "Agile" helps Localization with an old DilemaMatthias Caesar
Localization is often considered and "after-tought" and is only planned after development is completed or near completion. This presentation containts a case study where Agile helped localization to become part of the SAP development project.
DevOps Kaizen: Find and Fix What is Really Behind Your Problemsdev2ops
This document provides an overview of DevOps Kaizen, which is a methodology for continuous improvement in DevOps. It discusses how Kaizen focuses on continuously improving the flow of work through scientific problem-solving approaches and total workforce engagement. The document outlines elements of a DevOps Kaizen program, including making work processes visible, planning improvements, and overcoming barriers to change. Techniques for process mapping, identifying inefficiencies, and creating improvement plans are also presented.
ome teams find it difficult to measure the success (or failure) of Agile projects. In many cases this is because the link between process and technology is absent and the right tools are not being used - or are not being used in the right way. In this presentation we will introduce Atlasssian products that bring agile reporting to life.
Why We Need Architects (and Architecture) on Agile ProjectsRebecca Wirfs-Brock
This is an updated version of this talk which I will present at Agile 2013.
The rhythm of agile software development is to always be working on the next known, small batch of work. Is there a place for software architecture in this style of development? Some people think that software architecture should simply emerge and doesn’t require ongoing attention. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration. Complex software systems have lots of moving parts, dependencies, challenges, and unknowns. Counting on the software architecture to spontaneously emerge without any planning or architectural investigation is at best risky.
So how should architecting be done on agile projects? It varies from project to project. But there are effective techniques for incorporating architectural activities into agile projects. This talk explains how architecture can be done on agile projects and what an agile architect does.
This document summarizes an automation presentation given by Paul Gimbel. It discusses using Excel, VBA, and other tools to automate design processes in SolidWorks. Key points include using Excel for user interfaces, VBA for custom functions and macros, and integrating Excel and SolidWorks through macros and the SolidWorks API. Programming best practices like documentation and testing are also covered.
The document discusses how product structure is an important tool for product development teams that can help with communication, division of responsibilities, and integration across design, engineering, and manufacturing disciplines. It provides examples of challenges teams face without a clear product structure and recommends establishing a detailed product structure early in the development process using the right tools. The document advises getting management support, identifying needs and resources, prioritizing initiatives, and proceeding in a phased approach to implement better product structure practices.
You will learn about the key aspects of the DevOps cycle including:
Continuous Business Planning
Collaborative Development
Continuous Testing
Continuous Release & Deployment
Continuous Monitoring
Continuous Customer Feedback & Optimization
Whether you are Business Analyst, Program Manager, Process Specialist or Tool Specialist, this will be a great session to help you learn about building better solutions.
This presentation outlines how Suncorp has adopted Agile scrum and Lean kanban to effectively and efficiently deliver IT Service Management. This presentation was given at the BMC Remedy User Group forums in Sydney & Melbourne, Australia in November 2013.
The document discusses how DevOps can help transform enterprises from traditional slow and siloed software development processes to more agile and collaborative processes. It introduces a "Sonar model" to visualize how DevOps establishes feedback loops between development, testing, operations, and business users to continuously improve products and give businesses a competitive advantage. The model shows how Agile development, DevOps practices like continuous integration and delivery, and incorporating long-term business feedback can work together to achieve project, product, and business goals.
This presentation attempts to apply the missing science behind being successful with DevOps. Many DevOps practitioners are missing the science of Organizational Behavior and Organizational Development that are critical in the bringing about the desired DevOps change they are seeking
Agile and Continuous Delivery for Audits and Exams - DC Continuous Delivery M...Simon Storm
The document provides tips for auditors and examiners to better prepare for audits when using agile and continuous delivery practices. It recommends socializing plans for process changes to avoid surprises. It also suggests demonstrating expertise in agile and continuous delivery through training and certifications. Continuous delivery practices like infrastructure as code, static code analysis, automated testing, and repository management make the development process more auditable. The tips emphasize digitizing documentation, logging pipeline activity, and capturing metrics to demonstrate maturity. Ensuring quality practices like keeping QA involved, logging deployments, and code reviews with pull requests can help pass audits. Finally, it recommends getting ahead of outstanding risks like access controls and separation of duties when using tools like Jenkins and Git
The Business Analysts Role in Agile Software Developmentallan kelly
The document discusses the role of business analysts in agile software development. It argues that the product owner role is often filled by a business analyst. While business analysts take a backseat in early agile adoption, their role becomes more important as teams become more effective in delivering business needs. Specifically, business analysts are key to reducing unnecessary work through improved analysis and requirements. The document recommends a ratio of one business analyst for every 3-7 developers, depending on how stable the product is and how rapidly requirements change.
Agile Scrum Master is an advanced level Agile Project Management course that is ideal for individuals and enterprises that are looking to gain a comprehensive understanding of Agile methodologies and Scrum practices and covers Scrum Master role with regards to facilitating the Scrum team that adheres to Scrum theory, practices, and rules.
Agile and Scrum Master Certification training course accredited by EXIN is ideal for software developers, project team members, team leads, architects, project managers, scrum team members, scrum managers, scrum masters, teams transitioning to scrum, and any one who is part of IT and project management teams working on projects.
To know more about Agile Scrum Master Certification training worldwide,
please contact us at -
Email: support@invensislearning.com
Phone - US +1-910-726-3695,
Website: https://www.invensislearning.com
by Brad Appleton,
Presented August 2006 at Architecture & Design World 2006; Chicago, IL USA
Software Configuration Management Patterns for Agile Software Architectures.
The document provides an agenda for a presentation on the role of a business analyst on Agile projects. The agenda includes an overview of Agile, the role of a business analyst on traditional and Agile projects, why business analysts are important for project success, and a question and answer session. The presenter is Bill Gaiennie who has 17 years of software development experience and has trained over 500 teams on Agile.
This document discusses agile adoption in real world contexts. It emphasizes that agile adoption takes time, typically 3-5 years, and requires executive commitment. Common pitfalls include terminology abuse and an overreliance on user stories without considering other requirements. Automating processes through continuous integration is important for agile development. While agile principles have remained relevant, some argue the manifesto could be updated to reflect a greater focus on learning and customer empathy over just responding to change. The presentation concludes with questions about bringing change to companies, encouraging reluctant employees, and measuring agile maturity.
The document provides an overview of Agile development methods. It discusses what Agile is, why it is important, and how difficult it can be to implement. Specifically, it defines Agile as an iterative approach that emphasizes adaptation, incremental delivery, and collaboration. It then summarizes the Scrum framework, noting its core roles, meetings, and iterative process for completing work in short cycles.
Scrum is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to deliver increments of a product. Scrum roles include the Product Owner who represents stakeholders, the Development Team who does the work, and the Scrum Master who facilitates the process. Scrum ceremonies like daily stand-ups, sprint reviews and retrospectives provide visibility and opportunities to inspect and adapt the process as needed.
This document outlines the seven steps to developing a successful Office 365 roadmap: 1) Define organizational goals and strategy, 2) Identify current user issues, 3) Group issues into addressable problem areas, 4) Evaluate Office 365 technologies to address problems, 5) Create the roadmap, 6) Develop success criteria, and 7) Revisit the roadmap regularly. The presenter emphasizes starting with goals and current problems, mapping issues to technologies like OneDrive and Teams, and creating measurable success criteria to guide the roadmap.
Adam Ochs presented at the March 2018 Sharepoint Fest D.C. on developing an Office 365 roadmap. He discussed that an Office 365 roadmap should communicate an organization's strategy and path for productivity technologies over major steps. The seven steps to building a successful roadmap included: 1) defining goals and strategy, 2) identifying current user issues, 3) grouping issues into problem areas, 4) evaluating Office 365 technologies, 5) creating the roadmap, 6) developing success criteria, and 7) regularly revisiting and updating the roadmap. Developing a comprehensive roadmap is important for strategic planning and communicating an organization's path for Office 365.
Agile is a philosophy for delivering solutions that embraces and promotes evolutionary change throughout the life-cycle of a product. Many teams and organizations have been using Agile to, deliver software more timely, increase quality, and ultimately increase customer satisfaction.
These planning levels were originally described by Hubert Smits in the whitepaper "5 Levels of Agile Planning: From Enterprise Product Vision to Team Stand-up".
The document discusses how ITIL and DevOps approaches can work together at a large bank, ING. It describes how ING transitioned to more agile development methods over time from 2011-2015. There was initially a divide between risk management wanting to use full ITIL and DevOps teams finding ITIL too administrative. However, the document proposes ways to make ITIL processes more lean and integrated with agile approaches. For example, reserving sprint capacity for incidents, minimizing technical debt, and automating configuration management. The conclusion is that ITIL and agile/DevOps are not in conflict and both provide value when the processes are made lean and both sides understand each other's expertise.
How "Agile" helps Localization with an old DilemaMatthias Caesar
Localization is often considered and "after-tought" and is only planned after development is completed or near completion. This presentation containts a case study where Agile helped localization to become part of the SAP development project.
DevOps Kaizen: Find and Fix What is Really Behind Your Problemsdev2ops
This document provides an overview of DevOps Kaizen, which is a methodology for continuous improvement in DevOps. It discusses how Kaizen focuses on continuously improving the flow of work through scientific problem-solving approaches and total workforce engagement. The document outlines elements of a DevOps Kaizen program, including making work processes visible, planning improvements, and overcoming barriers to change. Techniques for process mapping, identifying inefficiencies, and creating improvement plans are also presented.
ome teams find it difficult to measure the success (or failure) of Agile projects. In many cases this is because the link between process and technology is absent and the right tools are not being used - or are not being used in the right way. In this presentation we will introduce Atlasssian products that bring agile reporting to life.
Why We Need Architects (and Architecture) on Agile ProjectsRebecca Wirfs-Brock
This is an updated version of this talk which I will present at Agile 2013.
The rhythm of agile software development is to always be working on the next known, small batch of work. Is there a place for software architecture in this style of development? Some people think that software architecture should simply emerge and doesn’t require ongoing attention. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration. Complex software systems have lots of moving parts, dependencies, challenges, and unknowns. Counting on the software architecture to spontaneously emerge without any planning or architectural investigation is at best risky.
So how should architecting be done on agile projects? It varies from project to project. But there are effective techniques for incorporating architectural activities into agile projects. This talk explains how architecture can be done on agile projects and what an agile architect does.
This document summarizes an automation presentation given by Paul Gimbel. It discusses using Excel, VBA, and other tools to automate design processes in SolidWorks. Key points include using Excel for user interfaces, VBA for custom functions and macros, and integrating Excel and SolidWorks through macros and the SolidWorks API. Programming best practices like documentation and testing are also covered.
The document discusses how product structure is an important tool for product development teams that can help with communication, division of responsibilities, and integration across design, engineering, and manufacturing disciplines. It provides examples of challenges teams face without a clear product structure and recommends establishing a detailed product structure early in the development process using the right tools. The document advises getting management support, identifying needs and resources, prioritizing initiatives, and proceeding in a phased approach to implement better product structure practices.
This live demo from Razorleaf Corporation will show how to achieve full digitalization. It will discuss digital assets like parts, assemblies, drawings and components. It will outline the "journey to FD" or full definition, including creating 3D CAD models, digital specifications, digital assets like pictures, and component lists. Functional details will be provided on identifying products, loading components, defining products with pictures and CAD, monitoring progress, and future phases of creating 3D assemblies and bills of materials. Contact information is provided for questions.
The SolidWorks API can automate your design simulations as easily as the building of the models. Your automation tools (even 3rd party apps) can integrate SolidWorks Simulation into the process with just a little bit of code and forward thinking. It's easier than you think.
Learn about the integration offerings for product data management (PDM) to Autodesk PLM 360 using Jitterbit. There are different ways to integrate these products depending on how your organization currently uses or plans to use PDM tools. PDM tools like Autodesk Vault, SolidWorks PDM Professional, PTC Windchill and others along with Autodesk PLM 360 are robust tools for data and product lifecycle management.
Presented Tuesday, March 29, 2016
Merging PLM and Microsoft SharePoint Strategies from GPDIS 2009Razorleaf Corporation
Jonathan Scott's presentation from Boeing & Northrop Grumman's GPDIS 2009 (Global Product Data Interoperability Summit) in Mesa, AZ. A brief background in SharePoint and in PLM, with ideas for how the two systems can be leverage together for product development synergy.
Jonathan Scott of Razorleaf presented at the request of COE (CATIA Operators Exchange) for their Ask The Expert webinar series. Mr. Scott presented the basics of CAD file management for CATIA in ENOVIA SmarTeam Design Express.
SolidWorks Design Automation Using the SolidWorks API, Microsoft Excel and VBARazorleaf Corporation
Design Automation Techniques (session 2) with SolidWorks 2009 and 2010, Excel and VBA - Presented to Greenville (SC) SolidWorks User Group September 15, 2009 @ CU-ICAR
Magical designs that build themselves are the goals of many a SolidWorks user. Getting there with pure SolidWorks functionality, a 3rd party automation tool or API programming requires up-front thought and models designed for automation. Learn techniques to construct bulletproof models for any automation system.
This SolidWorks World 2006 presentation from Paul Gimbel of Razorleaf Corporation focuses on how to redesign your engineering design processes to leverage the use of 3D CAD tools like SoildWorks.
Design Automation - Simple Solid Works Solutions To Practical Programmatic Pa...Razorleaf Corporation
Design Automation Techniques (session 1) with SolidWorks 2009 and 2010 - Presented to Greenville (SC) SolidWorks User Group September 15, 2009 @ CU-ICAR
This presentation was originally from a webinar sponsored by Aras (an open source PLM provider). In it, Jonathan Scott of Razorleaf describes a brief history of open source, the open source PLM market, and the top 5 misconceptions about open source PLM. Mr. Scott also interviews Marc Lind, VP Global Marketing for Aras to ask specific questions about the company and their open source plm product.
For more information, go to http://razorleaf.com
The document discusses technical data migration and outlines key factors to consider when migrating data. It provides an example of migrating data from multiple sources like Access, network file servers, and ERP systems into a PLM system. It illustrates the different data streams involved like ECOs, BOMs, CAD files, documents and estimates timelines for migrating different data based on complexity. The document emphasizes understanding factors like required accuracy, transformations needed, and revision history to properly estimate a migration. The goal is to make technical data migrations easier to understand and explain to others.
SolidWorks World 2010 presentation by Paul Gimbel of Razorleaf. This session provides an introduction to programming with the SolidWorks API and how to work with the SolidWorks Object Model. Not a programmer? No problem. This session was designed to inspire you and guide you to get started.
This document discusses automating SolidWorks with Excel using Visual Basic for Applications (VBA). It covers creating user interfaces in Excel, accessing SolidWorks through VBA code, and driving SolidWorks automatically using loops in Excel. Examples are provided on building SolidWorks VBA code that can be used in Excel macros, including connecting to SolidWorks, accessing Excel data from VBA, and driving SolidWorks models with Excel values and information. Attendees are encouraged to ask questions during or after the presentation.
The document discusses how TactonWorks can be used to iteratively solve design problems. It describes how TactonWorks considers all constraints and options simultaneously to develop a complete solution set. This allows it to resolve the design automatically each time a change is made. TactonWorks creates a dynamic user interface that updates based on design choices. It uses attributes, constraints, and collections to link different parts of the design tree together and ensure consistency.
This presentation covers two main topics: 1) how to roll out a DriveWorks implementation, and 2) where in an organization DriveWorks can provide benefit, outside of engineering. In addition, the following areas are covered:
- The impact of business processes on design automation
- Engineering drawings and communication challenges
- How design automation can directly impact sales revenue
- Why DriveWorks matters to marketing and where advertising fits into the equation
- What other deliverables can come along for free when generating models and drawings
- Why it is important to think about ongoing maintenance of a DriveWorks deployment
- Ensuring a positive and productive User Experience (UX) with DriveWorks
- How triggered actions can help ANY DriveWorks implementation
- Top failure modes for DriveWorks projects (how to fail at deployment)
- Why Use Cases are critical to the success of design automation projects, and what happens when they aren't used
- Top 10 ways to fail at design automation UX
- Steps to properly testing any design automation deployment
This document summarizes 10 cool tools for 2016, including both desktop and mobile applications. It provides a brief description of each tool, which cover areas like engineering, processes, IT, and general productivity. The tools highlighted include Magnifier, Wolfram Alpha, Ninite, IFTTT, Mobile Markup, Irfan Viewer, Evernote, Trello, Notepad++, and Screencast-o-matic. Additional recommendations are provided from the community as well as information on how to contact the author.
SolidWorks World Presentation from Paul Gimbel at Razorleaf. This presentation deals with the use of Microsoft Excel and Visual Basic for Applications as a front end to driving SolidWorks geometry in a design automation implementation.
AU 2014: Autodesk PLM 360 Success Story with Inphi (TECH PAPER)Razorleaf Corporation
Discover the iterative design process and how to foster Autodesk PLM 360 software's flexible design process. Understand how to use Autodesk PLM 360 software to bridge the gap between multiple business process. Understand how to manage different types of change across an entire organization. Recognize the challenges that come with adoption in a global organization and how Autodesk PLM 360 software can help.
AU 2015: Enterprise, Beam Me Up: Inphi's Enterprise PLM Solution (Tech Paper)Razorleaf Corporation
In this course you will learn how Inphi Corporation has capitalized on the Autodesk PLM 360 tool to
manage its enterprise business processes; including new product introduction, items and BOMs, change
management, quality management, supplier management and much more. Share Inphi’s excitement
about improved visibility of organizational performance to project managers, executives, and indeed the
entire global organization by incorporating all of these business applications onto a single platform.
Understand how Inphi has improved compliance to their NPI and Quality processes by implementing task
management with workflow validation and a tiered approval process. Learn how Inphi tracks their
development process through the use of connected, but dedicated, workspaces for Engineering,
Marketing and Operations. See how Inphi leverages Jitterbit to integrate with several other business
systems such as salesforce.com, Oracle EBS, and Autodesk Vault. By attending this class, you will go on a
tour of how Autodesk PLM 360 has transformed Inphi’s business and could potentially transform yours as
well.
DevOps provides the ability to increase time to market to an new level. The question is no longer if we need to speed up our delivery. The challenge is to find the right „pace“ for your product. Not every organization and every product needs to run at the speed of Netflix and Spotify, even if we’d like it to be like this. We need to adjust the organization, processes and tools appropriatly and to identify the real bottlenecks in the delivery pipeline continuously. And by the way, we need to justify our investment in the DevOps mission. Are we just automating the current processes or can we use this DevOps thing to really support our business? In this talk, I’d like to discuss with you how to find the right design for your delivery process and your organization to behave as a business enabler and how you can scale DevOps within your organization without loosing agility. Let’s explore how we can listen carefully to the unknown customer out there and to build software they really like in the speed of your business.
This document provides an overview of a company that specializes in PLM, CAD, IoT, and digital manufacturing solutions. It discusses who they are and their leadership team. It outlines their capabilities including PLM, CAD, IoT/IIoT, augmented reality, 3D printing, and engineering services. It also discusses their global partners, awards, training offerings, managed services, and how they implement projects using their EAC Value Model framework.
This document provides an overview of a company and its capabilities. It introduces the company's leadership team and describes the services it offers, including product lifecycle management, smart connected products, technical publications, CAD, simulation, 3D printing, engineering services, and training. It highlights the company's experience, major customers, alliances, awards, and approach to projects using its M.A.P. framework. The company positions itself as a leading global service provider with over 25 years of experience helping customers design, manufacture, connect, and service their products.
Using Lean Thinking to Identify and Address Delivery Pipeline BottlenecksIBM UrbanCode Products
Inefficient software delivery impacts the entire business, from line of business units, to operations, to development and test, and the variety of suppliers.
Wastes in your processes are causing bottlenecks.
Join Eric Minick, IBM DevOps Evangelist (and UrbanCode guy), as he explores how ‘Lean Thinking’ techniques can be leveraged to help identify ‘bottlenecks’ in your delivery pipeline that can be addressed by adopting DevOps.
Sify introduces Forum, an integrated internet and infrastructure services platform that enables visibility in forward supply chains. Forum provides a desktop solution and robust information exchange platform to integrate organizations' systems with supply chain partners. This allows for stock and sales visibility, better distribution management, and real-time MIS across the supply chain. Sify has implemented Forum for several clients across various industries in India, helping enable seamless data transfer, real-time information sharing, and standardization of best practices.
This document discusses Assimil8's experience developing a business analytics software-as-a-service (SaaS) capability. It describes Assimil8's SaaS offering, how it helps clients through lower costs and faster deployment. It details Assimil8's journey to delivering SaaS solutions, including internal preparation and overcoming challenges. Client benefits are outlined as rapid deployment, lower upfront and ongoing costs, and an ability to easily change solutions as business needs change.
IBM Cloud Service Management and Operations Field GuideCarol Wingfield
This field guide provides a high-level overview of cloud service management and operations. It discusses IBM's approach which involves organizing teams into personas, defining processes, and using tools to enable and support activities. The guide outlines considerations for moving operations into development processes, and emphasizes concepts like continuous delivery, monitoring, collaboration, and building a DevOps culture. It also introduces roles like site reliability engineers and discusses practices such as ChatOps, incident management, and ensuring applications are built to be manageable.
The document discusses the growing adoption of robotic process automation (RPA) and artificial intelligence technologies. It provides statistics from various sources about the projected impact and growth of RPA and AI over the next few years. Cognic offers RPA consulting services to help clients implement new automation technologies to improve business processes and increase productivity.
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.
HP's vision for an integrated IT Service Portfolio ManagementHP Enterprise Italia
Le innovazioni per gestire in maniera integrata l'IT Service Portoflio Management: dal Project Porfolio Management al Service e Asset Management e Configuration Management System. Modalita' diverse per gestire la service delivery per una migliore efficenza operativa e soddisfazione degli utenti, impatto e vantaggi.
Kevin Leslie, HP EMEA Sales Director SPM
How Schneider Electric Transformed Front-office Operations With Real-time Dat...Informatica Cloud
Many of the world’s corporations use Salesforce.com to drive their front office, and while most experience success others encounter roadblocks and difficulties as their Salesforce footprint grows. Countless customers suffer from a lack of up-to-date information which impedes business progress and stifles end-user productivity.
This presentation describes how Schneider Electric SE, a multinational corporation that specializes in electricity distribution, automation management and components product for energy management, used Informatica Cloud to improve the operational efficiency of their Salesforce.com front-office.
It also details how Schneider Electric was able to make key data readily available to Sales teams in real-time, on the right device, to ensure the success of a highly visible front-office integration initiative.
To watch this presentation visit : http://youtu.be/kU2A1xMvaI8
For a 30 day free trial of Informatica Cloud visit:
http://www.informaticacloud.com/trial
Impact 2012 1640 - BPM Design considerations when optimizing business process...Brian Petrini
Whilst it is not always possible to remove and automate human tasks in a process, if it can be done, it often leads to the most dramatic optimization, leading to fully straight through processing. The challenge is that if straight through processing is the goal, we may need to design the process differently from the beginning, with automation in mind. This lecture uses tried and tested techniques for assessing processes to establish whether they are likely to be able to evolve to full automation, and recommends design patterns to be used to simplify the progression from manual to decision supported to completely automated.
This workshop aims to demonstrate how to build a strong business process management (BPM) foundation for performance excellence. The workshop agenda includes introductions, an overview of the workshop objectives and scenario, breaking into teams to model and configure a service request workflow using Sequence software, and building an analytics dashboard. The scenario involves automating the service request process for a company called Acme Widgets. The teams will discuss requirements, model the process, deploy a version 1, identify improvements, and if time allows, implement further versions and an analytics dashboard. The objectives are to deliver value through agile process development, achieve quick ROI from automation, and easily improve processes with minimal IT involvement.
Business processes and decisions are the backbone of every company, from small to the Fortune 50. It is these processes and decisions that can create competitive advantage, helping the company react more quickly to changing trends. The processes can also drag the company down if they do not serve the business with agility. The first step in building business agility is to understand how the business works today, what are the processes, what are the decisions we should take, and how should we take them. Understanding these processes and decisions can enable a company to improve, streamline, and increase efficiency.
IBM Blueworks Live provides a single, shared repository where all the stakeholders can find a single version of truth about any process. It facilitates successful process improvement projects by enabling all the users in the process improvement team to be aligned to the process goals, problems, and areas of improvement. IBM Blueworks Live directly integrates with IBM Business Process Manager so that documentation of the business processes are implemented, run, and optimized.
This document discusses next level supply and demand planning (S&OP2) and how technology innovations can help balance supply and demand. It covers:
1. The present challenges of balancing S&OP due to differing technology maturity levels and process complexity across industries and organizations.
2. The key reasons for implementing S&OP, including having one consistent plan used throughout the organization to coordinate orders, inventory, and supply.
3. The author's experience with S&OP over many years and roles, and lessons learned around ensuring iterative planning and connectivity between smart processes.
4. The vision to build new software tools that leverage technologies like AI, blockchain, and cloud to enable continuous planning, data sharing,
The document provides information on Capgemini's capabilities for migrating customers from Siebel CRM to Salesforce CRM. It discusses Capgemini's expertise in Salesforce and Siebel implementations, its proven migration methodology, tools to accelerate the migration process, and key considerations for migrations. The conclusion emphasizes Capgemini's experience and tools for CRM modernization projects. Case studies of past Siebel to Salesforce migrations for various companies are also summarized.
Similar to AU 2014: Autodesk PLM 360 Success Story with Inphi (PPT) (20)
This document discusses customizing the 3DEXPERIENCE platform. It defines configuration vs customization, with configuration using native tools and customization requiring custom code. Customizations can include business processes, additional data capture, adaptability/integration and automation. Users, developers, administrators and sponsors are involved. Schema, commands, attributes and more can be customized. Property files, MQL, thick clients, and JSP files are ways to customize. Customizations should be deployed in development, test, staging and production environments following formal processes.
Integration is not a one-size-fits-all approach. Connecting two or more end points between applications is a straightforward goal, but how to get there is very different from one company to another. Further, PLM integrations have complex data sets that require analysis before establishing connection points. Not every piece of data may be needed to support the business need of the integration.This webinar will explore the three different approaches that are recommended to support PLM integrations.
In this webinar attendees will learn:
Three approaches to integration
- Pros and cons of each
- Overview of commercial integration tools
- Introduction to CLOVER, Razorleaf’s integration platform and demonstration
This webinar was held on 4/25/17 and presented by Derek Nieding of Razorleaf.
ENOVIA V6 is Dassault’s PLM platform and has been publicized as the backbone for a number of future SolidWorks offerings. Why not learn how Enterprise PDM and ENOVIA V6 can be connected to deliver PLM benefits today.
Michael Craffey presented on ENOVIA SmarTeam and V6 Readiness. He discussed what V6 readiness is, the benefits of preparing for the transition to V6, and the various paths companies can take to migrate from CATIA V5 to V6 depending on their current setup. He also covered challenges companies may face in the transition and emphasized starting planning early and getting help.
COE2010 Razorleaf SmarTeam Attribute Mappings for Word and ExcelRazorleaf Corporation
Data and file contents can be moved between ENOVIA SmarTeam and Microsoft Word and Excel. View this presentation to learn how to create attribute mappings for SmarTeam with Word and Excel.
Managing CATIA Catalogs in ENOVIA SmarTeam requires some specific configurations and there are defined methodologies for working with standard part data. View this presentation to learn the basics of setting up CATIA Catalogs in ENOVIA SmarTeam.
AS&E struggled initially with their ENOVIA SmarTeam deployment, but ultimately got the system up and running in production, winning over a number of skeptical users in the process. View this presentation to learn what made the difference for them.
Paul Gimbel from Razorleaf Corporation used this presentation as people entered into his SolidWorks World presentations. It is a collection of inspirational, insightful, and humorous quotations for a wide variety of sources.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Essentials of Automations: The Art of Triggers and Actions in FME
AU 2014: Autodesk PLM 360 Success Story with Inphi (PPT)
1. Join us on Twitter: #AU2014
Autodesk PLM 360 Success Story:
Inphi - A “Quality” Solution that Changed Our Business
Robb Johnson
Inphi - Director of Technology
Rodney Coffey
Razorleaf - Sr. PLM Consultant
2. Your Instructor
Rodney Coffey
Sr. 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
3. Learn how Inphi changed its business by implementing Autodesk
PLM 360 software for quality management
Learn how Inphi changed un-scalable processes like emails, forms,
and spreadsheets into manageable business flows that provide
valuable metrics and stability
Learn how Inphi built quality applications to support RMA, MRB,
CAR, CAPA, and Change Management and integrated with other
cloud software: salesforce and Oracle
Learn about the iterative design process used to implement Autodesk
PLM 360
Class Summary
5. Your Instructor
Dr. Robb Johnson
Director 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
6. 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
7. Inphi Leads in Data Movement Interconnects
Fabless semiconductor company
Founded in Nov. 2000, IPO in Nov. 2010
Optical, networking, memory interconnect leader
for service providers, data centers
400+ employees worldwide, 70% engineering
Focused on success of system and module
customers worldwide
Innovative breakthroughs, solid execution resulting
in many industry’s firsts
13. 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 400+ employee company with locations all over the
globe
Process and procedures became harder to manage and enforce
Things done differently at each location
Needed visibility to all and ease of reporting and data mining
Why PLM?
14. 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
15. 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
16. 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
18. 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
Choosing A PLM System
19. Cloud based
Administration & End User Experience
Ease of Use
Configurability
Broad Application to Business Cases
Integration Abilities to Other Business Systems
Cost of Ownership
Why We Chose Autodesk PLM 360
20. The World of PLM at Inphi
Product
Management
Quality
Management
Foundry
Management
Customers
Supplier
Management
Legal
Contracts
Equipment
Document
Management
24. 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
CRPUAT
25. Through our PLM implementation we found that each
core team member:
Responded differently when asked about requirements
Needed different levels of verification of what was being built
Had different styles of providing input and feedback
Requirements were impossible to write down and walk away with
100% accuracy
Why the “Iterative Design Process”
26. 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
28. Sitting down with the Core Team we identified key
areas that we knew Autodesk PLM 360 could help with
Quality Incidents (New)
Return Material Authorization
Failure Analysis
Corrective / Preventive Actions
Material Review Board (New)
Identifying the Quality Management Needs of Inphi
29. We gathered requirements and data from:
Existing Procedures
Workflows
Fields
Validation Scripts
Condition Scripts
Hard copy forms
Fields
Validators
Gathering Requirements
31. Key to Building:
We knew from the beginning
each piece was part of a bigger
solution
The overall process could start
from anywhere
Information coming from other
systems - Integration
Building out our solution
RMA FA
CAPA
MRB
QI
33. We began by building the individual workspaces with
the common PLM 360 Capabilities:
Workspace Architecture
QI RMA FA CAPA MRB
WorkflowAttachments Change LogItem Details
Action Notifications
35. RMA – Benefit to the Business
RMA
Sales continuously updated real time via integration
to salesforce Customers more informed
Reports to see which customers or products have
high RMA rate Improved product quality
RMA request process is now followed closely and
parts no longer show up at Inphi without proper
RMA paperwork
“My sales team now spends less time tracking down
RMA status and more time selling products.”
37. Failure Analysis – Benefit to the Business
FA
FA was previously managed in Excel spreadsheet
and network drive. With PLM, data is accessible by
anyone and has relationship to products and
suppliers.
Pareto reports for failure types are easy to produce
and show areas for improvement in our assembly
process or with our suppliers
“We realized a lot of our FA results are RTOK. We are
working closer with our customers to ensure they do due
diligence before sending parts back for analysis.”
39. CAPA – Benefit to the Business
CAPA
Relationship to other quality items helps pinpoint
areas for improvement
Status of CAPAs and other metrics are easy to
produce and help drive closure
Increased visibility and workflow reminders help to
close corrective actions quicker
“Corrective Actions are easier to manage. As a
result, they are closed in a more timely fashion.”
41. Material Review Board
MRB
With PLM, we were able to implement and bring up
an MRB process that allows us to disposition
material quickly
We are able to quickly disposition material and
inform the finance group
PLM is used to run the weekly MRB meeting
“PLM has allowed us to implement a much needed MRB.
We now disposition material in a short weekly meeting.”
43. Quality Incidents – Benefit to the Business
QI
Efficient way to track related RMA, FA, and CAPA
items
Improved communication and response time to
customers
Easy to identify patterns with customer or product
to enable us to fix issues or educate the customer
“We now have a way to see the big picture, prioritize
our efforts and manage customer communications.”
45. We had to refine our early process Maps
Putting all the pieces together - Process
46. All QM items needed to be related to a QI
The process could start from any single workspace
The RMA process needed to start in salesforce
Putting all the pieces together - Process
QI
RMA
FA
CAPA
MRB
CAPA
MRB
MRB
MRB
47. Breaking down the Solution Elements
QI
RMA
We had three main methods for relating data
48. Breaking down the Solution Elements – QI
QI
QI items needed to be related to all other QM items
PLM 360 Relationships
49. Breaking down the Solution Elements – QM Workflow
QM Process that:
Worked through each QM workspaces workflow
Could start anywhere in the QM process (RMA, FA, CAPA, MRB)
RMA
FA
CAPA
MRB
CAPA
MRB
MRB
MRB
50. Breaking down the Solution Elements – QM Workflow
Re-Evaluation of our Workflow:
RMA
FA
CAPA
MRB
51. Breaking down the Solution Elements – QM Workflow
Scripting:
Spawn Item and Add to Picklist (Library, Action)
Consistency between workspaces
Reference Hand Out
function spawnItemAndAddToPickList(baseItem, pickListFieldName, spawnItemToCreate, spawnItemProperties, twoWayLink, spawnedPickListField) {
//create the item
newItem = createItem(spawnItemToCreate);
//add the properties
for (var propKey in spawnItemProperties) {
newItem[propKey] = spawnItemProperties[propKey]; }
//associate with the item's picklist
baseItem[pickListFieldName] = newItem;
if (twoWayLink) {
//a two-way link is requested
if (spawnedPickListField !== null) {
//a two-way link is requested and a picklist field has been provided
newItem[spawnedPickListField] = baseItem;
}
}}
if (item.NUMBER.length > 0){
var newProperties = [];
newProperties.PRODUCT_LINE = item.PRODUCT_LINE;
spawnItemAndAddToPickList(item, "ASSOCIATED_CAPA_DOCUMENT", "WS_DOCUMENT_LIBRARY", newProperties, true, "ASSOCIATED_CAPA");
}
53. Breaking down the Solution Elements – QM Workflow
Scripting:
Auto-Transition of Related Items to reflect
current state of QM process
Reference Hand Out
var transName = item.workflowActions[0].transition.transitionID;
//FA Completed pushes RMA completed
if (transName == 920 && item.ASSOCIATED_FA !== null)
item.ASSOCIATED_FA.performWorkflowTransition(932,"Complete");
//Capa Completed pushes RMA completed
if (transName == 920 && item.ASSOCIATED_RMA !== null)
item.ASSOCIATED_RMA.performWorkflowTransition(898,"Complete");
55. Breaking down the Solution Elements – Integration
Integration:
Sales Team entered RMA Requests through salesforce
56. Breaking down the Solution Elements – Integration
Building the Integration:
Both salesforce & PLM 360 were static 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 QM application was piloted for 2-3 weeks
Used with out salesforce in production
Jitterbit installed On-Premise
Production
Development
57. Breaking down the Solution Elements – Integration
Integration at Work:
RMA Requests are created in salesforce
RMA record is created in PLM 360
All information from RMA in SF is populated to PLM
As the PLM 360 item progresses through the QM process in PLM
SF updates with new field data
PLM updates with SF data
The status of the PLM record updates in SF
62. 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
65. 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
66. 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
67. 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
Pay attention to the order in which you train
Have a wingman in your early training sessions
Allows you to focus on the adopters while they document
changes
Lessons Learned – Using It
69. Quality Management was a piece of our overall
Solution
Our Quality Management Applications reference many
other business applications within PLM 360
Suppliers
Foundry
Customers
Document Libraries
Product Management
Summary
72. The World of PLM at Inphi
Product
Management
Quality
Management
Foundry
Management
Customers
Supplier
Management
Legal
Contracts
Equipment
Document
Management
73. Inphi has successfully adopted PLM 360 across a wide
variety of business applications
Our five Quality Management workspaces were
developed using the Iterative Design Process and have
the following benefits to our business:
Increased visibility to QM throughout the organization
Improved response to customers
Real-time reporting to facilitate quality improvement
Summary
74. Please Fill Out Your Surveys
Make sure your voice is heard!
Please take the time to complete
your survey for this and every
class you attend at Autodesk
University.
Autodesk uses this information to
know what classes to offer in the
future.