ABBYY mobile real-time recognition

Dimitry Chubanov and Derek Gerber presented at the ABBYY Technology Summit on ABBYY’s mobile real-time recognition (RTR), which allows for recognition directly on a mobile device, rather than just capturing content to pass on to a back-end recognition server. Mobile data capture comes in two basic flavors: first, the mobile user is just entering data, such as an account number or password; and second, the mobile user is entering both data and image, such as personal data and a copy of their ID.

ABBYY RTR isn’t based on taking a photo and then running recognition on that image; instead, it uses several frames of image from the camera preview stream and runs recognition algorithms on the stream without having to capture an image. This provides a better user experience since the recognition results are immediate and they don’t have to type the data manually, and better privacy since no image is captured to the phone or passed to any other device or server. They demonstrated this using a sample app on an iPhone; it’s interesting to see the results changing slightly as the phone moves around, since the recognition is happening using the previous several frames of video data, and it gradually gains recognition confidence after a few seconds of video. We saw recognition of unstructured paragraphs of text, drivers licenses, passports and bank cards. The SDK ships with a lot of predefined document types, or you can create your own by training for specific fields using location and regular expressions. They are also offering the ability to capture meter data, such as electricity meters, although some of this requirement is being by smart meters and other IoT advances.

They also have a mobile imaging SDK that can capture an image when it’s needed — for proof of ID, for example — with scene stabilization, document edge detection, deskewing and various types of image enhancement to capture the optimal photo for downstream storage and processing.

I can imagine, for example, a mobile airline app that needs to capture your passport information using mobile RTR to grab the data directly rather than having you type it in. I’ve also seen something very similar used to capture the unique number from an iTunes gift card directly into the App Store on an iPhone. Just like QR code reading is now built right into the search bar on the mobile versions of Google Chrome, and Google Translate on mobile allows real-time capture of text using the same camera preview mode (plus simultaneous translation), being able to capture text from a printed source instead of requiring a mobile user to type it in is likely to become ubiquitous in mobile apps.

ABBYY Robotic Information Capture applies machine learning to capture

Back in the SDK track at ABBYY Technology Summit, I attended a session on “robotic information capture” with FlexiCapture Engine 12, with lead product manager Andrew Zyuzin and director of product marketing Semyon Sergunin showing some of the automation classification and data extraction capabilities powered by machine learning. Traditional enterprise capture uses manually-created rules for classification and data extraction to set up for automated capture: a time-consuming training process up front in order to maximize recognition rates. At the other end of the spectrum, robotic process automation uses machine learning to analyze user actions, and create classification and extraction algorithms that can be run by robots to replace human operators. In the Goldilocks middle, they position robotic information capture as a blending of these two ideas: the system is pre-trained and processes standard documents out of the box, then uses machine learning to enhance the recognition for non-standard documents by analyzing how human operators handle the exceptions. Although I’m not completely aligned with their use of the term robotic process automation since RPA is not completely synonymous with machine learning and also isn’t limited to capture applications, I understand why they’re positioning their ML-assisted capture as robotic information capture as a middle ground between traditional capture and ML-assisted RPA.

We saw a demo of this with invoice capture: a PDF invoice was processed through their standard invoice recognition, detecting vendor name and invoice number, but the wrong number was picked up for the total amount due to the location of the field. This was corrected by a user in the verification client, and the information of where to find the total was analyzed for retraining and fed back to the recognition model. The user doesn’t know that they’re actually training the system — there’s no explicit training mode — but it just happens automatically in the background for continuous improvement of the recognition rates, gradually reducing the amount of manual verification. After the training was fed back, we saw another invoice from the same vendor processed, with the invoice total field properly detected.

Although I think that most technology is pretty interesting, this is the first thing I’ve seen today that made me say “cool!”

Zyuzin also walked us through their advanced classification, which can classify documents without any development based on large data sets of typical document types such as invoices, cheques, and drivers licences; automatic classification is important as the front end to recognition so that the correct recognition techniques and templates can be applied. Their advanced classification uses both image and content classification, that is, determines what type of document it is based on how it looks as well as the available text content. He showed us a demo of processing a package of mortgage documents, where there is a large number of possible documents that can be submitted by a consumer as supporting documentation; most of the documents were properly classified, but a few were unrecognized and required a quick setup of a new document type to train the classifier. This was more of a manual training process, but once the new document class was created, it could be applied to other unrecognized documents in the package.

