Interviews

PLIYT, Inc.

1. For more than a century, vehicle architecture has been shaped around the needs of the driver. As automated driving advances, what fundamentally changes when passenger requirements can become a primary consideration in vehicle architecture?

For over a century, road-vehicle architecture has been organized around a single persistent constraint: a human must drive. That requirement imposed a set of first-order architectural requirements that dictated control positions, steering and pedal linkages, driver reach zones, forward sightlines, windshield rake, and front-seat orientation. Passengers were obviously important users, but their needs were downstream accommodations coexisting within an architecture whose primary hardpoints originated with the driver.  

As driving automation reaches high and full levels (SAE J3016), the automated driving system performs the complete dynamic driving task. This creates a historical architectural inflection point. When the human driver is no longer required to organize the vehicle, passenger requirements stop being secondary compromises squeezed into leftover cabin volume. Instead, they become primary upstream inputs that dictate physical packaging, ingress geometry, spatial allocation, environmental systems, and the overall mobility experience from first principles. 

2. Many autonomous vehicles are already being developed without conventional steering wheels, pedals and driver-focused interfaces. What distinguishes a vehicle that simply removes the driver from one that is genuinely designed around the passenger?

It is essential to decouple autonomy from passenger-defined architecture. An Autonomous Vehicle (AV) addresses the dynamic driving task - it answers the question, “Who or what drives?” A Passenger-Defined Vehicle (PDV) addresses architecture and mobility experience - it answers the question, “Who is the vehicle fundamentally designed around?”  

Simply removing the steering wheel, pedals, and driver displays from an existing platform does not make it a PDV. That merely produces a hollowed-out legacy package where occupants remain locked into forward-facing seating, facing blank bulkheads, constrained by proportions originally conceived around engine bays, steering columns, and driver sightlines. Autonomy creates the architectural freedom; passenger-defined architecture describes how that freedom is actually utilized. A genuinely passenger-defined vehicle uses that freedom to reorganize the physical and digital platform entirely around passenger use cases. 

3. How should passenger requirements influence vehicle development from the earliest stages? Which architectural decisions - such as seating, access, cabin geometry, space allocation and interfaces - should be reconsidered first?

Passenger needs must enter the design cycle early enough to influence vehicle hardpoints before platform dimensions and structural crash paths are frozen. 

The primary decisions to reconsider first include:

•    Door Aperture, Floor Height, and Access Strategy: Historical vehicles force awkward, stooping ingress because rooflines and sills were optimized around driver eyelines and aerodynamics. Passenger-first architecture starts with the step-in height, curb interface, and portal clearance required for dignified, unassisted walk-in access.  
•    Cabin Geometry and Seating Orientation: Relieved of the requirement that an operator must sit upright facing forward to scan the road, space can be allocated dynamically for resting, working, or conversation.  
•    Decentralized Human-Machine Interfaces (HMI): Interfaces must move away from the traditional center-stack dashboard and be integrated contextually around passenger reach zones, focusing on immediate control over micro-climate, lighting, privacy, and trip status. 

4. Not every autonomous vehicle will necessarily be designed around passengers to the same degree. What factors would distinguish a vehicle that simply accommodates passengers from one that is genuinely designed around their needs from the outset?

In the PDV foundational paper, passenger-definedness is formalized as an architectural spectrum rather than a binary label: 

1. Driver-Defined Vehicle: Driver requirements dominate the architecture.  
2. Passenger-Oriented Vehicle: Passenger comfort and features are improved within an inherited driver-defined architecture.  
3. Purpose-Built Passenger-Centric Autonomous Vehicle: Removing the driver enables significant structural reorganization around riders (e.g., collective shuttles or robotaxis).
4. Ground-Up / High-Expression PDV: Passenger requirements originate major physical, digital, access, experience, and service architecture decisions from the very beginning. 

A vehicle that merely accommodates passengers treats passenger comfort as an afterthought or feature layer (trim, styling, infotainment screens) applied over a generic box. A vehicle genuinely designed around passengers treats passenger requirements as structural inputs - meaning the physical boundaries, structural bulkheads, acoustic barriers, and digital systems change fundamentally based on the intended passenger mission. 

5. A passenger-first approach could involve developing the vehicle from the inside out. How might starting with the desired passenger environment influence cabin geometry, access, seating, interior systems and ultimately the vehicle's exterior architecture?

Inside-out architectural development is a core tenet of PDV. Traditionally, styling studios sculpt an exterior envelope and packaging engineers force occupants to fit inside it.  

Starting inside out reverses the hierarchy:

1. The Passenger Activity Envelope: Design begins by defining the volumetric space needed for human activities - such as reclining, working, or interacting - and accommodating luggage and personal belongings.  
2. Access and Aperture Geometry: Door openings, roof cutouts, and sill heights are established to enable natural, barrier-free ingress and egress.  
3. Packaging Around the Capsule: Structural crash rings, battery enclosures, thermal management loops, and autonomous sensor suites are then packaged around the exterior of that optimized living volume.  

