We have begun using Ariba Contract Workspace (ACW) as the sole repository of signed Contract Agreements and related electronic documents.
Our company records management dictates various retention schedules for documents
(e.g. documents associated with contracts are kept for 10 years from the expiration date of the contract).
Many of those documents are coming up for removal from the system.
We do not wish to be a manual task as there are far too many contracts and documents.
Is there any functionality available today with respect to the auto eDestruction of ACW documents?
The issue is not about eArchiving but rather eDestruction: the removal and destroying of the documents.
What future plans does Ariba have for on-Premise customers to satisfy this eDestruction need?
Ideally, documents would be tagged with a 'retention tag/retention date' at entry time and the document would automatically be purged from the system when that retention period is up. Functionality would also be needed to examine the retention settings of documents and visibility into what is next to be purged.
How are other on-Premise customers dealing or planning to deal with this retention issue?
Does the on-Demand solution have a solution for this retention issue?
Message was edited by: Bob Biros
Data Archiving and Purging for Contracts and Sourcing is a planned feature for the Ariba 9r2 release (scheduled for Q1 2014). The "purging" aspect of the feature will accomplish the eDestruction use case -- purged documents will be completely removed from the Ariba system (with the option to archive that data to a non-Ariba system if necessary).
The use case that you've provided regarding "retention tag/retention date" functionality would be addressed by the feature as well. Configuration of the archive/purge rules will allow businesses to define rules that determine what is archived and when it is archived, allowing for a "sliding window" for the archive/purge process. The functionality would also offer a preview of archive/purge candidates that can be reviewed prior to the archive/purge taking place.
On-Demand does not have an archive/purge feature at this time, although I know it has been discussed in detail and is under consideration for a future release.
We will be providing much more information regarding this feature (and many other features) during the 9r2 feature discussions that will be occurring in early 2013.
I was wondering if you had any updates pertaining to 9r2. Is it still on track for Q1 2014?
I've also heard that the letter "r" indicates that it's only for Ariba instances that are installed on the customer's server and that the letter "s" indicates that it's for the SaaS version. If that's the case, will these records management enhancements be available for customers who use the SaaS version?
Hi Bob, I have been asked to write up a CRD (Customer Requirements Document) about records retention / purge capabilities. Thus far, I have drafted the following key points and I welcome your input on these requirements:
I am not sure if this has progressed but one option would be for Ariba to leverage the CMIS integration standard to offload this challenge to an ECM platform - who have such information management capabilities as table stakes ( core capabilities ).
SAP have a strong relationship with OpenText , so it remains unclear as to why this has not been progressed or even the basic CMIS hooks so that customers can use any ECM platform of their choosing