Access Official Technical PDF

Share Summary:LinkedInEmail

A modular mobility platform changes the way a vehicle can be configured and used. Rather than treating the chassis and body as a single permanent assembly, Rinspeed’s microSNAP concept separates them into reusable chassis modules, called “skateboards,” and purpose-built bodies, called “pods.” At CES 2019, the company demonstrated a fully automated robot station designed to join and separate these modules—an approach that connects vehicle design with automation, system integration and lifecycle planning.

Although microSNAP is a compact automotive concept, its architecture raises questions familiar to industrial automation teams: How should separate modules interface? How can different subsystems operate together? And what must be coordinated when hardware is designed for more than one use case?

How the modular mobility platform is designed

The microSNAP is a further development of Rinspeed’s earlier SNAP concept, scaled to approximately the dimensions of a Renault Twizy. Its central design principle is a division of responsibilities between the skateboard and the pod.

  • The skateboard is the rolling chassis. It contains drivetrain components and technology associated with autonomous operation, including electronic hardware that may age or require replacement.
  • The pod is the body configured for a particular task, such as carrying passengers or transporting goods. Rinspeed’s concept envisages the body lasting longer than the chassis hardware.

Because the modules are intended to be temporary companions, a pod can be paired with an available skateboard for its intended purpose. The concept therefore treats the vehicle as a configurable system rather than a fixed body-and-chassis combination. Rinspeed’s stated rationale is that chassis components subject to wear and technological aging can be replaced at the end of their service life, rather than requiring a complex hardware update to the complete vehicle.

Automated mating makes modularity operational

Interchangeable modules only become practical when they can be connected and disconnected in a controlled way. The microSNAP demonstration addressed this with a fully automated robot station that autonomously joins and separates the chassis and body. In automotive manufacturing, bringing the chassis and body together is known as mating; in this concept, the connection is intended for a period of use rather than a permanent assembly.

This makes the station an important part of the overall architecture, not just a piece of factory equipment. The robot must interact with two distinct vehicle modules, while the wider system depends on those modules being suitable for repeatable pairing and separation. The source does not specify the station’s detailed control logic or interface design, but the demonstration makes clear that robotic handling is central to realizing the modular concept.

For automation engineers and integrators, the broader lesson is to consider the equipment and process needed to manage modularity alongside the modules themselves. A design that supports exchange at the vehicle level also requires an automated process capable of performing that exchange.

Integrating controls, sensing and connectivity

The microSNAP brings together technologies from multiple partners across the vehicle. Its systems include a 48-volt traction motor, a drive-by-wire steering system with redundant steering and braking, lidar sensors, an autonomous-driving compute platform and driving software. The concept also incorporates connected-vehicle functions, including 5G telematics, cloud connectivity and over-the-air software updates.

These elements illustrate the integration challenge behind an automated, connected vehicle. Mechanical systems, electronic controls, software and communications have to coexist within one platform. The concept also includes cybersecurity technology and multi-stage user authentication, while DEKRA verified the security of data and information transfer, according to the whitepaper. Functional safety, electromagnetic compatibility and secure wireless connections are among the issues identified as important for connected and automated vehicles.

The digital services introduce another integration layer. The concept assigns roles to mobility, data-analysis and transaction platforms, with the aim of supporting transport coordination and use-based settlement among participants. In practical terms, the vehicle’s operation is presented as part of a wider ecosystem involving vehicles, services and stakeholders—not simply as an isolated product.

Different pods require different system requirements

Rinspeed’s use cases include a two-seat passenger pod and a cargo pod for deliveries. Those applications place different demands on the vehicle. A passenger pod needs an appropriate cabin climate and occupant comfort; a cargo pod may need heating or cooling for goods. The whitepaper also describes a possible mobile charging pod as another use for the platform.

Thermal management is one example of how a shared chassis concept still needs application-specific solutions. For the passenger pod, Eberspächer supplied heating and cooling hardware with an independent energy supply, separate from the traction battery. For the cargo application, the described system includes heating and cooling units and containers. The concept therefore pairs a common modular idea with equipment tailored to each pod’s function.

Other systems support the passenger experience, including adaptive lighting, cabin monitoring, seat heating and cooling, and a wide digital display. These details reinforce the need to define interfaces and system responsibilities across the complete vehicle, even when the body configuration changes.

What industrial automation teams can take from microSNAP

MicroSNAP is a concept vehicle, not a specification for a production line or a validated deployment model. Still, its approach highlights several useful considerations for teams designing modular automated systems:

  • Design around the exchange process. If modules are intended to be swapped, the robotic station and handling sequence are part of the system architecture.
  • Separate shared functions from application-specific ones. A common platform can support different uses, but passenger and cargo configurations may require different equipment.
  • Plan for technology lifecycles. The concept distinguishes longer-lived bodies from chassis hardware that may wear or age sooner.
  • Account for integration beyond mechanics. Controls, software, sensors, connectivity, safety and cybersecurity all contribute to the operation of a connected modular system.

A systems-level view of future mobility

Rinspeed’s microSNAP presents modularity as a coordinated combination of vehicle architecture, robotic handling and connected services. Its automated mating station demonstrates how robotics can enable a design in which chassis and bodies are not permanently joined. Meanwhile, the range of passenger and cargo applications shows why modularity does not eliminate the need for tailored thermal, control and user-facing systems.

For industrial automation decision-makers, the practical implication is to evaluate a modular platform as a complete operating system: the modules, the automation that exchanges them, and the digital and safety functions that support their use. That systems-level perspective is essential when translating a flexible concept into a workable automation strategy.

Access Official Technical PDF

About The Author