You have an existing BPM Practice. Wonderful. More than half the job could be done for you. This article may bring you to terms with the second half and the newer bits.
Does RPA fit with BPM?
Yes. RPA is another form of Business Process Automation. BPA is the cherry at the top of the BPM life-cycle.
In the BPM space some of us have been doing BPA; particularly at the business process layer. Actually, this is the main paradigm for BPMSs' which translate graphical process models to workflow rules which in turn orchestrate application user interfaces. Aha!
In really simple terms, that was BPM at the business process layer. The end result of which is either back-end process integration or human-centric process applications with normal front-end user interfaces.
With time, particularly the WS-* flavor of SOA has moved from an early unified business process layer to building smaller services to address particular concerns at and within the same BP layer. Yet, that same flavor, even with microservices, never really came to realise presentation layer integration. Oops!
After some more time, RPA arrived with some good tools particularly suited for presentation layer integration. Yet, because RPA emerged from outside the traditional BPM space, it hadn't really come to terms with the microservices bit within its own accord.
So, what does that really mean?
Oh well, the following is what that divide does to the overall BPM/RPA landscape:
Here are 4 things you need to bring your BPM practice to terms with RPA. This is what you really need to achieve to bring things together. We recommend setting a short time-frame to having these items first realised. Here they are:
Download the PDF resource on adding RPA to BPM practice.