Idea

Maryam H2 avatar image
0 Likes"
Maryam H2 suggested Maryam H2 commented

Slot Weighting Feature

I'd like to suggest the addition of an automated slot weighting feature within the rack object slot assignment strategy.

This feature would automatically calculate and assign specific weights to slots based on various factors. These factors might be factors such as proximity to input/output points, the likelihood of product entry/exit, ease of navigation within the storage, slot height for handling efficiency, temperature considerations, and order picking sequence. I think we could then efficiently categorize slots as "hot," "warm," or "cold," which facilitates improved slot assignments that are based on considerations of accessibility and efficiency.

rackstorage systemslot assignment
· 8
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jason Lightfoot avatar image Jason Lightfoot ♦♦ commented ·
For this you can use findSlot query/activity so that you can ORDER BY one or more columns that are your described factor - no new development is required.
1 Like 1 ·
Maryam H2 avatar image Maryam H2 Jason Lightfoot ♦♦ commented ·

@Joerg Vogel@Jason Lightfoot

well, I was thinking about a feature (or key performance metric?) that software calculates and assign weights/scores to slots based on the defined factors (order picking sequence, proximity to enter/exit point, etc.). since the warehouse conditions change over running time (weeks or one month) the software would continually adapt the weights assigned to slots to reflect their utilization. After running the model over replications the software categorizes the slots into hot, warm, and cold based on their assigned weights value to each slot. This is very helpful to optimize slot assignments in real world and to optimize/modify the design of the warehouse. Do we have this feature/KPI already?

I believe Find Slot activity, is more of a search criteria to find available slots based on specific factors. While it's undoubtedly beneficial for organizing slots and assigning items to them, it doesn't inherently generate historical weight data for slots based on the factors I mentioned.


0 Likes 0 ·
Jason Lightfoot avatar image Jason Lightfoot ♦♦ Maryam H2 commented ·
You can write custom user commands to do this for a given slot address that can then be used in PFMs and findslot queries - and any other aspect of the model that might need them.
0 Likes 0 ·
Show more comments

1 Comment

Joerg Vogel avatar image
0 Likes"
Joerg Vogel commented

I understand what you want to achieve. I think it has been already available by slot labels. Each time you undertake a query to find one slot or you query for a subset of all slots in a warehouse you can calculate a value which distinguish a level of slot quality.

· 2
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jason Lightfoot avatar image Jason Lightfoot ♦♦ commented ·

The prebuilt slot assignment strategies logic loops through all the slots and exits when it finds one that matches the strategy - it does not consider all the slots in the way an ORDER BY clause in a findSlot query would.

1 Like 1 ·
Joerg Vogel avatar image Joerg Vogel Jason Lightfoot ♦♦ commented ·
Thank you, @Jason Lightfoot, this makes sense and accelerates findSlot method a lot. Still there are slot labels which can be evaluated finding a slot.
0 Likes 0 ·

Your Opinion Counts

Share your great idea, or help out by voting for other people's ideas.

Related Ideas