Vision

From device silos to software-defined, learning vehicle architectures.

From device silos to learning vehicle architectures

OSxCAR accelerates the transition to open, modular and intelligent Software-defined Vehicles – secure, efficient and interoperable.

View Demonstrators Full Version

Key Points

  • Architectural Freedom: Software reusable and portable – independent of hardware & OS.
  • Realistic Testing: Development "as in production systems" instead of artificial silos.
  • Efficiency & Impact: Shorter cycles, better utilization, data-driven decisions, measurable quality.

1) Open & modular

Clear interfaces and interchangeable components keep systems adaptable rather than fragile.

2) Production-ready

Testing on real target architectures – reproducible, scalable, remote.

3) AI-supported

Learning from data: Optimization of latencies, placement and resources.

4) Secure & interoperable

Isolated execution environments and standards create trust and speed.

The Vision – the Details

Why now? The automotive industry is transitioning from hardware-centric device silos to Software-defined Vehicles (SDV). This transformation often stalls at three points: heterogeneity (architectures, languages, toolchains), high integration costs and long test cycles. OSxCAR addresses exactly this: We create an open, scalable foundation on which development teams can experiment faster, maintain production proximity and feed learning effects from data back into the architecture.

Our approach in one sentence: Open interfaces, production-ready test environments and AI-supported optimization – integrated into a common, secure SDV ecosystem.

What changes specifically?

Today (Status Quo)

Highly encapsulated devices, many special paths, test environments that deviate from production, long conversion times & resource conflicts, gut-feeling decisions, integration risks & vendor lock-in

Tomorrow (with OSxCAR)

Modular software components with clear contracts, production-ready tests on real target hardware, remotely reconfigurable bench with time-sharing, data/AI-supported architecture and placement decisions, standards & interoperability as default

Architectural Freedom

Portable components, clear contracts, reduced coupling – faster iterations instead of large project risk.

Realistic Testing

"What runs on the bench, runs in the vehicle": Fewer media breaks, more evidence.

Efficiency & Quality

Shorter cycles, higher utilization, better test coverage and reliable quality metrics.

Interoperability

Standards & best practices as accelerators – cooperation instead of friction losses.

The Path Forward – Roadmap

Phase 1 Establish production proximity

Tests run on target hardware; setups are repeatable, documented, remotely accessible.

Phase 2 Scale & share

Resources are shared, topologies are switched, teams work in parallel across locations.

Phase 3 Learn & automate

AI helps optimize latencies and placements; architectural decisions become evidence-based.

Guiding Principles

  • Simple over complex: Solutions must remain maintainable.
  • Contracts over implicit assumptions: Interfaces are explicit, versioned, testable.
  • Security from day 1: Isolation, least privileges, traceable artifact chain.
  • Measure, don't assume: Quality and performance are made visible.
  • Prefer standards: Interoperability beats special paths.

Impact & Metrics (Examples)

  • Time-to-Integrate decreases; Time-to-Evidence for architectural decisions is shortened.
  • Test coverage and mutation score increase; rework rate decreases.
  • Bench utilization up, conversion times down.
  • Ecosystem maturity: Share of standards-compliant components & interfaces.

For Development Teams

Same artifacts on bench and target hardware, reproducible environments, clear contracts.

For Architects

Safely test variants, measure assumptions instead of guessing, justify design decisions.

For Management

Transparent metrics, faster milestones, reduced risk – path to scaling.

What OSxCAR is not

  • Not a proprietary lock – standards and openness are part of the goal.
  • Not a feature fireworks – reliable core competence takes precedence over "nice-to-have".
  • Not a laboratory island – production readiness is the standard, not the exception.

Continue: Funding / Work Packages & Milestones