Digital Transformation Journey

As we all know RPA takes the robot out of the human. In general terms, RPA is a type of software that mimics the activity of a human being in carrying out a task within a process and freeing them to do other tasks requiring human strengths. RPA projects follow Robotics development life cycle (RDLC), very similar to software development life cycle (SDLC), like any IT project. After the process prioritization and requirement gathering stages, the most important phase of RPA development is solution designing. We should give a sufficient amount of time to solution design before any implementation/coding happens because the success & failure of the deployment heavily depends on it. Also let’s make sure that each identified automated process should have a solution design document. While designing the solution we should always keep note of these few points… Trigger Point: Before any real coding or development happens, think about how the BOT will be triggered in the future. It is importa...

Someone said very rightly – “Automation is good, so long as you know exactly where to put the machine.” In all my previous blogs I wrote about BOT failure, ROI Modelling, Cost saving, RPA Governance, CoE, POC, POV etc. But then I realized that before taking a deep dive into any of these subjects, first we need to have a right RPA process identification & prioritization methodology in place. Everybody across the industry agrees that Robotic process automation (RPA) can make a big difference for organizations tormented by repetitive routine processes – the kind that suck up the productivity of people whose time would be better put toward more important work. But many are confused by what seems to be a deceivingly simple question — which are the right processes for RPA? The poor choice of process for initial pilot is the leading root cause for failure to meet customers’ expectations. Robotic Process Automation (RPA) doesn’t suit every process and in majority of cases we don’t have...