# Fixed-Route vs. Demand-Responsive Transport Feeder Services: An Exploratory Study Using an Agent-Based Model

Authors: Giovanni Calabrò; Michela Le Pira; Nadia Giuffrida; Giuseppe Inturri; Matteo Ignaccolo; Gonçalo H. de A. Correia
Journal: Journal of Advanced Transportation
 (2022)

---

## Abstract

Feeder transport services are fundamental as first and last-mile connectors of mass rapid transit (MRT). They are especially beneficial in low-demand areas where private transport is usually the main transport mode. Besides, the rapid spread of new technologies such as vehicle automation and the shared mobility paradigm gave rise to new mobility-on-demand modes that can dynamically match demand with service supply. In this context, the new generation of real-time demand-responsive transport services can act as on-demand feeders of MRT, but their performance needs to be compared with conventional fixed-route fixed-schedule feeders. This article aims at presenting an agent-based model able to simulate different feeder services and explore the conditions that make a demand-responsive feeder (DRF) service more or less attractive than a fixed-route fixed-schedule feeder (FRF). The parametric simulation environment creates realistic constraints and parameters that are usually not included in analytical models because of high computational complexity. First, we identified the critical demand density representing a switching point between the two services. Once the demand density is fixed, exploratory scenarios are tested by changing the demand spatial distribution and patterns, service area, and service configurations. Main results suggest that the DRF is to be preferred when the demand is spatially concentrated close to the MRT station (e.g., in a TOD-like land-use area) or when station spacing is quite high (e.g., a regional railway service), whereas the FRF performs better when the demand is mainly originated at the MRT station to any other destinations in the service area (e.g., during peak hours). Besides, automated vehicles could play a role in reducing the operator cost if the service is performed with many small vehicles rather than higher-capacity vehicles, even if this would not imply a major benefit gain for the users.


---

## Body

## 1. Introduction

Transport systems are experiencing times of unprecedented changes. The push towards sustainable mobility and the advances in technology are changing both transport services and user habits [1]. Besides, the COVID-19 outbreak has heavily hit public transport (PT) and influenced travel behaviour with expected long-lasting impacts, especially at the urban level. In this changing environment, good planning and designing of transport systems become increasingly important to shape the future of urban regions [2]. Transport planning cannot ignore new trends and paradigms that are rapidly emerging, oriented towards the concept of sharing assets and services via on-demand services enabled by digital platforms. Mobility as a Service (MaaS) is one good example of such a new concept, being a digital platform enabling multimodal door-to-door trips via a single app that should aim at reducing private car usage (and eventually ownership) [3]. To achieve this goal, PT is considered to be the backbone of MaaS, complemented by mobility on-demand and shared modes [4].In this context, demand-responsive transport (DRT) can play a fundamental role. Despite being an old concept that goes back as far as the end of the 90s as “an intermediate form of PT, somewhere between a regular service route that uses small low floor buses and variably routed, highly personalised transport services offered by taxis” [5], it came back in the limelight in recent years mainly due to the spread of app-based ride-sharing systems such as Uber, Via, and Lyft (also known as transportation network companies).However, the performance of these systems is often questioned especially concerning the transport demand they are meant to cover, the characteristics of the area, the topology of the road network in which they should operate, and the level of flexibility of the routes they follow. While they are often in competition with PT in the case of densely populated urban areas, they can potentially constitute a good solution to improve the accessibility to mass transit systems in the case of low-demand areas by covering the first-last mile of passenger PT trips [6]. The EU highlights how sparsely populated and underpopulated regions suffer from several structural problems such as lack of transport connections, few job opportunities, and inadequate social services [6]. In a recent publication by the European Parliament [7], the lack of accessibility to PT is considered one of the main issues faced by low-density and depopulated areas, with the consequent social exclusion of their inhabitants [8]. The strategic document underlines the role that DRT enabled by novel technologies could have in those regions as a result of its flexibility in meeting the demand. The document also notes that particular attention should be paid to its use in supplementing conventional PT such as train, metro, and trams that cannot reach all regions with the same coverage.The conditions for DRT success have been explored in the literature focusing on some of the key aspects for PT system viability, for example, the demand patterns making DRT services more attractive than fixed scheduled ones [9], optimal fleet size [10], and fleet composition [11]. Currie and Fournier [12] showed that, statistically, high service costs are a major failure factor for DRT systems and that simpler operations (e.g., many-to-few or many-to-one, where ridership is concentrated at one of the two trip ends or close to it) had lower failure rates compared to more complex, difficult to manage, many-to-many service types. The use of DRT as a feeder of PT has the double advantage of serving the commuting demand of suburban areas and enhancing the ridership of PT, that is, ensuring at the same time wide coverage and high ridership at the expense of increasing the number of transfers (e.g., from bus to mass rapid transit (MRT)). Wang et al. [9] found that poor accessibility to PT fosters the introduction of DRT services to cover long-distance trips. Besides, accessibility, safety, and comfort-related indicators should be considered to evaluate the satisfaction of PT users [13–15]. Real case studies (or pilots) involving DRT operations have been set up and investigated in the literature. However, they are inevitably influenced by the territorial context where they happen leading to results that are often difficult to generalize and thus transfer to other regions (e.g., [16, 17]). Analytical models have been typically used to find demand thresholds and switching points from one service to the other, as in, for example, the work by Quadrifoglio and Li [18].Moreover, while the routing of these systems has long been addressed in the literature [19–21], the recent technological innovations in the trip booking processes have led to the emergence of new problems due to the need to guarantee dispatching of vehicles and requests in real time. These issues are amplified in the case of shared rides since different users might have different time schedules.Finally, any analysis of these systems cannot ignore the technological evolution of the vehicles used. These seem to be oriented towards the conversion to full-electric ones and in the longer run to full automation [22].Based on these premises, this article aims at proposing the use of an agent-based model (ABM) to explore the performances of DRT in comparison with a fixed-route service as a feeder to mass transit. The authors began to address this issue in Calabrò et al. [23] by presenting and applying a new ABM to simulate adaptive flexible/fixed feeder services in a low-demand urban area in Catania (Italy). In this article, we upgrade the model also to verify current analytical models that aim at distinguishing DRT from fixed services [18]. Moreover, we extend such models introducing a nonuniform demand density and a variable vehicle capacity.Our work tries to answer the two following research questions: how can flexible demand-responsive feeder transport services effectively match the demand with the supply in real time, aiming at maximizing shareability, minimizing the operator costs, and limiting passenger travel time? And under which conditions is it more convenient to adopt a fixed-route policy rather than a flexible one in providing feeder services towards mass rapid transit? In the process, we address several open research issues: (i) the transferability to different contexts by introducing a parametric design model; (ii) the booking process, by taking into account user-based time constraints in the dispatching algorithm; and (iii) the possibility to perform the service with automated vehicles, considering the impact they could have especially in terms of the operator cost.The remainder of the article is organized as follows. The following section summarizes the literature on the DRT topic and highlights the current research gaps to be filled by this work. Section3 presents the methodology, drawing an overview of the model with the dispatching algorithm and the selected output indicators. The model is then applied to a synthetic parametric application case, and the results for different scenarios are presented in Section 4. Finally, conclusions and discussion and future research are proposed in Section 5.


## 2. Literature Review

DRT planning and design has been addressed in literature mainly since the beginning of the 2000s (e.g., [24, 25]). A fair number of analytical models have been developed to face strategic planning decisions. In 2004, Diana and Dessouky [26] addressed the dial-a-ride problem with time windows introducing a new regret insertion heuristic able to face a large number of requests and outperform classical heuristics when a high-quality service (narrow time windows) is provided to the users. However, a door-to-door transport policy is assumed, while more trip shareability and travel time savings could be achieved by aggregating requests in virtual stops even if passengers would have to walk a short distance. Later in 2007, Quadrifoglio et al. [27] proposed an insertion heuristic for flexible services that merge the flexibility of DRT systems with the low-cost operation of fixed-route ones; the proposed service covers a specific geographic zone, with mandatory checkpoints located at major connection points or high-density demand zones. However, the model assumes that customers never reject the insertion proposed by the algorithm, so there is no negotiation phase between the system and the customers. In 2009, Quadrifoglio and Li [18] proposed a continuous approximation approach to compare the user-related performance of two operating strategies for a feeder bus service: fixed-route and demand-responsive. They provided approximate analytical solutions to estimate the critical demand density that allows a transit agency to switch between the two types of services. Chandra and Quadrifoglio [28] extended this model [18], using a gravity-based accessibility model to evaluate the accessibility impacts for first-/last-mile transport connectivity in the case of fixed-route transit and DRT, although using the same uniform demand across space. Other issues investigated through analytical models were fleet sizing based on a given quality of service for users [10], route design [20, 29], and the choice between different flexible transit strategies to accommodate a variable demand level [30], or estimating how user and operator costs vary according to the demand density, the service area [31], and the fleet size [32].Analytical models can be considered design models that provide optimal solutions among infinite alternatives, thanks to introducing some approximations and simplifications within the model; such models are in general not capable of reproducing a complex reality without requiring enormous computation times; otherwise, it might be impossible to solve them analytically. In contrast, simulation models are ideal for reproducing the complexity of a system; once the input parameters are set, the simulation model runs a series of operations to the data whose number usually grows linearly with the size of the problem and can then generate several outputs, which can be used as key performance indicators of the system. In this respect, simulation models have been used extensively for making tactical and operational decisions regarding transport services in general and in particular for flexible transport services and last-mile connection [22, 33–36]. Winter et al. [11] designed, simulated, and tested an automated DRT for a campus-train station service; the simulation determined the optimal fleet size for the operation of the service and results showed the importance of adequate vehicle sizes and short vehicle dwell times. Scheltes and Correia [37] explored the use of automated vehicles as last-mile connection of train trips using an ABM. The ABM incorporated a dispatching algorithm distributing travel requests among the available vehicles using a first-come-first-serve sequence. However, the type of service that was tested was conceived as being individual; therefore, it did not allow for shared trips among the passengers. Araldo et al. [38] studied the impact of consolidating the demand and limiting the density of waypoints locations through a modular simulation platform, searching for a trade-off between guaranteeing high quality of service for the users and providing a high-efficiency system; the model simulated different flexibility levels from door-to-door to bus-like services. Oh et al. [39] proposed an agent-based simulation framework to evaluate the performance of an automated demand-responsive transit system as a complement and/or substitute to conventional mass transit. Their model suggests advantages in using higher-capacity vehicles rather than taxis, resulting in less travelled kilometres for the operator and less congestion. Fielbaum et al. [40] abandoned the door-to-door scheme showing that significant reductions in the vehicle-hours travelled and in the number of rejections can be achieved by asking travellers to walk a short distance to reach the assigned pick-up/drop-off points. They proposed an insertion heuristic algorithm that encompasses and weighs both the travellers and the operator costs. The simulation was performed both on a toy grid network and the real case study of Manhattan. However, they considered neither the integration with PT nor a comparison with other forms of PT. In 2019, Inturri et al. [41] developed an ABM to compare the performance of a shared DRT with that of a taxi service [42] both for low-demand areas and for fast-growing cities [43]. The results showed that DRT shared services are convenient under specific demand patterns for the analysed case studies. Based on these studies, Calabrò et al. [44] presented an ABM tailored to solve the last-mile problem of MRT in low-demand areas, identifying optimal routes of feeder services.Literature analysis shows that simulation models are not meant to provide optimal service design; they provide a good description of the performance of the system under specifically designed scenarios. Nevertheless, if the number of combinations between relevant parameters is not great and the simulation run time is not too long, it is possible to search the different configurations space in search for solutions that maximize or minimize a certain key performance indicator.In this article, we present an ABM, intending to integrate the benefits of the two methods: the model uses the simulation approach but on an ideal parameterizable environment so that the results are as scalable as possible. Based on [18, 23], the new ABM goes beyond a pure analytic model by proposing realistic and real-time dispatching algorithms, but without being tied to a specific simulation network neither to a particular case study, so its results are easily adaptable to other contexts using the main experimental parameters.


