In the DoD space, I see RIM related or affecting "automation" coming from a few places and would like to explore what that means to better managing the information flowing through the digital pipes.
1) Homegrown - buried in some generic support contract or generic IT support. There is no specific funded requirement for RIM, but there may be some purchases (not acquisitions) of RIM supportive stuff like data bases, office tools, archives. And there may be internal developments going on. We have these at JITC and I've seen them at DHA and other places. Here the people providing the solutions may not even be IT in the traditional sense. It may be a special projects group. And Records and Information Management gurus won't be invited into the table because even if someone thinks about it "they just make things harder." How do we reach these areas?
2) Part of another IT-related acquisition - This is what OMB-A130 targets. Build in RIM, don't bolt it on. These are funded programs and should have some sort of Information Support Plan that includes RIM aspects. Primarily the focus has been interoperability, at least from my test-centric perspective.
3) Purpose built/acquired - These are specific content management solutions that can be configured to support RIM. Many COTS fit here and are generally included as basis or components for the acquisitions mentioned in 2). Or they may be a stand-alone purchase to just do RM or CM or DM or ?
4) RIM Services/micro services - This may be emerging related to content content services. Because of the fundamental nature of services, I want to say that this perspective will help guide us to architected, engineered, integrated, interoperable and curated information ecosystems. But, because of what I've experienced with DISA's implementation of services, the integration, interoperability, and curation happen at the desktop via the bio-component. Certainly not acceptable.Thoughts? Ideas? Observations?
Good thoughts and discussion. I hope to encourage you both with an update from ground zero at Headquarters AF (HAF). The AF is moving to the DoD Office 365 Cloud as you know. There is a big records policy clean-up effort underway at the Headquarters AF ( being led by AFSPC who is sending their RM team out to HAF for one week each month to work with Records Managers to clean up all the outdated schedules. Their goal is to reduce the size of file plans by 50% minimum. Some have been able to reduce theirs by as much as 90%!Where the rubber meets the road in most organizations there is more interest in getting out of content chaos than managing Records. The solutions we are piloting support both. It feels to me like the first 3 approaches Jana listed were stairsteps that needed to happen. Knowing how long you have both been champions in this space I hope to encourage you that the move to Office 365 combined with the integration of a few 3rd party solutions are enabling the AF, and eventually DoD, to move into the 4th Area Jana describes without the problem of depending on the end-user to do everything right.I think Mark touches on a great point regarding the human element of it all. As much as we'd like to have all of this automated using AI, someone has to teach the AI and keep it up to date. As much as the size and complexity of DoD brings challenges it can be a great enabler if we can tap into its people the right way. Uniting our experts in this space, leading with clear policy and guidance and evangelizing whenever possible will keep us on the path to a bright future.Respectfully,Jason Marshall