As one of the first steps in the development of innovative systems, the customer's requirements are visually represented in a system architecture elaborated in an interdisciplinary cooperation.

This first representation of a possible system solution represents an essential communication tool with the customer and between the departments and will be refined and detailed in the further development process. Thus, the system architecture is a central document in our development projects based on which the developments in the individual departments start. New findings from the departments are included in the system architecture throughout the project phase.

Visualizing customer requirements in a system architecture

Basically, the approach of creating a system architecture is chosen in all projects in vehicle/system development, regardless of vehicle class and vehicle application. ​​​​​​​This means that the system architecture is used as the basis for developments in passenger vehicle, commercial vehicle and special vehicle projects. It is further used in the following developments of innovative mechatronic technologies regardless of the vehicle class:​​​

Drive system concepts can be built up from individual technologies or from a combination of different technologies, so-called hybrid systems. In general, fuel cells, battery technologies, electric drives / axles and internal combustion engines are used in various arrangements and combinations.

Considering developments of new concepts in the field of chassis systems, braking and steering systems in different variants are primarily understood. These variants range from conventional braking and steering systems to more complex systems such as brake-by-wire and steer-by-wire.

The system architecture as a tool is also used in development of driver assistance systems, in which the components of mechatronic systems, sensors, control units and actuators and their interactions with other vehicle systems are represented.

Based on the system architecture further activities are going to be started or continued in the project. The further tasks and activities vary depending on the scope of the project and the development goal.

The following are an excerpt of the activities that can be arranged after or in parallel of the elaboration of the system architecture:

  • Component research and supplier coordination
  • Development of the EE architecture (HV and LV)
  • Elaboration of a CAN communication concept
  • Development of the thermal concept
  • Function development and functional safety considerations

Further Steps based on System Architecture