Jimmy'sTubeCast Blog

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...

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...

To preface what could be regarded as a very small thing, I am reminded of a common turn of phrase concerning the amount of perspiration that should be afforded to the "stuff" belonging to a particular size-category, and pretty sure there was a book written about that topic. Not to come across as disagreeable, but rather to invite a little balance based on my own general observations over time, an increase in cost with things such as time, money, even relationships, can be avoided when the "small stuff" is given the regard that it deserves. One of these tiny details has to do with string variables that reference folder paths within a script. There are times when it is important that a defined directory for a particular folder should and must always end with a backslash. As an example: folderPath = "C:\Example"   Of course, it really is not very difficult to manually enter that backslash into the path. folderPath = "C:\Example\" ...