What is our primary use case?
This solution is primarily used for financial use cases like invoice processing and inventory reconciliation processes. Those are the classic use cases when we talk about IQ Bot. It deals with multiple types of invoices that have different structures, different data, and sometimes different images. This product has already been templatized and fits directly into any type of invoice coming in. If you have a new type of invoice then you have to train the tool to identify those new objects. We are partners with IQ Bot and also consultants. We assist our customers with implementing this tool. I'm an RPA director.
How has it helped my organization?
What I've seen with our clients in the last couple of years, especially with the STP, is that the solution is quite good when you train really well. It identifies the printed version, but nowadays it also identifies handwritten documents to some extent. The STP ranges between 50% to 60% success, especially on handwritten invoices, but we have also seen an increase in accuracy - somewhere between 60% to 80% - for printed invoices. Improved accuracy has been a benefit for us.
What is most valuable?
I think the product identifies really well and training is quite simple. Because of the templatization it directly slots in the company name, and other basics that are all pre-defined. Training time is minimal as a result.
What needs improvement?
I think improvement could be made where handwritten documents are concerned. If you have a printed invoice, it's easily identifiable, but if someone is writing the same thing in their own handwriting, then identifying it is much more difficult and less accurate. I'd also like to see more support available for our customers.
For how long have I used the solution?
I've been using this solution for two years.
What do I think about the stability of the solution?
It's stable but does require know-how. When you want to deploy these bots into production, the control room admin has to know what he or she is doing. The integration between IQ Bot and RPA is quite easy. This is where there can be a few challenges. If the person is not well trained, especially in the control room side, they might have some issues. But if they are well trained, it's stable.
What do I think about the scalability of the solution?
Scalability is quite good. I've never had an issue, it basically runs through how many bots you process so it keeps running one by one, because it has to read one at a time and it keeps running. If there's a memory issue or if the bots have not been written well, then probably the bots could fail. If you follow the Automation Anywhere best practices for development, then I don't think there are any issues. It requires a coding checklist from Automation Anywhere to make sure that it follows the standards.
How are customer service and technical support?
Because we are a partner we don't normally get into technical support. We receive help from Automation Anywhere directly.
How was the initial setup?
The initial setup is quite easy. Most of the time, we do a small POC then pick up one or two small devices, showcase them for those training in it and then create a bot using RPA. IQ Bot is only for intelligent document processing. It's only for the extraction, but the next step is to process that information which has been extracted by this IQ Bot. We use RPA to create the bots, extract the data and run through invoice processing, opening any SAP or Oracle application. It extracts the data from invoices, puts it into a CSE, Excel file, reads through the Excel file, then opens an application, and runs it through.
What was our ROI?
If you're buying this IDP tool, then you need to make sure you're going to get a substantial ROI. More importantly, the organization needs to have a vision as well as the ability to identify the right use cases for using IQ Bot. I've seen a few cases where organizations did not understand how this tool can be used and therefore did not achieve an ROI.
What other advice do I have?
From what I have seen in the industry, most organizations need intelligent document processing, because if you are using RPA, you have a financial department where you're doing invoicing or procurement, you're running purchase orders, or you have inventory, which requires inventory reconciliation. Every organization deals with documents, and the digitization of documents will increase the scale and scope of your process automation somewhere between 20% to 40%. You can also easily increase your ROI. This is the main task which requires a large manual effort with a lot of human error. You can reduce all those errors and your expenses. This tool automates it all and things are processed more accurately and quickly. On top of that, it works 24/7.
You do have to know how to use this tool, how to train the templates, to create that efficiency. It's part of the challenge. The main point is when you do a POC, you need to measure the cost of the software licenses, implementation, training, deployment versus your ROI. You have to make sure that if you're buying this IDP tool, then you are trying to get at least a substantial ROI. More importantly, the organization needs to have a vision as well as identifying the right use cases for IQ Bot. I have seen a few cases where organizations did not understand how this tool can be used and they didn't achieve the ROI.
I would rate this solution an eight out of 10.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.