What I learned in June is that SAP and their customer Colgate have been hard at work improving the way manufacturers innovate. While this isn’t a formal SAP product as of yet, the co-developed solution shows some real promise on how companies can use social computing to drive innovation.
Product cost is not getting the attention it deserves in PLM. I was presenting on the future of PLM and a participant asked “why I hadn’t included cost in the future of PLM?”
A peek into more research on how manufacturers and vendors plan to react to the market for CAD, CAE, PLM, and other engineering software in 2010 and beyond.
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 the PLM team at SAP recently to get an update on their plans and their progress to date. I struggled to understand why after all of the years of SAP getting too much credit for PLM, why they don’t seem to be getting as much credit for their recent efforts as I would expect. What do you think?