BPA – Why? We already have BPM! Can they co-exist?
So your company has invested a great deal of money and countless hours into planning and implementing a Business Process Management (BPM) suite in an operating department. Now your boss starts asking you about something they read about Business Process Automation (BPA) and if your department could benefit from it – how do you respond?
While both a BPA and BPM project starts with some type of Business Process Mapping, and both aim to improve business process efficiencies, there are differences. Here is a quick look at some of the differences between the two.
Business Process Management:
- BPM projects tend to do an extremely deep dive into a business process looking for ways to “optimize” business process. These focus on holistic process improvement and not necessarily on process automation.
- Processes tend to be limited to a single functional area, and there are clearly defined boundaries. There are manual or clunky systematic handoffs between outside departments.
- BPM systems typically use a “pull” methodology in how work is presented to the end user. Users work from task “lists”, and pull their work from those lists. This method of work delivery leads to “cherry picking”, where a user will pull the work that he or she is most comfortable completing.
Business Process Automation:
- Means taking a process and looking for repeatable, manual steps within that process that can be automated using technology to increase efficiency.
- BPA implementations also cross functional areas to consolodate handoffs and present work to a user in a single unified interface.
- BPA software resides as a layer over top several disparate back end systems pulling and pushing data between these systems. The user will work from one interface instead of having to jump between multiple screens for multiple systems.
- BPA lends itself to co-exist with other systems including BPM systems. It should be used to create an end to end system with no boundaries between functional areas. It is not meant to replace but work with other systems such as CRM, IVR, backend mainframe systems, SQL based systems, web services and finally BPM and ERP systems. BPA ties all of the existing systems together for the end user and offers craddle to grave tracking and reporting.
BPA and specifically Communications-Based Process Automation (CBPA) seek to give organizations end to end automation and to utilize skills based routing. Again, this is the concept of “push” vs. “pull” methodology for delivering work to the user with the appropriate skill to complete. Instead of an end user’s “pulling”, the work it is “pushed”, similar to how a telephone call routes to a user in a contact center. “Work” can be a document, a telephone call, an email, or a chat that routes to the next available user.
These are just a few high level differences that I have experienced working on both types of implementations. I would love to hear others’ opinions and experience on the subject. What are your experiences with BPM, BPA or CBPA systems?
What differences have you noticed?