Experience

Systemite AB

• Germany
• Business Consulting and Services

• Application Engineer

  • Sep 2020 - Present

  Working strategically with the long term development of Systemite, which includes balancing sustaineability with expansion of business and operations, which can be a challenge in a self-financed company competing with companies 100 times larger.

• Systemite Expert in Automotive Cybersecurity Solutions

  • Sep 2020 - Present



Volvo Construction Equipment

• Sweden
• Machinery Manufacturing
• 700 & Above Employee

• Process and architecture expert

  • Feb 2007 - Jun 2011

  Working with process, methods and architecture aspects of the E/E development process, particularly regarding large scale deployment of SystemWeaver. Working with process, methods and architecture aspects of the E/E development process, particularly regarding large scale deployment of SystemWeaver.



Volvo 3P

• Senior Consultant

  • May 2001 - Dec 2005

  Senior Consultant System Architecture and Process investigations Responsible for general architectural issues in concept development for new E/E Architecture. My assignment at Volvo in 2001 was to resolve systems related issues of the TEA2 electronic architecture of the soon-to-be-released FH truck. We had already presented the SystemWeaver product, and had a mutual idea that my work at Volvo could be beneficial for both companies regarding SystemWeaver, to build trust and understanding, although I naturally had to separate the different concerns. When the FH had been launched I got the chance to participate in the development of the new generation of electronic architecture, where I worked with great people, like Björn Villing. I was assigned responsibility for general architecture concerns. The methods in the architecture group was based on systems engineering principles, and for every aspect of the architecture several alternative concepts had to be evaluated. At the end we managed to derive a coherent E/E arcitecture, most of its principles surviving even until coming generations, including support for AUTOSAR, a truly distributed architecture with shared resources, an advanced mode management system, and more. Volvo had realized by that time that they would need tool support in order to manage system aspects of the new architecture, and in parallel with the architecture development Volvo started an ambitious tool selection project. At the end, after trying and evaluating virtually all alternatives at the market, the final choice was SystemWeaver. At that time it might have seemed a risky choice but now 10 years later the market success and continued use at Volvo has proven the case. I have continued to cooperate with Volvo in many projects since, both SystemWeaver related and not. Show less



Mecel AB

• Sweden
• Motor Vehicle Manufacturing
• 1 - 100 Employee

• Senior Consultant

  • May 1996 - May 2000

  Research in the automotive X-By-Wire research project, Consultant in Automotive E/E Systems projects, Product Owner of the Butler system development tool. At Mecel I met Mikael and Claes, with whom I would later start Systemite. The X-By-Wire was my first European research project, with a lot of travels and contacts with research organizations, and brilliant individuals, many of which I've had a lot of collaboration until today (2014). I was also involved in the standardization of OSEK/OS. At the end of the X-By-Wire project I got involved in the development of the electronic system of the first SAAB 9-3, where Mecel supported in various roles, including architecture and methods development. At this time Mikael had long had the idea of component based software development for embedded systems. This idea may seem similar to ideas like CORBA, but the embedded real-time environment means that it has to be implemented in a totally different way, supporting things like strict timeliness, static-cyclic sheduling, scheduled message sending rather than method calls, etc. (This was many years before AUTOSAR) In the SAAB project I saw the opportunity to implement the ideas Mikael had, combining them with my ideas of a collaborative development platform with support for graphical views, configuration management and versioning. At Ericsson I had seen how difficult it was to maintain both a model representation and a document based representation of a system at the same time, so to the tool solution, which we called Butler, I added capabilities to support specification and test, and the capability to generate any needed documentation. (This was many years before SysML, and UML did not include support for components until 2.0) To implement the tool I turned to the only one I knew who could do all this on a close-to-zero budget: Olle at Ergodata. In 2000 we got the chance to start a company based on the ideas of Butler: Systemite. Show less



Ericsson

• Sweden
• Telecommunications
• 700 & Above Employee

