Support structure for installing “WinActor” in Thailand
RPA - WinActor®
About the developer : NTT DATA (Thailand)
It is a Thai company under NTT who develops RPA tools “Office Robot” to support and assist in the installation of RPA in Thailand.
Location : 6th Fl., Column Tower, 199 Rachadapisek Road, Klongtoey, Klongtoey, Bangkok 10110 Thailand
About Consulting and Installation Support : QUNIE
In order to use the robot to work for the user in the most efficient way. Proper handling and control of the robot is essential. To expand the scope of automation to be wider There are issues that need to be pondered as follows.
issue
1. Number of licenses to install Scaling from 10 to 100 licenses may take some time to implement.
2. It is necessary to have a holistic management or supervision of the large number of WinActors distributed as points on the computer or server.
3. To operate for the benefit of the organization Must make the issue of abuse, NoraRobot* problem. to be clear
*NoraRobot is a robot built by the responsible person or on the site and not managed to organize the event so the robot cannot understand the content of the event or who is using it.
picture showing usage
WinDirector is a tool to control and manipulate robots by “directing” and “executing” by product name.
For the adoption of WinActor to increase the number of licenses to be used more widely in the organization. and systematically managed WinDirector is a powerful tool.
Improvements and developments in-house using WinActor. It's a good idea to first try to implement a trial version of some of the work in order to evaluate the implementation outcome. When the guidelines for how to improve and develop within the organization The points mentioned in the previous section should be made clear. Then gradually put the robot management system.
Especially large customers with more than 100 licenses need to create a proper management control system.
Functions provided
WinDirector is a management control tool created by WinActor user voice.
There are many functions that solve the problems mentioned above. Able to manage robots on behalf of users like a personal secretary.
The functions provided are as follows. (To know more details, please contact)
topic
function
1
2
3
It takes a lot of time to increase the number of robot licenses.
task management function
Register the Scenario to be executed by WinActor as a “job” and perform WinDirector registered tasks in the order and time set. It is also possible to register to use multiple robots simultaneously.
centralized management and WinActor supervision
function limit function
Set the function for each user. It is possible to determine whether jobs or Scenerio can be registered from the Rights Management setup method. Therefore, it can be managed to suit that segment.
Terminal management function
Solve the problem of use in a good way, the NoraRobot problem. to be clear
user management
It is possible to register and manage terminal data where the robot is installed. Use the task management function to issue action commands to any registerable terminal.
Can register users who can use WinDirector.
Scenario management
Scenarios created in WinActor can be registered and restricted by linking them to groups owned by the user.
Image showing centralized management by WinDirector.
An overview of WinActor handling (client/server version) is as shown below.
Before WinDirector was installed, WinActor's Scenario was managed by users distributed across server or client PC profiles.
On installation, WinDirector allows centralized management of the Scenario and “view/edit/execute” permission associations by user group. It also allows management, supervision, control and implementation according to the scene of each segment as appropriate.
In addition, executing commands from WinDirector can perform full control of all robot operations. Either the client version or the server version.
Recommended system requirements (on-premises)
Recommended system requirements (less than 20 operating robots)
Management System Requirements (WinDirector)
CPU
2.5 GHz 64-bit processor, 2 cores or more
3.0 GHz 64-bit processor, 8 cores or more
Category
topic
Specification of RDS Server (WinActor Action Robot) *1
Active Directory Server Requirements * 2
hardware
1.4 GHz 64-bit or greater processor
Memory
8GB or more
16GB or more
2GB or more
HDD
500GB or more
300GB or more
146 GB or more
OS
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
software
Windows Server 2016
Middleware software
Java
PostgreSQL
Apache Tomcat
Remote Desktop Connection Manager
*For each middleware version, the supported versions differ depending on the WinDirector product model.
Recommended system requirements (21 to 50 working robots or less)
Management System Requirements (WinDirector)
CPU
2.5 GHz 64-bit processor, 4 cores or more
3.0 GHz 64-bit processor, 8 cores or more
Category
topic
RDS Server (WinActor Action Robot) Requirements *1
Active Directory server specification *2
hardware
1.4 GHz 64-bit or greater processor
Memory
16GB or more
16GB or more
2GB or more
HDD
500GB or more
350GB or more
146 GB or more
OS
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
software
Windows Server 2016
Middleware software
Java
PostgreSQL
Apache Tomcat
Remote Desktop Connection Manager
*For each middleware version, the supported versions differ depending on the WinDirector product model.
Recommended system requirements (Robot performs 51 to 100 operations)
Management System Requirements (WinDirector)
CPU
2.5 GHz 64-bit processor, 8 cores or more
3.0 GHz 64-bit processor, 16 cores or more
Category
topic
RDS Server (WinActor Action Robot) Requirements *1
Active Directory Server Requirements * 2
hardware
1.4 GHz 64-bit or greater processor
Memory
32GB or more
32GB or more
2GB or more
HDD
500GB or more
450GB or more
146 GB or more
OS
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
software
Windows Server 2016
Middleware software
Java
PostgreSQL
Apache Tomcat
Remote Desktop Connection Manager
*For each middleware version, the supported versions differ depending on the WinDirector product model.
*1 RDS Server Requirements
◆ Since the CPU utilization rate and memory utilization vary according to the contents of the scene to be executed, it is necessary to properly configure the machine separately.
◆ We recommend the following RDS servers.
・When using 20 robots simultaneously: 1 RDS server is recommended to be configured.
・ When using 50 robots simultaneously: 2 RDS server configurations are recommended.
・ When using 100 robots to operate simultaneously: 3 RDS server configurations are recommended.
*2 Active Directory server specifications.
This is a recommended spec when installing a new Active Directory server. If an Active Directory server is available on the network, an existing Active Directory server is recommended.
Recommended System Requirements (AWS)
Recommended system requirements (less than 20 operating robots)
Eligibility Requirements Management system (WinDirector)
CPU
Instance type: T3. large or more
(CPU : 2.5 GHz 64-bit processor, 2 cores or more / MEM : 8 GB or more)
Instance type: c5.2 x large or greater
(CPU : 3.0 GHz 64-bit 8-core processor or more / MEM : 16 GB or more)
Category
topic
Eligibility Requirements RDS Server (WinActor Operated Robot) *1
Active Directory Server Requirements * 2
hardware
1.4 GHz 64-bit or greater processor
Memory
Instance type: T3. large or more
(CPU : 2.5 GHz 64-bit processor, 2 cores or more / MEM : 8 GB or more)
Instance type: c5.2 x large or greater
(CPU : 3.0 GHz 64-bit 8-core processor or more / MEM : 16 GB or more)
2GB or more
HDD
500GB or more
300GB or more
146 GB or more
OS
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
software
Windows Server 2016
Middleware software
Java
PostgreSQL
Apache Tomcat
Remote Desktop Connection Manager
*For each middleware version, the supported versions differ depending on the WinDirector product model.
Recommended system requirements (21 to 50 working robots or less)
Management System Requirements (WinDirector)
CPU
Instance type : T3. large or more (CPU : 2.5 GHz 64-bit processor, 4 cores or more / MEM : 8 GB or more)
Instance type : c5.2 x larger (CPU : 3.0 GHz 64-bit 8-core processor or more / MEM : 16 GB or more)
Category
topic
Configure the properties of the RDS server (WinActor Action Robot) *1
Active Directory Server Requirements * 2
hardware
1.4 GHz 64-bit or greater processor
Memory
Instance type : c5.2 x larger (CPU : 3.0 GHz 64-bit 8-core processor or more / MEM : 16 GB or more)
Instance type : c5.2 x larger (CPU : 3.0 GHz 64-bit 8-core processor or more / MEM : 16 GB or more)
2GB or more
HDD
500GB or more
350GB or more
146 GB or more
OS
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
software
Windows Server 2016
Middleware software
Java
PostgreSQL
Apache Tomcat
Remote Desktop Connection Manager
*For each middleware version, the supported versions differ depending on the WinDirector product model.
Recommended system requirements (Robot commands 51 to 100)
Management System Requirements (WinDirector)
CPU
Instance type : T3.2x larger (CPU : 2.5GHz 64-bit processor, 8 cores or more / MEM : 8GB or more)
Instance type : c5.4 x larger (CPU : 3.0 GHz 64-bit processor, 16 cores or more / MEM : 32 GB or more)
Category
topic
RDS Server (WinActor Action Robot) Requirements *1
Active Directory Server Requirements * 2
hardware
1.4 GHz 64-bit or greater processor
Memory
Instance type : T3.2x larger (CPU : 2.5GHz 64-bit processor, 8 cores or more / MEM : 8GB or more)
Instance type : c5.4 x larger (CPU : 3.0 GHz 64-bit processor, 16 cores or more / MEM : 32 GB or more)
2GB or more
HDD
500GB or more
450GB or more
146 GB or more
OS
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
software
Windows Server 2016
Middleware software
Java
PostgreSQL
Apache Tomcat
Remote Desktop Connection Manager
*For each middleware version, the supported versions differ depending on the WinDirector product model.
*1 RDS Server Requirements
◆ Since the CPU utilization rate and memory utilization vary according to the contents of the scene to be executed, it is necessary to properly configure the machine separately.
◆ We recommend the following RDS servers.
・When using 20 robots simultaneously: 1 RDS server is recommended to be configured.
・ When using 50 robots simultaneously: 2 RDS server configurations are recommended.
・ When using 100 robots to operate simultaneously: 3 RDS server configurations are recommended.
*2 Active Directory server specifications.
This is a recommended spec when installing a new Active Directory server. If an Active Directory server is available on the network, an existing Active Directory server is recommended.