- Getting Started
- Framework Components
- ML Packages
- Pipelines
- Data Manager
- OCR Services
- Document Understanding deployed in Automation Suite
- Document Understanding deployed in AI Center standalone
- Deep Learning
- Licensing
- References
- UiPath.Abbyy.Activities
- UiPath.AbbyyEmbedded.Activities
- UiPath.DocumentUnderstanding.ML.Activities
- UiPath.DocumentUnderstanding.OCR.LocalServer.Activities
- UiPath.IntelligentOCR.Activities
- UiPath.OCR.Activities
- UiPath.OCR.Contracts
- UiPath.DocumentProcessing.Contracts
- UiPath.OmniPage.Activities
- UiPath.PDF.Activities
Install and Use
This page describes how to deploy and configure Document Understanding, as well as special instructions on how to use Document Understanding on Automation Suite.
Document Understanding has a dependency on AI Center, meaning that AI Center always needs to be installed if Document Understanding is installed.
Also, Orchestrator must be activated before using Document Understanding.
Before starting the Document Understanding installation, make sure to check and satisfy all requirements for Automation Suite for single-node here and for multi-node here.
A GPU is strongly recommended for Document Understanding in one of the following scenarios:
- If you retrain the Document Understanding models
(DocumentUnderstanding - the general model, Invoices,Receipts, etc.)
on AI Center.
Training on CPU is 5-7 times slower and model performance degrades compared to training on GPU.
- If you run UiPathDocumentOCR (non-edge
version) on AI Center to process more than 2 million pages a year.
If you do not use a GPU, slow performance may impact the product experience.
For more details about how to provision a GPU, see Adding a dedicated agent node with GPU support.
Document Understanding requires the FullTextSearch feature to be enabled on the SQL server. Otherwise, the installation fails without an explicit error message.
