1 Introduction

Globalization is a growing trend that is driving companies to increase supply chain performance and warehouse efficiency. Just-in-time (JIT) production is essential to modern supply chains, requiring raw materials, WIPs (work in process), or assemblies in the right place at the right time. Simultaneously, customer demand is uncertain, being characterized by a complex inventory mix and short lead times. Moreover, the increase in e-commerce broadens the demand for customized products, requested in small volumes within a very short time [1]. Despite the costs, storage and warehousing systems play a pivotal role in achieving such goals throughout the supply chain. In line with Industry 4.0, automated warehouses can manage and optimize goods storage, picking, and shipment processes, ensuring high flexibility and short response time.

The automated storage and retrieval system (AS/RS) is one of the most common automated warehouse solutions. It consists of one or more aisles, each equipped with storage racks on either side, a stacker crane (the storage and retrieval machine, S/R), and input and output stations (called I/O stations). This S/R machine can simultaneously move vertically and horizontally along the aisle. The FEM 9.851 standard is the most used criterion in industrial applications to evaluate the AS/RS performance by estimating the cycle time. Although these automated systems guarantee a high storage density, they are not flexible: at least one stacker crane in each aisle can move unit loads (UL) singly, and simultaneous operations on different tiers are impossible. In addition, this automatic storage solution can usually feed shelving to the maximum triple depth, limiting storage capacity and space efficiency.

Companies are moving towards autonomous vehicle storage and retrieval systems (AVS/RS) to overcome these weaknesses. These automated warehouses can improve flexibility and responsiveness in handling unit loads and increase productivity (i.e., throughput) but still require design-support tools and modeling techniques that can fully exploit their technological potential.

The system object of this study is a tier-captive, deep-lane AVS/RS equipped with lifts and buffer areas (as summarized in Fig. 1) that consists of n-independent tiers (system levels). The tiers are connected with an elevator system that can vary according to the number of lifts, their position within the storage area, and their function (e.g., lift for storage activities, lift for retrieval activities, or lift for both). Each tier has at least two autonomous vehicles: a shuttle and satellite. This is the so-called tier-captive configuration equipped with one or more satellites.

In a generic tier, an input conveyor moves unit loads from the lift to the buffer area (input bay), waiting for the shuttle. The conveyor and buffer area are the handling interfaces between the lift and shuttle. An output conveyor at each tier moves unit loads from the shuttle to the buffer area (output bay), waiting for the lift. In addition, there are input and output bays at the ground floor, where the fleet of man-on-board forklifts or flexible/autonomous vehicles, for example, laser-guided vehicles (LGV) or autonomous mobile robots (AMR), hold unit loads coming from the end-of-line area of a production/packaging system and directly catch unit loads to the shipment area. A typical application of such a handling and storage system configuration is the food and beverage industry equipped with automated filling and packaging machines.

Each tier has a main double-sided cross-aisle and multideep lanes (named channels). Depending on the lane depth, each lane contains one or more unit loads (ULs) of the same item. These are single stock keeping unit (SKU) channels in a last-in-first-out (LIFO) unit load handling. The shuttle moves back and forth along the main cross-aisle (x-direction in Fig. 1), transporting at least one satellite. The satellite departs from the shuttle and enters the storage lanes to store or retrieve the UL (z-direction in Fig. 1). A single satellite can transport one UL or two simultaneously. Therefore, the maximum handling capacity is four ULs if the shuttle has a double handling capacity along the x-direction, and each satellite has a double capacity along the z-direction.

During the storage activity, the UL is stored in a specific (x,y) lane owing to the lift and shuttle and in a specific z-location within the lane owing to the satellite. The satellite stops precisely in front of the last previously inserted UL, respecting the dynamic filling of the lane. The satellite performs the next retrieving or stocking action in this position, agreeing with the LIFO policy for put-away activities.

The shuttle and satellite can be two independent vehicles. Consequently, when the satellite enters a specific lane, the shuttle can perform other handling tasks (e.g., the shuttle can move to the input bay loading another incoming UL). We name this configuration “free satellite (FS),” which differs from the “not-free satellite (NFS).” The FS option allows an increase in the throughput of the system owing to the introduction of multiple satellites for each tier. This is called multisatellite AVS/RS.

Figure 1 summarizes and exemplifies the adopted notation for a unit load AVS/RS deep-lane of six ULs in the z-direction with one double-capacity shuttle and a single satellite.

Fig. 1
figure 1

a AVS/RS front view, b AVS/RS plan view

For AVS/RS, there are no standards (see, for example, FEM 9.581 for AS/RS) for estimating cycle time. Therefore, most recent studies on AVS/RS focused on performance estimation.

The cycle time is one of the main factors affecting the overall performance of the system. The performance indicators that will be elucidated in this study are as follows.

  • Average service time of vehicles (i.e., shuttle, satellite, and lift)

  • Vehicle utilization

  • Average waiting time of ULs

  • Average number of ULs in the queues

  • Throughput of the system

AVS/RS is an expensive material handling technology. Monitoring and optimizing these performance indicators can help to choose a suitable number of vehicles, which directly impacts the cost of the entire system [1]. Most life cycle costs and capabilities are established when selecting device technologies, throughput rate, storage capacity, and rack configuration.

Most of the studies on AVS/RS focused on developing analytical or simulative models to estimate some of these system performance indicators alone, for example, the cycle time. Moreover, the literature rarely discusses deep-lane and multisatellite systems that are widespread in the food and beverage industry. Finally, most AVS/RS performance models are validated through numerical examples and not by applying them to real case studies. These topics are discussed in detail in Sect. 2.

This paper presents an original hybrid analytical-simulative model to estimate and control the performance of a deep-lane and multisatellite AVS/RS, that is, one equipped with multiple FS and NFS for each tier. This model is applied to a case study of the beverage industry conducting a what-if comparative and competitive multiscenario analysis. The analysis is based on realistic assumptions, filling the gap between the literature and real applications. A real AVS/RS inspires the data entry. Therefore, the sequence of storage and retrieval transactions and storage policy is not random.

Another contribution of this paper is a review of the literature on AVS/RS according to the introduction of 14 features grouped into five homogeneous groups: (1) rack configuration, (2) vehicle kinematics and configuration, (3) dispatching rules, (4) modeling approach, and (5) validation.

The remainder of this paper is organized as follows. Section 2 presents a literature review of the AVS/RS systems. Sections 3.1 and 3.2 illustrate the hierarchical approach and the sequence of activities required to perform a storage or retrieval transaction. Section 4 describes the analytical-simulative hybrid model for estimating the cycle time, system throughput, average queue length, average waiting time, and vehicle utilization (i.e., lift, shuttle, and satellite utilization). Section 5 shows the application of the proposed model to a case study that consists of a real AVS/RS in the beverage industry. Finally, Sect. 6 presents the conclusions and directions for further research.

2 Literature review

Research studies on AVS/RS are relatively recent. First, Malmborg [2] illustrated analytical conceptualizing tools for evaluating AVS/RS performance with a tier-to-tier configuration. Over the last few decades, many studies have focused on AVS/RS and SBS/RS (shuttle-based storage and retrieval systems). These two technologies differ in terms of the type of unit load handled. The AVS/RS manages the palletized unit loads, whereas the SBS/RS runs unit loads represented by a tote (i.e., a plastic container). Therefore, this literature review mentions studies on both technologies.

