Digital Transformation Journey

We keep reading and as business leaders claim that Robotic process automation (RPA) has made great strides in fulfilling its promise to the marketplace. RPA has positioned as a no-code end-user computing tool, owned, and operated by many business functions, that automates routine work tasks with quantifiable business results. Now, businesses have a digital workforce in the form of powerful new end-user computing tools positioned and priced attractively to operations and finance leaders. It has the power to reduce the dependency on traditional automation delivered by IT, improve productivity and accuracy, reduce operational risk, and enable redeployment of expensive human resources to tasks that add more value. But how far this claim is true or close to the reality need to be rechecked... We all know that RPA maturity model is designed across industry around two key components - the first one around RPA strategy or RPA operations and second is the levels of RPA Maturity that can be used...

The Robotics Process Industry is known for introducing & adopting several terms in its journey so far like - AI, IA, CoE, CV, CNN, DL, ML, NLP, NLG, iOCR, POV, POC, RNN etc. One term that is quite high in the list is “Proof of Concept”, or POC. POCs are not special to Robotics Process Automation, but very unusual if the RPA project doesn’t start with a POC. In general, a proof of concept (POC) serves as a stimulant for those businesses looking to leverage the RPA technology to improvise their business process outcomes. A POC can be built for one entire process or a small part within the process. Now a days the most surprising thing is that every company that is planning to use RPA technology believes religiously that they must start the work with a POC so that they can ensure and can see themselves that BOT software is working before full blown deployment. To a large extent this is justified, given the exceedingly high failure rate of the RPA projects. But it is bit difficult to ac...