Method and apparatus for propagation of file plans from enterprise retention management applications to records management systems

• US 8,250,041 B2
• Filed: 12/22/2009
• Issued: 08/21/2012
• Est. Priority Date: 12/22/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Pogodin, Andrey
• Primary Examiner(s): TIMBLIN, ROBERT M
• Application Number:
  US12/645,351
• Publication Number:
  US 20110153578A1
• Time in Patent Office: 973 Days
• Field of Search: 707/662, 707/665, 707/667, 707/756, 711161-162
• US Class Current: 707/662
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Integration between Enterprise Records Management systems (ERMs) and Records Management Systems (RMSs) is provided, thus providing a robust record classification and retention schedule enforcement process in large enterprises. Typically, ERMs have been designed from the ground up to be highly scalable across multiple national and regional jurisdictions, whereas RMS'"'"'s were primarily departmental. Proper integration between ERMs and RMSs, as provided by the invention, allows corporations to deploy larger scale multi-organizational instances of RMSs, thus achieving a better level of control and significant economies of scale.

Claims

1. A computer implemented method for propagation of file plans from an enterprise retention management system (ERM) to one or more records management systems (RMS), the method comprising:

providing a processor-based RMS that is configured to store a plurality of records which need to be preserved for a certain period of time to meet companies'"'"' regulatory obligations, the records comprising documents with associated metadata;

providing a processor-based ERM that is configured as a source of master data about record classification and record retention, the ERM configured to perform maintenance of record classes and retention/disposition rules and to propagate information to the RMS according to any of the following;

automatically via a connector between the ERM and the RMS;

semi-automatically via end user export of file plan information from the ERM in a form understood by RMS import tools; and

manually; and

wherein the ERM is configured to provide a mapping for translation between ERM and RMS objects to effect propagation of file plans which comprise a combination of a retention category tree, disposition schedules, and events, and which defines how records are stored and disposed of in a given RMS, from the ERM to the RMS, the mapping including;

translating ERM record classes within a classification of retention schedules to RMS record categories within a hierarchy of record categories set up within the RMS, and

translating ERM retention schedule codes (RSCs) into next level record categories under those created from record classes.

2. The method of claim 1, wherein:

the ERM is further configured to present said end user with a view of ERM objects translated into an RMS language to allow the end user to perform manual setup for an RMS.

3. The method of claim 1, wherein the mapping further comprises:

translating ERM organization-specific retention schedules (ORSs) into next level record categories under those created from RSCs;

translating ERM disposition rules associated with ORSs into RMS disposition schedules;

mapping ERM event types to RMS event types; and

storing records only under a bottom level records category at an ORS level.

4. The method of claim 1, wherein the mapping further comprises:

creating, by the ERM, a plurality of RMS objects, each comprising a bottom level record category and a disposition schedule associated with said bottom level record category, if there are disposition rules and organization-specific retention schedules for a plurality of entities associated with a particular ERM.

5. The method of claim 1, wherein the mapping further comprises:

creating, by the ERM, two levels of record category objects;

one object level representing retention schedule codes (RSC record category) and one object level representing a top level organization-specific retention schedule (ORS) if for a certain ERM, a top level ORS and RSC is a same entity, wherein all local ORS record categories belong to an RSC record category.

6. The method of claim 1, further comprising:

propagating, by the ERM, an organizational tree structure to the RMS, wherein only record categories which map to organization-specific retention schedules (ORSs) have an association with an organizational node.

7. The method of claim 6, further comprising:

determining, by the RMS, which record categories are relevant to a lower level of an organization within a known organizational tree if there is no organization-specific retention schedule-based records category for said the record categories, wherein the RMS;

traverses one level up the organizational tree;

checks if there is any ORS-based record category associated with a parent organization; and

if not, repeats the traversing and checking steps until an ORS-based record category is found or a top level of the organization tree is reached; and

reconciling, by the RMS, between an end user'"'"'s organization and an organization local schedule that belongs to the user'"'"'s organization;