Most studies on AVS/RS and SBS/RS focus on measuring system performance. The literature usually adopts two main approaches to estimate system performance: (1) dynamic modeling and (2) analytical modeling.

The first is based on dynamic modeling via simulation applied to different system configurations that operate according to randomly generated storage and retrieval transactions. Existing studies illustrate two main methods to simulate a generic AVS/RS or SBS/RS, according to the design environment [3]: (1.1) library-based simulation (LIBS) and (1.2) language-based simulation (LABS). The LIBS provides a set of routines that can be adopted with the support of a programming language. LIBS modeling is designed for a specific problem instance, that is, application, according to a Taylor-made approach. This simulative model can replicate the system dynamics according to a specific configuration with high accuracy, providing accurate results. Therefore, developing a simulation model for a large and complex system is highly time consuming and labor intensive. One of the most challenging issues is to support the general results and guidelines for the design, management, and optimization of AVS/RS. The LIBS models the system using commercial digital twin platforms such as Automod [4,5,6], Arena [1, 7,8,9], and Simulink [10].

Ekren [1] presented a simulation model to evaluate the performance of an AVS/RS under various predefined design scenarios. The model simulated 55 types of experiments. Marchet et al. [9] investigated the compound effect of the kinematic behavior of vehicles and lifts and the influence of rack configuration on performance assessment. Both studies explored the system performance using the commercial simulation software Arena. Marolt et al. [10] developed a simulation model in Simulink, focusing on the storage efficiency of a shuttle carrier and relocation strategies in a tier-captive multideep AVS/RS (without considering the lifts). The study compared nine different storage and relocation assignment strategy combinations, focusing on the assessment of dual-command cycle time.

The LABS provides a set of utilities to develop simulation models. This LABS modeling involves the use of a programming language such as VB.NET [11] or MATLAB [12,13,14]. The generic simulation model is easily parameterizable. Therefore, it fits with several system configurations supporting what-if, multiscenarios, and competitive analysis. This dynamic model is suitable for obtaining general results. A significant example of this modeling approach was presented by D’Antonio and Chiabert [12]. They illustrated original analytical models to evaluate AVS/RS cycle time and throughput according to different rack layouts, different fleet compositions, and different types of cycles. Based on a MATLAB routine, the simulation model runs a complete experimental plan of 1980 scenarios (replicated 10 times each). This study aimed to advocate both the design and deployment phases of AVS/RS by enabling performance estimation in a wide variety of scenarios.

The second approach to estimate system performance is based on analytical models and aims to evaluate the expected cycle times and throughput of the system. These performances can also be validated through simulations. Typically, there are two methods of investigating an analytical approach [15]: (1) cycle time modeling and (2) queuing network modeling.

Cycle time models are based on the mathematical relationships between inputs and outputs. The results are reasonably accurate. The researchers that follow this analytical approach aim to evaluate the cycle time, travel distance, and vehicle utilization (i.e., shuttle, satellite, and lift) in a reasonable time. Moreover, the development is typically not time consuming. However, changing the initial assumptions may render the analytical model invalid. In addition, developing an analytical model for a complex system such as an AVS/RS is difficult.

Lerher et al. [16] presented an analytical travel time model to estimate cycle time in an SBS/RS considering the real operating characteristics of the lift and the shuttle carrier (e.g., vehicle acceleration and deceleration). Thus, Manzini et al. [11] developed analytic models to determine the traveled distance and cycle time of shuttles, given alternative layout configurations and considering multideep systems. The results were validated through simulations using VB.NET programming language. Lerher et al. [17] presented analytical travel time models for computation cycle times and the throughput performance of AVS/RS with multiple-tier shuttle vehicles.

These analytical cycle time models focus on service times, ignoring the interactions between vehicles (e.g., lift shuttle and shuttle satellite). Therefore, waiting times are usually ignored.

The second analytical approach focuses on queuing network (QN) models to evaluate the waiting time between lifts and shuttles (and vice versa) and the cycle time to perform storage and retrieval transactions. A QN is a collection of service stations organized in the sequence that customers visit to satisfy their service requirements [18]. There are three main types of QN: the open queuing network (OQN), closed queueing network (CQN), and semi-open queuing network (SOQN). An OQN is a network in which customers arrive at a specified rate from outside to one or more queues, waiting to be processed at a finite number of servers. A CQN differs from OQN because the number of customers circulating in the system is fixed. An SOQN is a variation of the first two queueing network systems: customers arrive at a specified rate, and the maximum number of customers that can be processed at any time is fixed. A synchronization station (the so-called semaphore) decouples the arriving customers from the network resources using a semaphore queue.

Many studies on AVS/RS and SBS/RS have adopted the SOQN. In particular, Tappia et al. [14] modeled each tier of the SBS/RS as a multiclass SOQN, whereas an open queue modeled the vertical transfer. According to Jia and Heragu [19], using an SOQN rather than an OQN or a CQN allows capturing the pairing between transactions and shuttles. This enables a better estimation of the shuttle utilization and transaction waiting time for an available shuttle. Deng et al. [7] presented a SOQN model with class switching to analyze the throughput time of a single-tier shuttle-based compact storage system by varying the number of shuttles, arrival rate, and depth/width ratio. Moreover, they modeled the parallel movement of shuttles and “transfer car” using a fork-join queuing network.

Thus, Marchet et al. [8] modeled an AVS/RS using a QN approach to quantify the waiting time component of the transaction cycle time. In this case, the selected QN was an OQN because it reduces the effort in the modeling procedure to be implemented and to fulfill the need to minimize the time required in the “conceptualization” phase of an AVS/RS design [20]. The approach followed by Marchet et al. [8] did not impose restrictions on the queue length. This is a strong initial assumption. Eder overcame this assumption in their recent studies [15, 21, 22] by modeling the SBS/RS with a continuous open queuing system with limited capacity. Recently, Kumawat and Roy [23] illustrated an original method for solving multistage SOQNs and validated it using a case study on a multitier shuttle-based compact storage system. Finally, they demonstrated the model accuracy by benchmarking their results with an existing approach in the literature.

QN models for AVS/RS start with the following assumptions, unlike real industrial applications.

  1. 1.

    The arrival and service times follow a Poisson distribution and an exponential distribution (Markov chain basic hypotheses). These parametric functions roughly simplify the real dynamics of arrival and service times. In industrial applications, incoming and outgoing ULs are frequently subject to seasonal trends because of the throughput of production systems producing ULs and demand requests generating retrieval transactions.

  2. 2.

    QN models assume that the queue length is infinite. Therefore, unit loads always wait at the input/output stations for the lift or shuttle. Consequently, the estimation of the maximum throughput of the system can be unrealistic. The shuttle and satellite at each tier are always involved in storage or retrieval transactions to achieve maximum throughput. In the long term, the output buffer or input buffer may be full. Therefore, the shuttle and satellite are forced to stop, and the real throughput of the system decreases.

The literature illustrates several tools and methods for calculating the performance of AVS/RS. Table 1 presents a complete review of the literature by the classification of the most significant contributions according to the features and related options previously mentioned.

Table 1 An overview of the literature on AVS/RS and SBS/RS

