- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper presents FLOWS, a framework that turns natural-language warehouse requirements and drawings into rack layouts. An LLM formulation agent writes an explicit integer-programming formulation over a graph of the warehouse geometry and a finite rack catalog (e.g., "at least 16 slots; every rack accessible"); a separate strategy agent selects a solution procedure; a symbolic IP solver places the racks; and candidate layouts are checked by static validation (geometry, clearance, access) and an operational simulation (throughput, cycle time, travel), with diagnostic feedback for revising the formulation. The paper reports verified layouts on all 42 warehouse plans and better mean operating performance than two adapted planners.
Critical strengths
- The problem framing is interesting: separating formulation, solution procedure and acceptance makes each stage inspectable, and the idea of an LLM producing an explicit, checkable optimization formulation is novel for this application.
- The paper is clear and easy to follow; the problem (capacity vs. accessibility, physical feasibility vs. operational performance) is well motivated.
Critical weaknesses
- The experiments do not match the claimed role of the LLM. The LLM is said to do formulation, strategy selection and feedback-driven revision, but the experiments only cover formulation; there are no experiments on strategy selection or on revision from feedback. In the ablations the LLM components contribute little and the gains are small, so the evidence is loose relative to the claims.
- No clear evidence that an LLM is needed, and limited evaluation. The paper does not justify why this problem needs to be solved with a large language model rather than a conventional pipeline. The experimental cases are fixed; it is unclear how the system performs on new floor plans it has not seen, and there is no real-world deployment, only simulation and physical checks.
Questions for authors
- Can you provide experiments that isolate the contribution of LLM-based strategy selection and feedback-driven revision?
- What does the LLM provide that a non-LLM formulation pipeline would not?
- How does FLOWS perform on new, expert-validated floor plans not used during development?
- Is there any evaluation beyond simulation, e.g., in a real warehouse deployment?
4 comments
Thanks for the rebuttal. It addresses some of my questions. I will keep my rate.
Dear reviewer, We hope we can address all your concerns. Please let us know if any issues remain unresolved. We welcome any further feedback and would be grateful if you would consider raising your score in light of our clarifications. Best regards, all authors
Dear Reviewer,
Thanks again for your careful review and insightful question! I am writing to make sure you have seen our rebuttal. And if our rebuttal addressed your question, we sincerely hope you can consider improving your recommendation score, which will help us a lot.
Best regards,
All authors
Response to Reviewer Zrej
We submitted a revised manuscript with changes marked in blue.
We thank the reviewer for recognizing the inspectable architecture. The revision adds component studies and tests on additional drawings.
Q1: Can strategy selection and feedback revision be evaluated separately? [Original: Weakness 1; Question 1]
A1: Yes. Section 4.4 and Appendix E fix reference formulations to isolate Stages II and III from Stage I.
Condensed from manuscript Table 4:
Stage II uses identical formulations, placements, hints, and static checks under a 600-second total budget, including preparation and model calls. Both policies verify the same 33 cases; mean runtime falls by 50.3% overall / 66.4% on common successes. This compares complete policies, including stopping rules, rather than proving superiority over every deterministic alternative.
Stage III increases throughput floors by 10% and decreases cycle-time ceilings by 10%, retaining the 33% footprint floor. The arms share 22 initial KPI-failing layouts and a 1,800-second total budget. Improvement means nondecreasing throughput and nonincreasing cycle time, with one strict improvement; it does not necessarily meet every tightened target. All 19 locked improvements persist on 20 new paired streams, averaging +9.85% throughput / -9.15% cycle time. The revised controller was developed after earlier failures and combines LLM-authored restrictions with deterministic geometric search; we attribute the result to the complete feedback component. These tests support faster verified solving and operational improvement over the tested fixed procedures.
Q2: What does the LLM provide beyond a conventional formulation pipeline? [Original: Weakness 2; Question 2]
A2: The LLM composes supported objectives and constraints from facility-specific requirements; deterministic components bind geometry, compile, solve, and verify. Section 3.2 distinguishes capacity objectives from mandatory regional capacity floors; Appendix A.2 specifies spatial filters, logical combinations, access predicates, and provenance. The agent cannot replace catalog dimensions, waive checks, or introduce unsupported expressions. A fixed template remains suitable for fixed requirements; FLOWS offers flexibility within its supported modeling language.
The C04 case study illustrates adaptability to an irregular boundary and internal exclusions: 33.00% footprint utilization versus 28.85% for CBS and 12.08% for CPU, with throughput gains of 17.62% / 9.31%, respectively (Section 4.1). These outcomes support the framework's ability to accommodate complex geometry while improving storage and operations; they do not isolate LLM superiority over a matched deterministic parser.
Q3: How does FLOWS perform on new, expert-validated floorplans? [Original: Weakness 2; Question 3]
A3: Appendix B now clarifies that only C01 was used for development testing. Prompts, formulation-generation rules, and planning configuration were frozen before the other 41 cases were evaluated; their outcomes were not used for retuning. The 42-case aggregate includes C01.
Appendix H evaluates DXF drawings supplied after framework development. On the 12-drawing / 26-region common completed subset, FLOWS satisfies each region's CBS footprint floor and declared operational requirements. Against CBS, mean footprint utilization is 29.26% versus 29.20%, throughput is 1.96% higher, cycle time 4.27% shorter, and travel 8.70% shorter. This supports applicability to additional geometries, conditional on completed tasks and including corrections/recovery; it is not a frozen single-pass benchmark or overall success-rate estimate. The quantitative dataset is separate from ongoing industrial expert review; we do not claim completed expert validation of this benchmark.
Q4: Is there evidence beyond simulation or a real warehouse deployment? [Original: Weakness 2; Question 4]
A4: FLOWS is developed with a commercial company, and some generated proposals have entered expert review in the partner's engineering workflow. It improves planning efficiency by automating candidate generation and preliminary feasibility checks before expert assessment. This is practical engineering use, rather than a completed warehouse deployment or measured post-deployment operational gains. Because the ongoing review is sensitive, partner and project details cannot be disclosed at this stage. The manuscript's quantitative claims remain based on computational checks and simulation.