top of page
  • Writer's pictureAmanotes

How to reduce 15000 manual working hours by applying Robotic Process Automation?

Updated: Apr 20, 2023

Our team at Amanotes is hugely excited about our big goal of freeing up 15000 manual working hours by applying robotic process automation (RPA) to our business processes. We recognize that by automating repetitive tasks and techniques, we can improve productivity, reduce errors, and accelerate our time to market. This article will take you on a quick trip about how we apply RPA to minimize human efforts and maximize efficiency.

Table of content


What is robotic process automation (RPA)?


Robotic process automation (RPA), refers to the use of software robots or artificial intelligence (AI) to automate repetitive, rule-based tasks previously performed by humans. RPA tools can be programmed to mimic human actions such as logging into applications, copying and pasting data, creating, adjusting, and extracting information from documents, setting up projects, and making decisions based on predefined rules.


Value stream mapping


Value-stream mapping usually employs standard symbols to represent items and processes, therefore knowledge of these symbols is essential to correctly interpret the production system problems
Value stream mapping - source: internet

The number of 15,000 manual working hours may initially seem daunting, as it is equivalent to almost two years of working hours. However let’s take a look at the diagram, the production lead time is 14 days, meanwhile, the actual processing is only 585 seconds. Upon closer inspection, it is possible to significantly reduce this number by eliminating non-value-adding time in the production process. By using Value Stream Mapping (VSM) - a powerful visual representation of the entire process, including the time and resources required for each step, organizations can implement changes to streamline the process, reduce lead times, and increase efficiency.


How do Amanotes apply RPA?


Use login/authentication mechanisms (2 Factor Authentication) with OTP services

Authentication using Puzzle Captcha, source: internet

At Amanotes, we require a large number of daily reports for our huge game library which often entails accessing third-party services for the necessary analysis. These services typically require an additional layer of authentication, such as OTP codes, puzzle captcha, and CAPTCHA. Manual authentication is not feasible since the continuous process cannot be interrupted while waiting for human action. Recognizing the importance of authentication in RPA, we have made it a priority to invest in an OTP service to streamline the authentication process.


Emulate human-like actions on Google Chrome automatically


This involves integrating with third-party services that lack a public API, allowing our product owners and developers to streamline their workflows and minimize the risk of errors caused by human involvement. To achieve this, we utilize Headless Chromium, a tool that enables us to automate the browser without the need for a visible window.


By automating this process, we are able to reduce the number of steps required to get reports and format input data, generate registrations, and complete information forms using the available formats. This approach is applied across all of our product life circles ranging from ideation, protocol, testing, and launch to close, allowing our Product Owner and developers to centralize and simplify the processes.


(Demo video on how Headless Chromium works - source: Amanotes )


Build a job queue that's parallel and sequential


In simple terms, a job queue is a list of tasks that need to be executed by a computer system. A parallel job queue means that multiple tasks can be executed simultaneously, whereas a sequential job queue means that tasks need to be executed one after the other. Using a job queue that can handle both parallel and sequential processing, the software bots can work on multiple tasks simultaneously, accelerating processing times and increasing efficiency.


Applying this, the work process can be carried out 24/7, allowing for maximum productivity, as opposed to a traditional working day consisting of only 8 hours for human task performance. At the same time, sequential processing ensures that tasks are executed in a logical order, minimizing errors and ensuring accuracy.


Schedule tasks


With this approach, we can set up automated tasks to run at specific times, intervals, or according to certain triggers. For example, we can schedule a report to be generated and delivered to a specific email address every week or month. This saves a lot of time that would have been spent manually generating and sending the report. Moreover, we can arrange frequent system scans to identify any issues or glitches, enabling us to address them promptly and avoid potential downtime. Additionally, we can include in the automated report an auto-check of license expiration dates and notify relevant teams to prevent costly oversights.


At Amanotes, we provide global game solutions but our team only works during office hours, making 24/7 delivery of data or applications impossible. However, we utilize scheduling to minimize manual operation outside of working hours, ensuring our services remain available to customers around the clock. Count on us for the best possible gaming experience, anytime, anywhere.


Auto upload and sync the creative video into other Ad networks, source: Amanotes

Conclusion

At Amanotes, we leverage the power of RPA to ensure efficient resource utilization and provide high-quality services to our customers. We rely on the scheduling tasks mechanism to automate our workflows and reduce the need for manual intervention, enabling us to deliver value to our customers faster and more efficiently.


If you want to join us in our mission to provide high-quality services while maintaining cost-effectiveness and competitiveness in the market, we invite you to explore our career opportunities. Together, we can leverage the power of RPA to drive innovation and achieve success.





Sang Phan - Full-stack lead

Khoa - Full-stack developer

242 views0 comments

Comments


Blog

bottom of page