## 3. Methodology

Our research focuses on the first- and last-mile leg of PT trips, supposing that the PT backbone is a MRT network like rail or bus rapid transit (BRT). The transit agency might choose between the following two operational strategies:(1)
A fixed-route feeder (FRF) service carried out by buses that pick-up and drop-off passengers at predetermined stops(2)
A demand-responsive feeder (DRF) service, where each vehicle builds customized routes to serve a group of passengers.In our model, we assume that PT users choose between walking and using the feeder service to reach the MRT station. Although bikes and scooters (private or shared) can also be regarded as competitors to the proposed feeder system, we chose not to consider them in this first version of the model. In fact, we are interested in comparing the performance of FRF and DRF under different operating contexts, assuming that users have already chosen to use the bus as access/egress mode. Starting from this, the reliability of the two operational strategies should be considered the same, assuming an ideal scenario where all passengers are perfectly aware of the status of the system (e.g., real-time information sharing and no digital divide).


### 3.1. Overview of the Model

The main components of the simulation model are the service type (FRF or DRF), the geometric features of the service area, the demand model, the supply (vehicle) characteristics, and the simulation duration. The agents of the model are the travellers requesting a ride and the vehicles.We consider that our feeder service operates in a rectangular area of lengthL from the terminal station (horizontal direction) and width W (vertical direction). The mobility demand follows a many-to-one/one-to-many pattern since the focus is on the first/last leg of an entire PT multimodal trip. A trip request can therefore have either origin or destination at the MRT station (the terminal), located on the left side of the service region. The value of W can be considered the average distance between the terminal and the MRT stations upstream and downstream. Hereinafter, we will refer to the passengers originating at the terminal as egress passengers, while the passengers having destination at the terminal will be referred to as access passengers.From a spatial perspective, the base demand densityλ (in trips/km2h) is modelled as a linear function of the horizontal distance x from the terminal that is analytically derived in Appendix A. By varying the slope of the demand decay function, we reproduce different types of urban density and land use.Each trip requesti involves a group of a number Gi of travellers. We assume that Gi follows a geometric distribution. If we denote with p1 the probability that request i consists of a single user (PrGi=1); therefore, the probability that the group is constituted by k users is given by(1)PrGi=k=pk=p11−p1k−1.If the Manhattan distance (i.e., the distance measured along axes at right angles)dT,i between the user’s origin and the MRT station (access leg) or the MRT station and the destination (egress leg) is lower than a minimum threshold d0, a user is assumed to walk directly to/from the station. Otherwise, the probability of choosing the feeder service rapidly increases with dT,i and is given by the attractiveness coefficient η ∈ [0, 1] we introduced as follows:(2)η=1−e−0.5dT,i−d02/γ2,where γ is a parameter that rules the increase in attractivity of the feeder service due to the distance from the station: the lower the value of γ, the higher the speed at which η increases with dT,i. Figure 1 shows a graphical representation of η across the service area.Figure 1
Values of the attractiveness coefficient across a service area withL = 2.4 km and W = 1.2 km. In this example, we set γ = d0 = 0.3 km. From a temporal point of view, the demand follows a Poisson process with λ as the rate parameter.As in [18], the fraction of trips having the MRT station as the destination is given by the parameter α ∈ [0, 1], so the proportion of users going from the station to a destination inside the service area is (1−α). Although the Poisson process is well suited for the former, the temporal distribution of the egress passengers is strongly related to the schedule of the MRT line. However, assuming that the headway of the MRT line is small enough (i.e., less than 5 minutes) in both directions, we believe that the Poisson distribution with rate parameter λ is a reasonable approximation and should marginally affect the results.Regarding the supply side, the vehicles (buses, minibuses, vans, or automobiles) are defined by three input parameters: the number of vehiclesnV composing the fleet, the cruising speed v, and the allowed capacity in available seats in each vehicle cap.Finally, the duration of the simulationST, in which the input parameters are unchanged, should be sufficiently high to ensure that the steady state is reached and that the results are marginally affected by the warm-up period.


### 3.2. The Fixed-Route Feeder

The FRF (Figure2) runs back and forth on a straight line from the MRT station to the farthest bus stop, with spacing ds (input parameter) between the stops.Figure 2
Scheme of the FRF service: users in black are about to take the bus, users in grey got off the bus, and the user in blue is walking directly to the terminal.Assuming ideal conditions (no congestion or other disturbance to the service), the maximum cycle timeCTmax, that is, the time needed for a vehicle (bus) to complete the round trip, is the sum of two components (adapted from [18]), which is given as(3)CTmax=2L−ds/2v+2Lds−1⋅τs+τp,where the first component is the ratio between the length of a complete cycle and the bus cruising speed v, and the second one estimates the dwell time at each stop τs, including the time of acceleration and braking, and the additional dwell time due to boarding/alighting passengers τp.The headway between two vehicles is given by(4)h=CTmax+τtnV,where τt is the minimum dwell time required at the terminal.Egress passengers originate at the MRT station, take the bus with the earliest departure time, alight at the desired stop (i.e., the closest one to the destination of the trip) during the first half of the cycle, and walk to their final destination.Access passengers originate in the service area, walk to the closest stop, wait for the first bus headed to the terminal, travel onboard, and finally alight at the MRT station.We assume that a traveller is aware of the expected waiting time at the stop thanks to a real-time information system by the feeder service provider. Therefore, if the expected waiting time is above a certain maximum waiting timetw,max (input parameter), traveller i assumes the status “rejected” and walks to the station. Instead, if the overall travel time overcomes the latest drop-off time interval at the station ldi, the passenger assumes the status of “delayed.” This threshold varies according to the different time tolerance of the users, as shown in the following equation:(5)ldi=mintw,max+1+δi+γidT,iv,1+γidT,ivp,where δi=dT,i/L+W/2 relates the travellers’ distance to the maximum one to reach the terminal (based on the farthest user that could be generated in the service area) and represents the willingness to deviate from the shortest path based on his/her distance to the terminal; γi ∈ [0, 1] aims at reproducing travellers’ individual willingness to deviate based on the trip purpose, and vp is the walking speed since Equation (5) also takes into account the walking time from origin to destination.Fleet size, vehicle capacity, and cruising speed are set at the beginning of the simulation. Each vehicle is generated at the terminal stop (i.e., the MRT station). The fixed feeder vehicle travels along the route until it reaches a stop. Passengers at their destination stop alight while waiting travellers board the vehicle (if in the inbound direction), following the first-come-first-served (FCFS) queue rule, and only if the passenger group size is not greater than the available seats.


### 3.3. The Demand-Responsive Feeder

The DRF (Figure3) travels along a grid street network, with spacing dg between the streets. Vehicle routes are dynamically created based on users’ requests, and each intersection can act as a potential access/egress location for a traveller (virtual stop).Figure 3
Scheme of the DRF service: users in black are waiting for the assigned vehicle, users in grey have left the vehicle and are walking to their destination, and the user in blue is walking directly to the terminal.Unlike in the FRF case, choosing the headway of the DRF is not straightforward. While the flexibility of the DRF implies that vehicles could leave the station when they are full, in the case of a feeder service it could be better to assume a given headway to assure service regularity and synchronization with the MRT. In fact, the length of the full cycle route and the cycle time depend on the expected number of requestsn that the vehicle should serve along that route, which in turn depends on the headway, as shown in the following equation:(6)n=nu∑k=1∞pkk=λ¯LWh∑k=1∞pkk,where nu is the number of users generated during the time interval of duration h. We point out that n ≤ nu because a single trip request can involve k users (see equation (1)).A rough approximation of the expected cycle distance ECD, that is the length of the round route, can be estimated based onn (Equation (6)) and is given by the sum of a horizontal component (the vehicle movement from left to the right and vice versa) and a vertical component (the deviations along the vertical direction to serve the passengers). For the analytical derivation of ECD, the reader is referred to Appendix B.Finally, the headway of the DRF can be derived from the expected cycle time (ECT) and the fleet size as follows:(7)h=ECT+τTnV=ECD/v+ξcτs+τpn+τTnV.Equation (7) is nonlinear (as ECD depends on h), so we choose an initial value h∗ of the headway, compute n, ECD, and ECT using Equations (6) and (7), calculate the new value of h, and then repeat the process for an adequate number of iterations until convergence. This procedure takes place in the “setup” phase, before each simulation starts.The requests for the DRF service are processed in real time through a dispatching algorithm that assigns the traveller to a vehicle and a virtual stop (either a pick-up or drop-off location), according to the user time windows and the vehicle available seats, based on the FCFS rule. If no feasible match can be found, the user assumes the status “rejected” and walks directly to the destination. In this way, the penalty due to the rejection is not an arbitrary fixed value, as done, for example, in [41], but is directly related to the walking time from the origin to the destination, under the simplification that the rejected user does not have any other modal choices. This implies that rejecting requests involving longer trips plays a significant role in increasing the average user disutility (they will have to walk more to the station or from the station). Figure 4(a)illustrates the dynamics for a DRF passenger, from the trip request moment to the arrival at the destination, whereas Figure 4(b) shows the vehicle state chart.Figure 4
State charts for the DRF feeder service: (a) passenger state chart and (b) vehicle state chart.
(a)(b)Let us define the set of egress passengers asE and the set of access passengers as A. Egress passengers are assumed to make the trip request as soon as they show up at the terminal, so they are readily available to use the DRF service. Access passengers, instead, need to be given enough time to reach the assigned pick-up location and cannot be served before the earliest pick-up time interval epij, which is formulated as follows:(8)epij=0,ifi∈E,wkij+τwk,ifi∈A,where wkij is the walking time needed for passenger i to reach the pick-up location j and τwk is a fixed extra time to account for the variability of walking time implying the risk of late arrival at the stop (it can be reasonably set to 1 minute).When making a trip request, users should specify the latest pick-up time intervallpi they are willing to accept. Once again, this threshold is slightly different for egress and access passengers. The former has to wait for the DRF vehicle at the terminal, so they are supposed to be less tolerant towards the waiting time than the latter, who can generally wait at home or the workplace. The lpi is computed as follows:(9)lpi=tw,max,ifi∈E,1+γitw,max,ifi∈A,where the time tolerance level is ruled by the coefficient γi introduced in Equation (5).The last component of the user time windows is the latest drop-off time intervalldi, already introduced with the FRF service. This formulation is slightly different, since the term tw,max is replaced by lpi, as follows:(10)ldi=minlpi+1+δi+γidT,iv,1+γidT,ivp.


