Tulare County Superior Court Automates Procurement Documents with ABBYY Vantage

Project Details

The Court needed a reliable way to process incoming procurement and finance documents within its new M-Files environment. The documents ranged from standardized forms to highly variable invoices, agreements, and contracts, each requiring different information to be captured.

Simply storing the documents was not enough. The solution needed to identify document types, extract meaningful information, associate that information with the appropriate M-Files metadata, and provide a way for users to intervene when the information could not be reliably determined automatically.

There was also a need to clearly distinguish historical migration from future-state document processing. During design discussions, the teams aligned that historical documents would be migrated directly into M-Files, while ABBYY would support go-forward processing.

The Court was moving toward M-Files as the foundation for document management, making consistent classification and metadata important for how users would ultimately find and work with information.

For example, existing documents had historically been organized in PDF packets by fiscal year. In the future M-Files model, individual documents could instead be connected through metadata. The teams therefore spent time defining how document classes, fiscal-year information, agreements, purchase orders, invoices, and other records should be represented.

The approach was also designed to avoid assuming that every field could or should be automated. For complex agreements where dates or values depended on context not clearly available within the document, the Court could use ABBYY's manual-review process to complete or validate the information.

The Superior Court of California, County of Tulare engaged TEAM IM for an ABBYY Vantage implementation connected to its M-Files environment. TEAM IM's scope centered on deploying and configuring ABBYY Vantage and connecting its results to the Court's existing M-Files structures. TEAM IM was not responsible for the underlying M-Files system configuration. Our role focused on the ABBYY configuration, connector, metadata mapping, validation, and customer enablement.

The engagement objectives included configuring ABBYY Vantage, configuring document skills using existing ABBYY Production Skills, connecting processed documents and metadata to M-Files, establishing manual validation for exception scenarios, and transferring knowledge so designated Court administrators could understand and maintain the solution. 

TEAM IM worked closely with the Court's finance, procurement, and IT stakeholders as well as the M-Files team throughout design and implementation.

TEAM IM used a collaborative, iterative implementation approach which included the following phases and methodology:

1. Requirements and demonstrations

We first demonstrated the complete M-Files and ABBYY Vantage workflow so Court stakeholders could see how documents would move through processing, classification, metadata extraction, exception handling, and manual review. Sample documents and real business scenarios were then used to refine the requirements.

2. Solution design and metadata alignment

TEAM IM created a solution design capturing document types, required metadata, processing assumptions, and integration behavior. The design was reviewed alongside the Court and M-Files teams to make sure ABBYY's extracted information aligned with the metadata structure already being established in M-Files.

3. ABBYY skill and connector configuration

The implementation associated document classes with ABBYY skills and mapped extracted information back to M-Files properties and objects. The configured workflow included processing, exception handling, manual review, and completion states.

A customized classification and document-processing approach was ultimately used for the Court's required document types.

4. Human validation where appropriate

Automation was deliberately combined with human review. Missing or uncertain information could trigger review, while Court staff retained the ability to correct or manually provide values. This was particularly useful for agreements where dates, amounts, or other information depended on surrounding business context.

5. Customer testing and refinement

TEAM IM handed the configured development environment to the Court for practical testing. Users submitted representative documents, reviewed the metadata returned by Vantage, and provided feedback.

Testing uncovered issues such as metadata mappings, classification behavior, manual-review workflow behavior, and field population. TEAM IM investigated these items and made configuration adjustments before final deployment.

6. Deployment and transition

By the final project status, production deployment was complete, end-user and administrator documentation had been delivered, and go-live had occurred. The engagement concluded on time and within budget with early lifecycle support identified as the next activity.

The Court moved into production with an ABBYY Vantage solution integrated with M-Files that could route defined document types through document processing, extract configured metadata, support manual validation where needed, and return results to M-Files.

The implementation also provided the Court with end-user and administrative documentation to support its transition into ongoing ownership of the solution. 

Importantly, the solution was validated through hands-on customer testing rather than stopping at configuration. The court not only had a reliable solution in place, but all use cases were tested and passed and the Court received end user/admin documentation along with early lifecycle support as part of the engagement.