Industry


Ads by TechWords

See your link here


Larry Medina's picture
Larry Medina

For the Record

Let's talk about Records Management

After reading a recent article in Computerworld, I thought it might be important to have a discussion about what Records and Information Management (RIM) is from the perspective of a RIM Professional that's been in the field for 35 years.  During this time, there have been many changes to the process made necessary by the explosion of electronic format information (beginning for business actually in the early 1980s), but the practices and principles of RIM have essentially remained unchanged.

The object has always been to assign a value to information consistent with it's need for business and to retain it and maintain its availability for the period established for its retention.  Retention periods are based on a combination of factors:

  • Legal, Statutory, or Regulatory requirements (Federal, State, County, City, or in some cases, International)
  • Business Needs that may exceed those
  • An evaluation of possible legal or financial risks of retaining information beyond required periods
  • Any possible historic, enduring, or intrinsic value of the information for reference purposes

What defines information as a "record" can differ depending on the industry segment, business type, degree of regulation, or geographical setting you work in.  In general, (fore most businesses) it's anything that documents a decision, transaction, or provides guidance to others.  For anyone working in a Federal Agency or as Contractor to a Federal Agency, the definition comes from the US Code 44USC 3301 and it is rather specific.  The important things to note in this definition though is: "...regardless of physical form or characteristics..." because that means it applies to paper, electronic, microforms or any other material the "record" resides in/on.

This is critical for the people in IT to understand, that irrespective of the problems caused by the need to retain information that is defined as a record for periods that may exceed 50 or 75 years, it is now their responsibility to find methods to accommodate those needs.  And the records must remain viable, verifiable, able to be authenticated,  and accessible in a reasonable amount of time for as long as required to be retained.  About the only aspect of that list subject to any form of interpretation is "accessible in a reasonable amount of time", but what is reasonable is determined by who sets the requirement (SEC, HIPAA, FRCP, etc.)  

With the volume of information being produced electronically increasing exponentially, it is even MORE critical for RIM professionals to be involved in assisting in establishing criteria for identifying the percentage of information that meets the definition of "record" and to determine methods for classifying and managing this information independent of the general population of information.  In some instances, a majority of information may have a 2-3 year required retention, such as correspondence or general business information, some procurement or financial information may need to be retained for 6-10 years, and a much smaller percentage of information may have longer term retention, in excess of 15 years.  In some highly regulated industries or in the Federal arena, there are some records that have a retention period that actually is permanent.  This period affects less than 10% of all records, in fact, the number is thought to be closer to 3-5%, but special care must be given to determining methods to migrate and convert this information periodically to avoid obsolescence and degradation of the media, storage formats,  and or hardware the records are stored on.

And much needs to be done to break down the communication barriers between RIM and IT, the dissimilar use of common terms that have distinct definitions in each practice.  Another problem is the desire to find more cost effective means of managing information over it's life cycle, a practice in RIM known as life cycle management, which is distinctly different than what the storage vendors are "branding" ILM.  It's not a product or a process, it's a PRACTICE and it isn't SOLVED by the application of technology.  Technology is just a tool that aids RIM in satisfying the requirements to manage the information as a record.

Another term that has seriously different meanings to IT and RIM is "archive".  IT seems to think of it as a verb, and it involves the relocation of information to different types of storage based on it's use patterns... if it's less frequently accessed, then it should be "archived".  The problem is, and RIMs are well aware of this, some records may not be routinely accessed for years, and are then considered "inactive", but all of the sudden, something changes and the reference patterns of records with retention periods that haven't been met adjust drastically and the records become "active" again.   In RIM, nothing is "archived" until it's retention period, which includes any business needs that exceed regulated periods, has been met.  And then, they are only sent to an archive if they are deemed to have historic, enduring, or intrinsic value to the organization.

To me, we're at a critical point in the management of information where everyone is beginning to understand the need to provide appropriate controls over information that exists in storage, and especially that information which meets the definition of a "record", and to successfully address these issues, RIM and IT need to work collaboratively.

What People Are Saying

It's easy to accomplish this

It's easy to accomplish this through the use of an electronic records management system and it's rule based policies which disallow saving a document without incrementing the version.

There are other products

There are other products that provide this function, but hopefully this helps steer you in the right direction.

It's easy to accomplish this

It's easy to accomplish this through the use of an ERMS (electronic records management system) and it's rule based policies which disallow saving a document without incrementing the version.

Interseting comment about

Interseting comment about the small amount of permanent records. We are having a dialogue because the Commercial Ins. folks want to institute indefinite retention for nearly all documents.

On a related front, has anyone had any experience with legal concerns that the electronic image is not an exact replica of the paper because the printed image is a bit smaller. The image when printed has a small clear border around it and therefore the print fonts are smaller than the original. 8 1/2x11 reduces down to 8 3/16x10 7/16 The concern is for regulated documents where a certain size font is required. I would think that if it is standard practice and consistent would not be an issue Thanks.

Larry makes a number of

Larry makes a number of excellent points in what he has written. What many in the IT community fail to understand is the following: Records Managers are not eager to stifle progress, rather they are eager to ensure that their organizations avoid the risks associated with poor or non-existent record keeping practices.

The best way to avoid the famous mutli-million dollar judgments is for C-level executives, Business Unit managers and IT professionals to understand that the concerns of Records and Information Managers have a great deal more to do with regulatory, statutory and litigation issues, than with any resistance to new technology or to change.

Doug Allen, CRM, CDIA+

Does anyone have a good

Does anyone have a good source for procedures to keep manaagment of word processing document records (ie. version control). We have a document that is continually revised and we need a procedure to maintain the lastest version through version numbering, etc.

T.

Anonymous: We are currently

Anonymous: We are currently implementing an IBM system called Document Manager. This product "sits on top" of a Content Manager product which is the central repository for all documents whether WORD, Excel, PP, PDF, TIF etc.

Document Manager has Version Control. You "check out" the document and while you have it checked out others can view but not edit. Then you check it back in. By clicking a Version History icon, the user will see the version history, who revised it, and the date and time. You can view any version; the latest version always appears at the top of the list.

There are other products that provide this function, but hopefully this helps steer you in the right direction.

Some of this is available in

Some of this is available in MS Word through te use of "track changes" and "properties". Another simple procedure would be to use "save as" and append an alpha or numeric designator to the filename prior to it being saved.

It's easy to accomplish this through the use of an ERMS (electronic records management system) and it's rule based policies which disallow saving a document without incrementing the version.

Larry Medina Danville, CA

Records and Information Management Professional

Agree, people began to

Agree, people began to understand more and more about this, but what do you want? Society is developing, and that's great!

Ben- What do I want? Well,

Ben- What do I want?

Well, the list could be endless, but when it comes to this topic, I want society to continue developing... but I want them to also develop policies, practices, and procedures as they go along.

As mentioned with e-mail as the primary example, everyone started using it, but no one thought about how to control the content. And the volume continues to grow unchecked in many organizations because they have no policies. And setting a maximum volume limit or a time limit isn't a policy, it's a knee jerk reaction to a situation.

Record retention periods are based solely on the content of the record, and they are set to satisfy legal, regulatory or statutory requirements, based on who regulates the business an organization is involved in and any business needs that exceed those.

So, really... it's not what I WANT that matters, it's what is required by a regulating body that does.

Larry Medina Danville, CA

Records and Information Management Professional