SharePoint is a long debated topic in PLM ecosystem. Starting from the early success of SharePoint back in 2006-2007, many companies are asking question about SharePoint and PLM system comparison. SharePoint took a significant market share using a successful licensing policy to embed the introductory version of SharePoint into Windows Server license. Another strong point of SharePoint was a very good integration with Microsoft Office. At the same time, despite a significant mainstream success, SharePoint still raised many questions about how manufacturing companies can leverage SharePoint to manage CAD drawing, collaborate and share engineering data.
I addressed SharePoint point on my blog many times. If you never had a chance to read my SharePoint related articles, maybe you can start by Why PLM should care of SharePoint? Another post that will help you to learn more about SharePoint and PLM could be this one – PLM and SharePoint Technical Definition.
Microsoft and PLM vendors had long debates about how to partner about SharePoint. The results of debates and partnership was mixed. Some of vendors (eg. Siemens PLM) made a long commitment by integrating between TeamCenter and SharePoint. The examples are TeamCenter Community, SolidEdge Insight (SolidEdge XT, SolidEdge SP). Other vendors like PTC, tried to establish multiple products that re-using SharePoint infrastructure (Windchill SocialLink, Windchill ProductPoint, etc.). Some of them succeed and some of them failed. You can read more here. Other vendors tried to investigate more into service contracts to integrate SharePoint with PLM products and infrastructure.
Microsoft SharePoint business is big these days. At the same time, it started to show some indication of weakness that might be typical for enterprise type of solution. In a nutshell it became complex, hard to deploy and costly (especially in the situations when organization required to scale up SharePoint to a fully blown enterprise solution). Read my article SharePoint got infected with PLM disease. Microsoft is trying to react on the new SharePoint status. From what I see, Microsoft is transforming SharePoint from product into infrastructure. You can find more information about this activity in my post – Will PLM Benefit From “SharePoint Death”?
Recently, another interesting information about SharePoint deployment came to my attention. Navigate your browser to ArnoldIT blog – SharePoint Not on the Radar. The writeup quoting some research surveys made by AIIM. I found the following passage important.
AIIM conducted a survey and found that only 6% of its respondents found their deployments successful, while 43% are struggling with implementing SharePoint, and another 28% say that progress has stalled in their SharePoint projects. That only touches the shallow end of the SharePoint pool. Many companies are also running multiple versions of the software, which can only lead to compatibility issues.
Another interesting publication research made by consulting outfit – Razorleaf. Navigate to the following link to access Razorleaf’s PLM and SharePoint white paper. Here is an interesting passage from Razorleaf article:
SharePoint is poised to become an ubiquitous document and content management system with great capabilities for ad hoc collaboration, whereas Product Lifecycle Management (PLM) is a similar but more structured system focused on product development content. By integrating SharePoint and PLM (the Product Data Management (PDM) components of PLM), users can blend the benefits of both to enable ad hoc collaboration on top of rich, structured product data and information.
Another similar conclusion is coming from Aras PLM blog – Why Can’t We Just Use SharePoint? The discussion in the article is about why SharePoint is not capable to replace PLM software. Aras blog is mentioning two significant capabilities missed in SharePoint – context / relationships management and missing workflow capabilities. Without agreeing on specific elements, I have to admit that general conclusion in the following passage seems to be right:
SharePoint is a powerful tool that has a very useful place in your PLM strategy, however, unless you are ready to invest significant time and resources into customization (i.e. building all the PLM functionality), it is not a replacement for choosing and deploying a real PLM system.
What is my conclusion? Back in 2006-2007, SharePoint provided an interesting and easy to deploy set of tools perceived by everybody as something that might have a potential of PLM system. Since that time, SharePoint gravitated more towards “platform”. At the same time, PLM is more focusing on cloud vertical solution and business application. Will their paths meet in the future? This is a very good and important question to ask. I’m doubt about that. Meanwhile, the difference is so obvious, in my view. So, to stop comparing PLM and SharePoint should be a clear goals. The complimentary paths are possible indeed. Just my thoughts…