8 Things to consider when implementing SharePoint with another ECM engine

The latest blog entry is actually a guest blog entry.  This time an entry in the AIIM Digital Landfill regarding implementing SharePoint with another ECM.  A few goodies from my experience with implementing SharePoint with another ECM vendor's solution.  Many think it's just about adding a couple fo Web parts, but is it?  That depends...

http://aiim.typepad.com/aiim_blog/2009/10/8-things-to-consider-when-implementing-sharepoint-with-another-ecm-engine.html

Excerpt:
With any ECM deployment, it is important to have a solid implementation plan to be successful.  When combining multiple content solutions, it is critical.  Unfortunately, many SharePoint implementations are more organic than well thought out.  SharePoint sites are often created with little thought with respect to long term use.  As a result, when it comes to linking into another ECM solution, users are hit with unexpected changes and restrictions to sites they have become accustomed to.  Understanding the functionality people use, or expect to use, from each system is vital to the successful blending of the capabilities.  This list of things to consider is not an exhaustive list, but is intended to help get the planning process started...

 

What did you think of this article?




Trackbacks
  • No trackbacks exist for this entry.
Comments
  • No comments exist for this entry.
Leave a comment

Submitted comments will be subject to moderation before being displayed.

 Enter the above security code (required)

 Name

 Email (will not be published)

 Website

Your comment is 0 characters limited to 3000 characters.