wherein a complex corporate level tree of record categories is exposed as a relatively small sub-tree view applicable to the end user.

8. The method of claim 1, further comprising:

creating a subset of a corporate file plan applicable to a given instance of an RMS.

9. The method of claim 8, wherein:

the ERM is further configured to determine which instances of the RMS contain records that belong to certain organization-specific retention schedules (ORSs) by querying data in an ERM database which describes an association between data source records and ORS records; and

the ERM is further configured to traverse up to retention schedule codes (RSCs) of the ERM, then traversing up to record classes, to identify a subset of an overall record categorization hierarchy once a list of ORSs is defined.

10. The method of claim 8, further comprising:

passing, by the ERM, only those disposition rules and events which are applicable to a given subset of a file plan.

11. The method of claim 1, further comprising:

filtering only a relevant part of a record category tree for a particular RMS to integrate the ERM into multi-RMS environments.

12. The method of claim 1, further comprising:

using ERM business aliases to simplify record search and declaration.

13. The method of claim 12, further comprising:

communicating, by the ERM, business aliases and their associations with organization-specific retention schedules (ORSs) to the RMS; and

performing, by end users of the RMS, record declaration or searching through the RMS by choosing a familiar business alias.

14. The method of claim 13, wherein:

the ERM is further configured to filter a record category tree by organization.

15. The method of claim 12, further comprising:

communicating the business aliases to end user applications when ingesting records through the end user applications.

16. The method of claim 12, further comprising:

exposing business aliases as folders or tags in legacy record migration tools.

17. The method of claim 12, further comprising:

disambiguating end user aliases by at least one of;

grouping the aliases into a hierarchy in which record category names or identifiers are presented as parent nodes of the hierarchy; and

prefixing or suffixing the aliases with a records category name or identifier always or whenever an ambiguity exists.

23. A computer readable, non-transitory storage medium programmed to store instructions which, when executed by a processor, execute the method of any of claims 1, 19, and 20.

18. A computer implemented apparatus for propagation of file plans from an enterprise retention management system (ERM) to one or more records management systems (RMS), the apparatus comprising:

a processor-based RMS that is configured to store a plurality of records which need to be preserved for a certain period of time to meet companies'"'"' regulatory obligations, the records comprising documents with associated metadata;

a processor-based ERM that is configured as a source of master data about record classification and record retention, the ERM configured to perform maintenance of record classes and retention/disposition rules and to propagate information to the RMS according to any of the following;

automatically via a connector between the ERM and the RMS;

semi-automatically via end user export of file plan information from the ERM in a form understood by RMS import tools; and

manually; and

a mapping for translation between ERM and RMS objects to effect propagation of file plans which comprise a combination of a retention category tree, disposition schedules, and events, and which defines how records are stored and disposed of in a given RMS, from said ERM to said RMS,

wherein the mapping for translation between ERM and RMS objects includes;

a mapping for translating ERM record classes within a classification of retention schedules to RMS record categories within a hierarchy of record categories set up within the RMS, and

a mapping for translating ERM retention schedule codes (RSCs) into next level record categories under categories created from record classes.

19. A computer implemented method for propagation of information from an enterprise retention management system (ERM) to one or more records management systems (RMS) configured to store a plurality of records, the records comprising documents with associated metadata, which need to be preserved for a certain period of time to meet companies'"'"' regulatory obligations, the method comprising:

providing a processor-based ERM that is configured as a source of master data about record classification and record retention, the ERM configured to perform maintenance of record classes and retention/disposition rules and to propagate information to the RMS; and

wherein the ERM is configured to provide a mapping for translation between ERM and RMS objects to effect propagation of file plans which comprise a combination of a retention category tree, disposition schedules, and events, and which defines how records are stored and disposed of in a given RMS, from the ERM to the RMS, the mapping including;

translating ERM record classes within a classification of retention schedules to RMS record categories within a hierarchy of record categories set up within the RMS,

