Thursday, September 27, 2007
Records Management, ECM and an Enterprise Architecture Perspective
Laurence Hart provides wonderful insight into the RM world and is an insightful read for others...
![](http://www.bloomberg.com/apps/data?pid=avimage&iid=iScDg_ws9JRY)
The other thought that I had is this feels like an opportunity for Alfresco and Nuxeo to take marketshare away from Documentum and Stellent. The separate SKU sales pattern feels fugly when it should be a feature of an existing product and not something distinct as it cannot standalone on its own.
Imagine a scenario where you have a BPM system and an ECM system integrated where documents are in the ECM and processes are in the BPM. Shouldn't you be able to via some industry standard that is implemented in all products be able to say that all documents are disposed of when the business process reaches a certain state without fugly syncronization?
| | View blog reactions- RM capabilities should be built into any ECM platform... final disposition needs to be a built-in part of the platform. I believe all, and I am open to correction here, ECM vendors charge separately for retention and RM functionality, if they even have it split into two products.
The other thought that I had is this feels like an opportunity for Alfresco and Nuxeo to take marketshare away from Documentum and Stellent. The separate SKU sales pattern feels fugly when it should be a feature of an existing product and not something distinct as it cannot standalone on its own.
- Many people will still go with RM as tracks those paper records that James mentions and people still need CYA. However, it can lead an organization down a rabbit hole if they look at two products, RPS and RM, and pick the term Gartner uses to define the problem.
- He defined RM with the 20 year old definition focused around paper.
Imagine a scenario where you have a BPM system and an ECM system integrated where documents are in the ECM and processes are in the BPM. Shouldn't you be able to via some industry standard that is implemented in all products be able to say that all documents are disposed of when the business process reaches a certain state without fugly syncronization?