process-mining
2021.10
true
- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Adding automation estimates
Process Mining
Last updated Sep 2, 2024
Adding automation estimates
The Overview - Automation dashboard in AppOne enables business users to determine which manual events are possible candidates for automation. It displays, for example, information about the costs involved in the execution of an event which indicates the benefit of automating the event. See the illustration below.
Note:
Event costs are the costs for executing the event.
Event processing time is defined as the amount of time actually spent working for the event.
Event costs can be calculated from your dataset. However, if the information is not present in your source system it is also
possible to upload an
Automation estimates.csv
file that contains information that is used to calculate automation estimates, for example the labor costs of an event.
Note:
Automation estimates are either derived from your input data or calculated from data in the
Automation estimates.csv
file.
If the
Automation estimates.csv
file contains the event cost or the event processing time for at least one activity, this data is used to calculate the automation
estimates. If the file does not contain event cost or processing time data for all the activities, a warning message will
be displayed.
Below is a description on how to provide input data for automation estimates.
Create an
Automation estimates.csv
file and upload it to your workspace. It should only contain the headers Activity,Event cost, and Event processing time (hh:nn:ss). See the illustration below.
Edit the
Automation estimates.csv
file and add activities with the related event cost and processing times. See the illustration below for an example.
When you have added the automation estimates you can reload the
Automation_estimates_input
table to see if the automation estimates are visible in the connector. See the illustration below.