What I learned this week was that we could use a good, common PLM definition and scope, but we will not get one. The discussion (a lot of discussion in multiple forums, actually) came from my post SAP, Too Much or Too Little Credit for PLM Efforts and another called Who Will Disrupt Entrenched PLM Vendors?
What I learned this week … came from some discussions with Chris Williams yesterday about my blog post SAP – Too Much, or Too Little Credit for PLM? in combination with a conversation over breakfast with Oleg, author of PLMTwine. In both conversations I kept hearing about who is going to disrupt the big PLM vendors (Dassault Systemes, PTC, Siemens PLM).
I had the chance to talk with Tim Frost of Burner Systems International (BSI) about their adoption of Product Data Management (PDM) to improve engineering and new product development performance.
PLM can help, but compliance requires a multi-pronged approachthat includes strong data gathering, analysis, and docuumentation capabilities (this is where PLM comes in) but also intelligent supply chain relationships and physical validation.
A quick peek into some research on … the use of business intelligence in PLM provides insight on taking advantage of the tremendous amount of product data accumulating in today’s PLM systems. The research discusses how the maturation of manufacturers’ PLM implementations has created a tremendous volume of untapped information that can be leveraged to improve product innovation, product development, and engineering performance. As it has in previous enterprise applications (ERP, CRM, SCM, others), the time has come for manufacturers to tap into their growing information goldmines through the use of business intelligence (BI) tools.