In a post back in January, we described implementing a simple Records Management solution. Often times we have seen clients struggle with the large footprint of the Documentum Retention Policy Services (RPS), Records Manager (RM), and Physical Records Manager (PRM) products, and a limited budget to implement a records management solution. This post describes how several RM features have been implemented using minimally modified out-of-the-box ECM functionality. Continue reading
When first starting a records management (RM) program it can seem daunting and insurmountable, but once the decision is made to not keep everything forever the real work begins. At its most basic, there are three activities in an RM program: retention, disposition, and holds. This post will present a solution approach that leverages minor customizations and out-of-the-box (OOTB) capabilities to satisfy most electronic and physical records management requirements.
TSG recently assisted a client with upgrading their Documentum 6.5 environment to 6.7. Products included Content Server, xPlore, Business Process Manager (BPM), Content Transformation Services (ADTS, AVTS, MTS), DA, Webtop, Records Manager, Retention Policy Services (RPS), Archive Services for Reports (ASR), and TaskSpace. The client also runs TSG’s High Performance Interface (HPI) and OpenContent products. Continue reading
TSG recently worked with a client evaluating EMC’s Retention Policy Services (RPS) product. For those unfamiliar with RPS, RPS is used for automating content retention and disposition, while also allowing for holds that prevent disposition. Additional information can be found on the EMC website here: http://www.emc.com/products/detail/software2/retention-policy-services.htm
The client liked many of the features of the product and its user interface (which is very similar to Webtop). One of the appealing features is that RPS allows a clear separation of duties between roles of users along with multiple tools for managing retention with the WDK-based Retention Policy Services Administrator (RPSA). In this case, the end users are never aware that RPS is being used unless they try to delete a document that has a retention policy applied. For this client, a major concern focused on the RPS performance overhead of applying retention policies and mark ups to a multi-million document repository.