Predictika · Cube storage configuration: robots, bins, grid height and ports

An AI sales agent's AutoStore Red Line configuration, checked before it goes out

An AI sales agent prepares a cube-storage configuration: the robot model, bin height, grid levels, port type and rate, bin load and dividers, daily robot hours and ambient temperature. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the public product figures and returns a verdict, every reason and the figures it computed.

Scope: AutoStore Red Line configurations: robot model, bin height, grid levels, port type and rate, bin load, dividers, daily hours and temperature. See everything this validator covers

This validator models configurations of one product line, the AutoStore Red Line (R5, R5 Pro, R5+ and R5+ Pro robots; 220, 330 and 425 mm bins; CarouselPort, ConveyorPort, VersaPort, FusionPort and RelayPort), not just the scenarios shown below.

  • Robots and bins — the 425 mm bin is handled only by the R5+ and R5+ Pro; grid levels are limited per bin height (330 mm bins 18, 425 mm bins 14, 220 mm bins 26 on one AutoStore page and 24 on another, so the gap goes to a person); every bin is limited to 30 kg and to 32 divider sections.
  • Ports — each port type has a published maximum in bins per hour (for example the CarouselPort 400 at floor level and 500 at mezzanine level), and the rate the order states is compared with it; the VersaPort floor-level rate is published only for 16-level and 18-level grids.
  • Operation — a typical working day for the R5 and R5+ is about 20 hours because each robot needs at least 4 hours of charging per day; Pro robots above 20 hours, ambient temperatures below +1 C and other cases the sources leave open go to a person; above +35 C or below -25 C is blocked.

Any Red Line configuration that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (AutoStore publishes none, so this validator produces no price build-up or line-item quote), how many robots a site needs, grid footprint, software, service and other AutoStore lines.

