The Microsoft SharePoint 3.0 Juggernaut: Why Records Managers Should Care - Part 2
by James Just, ARMA Local Newsletters
01-01-2007
Part two of a two part article on a few of the opportunities and challenges created for records managers with the release of Microsoft SharePoint Services v3.0. In Part One of this article, the author explored why SharePoint 3.0 will change the landscape for many records managers. This section continues the discussion of SPS features and functionality and the impact on records managers.
SharePoint 3.0 has added extensive features that can be employed by records managers for extending the control of records under their supervision. While most records managers have employed some degree of records control automation, new demands arising from a growing web of governance rules and/or laws has created the need for more help than ever before. The recognition by Microsoft of the growing importance of structural management of official records is core to the records management features of SharePoint; the savvy records manager will employ them to their fullest.
Some of SPS’s Records Management features that hold the greatest benefit to records managers include:
But perhaps the most helpful features for day-to-day management of digital content isn’t a single feature at all but rather the overall tight integration between SPS and other Microsoft components. Office 12 integration is tight and intuitive whether users are writing letters, working with Email, processing an eform, or collaborating on content. The structured storage and management available in SPS is just a click away. Properly configured SPS repositories automatically categorize objects into the established file plan and impose full controls over the content. Office 12 integration is a singular reason for records managers to be integral participants in even casual SPS deployments. For these reasons, records managers’ involvement in SPS deployments will:
· Ensure the application design of the folder structure and metadata schema properly follows your file plan
· Build and implement content types that match your retention schedules to automate document lifecycle management as much as possible which will enhance user acceptance.
· Establish Information Management Policy for SPS applications (disposition and management rules)
· Define “hold order” types to deal with litigations & external events (see above)
· Ensure audit trail information and reports will verify that your system is functioning as expected and you are in compliance with applicable regulatory or governance requirements.
· Ensure there is a mechanism for accepting records declared as official from outside of the SPS application in a way that they fit into the file plan & metadata schema.
· From my perspective, I think it is also crucial that records managers strive to keep the deployments manageable and not overly complex. As anyone who has tried to implement an RMS in the past has come to realize: if the act of storing an object into the RMS isn’t simple, it won’t happen. Simplicity rules in the users’ world.
In summary, Microsoft’s new-found focus on integrating document, digital rights, and records management in the SharePoint 3.0 release means new opportunities for records managers to deliver the message of complete, reliable and accurate corporate records management and to be a part of designing solutions deployed across the enterprise. The 800lb gorilla is in the room; records managers need to find her a place to sit!
About the author: Jim Just is a partner with IMERGE Consulting, Inc., an unbiased, vendor neutral consultancy specializing in enterprise document management technologies and business process improvement. Mr. Just focuses on helping organizations attain operational excellence using process analysis and redesign techniques often utilizing best-of-breed technologies. For more information about Jim or IMERGE, please visit our web site at
www.imergeconsult.com. IMERGE does not sell nor support products, including SharePoint.
Download: Full Article in PDF Format