### 3.4. The Dispatching Algorithm for the DRF

Every time a new trip requesti (consisting of a user or group of users) occurs, the optimal matching between the demand (users group requesting the trip) and the supply (vehicle fleet) is carried out by the dispatching algorithm (Figure 5). As in [23], our algorithm follows an insertion heuristic approach (An insertion heuristic approach is adopted because it is widely used in practice to solve transportation scheduling problems, as it often provides very good solutions compared to optimality, it is computationally fast, and it can easily handle complicating constraints [20].), involving three levels of exploration of the feasible solutions:(i)
The set of routesr ∈ R, that is, the sequence of already scheduled stops (to be) visited by the vehicles (0, 1, …, p, p + 1, …, m, 0) where 0 refers to the terminal. Note that each route corresponds to a complete cycle.(ii)
The set of possible virtual stops for the new passengers ∈ S.(iii)
The set of feasible insertions of the request in the route schedule between two already scheduled stops (p, p + 1) ∈ r.Figure 5
Flowchart of the dispatching algorithm for the DRF service.When determiningR for a new trip request i, the algorithm first includes the vehicle routes of the current service cycle. In case no feasible insertion is found, R is updated including the vehicles’ route schedule of the next cycle. In this way, the possibility of rejection is reduced.The algorithm only considers the nearest three intersections to the user’s origin (or destination), plus the nearest already scheduled virtual stop, so to limit the vehicles’ detour from the original route. This implies a maximum of four possible stops, which is important to limit the length ofS, especially in very “dense” street networks and reduce the computational time. Moreover, through this approach, we keep constant the maximum number of candidates and unbind the time complexity of the algorithm from the granularity of the street network.For eachr ∈ R and each s ∈ S, the algorithm repeats the procedure of inserting s between p and p + 1 for each p = p∗, …, m, where p∗ is the first not yet visited stop of r, verifying that the following constraints are satisfied and computing the cost of the insertion.The first constraint to be met is that the timets at which the vehicle v will stop at s must be consistent with the time windows of the newly arrived user group i, as defined by Equations (8)–(10). This can be expressed as follows:(11)t0<ts≤ldi,ifi∈E,epi≤ts≤lpi,ifi∈A.The second constraint is related to the departure timet0 from the terminal and to the expected cycle time (ECT) (see (7)), as shown as follows:(12)0<t0≤lpi,ifi∈E,ts<t0+ECT≤ldi,ifi∈A.Finally, the third constraint imposes that the number of passengers on board (loadv,s) when vehicle v stops at s must not exceed the vehicle capacity, as expressed by the following relation:(13)loadv,s≤Cap.If all the constraints are met, the cost function of insertings into r between p and p + 1 is inspired by [40] and is computed as the sum of the cost ci for the user (group of users) i to be inserted, the additional cost Δcd for the passengers who are delayed because of the insertion, and the cost Δco for the operator due to the detour.(14)costr,s,p=cir,s,p+Δcdr,s,p+Δcor,s,p.Equations (15)–(17) show the three components of the cost function, expressed in terms of time. The cost for the user group is given by the weighted sum of the three components of the travel time minus the ride time related to the shortest path from/to the terminal (since it is not affected by the optimization procedure), multiplied by the number of users in the group Gi (see equation (1)) making the request, which is given as(15)cir,s,p=Giwwktwk,is+wwttwt,ir,p+wrdtrd,ir,s,p−dT,iv.Where wwk, wwt, and wrd are weighting coefficients related to the walking, waiting, and ride time, respectively. The additional costs depend on the detour time Δtr caused by the insertion of s in r, which is given as(16)Δcdr,s,p=wrdnrd,dr,p+wwtnwt,dr,pΔtrr,s,p,where nrd,d is the number of passengers on board affected by the detour, nwt,d is the number of users who will have to wait an extra Δtr at the stop due to the schedule update, and wo is the weighting coefficients of the additional cost caused by the detour for the operator, related to the vehicle-kilometres travelled. After having examined all the feasible solutions (if any), the insertion heuristic chooses the assignment that minimizes the cost function, which is shown as follows:(17)minr∈R;s∈S;p∈rcostr,s,ps.t.Equations11−13.Regarding the time complexity of the insertion heuristic, considering the “first level” of exploration of the feasible solution, the size of the set of feasible routesr is linearly related to the fleet size nV. It is an input parameter, but it should be properly chosen based on the expected number of requests n to serve (imagine having no constraints on nV). If n is sufficiently high, nV is linearly related with n. The second level regards the potential stops s to associate with the user request. As already explained, we chose to limit the number of feasible stops to a maximum of four. Finally, in the third level, the number of feasible insertions in the vehicle schedule (m + 1) is also linearly related to n. Based on these considerations, the time complexity of our insertion heuristic is O(n2), for each new request. This means that the matching process between passengers and vehicles requires low computational efforts and takes place dynamically, in real time, even with a high number of requests per unit of time.


### 3.5. Output Indicators

