Skip to content

Dashboard

In the BotCity Insights Dashboard, you can concisely view critical platform data and essential indicators related to processes.

Who has access?

The Dashboard section is accessed only by users with the Administrator or Manager role.

See more at:

Financial

BotCity Insights allows you to record and visualize high-level information about financial results and impacts.

Among the financial information that is automatically calculated and displayed are:

Data inputs

For dashboards to be built efficiently and contain relevant data, it is necessary that you configure and enter all the required information beforehand.

  • In the Data Input section, you can configure and enter the information that will be used as the basis for building the dashboards.

  • In the Reporting Data section, you can find more details on how to report data through your automation code.

Reports

Each card has a link directing to its respective report.

Financial section of the BotCity Insights Dashboard showing four cards: ROI (235%), Total Savings ($21,345,326), Hours Saved (4860h), and FTE (21.8), each with a link to its respective report.

ROI

Abbreviation for "Return on Investment". This indicator measures the efficiency and profitability of an automation investment. It displays the rate of financial benefit obtained in relation to the initial implementation and maintenance cost of the solution.

How is ROI calculated?

The ROI calculation is based on the following formula:

\[ ROI = \frac{(\text{Total Savings - Investment})}{\text{Investment}} * \text{100%} \]

Total Savings

Refers to the quantifiable financial benefit obtained from the implementation of automation. This includes all direct and indirect cost reductions resulting from automation.

How is Total Savings calculated?

The Total Savings calculation is based on the following formula:

\[ \text{Total Savings} = \text{Sum of all human costs per item} * \text{Sum of produced items} \]

Note: The Total Savings calculation does not take into account the investment value, but rather the human cost per each processed item.

Hours Saved

Represents the total hours of human work replaced by automation. This indicator quantifies the time it would take for people to manually perform the same tasks executed by the bots.

How is Hours Saved calculated?

The Hours Saved calculation is based on the following formula:

\[ \text{Hours Saved} = \text{Human time per item} * \text{Items processed by the bot} \]

Note: The result represents the total hours that would be spent by humans to process the same number of items that the bots executed.

FTE

Abbreviation for "Full-Time Equivalent". This indicator measures productivity by comparing the number of items a robot can process to the number of items a human can process in the same period of time.

How is FTE calculated?

The FTE calculation is based on the following formula:

\[ FTE = \frac{\text{Human Time per Item} * \text{Items Processed by the Bot}}{\text{Total Human Work Time per Month}} \]

RPA Initiative

In the chart you can track the evolution of the initiative over time through the number of Automations, Runners, and Tasks executed in production. You can also track cards with the total automations and total items processed in the platform.

How are these indicators calculated?

  • Evolution over time: The chart shows in line format the number of Automations created (orange), Runners (green), and Tasks executed (blue), month by month, over the last year. You can clearly see the numbers increasing as the initiative grows.
  • Total automations: This card shows the sum of all automations the workspace has, and by clicking it you can see each of them in a list in the reports section.
  • Total items processed: This card shows the count of each item successfully processed in this workspace; by clicking the card link you can access the tasks report and view the number of items processed by each one.

RPA Initiative section of the BotCity Insights Dashboard showing a line chart with the evolution of Automations (orange), Runners (green), and Tasks (blue) over the months, and two side cards with Total Automations (11) and Total Items Processed (293,262).

Automation Efficiency

In this section you can view the efficiency of automation processes.

In addition to an indicator with the total number of errors and the success/accuracy rate, you also have access to a chart with the number of errors per automation.

How are these indicators calculated?

  • Total items failed: This card shows the count of each item that failed to process in this workspace; by clicking the card link you can access the tasks report and view the number of items that failed in each one.
  • Success rate: Proportion of items successfully processed in relation to the total items executed. By clicking the card link, you can access the report to view the number of items processed successfully, failed, and the success rate of each automation.
  • Ranking of failed items per automation: The chart shows the automation processes with the highest number of failed items, ranked in descending order.

Automation Efficiency section of the BotCity Insights Dashboard showing a card with Total Items Failed (141), a donut chart with the Success Rate (72.35%, split between Success in green and Error in red), and a horizontal bar chart with the Ranking Items Failed per Automation.

Capacity and Velocity

In this section you can view information about the workspace's Runners and also get a general view of the automation downtime rate.

Capacity and Velocity section of the BotCity Insights Dashboard showing a bar chart with Runner utilization by day of the week (Runners Utilization by Weekdays) and a donut chart with the Downtime Rate (92.91% uptime in green and downtime in gray).

Runner Utilization

The chart shows the task distribution trend by day of the week, considering the behavior over the last 30 days.

By accessing the link, you can view the Runners report for the workspace.

More information

You can view more detailed information about the Runners by accessing the Runners Data page.

Downtime Rate

The downtime rate of an automation can be understood as the percentage of time spent processing failed items.

Thus, the rate refers to the proportion of the sum of time spent on failed items, considering the total execution time of the tasks.

For example, considering a scenario where the task processed 100 items successfully and 1 item failed during a 4-hour period, the downtime rate corresponds to the calculation of the time spent processing that failed item.

By accessing the link, you can view the automation ranking based on the downtime rate of each one in the reports section.