The image below shows the relationship between the components in Recognition Server.
Overview of ABBYY FlexiCapture and Typical Use CasesABBYY FlexiCapture is primarily an enterprise level data extraction software application which also provides OCR functions. FlexiCapture provides a means to automatically extract data from documents based upon the establishment of rules including keywords and location of the information on a page. FlexiCapture is also available in special, ready to run solution packages such as FlexiCapture for Invoices and FlexiCapture for Mailrooms. Although the solution heavily relies upon the use of the same OCR technology found within Recognition Server, and it can export a text searchable version of a document, it's core function is the following: classification of documents (determining their type), matching these document classes to the corresponding data extraction rules, and then exporting the data somewhere such as a database, XML file, Microsoft Excel, or multiple locations at the same time. FlexiCapture provides for the extraction of typed text, barcodes, handwriting and check mark field values.
The image below shows the stations and their relationships in ABBYY FlexiCapture.
Similarities and Differences Between FlexiCapture and Recognition Server by Function or Architecture
|Software Function or Architecture||ABBYY FlexiCapture||ABBYY Recognition Server|
|Bulk, high-volume unattended OCR conversion of documents.||No. |
This is possible, but FlexiCapture is uniquely designed to extract documents.
This is a core function and high page counts are affordable. Additionally, processing stations can be added for no additional charge which scale the processing speed in proportion to the number of stations added.
|Extract key values from a wide variety of different documents automatically and then export the data to a content management system.||Yes. |
This is a core function. Documents are extracted based upon rules inside of what is called a "document definition." For unstructured documents additional specifications are provided within a tool called Flexilayout Studio.
|No, not automatically, with the qualifications noted below.|
Index values can be added by clicking on the index field and then by lassoing the value on the image displayed during the document indexing function, a process referred to by ABBYY as "click and key." In some cases scripts can be developed to extract certain common values from documents and then automatically applied to the document. These functions will be further expanded in the upcoming version 5 of the product.
|Web-based client for performing scanning, verification, indexing and administrative functions.||Yes. |
This is a core function of the Distributed version of the application. All client functions are available in web based versions except for the configuration of the document definitions and FlexiLayouts. The base system comes with one of each kind of client and more stations can be easily added. In addition to the scanning and verification web stations, a combined station is available that provides both scanning and verification functions into one easy to use application.
All stations in Recognition Server are "rich client," meaning they are installed on computers running Microsoft Windows through the add / remove programs function. As with FlexiCapture, the base system comes with one of each type of client, additional stations can be added.
|Microsoft Active Directory Integration for User Login||Yes. |
This is a core function for all of the client workstations for both the thick (rich) clients and the web based version.
|Yes, with qualification as noted below. |
Access is provided for users of each of the three rich client workstation types (scanning, verification, indexing) through the assignment of named users in the admin and monitoring station.
Permissions for these different tasks (such as administration, verification and indexing) can be assigned through Microsoft Active Directory user groups. The admin function is handled with a snap-in for the Microsoft Management Console (MMC).
|Processing of Digitally Born Documents (such as Microsoft Word documents).||Yes. |
This is a core function of the system and like Recognition Server the system can use either Microsoft Office or Libre Office to provide access to these functions.
|Yes, within certain limits. |
Recognition Server can process digitally born documents through its built-in integration with a rendering engine including either Microsoft Office or Libre Office.
|Availability of Web Services API.||Yes. |
This is included in the base version of the product.
This is available as an add-on component.
|Automatic Classification of Documents||Yes.|
This is a core function.
|No, except this can be done through the use of a barcode separator sheet to explicitly specify the document type.|
|Automatic Separation of Documents.||Yes.|
This is a core function.
|Yes, but not automatically in all cases.|
Documents can be separated automatically through the use of barcodes and blank pages. Barcodes can be used to specify the type of document.
|Automatic Indexing of a Document||Yes.|
This is a core function.
|No, not automatically, except in certain cases with scripting. |
A degree of automatic indexing is being released in an upcoming version, however this is for basic indexing functions.
|Ability to "Train" the System for the Addition of New Fields||Yes.|
This is a core function. Field types are specified in the document definition without a region (location on the document). Then several example documents are run and the field values selected. Additional variations of the forms can be added at this stage or later as they are encountered.
Indexing fields are preconfigured for all of the various document types. Fields values are not automatically populated but are instead added through the use of the indexing station where the user first select the field and then uses the "click and key" method to populate the value.
We will be glad to answer any questions you have regarding this article explaining the differences between ABBYY FlexiCapture and ABBYY Recognition Server.
Have you encountered issues on difficulty in OCRing documents because of renderable text in the document? We got that issue and we do not know how to resolve it. ABBY does not OCR the document and sometimes only OCR a bit of the document.
After talking with you I see an article from Adobe about the problem:
This would require further investigation by talking with ABBYY Support. I am surprise that we have not yet run into this yet and am interested to hear about what you find out.