4 ms·
RPA can be a dangerous band aid. It often uses screen scraping or similar brittle interfaces that are known to change. Or, it doesn't know about certain error
by tyingq 6y ago
RPA can be a dangerous band aid. It often uses screen scraping or similar brittle interfaces that are known to change. Or, it doesn't know about certain error conditions, etc.
Also, if it's been running for months before it breaks, the humans that used to do the work are gone, or have forgotten how to do it.
- ackbar03 6y agoI've always found rpa a very curious thing. In some corners you have people really hyping it and how much value it can bring and everything e.g ui path and other products. But I can never imagine it to be a very good solution, the thing must be extraordinarily fragile and rule based clicking automation is a real pain to put together.
- monkeydust 6y agoDitto always felt like 'poor mans automation' to me but in some fields for some tasks it seems to deliver rapid ROI which is what the C suite love.
- afarviral 6y agoAt my work we are leaning heavily on RPA to automate away drudgery and ultimately reduce expendature. However it has been immensely frustrating, prone to errors and garnered endless suspicion. The experience has been that bots written by the service desk staff doing the job function better and are much more under our teams governance, which the official "automation" teams within our org are painful to deal with due to their lack of availability and not having first hand knowledge of the things being automated. I think the RPA approach requires dedicated people developing and monitoring the bots who have an active part in the process being automated. The difference in approach determines the result.
- tyingq 6y agoI've experienced the same. Centralized RPA teams tend to, for example, do web scraping when they could easily use an existing REST API. Because they either don't know it exists, or don't have that skill set. Similarly, seen things like using a email as a trigger, when the source application has configurable web hooks. Feels like there's an RPA culture of sorts to assume the things being automated only have human based interfaces.
- sitkack 6y agoThe work an RPA does is obvious, you can watch what it does. Your first statement is a trusism, any solution can be a dangerous band aid, if applied incorrectly. RPAs solve real problems now, really the only correct measure. Of the RPAs I have raised, I always watched them work, they just prevent mistakes. I would suggest taking a screen recording and verbally annotating it for posterity. Furthermore, nothing says your RPA has to run open-loop, one can put in checks to ensure that it hasn't gone off the rails.
- toss1 6y agoGood advice - carefully observing the process, annotating successful (& failing) processes and installing post-hoc checks seem like sound practices. Do you have other such practices to recommend? Can you say anything about what your production and testing stack look like (esp the versions that work better)?