Skip to main content

PLM and Sharepoint

So you have all these PDM/PLM suppliers out there who have systems that vault data, manage workflows, manage revisions and control access to product data.  Some of these systems have existed in one form or another for decades.  All of it home grown because nothing existed that could be used as a framework to build upon.

Now decades later, we have Sharepoint.  It is everywhere. It vaults data, manages workflows, manages revisions and controls access.  What is missing?  Not much.  With Sharepoint 2010 soon to be released, the framework is there.  All that needs to be done is create some webparts and templates, and a pretty finctional PDM system could be had.  Some have already headed down this path.  Solid Edge released Insight on Sharepoint 2001 and continues down this path supporting Sharepoint 2003 and 2007.  PTC recently released Product Point based on Sharepoint.

I predict others will be following fast.  How can they not?  The functionality and userbase is there. And think about this:  A new model where the applications interface to the PDM system, not the otherway around :)

Care to comment?

Comments

Oleg said…
SharePoint will have some success. However, it is still a framework. The question is what PLM vendors will try to accomplish on top of SP. If they (vendors) will try to convert SharePoint into traditional PDM, it probably will be a huge failure. Some of my additional thoughts are here --http://plmtwine.com/2010/01/06/key-success-of-sharepoint-what-should-plm-learn/.
Best, Oleg

Popular posts from this blog

Solid Edge ST3 - Part 1 of 4

The Siemens PLM Connection event is over.  Given the change of date and venue due to the flooding of the Opryland Hotel in Nashville, it was a great success.  There were many excellent presentations and "hands-on" training sessions for Solid Edge (including mine) , and even though a formal announcement of the upcoming ST3 is some time away, we got a sneak peak of several new customer driven enhancements as well as some hint of: A "bridge" to help existing users better adopt Synchronous Technology Simulation enhancements PDM enhancements 1000's of customer enhancements from modeling to the user interface Over the next few weeks, I'd like to cover some of the items presented around the customer driven enhancements, but please keep in mind there are still a whole lot of items that will not be presented until the official Solid Edge ST3 launch later in the year. For this post, I would like to cover the User Interface enhancements. You now have...

Dimension Projection Line Breaks

Often when placing dimensions on drawings, the projection lines of some dimensions will cross the projection lines of other dimensions as shown below. Solid Edge provides a function to automatically create breaks in one extension line where it crosses another. This function is called "Add Projection Line Break". It is accessible from the Shortcut Menu when you have a dimension highlighted. The result is shown below. If you wish to remove the projection line break, highlight the dimension, invoke the shortcut menu, and select "Remove Projection Line Break".

Solid Edge V20 Deployed!

I have finally gotten Solid Edge V20 and the Viewer deployed through my organization on Sept. 27th. We deploy SE to over 100 users and the Viewer to over 400 users across about 10 geographic locations in one night over a couple hours. All went well considering this was the first deployment since the new Packaging Specialist started, and it was done on a brand new version of the deployment system we use. We use Microsoft's System Center Configuration Manager (SCCM) which was just upgraded from SMS 2003. http://www.microsoft.com/systemcenter/configmgr/default.mspx . It allows inventorying PC's throughout the org, as well as pushing software to the PC's. To be able to push the software, you must use the MSI supplied by Solid Edge and repackage it as an EXE. Since the MSI is used, you must also install .NET and ISSCRIPT separately (which can also be added to the EXE package). We found that the ISSCRIPT.MSI must be modified to work with SCCM due to the fact that it insta...