## 3 Results
For the MAV fleet solution, where four modules are used to travel from the airport to the city center and then split into two road trains, each consisting of two modules, the overall energy consumption results are considered. In particular scenarios, it is essential to consider that the leading modules might draw more electrical energy from their battery packs, resulting in reduced range and more wear on the electrical components and some mechanical components as well. For this reason, a more detailed analysis is hinted by this paper, which implies looking at software solutions that allow simulation of MAVs operating together in a predetermined environment. As of the present access and capabilities of the available software, the defined scenarios can lead to results that show the conceptual impact of modular vehicle fleets, but they do not indicate exact numbers in terms of efficiency, energy consumption reduction, or equipment wear indications. The MAV fleet is comprised of four separate vehicles, each maintaining uniform weight distribution throughout its framework. During the simulation, each vehicle maintains an even distribution of weight, ensuring consistent performance and stability throughout the entire system. The intentional strategy of distributing weight enhances the vehicle's efficiency and versatility in different operational situations. In Table 8, the combined simulation results of the MAV application are listed. It should be noted that the initial State-of-Charge of the batteries is set at 85%, considering that the vehicle leaves the depot where it is charging and travels without running any passenger transport tasks until it reaches the starting point of the route--the airport's terminal bus station. Upon leaving the charging station, the vehicle is charged between 90% and 100%, considered to be fully charged. In both simulation scenarios, it can be observed that the autonomous vehicles end their tasks with a State-of-Charge of over 50%, allowing them to at least travel a returning route to the starting point. In any case, the scalability and planning of such vehicles are key factors in ensuring that tasks can be carried out without issues related to effective range or unexpected energy consumption. For each particular case of MAV applications, a reserve charge is taken into account based on the length of the routes, landmarks, weather conditions, and other relevant factors. Figure 10 shows the evolution of the batteries' State-of-Charge during each test run, starting from the airport, through the city center and to the last bus stop of every route, described below as End of Route. The city center is the detaching point, where the common path of the two routes ends and each route continues to its respective destination. The characteristics of electric buses are illustrated in shades of blue, while MAV performance is shown in shades of red. It can be noticed that the SoC evolution from the airport to the city center is similar for each mobility solution: the electric buses, having the same technical specifications and passenger load, perform the same, while the MAV alternative uses all four modules together to reach the city center, so the cumulated battery discharge is identical. In the city center, the two routes split and follow their respective paths. The route to the train station is shorter, so the remaining charge in the batteries at the end of the route is higher for both BEB (82.84%) and MAV (81.98%). The darker shades of each color are showing the SoC of runs to the Western area of the city, into the neighborhood. The route being longer, the impact on SoC is noticeably higher, obtaining a remaining charge of 76.89% for BEB and 77.39% for MAV. \begin{table}
\begin{tabular}{c c c} \hline \hline \multirow{2}{*}{**Quantity**} & \multicolumn{2}{c}{**Value**} \\ \cline{2-3}  & **Initial** & **Final** \\ \hline PT.BCU.BattHV.SOC [\%] & 85 & 57.11401368 \\ Average energy consumption [kWh/km] & & 1.22507 \\ Energy consumption per passenger [kWh/km] & & 0.02552 \\ \hline \hline \end{tabular}
\end{table}