The model results can be assessed through different output indicators [41] to compare the two feeder services: FRF and DRF as shown in Tables 1 and 2.Table 1
Description of the user-related output indicators.
IndicatorAbbreviationDescription/formulation#UsersNUTotal number of travellers generated during the simulation% Walking UsersWLKPercentage of users who do not request for the feeder service and walk to/from the terminal% Accepted PassengersACPPercentage of travellers using the feeder service% Rejected RequestsREJPercentage of travellers whose trip request was rejected% Delayed PassengersDELPercentage of users who are delayed beyond the time windowsAvg pretrip time [s]TPT∗Average time that elapses between when a user makes the trip request (and is accepted) and starts walking to the stopAvg walking time [s]TWKAverage time for a user of the feeder service walking from the origin to the stop or from the stop to the destinationAvg waiting time [s]TWTAverage time that a traveller waits at the stop for the vehicleAvg ride time [s]TRDAverage time that a passenger spends on board a vehicleAvg total travel time [s]TAverage total travel time, which is the sum of the following components: T = TWK + TWT + TRDRejection penalty [s]TrejTotal walking time related to rejected travellers divided by the total number of passengers.Avg time stretchSTRAverage ratio, for all passengers, between T and the sum of the ride and walking time if using the shortest path (no waiting time).Avg disutility [min]UAs defined in [18], it is the weighted sum of TWK, TWT, and TRD considering the weighting coefficients of equation (16)∗Only for the DRF service.Table 2
Description of the operator-related output indicators.
IndicatorAbbreviationDescription/formulationTot. Driven distance [km]DTotal distance travelled by the vehicles during the simulation timeTot. energy consumption [kWh]TECTotal energy used by the vehicles during the simulation time (energy consumption (EC): automobile 4 pax 0.18 kWh/km (range 250 km)-minivan 6/8 pax 0.3 kWh/km (range 200 km)-minibus 9 seats (20 pax) 0.6 kWh/km (range. 120-150 km)https://www.bluebus.fr/caracteristiques-techniques-electric bus 50 seats 1 kWh/km (range. 120 km)https://www.sustainable-bus.com/news/electric-bus-range-focus-on-electricity-consumption-a-sum-up/): TEC = D∙ECAvg vehicle occupancy [pax]AVOAverage number of passengers per vehicleTransport intensity [km/pax]TIAverage distance travelled by the service per transported passenger TI =D/(NU∙ACP)Commercial speed [km/h]vcvc = D/ST% Stopping timeSTRatio between the total time spent by vehicles at the terminal or the stops and the simulation timeAnother indicator that encompasses both the user and operator point of view is the so-called total unit cost (TUC). It is based on [41] and is equal to the sum of the passenger unit cost (PUC) and the operator unit cost (OUC), which is given as(18)TUC€/pax=PUC+OUC,where(19)PUC€pax=wwkTwk+Trej+wwtTwt+wrdTrd⋅VoT,OUC€/pax=D⋅Ckm+nV⋅ST⋅ChNU⋅ACP⋅1−WLK.Here, VoT (€/h) is the value of time for the travellers,Ckm (€/veh km) the distance-related operator cost, Ch (€/veh h) the hourly driver cost, and ST (h) the total simulation time. For the first test, VoT was estimated to be 10 €/h, while regarding the operator-related costs, we set Ch  = 25 €/veh h and Ckm ranging from 0.5 to 0.1 €/veh km according to the vehicle size (distance-related operator cost (CKm): automobile 4 pax 0.1 €/veh km; minivan 6/8 pax 0.25 €/veh km;minibus 9 seats (20 pax) 0.5 €/veh km.). It is worthy of notice that in the case of a service performed by automated vehicles, the second term of the OUC would be equal to zero since no drivers are considered.


## 3.1. Overview of the Model

The main components of the simulation model are the service type (FRF or DRF), the geometric features of the service area, the demand model, the supply (vehicle) characteristics, and the simulation duration. The agents of the model are the travellers requesting a ride and the vehicles.We consider that our feeder service operates in a rectangular area of lengthL from the terminal station (horizontal direction) and width W (vertical direction). The mobility demand follows a many-to-one/one-to-many pattern since the focus is on the first/last leg of an entire PT multimodal trip. A trip request can therefore have either origin or destination at the MRT station (the terminal), located on the left side of the service region. The value of W can be considered the average distance between the terminal and the MRT stations upstream and downstream. Hereinafter, we will refer to the passengers originating at the terminal as egress passengers, while the passengers having destination at the terminal will be referred to as access passengers.From a spatial perspective, the base demand densityλ (in trips/km2h) is modelled as a linear function of the horizontal distance x from the terminal that is analytically derived in Appendix A. By varying the slope of the demand decay function, we reproduce different types of urban density and land use.Each trip requesti involves a group of a number Gi of travellers. We assume that Gi follows a geometric distribution. If we denote with p1 the probability that request i consists of a single user (PrGi=1); therefore, the probability that the group is constituted by k users is given by(1)PrGi=k=pk=p11−p1k−1.If the Manhattan distance (i.e., the distance measured along axes at right angles)dT,i between the user’s origin and the MRT station (access leg) or the MRT station and the destination (egress leg) is lower than a minimum threshold d0, a user is assumed to walk directly to/from the station. Otherwise, the probability of choosing the feeder service rapidly increases with dT,i and is given by the attractiveness coefficient η ∈ [0, 1] we introduced as follows:(2)η=1−e−0.5dT,i−d02/γ2,where γ is a parameter that rules the increase in attractivity of the feeder service due to the distance from the station: the lower the value of γ, the higher the speed at which η increases with dT,i. Figure 1 shows a graphical representation of η across the service area.Figure 1
Values of the attractiveness coefficient across a service area withL = 2.4 km and W = 1.2 km. In this example, we set γ = d0 = 0.3 km. From a temporal point of view, the demand follows a Poisson process with λ as the rate parameter.As in [18], the fraction of trips having the MRT station as the destination is given by the parameter α ∈ [0, 1], so the proportion of users going from the station to a destination inside the service area is (1−α). Although the Poisson process is well suited for the former, the temporal distribution of the egress passengers is strongly related to the schedule of the MRT line. However, assuming that the headway of the MRT line is small enough (i.e., less than 5 minutes) in both directions, we believe that the Poisson distribution with rate parameter λ is a reasonable approximation and should marginally affect the results.Regarding the supply side, the vehicles (buses, minibuses, vans, or automobiles) are defined by three input parameters: the number of vehiclesnV composing the fleet, the cruising speed v, and the allowed capacity in available seats in each vehicle cap.Finally, the duration of the simulationST, in which the input parameters are unchanged, should be sufficiently high to ensure that the steady state is reached and that the results are marginally affected by the warm-up period.


## 3.2. The Fixed-Route Feeder

The FRF (Figure2) runs back and forth on a straight line from the MRT station to the farthest bus stop, with spacing ds (input parameter) between the stops.Figure 2
Scheme of the FRF service: users in black are about to take the bus, users in grey got off the bus, and the user in blue is walking directly to the terminal.Assuming ideal conditions (no congestion or other disturbance to the service), the maximum cycle timeCTmax, that is, the time needed for a vehicle (bus) to complete the round trip, is the sum of two components (adapted from [18]), which is given as(3)CTmax=2L−ds/2v+2Lds−1⋅τs+τp,where the first component is the ratio between the length of a complete cycle and the bus cruising speed v, and the second one estimates the dwell time at each stop τs, including the time of acceleration and braking, and the additional dwell time due to boarding/alighting passengers τp.The headway between two vehicles is given by(4)h=CTmax+τtnV,where τt is the minimum dwell time required at the terminal.Egress passengers originate at the MRT station, take the bus with the earliest departure time, alight at the desired stop (i.e., the closest one to the destination of the trip) during the first half of the cycle, and walk to their final destination.Access passengers originate in the service area, walk to the closest stop, wait for the first bus headed to the terminal, travel onboard, and finally alight at the MRT station.We assume that a traveller is aware of the expected waiting time at the stop thanks to a real-time information system by the feeder service provider. Therefore, if the expected waiting time is above a certain maximum waiting timetw,max (input parameter), traveller i assumes the status “rejected” and walks to the station. Instead, if the overall travel time overcomes the latest drop-off time interval at the station ldi, the passenger assumes the status of “delayed.” This threshold varies according to the different time tolerance of the users, as shown in the following equation:(5)ldi=mintw,max+1+δi+γidT,iv,1+γidT,ivp,where δi=dT,i/L+W/2 relates the travellers’ distance to the maximum one to reach the terminal (based on the farthest user that could be generated in the service area) and represents the willingness to deviate from the shortest path based on his/her distance to the terminal; γi ∈ [0, 1] aims at reproducing travellers’ individual willingness to deviate based on the trip purpose, and vp is the walking speed since Equation (5) also takes into account the walking time from origin to destination.Fleet size, vehicle capacity, and cruising speed are set at the beginning of the simulation. Each vehicle is generated at the terminal stop (i.e., the MRT station). The fixed feeder vehicle travels along the route until it reaches a stop. Passengers at their destination stop alight while waiting travellers board the vehicle (if in the inbound direction), following the first-come-first-served (FCFS) queue rule, and only if the passenger group size is not greater than the available seats.


## 3.3. The Demand-Responsive Feeder

The DRF (Figure3) travels along a grid street network, with spacing dg between the streets. Vehicle routes are dynamically created based on users’ requests, and each intersection can act as a potential access/egress location for a traveller (virtual stop).Figure 3
Scheme of the DRF service: users in black are waiting for the assigned vehicle, users in grey have left the vehicle and are walking to their destination, and the user in blue is walking directly to the terminal.Unlike in the FRF case, choosing the headway of the DRF is not straightforward. While the flexibility of the DRF implies that vehicles could leave the station when they are full, in the case of a feeder service it could be better to assume a given headway to assure service regularity and synchronization with the MRT. In fact, the length of the full cycle route and the cycle time depend on the expected number of requestsn that the vehicle should serve along that route, which in turn depends on the headway, as shown in the following equation:(6)n=nu∑k=1∞pkk=λ¯LWh∑k=1∞pkk,where nu is the number of users generated during the time interval of duration h. We point out that n ≤ nu because a single trip request can involve k users (see equation (1)).A rough approximation of the expected cycle distance ECD, that is the length of the round route, can be estimated based onn (Equation (6)) and is given by the sum of a horizontal component (the vehicle movement from left to the right and vice versa) and a vertical component (the deviations along the vertical direction to serve the passengers). For the analytical derivation of ECD, the reader is referred to Appendix B.Finally, the headway of the DRF can be derived from the expected cycle time (ECT) and the fleet size as follows:(7)h=ECT+τTnV=ECD/v+ξcτs+τpn+τTnV.Equation (7) is nonlinear (as ECD depends on h), so we choose an initial value h∗ of the headway, compute n, ECD, and ECT using Equations (6) and (7), calculate the new value of h, and then repeat the process for an adequate number of iterations until convergence. This procedure takes place in the “setup” phase, before each simulation starts.The requests for the DRF service are processed in real time through a dispatching algorithm that assigns the traveller to a vehicle and a virtual stop (either a pick-up or drop-off location), according to the user time windows and the vehicle available seats, based on the FCFS rule. If no feasible match can be found, the user assumes the status “rejected” and walks directly to the destination. In this way, the penalty due to the rejection is not an arbitrary fixed value, as done, for example, in [41], but is directly related to the walking time from the origin to the destination, under the simplification that the rejected user does not have any other modal choices. This implies that rejecting requests involving longer trips plays a significant role in increasing the average user disutility (they will have to walk more to the station or from the station). Figure 4(a)illustrates the dynamics for a DRF passenger, from the trip request moment to the arrival at the destination, whereas Figure 4(b) shows the vehicle state chart.Figure 4
State charts for the DRF feeder service: (a) passenger state chart and (b) vehicle state chart.
(a)(b)Let us define the set of egress passengers asE and the set of access passengers as A. Egress passengers are assumed to make the trip request as soon as they show up at the terminal, so they are readily available to use the DRF service. Access passengers, instead, need to be given enough time to reach the assigned pick-up location and cannot be served before the earliest pick-up time interval epij, which is formulated as follows:(8)epij=0,ifi∈E,wkij+τwk,ifi∈A,where wkij is the walking time needed for passenger i to reach the pick-up location j and τwk is a fixed extra time to account for the variability of walking time implying the risk of late arrival at the stop (it can be reasonably set to 1 minute).When making a trip request, users should specify the latest pick-up time intervallpi they are willing to accept. Once again, this threshold is slightly different for egress and access passengers. The former has to wait for the DRF vehicle at the terminal, so they are supposed to be less tolerant towards the waiting time than the latter, who can generally wait at home or the workplace. The lpi is computed as follows:(9)lpi=tw,max,ifi∈E,1+γitw,max,ifi∈A,where the time tolerance level is ruled by the coefficient γi introduced in Equation (5).The last component of the user time windows is the latest drop-off time intervalldi, already introduced with the FRF service. This formulation is slightly different, since the term tw,max is replaced by lpi, as follows:(10)ldi=minlpi+1+δi+γidT,iv,1+γidT,ivp.


## 3.4. The Dispatching Algorithm for the DRF

Every time a new trip requesti (consisting of a user or group of users) occurs, the optimal matching between the demand (users group requesting the trip) and the supply (vehicle fleet) is carried out by the dispatching algorithm (Figure 5). As in [23], our algorithm follows an insertion heuristic approach (An insertion heuristic approach is adopted because it is widely used in practice to solve transportation scheduling problems, as it often provides very good solutions compared to optimality, it is computationally fast, and it can easily handle complicating constraints [20].), involving three levels of exploration of the feasible solutions:(i)
The set of routesr ∈ R, that is, the sequence of already scheduled stops (to be) visited by the vehicles (0, 1, …, p, p + 1, …, m, 0) where 0 refers to the terminal. Note that each route corresponds to a complete cycle.(ii)
The set of possible virtual stops for the new passengers ∈ S.(iii)
The set of feasible insertions of the request in the route schedule between two already scheduled stops (p, p + 1) ∈ r.Figure 5
Flowchart of the dispatching algorithm for the DRF service.When determiningR for a new trip request i, the algorithm first includes the vehicle routes of the current service cycle. In case no feasible insertion is found, R is updated including the vehicles’ route schedule of the next cycle. In this way, the possibility of rejection is reduced.The algorithm only considers the nearest three intersections to the user’s origin (or destination), plus the nearest already scheduled virtual stop, so to limit the vehicles’ detour from the original route. This implies a maximum of four possible stops, which is important to limit the length ofS, especially in very “dense” street networks and reduce the computational time. Moreover, through this approach, we keep constant the maximum number of candidates and unbind the time complexity of the algorithm from the granularity of the street network.For eachr ∈ R and each s ∈ S, the algorithm repeats the procedure of inserting s between p and p + 1 for each p = p∗, …, m, where p∗ is the first not yet visited stop of r, verifying that the following constraints are satisfied and computing the cost of the insertion.The first constraint to be met is that the timets at which the vehicle v will stop at s must be consistent with the time windows of the newly arrived user group i, as defined by Equations (8)–(10). This can be expressed as follows:(11)t0<ts≤ldi,ifi∈E,epi≤ts≤lpi,ifi∈A.The second constraint is related to the departure timet0 from the terminal and to the expected cycle time (ECT) (see (7)), as shown as follows:(12)0<t0≤lpi,ifi∈E,ts<t0+ECT≤ldi,ifi∈A.Finally, the third constraint imposes that the number of passengers on board (loadv,s) when vehicle v stops at s must not exceed the vehicle capacity, as expressed by the following relation:(13)loadv,s≤Cap.If all the constraints are met, the cost function of insertings into r between p and p + 1 is inspired by [40] and is computed as the sum of the cost ci for the user (group of users) i to be inserted, the additional cost Δcd for the passengers who are delayed because of the insertion, and the cost Δco for the operator due to the detour.(14)costr,s,p=cir,s,p+Δcdr,s,p+Δcor,s,p.Equations (15)–(17) show the three components of the cost function, expressed in terms of time. The cost for the user group is given by the weighted sum of the three components of the travel time minus the ride time related to the shortest path from/to the terminal (since it is not affected by the optimization procedure), multiplied by the number of users in the group Gi (see equation (1)) making the request, which is given as(15)cir,s,p=Giwwktwk,is+wwttwt,ir,p+wrdtrd,ir,s,p−dT,iv.Where wwk, wwt, and wrd are weighting coefficients related to the walking, waiting, and ride time, respectively. The additional costs depend on the detour time Δtr caused by the insertion of s in r, which is given as(16)Δcdr,s,p=wrdnrd,dr,p+wwtnwt,dr,pΔtrr,s,p,where nrd,d is the number of passengers on board affected by the detour, nwt,d is the number of users who will have to wait an extra Δtr at the stop due to the schedule update, and wo is the weighting coefficients of the additional cost caused by the detour for the operator, related to the vehicle-kilometres travelled. After having examined all the feasible solutions (if any), the insertion heuristic chooses the assignment that minimizes the cost function, which is shown as follows:(17)minr∈R;s∈S;p∈rcostr,s,ps.t.Equations11−13.Regarding the time complexity of the insertion heuristic, considering the “first level” of exploration of the feasible solution, the size of the set of feasible routesr is linearly related to the fleet size nV. It is an input parameter, but it should be properly chosen based on the expected number of requests n to serve (imagine having no constraints on nV). If n is sufficiently high, nV is linearly related with n. The second level regards the potential stops s to associate with the user request. As already explained, we chose to limit the number of feasible stops to a maximum of four. Finally, in the third level, the number of feasible insertions in the vehicle schedule (m + 1) is also linearly related to n. Based on these considerations, the time complexity of our insertion heuristic is O(n2), for each new request. This means that the matching process between passengers and vehicles requires low computational efforts and takes place dynamically, in real time, even with a high number of requests per unit of time.


## 3.5. Output Indicators

The model results can be assessed through different output indicators [41] to compare the two feeder services: FRF and DRF as shown in Tables 1 and 2.Table 1
Description of the user-related output indicators.
IndicatorAbbreviationDescription/formulation#UsersNUTotal number of travellers generated during the simulation% Walking UsersWLKPercentage of users who do not request for the feeder service and walk to/from the terminal% Accepted PassengersACPPercentage of travellers using the feeder service% Rejected RequestsREJPercentage of travellers whose trip request was rejected% Delayed PassengersDELPercentage of users who are delayed beyond the time windowsAvg pretrip time [s]TPT∗Average time that elapses between when a user makes the trip request (and is accepted) and starts walking to the stopAvg walking time [s]TWKAverage time for a user of the feeder service walking from the origin to the stop or from the stop to the destinationAvg waiting time [s]TWTAverage time that a traveller waits at the stop for the vehicleAvg ride time [s]TRDAverage time that a passenger spends on board a vehicleAvg total travel time [s]TAverage total travel time, which is the sum of the following components: T = TWK + TWT + TRDRejection penalty [s]TrejTotal walking time related to rejected travellers divided by the total number of passengers.Avg time stretchSTRAverage ratio, for all passengers, between T and the sum of the ride and walking time if using the shortest path (no waiting time).Avg disutility [min]UAs defined in [18], it is the weighted sum of TWK, TWT, and TRD considering the weighting coefficients of equation (16)∗Only for the DRF service.Table 2
Description of the operator-related output indicators.
IndicatorAbbreviationDescription/formulationTot. Driven distance [km]DTotal distance travelled by the vehicles during the simulation timeTot. energy consumption [kWh]TECTotal energy used by the vehicles during the simulation time (energy consumption (EC): automobile 4 pax 0.18 kWh/km (range 250 km)-minivan 6/8 pax 0.3 kWh/km (range 200 km)-minibus 9 seats (20 pax) 0.6 kWh/km (range. 120-150 km)https://www.bluebus.fr/caracteristiques-techniques-electric bus 50 seats 1 kWh/km (range. 120 km)https://www.sustainable-bus.com/news/electric-bus-range-focus-on-electricity-consumption-a-sum-up/): TEC = D∙ECAvg vehicle occupancy [pax]AVOAverage number of passengers per vehicleTransport intensity [km/pax]TIAverage distance travelled by the service per transported passenger TI =D/(NU∙ACP)Commercial speed [km/h]vcvc = D/ST% Stopping timeSTRatio between the total time spent by vehicles at the terminal or the stops and the simulation timeAnother indicator that encompasses both the user and operator point of view is the so-called total unit cost (TUC). It is based on [41] and is equal to the sum of the passenger unit cost (PUC) and the operator unit cost (OUC), which is given as(18)TUC€/pax=PUC+OUC,where(19)PUC€pax=wwkTwk+Trej+wwtTwt+wrdTrd⋅VoT,OUC€/pax=D⋅Ckm+nV⋅ST⋅ChNU⋅ACP⋅1−WLK.Here, VoT (€/h) is the value of time for the travellers,Ckm (€/veh km) the distance-related operator cost, Ch (€/veh h) the hourly driver cost, and ST (h) the total simulation time. For the first test, VoT was estimated to be 10 €/h, while regarding the operator-related costs, we set Ch  = 25 €/veh h and Ckm ranging from 0.5 to 0.1 €/veh km according to the vehicle size (distance-related operator cost (CKm): automobile 4 pax 0.1 €/veh km; minivan 6/8 pax 0.25 €/veh km;minibus 9 seats (20 pax) 0.5 €/veh km.). It is worthy of notice that in the case of a service performed by automated vehicles, the second term of the OUC would be equal to zero since no drivers are considered.


## 4. Application of the Model with Different Parameters

The model described above is programmed in the NetLogo development environment [45]. The operation parameters of the feeder services can be varied, as already depicted in Figures 2 and 3. This approach provides the advantage of obtaining useful insights for a transit agency operating in different urban contexts and under different demand patterns. Moreover, it is easy to perform a broad range of sensitivity analyses regarding the main input parameters of the system, which are outlined as follows:(i)
Geometric: lengthL and width W of the service area, the distance between stops ds (for the FRF) and grid street spacing dg.(ii)
Service: type of service (FRF/DRF), total simulation timeST (h), and headway h (min).(iii)
Supply: number of operating vehiclesnV, vehicle average speed S (km/h), the maximum seat capacity cap of a vehicle.(iv)
Demand: average demand densityλ¯ (pax/h), trip direction coefficient α, demand decay coefficient Λ (ratio between demand density at x = 0 and at x = L), probability of having one user per request p1, maximum waiting time twt,max (min), and maximum walking distance dwk,max.(v)
Cost: weighting coefficients related to the passengerwwk, wwt,wrd, and the operator wo.


### 4.1. First Set of Simulations: Finding the Critical Demand Density

We first show the effectiveness of the simulation model and the proposed insertion heuristic by reproducing the scenarios described by Quadrifoglio and Li [18]. Following this approach, we computed the disutility function U for the FRF and the DRF services under increasing demand levels and keeping supply, cost, and geometric parameters fixed. The critical demand density λc is calculated as the one that provides an equal passengers’ disutility for the two services. The simulation input parameters are simulation time ST = 8 h, service area dimensions L = 3.2km and W = 0.8km, grid spacing dg = 0.1km, trip direction coefficient α = 0.5, and demand decay coefficient Λ = 1 (spatially uniform demand). The input parameters used for the simulations are listed in Table 3, where the abbreviation Sc-A1 refers to a one-vehicle case and Sc-A2 to a two-vehicle case. To better reproduce the assumptions made by Quadrifoglio and Li [18], we chose sufficiently high values of twt,max and cap to relax the passenger time windows and to assume an unlimited vehicle capacity, respectively.Table 3
Input parameters adopted for the first set of simulated scenarios.
ParameterAbbreviationValuesSc-A1Sc-A2Sc-baseStop spacing [m]ds490490425Average demand density [pax/km2h]λ¯5–3020–405–60PrGi=k group probabilityp11.01.00.8Maximum waiting time [min]tw,max303010Walking speed [m/s]vp0.90.91.0Vehicle cruising speed [km/h]v32.032.030.0Vehicle capacity [pax]Cap505020Number of vehiclesnV123Headway [min](FRF)h20107(DRF)17–3010–207Cost coefficients [−]wwt112wwk332wrd221wo004Besides, we set up a new scenario (Table3, Sc-Base) able to better exploit the novelty of our methodology and include the “real-world” constraints of the DRF operations (passenger time windows, vehicle capacity, maximum cycle time, etc.) that were not considered in [18]. Sc-Base also served as a reference scenario against which to compare other 10 operational scenarios (as shown in the next subsections) and thus perform a sensitivity analysis of the most significant input parameters. For each scenario, 25 simulation runs have been performed to have a statistic of events.The results of the first set of simulations in terms of average disutility and TUC are reported in Figures6 and 7.Figure 6
Disutility of Sc-A1 (a) and Sc-A2 (b) (bars showing confidence intervals).
(a)(b)Figure 7
Performance of the Sc-base scenario in terms of user disutility (a) and transport unit cost (b) (bars in (a) showing confidence intervals).
(a)(b)Sc-A1 (Figure6(a)) and Sc-A2 (Figure 6(b)) find the critical demand density of15 pax/h-km2 for the 1-vehicle case and 30 pax/h-km2 for the 2-vehicle case, respectively, a little bit higher than the 12 pax/h-km2 and 28 pax/h-km2 found by the analytical model of Quadrifoglio and Li [18]. This is probably due to the capability of the simulation model to reproduce a more efficient vehicle dispatching and routing for the DRF service, thus enlarging its range of performance.This is even more clear from the results of the Sc-base (Figure7(a)), obtained by removing the constraints corresponding to the analytical model, where the switching point for the passenger convenience shifts in the range between 45 and 50 pax/h-km2. However, by looking at the TUC (Figure 7(b)), which is an indicator of system efficiency including also the operator point of view, the threshold is lower, between 40 and 45 pax/h-km2. This is imputable to the fast increase in the DRF supply cost (distance travelled) for a higher demand rate.As expected, the disutility for the FRF travellers, as opposed to the DRF ones, is not very sensitive to the demand density variation. This can be ascribed to the regularity of the service since the average ride time is almost the same for travellers, and the headway (affecting the average waiting time at stops) as well as the walking time, which only depends onW, ds, and vp, is constant. In particular, in Figure 7(a), one can notice a small increase in U with the demand density due to the increasing number of passengers and vehicles causing higher idle times at stops.According to the results, we fixed the demand density to the critical value of 40 pax/h-km2 and performed a second set of simulations to assess the attractiveness of the two services by varying the other model parameters.


### 4.2. Second Set of Simulations: Testing Different Demand/Service Configurations

Several scenarios have been defined to reproduce different use cases by varying the following:(1)
Demand spatial distribution (Sc-1): from uniform (Sc-base) to trapezoidal (Sc-1a) or triangular (Sc-1b); the first one might represent a residential area, whereas the other two might mimic a TOD-like land-use area, where the demand progressively decreases from the MRT station to the outskirt.(2)
Demand O/D pattern (Sc-2): from uniform (α = 0.5) of the Sc-base, to more concentrated demand patterns to/from the MRT station (α = 0.9, Sc-2a; α = 0.1, Sc-2b). This allows mimicking different demand configurations according to both land use and temporal demand distribution. Sc-base is more representative of (i) a mixed land-use area with balanced trips from and to the MRT station, or (ii) a mono-functional land-use area during off-peak hours (e.g., a residential area). Both Sc-2a and Sc-2b might represent mono-functional land-use areas during peak hours. The former is a residential area during the “morning peak” period or a workplace/service area during the “evening peak” period and the opposite applies to the latter.(3)
Area stretching (Sc-3): modifying the ratio L/W from 4 (Sc-base) towards less-/more-stretched areas (L/W equal to 2 or 3, for Sc-3a and Sc-3b, and 6 for Sc-3c). This represents different MRT services according to the station spacing (from 0.6 km to 1.2 km), for example, from an urban metro service to a regional railway service.(4)
Vehicle capacity (Sc-4): increasing the number of vehicles of smaller capacity, from 3 vehicles of 20 seats (Sc-base) to 5 vehicles of 8 seats (Sc-4a), 10 vehicles of 4 seats (Sc-4b), and 20 vehicles of 2 seats (Sc-4c). This allows testing different types of flexible feeders, from those performed by minibuses or vans to a ride-sharing service with small vehicles (e.g., UberX Share).The ten simulated scenarios (each one involving 25 simulation runs) are synthetically described in Table4 concerning the Sc-base. All the other input parameters are set equal to those of Sc-base, as reported in Table 3. The main results are reported and commented in the next subsections. The results of the two services will be first separately presented; then, a comparison between them is performed. From the point of view of the demand, we focus on PUC, from the point of view of the operator on OUC, whereas TUC encompasses both points of view. An overview of scenario results with all the output indicators defined in Tables 1 and 2 is presented in Appendix E.Table 4
Description of the second set of simulated scenarios.
Sc-baseScenarioabcSc-1 spatial distribution-Sc-2 OD pattern-Sc-3 area stretchSc-4 DRF vehicle capacity


#### 4.2.1. Fixed-Route Feeder

The results of the simulations for the FRF in terms of PUC, OUC, and U are reported in Figure8.Figure 8
Results of the second set of simulations for the FRF (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost; U = utility).As expected, the operator cost OUC is quite constant over scenarios Sc-1 and Sc-2 because the fixed service is not affected by the spatiotemporal demand distribution, while Sc-3a provides a smaller operation cost because of the shorter travelled distance.If we look at demand spatial distribution (Sc-1), when demand is higher near the MRT station, the TUC of the FRF remains almost the same (+1%). We report a reduction of PUC of 3% (SC-1a) and 7% (Sc-1b) when compared to a uniform demand distribution (Sc-base). This is mainly due to shorter passenger ride times since they are more concentrated near the MRT station. On the other hand, the OUC increases, since fewer travellers are using the feeder service.Interesting results emerge if we consider different demand patterns (Sc-2). In particular, there are two opposite trends: a higher concentration of users directed to the MRT station (Sc-2a) worsens the performance of the FRF in terms of PUC (+9%) and, thus, TUC (+7%), whereas the opposite occurs when users originate mostly at the MRT station (with multiple destinations) (-7%, -5%). This could be explained in terms of the regularity of the service. In the first case, bus bunching might occur, thus worsening the headway regularity and average waiting times. Conversely, the regularity improves in the opposite case (Sc-2b) because passengers are generated mostly at the MRT station and board the FRF with scheduled departure times.A different configuration of the service area (more or less stretched) leads to different results. In particular, there is a decreasing trend of PUC (and TUC) from less-stretched to more-stretched areas with the best result for Sc-3c. This outcome was expected as well since walking time is more relevant for users than the other time components. In this respect, a more-stretched area implies shorter walking times and higher ride time.


#### 4.2.2. Demand-Responsive Feeder

Figure9 reports the results from DRF simulations, similar to the FRF case.Figure 9
Results of the second set of simulations for the DRF (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost; U = utility).Demand spatial distribution and, in particular, a demand concentrated closer to the MRT station (Sc-1) improves the performance of DRF compared to Sc-base, also because of better dispatching of passengers that can be more easily assigned to a few virtual stops. As in the previous case, the decrease in PUC (-2% in Sc-1a and -13% in Sc-1b) is compensated by the increase in OUC (+14% and +28%, respectively).Interesting and quite different results compared to the FRF case emerge if we consider different demand patterns (Sc-2). In particular, it is possible to see a lower performance of the DRF in Sc-2 compared to the Sc-base. More specifically, the worst case occurs in Sc-2b, that is, when the demand is mainly originated at the MRT station. This can be ascribed to higher waiting times at the station, since “waiting” starts once the demand is generated (vs. the “home”-based demand where it starts when the user arrives at the virtual stop). Therefore, demand concentration worsens the DRF. Besides, in Sc-2a, a higher number of rejected users (+141% higher than in the Sc-base) occur. This result can be explained by a simpler assignment of passengers to vehicles in the case of one origin and multiple destinations (one-to-many) than in the opposite case (many-to-one).Three more scenarios are simulated for the DRF case, that is, by varying the number and capacity of vehicles while keeping the total seat capacity constant (Sc-4). A clear increasing trend of TUC is visible due to higher OUC once the number of vehicles and drivers increases. Interestingly, PUC decreases from Sc-base to Sc-4, but the relative difference between the subscenarios is very low. This suggests that it is neither profitable nor beneficial to use a higher number of small vehicles (i.e., cars) to perform the DRF service (Sc-4b, Sc-4c), while vans might represent a good compromise. They would be a suitable solution from the user perspective while implying higher operator cost (+35%) but resulting in a slightly lower TUC (−4%) compared to the minibuses case of Sc-base.This result confirms the impact of driver costs on the total operator cost and suggests the possibility of looking at automated vehicles (AV) as a potential solution. Figure10 shows a comparison between TUC with and without the driver cost for Sc-base and Sc-4 showing how the difference between the two values increases with the number of vehicles. Clear savings can be obtained in the case of Sc-4c, implying 20 vehicles of 2 seats, that is, a Uber-like service. However, this option should be analysed more in detail by looking at other important variables like the cost of AVs and the different operation conditions (e.g., road infrastructure, commercial speed, increased road congestion) and the willingness of passengers to use them.Figure 10
Comparison between transport unit cost (TUC) for traditional and automated vehicles (AV) in Scenario Base (2 vehicles with capacity = 20 seats) and Scenario 4 (vehicle capacity x number of vehicles = 8 × 5, 4 × 10, 2 × 20).


#### 4.2.3. DRF vs. FRF

Figure11 shows the comparison between the DRF and the FRF. This analysis allows finding what service suits better to each situation.Figure 11
Comparison between the DRF and the FRF in different scenarios (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost).In general, the DRF performs better in Sc-1b where we have a decreasing demand from the MRT station to the outskirts, thanks to the flexibility of the service, which allows a better matching between passengers and vehicles and lower driving distances.There is no clear trend in varying the shape of the service area. The two services are almost equivalent in Sc-3a, Sc-3b, and Sc-3c where a better performance for the users is compensated by higher costs for the operator (and vice versa). By stretching the area (Sc-3c), thus representing different catchment areas according to the MRT network (in terms of the station and line spacing), the FRF starts becoming more attractive than the DRF.Demand pattern is a critical issue to consider when planning and designing feeder services (Sc-2). In this respect, the simulation results suggest adopting the FRF instead of the DRF when the demand is mainly originated at the MRT station (to multiple destinations) and vice versa, since this would imply smaller TUC, especially in the first case (Sc-2b). This is due to the regularity of the FRF service, which is higher compared to the DRF. On the opposite, when the demand is homogeneously distributed in origin/destination from/to the MRT station, a DRF service is to be preferred.


## 4.1. First Set of Simulations: Finding the Critical Demand Density

We first show the effectiveness of the simulation model and the proposed insertion heuristic by reproducing the scenarios described by Quadrifoglio and Li [18]. Following this approach, we computed the disutility function U for the FRF and the DRF services under increasing demand levels and keeping supply, cost, and geometric parameters fixed. The critical demand density λc is calculated as the one that provides an equal passengers’ disutility for the two services. The simulation input parameters are simulation time ST = 8 h, service area dimensions L = 3.2km and W = 0.8km, grid spacing dg = 0.1km, trip direction coefficient α = 0.5, and demand decay coefficient Λ = 1 (spatially uniform demand). The input parameters used for the simulations are listed in Table 3, where the abbreviation Sc-A1 refers to a one-vehicle case and Sc-A2 to a two-vehicle case. To better reproduce the assumptions made by Quadrifoglio and Li [18], we chose sufficiently high values of twt,max and cap to relax the passenger time windows and to assume an unlimited vehicle capacity, respectively.Table 3
Input parameters adopted for the first set of simulated scenarios.
ParameterAbbreviationValuesSc-A1Sc-A2Sc-baseStop spacing [m]ds490490425Average demand density [pax/km2h]λ¯5–3020–405–60PrGi=k group probabilityp11.01.00.8Maximum waiting time [min]tw,max303010Walking speed [m/s]vp0.90.91.0Vehicle cruising speed [km/h]v32.032.030.0Vehicle capacity [pax]Cap505020Number of vehiclesnV123Headway [min](FRF)h20107(DRF)17–3010–207Cost coefficients [−]wwt112wwk332wrd221wo004Besides, we set up a new scenario (Table3, Sc-Base) able to better exploit the novelty of our methodology and include the “real-world” constraints of the DRF operations (passenger time windows, vehicle capacity, maximum cycle time, etc.) that were not considered in [18]. Sc-Base also served as a reference scenario against which to compare other 10 operational scenarios (as shown in the next subsections) and thus perform a sensitivity analysis of the most significant input parameters. For each scenario, 25 simulation runs have been performed to have a statistic of events.The results of the first set of simulations in terms of average disutility and TUC are reported in Figures6 and 7.Figure 6
Disutility of Sc-A1 (a) and Sc-A2 (b) (bars showing confidence intervals).
(a)(b)Figure 7
Performance of the Sc-base scenario in terms of user disutility (a) and transport unit cost (b) (bars in (a) showing confidence intervals).
(a)(b)Sc-A1 (Figure6(a)) and Sc-A2 (Figure 6(b)) find the critical demand density of15 pax/h-km2 for the 1-vehicle case and 30 pax/h-km2 for the 2-vehicle case, respectively, a little bit higher than the 12 pax/h-km2 and 28 pax/h-km2 found by the analytical model of Quadrifoglio and Li [18]. This is probably due to the capability of the simulation model to reproduce a more efficient vehicle dispatching and routing for the DRF service, thus enlarging its range of performance.This is even more clear from the results of the Sc-base (Figure7(a)), obtained by removing the constraints corresponding to the analytical model, where the switching point for the passenger convenience shifts in the range between 45 and 50 pax/h-km2. However, by looking at the TUC (Figure 7(b)), which is an indicator of system efficiency including also the operator point of view, the threshold is lower, between 40 and 45 pax/h-km2. This is imputable to the fast increase in the DRF supply cost (distance travelled) for a higher demand rate.As expected, the disutility for the FRF travellers, as opposed to the DRF ones, is not very sensitive to the demand density variation. This can be ascribed to the regularity of the service since the average ride time is almost the same for travellers, and the headway (affecting the average waiting time at stops) as well as the walking time, which only depends onW, ds, and vp, is constant. In particular, in Figure 7(a), one can notice a small increase in U with the demand density due to the increasing number of passengers and vehicles causing higher idle times at stops.According to the results, we fixed the demand density to the critical value of 40 pax/h-km2 and performed a second set of simulations to assess the attractiveness of the two services by varying the other model parameters.


## 4.2. Second Set of Simulations: Testing Different Demand/Service Configurations

Several scenarios have been defined to reproduce different use cases by varying the following:(1)
Demand spatial distribution (Sc-1): from uniform (Sc-base) to trapezoidal (Sc-1a) or triangular (Sc-1b); the first one might represent a residential area, whereas the other two might mimic a TOD-like land-use area, where the demand progressively decreases from the MRT station to the outskirt.(2)
Demand O/D pattern (Sc-2): from uniform (α = 0.5) of the Sc-base, to more concentrated demand patterns to/from the MRT station (α = 0.9, Sc-2a; α = 0.1, Sc-2b). This allows mimicking different demand configurations according to both land use and temporal demand distribution. Sc-base is more representative of (i) a mixed land-use area with balanced trips from and to the MRT station, or (ii) a mono-functional land-use area during off-peak hours (e.g., a residential area). Both Sc-2a and Sc-2b might represent mono-functional land-use areas during peak hours. The former is a residential area during the “morning peak” period or a workplace/service area during the “evening peak” period and the opposite applies to the latter.(3)
Area stretching (Sc-3): modifying the ratio L/W from 4 (Sc-base) towards less-/more-stretched areas (L/W equal to 2 or 3, for Sc-3a and Sc-3b, and 6 for Sc-3c). This represents different MRT services according to the station spacing (from 0.6 km to 1.2 km), for example, from an urban metro service to a regional railway service.(4)
Vehicle capacity (Sc-4): increasing the number of vehicles of smaller capacity, from 3 vehicles of 20 seats (Sc-base) to 5 vehicles of 8 seats (Sc-4a), 10 vehicles of 4 seats (Sc-4b), and 20 vehicles of 2 seats (Sc-4c). This allows testing different types of flexible feeders, from those performed by minibuses or vans to a ride-sharing service with small vehicles (e.g., UberX Share).The ten simulated scenarios (each one involving 25 simulation runs) are synthetically described in Table4 concerning the Sc-base. All the other input parameters are set equal to those of Sc-base, as reported in Table 3. The main results are reported and commented in the next subsections. The results of the two services will be first separately presented; then, a comparison between them is performed. From the point of view of the demand, we focus on PUC, from the point of view of the operator on OUC, whereas TUC encompasses both points of view. An overview of scenario results with all the output indicators defined in Tables 1 and 2 is presented in Appendix E.Table 4
Description of the second set of simulated scenarios.
Sc-baseScenarioabcSc-1 spatial distribution-Sc-2 OD pattern-Sc-3 area stretchSc-4 DRF vehicle capacity


### 4.2.1. Fixed-Route Feeder

The results of the simulations for the FRF in terms of PUC, OUC, and U are reported in Figure8.Figure 8
Results of the second set of simulations for the FRF (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost; U = utility).As expected, the operator cost OUC is quite constant over scenarios Sc-1 and Sc-2 because the fixed service is not affected by the spatiotemporal demand distribution, while Sc-3a provides a smaller operation cost because of the shorter travelled distance.If we look at demand spatial distribution (Sc-1), when demand is higher near the MRT station, the TUC of the FRF remains almost the same (+1%). We report a reduction of PUC of 3% (SC-1a) and 7% (Sc-1b) when compared to a uniform demand distribution (Sc-base). This is mainly due to shorter passenger ride times since they are more concentrated near the MRT station. On the other hand, the OUC increases, since fewer travellers are using the feeder service.Interesting results emerge if we consider different demand patterns (Sc-2). In particular, there are two opposite trends: a higher concentration of users directed to the MRT station (Sc-2a) worsens the performance of the FRF in terms of PUC (+9%) and, thus, TUC (+7%), whereas the opposite occurs when users originate mostly at the MRT station (with multiple destinations) (-7%, -5%). This could be explained in terms of the regularity of the service. In the first case, bus bunching might occur, thus worsening the headway regularity and average waiting times. Conversely, the regularity improves in the opposite case (Sc-2b) because passengers are generated mostly at the MRT station and board the FRF with scheduled departure times.A different configuration of the service area (more or less stretched) leads to different results. In particular, there is a decreasing trend of PUC (and TUC) from less-stretched to more-stretched areas with the best result for Sc-3c. This outcome was expected as well since walking time is more relevant for users than the other time components. In this respect, a more-stretched area implies shorter walking times and higher ride time.


### 4.2.2. Demand-Responsive Feeder

Figure9 reports the results from DRF simulations, similar to the FRF case.Figure 9
Results of the second set of simulations for the DRF (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost; U = utility).Demand spatial distribution and, in particular, a demand concentrated closer to the MRT station (Sc-1) improves the performance of DRF compared to Sc-base, also because of better dispatching of passengers that can be more easily assigned to a few virtual stops. As in the previous case, the decrease in PUC (-2% in Sc-1a and -13% in Sc-1b) is compensated by the increase in OUC (+14% and +28%, respectively).Interesting and quite different results compared to the FRF case emerge if we consider different demand patterns (Sc-2). In particular, it is possible to see a lower performance of the DRF in Sc-2 compared to the Sc-base. More specifically, the worst case occurs in Sc-2b, that is, when the demand is mainly originated at the MRT station. This can be ascribed to higher waiting times at the station, since “waiting” starts once the demand is generated (vs. the “home”-based demand where it starts when the user arrives at the virtual stop). Therefore, demand concentration worsens the DRF. Besides, in Sc-2a, a higher number of rejected users (+141% higher than in the Sc-base) occur. This result can be explained by a simpler assignment of passengers to vehicles in the case of one origin and multiple destinations (one-to-many) than in the opposite case (many-to-one).Three more scenarios are simulated for the DRF case, that is, by varying the number and capacity of vehicles while keeping the total seat capacity constant (Sc-4). A clear increasing trend of TUC is visible due to higher OUC once the number of vehicles and drivers increases. Interestingly, PUC decreases from Sc-base to Sc-4, but the relative difference between the subscenarios is very low. This suggests that it is neither profitable nor beneficial to use a higher number of small vehicles (i.e., cars) to perform the DRF service (Sc-4b, Sc-4c), while vans might represent a good compromise. They would be a suitable solution from the user perspective while implying higher operator cost (+35%) but resulting in a slightly lower TUC (−4%) compared to the minibuses case of Sc-base.This result confirms the impact of driver costs on the total operator cost and suggests the possibility of looking at automated vehicles (AV) as a potential solution. Figure10 shows a comparison between TUC with and without the driver cost for Sc-base and Sc-4 showing how the difference between the two values increases with the number of vehicles. Clear savings can be obtained in the case of Sc-4c, implying 20 vehicles of 2 seats, that is, a Uber-like service. However, this option should be analysed more in detail by looking at other important variables like the cost of AVs and the different operation conditions (e.g., road infrastructure, commercial speed, increased road congestion) and the willingness of passengers to use them.Figure 10
Comparison between transport unit cost (TUC) for traditional and automated vehicles (AV) in Scenario Base (2 vehicles with capacity = 20 seats) and Scenario 4 (vehicle capacity x number of vehicles = 8 × 5, 4 × 10, 2 × 20).


### 4.2.3. DRF vs. FRF

Figure11 shows the comparison between the DRF and the FRF. This analysis allows finding what service suits better to each situation.Figure 11
Comparison between the DRF and the FRF in different scenarios (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost).In general, the DRF performs better in Sc-1b where we have a decreasing demand from the MRT station to the outskirts, thanks to the flexibility of the service, which allows a better matching between passengers and vehicles and lower driving distances.There is no clear trend in varying the shape of the service area. The two services are almost equivalent in Sc-3a, Sc-3b, and Sc-3c where a better performance for the users is compensated by higher costs for the operator (and vice versa). By stretching the area (Sc-3c), thus representing different catchment areas according to the MRT network (in terms of the station and line spacing), the FRF starts becoming more attractive than the DRF.Demand pattern is a critical issue to consider when planning and designing feeder services (Sc-2). In this respect, the simulation results suggest adopting the FRF instead of the DRF when the demand is mainly originated at the MRT station (to multiple destinations) and vice versa, since this would imply smaller TUC, especially in the first case (Sc-2b). This is due to the regularity of the FRF service, which is higher compared to the DRF. On the opposite, when the demand is homogeneously distributed in origin/destination from/to the MRT station, a DRF service is to be preferred.


## 4.2.1. Fixed-Route Feeder

The results of the simulations for the FRF in terms of PUC, OUC, and U are reported in Figure8.Figure 8
Results of the second set of simulations for the FRF (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost; U = utility).As expected, the operator cost OUC is quite constant over scenarios Sc-1 and Sc-2 because the fixed service is not affected by the spatiotemporal demand distribution, while Sc-3a provides a smaller operation cost because of the shorter travelled distance.If we look at demand spatial distribution (Sc-1), when demand is higher near the MRT station, the TUC of the FRF remains almost the same (+1%). We report a reduction of PUC of 3% (SC-1a) and 7% (Sc-1b) when compared to a uniform demand distribution (Sc-base). This is mainly due to shorter passenger ride times since they are more concentrated near the MRT station. On the other hand, the OUC increases, since fewer travellers are using the feeder service.Interesting results emerge if we consider different demand patterns (Sc-2). In particular, there are two opposite trends: a higher concentration of users directed to the MRT station (Sc-2a) worsens the performance of the FRF in terms of PUC (+9%) and, thus, TUC (+7%), whereas the opposite occurs when users originate mostly at the MRT station (with multiple destinations) (-7%, -5%). This could be explained in terms of the regularity of the service. In the first case, bus bunching might occur, thus worsening the headway regularity and average waiting times. Conversely, the regularity improves in the opposite case (Sc-2b) because passengers are generated mostly at the MRT station and board the FRF with scheduled departure times.A different configuration of the service area (more or less stretched) leads to different results. In particular, there is a decreasing trend of PUC (and TUC) from less-stretched to more-stretched areas with the best result for Sc-3c. This outcome was expected as well since walking time is more relevant for users than the other time components. In this respect, a more-stretched area implies shorter walking times and higher ride time.


## 4.2.2. Demand-Responsive Feeder

Figure9 reports the results from DRF simulations, similar to the FRF case.Figure 9
Results of the second set of simulations for the DRF (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost; U = utility).Demand spatial distribution and, in particular, a demand concentrated closer to the MRT station (Sc-1) improves the performance of DRF compared to Sc-base, also because of better dispatching of passengers that can be more easily assigned to a few virtual stops. As in the previous case, the decrease in PUC (-2% in Sc-1a and -13% in Sc-1b) is compensated by the increase in OUC (+14% and +28%, respectively).Interesting and quite different results compared to the FRF case emerge if we consider different demand patterns (Sc-2). In particular, it is possible to see a lower performance of the DRF in Sc-2 compared to the Sc-base. More specifically, the worst case occurs in Sc-2b, that is, when the demand is mainly originated at the MRT station. This can be ascribed to higher waiting times at the station, since “waiting” starts once the demand is generated (vs. the “home”-based demand where it starts when the user arrives at the virtual stop). Therefore, demand concentration worsens the DRF. Besides, in Sc-2a, a higher number of rejected users (+141% higher than in the Sc-base) occur. This result can be explained by a simpler assignment of passengers to vehicles in the case of one origin and multiple destinations (one-to-many) than in the opposite case (many-to-one).Three more scenarios are simulated for the DRF case, that is, by varying the number and capacity of vehicles while keeping the total seat capacity constant (Sc-4). A clear increasing trend of TUC is visible due to higher OUC once the number of vehicles and drivers increases. Interestingly, PUC decreases from Sc-base to Sc-4, but the relative difference between the subscenarios is very low. This suggests that it is neither profitable nor beneficial to use a higher number of small vehicles (i.e., cars) to perform the DRF service (Sc-4b, Sc-4c), while vans might represent a good compromise. They would be a suitable solution from the user perspective while implying higher operator cost (+35%) but resulting in a slightly lower TUC (−4%) compared to the minibuses case of Sc-base.This result confirms the impact of driver costs on the total operator cost and suggests the possibility of looking at automated vehicles (AV) as a potential solution. Figure10 shows a comparison between TUC with and without the driver cost for Sc-base and Sc-4 showing how the difference between the two values increases with the number of vehicles. Clear savings can be obtained in the case of Sc-4c, implying 20 vehicles of 2 seats, that is, a Uber-like service. However, this option should be analysed more in detail by looking at other important variables like the cost of AVs and the different operation conditions (e.g., road infrastructure, commercial speed, increased road congestion) and the willingness of passengers to use them.Figure 10
Comparison between transport unit cost (TUC) for traditional and automated vehicles (AV) in Scenario Base (2 vehicles with capacity = 20 seats) and Scenario 4 (vehicle capacity x number of vehicles = 8 × 5, 4 × 10, 2 × 20).


## 4.2.3. DRF vs. FRF

Figure11 shows the comparison between the DRF and the FRF. This analysis allows finding what service suits better to each situation.Figure 11
Comparison between the DRF and the FRF in different scenarios (for result interpretation; PUC = passenger unit cost; OUC = operator unit cost).In general, the DRF performs better in Sc-1b where we have a decreasing demand from the MRT station to the outskirts, thanks to the flexibility of the service, which allows a better matching between passengers and vehicles and lower driving distances.There is no clear trend in varying the shape of the service area. The two services are almost equivalent in Sc-3a, Sc-3b, and Sc-3c where a better performance for the users is compensated by higher costs for the operator (and vice versa). By stretching the area (Sc-3c), thus representing different catchment areas according to the MRT network (in terms of the station and line spacing), the FRF starts becoming more attractive than the DRF.Demand pattern is a critical issue to consider when planning and designing feeder services (Sc-2). In this respect, the simulation results suggest adopting the FRF instead of the DRF when the demand is mainly originated at the MRT station (to multiple destinations) and vice versa, since this would imply smaller TUC, especially in the first case (Sc-2b). This is due to the regularity of the FRF service, which is higher compared to the DRF. On the opposite, when the demand is homogeneously distributed in origin/destination from/to the MRT station, a DRF service is to be preferred.


## 5. Conclusions

This article presented an agent-based model (ABM) for the mass rapid transit feeder design. Fixed-route feeder (FRF) and demand-responsive feeder (DRF) services have been compared to understand their attractiveness under different conditions, by taking into account both operator and user perspectives. The ABM reproduces a parametric synthetic environment where different variables related to demand, service area, and service configurations can be easily modified. The first set of scenarios allowed a comparison with the analytical model presented in Quadrifoglio and Li [18] finding a critical demand density that acts as a switching point between the two services. This was performed to show the effectiveness of the simulation model and the proposed insertion heuristic by reproducing the same scenarios and introducing new realistic constraints, allowing to find a demand density threshold.The second set of simulations was performed to reproduce different use cases by changing the demand/service configurations while maintaining the same demand density, mimicking realistic scenarios of different transport services and land-use areas. The results of ten scenarios show that a demand concentrated near the MRT station improves the performance of both the DRF and FRF services with the DRF to be preferred due to lower total (user and operator) unit costs. Stretching the service area improves the performance of the FRF services because of the lower travellers’ walking time, while a nonhomogeneous demand pattern may suggest adopting different service configurations (FRF of DRF) along the day. Finally, by increasing the DRF fleet while maintaining the same total capacity (i.e., using smaller vehicles), one can notice that there is no gain in terms of total unit cost since the increase in the operator cost is not compensated by an equivalent decrease of user cost. This could be changed by considering automated vehicles that would drastically reduce the operator cost.In terms of practical implications, the results suggest that the DRF is to be preferred in TOD-like areas characterized by a high negative density gradient from the MRT station (Sc-1b), or in peripheral areas where station spacing is quite high (Sc-base). Vice versa, the FRF should be preferred in mono-functional land-use areas (e.g., residential or workplaces) during peak periods. Besides, the same transport operator might switch services along the day as the demand pattern changes over time, using an FRF during peak periods and a DRF during off-peak periods. This could be carried out using the same vehicle fleet and staff, just changing the operation parameters.In summary, the proposed model can be used to optimize a feeder-trunk transit network, by using variables related to MRT network topology, its line and station spacing, and spatial and temporal demand pattern as inputs, and finding the optimal feeder operation as output. Our dispatching algorithm, based on insertion heuristics, involves three levels of exploration of the feasible solutions, that is, the set of vehicles that can serve the request, the set of locations where the request can be physically served, and the set of feasible insertions between two already scheduled stops. This approach has the advantage of consolidating passenger requests, reducing detours, and allowing for a higher shareability of the service. Moreover, it enables the transit operator to vary the flexibility of the operation from almost a door-to-door service to a point- or route-deviation service. We believe that such a dynamic procedure can be applied by real operators in real transit networks, providing good solutions without high computational burden, and it can be improved to deal with wider operating context.This study comes with some limitations opening future research. First, the theoretical nature of the model, and the application to a synthetic case study, while making it generalizable, do not allow to formulate context-based practical implications. In this respect, the upgraded version of our model should consider the user-specific (e.g., gender, age, occupation) and mode-specific differences [46], which reflect the heterogeneity of user preferences regarding the different time components, the value of time, and the service fare. Also, applying the model to real case studies would imply devoting particular attention to the demand forecasting and user loyalty to the DRT service over time [47], two factors which are crucial to ensure a proper planning, operation design, and eventually the viability of the service itself. Accordingly, we would address the problem of travel demand uncertainty, relying on more data and use cases. Another attractive issue, which is currently poorly addressed in literature, is the evaluation of dynamic pricing schemes for flexible transit, which would help the service providers improve system performance, maximizing the profit according to the spatial and temporal variation in demand. Dynamic pricing strategies [48] can be included in more sophisticated ABMs, where negotiation mechanisms between the vehicle fleet and the users and among the vehicles themselves would be simulated. In future research endeavours, it will be interesting to compare the performance of DRF and of parallel FRF services that could be used to serve the service area with the same operation costs, reducing the walking time of users while increasing the headway. Finally, the impact of automated vehicles on service performance should be analysed more in detail to further explore the potential of this new technology to provide efficient feeder services.



---

*Source: 8382754-2022-01-24.xml*