Is PLM too Complex to Mashup?

 I was amazed to discover that there is almost no reference to PLM systems using Mashup technologies. So, what is wrong with Mashups? My impression was this is a very successful technology since Mashup usage is growing in multiple vertical industries. Starting with Google Maps, Mashups show their power through their ability to combine data coming from multiple sources. So, why don’t PLM systems understand this value?

 My initial assumption takes me back to PLM content management. PLM absolutely dislikes the ability of foreign systems to touch and manipulate content – design, bill of materials etc. The core perception is that this content is complex and cannot be simply extracted from a PLM system. At the same time, most of the successful Mashup technologies are based on their ability to take data from multiple systems and merge them together – in other words “mash” them “up”.

 So, what we can do to improve this?  How can we popularize PLM content? – by allowing multiple functions in PLM software to extract content such as models and drawings,  Bill of Materials etc., and make them available in formats and representations that can mash-them-up to something people will actually use. I can find multiple use cases for this such as mash-up design information with CRM systems – to see what parts of a design are most problematic in customer reports. I’m sure you will be able to find more applications and use cases for such Mashups…

 What is a Mashup? – ZDNet

 Let me know if you have experience with Mashups and have found them useful…