Hardware Requirements
Hardware and software requirements can vary depending on the deployment type (e.g., cloud-based or on-premises) and the scale of the environment being implemented. Evaluating the specific requirements of the deployment is critical to achieving optimal performance, scalability, and security while reducing the risk of challenges during deployment.
Small to Medium Deployments
Small to medium deployments in Robility is designed for organizations with moderate operational and scalability requirements. These deployments typically involve a limited number of robots, processes, and users, making them ideal for small to medium businesses or specific departments within larger enterprises.
The hardware requirements provided below are tailored for the development environment and may differ significantly from the specifications required for the production environment, which often handles higher workloads and greater complexity.
Development Environments
These requirements are based on a setup with 25 to 75 unattended robots running simultaneously. The configuration utilizes two machines:
1. Web Application Server: This machine hosts the web-based interface and services of the Robility Manager platform, handling communication with robots and facilitating user interactions.
2. SQL Server: This machine operates as the database server, responsible for storing critical data such as process logs, configurations, and execution details.
The required specifications for each are outlined below.
Web Application Server
| CPU Cores (>2GHz) | RAM (GB) | HDD (GB) |
|---|---|---|
|
4 |
16 |
100 |
SQL Server
| CPU Cores (>2GHz) | RAM (GB) | HDD (GB) |
|---|---|---|
|
4 |
32 |
100 |
Production Environments
Production environments for SMEs are designed to handle the organization’s live automation workload with stability, scalability, and security in mind, ensuring seamless operations as automation scales. For production environment, it is recommended to provide one dedicated server for each of the following,
1. Web application server.
2. SQL Server Database.
It sends messages to Robility Manager at a frequency of one message every 30 seconds. Within each 30-second interval, the Robot performs the following actions,
2 heartbeat requests sent by the Robility Runner (Unattended) in two different states:
a. Idle state: The first heartbeat is sent to indicate the Runner is in active state but not executing tasks.
b. Running state: The second heartbeat is sent when the machine is actively executing workflows.
When the robot is in the running state, it communicates with the Robility Manager every 30 seconds with the following requests:
a. Get workflow request: Ensures the workflow is properly extracted and required features are downloaded.
b. Stop workflow request: Checks if the bot has initiated the stop workflow action, enabling Robility Manager to monitor and control workflow execution.
Web Application Server
This outlines the requirements for web application server that supports up to 200 unattended robots in a production environment.
| Number of Robots | CPU Cores (>2GHz) | RAM (GB) | HDD (GB) |
|---|---|---|---|
|
25 to 50 |
4 |
16 |
100 |
|
50 to 100 |
4 |
16 |
100 |
|
100 to 150 |
4 |
32 |
150 |
|
150 to 200 |
4 |
32 |
200 |
SQL Server Database
| Number of Robots | CPU Cores (>2GHz) | RAM (GB) | HDD (GB) |
|---|---|---|---|
|
25 to 50 |
4 |
32 |
100 |
|
50 to 100 |
4 |
32 |
150 |
|
100 to 150 |
8 |
32 |
200 |
|
150 to 200 |
8 |
32 |
250 |
The hard disk drive requirements depend on the below points,
