The UiPath Document Understanding framework facilitates the processing of incoming files, from file digitization to extracted data validation, all in an open, extensible, and versatile environment.
Document Understanding is designed to help you combine different approaches to extract information from multiple document types. The main aim is to make the process of extracting data as easy as possible: creating one single workflow that will extract data from a variety of documents.
Before using the Document Understanding framework, it is recommended to understand the following Document Understanding Framework Components:
- Taxonomy What documents need to be processed and what data is required from them? Used to define the document types and the pieces of information targeted for data extraction (fields) for each document type, and formalizes this information into a dedicated Taxonomy structure. This metadata information is managed through the Taxonomy Manager.
- Digitization What does this file contain? Used to obtain the textual content and the structure of the incoming document, turning a file into machine-readable content so it can be further processed downstream.
- What types of documents from the taxonomy are found in this file? Used to automatically determine what document types are found within a digitized file.
- Is the predicted classification correct? This is how I can review and correct it. Used for assisting in the human validation and correction of the automatic classification and document splitting results.
- Did the human review the data? This is how the robot can learn from it. Used to pass the human validated information back to the classifiers, to use it to improve their future predictions.
- Data Extraction What data can be found in this particular document? Used to capture the information required for the identified document type, within the given input document and classification page range.
- Data Extraction Validation Is the extracted information correct? This is how I can review and correct it. Used for assisting in the human validation and correction of the automatically extracted data results.
- Data Extraction Training Did the human review the data? This is how the robot can learn from it. Used to pass the human validated extracted data back to the extractors, to use it to improve their extraction predictions.
- Data Consumption Used to export the validated data in order to consume it.
- Metering & Charging Logic Used to explain the consumption of units per page for each available service.
The diagram below presents the Document Understanding Framework components and how they relate to one another:
The Document Understanding framework is found in the UiPath.IntelligentOCR.Activities package. Once the UiPath.IntelligentOCR.Activities package is installed, the Taxonomy Manager wizard appears in the top ribbon of the UiPath Studio. This same package contains all the core document understanding framework activities.
The Document Understanding framework can be used not only with the out-of-the-box classifiers and extractors but also with any custom-built ones. These can be created using the abstract classes from the package and can be implemented as classification or data extraction activities. Custom-built OCR engines can also be created using the abstract classes from the package.
FAQs
The Document Understanding Process is preconfigured with a series of basic document types in a taxonomy, a classifier configured to distinguish between these classes, and extractors to showcase how to use the Data Extraction capabilities of the framework.
How to create an understanding document? ›
Creating and approving a document of understanding
- Create a new document of understanding (DOU).
- Propose the DOU.
- Approve the DOU scope.
- Propose the DOU specification.
- Approve the DOU specification.
- Submit the DOU for approval.
- Approve the DOU.
Document understanding is another technique in the automation toolbox that drives operational efficiency. You can streamline workflows, eliminate errors that would occur during manual extraction, use data more effectively, and more. Document understanding is also highly scalable.
How does UiPath document understanding work? ›
UiPath® Document Understanding TM uses a combination of robotic process automation (RPA) and AI to automatically process your documents. Document processing is a challenge every company faces. Manual document processing and legacy solutions limit business growth, increase risk, and deliver poor customer experiences.
What is the purpose of the document of understanding? ›
A memorandum of understanding allows all parties to clearly state all of their objectives and goals. This makes for less uncertainty and prevents future unexpected disputes from occurring.
What is your understanding of documentation? ›
Documentation is written information that describes and explains a product, system, or service.
Which are mandatory steps in the document understanding framework? ›
The scope activities (Classify Document Scope, Data Extraction Scope, Train Classifiers Scope, Train Extractors Scope) that are part of the Document Understanding framework allow you to use any document classification and data extraction algorithms that fit your use case and then train these algorithms.
How to document a process step by step? ›
How to document a process
- Identify the process.
- Place boundaries.
- List the expected result.
- Detail the inputs.
- Walk through the process.
- Determine who is involved.
- Utilize your process documentation system.
Steps to create a new blank document are as follows: a Step 1: Click the Microsoft Office button. b Step 2: Select New the New Document dialog box will appear as shown below:c Step 3: Select Blank document under the Blank and recent section It will be highlighted by default.
Why do you need to understand documentation? ›
Documentation plays a crucial role in ensuring quality and process control. By documenting every step of a process, it becomes easier to identify inefficiencies, reduce waste, and maintain consistency.
It is typically included in the introduction to give the reader an accurate, concrete understanding what the document will cover and what he/she can gain from reading it. To be effective, a statement of purpose should be: Specific and precise - not general, broad or obscure.
Why is documenting knowledge important? ›
Documentation is important in knowledge management because it makes information easily accessible to the required people. This will remove the need for guesswork by your organization, while the documentation acts as a central hub for all the vital project and team information.
What is the use case of document understanding? ›
Document Understanding can be employed for automating the extraction of data from various HR documents, including resumes, employee onboarding forms, and timesheets. This facilitates efficient HR document management.
What components are part of the document understanding process template? ›
The Document Understanding Process is preconfigured with a series of basic document types in a taxonomy, a classifier configured to distinguish between these classes, and extractors to showcase how to use the Data Extraction capabilities of the framework.
Can you use queues in the document understanding process? ›
Another piece that assists in enabling human-in-the-loop functionality is the structure of queues in the Document Understanding Process template.
What is the understanding process? ›
The Process of Understanding. We propose that understanding should be conceptualized as a process. Understanding is an ongoing cognitive activity of acquiring, integrating and expressing knowledge according to the task or situation at hand.
What do you understand by document process? ›
Process documentation is a detailed description of how to execute a process, and it outlines the exact steps needed to complete a task from start to finish. Creating a detailed document can align teamwork around process objectives and encourage organizational clarity.
What is document structure understanding? ›
Document understanding depends on a reader's own interpreta- tion, where a document may structured, semi-structured or unstruc- tured. Usually a human readable document has a physical layout and logical structure. A document contains sections. Sections may contain a title, section body or a nested structure.
