The lower-count pattern is still in our comparison. Support looks more promising, tool opening still needs review, and dispatch says the extra pallets could block their staging space. I need that cost beside the fancy alternating option, not dismissed as somebody else's department.
Ask dispatch to walk through a busy changeover with it. Extra pallet isn't just another footprint if they have to move the previous product out before there's anywhere to put it.
I would also ask what the normal collection rhythm is. A staging problem might depend on when pallets leave, though that is not permission to assume a more convenient collection schedule for the robot proposal.
Clara, collection rhythm is fixed for this comparison. Jane, the busy changeover is where dispatch predicts the blockage. Quiet single-product runs are easy, as usual.
Could the lower-count option be assessed for only the product where it gives the clearest support benefit? A universal pattern might not be the useful target.
Aaron, one product is where most of the support concern sits. I'll ask for that limited option too. Bruno and Jane, selection and changeover effort will stay in it. Nobody gets a free clever feature.
Can dispatch show the expected pallet buildup using their actual outgoing batches? A sketch with the collection points marked may expose the awkward period before anyone spends time redrawing the station.
Dispatch did the sketch. The worst overlap is old product waiting to leave while the new batch starts. Extra pallet worsens it, but the overlap exists with either pattern.
That is useful to know without charging the entire existing problem to the alternative. What additional handling does the extra pallet cause during that overlap?
Still being worked out. I have kept the existing overlap and the added pallet separate in the comparison. Packaging and tool access reviews remain open too.