RPA as a Service is Not New or Unique
Is an RPA platform or is a Partner most important when starting or continuing your automation journey?
This is a question we are often asked, and the answer isn’t always clear. As RPA started to take off in 2016/2017 the focus was on enterprise RPA vendors, e.g. UiPath, Automation Anywhere, Blue Prism and others. They all made promises that the technology would just work with little-to-no guidance or support, that they had a very clear and immediate ROI and the solutions would be built resiliently. Large ISP’s treated RPA similar to the way they implemented other enterprise technologies: throw resources at the problem with either too much strategy or not enough. I’ve read a statistic out there that says close to 50% of RPA projects fail. You can appreciate why this is the experience of too many. Often times, reasons that automations aren’t successful is because: a) there is not enough definition around the overall need and/or b) there is a lack of understanding of how to identify, create, and continue discovering more processes to automate. As I have shared before, the main reason I started CampTek Software, was because there is an obvious need for “support.” The bots need to be supported for their entire life cycle, from the analysis/discovery phase, development, testing/acceptance, and through production/hyper care, and legacy support.