3/11/2023 0 Comments Ocr abbyy finereaderIn a nutshell, it would have been way more expensive and difficult for us to roll our own than even the high cost of a FlexiCapture license. limited flexibility in implementing distributed services, costs that add up fast, you have to be trained in their own stackĬan you provide an example where you think that a custom solution would not work? I'm curious.įirst of all, why don't you shoot me an email at and we can talk further. ABBYY really wants to sell you their own cluster/cloud management services which is all proprietary limits on how many pages you can process per year or in total (complex licensing schemes) ridiculous extra costs for things like "cloud/VM license", exporting to PDF, etc. This has the same problems as the other offerings by ABBYY (I don't know about Nuance but I suspect it's the same): There is also FlexiCapture Engine that is meant for developers. In my (biased) opinion, it makes more sense for some businesses to go the custom route instead of investing in FlexiCapture. ![]() The products sold by ABBYY/Nuance are meant to be used by integrators (no programming needed other than the occasional VB.net script), not image processing specialists/developers. Do you need deskewing of documents? Click a button and you get deskewing. It abstracts the OCR bits so that the system designer can think about the problem itself, design a spec and think about the logic the logic. I think that is one of the main selling points of FlexiCapture. It's way easier for a non developer to think about what rulesets/logic to apply and not having to think about the image processing/OCR bits. This is of course not an easy task because you need someone who can design and implement an end to end system that possibly involves image processing, "zonal OCR", include an OCR engine and also perform reliable text extraction from images/PDFs (extracting text from PDFs is tricky). Some cases have a lot of templates and need the "automatic fuzzy matching" functionality and the extra bells and whistles.īut smaller players often deal with just a handful of relatively simple templates where FlexiCapture would just be overkill (not to mention a couple of other problems that I'm covering at the end of the post). I think it boils down to the needs of each individual application. Just to be sure that we're talking about the same thing, by "custom parser" I meant implementing your own barebones "zonal OCR" functionality with just the features that are needed for the specific problem. FlexiCapture will do 95%+ accuracy out of the box (on a character by character basis) with no human verification. I haven't used Nuance's stuff much but ABBYY's products are actually incredibly robust under the hood- stuff you wouldn't want to build yourself unless you absolutely had to. There's still a need for on-prem style solutions for people doing huge volumes (hundreds of thousands of pages a year), whereas most of the new market entrants are cloud only.ĥ. ![]() The market for complex data extraction (at least the kind of stuff I do) may not actually be big enough for smaller players to bother pursuing (most new players are going after tasks of intermediate difficulty, like invoice and receipt capture).Ĥ. ABBYY and Nuance have a lot of IP in the space on lock.ģ. ![]() There are alternatives for simple capture tasks (like DocParser), but not for complex ones.Ģ. ![]() ABBYY and Nuance are the only ones with products that can handle it. The commercial stuff is really for extraction of structured info from unstructured and semi-structured documents. Anyone who's just doing full-page OCR has no business using one of these commercial offerings. Lots of reasons they haven't been wiped off the map.ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |