Major Topics Already Covered
•Major roles of Warehouses in contemporary supply chains
•Warehouse processes and the organization of the material
flow
•Warehouse equipment
•Overview of the warehouse design and control problem(s)
•Warehouse Activity Profiling
Next Issues
–Storage configuration and storage policies
–the forward/reserve problem
–order-picking: batching, zoning, and routing
–Pallet-building
–Warehouse layout
–Configuring and controlling automated storage and
retrieval equipment
–Cross-docking
Warehouse Storage Configuration
and Storage Policies
Bibliography
•Bartholdi & Hackman: Chapter 6
•Francis, McGinnis, White: Chapter 5
•Askin and Standridge: Sections 10.3 and 10.4
Storage Policies
•Main Issue:Decide how to allocate the various storage
locations of a uniformstorage medium to a number of
SKU’s.
I/O
Types of Storage Policies
•Dedicated storage:Every SKU i gets a number of storage
locations, N_i, exclusively allocated to it. The number of
storage locations allocated to it, N_i, reflects its maximum
storage needs and it must be determined through inventory
activity profiling.
•Randomized storage:Each unit from any SKU can by
stored in any available location
•Class-based storage:SKU’s are grouped into classes. Each
class is assigned a dedicated storage area, but SKU’s
within a class are stored according to randomized storage
logic.
Location Assignment under
dedicated storage policy
•Major Criterion driving the decision-making process:
Enhance the throughput of your storage and retrieval
operations by reducing the travel time <=> reducing the
travel distance
•How?By allocating the most “active”units to the most
“convenient”locations...
“Convenient” Locations
•Locations with the smallest distanced_jto the I/O point!
•In case that the material transfer is performed through a
forklift truck (or a similar type of material handling
equipment), a proper distance metric is the, so-called,
rectilinearor Manhattan metric(or L1 norm):
d_j = |x(j)-x(I/O)| + |y(j)-y(I/O)|
•For an AS/RS type of storage mode, where the S/R unit
can move simultaneously in both axes, with uniform speed,
the most appropriate distance metric is the, so-called
Tchebychev metric(or Lnorm):
d_j = max (|x(j)-x(I/O)|,|y(j)-y(I/O)|)
“Active” SKU’s
•SKU’s that cause a lot of traffic!
•In steady state, the appropriate “activity” measure for a
given SKU i:
Average visits per storage location =
(number of units handled per unit of time) /
(number of allocated storage locations) =
TH_i / N_i
Problem Representation
SKU
Location
N_1
N_i
N_S
1
1
1
c_ij = (TH_i/N_i)*d_j
1
i
S
1
j
L
Problem Formulation
•Decision variables:x_ij = 1 if location j is allocated to
SKU I; 0 otherwise.
•Formulation:
min S_i S_j [(TH_i/N_i) * d_j] * x_ij
s.t.
i, S_j x_ij = N_i
j, S_i x_ij = 1
i, j, x_ij {0,1} =>x_ij 0
Remarks
•The previous problem representation corresponds to a
balancedtransportation problem: Implicitly it has been
assumed that:L = S_iN_i
•For the problem to be feasible, in general, it must hold that:
L S_iN_i
•If L -S_iN_i > 0, the previous balanced formulation is
obtained by introducing a fictitious SKU 0, with
N_0 = L -S_iN_i and TH_0 = 0
A fast solution algorithm
•Rank all the available storage locations in increasing
distance from the I/O point, d_j.
•Rank all SKU’s in decreasing “turns”, TH_i/N_i.
•Move down the two lists, assigning to the next most highly
ranked SKU i, the next N_i locations.
Example
I/O
I/O
011
2
2
2 2
2
3
3
3
3
4
3
3
34
4
4
4
5
4
4
4
45
5
5
5
5
5
5
5
5
5
6
6
6
6
6
6
6
6
7
7
7 7
7
7
8
8 8
8
9 9
A: 20/10=2
B: 15/5 = 3
C: 10/2 = 5
D: 20/5 = 4
CC
D
D
D
D
B
D
B
B
B
B
A
A
A
A
A
A
A
AA
A
Locating the I/O point
•In many cases, this location is already predetermined by
the building characteristics, its location/orientation with
respect to the neighboring area/roads/railway tracks, etc.
•Also, in the case of an AS/RS, this location is specified by
the AS/RS technical/operational characteristics.
•In case that the I/O point can be placed at will, the ultimate
choice should seek to enhance its “proximity”to the
storage locations.
Example 2 (cont.)
•Option A: U-shaped or cross-docking configuration
–amplifies the convenience/inconvenience of close/distant locations
–appropriate for product movement with strong ABC skew
–provides flexibility for interchanging between shipping and receiving
docking capacity
–allows for “dual command” operation of forklifts, reducing, thus, the
deadhead traveling
–minimizes truck apron and roadway
•Option C: Flow-through configuration
–attenuates the convenience difference among storage locations
–conservative design: more reasonably convenient storage locations
but fewer very convenient
–more appropriate for extremely high volume
–preferable when the building is long and narrow
–limits the opportunity for efficiencies for “dual command” operations
Storage Sizing
•Dedicated storage:
–How many storage locations, N_i, should be dedicated to each
SKU i?
•Randomized Storage:
–How many storage locations, N, should be employed for the
storage of the entire SKU set?
•Class-based storage:
–How should SKU’s be organized into classes?
–How many storage locations, N_k, should be dedicated to each
SKU class k?
Possible Approaches to Storage Sizing
under Dedicated Storage
•Issue resolved/predetermined through operational (e.g.,
replenishment) policies, contractual agreements, etc.
•“Service-level” type of analysis:
–Determine the number of storage locations, N_i to be assigned to
each SKU i in a way that tends to control the probability that there
will be a lack of storage space in any operational period (e.g., day).
•Cost-based Analysis
–Select N_i’s in a way that minimizes the total operational cost over
a given horizon, taking into consideration the cost of owning and
operating the storage space and equipment, and also any additional
costs resulting from space shortage and/or the need to contract
additional storage space.
Sizing dedicated storage based on
“service level” requirements
•F_i(Q_i) = Prob{stor. loc. requested by SKU i in a single period Q_i}
i.e., the cumulative distribution functionof the storage locations requested
by SKU i during any single operational period (day)
•Assuming independence of daily storage requirements across SKU’s, for
an assignment of N_i locations to each SKU i,
Prob{no storage shortages in a single day} = _i F_i(N_i)
and
Prob{1 or more storage shortages} = 1 -_i F_i(N_i)
Sizing dedicated storage based on
“service level” requirements (cont.)
•Formulation I: Fixed service level, P
min S_i N_i
s.t.
_i F_i(N_i) P
N_i 0 i
•Formulation II: Fixed storage space, S
max _i F_i(N_i)
s.t.
S_i N_I S
N_i 0 i
Sizing randomized storage based on
“service level” requirements
•F(Q) = Prob{stor. loc. requested by all SKU’s in a single period Q}
i.e., the cumulative distribution functionof the storage locations requested
by all SKU’s during any single operational period (day)
•For a storage size of N locations:
Prob{No storage shortage in a single period} = F(N)
•Problem Formulations:
–Formulation I: Fixed service level, P
min N
s.t.
F(N) P
N 0
–Formulation II: Fixed storage space, S
max F(N)
s.t.
0 N S
Class-Based Storage Sizing and
Location Assignment
•Divide SKU’s into classes, using ABC (Pareto) analysis, based
on their number of turns TH_i/N_i.
•Determine the required number of storage locations for each
class C_k
–ad-hoc adjustment of the total storage requirement of the class SKU’s
N_k = p * S_{iC_k }N_i
–Class-based “service-level” type of analysis, e.g.,
•Assign to each class the requested storage locations,
prioritizing them according to their number of turns,
TH_k (=S_{iC_k }TH_i)/N_k
min S_k N_k
s.t.
_k F_k(N_k) P
N_k 0 k
A simple cost-based model
for (dedicated) storage sizing
•Model-defining logic:Assuming that you know your
storage needs d_ti, for each SKU i, over a planning horizon
T, determine the optimal storage locations N_i for each
SKU i, by establishing a trade-off between the
–fixed and variable costs for developing this set of locations, and
operating them over the planning horizon T, and
–the costs resulting from any experienced storage shortage.
A simple cost-based model
for (dedicated) storage sizing (cont.)
•Model Parameters:
–T = length of planning horizon in time periods
–d_ti = storage space required for SKU i during period t
–C_0 = discounted present worth cost per unit storage capacity
owned during the planning horizon T
–C_1t = discounted present worth cost per unit stored in owned
space during period t
–C_2t = discounted present worth cost per unit stored in leased
space or per unit of space shortage during period t
•Model Decision Variables:
–N_i = “owned” storage capacity for SKU i
•Model Objective:
–min TC (N_1,N_2,…,N_n) =
S_i [C_0 N_i + S_t{C_1t [min(d_ti, N_i)]+ C_2t [max(d_ti -N_i, 0)]}]
A fast solution algorithm for the case of
time-invariant costs
•For each SKU i:
–Sequence the storage demands appearing in the d_ti, t=1,…T,
sequence in decreasing order.
–Determine the frequency of the various values in the ordered
sequence obtained in Step 1.
–Sum the demand frequencies over the sequence.
–When the obtained partial sum is first equal to or greater than
C’ = C_0/ (C_2-C_1)
stop; the optimum capacity for SKU i, N_i, equals the
corresponding demand level.
A probabilistic version
•Additional data
–p(d_ti) = probability mass function for the storage requirement of SKU i
during period t
•New objective function
–min E[TC (N_1,N_2,…,N_n)] =
S_i [C_0 N_i + S_t{C_1 E[min(d_ti, N_i)]+ C_2 E[max(d_ti -N_i,
0)]}] =
S_i [C_0 N_i +
S_t{C_1[S_{d_ti N_i} d_ti p(d_ti) + S_{d_ti > N_i} N_i p(d_ti) ]+
C_2 [S_{d_ti > N_i} (d_ti -N_i) p(d_ti) ]}]
A probabilistic version (cont.)
•Model Properties:
–Separable
–Piece-wise linear
–convex
•Optimality Condition:
N_i = Q_ij optimal <=>
S_t F
c
_ti(Q_ij) C_0 / (C_2 -C_1) S_t F
c
_ti(Q_i,j+1) <=>
S_t [1-F_ti (Q_ij) +p(Q_ij)] C_0 / (C_2 -C_1)
S_t [1-F_ti (Q_i,j+1)+p(Q_i,j+1)]
where F_ti( ) is the cdf for the storage requirements of SKU i in period t.
Storage Configuration and Policies
for “Unit Load” warehouses:
Topics covered
•Storage Policies:Assigning storage locations of a uniform
storage medium to the various SKU’s stored in that
medium
–Dedicated
–Randomized
–Class-based
Criterion:Maximize productivity by reducing the traveling effort /
cost
•The placement of the I/O point(s)
Criterion:Maximize productivity by reducing the traveling effort /
cost
Storage Configuration and Policies
for “Unit Load” warehouses:
Topics covered (cont.)
•Storage sizing for various SKU’s: Determine the number
of storage locations to be assigned to each SKU / group of
SKU’s.
Criterion:
–provide a certain (or a maximal) “service level”
–minimize the total (space+equipment+labor+shortage) cost over a
planning horizon
•Next major theme:Storage Configuration for better space
exploitation
–floor versus rack-based storage for pallet-handling warehouses
–determining the lane depth (mainly for randomizedstorage)
(based on Bartholdi & Hackman, Section 6.3)
Determining the Employment (and
Configuration) of Rack-based storage
•Basic Logic:
–For each SKU,
•compute how many pallet locations would be created by moving it
into rack of a given configuration;
•compute the value of the created pallet locations;
•move the sku into rack if the value it creates is sufficient to justify the
rack.
•Remark:In general, space utilization will be only one of
the factors affecting the final decision on whether to move
an SKU into rack or not. Other important factors can be
–the protection that the rack might provide for the pallets of the
considered SKU;
–the ability to support certain operational schemes, e.g., FIFO
retrieval;
–etc.
Examples on evaluating the efficiencies
from moving to rack-based storage
•Case I:Utilizing 3-high pallet rack for an SKU of N=4
(pallets), which is not stackable at all.
–Current footprint: 4 pallet positions
–Introducing a 3-high rack in the same area creates 3x4=12 position,
8 of which are available to store other SKU’s. What are the gains
of exploiting these new locations vs the cost of purchasing and
installing the rack?
•Case II:Utilizing a 3-high pallet rack for an SKU with
N=30 (pallets), which are currently floor-stacked 3-high, to
come within 4 ft from the ceiling.
–Current footprint: 10 pallet positions
–Introducing a 3-high rack does not create any new positions, and it
will actually require more space in order to accommodate the rack
structure (cross-beams and the space above the pallets, required for
pallet handling)
Determining an efficient lane depth
(in case of randomized storage)
•A conceptual characterization of the problem:
–More shallow lanes imply more of them, and therefore, more space
is lost in aisles (the size of which is typically determined by the
maneuvering requirements of the warehouse vehicles)
–On the other hand, assuming that a lane can be occupied only by
loads of the same SKU, a deeper lane will have many of its
locations utilized over a smaller fraction of time
(“honeycombing”).
–So, we need to compute an optimal lane depth, that balances out
the two opposite effects identified above, and minimizes the
averagefloor space required for storing all SKU’s.
Lanes
Lane Depth
(3-deep)
Lane Height
Aisle
Notation
•w = pallet width
•d = pallet depth
•g = gap between adjacent lanes
•a = aisle width
•x = lane depth
•n = number of SKU’s
•N_i = max storage demand by SKU i
•z_i = column height for SKU I
•lane footprint = (g+w)(d*x+a/2)
Key results
•Assuming that the same lane depth is employed across all n SKU’s,
under floor storage, the average space consumed per pallet is
minimized by a lane depth computed approximately through the
following formula:
x_opt = [(a/2dn)*_i (N_i /z_i)]
•The optimal lane depth for any single SKU i, which is stackable z_i
pallets high, is
x_opt = [(a/2d)*(N_i /z_i)]
•Assuming that the same lane depth is employed across all n SKU’s,
under rack storage, the average space consumed per pallet is
minimized by a lane depth computed approximately through the
following formula:
x_opt = [(a/2dn)*_i N_i ]