ACC home page for administrators

As an automation administrator you can view operations-related widgets on the Automation Command Center (ACC) home page. These widgets provide information on the automation statuses, license and device utilization. This enables you to focus on the progress of the automation, drive optimal utilization of resources, and make efficient decisions.

Permissions

You must have the following permissions to access the operation-related widgets on the ACC home page.

  • View operations data
  • View and manage ALL devices (s)
  • View licenses
  • AAE_Queue_Admin
  • View private repo operation details

    This permission required to view Automation status - private widget.

  • View IQ Bot > View Administration and View all tasks from public processes > View all tasks from public and private processes.

    These permissions required to view the Document automations widget.

The ACC homepage provides you a holistic view of the automation landscape. The information is distributed within various specific sections.

  • You can see the consolidated dashboard details which displays all the information at a single glance.
  • The development details provides a quick glance at the automations run or scheduled by you. You can also view the automations which you have labeled or canceled the check-out operation.

  • The operational insights provides you comprehensive and statistical information about automation metrics and the device and license statuses. By default, you can view these data for the last 24 hours. The maximum time duration for which you can view automation details is for the last 90 days. For more details, see Time filter.

    Automation data
    Starting from Automation 360 v.32 release, Control Room administrators can view the private repository by default for various automation details along with public repository widget on the ACC homepage. The private repository enables you to review automations across various time periods (24 hours to 90 days), automation name and the user that initiated it, folder path, whether the automation completed successfully or failed, and any other details related to the automation run.
    Note: Only the user roles associated with View operations data > View private repo operation details permission can view the private repository on the ACC homepage.
    The various widgets provide you data that includes automation schedule and status, automation run time, most failed and most run automations, as well as the currently running automation details. You can use this information to:
    • Analyze recent executions.
    • Take corrective action for failed automations.
    • Plan capacity for the upcoming scheduled automations.
    • Work efficiently, improve reliability, and scale your automation program.
    • Understand the impact of automations, ensure all operations are running as required.
    • Monitor devices that are in use.
    Device data
    The widgets provide information about resource utilization of all the devices and average utilization of each devices on which automations are executed. The information includes device status, device details, average utilization of each device, and insights on KPIs related to queues and work items such as queue status and the number of work items processed in a queue. You can use this information to:
    • Plan the optimum usage of devices in the Control Room. For example, if the average utilization achieved over the last 24 hours on a set number of devices is very low, you can identify the total number of devices that are idle and deploy automations on those devices, thus improving their utilization.
    • Plan you automation deployments thus improving the efficiency. For example, if the number of active queues at a given point differs from the data 24 hours ago, you can check for any issue and proactively take action. Similarly, with the help of this data, you can restart paused queues and delete inactive queues if they are not required.
    • Understand the capacity available for additional automation scheduling, scaling automation program, and for planning the infrastructure budget.
    • Distribute the load for better performance, thus reducing the wait time for devices.
    License data
    Provides license allocation information for all users and all Control Room instances. It also provides details on purchased license counts and available licenses.

    This helps you realize the available capacity, drive optimal utilization of the licenses, and deliver value.

    For more information, you can navigate to the licenses page. See Manage licenses.

    Document automations
    Provides an overview of the total number of processed and failed documents, along with the documents that have queued for validation in Document Automation.
    API Task data
    • The API Task widget displays information about the top 5 most frequently used API Tasks. Like other widgets, it updates at a regular intervals to reflect the current top 5.
    • To view a detailed dashboard with additional API Task information, follow these steps:
      1. Click the three dots at the end of the widget.
      2. Select View details.
      The detailed dashboard includes:
      • Name - The name of the API Task.
      • File Path - The location of the API Task.
      • Total calls - The total number of API Task calls .
        Note: Regardless of how many individual APIs are invoked within an API Task, it is counted as a single call for tracking purposes.
      • Max concurrency - The maximum number of concurrent API Task instances that ran simultaneously.
      • Run-as-user - The corresponding Run-as-user associated to an API Task.
      • Modified by - The user who most recently made changes to the API Task.
    To configure concurrency or add API Tasks in forms, click the three dots at the end of the detailed dashboard and select the appropriate option. For more information, see Cloud device management (API Task).
  • You can view the compliance details in the form of a graphical insight. This helps you analzye the code quality of automations such as the total number of automations with high or low severity violations. It also shows the number of automations for which code analysis has not been performed.

    You can use this information to improve code readability and quality and control the structure of your automation code. This helps you improve the productivity of the developer and also enable complex automations to be more accessible.

    You can further navigate to manage policies page for more information. See Manage policies | Configure and assign code analysis policy.

  • You can use the links to quickly and easily navigate to other components or domains such as the pathfinder program, Automation Anywhere University, and pathfinder community. You can also use these links to navigate to other areas such as Automation Co-Pilot, CoE Manager, Bot Insight, and so on.