Category Archives for "Uncategorized"

Effortlessly Configure SSL Offload in ILINX for Processing & Security Gains

Recently, I had the opportunity to configure a system in network load balanced configuration for ILINX Content Store and ILINX Capture systems. There was a separate virtual IP address (VIP) for each service (ILINX Content Store and ILINX Capture) and two servers assigned to each VIP. Additional modules, ILINX Capture Format Converter and ILINX Release, resided on the capture servers.

The exact nature of the configuration is not critical for this discussion. What we want to focus on is how easy it is to configure SSL offload in this sort of scenario. SSL offload is a configuration—typically involving a load balancer—where HTTPS (SSL/TLS) communication is terminated at the network device and the network device forwards the communication as HTTP. There are both performance and security benefits for this configuration.

So how do ILINX Content Store, ILINX Capture and associated modules handle this? We will focus on ILINX Content Store first, where there are two main components to the application: the server-side component in the WCF folder and the client-side component in the WebClient folder. The configuration is easy; leave the server-side components in regular HTTP mode and configure the client-side as HTTPS—that’s it. For normal HTTPS (SSL/TLS) configuration, you would follow the instructions for both server and client to communicate in HTTPS. For SSL offload, configure just the client for HTTPS.

ILINX Capture is configured exactly the same as its counterpart. There is one caveat though: there are client bindings in the server-side WCF/web.config for additional modules (ConvertBatchBinding, ReleaseBatchBinding and RecognitionBinding). Those need to have the <security mode=”Transport” /> tag added so that the workflow engine knows to communicate in HTTPS from the IXM’s that utilize those services if those IXM modules are used.

The additional modules—ILINX Format Converter and ILINX Release—do not need to be modified in any way. They do not include client components and remain in OOB HTTP configuration.

As always, if you have questions, get a hold of our support team and they can point you in the right direction.

Mike Peterson
Systems Engineer

How WSDOT Leverages ILINX Workflow for Auto-Matching Vouchers & Receipts

Richard Norrell, Washington State Department of Transportation

Washington State Department of Transportation (WSDOT) has a lot of processes where transaction documents are created in a system, printed, processed then scanned into the Enterprise Content Management (ECM) system for search and Retention Management. In addition to these documents, there are summary reports that are produced, and in the old days these reports were manually verified to confirm that each transaction document referenced was actually processed and captured in the ECM. Sometimes it would take several days or even weeks for the various geographically dispersed offices of the agency to get the paper documents processed and scanned, so the manual matching process had to be repeated on a daily basis until all documents were present. With the implementation of the new ILINX Capture system this process is now completely automated, only requiring human intervention if documents fail to show up after a designated grace period. Here are some screen shots and explanations of how it all works for the newest implementation, Payment Vouchers.

The ILINX Capture Workflow

The main section of the workflow, shown above, handles the scanning, indexing and processing of the Payment Vouchers and routing of the Register reports into the Register Subflow. 

The Register Subflow is where the matching process takes place. This process uses two custom Server Extension ILINX Extension Modules (IXM). The first Server Extension (Parse RAM 0051) takes the Summary Report and parses it into individual rows in a Line Item table. Each line is a reference to one or more documents that require matching. The second Server Extension (RAM Auto Match) reads through the entries in the Line Item table and conducts a search for documents that match the Line Item reference. When documents are found they are updated indicating the Line Item that they match and then the Line Item itself is updated to indicate it has been matched to the documents. After the Auto-Matching is attempted the workflow checks to see if all the Line Items were matched or if the prescribed number of cycles has been attempted. Based on these checks the Register batch will either go into the Pending Match Cycle queue, the Warrant Manual Match queue, or Complete the subflow.

Here is what the actual summary report looks like: As you can see it could be pretty tedious to sit and manually match each of these lines to the documents they represent in the system.

Should a manual review be necessary, a Workflow Form is used. On this form, workflow fields are shown that keep track of how many documents are referenced in each summary report. At a quick glance, the user can see how many documents have been matched, how many are missing and the number of times the workflow has attempted to do the matching process.

The table on the left side of the form shows the documents that have been previously matched, indicated by the padlock icon, and the remaining documents that are available for matching. The table on the right shows all of the documents that are referenced in the report. If manual matching is desired, the user simply selects a document in the left table, not already matched, and presses the Match button on the corresponding line on the right table.

