SIMULSCAN DOCUMENT CAPTURE

ROB GALVIN

SIMULSCAN DOCUMENT CAPTURE

End-to-end solution for data capture and

processing

- Extract and process critical data from paper-based documents in

real time

New usage cases on MSI terminals

- Productivity gain by multiple barcodes read with a single trigger pull

- Automated data entry with character recognition [OCR]

- Simplified workflow exceptions with checked mark

recognition[OMR] and data presence detection

Market differentiation with expanded core data

capture competencies

- Increased network usage savings due to completely local offline

processing

- Patented home-grown technology

• Supported on KitKat devices TC55, TC75

FEATURES

SIMULSCAN DOCUMENT CAPTURE

MULTICODE

• Up to 6 barcodes decoded in <1 sec

• Output sequencing by symbology, length or content

• Name – value pair returned to host application

• Intrinsically enables picking barcode(s) accurately

Manufacturing

Healthcare

Travel docs

Bank Checks

• Read multiple barcode symbols simultaneously

STRUCTURED DOCUMENTS

• OCR - 35 fonts in 5 languages [English, Spanish, French, German, Portuguese ]

• OMR – Checkboxes, radio buttons, bubbles

• Color picture support

• Signature presence verification

• Capture and process entire documents in a single session

COMPONENTS

SIMULSCAN DOCUMENT CAPTURE

TEMPLATE BUILDER

- Define “fields” containing critical

information

- Metadata for a field like symbologies

for barcodes, RegEx or language for

text, etc

- Fields can be grouped like multiple

fields of an address (name, street, city,

state, zip, etc.).

- Output from this tool is a “Template”

that can be mass deployed

- Templates are stored online and are

accessible programmatically from the

device

- Validation support to improve efficacy

• Cloud based utility to describe documents

TYPE OF DOCUMENT

CROP

IDENTIFIERS

• Best use 3 Identifiers

• Impacts identification

time and orientation

• ID item does not need to

be a data item

• Items with good

whitespace buffer make

good candidates

TYPE: BARCODE

• Best to identify barcodes by type

and length

• Won’t allow multiple

‘ANY_BARCODE’

TYPE: OCR

• Advanced settings used to check

format of the string to ensure

accuracy

• English / EFIGS language sets

• Auto correct misdecoded words

using spell checker

TYPE: PICTURE

• Common use: Form Identifiers

• Detection of Signature to alert

user

TYPE: OMR

• Identifies if items on form checked

• Square, Circle, Oval

TEMPLATE SETTINGS

• Default settings for all templates

• User can override

• Feedback

• Timeouts (ID / Process)

• Auto capture

- Sensitivity controls how long image

must be identified for

• Output entire form – raw

image captured passed to

application

TEMPLATE VALIDATION

• Make sure template is well

defined before deploying to

device

SAVING

• Save to release folder will

show in Showcase App

• Download and copy XML

file to device (accessible

folder)

DEVICE UI

- Real time document capture and processing

- UI complexities abstracted from host app

• Intuitive UI to guide end-user for accuracy

- End-user customizable settings

- Verify results and handle any exceptions

SHOWCASE APP

- Canned postal form showcases structured document support

- Manufacturing tab demonstrates multiple barcode capabilities

• Built in application with canned templates

SHOWCASE APP

- Custom demo tab enables you to customize and try out your own use-case

• Built in application to create custom demo

API SUPPORT

- Integrated with DataWedge with powerful Keyboard and Intent

plug-in support

- Built into Rho 5.0 and above

- Targeting EMDK support for Q1 ‘15

• Customer applications enabled for next level of processing

Future opportunities

Extensible framework for partner value-adds such as address

verification, translation etc

Expand use-cases to support unstructured targets like addresses,

trailer ids, shelf labels etc

API SUPPORT - DATAWEDGE

- Keystroke Output – Barcode Only, concatenated string

- Intent Output - Regions Bundle EXTRA

API SUPPORT - RHOMOBILE

• Templates must exist on device (non app container folder)

- Manual/MDM or use API method: fetchTemplates

API SUPPORT - RHOMOBILE

• Assign template file to template property

• Call captureDocument method

API SUPPORT - RHOMOBILE

REFERENCES

SIMULSCAN DOCUMENT CAPTURE

REFERENCES

• SimulScan Document Capture Launchpad site

- https://developer.motorolasolutions.com/community/technologies/dpx--beta-eap

- Contact: Ana.sanchez@zebra.com

• RhoMobile Documentation

- http://docs.rhomobile.com/en/edge/api/SimulScan

• Datawedge Intent Sample App

- http://tiny.cc/simulscanintent