A list of the features and related options identified and compared for each group of factors is as follows.

  1. 1.

    Rack configuration. The features that primarily affect the performance of the system are the number of tiers, lane depth, and location and capacity of I/O stations.

    In the food and beverage industry, AVS/RS exploits the relevant vertical development. The performance of the system changes according to the number of tiers. This correlation is not linear. In particular, Marchet et al. [9] developed a simulation model using Arena to analyze the system performance, demonstrating that the maximum throughput does not necessarily correspond to the maximum possible rack height configuration. The lift was the bottleneck of the system in which the configuration had high racks. Therefore, vehicles created a bottleneck for a given storage capacity as the number of tiers was reduced. Consequently, a model that estimates system performance must consider all tiers and not a single-tier configuration. Most studies related to AVS/RS estimate system performance considering a single-tier system [7] or simply by multiplying the performance of a single tier by the number of tiers in the system [15, 21, 22].

    Moreover, the AVS/RS is typically a deep-lane. However, studies on AVS/RS primarily discuss single-deep lanes [2, 8, 16] or double-deep lanes [26, 27]. Few studies have assumed multideep lanes [11, 13]. The lane depth significantly affects the system performance, particularly the storage capacity, space area utilization, vehicle utilization, and system throughput. For instance, Lerher [26] proposed a model to calculate the performance of a double-deep SBS/RS, focusing on cycle time estimation. This study introduced the advantage of the double-deep system, which primarily concerns the reduction in the number of aisles, given the same storage capacity. This is a more efficient use of floor space than that in a single-deep lane system. This result can be extended to multideep lane systems to extrapolate the relationship between lane depth, number of aisles, and system performance. Finally, Manzini et al. [11] studied a multideep AVS/RS. They proposed alternative analytical models for different layout configurations, distinguishing the location of the I/O points and the shape ratio (which varies according to the number of aisles and lane depth).

    As presented by Manzini et al. [11], the location of I/O stations influences the system performance. Most studies on AVS/RS allocate the I/O stations at the first tiers, usually one in front of the other to decongest the access and exit area to the warehouse. Krenczyk et al. [28] compared two simulation environments platforms (FlexSim and GPenSIM) and presented a case study involving an elevator as a part of an SBS/RS. Each tier had input and output locations split in front of the lifting table. The location of I/O stations in the first tier is commonly spread in the real AVS/RS.

    I/O stations are also characterized by the loading capacity, which is the number of ULs in the buffer area waiting for handling devices. The station loading capacity is a physical limit of the system that indirectly affects the system performance. Ignoring it can result in an overestimation of the performance. Typically, studies on AVS/RS do not consider the buffer loading capacity. For instance, Fukunari and Malmborg [4] illustrated a network queuing approach for estimating performance measures. This requires assumptions, including the existence of a steady state and unlimited buffer capacity. Generally, all models based on the QN consider infinite capacities. Few studies have introduced the buffer capacity of I/O stations. In particular, Marchet et al. [9] developed a simulation model to evaluate SBS/RS performance. In the definition of the primary assumption, they limited the maximum number of totes to one UL in the queue at buffer out. This assumption made the retrieval cycle more realistic because each time a vehicle retrieves a tote and goes to the buffer out, it must wait till the buffer is full.

  2. 2.

    Vehicle configuration. The features that influence the system performance are the number of satellites per shuttle and FS option. In AVS/RS, at least one satellite is assigned for each shuttle. Most studies on AVS/RS simplify the system transactions by defining a single vehicle per tier, representing both the shuttle and the satellite. In particular, [15, 21, 22] Eder recently considered the shuttle and satellite as a single vehicle and linked the number of vehicles to the number of tiers. Thus, Lerher [26] studied double-deep AVS/RS considering a single vehicle, called a shuttle carrier, to perform the task along the cross-aisle and within the lanes. Few studies have analyzed different vehicle configurations. For instance, D’Antonio et al. [12, 13] illustrated original analytical models capable of assessing the performance of a tier-to-tier AVS/RS considering an arbitrary number of shuttles and assigning only one satellite per shuttle. One of the contributions of the present study is the comparative analysis between scenarios with an arbitrary number of satellites per shuttle. An AVS/RS with a single vehicle that performs both operations is indirectly an AVS/RS with the NFS. Therefore, the shuttle must wait for the satellite while performing a task within a lane (and vice versa). Similar to the number of satellites, the FS/NFS configuration directly affects the system productivity. Existing studies on AVS/RS rarely consider this option. Some studies considered two vehicles assigned to each tier, one for the handlings along the cross-aisle and one within the lanes. However, they usually work together and expect each other. For instance, Tappia et al. [14] recognized two independent vehicles, the shuttle and the transfer car (i.e., the satellite), but the assumption was that both movements were sequential. Therefore, the two vehicles moved as one. No simultaneous operations were performed. Thus, Marolt et al. [20] considered two vehicles (shuttle and satellite), although they could not move independently from one another. In both cases, this is the NFS option. Recently, Deng et al. [7] modeled a single-tier specialized shuttle-based compact storage system considering a parallel processing policy. The parallel movement of vehicles was modeled using a fork-join queuing network.

  3. 3.

    Vehicle kinematics. The most critical factors in vehicle kinematics are the velocity profile of the lifts, shuttles, and satellites; the type of command cycles that each vehicle can execute; and the vehicle loading capacity. Furthermore, many studies on AVS/RS ignore acceleration and deceleration [4, 5, 7] or assume a constant vehicle velocity [15, 21, 22]. Acceleration and deceleration significantly affect system performance, especially in short-distance routes.

    There are two main types of vehicle routing to perform storage and retrieval transactions: the single command cycle (SCC) and the double command cycle (DCC). In the AVS/RS literature, some studies consider both SCC and DCC, defining a priori a percentage of transactions to execute as SCC and a percentage as DCC. For example, Lerher et al. [17] developed an analytical travel time model to compute cycle times in an AVS/RS system with multiple-tier shuttle vehicles. Other contributions have focused solely on SCC [7, 8, 25]. In particular, Marchet et al. [8] developed an analytical model to estimate AVS/RS performance considering retrieval SCC because retrieval transactions represent the most critical activities from an organizational viewpoint. Some studies have only considered the DCC. In particular, Marolt et al. [20] developed a discrete event simulation of multiple-deep AVS/RS with a tier-captive shuttle carrier capable of performing DCC because the vehicle performed more efficiently: it operated with fewer empty travels than an SCC.

    Finally, the loading capacity of each vehicle is rarely discussed in the literature. Lerher et al. [17] illustrated a multiple-tier AVS/RS equipped with a lift that provided vertical movements. They considered two main lift installations: one and two lifting tables. Deng et al. [7] concluded their study by declaring that future research should investigate the system performance with transactions requiring more than one unit load and considering both single- and dual-command cycles.

  4. 4.

    Dispatching rules. The dispatching rules primarily concern vehicle allocation to S/R transactions, the management of different SKUs, and the storage policy.

    Vehicle allocation to S/R transactions is a feature of tier-to-tier systems (i.e., systems where vehicles can move between tiers) or tier-captive systems with multiple shuttles or multiple satellites.

    Most studies on AVS/RS focused on tier-captive systems, with one vehicle and one satellite per tier. In these systems, S/R transactions are typically performed according to the first-in-first-out (FIFO) policy. Therefore, an assignment rule is not required. Instead, in tier-to-tier systems or tier-captive systems with multishuttles or multisatellites, S/R transactions can be performed by several vehicles. Therefore, an assignment rule is not introduced. This paper presents a rule inspired by a real application, both for the assignment of the satellite to the shuttle and the UL to the shuttle.

    In addition, S/R transactions involve one or more ULs, each of which is characterized by a specific SKU type (i.e., product type). Real AVS/RS manages hundreds of SKU types, and each lane is a mono-SKU. Consequently, the sequence of S/R transactions that handle a specific SKU type can involve the lanes assigned to the SKU type (single SKU lane assignment). Currently, few studies have addressed these topics. D’Antonio and Chiabert [12] and D’Antonio et al. [13] considered four different SKUs in the illustrated case study, and Deng et al. [7] introduced the assumption that each storage lane holds one product. Furthermore, there are no standards available for storage assignment policy. Most studies on AVS/RS adopted a random storage policy [7, 15, 21, 22, 24, 25]. Models based on this storage assignment policy do not consider the real filling of a warehouse. Few studies have focused on this topic. In particular, D’Antonio and Chiabert [12] and D'Antonio et al. [13] introduced three storage criteria: random, closest floor, and closest channel. They compared the performance of these different storage policies by adopting a simulation model that assumed a starting time filling ratio of 50%.

  5. 5.

    Validation. Many studies have validated their models through numerical examples [4, 20] or experimental results [1]. Few studies have translated their numerical applications in real case studies [9]. The application of the proposed models to real AVS/RS or SBS/RS allows the estimation of system performance as realistic as possible.

