SharePointRecordsManagement.com

I have about as much experience with the MOSS 2007 DoD 5015.2 Resource Kit as anyone else and I intend to write about it ad nauseam in future posts.  But before I do that, I’d like to make a couple of comments about the DoD 5015.2 Standard in general.

I’ve worked with the Standard for many years.  I’ve been involved in product development and certification testing for several major Records Management applications, including Documentum, Meridio, Interwoven and SharePoint.  I could write a book about the 5015.2, but I promised myself I’d keep these posts short and to-the-point.  So here are a few comments.  Please let me know if you disagree with me.

• The Standard is too complicated.  There are a tremendous amount of unnecessary requirements in the DoD 5015.2 that RMA vendors spend a lot of time and money on developing the technology to meet.  A lot of these requirements are for functionality that really won’t ever be used in a real-world implementation.
• The Standard is too narrowly focused on how the US DoD manages records.  This is especially true with regard to file plan structures and records disposition processing.
• Nobody seems to agree on what being certified really means.  If you take Product X, which has been certified in a testing environment and implement it in a completely different manner at your organization, is the certification still valid?  Who checks to make sure it is?  More importantly, what is being tested?  Is it the application’s functionality that meets the requirements?  Or is it the application’s ability to be customized or configured to meet the requirements?  There’s a big difference.
• Despite its many faults, the Standard is vitally important and I wouldn’t consider investing in a solution that wasn’t certified.  Having all the functionality that the Standard requires is nice, but the real value of certification is that it legitimizes the solution as a top level Records Management application and validates it as a secure records repository.