Skip to main content
The automatically processed documents can be verified manually, if needed. For this reason, ABBYY FlexiCapture provides rich and thin verification clients. Verification is a slow and expensive process. ABBYY FlexiCapture provides a functionality of automatic validation rules that can validate documents automatically, meaning that manual verification can be skipped. Another way to reduce the amount of verification work is to clarify with the customer precisely which document fields have to be extracted with 100% quality – sometimes this is not all fields of the document and this also allows verification to focus only on documents with problems in these fields. To calculate the number of verification operators, you need to understand the number of documents to be processed, how many of them require verification, the period of time to process the document according to the Service Level Agreement, and the average time needed to verify one document. Verifiers also generate a workload on the System. A Verification Station interacts with the Application Server in a similar way to a Processing Station: it requests tasks and downloads images and document data from the Application Server, and sends modified data back.
  • The processing speed of Verification Stations is much slower because manual verification usually takes a lot more time than automatic processing on a Processing Station.
  • Verification operators do not always need to see document images in their original quality. The FlexiCapture settings enable the compression to be changed (which is 60% by default) for images downloaded by operators from the Application Server.
For practical purposes, we can assume that a verification operator working at the top of his/her capacity generates up to 1/5 of the load created by one processing core of a Processing Station. You can use this assumption to interpret the results of your tests (conducted without verification operators, using only unattended processing): if the System with, say, 100 processing cores, appears to be stable, you can safely replace N of the processing cores with N*5 simultaneously working verification operators. Example. A customer needs to process 100,000 documents in 8 working hours. Based on our earlier assumption that only 30% of documents require manual verification and verification of each document takes up to 2 minutes, we conclude that up to 125 verifiers are required. Each document has about 3 pages on average. You can create a test batch from typical documents and test the System before going live in unattended processing mode. Let’s say the System is stable and you do not see any bottlenecks using 100 processing cores, while 60 processing cores is already enough to process the desired 300,000 pages in 8 hours. The upper bound estimate is 25 processing cores for 125 verifiers, so the System will easily handle 125 verifiers working on 60 processing cores.