Posts

Showing posts from 2016

AutoStore: Reasons to Consider Using the Document Writer

A really great tool tucked inside the AutoStore toolbox is the Document Writer process component. Essentially, it provides the ability to create a text-based file within an AutoStore task. The text produced can include both static elements, and well as RRT values. Here are a few practical reasons why the Document Writer can be so useful. Testing RRT Values Sometimes, we need to confirm the value of a particular RRT as it makes its way through the process. Include one or a group of RRTs in the Document Writer for the resulting text file to reveal the answer. For example, take an unfamiliar process component where the exact RRT values need to be analyzed. Just add those RRTs into the document writer to reveal the output, and it's a great way to get through the testing phase. Testing OCR Text OK, this is similar to Testing RRT Values, but different. Yes, we are testing an RRT value, but not from a logical data point in the process. What's really being tested is the rec

AutoStore: Planning Solid Barcode Workflows

Image
Processing barcodes using AutoStore is something I get asked about frequently, and for what would appear to be a pretty simple image of bars and blocks, there's quite a bit worth talking about from a technical perspective. Notwithstanding, actual workflow requirements are key. When building any document barcode process, and considering even the simplest of jobs, there are three main categories of what is actually being processed which deserve to be examined: Batch Document Page Generally speaking, a batch consists of many documents, and a document is made of of one or more pages. Obviously, we can break these items down into even smaller pieces, but these are the basics. With respect to the actual barcode value in the job, there are the actions which can then be taken: Split Keep Extract Knowing how barcodes can be handled, the following 3 questions will help take us to creating the most solid AutoStore process process. What's The Goal? Barcodes can a

AutoStore: Why Multiple Tasks Are Needed

Our neighborhood market, the big-mega outlets, airport security screening, the DMV, and the interstate freeway system in most major metropolitan areas during rush hour traffic all have one thing in common: there are never enough open lanes. To the endeavor of order and process, when the volume of activity is not accounted for, regulating the forward flow to a single line creates what we call in the industry as a bottleneck. Stalled movement feels like being tied up in a straight jacket. One way to think about an AutoStore task how a printer prints. After the print command is launched, bits and bytes received by the printer trigger a series of events. Paper is pulled from the tray, the information is applied to the paper, and the final product is placed on the exit tray. Before any print job is completed, the printer is in a busy state, and can't be used. Any other jobs that need to be printed are waiting in a queue, and begin after the printer has finished printing the job wh