Controlling Bin Locations

📘
NOTICE
Avoid using the features marked as Deprecated. Features marked as deprecated are not supported by AS
Router

📘
NOTICE
AS Router only supports one code per cell. Use ranges when multiple codes are needed.

Introduction

The features and concepts described in this chapter make it possible to assign specific grid areas to store
specific bins or SKUs. One use case is to assign one area of the grid for ESD bins and another area for non-ESD bins.

These features also enable installations to operate without bin preparation or digging for the normal
processes. This is supported by not mixing different SKUs in the same stack, so that outgoing bins can always
be taken from the top. Please note that such use cases will typically cause a lower fill rate in the grid as many
stacks will be partially filled.

Bin Content Code

Every AutoStore Bin is assigned a content code. Previously, the content codes specified whether a Bin is
empty or not (and possibly also compartment information). They were used for the put-away process. The
WMS may request bins (in the port queue) by specifying content codes instead of specific Bin IDs.

The same Bin content code is central in Controlling the Location of Bins, but depending on the use case, the
Bin content code may also reflect the inventory of the Bin (SKU or batch).

The Bin content code is controlled by the WMS, and is updated via the interface. The mapping between SKU/
batch and content codes is defined by the WMS. The Bin content code may identify a SKU or a group of
SKUs. The WMS may also use multiple content codes per SKU to control the bin flow

📘
Learn more about Content Codes HERE.

Interface

The functionality for Controlling the Location of Bins is available in both Bin Interface and Task Interface.

Much of the behavior is controlled by static configurations.

The Bin content code is set by using the interface methods: closebin, insertbin, and updatebin.

A new method is introduced: updatecellandbincontent. This method updates the content code of a specified
cell and all the Bins that are stored in that cell. (This method is often not required; it is only needed for some
specific use cases.) Using the AutoStore Console, it will be possible to update the cell content code without
changing the content code of the Bins that are stored in the cell.

📘
NOTICE
See section Feature Compability about feature support in ASPlanner and ASRouter.

Configurations

AutoStore includes the following main configurations to control the behavior:

Configuration	Value	Description
OverflowToFreeCells	True or False	A Bin cannot be placed in a cell without content code when there exist cells that have a cell content code equal to the given Bin's content code, unless this setting is enabled. In other words: A Bin can be placed in an empty stack without cell content code if, and only if, either: (a) There are no cells with cell content code equal to the Bin's content code. (b) Configuration OverflowToFreeCells==True.
UniqueContentInStack	True or False	UniqueContentInStack feature is deprecated. When this setting is enabled, different Bin content codes cannot be mixed in the same stack.
StackFifoTimeStamp	True or False	StackFifoTimeStamp feature is deprecated. When this setting is enabled, incoming Bins will be placed in locations according to the timestamp of the cell (newest cell timestamp), and outgoing Bins are selected based on the timestamp of each cell (oldest cell timestamp). This configuration can only be True if UniqueContentInStack is also enabled.
ContentRandomTarget	True or False	ContentRandomTarget feature is deprecated. This setting affects the location where inserted Bins are placed. If several options remain after searching for the target with lowest consumer distance, the selection can be random or by shortest driving distance. Random will spread the content throughout the Grid, beneficial if it is inserted at one location, but used at multiple. Shortest driving distance will make it greedy, choosing the option that is most effective at the actual moment in time.

Terms

The features UniqueContentInStack and StackFifoTimeStamp that support these terms are deprecated.

STACKFIFO means that UniqueContentInStack=True and StackFifoTimeStamp=True.

In this mode, Bins with different content code cannot be stored in the same stack.

Each cell includes a time stamp that is set when the first Bin is stored (in an empty stack), and cleared when
the stack becomes empty. When Bins are inserted, they will be stored in the newest stack that is used by that
content code. Hence, the stacks are filled one by one. When a new empty stack is needed, AutoStore will
dynamically select one (according to cell content restrictions and content consumer configurations). When
Bins are taken out, they will be taken from the oldest stack that is used by the content code. Stacks are
emptied one by one – by FIFO based on the cells' time stamp.

