FastFetch Order Fulfillment Distributed Processing Architecture

The FastFetch system uses a distributed architecture model with multiple PDAs, each running a separate copy of the FastFetch application and the SQL database system. The Fastetch Optimizer PC communicates with the PDAs through a host SQL database server to create a distributed database application.

Once a batch of pick tickets have been downloaded to a PDA or Tablet PC, picking can commence with no required communication between the PDA or Tablet PC and the host SQL database server. If communication connectivity is available, results of picking will be communicated in real-time from the PDA or Tablet PC local SQL database to the host SQL database server and subsequently to the FastFetch Optimizer PC.  If however communications connectivity is unavailable or is interrupted (e.g. due to a deadspot in the warehouse) picking can continue using data stored locally in the local SQL database.  When communications is again restored, the local SQL database will automatically be synchronized with the host SQL database server.  Click here to learn more about FastFetch's fail safe design.

The Optimizer PC periodically receives and sends information to the Host ERP or WMS by one of several available interfacing methods.  The simplest method of interfacing data exchange is through a flat file containing CSV or XML formatted information.  Other methods include database stored procedures, data queues and IP messaging.  The minimal information required for picking is a set of records with pick ticket #, picking location and quantity (although if available, other information will be used).   The minimal set of information returned after picking is the same as that initially received with an additional field of quantity picked.  Additional information such as picker ID, time picked, serial number, lot number, etc is available for client processing after picking and for the FastFetch Performance Management Reporting System.