ABBYY Recognition Server 5.0 update

I’ve switched over to the FlexiCapture technical track at the ABBYY Technology Summit for a preview of the new version of Recognition Server to be released in the first half of 2018. Paula Saunders, director of sales engineering, walked us through a presentation of the features and a demo.

New features include:

  • Smart PDF quality detection and processing, including detecting if there is already an OCR layer on the document and using that instead of re-recognizing
  • Support of PDF/E standard for engineering drawings
  • Import of email messages in MSG format, including both the message text and attachments
  • Advanced document editing at indexing and verification stations, such as rotation and redaction
  • Support of user languages and pattern-matching to fine-tune non-standard text
  • Extracting index fields by using a template of fixed regions
  • Native 64-bit support

Recognition Server is for more of the production capture work, where you set up a capture workflow and define several properties that define the input, process, document separation, quality control, indexing and output stages of that flow. She walked us through the screens for creating a new workflow and setting the properties at each stage, then showed us what it would look like at an indexing station if you wanted to edit the original image: deskewing, despeckling, cropping and more. The indexing station module also allows you to create field templates, for fine-tuning the recognition and assigning for mapping form areas to index fields directly on live document data. The verification station module can be used for additional training using pattern matching, such as recognizing unusual fonts.

ABBYY SDK update and FineReader Engine deep dive

I attended two back-to-back sessions from the SDK track in the first round of breakouts at the 2017 ABBYY Technology Summit. All of the products covered in these sessions are developer tools for building OCR capabilities into other solutions, not end-user tools.

Semyon Sergunin, director of product marketing for ABBYY‘s SDK products, gave us a high-level update and a bit of the roadmap for all of the SDK products. For reference, FineReader Engine is an OCR toolkit, while FlexiCapture Engine is based on the same technology but is an SDK for document separation, classification and data extraction.

FineReader Engine 12:

  • New OCR support for Farsi and Burmese languages, and improved OCR for Japanese
  • Improved layout retention, so that the recognized/exported document in plain text or structured document formats (MS Office) looks more like the original
  • Improved automation of document classification and data extraction using machine learning
  • Additional export formats (ALTO, PDF/A 2-b and 3-b), and improvements to some existing ones (XML, TXT)

He also discussed some of their licensing changes, including cloud licenses for Azure public cloud and virtual cloud instances.

FlexiCapture Engine 12:

  • New classification and PDF export features supported via the API
  • Update to latest version of OCR technologies
  • Processing of natively-digital documents (email, text, MS-Word), not just images
  • Cloud licensing
  • Changes to classification logic depending on whether the text or image version of the content is available
  • Processing of PDFs with text layers
  • Linux support using a Wine wrapper

Receipts Capture SDK:

  • Available on Windows, Linux (via Wine) and cloud
  • Supports 120 major US vendor receipt styles
  • Added field-level confidence levels, not just character or word confidence
  • Added manual verification service

Mobile real-time recognition SDK:

  • Built-in support for bank cards, passports, several different states’ drivers licenses, and regular expressions
  • Combined SDK for video or still photo input on mobile

Cloud OCR SDK:

  • Same functionality as FineReader Engine, plus a few extras such as receipt recognition
  • Subscription and package pricing

There’s also a new FlexiCapture Cloud product in beta now, providing the additional functionality for document classification and data extraction.

The details here are primarily of interested to technical developers who are working with ABBYY products (or planning to), but the amount of new information shows a good rate of innovation. This was a fast high-level update, although more detail than we saw in the analyst briefing yesterday; there will be more information coming in later breakout sessions.

This was followed by a deep dive session on the use of FineReader Engine, with Larysa Lototska, technical marketing manager, and Tony Connell, pre-sales engineer. They covered the following topics:

  • Licensing, both runtime and developer
  • Improving recognition accuracy by using predefined profiles for specific types of documents or data extraction, e.g., engineering drawings or business cards; and by applying additional settings via code
  • Improving recognition speed by changing the engine loading method; using multiple CPU cores or concurrent recognition processes; using parallelism for multiple pages within documents; and batch scanning for batches of documents with the same number of pages (including single-page documents)