The analytical-simulative hybrid model proposed in this study overcomes the limits of both analytical and simulative approaches. The analytical approach allows the evaluation of travel time to perform storage or retrieval transactions. The simulative approach aims to estimate the waiting times in agreement with the real trends of incoming ULs and real demand for retrieval transactions (outgoing ULs). This dynamic step, based on simulation, allows the parameterization of the variables of the system. It enables a what-if comparative and competitive multiscenario analysis owing to the parameterization of the variables of the system (e.g., the number of tiers, kinematics of vehicles, and number of satellites). Moreover, this language-based simulation overcomes the assumptions of QN models. In particular, the proposed model follows a data entry where a real AVS/RS inspires the “arrival time” of storage and retrieval transactions. Moreover, the buffer capacity (i.e., queue length) is finite and depends on the rack configuration. The obtained performance, for example, the system throughput, vehicle utilization, and WIP unit loads, is robust and realistic.

3 Methodology

3.1 Data-driven hierarchical approach

This section illustrates the novel adopted approach to model the selected deep-lane and multisatellite AVS/RS according to the evaluation of some critical performance.

This approach is hybrid, that is, mixed analytic and simulative. The aim is to measure multiple performance indicators, such as the throughput and productivity of the entire system and the utilization of each material handling resource (shuttle, satellite, lift, and bay). These performance levels were significantly affected by the cycle waiting times and service times quantified for each vehicle. Many studies have focused on service times without interest in evaluating buffering areas corresponding to the queues of the handling system [11, 16]. In real AVS/RS, the queue time can represent a considerable percentage of the total time spent by each UL within the system [5]. Therefore, queue dynamics should not be neglected. Figure 2 summarizes the proposed hierarchical analytical-simulative hybrid approach to quantify the system performance and compare different system configurations.

Fig. 2
figure 2

The analytical-simulative hybrid approach

As illustrated in Fig. 2, the starting point, which is one of the original contributions of this study, relates to the data entry definition (detailed in Sect. 4), inspired by real AVS/RS applications. The second step is the analytical travel time modeling for data entry service time determination. The third is the simulative time modeling, which focuses on the waiting time determination according to system capacity constraints at the buffering areas. The performance dashboard section details the evaluation of the key performance indicators (KPIs) in a what-if multiscenario environment.

This hybrid approach considers four time contributions to model storage and retrieval transactions:

  1. 1.

    Input lift (output lift) waiting time in storage (retrieval) transactions

  2. 2.

    Idle/waiting of shuttle and satellites

  3. 3.

    Input lift (output lift) service time in storage (retrieval) transactions

  4. 4.

    Service time of the shuttle and satellites to perform the storage or retrieval transaction in the location (x,y,z)

According to the storage and retrieval transaction data entry, the analytical model quantifies the minimum service times for shuttles, satellites, and lifts to perform each task. This time is obtained from applying a heuristic procedure that minimizes the total service time transaction. Subsequently, storage and retrieval transactions are processed by the simulative part of the proposed model, which estimates the waiting times for shuttles, satellites, and lifts. Finally, the model provides a performance dashboard that reports the system’s average performance.

3.2 System configuration and transactions

In an AVS/RS, the cycle time of a generic transaction, throughput of the system, and vehicle utilization depend on the system configuration and the sequence of storage and retrieval tasks. In addition to the previously introduced rack configuration features (see Table 1), the following issues critically influence the system performance, as demonstrated by industrial applications:

  1. 1.

    Number and loading capacity of lifts. This study assumes two lifts: one for storage (LiftS) and one for retrieval (LiftR) transactions. Both simultaneously can move two unit loads (i.e., a double-capacity lift).

  2. 2.

    Number and loading capacity of the bays. This study assumes two bays at each tier, one for input (BayI) and one for output (BayO). Moreover, there are two bays on the ground floor, corresponding to LiftS and LiftR. Each bay can accommodate up to three ULs.

Similarly, concerning the vehicle assumptions, these are the additional features:

  1. 1.

    Shuttle loading capacity. This study assumes one shuttle per tier that can handle up to two ULs simultaneously (i.e., a double-capacity shuttle). Therefore, each storage and retrieval transaction involves two ULs.

  2. 2.

    Satellite loading capacity. This study assumes that at least one satellite is assigned to each shuttle. The satellite can move one UL (i.e., a single-capacity satellite).

The number of free and non-free satellites has rarely been discussed in the literature. Therefore, this study aims to study the impact of the number of satellites on the cycle time, measuring the throughput of the system and vehicle utilization. In particular, the previously introduced FS option allows the shuttle to release the satellite within a lane and perform other tasks, that is, movements, while decreasing idle waiting time. When a satellite goes back and forth within a lane, the shuttle can simultaneously perform operations, minimizing the total time needed to complete the transaction. The possibility of working with free satellites and their number generates the following three alternative scenarios:

  1. 1.

    1NFS, i.e., AVS/RS TC with one NFS per shuttle

  2. 2.

    1FS, i.e., AVS/RS TC with one FS per shuttle

  3. 3.

    2FS, i.e., AVS/RS TC with two FS per shuttle

According to these scenarios and the other assumptions, the sequence of tasks to perform a storage or retrieval transaction can differ significantly. Hence, Table 2 illustrates the tasks to visit two storage locations (SL1 and SL2) at the assigned tier (AT). The ULs come from a production system, for example, a filling and packaging line producing single SKU ULs in the beverage industry.

Table 2 The sequence of tasks to visit the storage locations in the three scenarios

Figure 3 exemplifies the storage activity, illustrated from the explicit task ID reported in Table 2. The (x, z) location of SL1 and SL2 is also represented. The lane is assumed to be a single SKU subject to LIFO unit load handling. The lane depth is equal to 6.

Fig. 3
figure 3

