- Overview
- Getting started
- Building models
- Consuming models
- ML packages
- 1040 - ML package
- 1040 Schedule C - ML package
- 1040 Schedule D - ML package
- 1040 Schedule E - ML package
- 1040x - ML package
- 3949a - ML package
- 4506T - ML package
- 709 - ML package
- 941x - ML package
- 9465 - ML package
- ACORD125 - ML package
- ACORD126 - ML package
- ACORD131 - ML package
- ACORD140 - ML package
- ACORD25 - ML package
- Bank Statements - ML package
- Bills Of Lading - ML package
- Certificate of Incorporation - ML package
- Certificate of Origin - ML package
- Checks - ML package
- Children Product Certificate - ML package
- CMS 1500 - ML package
- EU Declaration of Conformity - ML package
- Financial Statements - ML package
- FM1003 - ML package
- I9 - ML package
- ID Cards - ML package
- Invoices - ML package
- Invoices Australia - ML package
- Invoices China - ML package
- Invoices Hebrew - ML package
- Invoices India - ML package
- Invoices Japan - ML package
- Invoices Shipping - ML package
- Packing Lists - ML package
- Payslips - ML package
- Passports - ML package
- Purchase Orders - ML package
- Receipts - ML Package
- Remittance Advices - ML package
- UB04 - ML package
- Utility Bills - ML package
- Vehicle Titles - ML package
- W2 - ML package
- W9 - ML package
- Public endpoints
- Supported languages
- Insights dashboards
- AI units consumption overview - Preview dashboard
- [Preview] Document Understanding and AI Center consumption dashboard
- Data and security
- Licensing
- How to
- Troubleshooting

Document Understanding Modern Projects User Guide
PREVIEWAI units consumption overview - Preview
dashboard
Based on the activity performed in Document UnderstandingTM and AI Center, the dashboard offers a detailed view of the AI units consumption.
- Dashboard data is limited to information from the same region as that of the organization.
- Data is refreshed every 24 hours.
- The dashboard includes AI units consumption data for Document Understanding and AI Center.
- The default tenant's name may be
displayed as Unknown in the following scenarios:
- If the tenant was created while the organization was on the Community plan, but it was then moved to the Enterprise plan.
- If data pertains to a different region than that of the organization.
- If consumption data pertains to missing transactions, such as those with no job ID.
To access the AI units consumption overview dashboard, Insights must be enabled on your tenant.
- UiPath Studio and Robot: 2023.6
- UiPath.DocumentUnderstanding.Activities package: 2.9.1
- UiPath.DocumentUnderstanding.ML.Activities package: 1.28.2
- UiPath.IntelligentOCR.Activities package: 6.19.1
- UiPath.MLServices.Activities: 2.0.2
Note that upgrading the ML packages version also implies retraining for retrainable models.
This dashboard displays an overview of the number AI units consumed by each tenant.
For more information on how to track the consumption at organization level, check the Monitoring license allocation page from the Automation Cloud™ Admin Guide.
This dashboard outlines the usage pattern of AI units specific to an individual tenant.
- Dashboard data is limited to information from the same region as that of the organization.
- Data is refreshed every 24 hours.
- The default tenant's name may be displayed as Unknown in the following
scenarios:
- If the tenant was created while the organization was on the Community plan, but it was then moved to the Enterprise plan.
- If data pertains to a different region than that of the organization.
- If consumption data pertains to missing transactions, such as those with no job ID.
- If the value for Orchestrator
folder is displayed as Unknown, it means that there is no related data.
This could result from using an outdated Robot or activity package version, or
if API Keys were used to access public endpoints, such as
du.uipath.com/invoices
. - The dashboard displays all data from a tenant.
- The dashboard includes AI units
consumption data for Document Understanding and AI Center.
For Document Understanding, the data covers both cross-platform and IntelligentOCR activities, applicable for both classic and modern projects. Data is reported for pre-trained specialized and generative models, as well as custom models.
- The dashboard displays consumption data from one of the following:
- AI units allocated at tenant level.
- AI units allocated at the organization level. This only applies if the tenant has no allocated AI units, but there is an associated tenant for the consumption event. For example, the number of AI units consumed by a tenant displayed on the dashboard will match the number displayed on the organization-level dashboard.
You can choose a specific time period to review AI units usage. The default period is set at 90 days.
Tile | Description |
---|---|
Consumption by product | Total number of consumed AI units distributed by product:
|
Consumption by Orchestrator folder | Total number of consumed AI units, distributed by the
Orchestrator folder the automation is run in.
Note: If the value is displayed as
Unknown, it means that there is no related data. This
could result from using an outdated Robot or activity package
version, or if API Keys were used to access public endpoints,
such as
du.uipath.com/invoices .
The value is displayed as Unknown also in the case of suspended jobs. In this case, the entry is populated after the job resumes and the automation execution finishes. If the value is displayed as N/A, this indicates that it's not applicable because the operation was carried out outside of an Orchestrator folder. |
Consumption by Orchestrator folder and product | Total number of consumed AI units, distributed by the Orchestrator folder the automation is run in, and the product consuming these AI units. |
Consumption by automation | Total number of consumed AI units, distributed by the automation
name:
Note: If the value is displayed as
Unknown, this means that there is no data for it. One
potential cause could be an older Robot or activity package
version.
If the value is displayed as N/A, this indicates that it's not applicable because the operation was carried out outside of an automation, Orchestrator folder. |