Document Automation architecture
- Updated: 2025/07/01
Document Automation uses features from the Control Room, Automation Co-Pilot, and third-party providers to provide a secure, scalable, and end-to-end solution for automating document processing workflows.
Review the architecture to get a high-level overview of the different phases involved in the document processing data flow.
Note: For information about how documents are stored in Document
Automation, see Document Automation security FAQ.
The following image shows an overview of the different components used in Cloud deployments:
The following image shows an overview of the different components used in On-Premises deployments:
- Customer network
- The customer network is where the data extraction process is initiated.
- Input: This process involves uploading the documents that need to be processed for data extraction.
- Bot Runner device: All data extraction requests are sent and received via the Bot Runner device.
- Control Room (On-Premises only): Orchestrates the data extraction process by acknowledging requests from Bot Runner device.
- Upload bot: This process involves uploading the documents to the Control Room Cloud storage services.
- Extraction bot: This process involves extracting
information from documents by sending requests to OCR and third-party Cloud
services.
ABBY OCR: This process involves converting documents into machine-readable format and the documents are processed for OCR on the Bot Runner machine.
- Download bot: This process involves downloading the extracted information from the documents.
- Output: This process involves storing the extracted information.
- Automation Anywhere Cloud
- Control Room (Cloud only): Orchestrates the data extraction process by acknowledging requests from Bot Runner device.
- Third-party Cloud services
- Google Vision OCR: This process involves converting documents into machine-readable format and the documents are processed for OCR on Google Cloud.