Exemplifying a sequence of tasks for a storage cycle in the three scenarios

Similarly, Table 3 illustrates the tasks to visit the two retrieval locations (RL1, RL2) at the assigned tier (AT) to collect two unit loads (ULs).

Table 3 The sequence of tasks to visit the retrieval locations in the three scenarios

Figure 4 exemplifies the retrieval process for the three alternative scenarios. Each task is related to the explicit task ID reported in Table 3.

Fig. 4
figure 4

Exemplifying a sequence of tasks for a retrieval cycle in the three scenarios

3.3 Free satellite option

The previous subsection illustrates how the sequence of operations changes according to the number of satellites adopted by each shuttle and the FS option. In particular, the examples in Figs. 3 and 4 show that the FS configuration has several implications. The most critical issues are as follows.

  1. 1.

    A generic free satellite can be on its shuttle or within a lane when it does not perform any transaction. If the satellite is not free, it is always on the shuttle when performing any task. Consequently, in the presence of the free option, the shuttle must decide whether to recover a satellite and which satellite recovers in the presence of more than one.

  2. 2.

    The FS option allows shuttles and satellites to perform different operations simultaneously. For example, the shuttle, after releasing the satellite inside a lane to carry out a storage transaction, can go to the input bay and load two new ULs for storage. While performing this task, the satellite completes the previous storage transaction within the lane. The proposed heuristic procedure explores this option to best perform generic transactions.

In practical applications, satellites are not typically used to load the ULs in the input bay. This assumption is maintained in this study. Moreover, the management of simultaneous operations is more complex for retrieval than storage transactions because the shuttle must recover the ULs collected by satellites before going to the output bay. When the shuttle waits for the satellite, it simply rejoins it. However, if it decides to execute another task while the satellite performs the retrieval, it has to postpone the collection of the satellite with the ULs on board.

3.3.1 Next task selection

This subsection illustrates a heuristic procedure to define the sequence of tasks executed by vehicles of a multisatellite AVS/RS according to throughput maximization. The approach is heuristic because of the hard computational complexity of such a sequencing and scheduling decisional problem that involves multiple tasks and multiple vehicles operating in a stochastic environment owing to the proposed data-driven approach inspired by real applications. In particular, the number of alternative options to schedule the following available tasks significantly increases in real applications.

With respect to the shuttle, the choice of whether to wait for the satellite relies on two factors: travel time (1) and availability of the satellite (2). These measures must be continuously evaluated whenever the shuttle has to decide to wait for the satellite because this choice directly impacts the global handling time of generic transactions. Therefore, it is necessary to introduce three analytical time-based equations to support the measurement and monitoring of these two factors to select the best shuttle task to be executed.

Table 4 reports the notation adopted to quantify the following:

  1. 1.

    Travel time. Every time the shuttle releases a satellite into a lane, it can choose whether to perform another operation (e.g., recover another satellite) while the satellite is running a storage (or retrieval) transaction or is in idle time waiting for the satellite. The choice is the result of comparing the satellite waiting time, named twait, with the time the shuttle would take to perform the subsequent operation, tmove. If tmove is lower than twait, the shuttle executes the next transaction. Otherwise, the shuttle waits for the satellite in front of the lane where the satellite is visiting. For example, in the AVS/RS with 2FS described in Fig. 5, shuttle k can wait for satellite n to retrieve the first UL or recover satellite j to perform the second retrieval. The two periods can be evaluated as the sum of different contributions: fixed times (e.g., \({\mathrm{t}}_{\mathrm{coupling}}\)) and variable times affected by the traveling distance according to (x,z) locations, vehicle speed (v), and acceleration (a):

    $$\begin{aligned}t_{move}&=\mathrm{t }\left[\left|{x}_{sh(k)}-{\mathrm{ x}}_{\mathrm{sat}(\mathrm{j})}\right|,{\mathrm{v}}_{\mathrm{sh}\_\mathrm{e}}, {\mathrm{a}}_{\mathrm{sh}\_\mathrm{e}}\right]\\&+ {\mathrm{t}}_{\mathrm{coupling }}+\mathrm{t }\left[\left|{x}_{s\mathrm{at}(\mathrm{j})}-{\mathrm{ x}}_{i+1}\right|,{\mathrm{v}}_{\mathrm{sh}\_\mathrm{e}}, {\mathrm{a}}_{\mathrm{sh}\_\mathrm{e}}\right]\end{aligned}$$
    (1)
    $$\begin{aligned}t_{wait}&=\mathrm{t }\left[{\mathrm{z}}_{\mathrm{i}},{\mathrm{v}}_{\mathrm{sat}\_\mathrm{e}}, {\mathrm{a}}_{\mathrm{sat}\_\mathrm{e}}\right] +{\mathrm{t}}_{\mathrm{collect }}\\&+\mathrm{ t }\left[{\mathrm{z}}_{\mathrm{i}},{\mathrm{v}}_{\mathrm{sat}}, {\mathrm{a}}_{\mathrm{sat}}\right] + {\mathrm{t}}_{\mathrm{coupling}}\end{aligned}$$
    (2)

    where T[Δx,v,a] is the shuttle travel time to achieve the x-location along the cross-aisle, and T[z,v,a] is the satellite travel time to achieve the z-location within the lane.

Table 4 Analytical time models’ notation, Eqs. (1)–(3)
Fig. 5
figure 5

Comparison between the time awaiting the first satellite (twait) and the time to recover another one (tmove)

  1. 2.

    Availability of satellites. The shuttle can retrieve a satellite if it is not involved in another operation. The binary variable Asat(n) measures whether satellite n is available. Satellite n is defined as available if it is free to be loaded by shuttle k when the shuttle k arrives in front of the lane of satellite n.

    $$A_{sat(n)}=\begin{cases}1 \quad if \;t\left[\left|{x}_{sh(k)}-{\mathrm{ x}}_{\mathrm{sat}(\mathrm{n})}\right|,{\mathrm{v}}_{\mathrm{sh}\_\mathrm{e}}, {\mathrm{a}}_{\mathrm{sh}\_\mathrm{e}}\right] \ge {Tfree}_{sat(n)}\\ 0\quad otherwise\end{cases}$$
    (3)

For example, in the AVS/RS with 2FS described in Fig. 5, Asat(j) is 1 if satellite j will be available to be loaded on the shuttle when shuttle k is ready to retrieve it.

The proposed decision-making process for “next task selection” is based on the following steps for storage transactions:

  1. 1.

    Shuttle moved to the input bay to load the two ULs. Meanwhile, it decides whether to retrieve one or two satellites.

  2. 2.

    Shuttle loads the two ULs and retrieves the nearest one if there is no satellite onboard. If it only has one satellite onboard, it decides whether to retrieve another satellite. Finally, it moved to the nearest SL.

  3. 3.

    After releasing satellite into the lane, shuttle decides whether to wait or retrieve another for the subsequent storage transaction.

Similarly, the following is for retrieval transactions:

  1. 1.

    Depending on the number of satellites on board, shuttle can choose to retrieve the nearest one. Finally, it moved to the nearest RL.

  2. 2.

    Shuttle releases satellite in the destination lane (x) and decides whether to wait in RL or move to retrieve another UL.

  3. 3.

    Before going to the output bay, shuttle retrieves satellites with the recovered ULs (unless they are already on board).

