public transport

operational dynamics 

To ensure energy efficiency, passenger comfort, and urban safety public transport shall ensure:

  • standard speed class (urban-50)
    The default operational class is limited to 50 km/h. This ensures optimized sensor range requirements and minimizes kinetic energy in urban environments. Optional higher classes (e.g., regional-70) may be defined for specific corridors.
  • acceleration limits (comfort & efficiency)
    Maximum longitudinal acceleration is capped at 1.5 m/s² (subject to safety-critical overrides). This reduces battery drain and prevents motion sickness.
  • jerk limitation (smoothness)
    To ensure a comfortable and safe ride, the rate of change of acceleration (jerk) is strictly limited, ensuring smooth transitions during starting and braking.
  • deceleration profiles
    Standard braking for energy recuperation is prioritized. Mechanical friction braking is reserved for emergency scenarios and final standstill.

accessibility & inclusion

  • Low-floor entry with automated ramps, dedicated wheelchair spaces, and securing systems.
  • Acoustic and visual announcements, high-contrast displays, and simple language lokal + English
  • Optional bike carrier

social security for autonomous ride sharing / pooling

Social security is the decisive factor for the success of autonomous public transport. A driverless shuttle will only gain acceptance if people – particularly women and seniors -feel safe and protected, even during late-night hours.

  • 24/7 control center with intervention chain: Immediate contact, clear escalation tiers, and direct links to police or municipal security services.
  • panic & assistance buttons: Easily accessible, barrier-free, multilingual, and equipped with a direct voice link to the control center.
  • Safe-Stop Logic: In case of conflict, the vehicle proactively steers toward well-lit, frequented “Safe Hubs” rather than stopping in isolated areas.
  • Event-Based Detection (Privacy-by-Design): Automated triggers for screams, sounds of violence, breaking glass, or heavy impacts. This ensures privacy by avoiding continuous surveillance while providing immediate response when needed.
  • Interior design: Bright lighting, clear sightlines (no blind spots), non-slip flooring, and ergonomic handrails
  • Visible code of conduct: Clear house rules displayed in-vehicle and via the app, with consistent enforcement
  • Police for immediate on-site support
  • De-escalation training: Specialized training for control center staff in conflict resolution and crisis management.
  • Phased Rollout: A step-by-step transition (Daytime → Evening → Night) only after proven performance and high public acceptance.
  • Verified accounts: Identity and payment verification as a standard requirement, especially for night-time operation.
  • Sanction system: Temporary or permanent bans for harassment, violence, or vandalism.
  • Anti-vandalism features: Robust materials, secured sensor covers, and alarms for physical tampering.
  • Protection modes for vulnerable groups: * Options for “Verified Passengers Only.”
    • Night-time “Safe-Match” logic (e.g., grouping passengers based on age or verified status).
    • Optional “Opt-out” of pooling for late-night journeys.

operational safety

  • Vulnerable Road User (VRU) Interaction: Low operational speeds in pedestrian zones, clear signaling of intent, and a “Safety-First” priority logic for cyclists and pedestrians.
  • Full redundancy: Independent systems for braking, steering, power supply, and compute; defined degradation modes for safe operation.
  • ODD Management (Operational Design Domain): Operation restricted to strictly defined domains (weather, speed, and road classes).
  • Minimal Risk Condition (MRC): Automated controlled stop or transition to a “Safe-Stop” location in the event of a system failure.
  • Remote Assistance: Local control center with “remote operators” to provide guidance at complex intersections or in conflicting traffic situations.

governance, data, and transparency

  • Standardized Incident Reporting: Mandatory reporting of both technical and social safety incidents to public authorities.
  • Data Sovereignty: Minimal data collection, short retention periods, and strict purpose-binding (GDPR compliant).
  • Public Safety KPIs: Transparent publishing of safety data (incidents per 100k km), control center response times, and user satisfaction rates.

cybersecurity & integrity

  • Security by Design: Threat modeling, penetration testing, and Zero-Trust architectures.
  • Secure supply chain: Signed updates, secure key management, and hardware security modules (HSM).
  • Intrusion detection: Real-time monitoring for manipulation with clear response plans (isolation or safe degradation).