As a consequence, exterior styling is no longer bound to traditional three-box (sedan) or two-box (SUV) silhouettes. The exterior naturally becomes a streamlined, aerodynamically cohesive monovolume whose aesthetic expression is dictated by the spatial envelope within. 

6. Autonomous driving creates greater freedom to reconsider seating orientation, cabin configuration and passenger interaction, but these changes also raise safety and regulatory challenges. How should passenger-oriented architectural innovation be balanced with crashworthiness, restraint systems, emergency egress and functional safety?

A foundational principle of PDV is that safety remains a governing requirement: passenger-first architecture is not permission to subordinate safety to interior novelty.

Reconfiguring cabins raises critical physical challenges. For example, research demonstrates that rearward-facing seating measurably increases motion-sickness likelihood, highlighting that non-traditional layouts must be empirically validated, not blindly assumed.  

To balance innovation with rigorous safety:

•    Seat-Integrated Restraint Architecture: Restraints, pre-tensioners, and dynamic load limiters must be built directly into the seat structure (all-belts-to-seat) rather than relying on vehicle pillars, accommodating various reclined or swiveled postures.
•    Proactive Pre-Crash Interventions: Vehicles can utilize automated perception stacks to detect imminent, unavoidable collisions, automatically adjusting motorized seat geometries into optimal deceleration postures milliseconds prior to impact.
•    Mechanical Egress Redundancy: Passenger-first door systems must retain intuitive, fail-safe mechanical manual releases that function independently of high-voltage electronics or automated actuators during structural deformation. 

7. Passenger experience in an autonomous vehicle extends beyond physical comfort to privacy, personalization, climate, lighting, connectivity and digital identity. How should physical and digital systems be co-designed to create a coherent passenger experience?

Under the PDV framework, physical and digital systems must be co-designed from inception. A passenger-defined experience cannot be achieved by bolting consumer tablets onto static interior panels.  

Physical surfaces must be engineered as digital interaction points: ambient, hidden-until-lit controls, materials that incorporate tactile feedback, and localized acoustic zones that deliver personalized audio without spillover. Digitally, systems must seamlessly recognize passenger identity to configure micro-climate, seating presets, ambient lighting, and media routing. Crucially, this must be executed through privacy-preserving edge architectures where user preferences configure the vehicle dynamically without requiring persistent, centralized surveillance or cloud tracking of personal habits. 

8. Shared autonomous mobility presents a particular challenge: passengers may value the efficiency of sharing while also expecting privacy, cleanliness, personal space and control. What architectural approaches could help address these competing requirements?

Shared autonomous mobility is a vital test bed for PDV because the efficiency of asset-sharing inherently conflicts with passenger desires for personal space, acoustic privacy, and cleanliness.  

Rather than attempting to solve these frictions purely through operational rules or software policies, PDV resolves them structurally:  

•    Spatial & Acoustic Partitioning: Architectures can utilize lightweight acoustic bulkheads, physical barriers, and electrochromic privacy glass to establish individualized, secure micro-compartments within a single shared platform.
•    Isolated HVAC Micro-Zones: Engineering separate ventilation pathways equipped with localized filtration prevents cross-cabin airflow between shared occupants. 
•    Designed-in Serviceability: Incorporating non-porous, antimicrobial surfaces, seamless floor transitions, and automated UV-C disinfection routines enables high fleet turnover and immaculate hygiene without manual turnaround delays.

9. Accessibility is often addressed within an existing vehicle architecture. What would it mean to make accessibility a foundational requirement when designing a vehicle around passengers from the beginning?

Historically, accessibility has been an aftermarket modification: cutting into existing vehicle floors, installing cumbersome hydraulic lifts, and relegating wheelchair occupants to secondary, retrofitted spaces. 

Making accessibility a foundational architectural requirement means the base vehicle platform is conceived from first principles around universal human mobility:  

•    Level-Entry Skateboard Design: Integrating low-profile battery packs and suspension geometries to align cabin floor height directly with standard pedestrian curbs, providing ramp-free, roll-on boarding.  
•    Integrated Universal Restraints: Cabin floors engineered with flush, automated docking stations that secure mobility devices rapidly without requiring manual assistance.  
•    Multi-Sensory In-Cabin HMI: Communication systems that output environmental and trip data across visual, tactile (braille/haptic), and audio channels simultaneously, ensuring riders with diverse capabilities have equal operational agency. 

10. As vehicles become increasingly personalized, issues such as passenger identity, privacy, cybersecurity, remote assistance and emergency intervention become more important. How could these requirements influence the architecture and operation of future autonomous vehicles?

