1 of 1 people found this helpful
We are not looking to prove any hard dollar savings (or even soft dollars) while migrating to an automated process using Ariba. Instead, we will be implementing data collection through a monitor and measure process so that future improvements can be quantified for hard dollar savings.
There are quite a few obstacles in showing hard dollar savings when switching over from a manual process to an automated process. Lack of reliable data is probably the most significant factor. Manual processes commonly rely on manual data collection. For example, we recently did a comparison of our manually recorded cycle time to like-data manually captured by the departments we work with. A typical discrepancy ranged from -3 to +3 days. In at least one case, the wrong year was “fat fingered.”
Another roadblock is the “apples to oranges” comparison inherent in a manual to automated process change. One might be able to show a cycle-time reduction by comparing hours worked per contract before-and-after. On the other hand, cost-savings and quality (long-term contract survivability) require a wealth of long-term data. Even using an automated process, cost-savings and quality data-sets are challenging to collect, properly analyze, and quantify.
Our finance department scrutinizes the analysis methods used to show any hard dollar savings (as they should). Combine that with the questionable reliability of data from the manual process and it is unlikely hard dollar savings would be approved.