How are the benefits calculated in Automation Hub?
The estimated savings (in hours saved and money) are the output of the Detailed Assessment, based on the algorithm designed. The formula designed details as the algorithm is UiPath's Intellectual Property( IP) .
However, a small visibility on what contributes to computing the Automation potential % and the Ease of implementation % is listed below :
- The Benefit in hours saved is computed as the Automation Potential % * Total Time Needed to Perform the Work - AS IS Process (hours/year)
- The Benefit in money is computed as the Automation Potential % * Cost/year for the process AS IS
- Based on the information filled in (regarding the frequency, average transactions per frequency, average processing time, error rate, audit time) -> Total Time Needed to Perform the Work - AS IS Process is computed as how many hours are spent in a year by the humans to perform the process AS IS.
- If the frequency is Daily -> then the information "Average Working Days/Year" from Employee profile is used to compute how many transactions are performed in a year (multiply daily transaction by the defined value for average working days/year)
- For all the other frequencies, the transactions per year are computed: Weekly -> multiply by 52, Bi-weekly -> multiply by 26, Monthly -> multiply by 12, Quarterly -> multiply by 4, Yearly -> multiply by 1.
- "Cost/Year for Process AS IS" = "Average Employee Full Cost/Year" * "FTEs required"
- Estimated benefits in hours/year = "Total Time Needed to Perform the Work - AS IS Process" * Automation potential %
- Estimated benefits in currency/year = "Cost/Year for Process AS IS" * Automation Potential %
Where the Automation Potential % is computed based on the answers from the other sections in the Detailed assessment: how digital it is, how structured is the input, Number of Ways to Complete the Process.
*details around the weightage for each factor is undisclosed.
- Process Stability
- Applications Stability
- Structured Input
- Process Variability
- Process Length
- Number of Applications
- Whether it is accessed through a Thin Client
- Scanned input
The Number of Employees Performing the Task field does not have any impact on the calculation. It is used in the Cost Benefit analysis, in the case of attended automation (you need as many attended robots as number of employees).
More information on Average Work to be Reviewed / Audited - To compute what is the total number of hours spent on performing the Process AS IS, during a year (before automating).
The total time includes: time spent by the employees performing the work + time spent by the employees to correct the work identified as faulty (due to error rate) + time spent to review the transactions performed (time spent by auditor).
- For this reason the Average Work to be Reviewed/Audited (% of Total Volume) and Average Review or Audit Time/Transaction (min) is requested. Because it represents an effort that is consumed for the process AS IS.
- Once automated, by replacing a part of the transaction being performed by errors (because a Robot covers a part), then the audit time also decreases (in absolute value).
Total Processing Time: The details like "Task/Process Frequency", "Activity volume average (per selected frequency)" and "Average processing time" to compute Total processing time (in hours/year) are utilized. So, if the user defines as "We perform 10 transactions with a weekly frequency" or "520 transaction a year" (52 weeks = 1 year), it leads to same total number of transactions per year.
Benefit (hours saved/year) = The Automation Potential % multiplied by the Total Time Needed to Perform the Work - AS IS Process (hours/year) .