As vehicles become more responsive to the individual, the tension between personalization and privacy escalates. If an autonomous fleet tracks interior occupant activity via centralized video and audio streams, it risks turning vehicles into mobile surveillance environments. 

Architecturally, this demands:

•    Edge-Based Data Sovereignty: Personal identity and behavioral preferences must remain stored on the passenger’s device or processed within ephemeral, localized vehicle compute that cryptographically purges upon trip completion.  
•    Hardware-Enforced Separation of Domains: Safety-critical vehicle controllers (braking, steering, path planning) must be strictly isolated via hardware-enforced domain isolation and secure gateways from cabin infotainment and personalization networks.  
•    Calibrated Teleoperation Boundaries: Remote assistance systems must be architected to operate on vehicle telemetry, exterior perception streams, and fleet health diagnostics. In-cabin cameras and microphones should remain strictly private, activating only upon explicit passenger request or verified emergency intervention triggers. 

11. Could passenger-first vehicle architecture extend beyond autonomous shared mobility to privately owned vehicles, commercial transportation, healthcare mobility or other applications? What principles could remain common across these different mobility missions?

Yes. PDV is explicitly an architectural paradigm, not a specific body style, compartment configuration, or business model. While shared mobility highlights acute passenger compromises, the framework applies across multiple sectors:  

•    Privately Owned Vehicles: Vehicles designed not as driver workstations, but as quiet mobile lounges, restorative sleep spaces for highway travel, or personal study environments.  
•    Healthcare & Non-Emergency Medical Transport: Platforms featuring sterile interior surfaces, level stretcher access, and isolated medical monitoring bays.  
•    Commercial Mobile Workspaces: Cabins optimized with ergonomic desk integration, acoustic soundproofing, and enterprise-grade connectivity.  

The unifying principle across all these missions is identical: passenger use cases serve as primary upstream inputs, defining the vehicle from the inside out once legacy driver constraints recede. 

12. Moving away from conventional driver-centric architectures could introduce significant engineering and commercial trade-offs. What challenges do you foresee around manufacturing complexity, vehicle cost, weight, maintenance, cleaning, utilization and fleet economics?

The transition away from driver-defined architectures introduces substantial commercial and engineering considerations that must be validated in fleet operations: 

•    Capital Tooling & Validation: Deviating from established unibody stamping dies increases upfront engineering costs for bespoke structural geometries, specialized opening mechanisms, and unique occupant crash structures.  
•    Mass versus Volumetric Efficiency: Accommodating upright ingress, acoustic isolation materials, and robust partition walls can add structural weight, requiring optimization in lightweight composites to protect vehicle efficiency.  
•    Material Resilience & Maintenance: High-utilization passenger cabins must balance premium tactile aesthetics with industrial durability, resisting wear across thousands of cleaning cycles.  

However, when evaluated through commercial fleet economics, purpose-built PDVs provide significant total-cost-of-ownership (TCO) advantages. They eliminate aftermarket conversion costs, increase vehicle operational uptime, simplify interior cleaning, and drive higher passenger willingness to pay through a demonstrably superior experience. 

13. What research, engineering validation and industry collaboration are still needed before more passenger-oriented vehicle architectures can become practical and scalable?

To advance passenger-defined architecture toward high-volume reality, the industry must align across three critical domains:  

1. Modernized Occupant Protection Regulations: Continued evolution of safety standards (such as NHTSA’s occupant protection rules for vehicles without manual controls) to establish standardized crash-test protocols and anthropomorphic test devices for non-traditional and reclined seating postures.  
2. Standardized Modular Interfaces: Cross-industry collaboration between OEMs and Tier 1 suppliers to develop standardized mechanical rails, electrical power couplings, and data networks that allow cabin interiors to be upgraded over multi-year operational life cycles.  
3. Biomechanical Motion Sickness Mitigation: Rigorous research into motion sickness countermeasures - optimizing the relationship between visual horizon references, active suspension damping, dynamic airflow, and seating direction. 

14. Looking ahead, if automated driving eventually removes the human driver as a fundamental architectural constraint, what aspects of today's vehicle architecture do you believe the automotive industry will rethink most fundamentally—and what could future vehicles ultimately be designed around?

The automotive industry will fundamentally rethink the premise that a vehicle’s form must be governed by the act of dynamic human driving. For more than a century, automotive metrics were defined by horsepower, acceleration, dashboard ergonomics, and driver forward visibility. 

When the driver constraint recedes, vehicles will no longer be designed around driving performance; they will be designed around human spatial utility and well-being. Vehicle architecture will be understood through two distinct historical eras: the Driver-Defined Era, where passengers were accommodated within an operator’s machine; and the Passenger-Defined Era, where the vehicle becomes a configurable, dignified human environment. Future vehicles will be judged not by how they engage a driver on the road, but by the physical comfort, privacy, and utility they afford the human beings inside.