Don’t just archive your content, use it when you need it

Whether you are dealing with student records, registration forms, accounting files, financial aid or any other departmental processes, the most efficient way to use the information and get it to your main system is to scan the documents at the time they are created or received.

If you wait until the end of the process, many people across your organization will have photocopied, faxed, emailed, sorted, filed and re-filed, creating massive amounts of unnecessary work, expense and wasted resources.

Continue reading

Why Imprint Documents?

This is a question we ask our customers when choosing scanning hardware for their Enterprise Content Management solutions.  It is easily overlooked when reviewing the specifications of a scanner, as it is a separate hardware purchase and generally is a business process requirement not a scanner specification requirement.

When there is a need to “imprint” or “stamp” a scanned document, it is required to have the date of the scan on each and every page that is processed. This requirement usually is used for tracking purposes or compliance to show that the document was scanned.

Do you Pre or Post-Scan Imprint?
Pre-Scan imprinting is the most common option that allows the organization to have the stamp on both the physical paper copy and the scan. The pre-scan imprint will print on the document PRIOR to the image reaching the scanners imaging lamps.  So the imprint stamp will also be a part of the scan image.

Post-Scan imprinting is generally utilized when an organization needs the data or tracking mechanism on the physical paper after the scan. This is mostly used to indicate if a page of paper has been processed or not.  The stamp is NOT on the scanned image.

Can I automatically imprint on a flatbed scanned documents?
Keep in mind when purchasing a scanner with a flatbed – either integrated with the scanner or as a detachable USB connected flatbed – there is no automatic imprinting option for the documents scanned using a flatbed.  Flatbed scanned documents will need to be manually stamped to meet requirements – either pre-scan or post-scan.

Another option for imprinting is “Software Annotation”…
If only a data or tracking on the scanned image is needed, software annotation could be considered.  With software annotation you have greater flexibility on where the imprint data can be placed on the image. Keep in mind software annotation needs to be part of your batch scanning process and is a separate software purchase to your hardware scanner.

So keep this information in mind when considering what is the “best fit” for imprinting based on your business process AND scanner requirements.
Megan Lane
Inside Sales
ImageSource,Inc.  

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

5 mistaken beliefs about information management in Higher Ed

Your university may or may not have a strategy for managing content, the unstructured information streaming in and out of all areas of your campus on a daily basis. It’s likely you at least have a partial strategy where one or more of your departments is capturing and storing some type of unstructured information for later retrieval.

In a world where the use of digital channels is enabling organizations to synthesize large amounts of information in seconds, universities are making it a top priority to gain control of that rogue 80%, which is the approximate amount of unstructured information slipping through the cracks. This information is not easily accessible because it is scattered and isolated in departmental or personal file systems. This is the information employees need to do their jobs.

Information management 20% structured 80% unstructured information

University structured v. unstructured content

Content management services and software technologies have adapted to changing business environments so quickly over the past ten years, it is difficult to keep up with where the capabilities lie today. The following are five mistaken beliefs about content management and the facts that dispel those beliefs.

5. Content management is mostly beneficial for scanning and archiving documents.

Content management covers the lifecycle of information from creation and publication to archival and eventual disposal. One of the largest benefits of content management is enabling workflow automation. A perfect example is when someone in your organization wants to buy something. The individual begins to create documentation such as pricing research, correspondence, a requisition, purchase order, invoice and a contract to name a few. With workflow automation, these supporting documents are captured, routed and accessed interdepartmentally for approval, payment and auditing. Transactions are processed in hours or days instead of weeks.

Continue reading

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.

1 2 3 53