They gave live demos showing how to use some of the different profiles and settings in sample code in Visual Studio, applying methods for classifying and recognizing particularly difficult or degraded images.

They also discussed turning on the FineReader Engine log file to track down performance problems, since it tracks and timestamps every engine call plus any errors that are thrown, and walked through various sources of developer help on their site and bundled with the SDK.

There are a lot of interesting sessions at the conference: even with only three tracks, I’m having trouble deciding what to attend in some time slots.

The collision of capture, content and analytics

Martyn Christian of UNDRSTND Group, who I worked with back in FileNet in 2000-1, gave a keynote at ABBYY Technology Summit 2017 on the evolution and ultimate collision of capture, content and analytics. He started by highlighting some key acquisitions in the industry, including the entry of private capital, as well as a move to artificial intelligence in the capture space, as harbingers of the changes in the capture market. Since Gartner declared enterprise content management dead — long live content services platforms! — and introduced new players in the magic quadrant alongside the traditional ECM players, while shifting IBM from the leaders quadrant back to the challengers quadrant.

Intelligent capture is gaining visibility and importance, particularly as a driver for digital transformation. Interestingly, capture was traditionally about converting analog (paper) to digital (data); now, however, many forms of information are natively digital, and capture is not only about performing OCR on scanned paper documents but about extracting and analyzing actionable data from both analog and digital content. High-volume in-house production scanning operations are being augmented — or replaced — with customers doing their own capture, such as we now see with depositing a check using a mobile banking application. Information about customer actions and sentiment is being automatically gleaned from their social media actions. Advanced machine learning is being used to classify content, reducing the need for manual intervention further downstream, and enabling straight-through processing or the use of autonomous agents.

As a marketing guy, he had a lot of advice on how this can be positioned and sold into customers; UNDRSTND apparently ran a workshop yesterday for some of the channel partner companies on bringing this message to their customers who are seeking to move beyond simple capture solutions to digital transformation.

ABBYY corporate vision and strategy

We have a pretty full agenda for the next two days of the 2017 ABBYY Technology Summit, and we started off with an address from Ulf Persson, ABBYY’s relatively new worldwide CEO (although he is a long-time board member). As a company with its roots in Russia that has spread from country to country in a bit of a disjointed way in the past, Persson is pushing the idea of #OneABBYY: a global company rather than a collection of regional companies. A leader in OCR since 1989, ABBYY is the best-kept secret in OCR: end customers don’t know who they are, and even other vendors in the same space haven’t heard the name, unlike that of their competitors. They are actively trying to change how they grow: becoming more globally balanced in terms of development, marketing and organizational structure; becoming more agile and customer-centric; and continuing to be profitable and innovative. Their revenues are well-diversified, with 33% in Europe, 28% in North America, global accounts (bundling with hardware vendors) 19%, then smaller segments in Russia, Africa and Australia.

Their strategy includes:

  • Increasing market share in enterprise capture by pushing intelligent capture solutions, primarily as a cloud service.
  • Becoming the partner of choice for ISVs that need to build capture capabilities into their solutions. Unlike some other capture vendors, they are not looking to push into adjacent spaces, such as BPM, but plan to stay as an indepedent vendor in the intelligent capture and automation market that can partner with a wide variety of hardware, software and solution providers.
  • Becoming a leader in text analytics solutions, driven by the data that they capture from documents. He mentioned contracts in particular, where very complex text analytics are required to automate understanding of these types of documents.

They are making use of machine learning and artificial intelligence in their capture technology, and offering real-time recognition as a service or as embedded technology.

As a self-funded profitable company, they don’t need to go to the markets for funding, and state outright that they are not for sale.

Disclaimer: ABBYY has been my customer in the past — I gave the keynote here last year as well as another presentation in Toronto, and wrote a white paper — but I am not being compensated for my time here this week or for writing these posts. ABBYY did pay for my flights and hotel, which is the usual deal that I have with vendors to attend their conferences and blog my thoughts about what I see.

