Two Cents on Implementing Advanced Capture Solutions

I have implemented numerous Advanced Capture solutions over the years and have identified a number of sticking points that are easily overcome, but can also be a real pain. I would classify an Advanced Capture solution as any document capture implementation that is more than a standard heads-up indexing or very basic zonal OCR of fixed forms based on X and Y coordinates. That definition leaves a lot of room for what could be designated as an ‘advanced capture solution’, but I think it fits. Once you move out of the realm of basic capture, you start to encounter a lot of the same problems. There is one problem I seem to encounter every time we implement a solution.

Not enough sample pages when configuring the solution

I can’t tell you how many times I have been engaged to implement a project and only given one or two sample pages. It seems crazy to me that someone could think that there might be a positive result from this approach, but believe me, it still happens all the time. If you trudge along and configure the solution with your minimal sample set, you will enjoy a very long and drawn out beta testing and implementation. There is always variation when talking about documents, even fixed form documents. Whether it is different printers, different content creators, or just different versions of the same form, there is always variation. Variation has to be accounted for, or else the solution won’t work, that is why configuring a solution with only one or two sample pages will cause a long implementation. Every time you encounter a variation, you will inevitably have to go back and reconfigure the solution. Some of this can be mitigated with how you configure the solution, but having sufficient samples is still a must. Even if using a software package with ‘learning’ capability, it is best to get a lot of samples up front.

How many samples you ask? The answer is seems pretty simple, to configure an advanced capture solution you need as many samples as possible to cover every possible variation of a form. If you get that many samples and configure the solution to work with and account for all variations, you end up with a much more bullet proof configuration come beta testing and implementation time. A good rule of thumb would be to have a minimum of 10 samples for every document type, but ask for 50 and reserve the right to ask for more. 50 might seem like a lot but in the scheme of things it is nothing. A company wouldn’t implement an advanced capture solution unless they could justify the steep price of it, the only way to justify that price it implement these solutions for processes that process thousands (if not tens of thousands) of documents a day. 50 sample documents for a solution that is expected to handle thousands of documents a day is not much and you’ll hit the ground running when beta testing starts rather than grinding to a screeching halt.

raj kumar - May 27, 2013

Attractive section of content. I just stumbled upon your site and to say that I get actually enjoyed account
your weblog posts. Any way I will be subscribing for your feeds
or even I fulfillment you get right of entry to consistently
fast.

apart from these i have some doubts regarding filenet p8 and kofax integretion, can u please let me know what procedure standard rules need to follow integretion???

John Linehan - May 28, 2013

Raj,
I have configured Kofax to Release/Export to many different flavors of FileNet over the years but I don’t recall if P8 was one. I always used the Release Script / Export Connectors that either Kofax or FileNet supported. You can find a number of them here: http://www.kofax.com/software/capture/export-connectors.php

rajkumar - May 28, 2013

John,

ok, i don’t stress more about filenet versions and flavours,

but atleast i need standards steps and procedures for integretion between kofax and filenet,

i mean how to connect filenet through export connectors and release scripts? implementation??

that would be really helpful for me, can i have ur mail id??

thanks in advance

rajkumar - May 28, 2013

John,

ok, i don’t stress more about filenet versions and flavours,

but atleast i need standards steps and procedures for integretion between kofax and filenet,

i mean how to connect filenet through export connectors and release scripts? implementation??

that would be really helpful for me, can i have ur mail id??

thanks in advance

John Linehan - May 28, 2013

Every Release Script/Export Connector is a little different depending on what back-end system you are sending the documents and metadata to. However they all follow the basic principal of making a connection to the server then mapping the Kofax fields to the fields in the repository. I’d suggest reviewing the P8 Export Conector documentation. Here is the admin guide for P8/Content Manager 5.0 Export Connector:
http://www.kofax.com/software/capture/downloads/P8Rel50Admin_v80.pdf

It looks like the Export Connector for P8 is something that Kofax sells.

rajkumar - May 29, 2013

john,

first of all starting of our discussion am very thankful to you for showing keen interest in helping me in sorting out the issues like this,

i will agree for your words,
Every Release Script/Export Connector is a little different depending on what back-end system you are sending the documents and metadata to. However they all follow the basic principal of making a connection to the server then mapping the Kofax fields to the fields in the repository

but apart from estabhlising connection between between two appilications,
can i know how data and metadata will be processed from kofax to backend(filenet)??
any specific methodilgies or technigques for process flow

we can discuss further, if you have mail id, please share it, so it will be handful

Regards,
raj kumar

rajkumar - June 6, 2013

hi john,

can i get any information or update on this??

thanks in advance

rajkumar - June 11, 2013

hi John,

can you please reply?

John Linehan - June 11, 2013

Hi There,
I responded to the gmail address that was associated with your comment on the 29th. You asked about releasing/exporting from Kofax to FileNet, correct? Those Release/Export connectors are sold and supported by Kofax. If you want, I can look into the price. Basically the way it works is as every document is released from Kofax Capture the Release/Export settings are referenced so it knows where to send the documents and what the mapping for the metadata is. What you do is install the Release Script/Export Connector on a server with the Kofax Capture client installed, then from within the Kofax Capture Administration module you launch the configuration utility to perform the mappings of metadata and documents. The last step is to make sure the Kofax Release/Export service is running as a Windows service on that server.

rajkumar - June 11, 2013

Hi John,

thats ok from kofax part, as to recieve data from kofax and should we need to install any kofax instances in filenet server again??

in order to communicate each other?

John Linehan - June 11, 2013

Hi Raj,
You can reach me at johnl@imagesourceinc.com.

Comments are closed