What I learned this week was a retrospective look at an article analyzing how industry-specific PLM application are. The review was in response to a comment on my post In Search of a Common PLM Definition.
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).
What I learned this week … came from a conversation with Jeremy Johnson from IHS. Jeremy opened my eyes to a new way to make manufacturing more sustainable and ecologically friendly. I have written in the past about how companies are making their products compliant in Product Compliance – Hidden Tax on Innovation and Making Product Compliance Sustainable. But here’s the catch that makes this the most interesting to me. While product compliance helps to protect top-line revenue and market access across the globe, it is an activity that costs manufacturers money.
We were discussing my thoughts on PLM in the Cloud, when it finally struck me. Are we going to ruin the design process for experienced engineers by hampering their real-time interaction with the system?
So now “PLM” and “Cloud” are official buzz. Is this a brave new world, or just another buzzword to throw around?