Part One: First Steps

Posted: April 28, 2025

In this article

After almost 20 years at SystemWeaver, I believe it can be interesting to look back and to reflect upon how we, as well as our environment, have changed over time.

Looking back, it is easy to see that the insight from the founding fathers that the introduction of software to an automotive industry where processes and development tools were based on mechanics would be a game changer was correct but that the insight was long before its time.

First steps

After initially working from within Mecel (now a part of Aptiv), SystemWeaver was created in 2000 to address the growing software problem in automotive. However, management was not yet aware of the gravity of the problem and being first in a new market isn’t necessarily an advantage for a small company.

We were fortunate to attract interest from early adaptors at both AB Volvo and Volvo Cars and thanks to this we were able to launch the world’s first System Engineering tools for Software.

Lesson: Everyone needs sponsors to get going

You may also be interested in

  • Driving car in mist

    Driving the Future of Automotive Development: How SystemWeaver Revolutionizes Software Product Lifecycle Management

    The automotive industry is undergoing a profound transformation, driven by the growing importance of software in vehicles. As the industry shifts towards Software Defined Vehicles (SDVs), the need for robust, comprehensive software product lifecycle management (PLM) solutions has never been greater. SystemWeaver is at the forefront of this revolution, offering a suite of tools and [...]

  • Grounded in AI System Engineering

    Grounded AI in System Engineering: Letting the SystemWeaver Model Do the Heavy Lifting

    We often see AI initiatives in engineering begin by pointing an LLM at documents, while the richest context – the structured system and safety data in MBSE/PLM tools – ends up as an afterthought. Our experience in safety-critical development is that the real asset is something else entirely – the system model you already keep [...]

  • How automotive software development i changing blog image

    How automotive software development is changing, and what that means for standards, architectures, and long term flexibility

    In this interview, Anders Hallgren, VP Product at SystemWeaver, shares his perspective on AUTOSAR, the shift toward service based communication, and why technology agnostic system design is becoming increasingly important for OEMs navigating rapid change. What is happening with AUTOSAR? From what we see through our participation and through our customers worldwide, the Classic Platform [...]