Robots specifications and limits

• Small teams or individuals with light automation needs.
• No requirement to store Analytics data tables for use as input in subsequent scripts.
• Organizations that want to familiarize with automation capabilities before deciding whether to implement ACL Robotics Enterprise Edition.

• Large organizations that require full automation capabilities for continuous monitoring programs, but minimal involvement of IT resources.
• Organizations that intend to access cloud data sources only.
• No requirement to store Analytics data tables for use as input in subsequent scripts.
• Data storage and processing requirements fall within imposed limits (specified below).
• Organizations that want to familiarize with automation capabilities while waiting for deployment of an on-premise Robots Agent.

• Large organizations that require full automation capabilities, and data storage and processing without imposed limits, for continuous monitoring programs.
• Organizations with large analytics programs that need the processing scalability and load-balancing provided by a multi-agent cluster.
• Organizations that want data processing to occur on their own network, and the option to store all data locally with no data uploaded to the cloud.
• The need to store Analytics data tables for use as input in subsequent scripts.
• The need to connect to customer SAP data sources

• Enterprise Edition No limit

• Professional Edition On-premise Robots Agent not supported

100 per robot type

300, in total, per Diligent One account

• Enterprise Edition No limit

• Professional Edition 5

  The limit applies separately to development mode and production mode, so you can have a maximum of 10 tasks per robot across both modes (5 development + 5 production).

• Enterprise Edition No limit

• Professional Edition 1

  The limit applies across both development mode and production mode – that is, 1 automated robot at a time in all of Robots. You are free to disable and enable tasks to change which robot is automated.

  Note

  Tasks can only run if they are enabled.

• scheduled

• run ad-hoc (manually)

• scheduled

• run ad-hoc (manually)

• triggered by Diligent One event (functionality not available yet)

No limit

5

The limit applies across both development mode and production mode – that is, 5 tasks running simultaneously in total in all of Robots.

5 per agent

The limit applies across both development mode and production mode – that is, 5 tasks running simultaneously in total in all of Robots, per agent.

Professional Edition On-premise Robots Agent not supported

5

The limit applies across both development mode and production mode – that is, 5 tasks running simultaneously in total in all of Robots.

50

The limit applies across both development mode and production mode – that is, 50 tasks running simultaneously in total in all of Robots.

• be a collaborator for the robot

• degree of access controlled by the collaborator's robot role (Owner, Editor, Reviewer)

• Diligent One platform automation

• light data analysis

• Python

• Pandas, NumPy, Requests, and other standard Python libraries

• HCL custom Python library (HighBond Command Language)

on-premise

Professional Edition On-premise Robots Agent not supported

• commands requiring user interaction

• NOTIFY

• EXECUTE

• RCOMMAND

• Analytics R and Python functions

• Machine learning commands: CLUSTER, TRAIN, PREDICT

• commands requiring user interaction

Cloud-based Robots Agent

The Robots Agent is co-located with the Robots app in a secured data center operated by Amazon Web Services (AWS).

On-premise Robots Agent

The Robots Agent is installed locally on a server within your network.

Professional Edition On-premise Robots Agent not supported

Cloud-based Python engine

The Python engine is co-located with the Robots app in a secured data center operated by Amazon Web Services (AWS).

Cloud-based Robots Agent and Robots app (AWS)

All data in secured AWS data centers is encrypted in transit and at rest.

For more information about Diligent One security and data privacy, see Diligent Trust Center.

One of the following options, configurable by the customer:

• Keep all data on premise
• Upload non-Analytics result files and result logs to the Robots app
• Upload Analytics result tables, non-Analytics result files, and result logs to the Robots app

You can manually upload non-Analytics related files unless the Robots app is configured to keep all data on premise.

Analytics data tables (working tables) are always kept on premise regardless of how Robots is configured. Only the table layout is uploaded to Robots.

Cloud-based Diligent One data storage location (AWS)

All data in secured AWS data centers is encrypted in transit and at rest.

For more information about Diligent One security and data privacy, see Diligent Trust Center.

• data storage: 20 GB
• RAM: 3 GB
• processors: 1
• maximum processing time per task: 60 minutes

• Governed by the specifications of your network server housing the on-premise Robots Agent.

• 1 GB

• 2 GB (zipped size)

• cloud databases and cloud data services accessible with Diligent data connectors
• uploaded flat files

• customer network data sources
• customer ODBC data sources
• customer SAP data sources

  (requires an additional subscription entitlement)

• cloud databases and cloud data services accessible with Diligent data connectors
• Analytics data tables
• uploaded flat files

• cloud databases and cloud data services accessible with Python data access methods and API-based connections.

• uploaded flat files

Analytics result tables:

• download and open locally in Analytics
• export and view in Results

  Professional Edition maximum of 5 tables in total in Results

Analytics result tables:

• if configured, download and open locally in Analytics
• open locally via connection between Analytics and on-premise Robots Agent
• export and view in Results

• download and open locally
• export and view in Results

Non-Analytics result files:

• download from Robots and open locally

Non-Analytics result files:

• if configured, download from Robots and open locally

Analytics data tables (working tables):

• not supported

  Temporary Analytics tables are not saved after data processing is complete.

Analytics data tables (working tables):

• open locally via connection between Analytics and on-premise Robots Agent

• download and open locally

Log files:

• Enterprise Edition view in Robots, or download and view locally

• Professional Edition download from Robots and view locally

Log files:

• if configured, view in Robots, or download and view locally