Failure-handling strategies for mobile robots in automated warehouses

Thomas Lienert, Ludwig Stigler, Johannes Fottner

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

4 Scopus citations

Abstract

Automated warehouses operated by a fleet of robots not only offer great flexibility, as fleet size can be adjusted easily to throughput requirements, they also provide higher redundancy compared to common solutions for automated storage and retrieval systems. In case a single robot fails, the remaining fleet of robots is able to continue working within the system, so that throughput is only slightly affected. However, adequate strategies are required for this scenario. In this contribution, we present four different approaches to cope with robot downtimes, which are based on the routing of the robots. These strategies are compared by performing a simulation study in which a robotic mobile fulfilment system is considered.

Original languageEnglish
Title of host publicationProceedings - European Council for Modelling and Simulation, ECMS
EditorsMauro Iacono, Francesco Palmieri, Marco Gribaudo, Massimo Ficco, Lars Nolle, Evtim Peytchev
PublisherEuropean Council for Modelling and Simulation
Pages199-205
Number of pages7
Edition1
ISBN (Electronic)9783937436654
DOIs
StatePublished - 1 Jun 2019
Event33rd International ECMS Conference on Modelling and Simulation, ECMS 2019 - Caserta, Italy
Duration: 11 Jun 201914 Jun 2019

Publication series

NameProceedings - European Council for Modelling and Simulation, ECMS
Number1
Volume33
ISSN (Print)2522-2414

Conference

Conference33rd International ECMS Conference on Modelling and Simulation, ECMS 2019
Country/TerritoryItaly
CityCaserta
Period11/06/1914/06/19

Keywords

  • Automated Warehouses
  • Discrete Event Simulation
  • Failure Handling
  • Mobile Robots
  • Time Window Routing Method

Fingerprint

Dive into the research topics of 'Failure-handling strategies for mobile robots in automated warehouses'. Together they form a unique fingerprint.

Cite this