Access Official Technical PDF

Share Summary:LinkedInEmail

The Rinspeed Oasis concept car offered a 2017 vision of connected urban mobility: a compact electric vehicle designed to drive autonomously, support different users and adapt its interior to work, travel or leisure. For industrial automation professionals, its value is not as a production-ready blueprint, but as a case study in connected vehicle architecture. The concept shows how computing, sensing, communications, user access and safety must work together when a product combines many functions and stakeholders.

Connected vehicle architecture begins with integration

Oasis was conceived as more than an electric runabout. Its proposed functions included autonomous driving, passenger services, digital access for sharing, and an interior that could shift between a driving space and a mobile office. The vehicle could also be configured for uses such as passenger transport or deliveries. That breadth makes the concept relevant to system integrators: adding features is only part of the challenge; the subsystems must exchange information and operate coherently.

The concept brought together technologies from multiple suppliers. A flexible computing architecture based on HARTING’s miniMICA was intended to connect different modules for functions such as computation, communications and sensor connectivity. The stated aim was to adapt the system configuration to the requirements of a particular vehicle user. This modular approach reflects a familiar engineering principle: separate functions into components that can be combined for different applications, while maintaining a planned interface between them.

In industrial projects, that principle is useful when equipment must support changing processes or operating modes. Modularity can make it easier to select and configure components for a defined use case. It does not, by itself, guarantee interoperability or simplify commissioning; those outcomes depend on how interfaces, data flows and system responsibilities are designed.

Sensor fusion and communication support autonomous operation

Oasis was described as using sensors based on NXP technology to build a 360-degree view of its surroundings. The vehicle would combine this information to calculate a driving maneuver, while vehicle-to-vehicle communication could extend awareness around corners or obstacles. This illustrates the role of sensor fusion: a system uses information from multiple sources to form a picture that supports a decision.

For automation engineers, the broader lesson is that sensing is not an isolated subsystem. Sensor data must be collected, communicated and interpreted in the context of the system’s operating conditions. In the Oasis concept, this chain extended from environmental sensing to the computation of a safe maneuver. Communications also mattered beyond the vehicle itself: intelligent traffic management and vehicle-to-vehicle links were presented as ways to support traffic flow and share relevant warnings.

These capabilities also increase the importance of defining what information is exchanged, where it is processed and how the system responds when data is incomplete or unavailable. The press materials describe the intended functions, but do not provide detailed fault-handling logic or performance specifications. Those details would be essential in any implementation.

Cybersecurity and functional safety are system concerns

A connected vehicle links software, electronic control units, sensors and wireless communication. The Oasis materials therefore highlighted several safety topics: secure wireless connections, interoperability, electromagnetic compatibility, cybersecurity and functional safety. BlackBerry QNX was identified as supplying an integrated software platform for self-driving vehicles, while DEKRA’s contribution was described in terms of testing and certification expertise.

The important point for technical decision-makers is that safety cannot be treated as a final inspection of individual components alone. Interactions matter: devices must not interfere with one another, software and hardware must function as a system, and communications with the outside environment introduce additional considerations. The concept’s emphasis on testing both components and the vehicle as a whole reflects this system-level view.

For connected automation projects, a comparable review should consider the complete chain of operation: data acquisition, processing, communication, control action and the consequences of malfunction. The Oasis materials do not specify a complete safety case, but they make clear that connectivity and autonomy raise concerns beyond basic feature integration.

Digital access turns a vehicle into a shared asset

Oasis also explored how digital access could support shared use. Huf’s SixSense system was described as transferring time-limited usage rights digitally, allowing an authorized user to unlock and start the vehicle with a mobile device. The concept distinguished between different permissions: a driver could receive broader vehicle access, while a delivery user might only be authorized to open and close a delivery compartment.

This is an example of access control being tied to a service model, not just to a physical key. It connects identity, authorization and the intended task. For industrial operators managing shared equipment or mobile assets, the same design question is relevant: who may use an asset, for what purpose and for how long? The concept demonstrates the importance of matching access rights to roles, although its materials do not establish how such a system would be deployed in an industrial environment.

Designing systems around changing use

The Oasis concept combined an electric powertrain, flexible computing, connected services, sensor-based driving functions and configurable user access. Its proposed business models depended on treating the vehicle as an asset that could serve different users and tasks over time. That makes the case study especially useful for teams planning systems that must accommodate evolving requirements.

Three practical questions emerge:

  • How will modules work together? Define interfaces and data responsibilities before adding functions.
  • How will the system make decisions? Trace information from sensors and external communications through processing to the resulting action.
  • How will access and safety be managed? Consider user permissions, system interactions, cybersecurity and functional safety as part of the architecture.

Conclusion: treat connectivity as an architecture decision

The Rinspeed Oasis was a concept vehicle, not evidence that every proposed feature was ready for deployment. Its practical significance lies in the integration challenges it brought into view. A connected vehicle architecture must account for modular computing, sensor fusion, external communications, secure access and system-level safety together. For automation engineers and technical decision-makers, the lesson is straightforward: define how components, data and permissions relate to one another early, so that new functions fit into a coherent and supportable system.

Access Official Technical PDF

About The Author