3
Process characteristics:
- This is for companies that rely on system directed cluster picking.
- Have a paperless picking process and do not want to print unnecessary (license plate) labels
- Have unique, but fixed cluster positions/bins/totes. F.e. positions are named something like:
- CART-01-P01 , CART-01-P02 … CART-01-P15. Explanation: ClusterId ''Cart 01'' has got 15 positions
- CART-02-P01, CART-02-P02 … CART-02-P20. Explanation: ClusterId ''Cart 02'' has got 20 positions
So the cart itself is referred to as ''Cluster'' and the A,B,C, etc are referred to as ''Cluster position'' or ''license plate'' in this context.
- Use the standard ''pack'' screen to scan the cluster position and pack it into containers.
Depending on the cluster profile setup (meaning fields like ''activate position'', ''number of positions'', ''position name'' and ''sort verification type'' warehouse management will assign a workid to a cluster position. There are 3 options to identify the cluster position:
1. Numeric: Cluster positions are called 1, 2, 3, etc.
2. Alpha: Cluster positions are named A, B, C, etc.
3. License plate.
The system will link the number of workId's automatically and nicely to the cluster using the number of positions setup.
Problem description:
With fixed and unique positions like in this example CART-* it is very obvious to go for the License plate option.
Problem 1: When choosing for option 3 (identify a license plate as cluster position) it is cumbersome to link the cluster position to the workId. This is because you need to scan 15 or 20 positions even before any goods are picked or scanned to the position!
Problem 2: If you drop the requirement of having a unique and fixed naming and when choosing for option 1 or 2 the workId will be linked to the cluster and cluster positions fully automatically.
This solves the initial problem, but immediately creates a new one that occurs right after putting the inventory at the packing station, meaning that the cluster position cannot be scanned starting the packing process.
The reason is clear: There are multiple cluster positions 1,2,3 or A,B,C, etc. and the packing process relies on the scan of a unique license plate or shipment scan.
Global solution direction - Predefined/custom naming of cluster positions:
To solve both problems, create a new option (enum) in the ''position name'' field in the cluster profile table. With this option it is possible to create your own fixed cluster position naming convention. It looks a lot like defining the current so called 'location format' where you can indicate how an aisle, position, height find it's place in the locationId.
With the cluster profile with the current set up possibilities behaving like a cluster position/bin/tote is behaving like a license plate, the fixed and predefined cluster positions are automatically linked to the cluster and workId without an additional scan!
- This is for companies that rely on system directed cluster picking.
- Have a paperless picking process and do not want to print unnecessary (license plate) labels
- Have unique, but fixed cluster positions/bins/totes. F.e. positions are named something like:
- CART-01-P01 , CART-01-P02 … CART-01-P15. Explanation: ClusterId ''Cart 01'' has got 15 positions
- CART-02-P01, CART-02-P02 … CART-02-P20. Explanation: ClusterId ''Cart 02'' has got 20 positions
So the cart itself is referred to as ''Cluster'' and the A,B,C, etc are referred to as ''Cluster position'' or ''license plate'' in this context.
- Use the standard ''pack'' screen to scan the cluster position and pack it into containers.
Depending on the cluster profile setup (meaning fields like ''activate position'', ''number of positions'', ''position name'' and ''sort verification type'' warehouse management will assign a workid to a cluster position. There are 3 options to identify the cluster position:
1. Numeric: Cluster positions are called 1, 2, 3, etc.
2. Alpha: Cluster positions are named A, B, C, etc.
3. License plate.
The system will link the number of workId's automatically and nicely to the cluster using the number of positions setup.
Problem description:
With fixed and unique positions like in this example CART-* it is very obvious to go for the License plate option.
Problem 1: When choosing for option 3 (identify a license plate as cluster position) it is cumbersome to link the cluster position to the workId. This is because you need to scan 15 or 20 positions even before any goods are picked or scanned to the position!
Problem 2: If you drop the requirement of having a unique and fixed naming and when choosing for option 1 or 2 the workId will be linked to the cluster and cluster positions fully automatically.
This solves the initial problem, but immediately creates a new one that occurs right after putting the inventory at the packing station, meaning that the cluster position cannot be scanned starting the packing process.
The reason is clear: There are multiple cluster positions 1,2,3 or A,B,C, etc. and the packing process relies on the scan of a unique license plate or shipment scan.
Global solution direction - Predefined/custom naming of cluster positions:
To solve both problems, create a new option (enum) in the ''position name'' field in the cluster profile table. With this option it is possible to create your own fixed cluster position naming convention. It looks a lot like defining the current so called 'location format' where you can indicate how an aisle, position, height find it's place in the locationId.
With the cluster profile with the current set up possibilities behaving like a cluster position/bin/tote is behaving like a license plate, the fixed and predefined cluster positions are automatically linked to the cluster and workId without an additional scan!
STATUS DETAILS
Needs Votes