The AI sales agentBuilds the cube-storage configuration from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 scenarios in 2 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
A bin height that only some robots can handleOnly with care
A compatibility between a bin option and a robot model is a rule per pair; it works, but each new robot or bin needs another rule kept in step with the product pages.		Robot model and bin height arrive together and are checked on every call.
Grid height limits that depend on the bin heightOnly with care
A maximum number of levels per bin height is a lookup that must be written and maintained as a separate table.		The grid levels are compared with the published maximum for the chosen bin height.
Port rates that depend on port type, floor or mezzanine level and grid levelsOnly with workarounds
The published maximum is a function of three choices, and where a figure is not published for some grids a plain rule cannot say so; a reviewer is needed.		The stated rate is compared with the published maximum, and a case with no published figure goes to a person with the reason.
Facts that two public pages state differentlyOnly with workarounds
A rule has one answer; where the sources differ the case needs a human, which a plain validation rule cannot express.		The overlap between the two figures goes to a person with the reason, and the rest is decided.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1The 425 mm bin can only be handled by the R5+ and R5+ Pro robots, but the order uses a robot without that capability.
2The grid has 19 levels, but AutoStore publishes a maximum of 18 levels for this bin height.
3The grid has 15 levels, but AutoStore publishes a maximum of 14 levels for this bin height.
4AutoStore pages differ on the 220 mm bin stack (24 bins on one page, 26 levels on another); 26 levels needs a person to confirm it.
5The grid has 27 levels, but AutoStore publishes a maximum of 26 levels for this bin height.
6AutoStore lists a maximum grid height of 14 levels for the R5+ and R5+ Pro; 16 levels with these robots needs a person to confirm it.
7AutoStore pages differ on the 220 mm bin stack (24 bins on one page, 26 levels on another); 25 levels needs a person to confirm it.
8AutoStore lists a maximum grid height of 14 levels for the R5+ and R5+ Pro; 25 levels with these robots needs a person to confirm it.
9The planned bin load is 31 kg, but all AutoStore bin sizes have a limit of 30 kg.
10The order asks for 33 sections in a bin, but a bin can be subdivided into at most 32 sections.
11One AutoStore page says the 425 mm bin can be divided into a maximum of 8 containers; 9 sections needs a person to confirm it.
12The plan runs each robot 21 hours a day, but a typical working day for the R5 and R5+ is about 20 hours because each robot needs at least 4 hours of charging per day.
13The plan runs each robot 24 hours a day, but a typical working day for the R5 and R5+ is about 20 hours because each robot needs at least 4 hours of charging per day.
14AutoStore says the Pro robots support 24-hour multishift operation but publishes no hours per day; 22 hours a day needs a person to confirm it.
15The plan runs each robot 25 hours a day, which is more than a day has.
16The ambient temperature of 36 degrees C is above the +35 degrees C upper limit AutoStore publishes for its robots.
17AutoStore publishes +1 degrees C to +35 degrees C for its robots and a -25 degrees C to +6 degrees C range for chilled and frozen storage; 0 degrees C needs a person to confirm the cold-storage configuration.
18AutoStore publishes +1 degrees C to +35 degrees C for its robots and a -25 degrees C to +6 degrees C range for chilled and frozen storage; -25 degrees C needs a person to confirm the cold-storage configuration.
19The ambient temperature of -26 degrees C is below the -25 degrees C lower limit of the chilled and frozen range AutoStore publishes.
20The order states 401 bins per hour per port, but the published maximum for this port is 400 bins per hour.
21The order states 501 bins per hour per port, but the published maximum for this port is 500 bins per hour.
22The order states 240 bins per hour per port, but the published maximum for this port is 180 bins per hour.
23The order states 180 bins per hour per port, but the published maximum for this port is 170 bins per hour.
24AutoStore publishes the VersaPort floor-level rate only for 16-level and 18-level grids; a person should confirm the rate for 14 levels.
25The order states 551 bins per hour per port, but the published maximum for this port is 550 bins per hour.
26The order states 700 bins per hour per port, but the published maximum for this port is 650 bins per hour.
27The order has 0 robots and 4 ports; at least 1 of each is needed.
28The order has 40 robots and 0 ports; at least 1 of each is needed.
29The grid has 20 levels, but AutoStore publishes a maximum of 14 levels for this bin height.
30The planned bin load is 35 kg, but all AutoStore bin sizes have a limit of 30 kg.
31The order asks for 40 sections in a bin, but a bin can be subdivided into at most 32 sections.
32The plan runs each robot 22 hours a day, but a typical working day for the R5 and R5+ is about 20 hours because each robot needs at least 4 hours of charging per day.
33The ambient temperature of 40 degrees C is above the +35 degrees C upper limit AutoStore publishes for its robots.
34The order states 500 bins per hour per port, but the published maximum for this port is 400 bins per hour.
35AutoStore says the Pro robots support 24-hour multishift operation but publishes no hours per day; 23 hours a day needs a person to confirm it.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Bins, robots and port rate: A 425 mm bin system on R5 robots with a RelayPort rate of 700 bins per hour

    
The agent's request. Please quote an AutoStore Red Line system with 60 R5 robots, 6 RelayPorts at floor level and a grid of 14 levels using 425 mm bins, planned for a bin load of 34 kg and 4 divider sections per bin. The robots will run 22 hours a day in an ambient temperature of 18 degrees C. The configuration states 700 bins per hour per port. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • 425 mm bin needs an R5+ robot. The 425 mm bin can only be handled by the R5+ and R5+ Pro robots, but the order uses a robot without that capability.
    • 
      
  • Bin load above 30 kg. The planned bin load is 34 kg, but all AutoStore bin sizes have a limit of 30 kg.
    • 
      
  • Daily hours above the charging limit. The plan runs each robot 22 hours a day, but a typical working day for the R5 and R5+ is about 20 hours because each robot needs at least 4 hours of charging per day.
    • 
      
  • Stated port rate above the published maximum. The order states 700 bins per hour per port, but the published maximum for this port is 650 bins per hour.
    • 
    

    
