- Release notes
- Getting Started
- Permissions
- Starting as
- Admin Console
- Workspace
- Explore
- Share Idea or Automation
- Dashboards
- My Tasks
- Notifications
- Email Notifications
- Resources
- Studio Integration
- Task Capture Integration
- Automation Store
- Additional Resources
Execution Assessment
This assessment is used to connect live automation ideas with their corresponding package in UiPath Orchestrator Cloud and to define the business data needed for computing the Actual benefits based on the automation's successful runs. The information from the Execution Assessment can later be used for ROI reporting in UiPath Insights.
- Execution assessment is only available for automation ideas in Live phase.
The Referenced questions and KPIs section is set by default to be hidden in the execution assessment. The questions and KPIs within this section are only needed to calculate the KPIs defined in the Actual saving data and Total actual savings per automation idea sections.
|
Section |
Field |
Details |
|---|---|---|
|
Actual saving data |
Select one or several Orchestrator packages that reflect the automation build for the idea, and define the additional metadata needed for computing the actual benefits. This information with be used in UiPath Insights, for ROI reporting. | |
|
Orchestrator package |
Select the Orchestrator package. In case several packages cover the entire scope of the idea, use the add row button for adding a second package. This information will be used in UiPath Insights, for ROI reporting. | |
|
Using queues |
If the process using the package is run through queues, the actual benefit formula in Insights adapts to take queue item counts into account. | |
|
Reference manual time saved per run (min) |
Auto-computed based on values inserted in the Process Volumetry section of the Detailed assessment or the Citizen Developer assessment. | |
|
Final manual time saved per run |
Allocate 100% or less of the reference manual time saved per run (min). | |
|
Time savings per run |
Auto-computed based on whether the user overridden the Final manual time saved per run or not. Used in Insights for ROI reporting purposes. | |
|
Cost savings per run |
Auto-computed from the Employee Profile data and the Final manual time saved per run. | |
|
Yearly target automated volumes |
Auto-computed based on the manual volumes of transactions and the automation potential %. | |
|
Yearly target hours saved |
Auto-computed based on the data input per Orchestrator package. | |
|
Yearly target cost savings |
Auto-computed based on the data input per Orchestrator package. | |
|
Total actual savings per automation idea |
Aggregates the target actual savings for the entire automation idea | |
|
Total time savings per run |
Sum of time savings per run from the referenced Orchestrator packages. | |
|
Total cost savings per run |
Sum of cost savings per run from the referenced Orchestrator packages. | |
|
Total hours saved |
Sum of all yearly target hours saved from the referenced Orchestrator packages. | |
|
Total cost savings |
Sum of all yearly target cost savings from the referenced Orchestrator packages. |
Actual saving data is predefined with tabular questions. This helps you add one or several Orchestrator packages that reflect the automation build for the idea, and you can define the additional metadata needed for computing the actual benefits.
Total actual savings per automation idea helps you aggregate all the actual savings for one automation idea by summing up the values filled in or computed in the Actual savings data section, for every Orchestrator package linked to the automation idea.
