The impact of the existence of multiple adjustable robust solutions

Frans de Ruiter, Ruud Brekelmans, Dick den Hertog

Research output: Contribution to journalArticleScientificpeer-review

17 Citations (Scopus)
274 Downloads (Pure)


In this note we show that multiple solutions exist for the production-inventory example in the seminal paper on adjustable robust optimization in Ben-Tal et al. (Math Program 99(2):351–376, 2004). All these optimal robust solutions have the same worst-case objective value, but the mean objective values differ up to 21.9 % and for individual realizations this difference can be up to 59.4 %. We show via additional experiments that these differences in performance become negligible when using a folding horizon approach. The aim of this paper is to convince users of adjustable robust optimization to check for existence of multiple solutions. Using the production-inventory example and an illustrative toy example we deduce three important implications of the existence of multiple optimal robust solutions. First, if one neglects this existence of multiple solutions, then one can wrongly conclude that the adjustable robust solution does not outperform the nonadjustable robust solution. Second, even when it is a priori known that the adjustable and nonadjustable robust solutions are equivalent on worst-case objective value, they might still differ on the mean objective value. Third, even if it is known that affine decision rules yield (near) optimal performance in the adjustable robust optimization setting, then still nonlinear decision rules can yield much better mean objective values.
Original languageEnglish
Pages (from-to)531-545
JournalMathematical Programming
Issue number1-2
Early online date30 Jan 2016
Publication statusPublished - 11 Oct 2016


  • adjustable robust optimization
  • production-inventory problems
  • folding horizon
  • multiple solutions


Dive into the research topics of 'The impact of the existence of multiple adjustable robust solutions'. Together they form a unique fingerprint.

Cite this