Empty Bins are treated specially by AutoStore. A specific content code must be reserved for empty Bins.
Empty Bins do not follow FIFO.

BATCHFIFO means that UniqueContentInStack=True and StackFifoTimeStamp=False.

This mode is similar to STACKFIFO, but does not use the cell time stamp. Typically, the WMS assigns a
content code to each batch (instead of each SKU), and in the picking process the WMS requests a specific
batch to be used. This gives AutoStore more flexibility, because there is no FIFO requirements between the
stacks that belong to the same batch.

Content Consumers

The Content Consumers feature is deprecated.

The Content Consumers configuration specifies where (which ports) the different Bin content codes are
expected to be used (consumed).

Content code ranges can be used in the configuration. A content code range can be associated with a list of
Ports (consumers) where the Bins are expected to be delivered. The configuration may contain many such
associations. The same content code may only be included in one association (no overlapping ranges).

AutoStore will use the Content Consumers configuration when it selects among legal storage location in the
Grid for a Bin.

The Content Consumer configuration does not control which Ports the Bins are delivered to. The Content
Consumer configuration only tells AutoStore where the recommended storage locations in the Grid are. The
WMS can request the Bins in any Port independent of the Content Consumer configurations. For best
performance, they should be requested in Ports close to their current position.

A Bin is considered being placed in the Proximity of its configured consumers if it is placed among the 50
nearest cells of any of its consumers. Nearest means shortest Manhattan traveling distance (L-shape route).

Managing Frozen Zone

In a solution that supports frozen and chilled temperature storage areas in the same grid, it is critical that the
bins are stored in the correct area. This is controlled by using content codes.

Bins assigned to the frozen zone shall remain assigned to the frozen zone. Reassigning a bin to a different temperature zone can impact its lifespan and quality.

📘
NOTICE
Installations with different temperature zones in the same Grid require AS Router. Although AS Planner
supports cell content codes, AS Planner will to a greater extent allow bins to temporarlily be in another
zone.

Defining the Zones

Normally, different content codes are used to reflect if the bins are empty or not, and the number of available
compartments in the bins. In a multi-temperature environment, the content code must also reflect which zone
the bin belongs. Each temperature zone shall be assigned a range of content codes. The Content Ranges
shall not overlap.

▪ Each temperature zone shall have it's specific Content Set or Content Code Range.
▪ Each grid storage cell shall be defined with Cell Content = its zone's Content Code Range.
▪ Every bin shall belong to one and only one zone and use content codes that belongs to its zone's Content
Code Range.

It is the responsibility of the WMS to maintain a correct bin content code. Assigning wrong content code to a
bin may cause the bin to be stored in the wrong temperature zone and may damage the bin's content.

Controlling Bin time outside its Zone

In order to preserve the quality of the stored inventory, the WMS must control the time a bin spends outside its
storage zone. The WMS should monitor that the handling time in the port is compatible with the inventory of
the bin, and also consider total time outside the zone within a time interval if the bin is used several times.

To avoid that a bin is stuck in a port because the operator has left the port, the WMS should implement some
kind of timeout and automatic log out. If the port is not being used, it is important to close the bin and close
the port so that the bin can be returned to its storage zone.

To avoid that bins stay too long in the port, AutoStore has introduced a port configuration: AutoFlush. When
AutoFlush is enabled, the system will, after a certain period with idle time (time since the port had a selected
bin), automatically flush the bins in the port so that they are returned to their storage zone. The feature does
not flush the bins with bin mode OPEN. Bins that are open are controlled by the WMS and should be handled
by some timeout functionality in the WMS.

AutoFlush can be configured for each port, and can have a different timeout value for each port. AutoFlush
can be configured via AS Console, and should normally be set in the initial setup. It is important that
AutoFlush is enabled in multi-temperature solutions.

Stop and Service the System

The WMS should also detect if any bins are outside its temperature zone during Stop and Service mode.