ABBYY analyst briefing

I’m in San Deigo for a quick visit to the ABBYY Technology Summit. I’m not speaking this year (I keynoted last year), but wanted to take a look at some of the advances that they’re making in intelligent capture. We had an analyst briefing today in advance of the general conference tomorrow, and some of this is a preview for those more detailed sessions.

ABBYY’s legacy is in the OCR SDK business, which allows their partners to build solutions that include intelligent data capture from scanned documents. They’re moving beyond that with mobile capture products and cloud capture solutions. They have a lot of flexibility with mobile and cloud, allowing for both hybrid solutions that use mobile for capture with recognition on a more powerful cloud platform, and for mobile-only data extraction that operates completely on the mobile platform. Since there are components for this in addition to packaged solutions, a developer can create a mobile application that makes decisions about what type of recognition to do, and where to do it. This uses a real-time recognition SDK that uses video feed to do self-correction based on several frames of video rather than just a single snap, or simpler recognition based on still photos.

Their cloud OCR service supports a community of more than 65,000 developers with 69,000 connected applications: a great use of distributed microservices from applications that need OCR but don’t want to own that technology. Assuming that privacy issues can be satisfied (since you’re sending them potentially private documents), many organizations could benefit from OCR but may not be able to afford to own a high-performance solution in-house.

They also have some packaged solutions for receipt capture and identity documents (e.g., passports). They also have a Linux version of their OCR services (their primary products are Windows and Azure-based), which is popular in certain markets.

They covered some of the market trends in capture:

  • Less of a discrete technology and more of an embedded capability in business applications
  • No longer production-line capture, but more intelligent capture of heterogeneous documents; there’s a great deal more diversity in document type and point of origin
  • Organizations are using this to automate where possible, particularly for front-end work such as capture

This requires core capabilities of processing large volumes of documents where the content may be diverse and frequently changing, and the seamless interaction of content coming from a variety of input streams with a larger business solution. Back in the earlier days of “imaging and workflow”, we had dedicated scanning and recognition workstations for high-volume assembly line processing of documents that were all the same, or manually classified. Now, we need to have this happening on any computer, or on a mobile device, at any point in a process.

ABBYY’s products are aiming to address these changing market conditions with autonomous classification and train-by-example data extraction, including some clever processing of related documents: if you have two documents from someone with the same piece of information (e.g, a SSN), and the confidence level is low on the recognition of that information on one of the documents but high on the other, the stronger confidence level can be used to boost the confidence of the lower level. They also have improved integration capabilities including being able to embed the capture capabilities as an iframe in an html page. and an increased number of input channel types. They’re working with some of the low-code vendors since it’s now pretty straightforward to map the outputs from an ABBYY service to the inputs of a data-centric low-code application.

Their core customer base is still banking — at least in North America — but they are starting to see growth in insurance and other markets. Their number one use case is invoice processing, and they have a packaged application to address that sector. The mid market is underserved in terms of automating invoice processing; it’s a tough problem since inbound invoices can be in any sort of format, and there’s quite a bit of intelligence to ensure that all of the data is extracted correctly. Note that a lot of larger enterprises either have EDI-type processes for invoices, or force smaller vendors to login to a dedicated invoicing portal to submit an invoice in the enterprise’s format rather than the vendor’s usual format, and are more likely to have automated capture processes for the remainder. ABBYY’s goal is to complement existing accounts payable solutions by being built in as the front-end capture component, not to displace these systems.

This briefing drives home that ABBYY is the best-kept secret in intelligent capture because they work primarily through partners who bundle their capture technology into vertical solutions, but don’t have as much visibility to the end customers. Most of the enterprise customers that I talk to have never heard of ABBYY, although they may have it running in their organizations embedded within another application. Even other vendors in this space, such as BPM and low-code vendors, don’t know the name. This is a bit different from ABBYY’s competitors Kofax and Captiva, who both have had a lot of end-customer solutions that move beyond capture in addition to capture-related SDKs, or IBM’s Datacap, which does some of that but also comes in on the coattails of a suite of IBM products such as ECM and BPM. Whether ABBYY can change this market visibility themselves — or if they even want to — will be an interesting positioning going forward.