WSDOT has now automated the process of matching several business areas including Payment Vouchers, Journal Vouchers and Cash Receipts. Once documents are matched, the properties on the documents can be used creating a cross reference to the summary report. Also, using the Full Text capabilities of ILINX Content Store, users are now able to research both the summary report information and their corresponding documents without having to return to the source system. In this case, the source system is a mainframe application so the users are really loving that little side benefit.

If you are interested in more details of how these processes work, please contact ImageSource.

Richard Norrell is a Senior ECM Systems Engineer at Washington State Department of Transportation in Olympia, WA. He was instrumental in helping them move from Oracle IPM and Kofax to ILINX technologies for migration, capture, workflow, repository, retention management and COLD processing.

How Intelligent Capture Utilizes Machine Learning for Template-free Training

There has recently been a lot of chatter in our industry about machine, and I want to share a few thoughts about how ImageSource’s ILINX Advanced Capture 8.5 platform tackles this topic. Our approach is to deploy a neural network-based document processing model that does not rely on templates. Our machine-learning platform supports custom-developed content classification projects with much faster turnaround than traditional rules-based models. The result is significantly faster time-to-production with more reliable and accurate results for our customer partners. ILINX machine learning offers:

  • Dynamic data location and extraction of information on complex documents
  • Image comparison to support check fraud applications
  • Feature extraction and classification to support medical imaging diagnostics

Our solutions leverage machine learning to create pre-built form classification algorithms in the lab, which provides a more-flexible and efficient way to develop new document processes.

For the sake of this article, I’d like to focus on the goals of almost every AP automation project:

  • Reduce paper handling and workload
  • Simplify processes down to one system for all invoices and other types of documents whether paper or digital
  • Gain visibility into where each invoice is in the process

For the initial document discovery, a technique called “clustering” can be used to automate the logical grouping of like documents. Clustering, in this example, refers to different categories of like invoices, checks, receipts and remittances. Documents can be organized automatically. Invoices from one vendor can be grouped together, such as receipts to travel documents. The result is a set of documents grouped by likeness that can then be further evaluated.

Next, each cluster, if part of a required document, can be given a document type (or class). The training set can then be imported into the machine learning ILINX solution designed to automatically identify key characteristics of each document type (often called “feature extraction”). This trains the neural network for each document type. When performance is not ideal for a specific class, the customer can add those misclassified or unclassified documents to the class sample set to “re-train” the neural network.

Data extraction is simplified by taking sample invoices that have been processed, along with the data required for each document. Together, these automatically train the software to locate the matching data and derive positional algorithms for each data field. The software uses the processed data for each page and locates the corresponding data on every document. The solution will do this for each sample and then automatically create algorithms based upon exact location, changes in placement across each example and relative position to other data, among other elements. The knowledge worker simply examines the results.

The technology used to configure the system also makes real-time adjustments. Complicated projects that typically would take weeks, if not months, are significantly reduced. Machine learning technology streamlines the manual processes used in production and helps reduce overall labor costs.
This effort can be applied to automate both paper-based and electronic document-based processes in a single workflow.

by Terry Sutherland, CEO, ImageSource

If you would like to learn more about how ILINX machine learning can automate your business please contact us at or

What was your “ah-ha” moment in communicating ECM?

