The Rise of Robotic Process Automation

In contrast, a full specification for making tea would require a tea cup, a volume of water, a thermometer, a timer, a measured quantity of tea, etc. It defines what should happen when the thermometer or timer is broken. It would check that the tea cup is large enough to hold the volume of water and describe the result otherwise. The software engineering life cycle describes the formal process of software development from gathering requirements to coding, testing, documenting and delivery. Even in its agile form with minimal up-front specification, the software development process is necessarily formal to understand and capture the objectives and deliver a verified solution that can be understood, integrated into other solutions, maintained and perhaps reused in the future. These are critical, particularly as the number of users and size of the solution increase.

RPA fills the space between the lightweight macros and heavyweight software engineering to efficiently provide solutions. It sometimes utilizes a recorded script (like Excel) that enables a solution to be developed without programming, but more commonly uses a scripting language to construct a rule-based workflow. RPA adds enough documentation and tests to achieve its goal without being generalizable. Unlike the Excel macros that function only in Excel, RPA operates at the user-computer level so it mimics a user actions. This user-interaction approach can even transform the automation of legacy systems written by former employees with no documentation. Rather than trying to understand the system and programming interface (API) yet alone try to rebuild it, RPA can interact with the legacy system and add functionality with a user-level business process understanding. Furthermore, RPA solutions solve existing challenges of software versioning, deploying the software across enterprise computers, auditing processes, enabling access security, load balancing computationally-intensive tasks across systems and even disaster-recovery.

Can we replace our software infrastructure with RPA?

With most businesses today centered around data, companies aim to effectively leverage their data to make better, timely decisions. Software engineering focuses mostly on the storage and access of data, whereas RPA focuses on the user workflows. In that sense, RPA depends on the formal software engineering management of the data and enhances user activities through automation. RPA only manipulates data through the software system’s user interfaces which is slower and less efficient than API access, but RPA can be scaled to overcome these limitations. As companies productionize 100s of RPA scripts, the challenge of maintaining, interconnecting and perhaps reusing the scripts will require additional specifications, testing and documentation that encumbers their software engineering counterparts.

RPA is the primary technology for rapidly automating existing user processes across industries. Accounting and finance organizations have led the way due to their repeated auditable processes. In the pharmaceutical space, Pfizer is using RPA for report processing for the FDA, clinical trial management and product labeling. The range of opportunities seems almost endless.

Although RPA has already added significant value to the workplace, it doesn’t currently use artificial intelligence (AI). General purpose AI tools such as OCR enable RPA workflows to scan and recognize texts, and some natural language processing capability has entered the workflows but the current RPA technology is mostly running a set of business rules. Enabling AI to assist with each individual’s business decisions will require machine learning systems to be trained for each specific human decision. Such training currently requires data science expertise, but recent AutoML advances show promise in training AI systems to make decisions automatically. This enhancement of smart RPA capabilities will certainly transform the workplace.