• Software Developer

  • Jan 1993 - Apr 1996

  Real-time Software Development, Software Quality Assurance, Project Manager for Electronic Radar and Radio projects. Sales Engineer. My second period at Ericsson started with embedded software development, with Ada and C on commercial hardware, rather than the Pascal/D80, EriPascal and custom H/W of the Eighties. Got the SQA responsibility of the EriEye project (Airborn Early Warning and Survillance), which was an experience in many ways. This was my first involvment in highly formalized processes and documentation (MIL-STD), that would be followed by more in the years to come. Worked as team leader for a group responsible for the Network Management of an airborn digital radio system, similar to Link 16. There were many great persons in that project.This work was also very interesting, including development of processes and methods, like scenario based specifications, and tools like SDL/SDT, and code generation. Got the chance to work with the US based partner in the project, on processes and methods. When Ericsson did not win the contract I as everyone in the project had to look for other alternatives. Many went to the growing mobile communication (cell phone) development at Ericsson, but I happend to read an article about the network-based elektronic architecture of the then new BMW 850, and at the same time an ad from Mecel where they were looking for people to work with Automotive electronic systems... Show less



Defence electronics

• 1 - 100 Employee

• Software Developer Mission Planing System

  • Feb 1996 - Mar 1996

  At the end of my career in defense electronics I had a strange, almost surreal experience. I became the sole developer of an abandoned mission planning project, where the simulation parts didn’t work. I had experience from earth models and geodetic transformations so it wasn’t too hard to figure out what was the problem. At the end all I had to do was to replace a couple of plus signs with minus signs to make it all work! At the end of my career in defense electronics I had a strange, almost surreal experience. I became the sole developer of an abandoned mission planning project, where the simulation parts didn’t work. I had experience from earth models and geodetic transformations so it wasn’t too hard to figure out what was the problem. At the end all I had to do was to replace a couple of plus signs with minus signs to make it all work!



ErgoData (Sweden)

• Senior Consultant

  • Jan 1990 - Dec 1992

  Software Development Databases Real-time Systems At ErgoData I got the chance to work with persons like Håkan Edler, Olle, Tarja and more. (My short period at ErgoData would mean a lot almost 10 years later, for the development of the Butler and SystemWeaver products, which development were decommissioned to Ergodata) ErgoData was an advanced company already then, everyone working on (Apollo) workstations, had their own Internet class C domain, source code license of Unix etc. My first e-mail account was set up in late 1989! At ErgoData I had my first experience of relational databases, and even had the chance to implement my own RDBMS, which was offered as a low cost embedded database alternative to the market-leading solutions. Implemented a database connected tabular calculation application that turned out to be maintained still after ten years. (Got to see the code, where a change note told that some other "Jan S" (Sörfeldt) had been working on my code after all those years, almost a historic perspective to me...) I also had a very interesting experience in CASE tools where we evaluated tools like ROSE and HOOD. I and Håkan Edler had a business trip to England (Macclesfield) where we discussed the option of becoming agents of the IPSYS/HOOD solution. Still remember all details of this trip, persons like John and Rebecca, the Mill and more. Unfortunately we could not take this chance, but I would return to the tool business later on. Show less

• Software and Systems Developer

  • Sep 1985 - Dec 1990

  Real-time software development, Systems Engineering, Hardware Development Ericsson Radio Systems AB, Ericsson Microwave Systems AB (now Saab Microwave Systems). Ericsson at the time was a very nice place to start a working career, with plenty of technically challenging projects, peered with skilled colleagues and in-house resources. Much of this dealt with things that I hadn't studies at school, like working in large projects, large scale Systems Engineering and so on. One of the most interesting things I did was to completely re-design the antenna control of a phased array antenna of an airborn surveillance system, at a late stage of the project. This included the first use of a new integrated bit-slice processor design, two executing in parallel, micro coding, designing a double port memory, negotiating (rare) rack space with other sub systems, comissioning parts of the software design to an Ericsson department in Lund and other extremely interesting engineering tasks. I remember that the pipeline of the control included a varying number of stages, up to 12 or 13, and kneeping track of all stages was a challenge, especially during radar mode changes where the (soft) pipeline was reconfigured, but no slack could be afforded. This was well before the Web, and there was little time for litterature studies, so we had to re-invent a lot of solutions like non-blocking communication, management of large state machines and so on. Show less