Toolbox

In the context of AWO (Advanced Warehouse Operations) a Deviation is a process that happens within the generation of a Task to swap the initial Routing assigned to the Task being generated with a different one, based on the Warehouse definition.

The AWO engine generates Tasks based on the Warehouse Definition, the actual stock situation, and optionally a specific Document, like a Sales Order.

In order to generate a Task the engine follows this steps:

Detect ITT. Based on the user action, the engine has to detect the Inventory Transaction Type (ITT) that needs to be used, e.g., when the user clicks on the Pick button of a Sales Order, the system detects that it has to use the Picking Sales Order ITT
Search Routing. Based on the ITT detected, the engine reads the Warehouse Definition and looks for the Routing Assignment configuration. With this ITT, it searches for the Routing that is related to it
Determine Routing. Finally, the engine has found which Routing it has to use and it can continue with the rest of the operations

With the Routing already determined, the engine can continue with the rest of the validations and operations. However, it is possible that at this moment, the engine detects that a Deviation has been defined for the selected Routing.

In this case the engine checks if it is possible to use the new Routing defined in the Deviation and, if so, it swaps the Routing with the one defined in the Deviation.

The rest of the validations and operations are done using the new Routing.

Note

All the Deviations implemented actually can be used in ITT's that use a Base Task Type of From-To and for which the From is already defined, e.g. a Put-Away of stock, in this case the stock is already selected

This means that the actual deviations can only modify the destination Internal Routing Area by changing the Routing

Deviation To Quality Inspection

The Deviation To Quality Inspection allows to automatically deviate goods to the Quality Inspection Area before placing them in the Storage Area.

This type of deviation is useful in cases in which there are Products that must be always reviewed before storing them, either because the Product itself is quite sensitive or in order to comply with local regulations.

To implement this scenario, it is necessary to define at least three different Internal Routing Areas:

Reception. The Area to receive the goods and from which a Put-Away to Storage should be done
Storage. The Area to store the goods
Inspection. The Quality Inspection Area. This is where the deviation should move the goods instead of Storage in the Put-Away

Deviation To Quality Inspection flow chart

Restrictions

There are several conditions that must be fulfilled to allow the AWO engine to successfully generate a Deviation To Quality Inspection:

Put-Away. This Deviation can be defined only for Routings that use a Task Type with a Base Task Type of From-To. Additionally, this Deviation will only work with ITT's of the type Put-Away.
Product Definition. The Product must be also defined as Deviation To Quality Inspection
Full Quantity. In a Deviation To Quality Inspection, all the quantity of the Task will be deviated to the Inspection Area

Configuration

As explained above, it is necessary to have three different Internal Routing Areas, and a Routing to do the Put-Away from Reception to Storage Areas

Reception, Storage and Inspection Internal Routing Areas

Put-Away Routing Configuration

In the Routing for the Put-Away from Reception To Storage it is necessary to enable the flag for Deviation To quality Inspection

Put-Away Routing with Deviation To Quality Inspection enabled

Deviation To Quality Inspection Routing Configuration

It is necessary to define a new Routing for Deviation To Quality Inspection that goes from Reception to Inspection Areas.

Routing definition for Deviation To Quality Inspection

Also, a Routing Assignment that links with the new Routing is necessary. And finally the Warehouse Algorithm Assignments related to this ITT should be also defined (this ITT needs to find the destination Bin to place the stock, so only PA type algorithms will be shown)

Product Configuration

Finally, it is necessary to enable the Deviation To Quality Inspection flag for those Products that need to be deviated to Inspection. Only the ones flagged as such will be deviated, the rest will not.

Deviation To Quality Inspection Product configuration

Example

With the configuration in place, when a Put-Away is generated from Reception to Storage Area, if both the Routing and Product are flagged as Deviation To Quality Inspection, the Task generated will not be a Put-Away Task from Reception to Storage, but a Deviation To Quality Inspection Task from Reception To Inspection

Deviation To Quality Inspection Task

Deviation To Cross Docking

This feature is available starting from 1.5.200.

The Deviation To Cross Docking is a functionality of AWO that allows to optimize Warehouse Operations by deviating goods directly to the Shipping Area when there is an Order pending to be picked for the same day.

By directly moving the goods to the Shipping area is possible to bypass the operation of Putting-Away the goods into storage and then perform the picking operations, thus maximizing efficiency in the number of movements performed to prepare an Order.

This deviation only takes into account Orders (either Sales Orders or Distribution Orders that have a delivery date for the actual day)

To implement this scenario it is necessary to define at least three different Internal Routing Areas:

Reception. The Area to receive the goods and from which a Put-Away to Storage should be done
Storage. The Area to store the goods
Shipping. The Area from which the goods will be delivered. This is where the deviation should move the goods instead of Storage in the Put-Away

Deviation To Cross Docking flow chart