Method and apparatus for propagation of file plans from enterprise retention management applications to records management systems
First Claim
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, andtranslating ERM retention schedule codes (RSCs) into next level record categories under those created from record classes.
2 Assignments
0 Petitions
Accused Products
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.
-
Citations
24 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 23)
-
-
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.
-
Specification