Storage Strategy Engine

Planning to redesign or open a new facility and don’t know how much space or what type of storage you need? Need to generate a baseline for your operations to better assess automation projects? Is timely and accurate slotting guidance a challenge?

Why not solve all of these issues in minutes?

Step 1: Upload Data

The Storage Strategy Engine requires 3 datasets: SKU master, location-level inventory, and SKU velocity in either order line or summarized datasets

  • SKU Master:

    • SKU ID

    • Unit of Measure

    • Dimensions (length, width, height)

  • Location-level Inventory:

    • SKU ID

    • Location ID

    • Location Dimensions (length, depth, height)

    • Quantity

  • SKU Velocity - Order line:

    • SKU ID

    • Order ID

    • Date

    • Unit of Measure

    • Quantity

  • SKU Velocity - Summarized:

    • SKU ID

    • Unit of Measure

    • Quantity

    • Number of days sold in period

Step 2: Set Modeling Parameters

The Storage Strategy Engine is able to model changes in inventory, velocity, and locations across several parameters:

  • General Parameters:

    • Pickface days-on-hand requirements

    • Volume increase factor

    • Inventory increase factor

    • Clear height

    • Max location utilization percent

    • Minimum quantities in pickface locations

  • Location Fitting Logic:

    • Single pickface per SKU

      • Option to fit SKUs with inventory but without volume to a location

    • Fit to multiple pickface locations

    • Fit everything to a pickface, no reserve locations

  • Pickface Locations:

    • Only use existing locations

    • Only use our default library of locations

    • Use both existing or default library locations

    • Use custom list of uploaded locations

  • Reserve Locations:

    • Only use existing locations

    • Only use our default library of locations

    • Use both existing or default library locations

    • Use custom list of uploaded locations

    • Use pickface location types

  • Bay Types:

    • Use standard bay library

    • Use custom list of uploaded bay types