More on all of this tomorrow and Friday.

ABBYY Technology Summit 2017

Welcome back after a nice long summer break!

Last year, I gave the keynote at ABBYY’s Technology Summit, and I’m headed back to San Diego this year to just do the analyst stuff: attend briefings and hang out at the conference sessions. This will give me a chance to do more writing than when I’m presenting; last year, I only had time to blog about one session at ABBYY’s conference.

You can find out more about the summit and register to attend here, and more about ABBYY and their intelligent capture products here. Looks like some interesting sessions, including those on improving capture and recognition with machine learning.

Readers may have noticed that I’ve severely curtailed my conference travel in the past year or two. Large conferences just aren’t good value for my time, especially for vendors that have a wide variety of products outside my area of interest:  when I attend a conference, I’m giving up billable time to be there so need to gain useful information or make valuable contacts to make it worth my while. I will almost always attend a client’s conference even if I’m not speaking, or a smaller conference that looks interesting, or one in an interesting location. As described on my Legal page, a vendor must cover my travel expenses to have me attend their conference but doesn’t provide any other remuneration unless I’m also giving a presentation at the conference.

AIIM breakfast meeting on Feb 16: digital transformation and intelligent capture

AIIM TorontoI’m speaking at the AIIM breakfast meeting in Toronto on February 16, with an updated version of the presentation that I gave at the ABBYY conference in November on digital transformation and intelligent capture. ABBYY is generously sponsoring this meeting and will give a brief presentation/demo on their intelligent capture and text analytics products after my presentation.

Here’s the description of my talk:

This presentation will look at how digital transformation is increasing the value of capture and text analytics, recognizing that these technologies provide an “on ramp” to the intelligent, automated processes that underlie digital transformation. Using examples from financial services and retail companies, we will examine the key attributes of this digital transformation. We will review step-by-step, the role of intelligent capture in digital transformation, showing how a customer-facing financial services process is changed by intelligent capture technologies. We will finish with a discussion of the challenges of introducing intelligent capture technologies as part of a digital transformation initiative.

You can register to attend here, and there’s a discount if you’re an AIIM member.

You can read about last month’s meeting here, which featured Jason Bero of Microsoft talking about SharePoint and related Microsoft technologies that are used for classification, preservation, protection and disposal of information assets.

Intelligent Capture enables Digital Transformation at #ABBYYSummit16

IMG_0672I’ve been in beautiful San Diego for the past couple of days at the ABBYY Technology Summit, where I gave the keynote yesterday on why intelligent capture (including recognition technologies and content analytics) is a necessary onramp to digital transformation. I started my career in imaging and workflow over 25 years ago – what we would now call capture, ECM and BPM – and I’ve seen over and over again that if you don’t extract good data up front as quickly as possible, then you just can’t do a lot to transform those downstream processes. You can see my slides at Slideshare as usual:

I’m finishing up a white paper for ABBYY on the same topic, and will post a link here when it’s up on their site. Here’s the introduction (although it will probably change slightly before final publication):

Data capture from paper or electronic documents is an essential step for most business processes, and often is the initiator for customer-facing business processes. Capture has traditionally required human effort – data entry workers transcribing information from paper documents, or copying and pasting text from electronic documents – to expose information for downstream processing. These manual capture methods are inefficient and error-prone, but more importantly, they hinder customer engagement and self-service by placing an unnecessary barrier between customers and the processes that serve them.

Intelligent capture – including recognition, document classification, data extraction and text analytics – replaces manual capture with fully-automated conversion of documents to business-ready data. This streamlines the essential link between customers and your business, enhancing the customer journey and enabling digital transformation of customer-facing processes.

I chilled out a bit after my presentation, then decided to attend one presentation that looked really interesting. It was, but was an advance preview of a product that’s embargoed until it comes out next year, so you’ll have to wait for my comments on it. Winking smile

A well-run event with a lot of interesting content, attended primarily by partners who build solutions based on ABBYY products, as well as many of ABBYY’s team from Russia (where a significant amount of their development is done) and other locations. It’s nice to attend a 200-person conference for a change, where – just like Cheers – everybody knows your name.