Cloud PLM is a not a new word any more. Established vendors and newcomers in PLM world are developing strategies and implementations how to embrace PLM cloud. In my article few months ago, I’ve talking about multiple faces of the cloud – public, private, hybrid, collocation. Jim Brown, well-known PLM analyst and my long time blogging buddies is covering different visions of PLM vendors in his Tech-Clarity blog these days. Two first articles covered Autodesk and Dassault. It is interesting to see a difference. Autodesk vision described by Jim in the following passage:
Autodesk is embracing the Cloud like no other PLM vendor – Autodesk has made big gets on the cloud. They introduced CAD on the cloud (Fusion360), simulation on the cloud (Sim360), and a host of other new “360″ products to join PLM360 on the cloud. As one of my analyst friends tweeted the Autodesk keynotes mentioned “cloud, cloud, cloud, and cloud.”
Opposite to that, Dassault strategy is quite different and focuses on strategic choice of private cloud (even if technically claims no difference between public and private cloud). Here is an interesting passage from Jim’s post outline Dassault vision:
My final comment on DS strategy is about the cloud. Given the SOA architecture behind DS’ solutions one might expect DS to embrace the cloud wholeheartedly. DS execs were clear in pointing out that they support the cloud – but that they believe the on premise cloud is the viable option for companies today. It’s an interesting stance given that they appear to have the technical capabilities required but are choosing to opt away from the public cloud. This is an area to watch.
The question of private and public cloud strategies is important. Even cloud is a new trend, PLM vendors can gather some experience from challenges that non-PLM vendors are experiencing with implementing different cloud strategies. ComputerWorld article Why Microsoft SharePoint Faces a Challenging Future speaks about SharePoint dual strategy to maintain existing SharePoint 2013 on premise version as well as developing new SharePoint Online. The article is worth looking and contains lots of interesting examples. The following passage is my favorite:
Many enterprises use and like SharePoint. Microsoft likes it, too, because it’s one of the company’s fastest-growing product lines. But making enterprises support separate cloud and on-premises versions and telling SharePoint app developers not to work in C# and ASP.NET may make for a rocky relationship as time goes by.
Customization is an important aspect of every enterprise deployment. PLM is not an exclusion. Existing PLM deployments are full of customization made using existing development tools. Even more, on-premise deployments can provide some customization flexibilities that hardly can be achieved in public cloud implementations.
What is my conclusion? Dual cloud strategy sounds very compelling and we can hear about it a lot. However, to achieve real "cloud duality" can be tricky. Another level of complexity is to maintain transparent private/public customization and configuration using existing and new PLM technologies and tools. IT managers, PLM advisers and customers should take a note. Just my thoughts…