What is our primary use case?
I work for different clients. Currently, I have three clients, and I use it based on their requirements.
We have contract generations, and we extract data from contracts. This is our primary use case. We are receiving documents through an omnichannel, and we extract data based on the business requirements. After that, we automate and upload the data to Salesforce and SAP.
We process 1,000 to 1,500 invoices weekly. They are mostly semi-structured contracts. There are also some invoices or printed bills.
How has it helped my organization?
Document Understanding has been very helpful for my project. Its architecture and concept were very helpful for my process.
Document Understanding has saved us a lot of time. I have much more time. For example, in 2017, when I was doing the same normal extraction without it, it used to take two hours. Now it takes only 20 minutes to extract 20 to 30 documents. If our configuration and technique are very good, it would take only 10 minutes. Document Understanding is very powerful if a developer has good technical knowledge. By properly configuring the workflow, you save more time compared to other tools.
At times, we have business requirements for human approval. When required, the human approval or validation process happens immediately. We design the workflow for attended or unattended automation. Once configured, immediately after extraction, it will go for human approval. The automation happens based on approval or rejection.
It has a good framework. It takes care of all things. We sometimes need to configure manually, but generally, it takes care of 95% percent of error handling. Its framework gives very good results.
What is most valuable?
AI Center is helpful for creating data sets. Machine learning helps with some extraction. The ML extractor gives good results after training. It also gives automatic results. It automatically identifies the same type of invoices or a different type of classification. The ML extractor is very good.
What needs improvement?
The extraction can be better. ABBYY FlexiCapture has more capabilities than Document Understanding. It can also extract automatically without training, whereas with Document Understanding, we need to train everything. For example, we have uploaded ten invoices of a type, and when we upload the eleventh invoice, it can find approximately eight fields out of ten, but ABBYY FlexiCapture can find ten out of ten. More documents are required to train Document Understanding.
There should be Generative AI and sentiment analysis. These two things will be very good.
For how long have I used the solution?
I have been using this solution for three years.
What do I think about the stability of the solution?
I would rate Document Understanding a ten out of ten for stability.
What do I think about the scalability of the solution?
I would rate Document Understanding a ten out of ten for scalability.
How are customer service and support?
We sometimes require technical support from UiPath. Sometimes, we get an error, and we cannot find the solution on the web. We have to contact UiPath's support team. I have already contacted them two or three times.
The support experience varies based on the type of support plan. We have a silver membership. They also have diamond and gold memberships. If an organization has a diamond membership, support will be given very fast. For silver, it takes three to four hours depending on the emergency.
Overall, their support is good. I would rate them an eight out of ten for support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I was not using a similar solution previously. Before UiPath, I was a .Net developer. Stanford University was providing a code-based extraction tool that I was using.
Currently, we are also using ABBYY FlexiCapture. We are not using Document Understanding for handwriting. We are using ABBYY FlexiCapture for that. Document Understanding gives good results, but ABBYY FlexiCapture is tap-and-play. For extraction, ABBYY FlexiCapture gives very fast results, whereas Document Understanding requires some processes. To save time, I am using ABBYY FlexiCapture even though Document Understanding is more accurate than ABBYY FlexiCapture.
What's my experience with pricing, setup cost, and licensing?
I do not know about its price, but for large organizations, UiPath is cheap, whereas, for small organizations, UiPath is expensive. For example, if 500 licenses are needed for one company, UiPath is cheap. If only 5 licenses are required, UiPath is costly.
What other advice do I have?
I would advise taking a step-by-step approach. If you miss any step, the bot will fail. For large document extractions, you need to follow the step-by-step instructions provided in the UiPath Academy.
I have not used Forms AI, but I use AI Center. In AI Center, I am using some datasets. I am maintaining some data sets, and based on the business requirement, I use the data.
Its integration should be good, but I have not tried any integration with other tools. I have integrated ABBYY and UiPath, but I have not integrated Document Understanding.
I would rate it a ten out of ten. It is now a very mature tool.
Which deployment model are you using for this solution?
On-premises