 Code -> Vehicle 1
We were there, people from your team approached one of a corporation's brands. Perhaps you're there too, in a subgroup that deals with the powertrain and, subsequently, the chassis. It's a wonder how the other three
groups might be divided.
Let's put it a bit more bluntly. Your group may only be a guest at one brand in the small car segment and one in the highest class. Where do you position your offering then? Would you rather offer a particularly ambitious
solution that would be met with incomprehension by the small car market?
After all, you or your group want to achieve synergies or savings. Or are you trying to promote a simpler chassis for the luxury brand? You can be sure of a certain degree of suspicion on both visits.
However, not all circumstances are against you or your group. This has to do with how your overall organization got to the individual employeesEven in Germany, programmers aren't exactly hanging on the trees and are
just waiting to be picked.
The high number initially deemed necessary must have been perceived as a major challenge. Recruitment efforts must have also been directed at those already employed by the company, and perhaps a significant
number like yourself were attracted by the new challenges.
Such employees are, of course, indispensable when it comes to convincing those responsible for the respective brand to make a particular change, because you are picking along those who originally come from these
very factories.
No, we haven't finished with the problems yet, but we'll stick with the chassis section to make it easier for you to understand. So, there was a new idea regarding the chassis that either saves money, making it suitable for
small cars, or offers additional features for the luxury class.
However, you are responsible for the software, although all parts of the chassis are connected to hardware. Now let's assume, as in most cases, that your company doesn't produce the part itself, even if it requires only
minor modifications.
Now it might be easy to get the supplier(s) to change the design, not just you or your team alone, but together with experienced engineers from the sector. The problem is, almost every part of the chassis requires software.
Well, that's not the case with steel suspension, but it is when it comes to vibration dampers these days. Even the fundamental distinction between active and passive dampers is of little help here, since you can safely
count the latter as steel suspension, as they are generally completely non-electronic.
But that doesn't protect you from having to leave your nest as a software programmer, because there's plenty of room for improvement with active dampers. Their adjustability can, for example, apply to just one stage or to
rebound and compression separately. Does the system only have basic damping adjustability or dynamic adjustability?
This goes so far that a chassis interacts with other systems and learns very early on during driving about challenges detected by a camera. You can probably guess that there are a lot of nuances lurking here, including
with regard to a very fast response.
| 
