Continuous motion pot washing

Continuous motion pot washing systems are, in the most basic form, three compartment sinks with an agitating wash compartment. Most commonly used in the food service industry, the term continuous motion pot washing describes washing systems that do not have a set wash cycle (aka: cycle-less) or require an attendant. Unlike old three compartment sink systems where an employee was tied to a machine for hours scrubbing dirty ware, continuous motion pot washing systems allow employees to drop any number or type of pots and pans in the system and walk away. Later any employee can come by and move ware items to other compartments of the system. These systems are called “continuous motion” because they never stop working. When the machine is turned on, they are always running and always washing. The motion created is a very turbulent agitation created by a flow of continuous fluid movement powered by a motorized system.

History

The term “Continuous Motion Pot Washing” was coined in 1987 by the Cantrell family who designed the “Power Soak” potwashing system in Kansas City, Missouri. Designed with powerful jet and intake manifolds on the back of the main compartment tank, the Power Soak was the first continuous motion pot washing system sold. Since 1987 many competitors have entered the category as manufacturers of similar continuous motion pot washing systems. Among these competitors include the AquaScrubber by Insinger the TurboWash by Hobart and the X-Stream Wash by Steelkor.

How it works

A continuous motion system uses the natural properties of highly turbulent water, heat, and low foam detergent to clean kitchenware products. Powered by one or more motorized pumps, continuous motion pot washing systems re-circulate water through a series of jets and intakes in order to create a whirlpool like motion that agitates the water within the wash tank in order to continuously move the ware products. These jets and intakes can be located in a variety of locations depending on the manufacturer and model.

Sources


gollark: PotatOS uses the Polychoron process manager I made, but it's not hooked into multishell or anything.
gollark: `window` has very useful capabilities, but barely exposes any.
gollark: `multishell` manages its coroutines internally, and you can't really touch them in a useful way.
gollark: It uses `parallel` as its top level event loop thing to run rednet.run and shell at the same time, but you can't add your own stuff to that.
gollark: I think a major problem with CraftOS is that it's not designed very extensibly, to be honest.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.