These steps reduce the complexity of multisatellite management for both storage and retrieval transactions. The number of alternative options is significantly increased in real applications. For example, in a tier-captive AVS/RS with two free satellites per shuttle, the alternative paths for storage transactions in SCC are 28. For retrieval transactions in SCC, they amount to 20, whereas for transactions in DCC, there are 640 alternative decisional paths. Figure 6 illustrates the decision tree diagram for an SCC of storage and an SCC of retrieval in an AVS/RS with 2FS. The previously introduced three steps are explicitly reported as the 1st, 2nd, and 3rd steps.

Fig. 6
figure 6

Storage and retrieval decision tree diagram (note: blocks with colored background represent operations that can be performed at the same time)

The high level of complexity of this sequencing and scheduling problem requires an original heuristic approach, whose aim is to control the system throughput. Figure 7 illustrates this heuristic procedure to dynamically select the next task for the shuttle and its satellites at the generic tier of an AVS/RS.

Fig. 7
figure 7

A heuristic approach for storage and retrieval transactions with free satellite

4 Analytical-simulative hybrid model

The proposed data-driven hybrid model for designing and controlling a multishuttle AVS/RS is analytical and simulative. In particular, data entry is made of a chronological sequence of storage and retrieval transactions. The generic transaction record refers to the (x,y,z) system location and is expressed as follows:

  1. 1.

    Date and time (e.g., 29/07/2021, 12:00:03)

  2. 2.

    SKU name (for each mission, the type of the two ULs is the same)

  3. 3.

    Tier (yS1/yR1 and yS2/yR2)

  4. 4.

    Lane (xS1/xR1 and xS2/xR2)

  5. 5.

    Storage location (zS1/zR1 and zS2/zR2)

The input file can be generated following a random storage policy or by extrapolating data from a real AVS/RS. Section 6 illustrates how the system performance changes  in line with the origin of the data entry.

According to the transaction arrival time, the model processes the storage and retrieval missions by considering both single and double command cycles. The type of cycle depends on the sequence of the incoming transactions.

Table 5 introduces the notation of the proposed hybrid model.

Table 5 Analytical-simulative hybrid model notation

Section 4.1 illustrates the travel time analytical equations for cycle time determination. Another contribution to cycle time is the result of the application of a dynamic model measuring the waiting times (see Subsect. 4.2).

4.1 Cycle time analytical model

The following equations of motion assume constant acceleration and deceleration for the generic vehicle (i.e., shuttle, satellite, and lift). Two types of velocity profiles can be distinguished depending on whether the obtained velocity peak v(tp) at time tp is less than vmax (type 1) or equal to vmax (type II). For clarity, vmax of the shuttle equals vsh if the shuttle is full; otherwise, it is vsh_e. The vmax of the satellite equals vsat if the satellite is full; otherwise, it is vsat_e. The vmax of the lift equals vlift if the lift is full; otherwise, it is vlift_e. The two velocity profiles are as follows:

  1. 1.

    Type 1: if the obtained peak velocity v(t’p) is less than vmax, the time to reach v(t’p) is tp = \(\frac{v}{a}\) \([s]\), and the distance traveled after the time tp is equal to xp = \(\frac{1}{2}a{t ^{\prime}}_{p}^{2}\)  \([m]\). Consequently, the time spent traveling for the total distance d = 2xp is equal to ttotal = 2 \(\sqrt{\frac{D}{a}}\) [s].

  2. 2.

    Type 2: if the obtained peak velocity v(tp) is equal to vmax, the time to reach v(tp) is equal to tp = \(\frac{v}{a}\) \([s]\), and the distance traveled after time tp is equal to xp = \(\frac{1}{2}a{t}_{p}^{2}\) \([m]\). Consequently, the time spent traveling for the total distance d = 2xp + ∆x is equal to ttotal = 2tp + \(\frac{\Delta x}{v}\) [s].

The velocity profiles are illustrated in Fig. 8:

Fig. 8
figure 8

Velocity profiles

The motion equations depend on velocity (v), acceleration (a), and distance (d) traveled. Therefore, the time contribution (t) to perform each task is expressed considering these three elements: t[d, v, a].

The time contributions shown for storage transactions in Table 6 and for retrieval in Table 7 are effective for the AVS/RS system with 1NFS. In scenarios with one or two free satellites, the sequence of operations can change. We decided not to illustrate these scenarios.

Table 6 Storage travel time in an AVS/RS with 1NFS
Table 7 Retrieval travel time in an AVS/RS with 1NFS

4.2 Time-dependent simulative model

The proposed hybrid approach requires a simulation model to analyze the interactions between the different entities of the system (i.e., shuttles, satellites, and lifts) and quantify waiting times and the number of items in the queues. The simulation model is a discrete event simulation based on a MATLAB routine. Figure 9 illustrates the simulation model adopting a notation from the queueing network theory.

Fig. 9
figure 9

The time-dependent simulation model

The simulation is powered by the data entry inspired by the real AVS/RS system. Storage and retrieval transactions are ordered chronologically and dispatched among the tiers (in number). The simulation is time-driven. Therefore, the transactions arrive at the system according to the arrival time declared in the data entry.

Storage transactions (S) arrive at the interface with the climb elevator (node lift-up in Fig. 9), waiting for the resource in queue Qs. Each storage transaction is composed of one or two items that need to be brought to the assigned tier (AT); if the items have two different ATs, the elevator stops at the nearest one and then moves to the other AT. The lift-up waits for the following storage request in the QLUp queue, whereas the items wait for the shuttle in the queue QSRi at tier i.

The retrieval transactions (R) arrive directly to tier i (e.g., R1 at tier 1), waiting for the resource in queue QSRi. Each retrieval transaction is composed of one or two items that need to be collected. At each tier, the storage and retrieval transactions are processed by shuttles and satellites. Every time the resource turns free, another transaction can be performed. For retrieval transactions, after being processed by the shuttle and satellite, the items wait for the elevator (node lift-down in Fig. 9) in queue QR. When the lift-down is free, it moves to the tier of the retrieval request, in agreement with the FIFO policy, and simultaneously loads one or two unit loads. Then, it moves to the ground floor and downloads the items.

The service times of lift, shuttle, and satellite for each storage and retrieval transaction are provided by the analytical model previously described according to the proposed mixed analytical and simulative approach. Therefore, the results generated by the simulation model vary according to the configuration selected for the analytical model (i.e., 1NFS, 1FS, and 2FS).

5 Case study

This section presents the results of the application of the proposed analytical-simulative hybrid model to aid the design of a new AVS/RS system. This case study was inspired by a real application in the beverage industry.

What is the number of satellites and which free satellite option best performs the system throughput? The proposed approach is suitable for addressing this challenge in a comparative and competitive multiscenario analysis. Table 8 summarizes the features and technological constraints in 1NFS, 1FS, and 2FS. The resulting storage capacity of the system is 6080 unit loads (i.e., {32 [lane/dx] * 22 [UL/lane] + 32 [lane/sx] * 16 [UL/lane]} * 5 [tier]).

Table 8 Features and technological constraints

For clarity, the layout of the multideep AVS/RS proposed in this case study is reported in Fig. 10.

Fig. 10
figure 10

a AVS/RS front view, b AVS/RS plan view

5.1 Analysis 1: real data entry