Working in Content Management for over 12 years often times I have found it somewhat difficult to explain what we do and/or sell. Have you?
I have found that who your audience is often dictates how you explain it. To an IT group I have described ECM in terms of storage and retrieval of images in to database/repository with searching capability, ability to apply rules for authentication and accessibility, removing silos of information, ability to do workflow and BPM, and other things like Meta-Data, networks, through-put and HA/DR. Sometimes their eyes gloss over and other times they “understand.”
To some business folks when I’ m talking ECM I most usually reference things like accessibility of their documentation, being able to search on key fields and automatically route work/documents/content without the use of email or paper files (at its simplest form) and its all stored in a database otherwise known as a “repository.” Or, when describing workflow, using the old analogy of a restaurant. When you go in to the establishment a hostess seats you, then you get a menu, a waiter comes up and then you order, that order goes back to the kitchen and you get your meal prepared, then after you have dessert, you get a bill, pay and get a receipt then the bus boy comes and cleans everything up – that’s a workflow.
But what do you say to your mother or father, sister or brother and even children (aka the layman)? I’ve tried things like, “I sell software that lifts information off paper or documents and puts that data in a data base that allows people to find it. Then the people can see the documents on their computer necessary to do their job.” But I still get a ‘blank stare.’
Then one day, maybe three or four months ago, my dad was asking me for his usual P.C. help and he said, “my printer/scanner isn’t reading the words as well as it used to.” Of course, that got my attention! Could my dad know what O.C.R. is? After 12 years of me talking about IBM, FileNet, EMC/Documentum, Microsoft , Captiva, Kofax and AnyDoc and him saying “I still don’t get what you do.” NO WAY! How could my dad possibly know about O.C.R?
So I asked him, “Dad, you know what OCR is?” Guess what, he replied YES! “Its that software that I use when I want to take words off my documents that are PDF or Tiffs”. BAM! He knew! Finally after 12 years he “figured it out” partially what I did for a living. Putting this in context, my dad is an automotive guy, first sales and then executive, who had never a need to do any “computing” most of his professional career.
We have a lot of acronyms in our ECM vocabulary: OCR, ICR, OMR, BPM, OSR, ODAR, HIPI, TIFF, etc etc etc. (I can go on for a lifetime of our acronyms). But what do you say so that IT people get what ECM is? What do YOU say to a business user, who never ever ever thought of this stuff day to day? What do you tell your mom, dad, brother, sister, what you do every day? What have you said that brings blank stares? But, most importantly, what have you said to a customer and then you saw the “light bulb” go off? It appears O.C.R. is making it in to the mainstream vocabulary, if my dad is any example, because he knows his, “HP MFP does OCR.”

So I asked him, “Dad, you know what OCR is?”  Guess what, he replied YES!  “Its that software that I use when I want to take words off my documents that are PDF or Tiffs”.   BAM!  He knew!  Finally after 12 years he “figured it out” partially what I did for a living.  Putting this in context, my dad is an automotive guy, first sales and then executive, who had never a need to do any “computing” most of his professional career.

We have a lot of acronyms in our ECM vocabulary:  OCR, ICR, OMR, BPM, OSR, ODAR, HIPI, TIFF, etc etc etc.  (I can go on for a lifetime of our acronyms).   But what do you say so that IT people get what ECM is?  What do YOU say to a business user, who never ever ever thought of this stuff day to day?  What do you tell your mom, dad, brother, sister, what you do every day?   What have you said that brings blank stares?  But, most importantly, what have you said to a customer and then you saw the “light bulb” go off?  It appears O.C.R. is making it in to the mainstream vocabulary, if my dad is any example, because he knows his, “HP MFP does OCR.”

Document Scanning Best Practices

Document Scanning Best Practices Content Management Systems are one of the most useful resources companies have available to keep their managers, staff, and customers informed. Managing those files effectively is an ongoing challenge, but a well-planned, best practices implementation makes it significantly easier. Most Content Management Systems start with Scanning as the starting point in the lifecycle of any document. The decision of whether to go with a centralized or distributed scanning model must be carefully evaluated to see which may be a better fit for the organization. Many times a hybrid model of both remote and centralized is required and becoming more popular. When it is done designed and implemented correctly scanning ensures that the data stored in the document management repository is valid, readable, secure, accessible, and useful throughout the enterprise. Some important things to remember when deploying document a document scanning system: • Establish clear goals and objectives before you start or deploy a Document Scanning System. • Establish clear and concise business rules around your company’s requirements. • Consult a well established Systems Integrator with the knowledge and expertise to help you with defining “Best Practices for Document Scanning” and always check references. • Understand the nature of your documents, the quality of many documents may be poor, this in turn will require you to use Image Enhancement Technologies that will automatically clean up the document and improve its readability. These types of technologies are a must especially when utilizing OCR or any advanced form of capture. • Scanning and especially the Indexing of documents can be somewhat laborious, so anything to help automate these tasks such as Bar Coding, OCR, database lookups and electronic forms will make life a lot easier. • Use the KISS Principle in dealing with data taxonomy and avoid capturing too many fields, but make sure it’s enough to do valuable searches. Here at ImageSource we try to have 10 document types maximum and 8 data fields which allows for effective searches, retrieval and reporting. Lastly, don’t lose sight of your short and long term goals, do your homework and study your documents and see how they fit into your business lifecycle and corporate governance. Talk with people throughout you organization and get their input to better understand your documents are used. Finally, if you’re unsure get help, this is not an area where you can afford a mistake. Remember, it all starts with getting information into the system. Bob Garrido Senior Account Executive ImageSource

1 2 3