translating ERM retention schedule codes (RSCs) into next level record categories under categories created from record classes.

20. A computer implemented method for propagation of file plans from an enterprise retention management system (ERM) that is configured as a source of master data about record classification and record retention, the ERM configured to perform maintenance of record classes and retention/disposition rules and to propagate information to one or more records management systems (RMS), the method comprising:

providing a processor-based RMS that is configured to store a plurality of records which need to be preserved for a certain period of time to meet companies'"'"' regulatory obligations, the records comprising documents with associated metadata; and

providing a mapping for translation between ERM and RMS objects to effect propagation of file plans which comprise a combination of a retention category tree, disposition schedules, and events, and which defines how records are stored and disposed of in a given RMS, from the ERM to the RMS, including;

translating ERM record classes within a classification of retention schedules to RMS record categories within a hierarchy of record categories set up within the RMS, and

translating ERM retention schedule codes (RSCs) into next level record categories under categories created from record classes.

21. An apparatus for propagation of information from an enterprise retention management system (ERM) to one or more records management systems (RMS) configured to store a plurality of records, the records comprising documents with associated metadata, which need to be preserved for a certain period of time to meet companies'"'"' regulatory obligations, the apparatus comprising:

a processor-based ERM that is configured as a source of master data about record classification and record retention, the ERM configured to perform maintenance of record classes and retention/disposition rules and to propagate information to the RMS; and

a processor-based mapping for translation between ERM and RMS objects to effect propagation of file plans which comprise a combination of a retention category tree, disposition schedules, and events, and which defines how records are stored and disposed of in a given RMS, from the ERM to the RMS, the mapping for translation between ERM and RMS objects including;

a mapping for translating ERM record classes within a classification of retention schedules to RMS record categories within a hierarchy of record categories set up within the RMS, and

a mapping for translating ERM retention schedule codes (RSCs) into next level record categories under categories created from record classes.

22. An apparatus for propagation of file plans from an enterprise retention management system (ERM) that is configured as a source of master data about record classification and record retention, the ERM configured to perform maintenance of record classes and retention/disposition rules and to propagate information to one or more records management systems (RMS), the apparatus comprising:

a processor-based RMS that is configured to store a plurality of records which need to be preserved for a certain period of time to meet companies'"'"' regulatory obligations, the records comprising documents with associated metadata; and

a processor-based mapping for translation between ERM and RMS objects to effect propagation of file plans which comprise a combination of a retention category tree, disposition schedules, and events, and which defines how records are stored and disposed of in a given RMS, from the ERM to the RMS, the mapping for translation between ERM and RMS objects including;

a mapping for translating ERM record classes within a classification of retention schedules to RMS record categories within a hierarchy of record categories set up within the RMS, and

a mapping for translating ERM retention schedule codes (RSCs) into next level record categories under categories created from record classes.

24. A computer implemented method for propagation of file plans from an enterprise retention management system (ERM) to one or more records management systems (RMS), the method comprising:

providing a processor-based RMS that is configured to store a plurality of records which need to be preserved for a certain period of time to meet companies'"'"' regulatory obligations, the records comprising documents with associated metadata;

providing a processor-based ERM that is configured as a source of master data about record classification and record retention, the ERM configured to perform maintenance of record classes and retention/disposition rules and to propagate information to the RMS according to any of the following;

automatically via a connector between the ERM and the RMS;

semi-automatically via end user export of file plan information from the ERM in a form understood by RMS import tools; and

manually; and

wherein the ERM is configured to provide a mapping for translation between ERM and RMS objects to effect propagation of file plans which comprise a combination of a retention category tree, disposition schedules, and events, and which defines how records are stored and disposed of in a given RMS, from the ERM to the RMS, the mapping including;

translating ERM record classes within a classification of retention schedules to RMS record categories within a hierarchy of record categories set up within the RMS, and

translating ERM organization-specific retention schedules (ORSs) into record categories under categories created from record classes.