One of the many results of these changes was the creation of a Department of Defense-wide standard for records management applications, the DoD 5015.2 Electronic Records Management Software Applications Design Criteria Standard. Nearly fifteen years later, Chris DeLara was serving his country as a soldier in Iraq
4 Comments - Meg - Microsoft hired Gimmal (including Don Lueders) to design a add-in for SharePoint 2010 that could be certified by the DoD 5015.2 standard. After we designed it, Jeff Teper decided that there were too many international jurisdictions with conflicting records management rules to add these capabilities to the SharePoint code base. Gimmal then developed and certified our products by the DoD 5015.2 standard, Chapters 2, 3 & 5
Very few people outside of the Department of Defense have more firsthand experience with the DoD 5015.2 Electronic Records Management Software Applications Design Criteria Standard than I do
17 Comments - One key misconception is that the standard somehow mandates a concept of operations
Here's the longer version of my title: Why I Not Only Support the DoD 5015.02-STD Standard, I Encourage all Federal Agencies to Adopt it
5 Comments - Why are the discussions and serious work on standards for managing Government electronic records in the US always limited to DoD 5015.2, as though it is the only existing standard? As you very convincingly point out, this standard is so outdated and inadequate in many ways as compared to others such as MoReq 2010, ISO 16175 and the Object Management Group’s Records Management Services (RMS) specification
When selecting a records management system, there are two important certifications to consider: DoD 5015.2 and VERS. What is DoD 5015.2? Many organizations use DoD 5015.2-STD Electronic Records Management Software Applications Design Criteria Standard from the U.S
I love both Don Lueders’ detailed post on this subject, On Why I No Longer Support the DoD 5015.2 Standard , and Mark Mandel’s rebuttal, I Support DoD 5015.2; and Encourage ALL Federal Agencies to Adopt It, as I believe that a full debate on standards for IT systems creating and housing Official Federal Records is really needed
4 Comments - "5015.2 is fundamentally flawed by its assumptions that all of an organization’s record information will be managed in some type of centralized and stand-alone RMA, EDM/ECM system
A little over a year ago, I posted an article on the AIIM Community explaining why I no longer supported the DoD 5015.2 Electronic Records Management Standard
This is the part where serendipity comes in. The DoD 5015.2 records management standard had just been issued and one of our customers wanted a document management solution, which would also comply with the brand new DoD 5015.2 standard
The question I am most often asked by records managers is 'do we need to plug a DoD 5015.2/MoReq2 compliant ECM at the back of SharePoint?
Lack of portability standards, moving data in and out of cloud environments into other systems, particularly when contracts end
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use