SystemWeaver and RemotiveLabs announce collaboration

Posted: June 18, 2025

In this article

Sara Hulander

Integrating SystemWeaver and RemotiveLabs for Seamless SDV Development

SystemWeaver and RemotiveLabs are proud to announce a strategic collaboration that connects structured systems engineering with agile, simulation-first software testing. This integration is designed to accelerate SDV development by eliminating silos between system architecture and software verification. The result is a development process that allows teams to move faster, test earlier, and maintain full end-to-end traceability.

Bridging System Architecture and Virtual Testing

As the automotive industry shifts toward software-defined vehicles, the gap between system design and implementation continues to create inefficiencies. System architects define topology, communication and behavior, while developers iterate and test, often in separate environments. This fragmentation leads to late-stage integration issues, slower feedback cycles, and limited traceability.

By combining SystemWeaver’s structured approach to requirements and architecture with the virtualization capabilities of RemotiveLabs, engineering teams can begin meaningful testing from day one. Design intent flows directly into test execution, supported by traceable and actionable feedback throughout the development lifecycle.

Integrated Engineering for SDV development

“Companies are investing heavily in software, but system and software disciplines often remain separated,” says Magnus Carlsson, VP Expert Services at SystemWeaver. “Through this collaboration, we make it possible to begin meaningful testing earlier, even before ECUs exist.”

“At RemotiveLabs, our mission is to left-shift key engineering activities, enabling teams to test and iterate long before hardware exists,” says Per Sigurdson, CEO. “By integrating with SystemWeaver we bridge the gap between software PLM workflow and agile execution in a natural and scalable way.”

 

Key Benefits for OEMs and Tier 1s

This joint solution enables development teams to:

  • Connect system design and software testing to ensure alignment between design intent and implementation
  • Start integration testing early, even without hardware, across both current and upcoming ECUs
  • Maintain end-to-end traceability from requirements to test results
  • Enable true platform reuse by linking software and testing directly back to the system architecture, keeping both worlds up-to-date

Why This Matters

SDV development requires both speed and system-level precision. Integrating structured design with virtualized testing is no longer optional, it’s a must to be competitive. This collaboration provides a scalable solution that supports early validation, continuous traceability, and true cross-discipline collaboration.

You may also be interested in

  • Subsystems and meta models

    White Paper: Subsystems, Meta-Models and Architecture

    Download this White Paper as a PDF Executive summary The meta-model supports the architecture without defining it. Clear, cohesive subsystems with explicit interfaces are what make model-based systems engineering usable at scale. This white paper distills ten practical insights drawn directly from SystemWeaver experts and practitioners, both at SystemWeaver and customers to SystemWeaver. [...]

  • Marcus and Anders interview

    5 Realities of AI in Modern Cybersecurity

    Every vendor in security claims AI changes everything. Ask the engineers actually building these systems and a different story comes up: a context gap. The AI returns a threat analysis that reads well and sounds confident but has little connection to the product.  That is where a recent conversation with Anders Hallgren and Marcus [...]

  • Strong engagement at the GAIA workshop: Trustworthy AI in Systems Engineering – Keeping Control and Traceability

    The central question during this workshop was one that matters more as engineering complexity grows: "How does AI fit into systems engineering without eroding control, traceability, or engineering accountability?" The answer is not to add AI as a black-box layer on top of engineering work. It is to ground AI in structured engineering context, [...]