Autonomous vehicles are already capable of driving reliably today. The real challenge, however, begins when a pilot project is to be transformed into a permanently stable, economical, and safely controllable regular operation.
The discussion about autonomous mobility often focuses on technological feasibility. In doing so, a crucial question is frequently asked too late: Can an autonomous system not only be demonstrated but also operated sustainably as part of public transportation? This is precisely where the true test of autonomous mobility in public transportation begins.
For there is a systemic gap between successful testing and robust regular operations. The German federal government, too, explicitly describes the current situation as a phase between completed testing and the lack of scaling. At the same time, there is a lack of production-ready offerings as well as robust operator and business models for autonomous shuttle systems.
Internationally, this development is increasingly being approached from an operational perspective. France already explicitly describes autonomous mobility as a future mobility service and no longer exclusively as a technology trial.
Regular operation changes the requirements
This is precisely where the technical perspective is also shifting. In pilot operations, many risks can still be mitigated through clearly defined routes, limited scenarios, safety drivers, additional intervention options, or remote backup structures.
In subsequent regular operation, however, many of these implicit safety measures are eliminated. It is then no longer sufficient for a vehicle to be able to drive autonomously under ideal conditions. Rather, the decisive factor is whether vehicle movement remains controllable at all times, even under varying environmental and operating conditions.
This shifts the central question: no longer just whether a system works—but whether it remains controllable and capable of acting even when parts of the system are operating at reduced capacity or conditions deviate from the nominal state.
Fail-operational becomes an operational requirement
It is precisely at this point that a term becomes central, one that often appears too late in many discussions: fail-operational. For autonomous mobility in public transportation, it is not enough to simply bring systems to a safe stop in the event of a fault. A vehicle that simply stops in the event of a malfunction reduces availability, impairs operations, and creates additional risks in the overall system.
In public transportation, therefore, normal operation means more: systems must be able to safely maintain defined operating states even under fault conditions. This is not a convenience feature, but a basic prerequisite for availability, reliability, predictability, and economically viable operation.
The “Handbook on Autonomous Driving in Public Transport” therefore explicitly describes autonomous mobility as an integrated operational and system task. In addition to vehicle technology, the handbook focuses on topics such as technical supervision, control centers, maintenance, safety, and organizational operational processes.
Control Becomes a Critical System Element
As the scale increases, it becomes clear: The real challenge of autonomous mobility no longer lies solely in perception or decision-making logic. What is crucial is the safe and reproducible execution of movement under real-world operating conditions. Many of today’s pilot projects still circumvent this challenge through limited operational areas, additional levels of intervention, or highly controlled scenarios. In regular operation, however, such workarounds are of limited use.
As a result, vehicle control itself becomes a critical system element of autonomous mobility. Bitkom therefore also calls for larger pilot regions and realistic operating conditions to gain reliable insights into the scalability, cost-effectiveness, and operational capability of autonomous systems. For developers, OEMs, and system architects, this means a fundamental shift in perspective: routine operation must not be viewed as a later stage of development. It must be the benchmark for system architecture from the very beginning.
With NX NextMotion, Arnold NextG addresses precisely this challenge: vehicle control as an independent, fail-operational system level for autonomous and safely controllable mobility systems.
Conclusion
Autonomous mobility is not decided in demonstration operations, but in everyday life. Only when systems remain controllable, available, and capable of acting under real-world conditions does technological feasibility give rise to a resilient public mobility system. Regular operation is therefore not a later addition to autonomous mobility, but its actual target.
We Control What Moves!
For more information, visit www.arnoldnextg.com/blog
The discussion about autonomous mobility often focuses on technological feasibility. In doing so, a crucial question is frequently asked too late: Can an autonomous system not only be demonstrated but also operated sustainably as part of public transportation? This is precisely where the true test of autonomous mobility in public transportation begins.
For there is a systemic gap between successful testing and robust regular operations. The German federal government, too, explicitly describes the current situation as a phase between completed testing and the lack of scaling. At the same time, there is a lack of production-ready offerings as well as robust operator and business models for autonomous shuttle systems.
Internationally, this development is increasingly being approached from an operational perspective. France already explicitly describes autonomous mobility as a future mobility service and no longer exclusively as a technology trial.
Regular operation changes the requirements
This is precisely where the technical perspective is also shifting. In pilot operations, many risks can still be mitigated through clearly defined routes, limited scenarios, safety drivers, additional intervention options, or remote backup structures.
In subsequent regular operation, however, many of these implicit safety measures are eliminated. It is then no longer sufficient for a vehicle to be able to drive autonomously under ideal conditions. Rather, the decisive factor is whether vehicle movement remains controllable at all times, even under varying environmental and operating conditions.
This shifts the central question: no longer just whether a system works—but whether it remains controllable and capable of acting even when parts of the system are operating at reduced capacity or conditions deviate from the nominal state.
Fail-operational becomes an operational requirement
It is precisely at this point that a term becomes central, one that often appears too late in many discussions: fail-operational. For autonomous mobility in public transportation, it is not enough to simply bring systems to a safe stop in the event of a fault. A vehicle that simply stops in the event of a malfunction reduces availability, impairs operations, and creates additional risks in the overall system.
In public transportation, therefore, normal operation means more: systems must be able to safely maintain defined operating states even under fault conditions. This is not a convenience feature, but a basic prerequisite for availability, reliability, predictability, and economically viable operation.
The “Handbook on Autonomous Driving in Public Transport” therefore explicitly describes autonomous mobility as an integrated operational and system task. In addition to vehicle technology, the handbook focuses on topics such as technical supervision, control centers, maintenance, safety, and organizational operational processes.
Control Becomes a Critical System Element
As the scale increases, it becomes clear: The real challenge of autonomous mobility no longer lies solely in perception or decision-making logic. What is crucial is the safe and reproducible execution of movement under real-world operating conditions. Many of today’s pilot projects still circumvent this challenge through limited operational areas, additional levels of intervention, or highly controlled scenarios. In regular operation, however, such workarounds are of limited use.
As a result, vehicle control itself becomes a critical system element of autonomous mobility. Bitkom therefore also calls for larger pilot regions and realistic operating conditions to gain reliable insights into the scalability, cost-effectiveness, and operational capability of autonomous systems. For developers, OEMs, and system architects, this means a fundamental shift in perspective: routine operation must not be viewed as a later stage of development. It must be the benchmark for system architecture from the very beginning.
With NX NextMotion, Arnold NextG addresses precisely this challenge: vehicle control as an independent, fail-operational system level for autonomous and safely controllable mobility systems.
Conclusion
Autonomous mobility is not decided in demonstration operations, but in everyday life. Only when systems remain controllable, available, and capable of acting under real-world conditions does technological feasibility give rise to a resilient public mobility system. Regular operation is therefore not a later addition to autonomous mobility, but its actual target.
We Control What Moves!
For more information, visit www.arnoldnextg.com/blog
