# Configuring fields for Automation potential

> :::note
Make sure the fields for Automation potential are correctly mapped in the Event table in the data model:
* `Automated`
* `Event_cost`
* `Event_processing_time`

:::note
Make sure the fields for Automation potential are correctly mapped in the Event table in the data model:
* `Automated`
* `Event_cost`
* `Event_processing_time`

  ![Fields for automation potential in the data model](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-fields-for-automation-potential-in-the-data-model-597696-7050c023-783c05c8.webp)
:::

## `Event_cost` and `Event_processing_time`

`Event_cost` and `Event_processing_time` used to calculate Automation potential are not part of the input data. You can configure these fields for the event log in Data transformations using SQL statements.

The following code block shows an example SQL query to define `Event_cost`.

```
case
            when tableA."Activity" = 'ActivityA'
                then {{ pm_utils.to_double(20.00) }}
            when tableA."Activity" = 'ActivityB'
                then {{ pm_utils.to_double(10.00) }}
            when tableA."Activity" = 'ActivityC'
                then {{ pm_utils.to_double(5.00) }}
            when tableA."Activity" = 'ActivityD'
                then {{ pm_utils.to_double(0) }}
     end as "Event_cost"
```

The following code block shows an example SQL query to define `Event_processing_time`.

```
case
            when tableA."Activity" = 'ActivityA'
                then 50000
            when tableA."Activity" = 'ActivityB'
                then 120000
            when tableA."Activity" = 'ActivityC'
                then 300000
            when tableA."Activity" = 'ActivityD'
                then 40000
     end as "Event_processing_time"
```

:::note
The time unit of `Event_processing_time` is milliseconds.
:::

## Providing data input using dbt seeds

For process apps that still contain the `Automation_estimates_raw.csv` seeds file in the `seeds\` folder of the data transformations, you can use this file to provide input data to be used for the calculations in the **Automation potential** dashboard. For all activities, you can provide the `Event_processing_time` (in milliseconds) and the `Event_cost`. The following illustration showns an example.

![Example seeds file](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-example-seeds-file-18952-fad9da09-8432ebec.webp)

:::note
If the event_processing_time is provided using the Automation_estimates_raw.csv seeds file, but not filled in for all activities, the **Manual processing time** for the remaining activities is NULL by default. Consider using the average throughput time as the event_processing_time for these activities.
:::

:::note
If you are using an app template where you provide an `event_log` as input, you can also specify the `event_processing_time` as a column in that file. Values specified on event level will take precedence over values specified per activity using the seed file.
:::