2. Bins, robots and port rate: The agent resubmits after fixing the errors

    
The agent's request. Please quote an AutoStore Red Line system with 60 R5+ Pro robots, 6 RelayPorts at floor level and a grid of 14 levels using 425 mm bins, planned for a bin load of 28 kg and 4 divider sections per bin. The robots will run 22 hours a day in an ambient temperature of 18 degrees C. The configuration states 650 bins per hour per port. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Pro robot above 20 hours a day to confirm. AutoStore says the Pro robots support 24-hour multishift operation but publishes no hours per day; 22 hours a day needs a person to confirm it.
    • 
      
  • Configuration summary. 60 robots and 6 ports; published maximum 14 grid levels for this bin height.
    • 
    

    
3. Bins, robots and port rate: The agent resubmits after fixing the errors

    
The agent's request. Please quote an AutoStore Red Line system with 60 R5+ Pro robots, 6 RelayPorts at floor level and a grid of 14 levels using 425 mm bins, planned for a bin load of 28 kg and 4 divider sections per bin. The robots will run 20 hours a day in an ambient temperature of 18 degrees C. The configuration states 650 bins per hour per port. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Configuration summary. 60 robots and 6 ports; published maximum 14 grid levels for this bin height.
    • 
    

    
4. Grid height and port rate: A 330 mm bin grid of 20 levels with a CarouselPort rate of 450 bins per hour

    
The agent's request. Please quote an AutoStore Red Line system with 80 R5 robots, 8 CarouselPorts at floor level and a grid of 20 levels using 330 mm bins, planned for a bin load of 22 kg and 6 divider sections per bin. The robots will run 18 hours a day in an ambient temperature of 20 degrees C. The configuration states 450 bins per hour per port. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Grid taller than the bin height allows. The grid has 20 levels, but AutoStore publishes a maximum of 18 levels for this bin height.
    • 
      
  • Stated port rate above the published maximum. The order states 450 bins per hour per port, but the published maximum for this port is 400 bins per hour.
    • 
    

    
5. Grid height and port rate: The agent resubmits after fixing the errors

    
The agent's request. Please quote an AutoStore Red Line system with 80 R5 robots, 8 CarouselPorts at floor level and a grid of 18 levels using 330 mm bins, planned for a bin load of 22 kg and 6 divider sections per bin. The robots will run 18 hours a day in an ambient temperature of 20 degrees C. The configuration states 450 bins per hour per port. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated port rate above the published maximum. The order states 450 bins per hour per port, but the published maximum for this port is 400 bins per hour.
    • 
    

    
6. Grid height and port rate: The agent resubmits after fixing the errors

    
The agent's request. Please quote an AutoStore Red Line system with 80 R5 robots, 8 CarouselPorts at floor level and a grid of 18 levels using 330 mm bins, planned for a bin load of 22 kg and 6 divider sections per bin. The robots will run 18 hours a day in an ambient temperature of 20 degrees C. The configuration states 400 bins per hour per port. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Configuration summary. 80 robots and 8 ports; published maximum 18 grid levels for this bin height.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a cube-storage configuration: the robot model, bin height, grid levels, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the public product figures and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote an AutoStore Red Line system with 60 R5 robots, 6 RelayPorts at floor level and a grid of 14 levels using 425 mm bins. The robots will run 22 hours a day in an ambient temperature of 18 degrees C. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. The 425 mm bin can only be handled by the R5+ and R5+ Pro robots, but the order uses a robot without that capability. The planned bin load is 34 kg, but all AutoStore bin sizes have a limit of 30 kg. The plan runs each robot 22 hours a day, but a typical working day for the R5 and R5+ is about 20 hours because each robot needs at least 4 hours of charging per day. The other one is on screen.
    6. 
      
  6. The validator returned four blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for a bin height that only some robots can handle, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the robot model to R5+ Pro, the bin load to 28 kg and the stated rate per port to 650 bins per hour.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The four blocking findings are cleared; one approval remains for a person: Pro robot above 20 hours a day to confirm.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the robot hours per day to 20.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared, and the validator's figure matches the quote.
    18. 
      
  18. Four problems caught in one call, fixed in two passes, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer.
    19.