The data entry selected for this analysis is a list of chronologically ordered storage and retrieval historical transactions for an existing unit load storage system made of five tiers. The following five features characterize generic transactions:

  1. 1.

    Arrival time that defines the sequence of transactions

  2. 2.

    Transaction type (storage or retrieval)

  3. 3.

    y-level assigned to the transaction

  4. 4.

    x-lane assigned to the transaction

  5. 5.

    z-storage location (z) where the UL are collected or dropped

The real data entry counts 23,662 storages and 25,976 retrievals corresponding to a horizon time of 1 month. The number of SKUs was 140.

The proposed hybrid model processes the storage and retrieval transactions following this data entry and quantifies several KPIs. Table 9 summarizes some relevant KPIs such as the average service time (service), average waiting time (waiting), and impact of waiting time on total time (% wait) for a storage or retrieval transaction. Values are reported for each tier of the AVS/RS and each configuration (1NFS, 1FS, and 2FS). The temporal contribution of the lift was not reported because it did not change according to the selected system configuration. Therefore, it does not directly influence the system performance at tier.

Table 9 Average service times and waiting times of shuttle and satellite/s for storage and retrieval tasks

The comparison between the three scenarios shows that introducing the “free option” and increasing the number of satellites minimize service and waiting times. In 1FS configuration, the average service time required by the shuttle and the satellite to perform the operations is approximately 10% lower for storage and retrieval tasks than the 1NFS configuration. In addition, if the number of FS increases to two (2FS), the average service time decreases by 15% compared to 1NFS and by 6% compared to 1FS.

Thus, the waiting time and impact on the total time also decreased from the 1NFS to the 2FS configuration. The average waiting time of configuration 2FS decreases by 26% compared to the 1NFS configuration and by 21% compared to the 1FS configuration. In general, the impact of waiting time on total time is significant, depending on the data entry. This demonstrates the effectiveness of the proposed hybrid approach that does not assume random arrival times and random storage locations.

The previous observations were related to the average values. The proposed model allows data collection on the distribution of service and waiting times for all processed storage and retrieval transactions. Tables 10 and 11 report the distributions of the following:

  1. 1.

    Service time: the time required by the shuttle and satellite to perform a storage or retrieval transaction.

  2. 2.

    Waiting time: the waiting time for a storage (retrieval) transaction in the input buffer at the tier (in the location within the lane).

  3. 3.

    Throughput time: the total time required to perform a storage (retrieval) transaction. For storage transactions, it is the time interval between the UL arriving at the input buffer of the lift-up and the UL being dropped into the storage location. For retrieval transactions, it is the time interval between the UL being collected and downloaded in the output bay on the ground floor.

Table 10 Distribution of times for storage transactions
Table 11 Distribution of times for retrieval transactions

The proposed model quantifies the average number of items in the generic queue. Table 12 presents the distribution of ULs at the interface with the input lift (LiftS), at the input bay of each tier (Tier), and at the interface with the output lift (LiftR). The number of items varies in a range of 0–3 ULs, and it is reported for the three configurations selected (1NFS, 1FS, and 2FS).

Table 12 Distribution of ULs at lift-up, tier, and lift-down, according to the three scenarios

Table 12 demonstrates that the bottleneck in the system is the capacity of the buffer located at the point of output in each tier, which is typical of such a storage system. The column “LiftR” illustrates how the percentage related to the probability of having 0 UL in the output buffer decreases by 15% (from 72 to 57%) in the configuration with 2FS compared with 1NFS. By increasing shuttle and satellite performance on the tier, the output buffer fills up faster. The output buffer has a finite capacity due to the physical limits of the warehouse. Consequently, a performance improvement of shuttle and satellite handling positively affects the system throughput on one hand and generates bottlenecks on the other. It is essential to control bottlenecks and throughput simultaneously as in real operating conditions. Typically, production systems produce large batches of single SKU ULs, located in dedicated and homogeneous lanes. Retrieval transactions have to be executed as quickly as possible to guarantee high levels of customer service. The storage and retrieval transactions sequence is variable with a day, a week, a month, and a year.

The proposed hybrid and data-driven approach allows the time spent by each vehicle moving back and forth within the warehouse and the idle times to be tracked. Table 13 illustrates the utilization of the input lift (LiftS), shuttle and satellite (tier 1–tier 5), and the output lift (LiftR) according to the free/not-free option and number of satellites.

Table 13 Vehicle utilization

The utilization of LiftS and LiftR is lower than those of the shuttle and satellite. This result supports the previous statement regarding the output buffer, which is declared as the critical queue in this system.

In conclusion, the model suggests that the 2FS configuration minimizes the service and waiting times and the number of items in the queue. However, this solution also generates the worst utilization for shuttles and satellites. Finally, the system throughput amounts to 33 ULs per hour, and it depends on the arrival rate of the data entry. In particular, the system throughput is the same for the three scenarios (1NFS, 1FS, and 2FS) because of the incoming sequence and timing of transactions.

An original contribution of this study is the data entry inspired by a real AVS/RS. Therefore, storage and retrieval tasks follow the trends of production lines and shipments. The following subsections illustrate the impact of different data entries on the system performance. In particular, Subsection 5.2 illustrates the adoption of a random storage assignment policy (Analysis 2). Subsection 5.3 quantifies the maximum throughput of the system (Analysis 3). Both analyses assumed the same sequence of transactions adopted in Analysis 1 and came from real applications.

5.2 Analysis 2: random storage assignment

This analysis reports some relevant KPIs obtained starting from a new data entry where the level and lane assigned to each transaction are randomly generated. The storage locations (z) follow the dynamic filling of the lane according to the LIFO policy. The sequence and number of storage and retrieval transactions are the same of the data entry previously discussed (real case study, named “Seq_Time_xyz”). This new data entry is named “Seq_Time_Random.” Table 14 reports the results in terms of the average service times and average waiting times for scenarios 1NFS, 1FS, and 2FS.

Table 14 Comparison between Seq_Time_Random and Seq_Time_xyz data entry

Figure 11 illustrates the percentage deviation between the average service time and the average waiting time to perform a storage and a retrieval transaction according to the two data entries. The values are referred to Seq_Time_xyz data entry.

Fig. 11
figure 11

Percentage deviation of average values between Seq_Time_Random and Seq_Time_xyz scenarios

In the 2FS configuration, the service time generated by the Seq_Time_xyz data entry for storage transactions is 23.2% lower than that obtained by the Seq_Time_Random data entry. Thus, the waiting times are also 25.2% lower. The main reason is that Seq_Time_xyz data entry follows a storage policy that favors locations close to each other for unit loads that belong to the same production batch. While the first satellite is within a lane (z-direction) to drop a UL, the shuttle moves to the lane of the second UL (x-direction) and releases the second satellite to perform another task (z-direction). The total service time includes all the temporal contributions along the z-direction and the ones along the x-direction. The storage policy directly influences the contributions along the x-direction, whereas the contributions along the z-direction depend on the dynamic filling of the lanes. Therefore, the two data entries generate comparable contributions along the z-direction, whereas the contributions along the x-direction are different. Consequently, if the Seq_Time_xyz data entry favors locations close to each other, the service and waiting times are significantly lower than those obtained with the Seq_Time_Random data entry due to the temporal contributions along the x-direction.

