The most important goal of the initial customer workshop is to classify processes for automation. The challenge is that, while as experts in the area of process automation we know what processes we are looking for, unfortunately in most cases we do not know the customer's operations well enough to be able to point them out while waiting.
Typically, workshops involve bringing specialists or managers to the subject of automation, showing examples and identifying the characteristics that the processes sought to characterize. During the workshops, many spontaneous proposals usually fall and the question is asked many times:
"Is this process suitable?"
So, what process is suitable and what isn’t? In general, the process must be evaluated in several aspects.
Is the process carried out entirely electronically, whether there are elements requiring physically processing of documentation? Necessity to print a document is not a problem but the problem is taking the document from the right binder and rewriting the variable. The more electronic process, the more susceptible to automation.
The process must be structurally possible in a format similar to the UML chart. Without this, the developer will not be able to create an efficient robot. Most business processes meet this condition. It is important to find out whether, at some stage there is no complex decision point at which the specialist makes a decision based on subjective factors.
The process should be repeatable - it should not change significantly over time. The more repeatable the process over time, the lower the cost of maintaining robots automating it.
The process volume is proportional to the savings potential. This is an optional element because for many organizations, savings are not the most important benefit of automation. Our experience indicates that process automation can be profitable when the process involves at least part-time.
A reliable analysis carried out in terms of the criteria described above can be implemented Internally by specialists or managers without expert knowledge in the area of process automation. Actions taken this way will not only save time and money. It will also enable RPA experts to make a quicker decision about choosing optimal processes and starting work. I recommend this exercise also to organizations that have not yet analyzed the possibilities of implementing RPA. Perhaps the potential is bigger than you think!