This
guide is to help engineers learn the basics of the technology supported by the
Order Fulfillment team. I have provided headings for each section, with a focus
on interfaces from Pick/Put systems, Routing for inbound and outbound, and generally how pick/put to light works.
Pick and Put
User Login
Users
each have a UID tag that they scan with their guns at the login prompt. This is
how their login session is mapped to their pick station.
Barcode Anatomy
Below
is a sample 18 digit barcode (specifically from Walmart), as well as the
anatomy laid out with | delimiters:
Area Descriptions
Section: Discrete
area that a bay module controls, 7 XD modules max
Work Area: Maximum
number of sections a user can log in to
Pick Area: Maximum
number of section a carton can pass through
Pack Area: Pack
items from previously picked orders
Pick to Light
Pick Telegram Path (RF Scan)
Path the telegrams take from the scan use the RF scanner:
Scan -> Wireless
transfer to application server
-> query client
database server
-> Controller (EZ
Pick)
-> Signal
converter
-> Node boards
-> pick lights
(over CAT5 ethernet)
Pick Telegram Path (Tethered)
Telegram path using
a tethered multidrop connection:
Scan ->
Controller (EZ Pick)
-> Application
Server
-> query client
database server
-> Controller (EZ
Pick)
-> Signal
converter
-> Node boards
-CAT5> pick
lights
Q_down_load and Complete Processes
A few processes help
the pick system download and complete orders in the system as they are sent and
finished. These are:
Q_down_load: Process
that picks up files sent by customer that hold pick information. These files
are .dat files, but get renamed .tmp during the transfer so the q_down_load
process doesn't pick it up prematurely.
Complete process:
Process that generates an upload record for the archive after uploads are ftp'd
to to WMS. Up_binary (spelling) process actually reads the log and sends it.
Put to Light
Mirrored Zones
With
mirrored zones, work can be done the same way in any zone. Puts are done by
store, not put bins. Each zone will have the same layout as any other, but they
will be for different stores.
Downloads
There are 3 types of
downloaded files:
C: Carton Supply,
information about stock
D: Demand, usually
in following format
- Store, Division, Label Date,
Distribution Center #, Billing #
X (rbo): Exceptions,
remove cartons for any reason
- In use cartons cannot be
excepted
Telegram Path
Telegram path followed by the inbound:
Receiving Dock
-> Regional Unix
Server
-> Put system