In retrieval transactions, the difference between service times amounts to 7%. These transactions follow customer demand (characterized by a variable product variety), requiring different unit loads located in random lanes. Seq_Time_Random data entry is similar to the Seq_Time_xyz data entry for retrieval transactions. Therefore, the difference between the two service times is lower than for storage.

Finally, Fig. 11 shows that the gap between service times is more relevant for the 2FS configuration than for 1NSF and 1FS. In the 1NSF and 1FS configurations, when the satellite performs a task inside the first lane, the shuttle must wait before moving to the second lane. In the 2FS configuration, the temporal contributions along the z-direction can be reduced because different tasks can be performed simultaneously. Consequently, the effect of the temporal contribution along the x-direction on the total time is lower for 1NSF and 1FS than for 2FS. In conclusion, even if the Seq_Time_xyz data entry favors lanes close to each other for storage transactions, this temporal reduction has a minor effect on the total time.

Existing literature studies did not address these important issues, further demonstrating the effectiveness of the proposed hybrid approach.

5.3 Analysis 3: maximum system throughput

The data entry named Seq_Time_xyz generates a system throughput of 33 ULs per hour in all scenarios (1NFS, 1FS, and 2FS). This section illustrates how system performance changes according to different arrival times, given the same number and type of storage and retrieval transactions (i.e., 23,662 storages and 25,976 retrievals). In particular, we assumed the same arrival time for each UL, strictly respecting the sequence of transactions and incoming/outgoing SKU. Therefore, the transactions executed in Analyses 1 and 2 are now processed by the system according to a push–pull policy, i.e., incoming ULs are pushed and outgoing ULs are pulled respecting the original sequence of transactions. The first application of this push–pull policy estimates the so-called minimum arrival time for each transaction and releases a list of new arrival times. The “minimum arrival time” is the time when the transaction can arrive and be hosted by the system without saturating the input and output buffers. The maximum capacity of each buffer is a parametric value. In this analysis, it was set to three (inspired by a real case study). The new Seq_Time_xyz data entry reports all chronologically sorted transactions according to new arrival times.

The system performance can be estimated by applying the proposed model to new data entry. The obtained time to complete all transactions is now 284 h for the 1NSF configuration, 259 h for the 1FS configuration, and 227 h for the 2FS configuration. The time to complete all transactions decreases by increasing the number of satellites and in the presence of the free option. The average service times of the shuttle, satellite, and lift did not change.

Another observation from Analysis 3 is that arrival times have no impact on service times. Waiting times and UL distribution in the buffers change according to the new arrival times, which are assumed to be in line with the push–pull policy.

Table 15 illustrates the distribution of ULs at the interface with the input lift (LiftS), at the input bay of each tier (Tier), and at the interface with the output lift (LiftR). Both the number of items in the queues (with the related probabilities) of Analysis 1 (named A1) and Analysis 3 (named A3) are reported for each buffer.

Table 15 Comparison between the distribution of ULs at lift-up, tier, and lift-down of the Seq_Time_xyz and Seq_Time_Random data entry

Table 15 illustrates how the buffer saturation increases when the time interval between one transaction and the next decreases. Moreover, Table 16 shows how also vehicle utilization increases.

Table 16 The utilization of the Seq_Time_Random data entry

The highest level of utilization is for shuttle one. Nevertheless, shuttles never reach 100% because the transaction arrival rates are set to never exceed buffer capacities. The utilization reaches 100% if buffer capacity is ignored, confirming that the shuttle is the bottleneck of the system. Thus, the system throughput also changes according to the configuration and the possibility of considering buffers capacity (named BC). Table 17 illustrates how the system throughput changes according to these two hypotheses (BC Yes/No).

Table 17 Throughput variation according to buffer capacities, following the Seq_Time_Random data entry

This analysis demonstrates that buffer capacity significantly affects system performance. In 1NSF and 1FS configurations, the throughputs are 24% lower than those that do not consider buffer capacity (BC: No). Moreover, the throughput of the 2FS configuration decreases by 30% compared with the same configuration that does not consider buffers capacity.

In conclusion, scenario 2FS guarantees the maximum throughput, considering both the buffer capacity and the lower utilization. A fourth scenario, with three free satellites (3SF), was tested to identify the maximum throughput of the system. The throughput of the system does not change compared to that of the 2FS configuration and is equal to 217 ULs per hour. Therefore, introducing an additional satellite (i.e., more than two per shuttle) does not increase the system performance. This result refers to a specific case study. However, the proposed hybrid approach of modeling gives the decision maker the opportunity to best design and configure any AVS/RS control and best performing the performance in coherence with real operating conditions.

6 Conclusions and further research

This study introduces an original data-driven hybrid approach for the design and control of an AVS/RS based on analytical and simulative models, multiple performance indicators (e.g., vehicle utilization, system throughput, service and waiting times of S/R transactions), real data entry (with realistic sequence and timing of S/R transactions, dispatching rules, storage policies, etc.), dynamic filling of the lane with homogeneous unit loads (single SKU of the same production batch), and free and not-free multiple satellites working with shuttles operating at different tiers. This approach attempts to solve the limits of traditional models and assumptions, producing useful results for real applications.

The proposed hybrid model is applied to a real case study involving three analyses based on different assumptions:

  1. 1.

    Analysis 1: number and typology (free and not free) of satellites. It assumes the real arrival time and sequence of storage and retrieval transactions according to the production rate of the filling beverage machine and customer demand. This analysis demonstrates the effectiveness of the proposed hybrid model that quantifies the service time, waiting time, and throughput time for each transaction (1); the time-varying number of ULs at the input/output lift interfaces and tier input bay (2); and vehicle utilization (3). Moreover, it identifies the system bottlenecks, demonstrating the importance of buffer capacity. This data-driven approach is necessary to configure an AVS/RS to control system performance.

  2. 2.

    Analysis 2: random storage assignment. The literature frequently adopts a random storage policy, i.e., given a storage transaction, the selection of the lane in the x-direction is random. In real applications, it is necessary to fill the generic lane according to the single SKU and production batch constraints that are rarely discussed by existing studies, especially for many SKUs. This analysis demonstrates that storage assignment significantly affects the system performance, and that the proposed data-driven and hybrid approach is effective.

  3. 3.

    Analysis 3: maximum system throughput. The proposed hybrid approach quantifies the maximum system throughput. The time to complete all transactions decreases by increasing the number of satellites and adopting the free option. The average service times of the shuttle, satellite, and lift did not change. The level of generic buffer capacity significantly affects system throughput. Finally, introducing more than two satellites did not increase the productivity of the system.

The sequence and timing of storage and retrieval transactions significantly affect the system performance. Any theoretical assumption on storage policy (e.g., random storage policy), arrival times (e.g., Poisson distribution of arrival times), and service times (e.g., exponential distribution of service times) is not acceptable. This general result makes it necessary to combine the proposed data-driven approach with analytical and dynamic models to realistically support the design and control of deep-lane multisatellite AVS/RS.

Further research on the application of this hybrid model to different system configurations (e.g., layout, lane depths, number and location of lifts, and vehicle UL capacity) and applications (i.e., case studies coming from different sectors) is required to support the technological development of new vehicles. New studies concerning the space efficiency control and maximization combined with system throughput analysis and according with different system configuration, equipment, and S/R policies are achieved.