Engineering Transformation


Today’s consumer expectations on comfort, safety has increased, while Government regulations and compliance standards puts pressure on emission control or mileage.

While it may also open up new lines of business for the industries, it is also fueling an increased innovation.

Complex developments like connected systems and driverless cars have led to complex software architecture. This is challenging traditional methods of development in an organization.

Adding to all this is many execution paths in the product development like the mechanical, Electrical, Electronics and the S/W development have different cycle times adding to the woes of the organization. Mechanical centric products have now been “SOFTWARED.”

Some of the problems plaguing the organization are:

  1. Old methods of S/W architecture and development is proving to be insufficient
  2. More features need to be packed in a limited set of memory available
  3. Unable to manage the project risk with business risks
  4. New disciplines like model based development
  5. Pressure from business to release new variants faster
  6. Missing strong insight into the overall project states
  7. Chaotic communication between various disciplines

However, addressing efficiencies in small pockets is not helping much so what should organizations do?

A holistic approach looking into all the aspects of the problem is probably the solution, because addressing only one part of the product development would not help.

Organizations need to look at the problem on a larger plane and apply various methods to bring the needed transformation. Let’s look at the various aspects of this Engineering transformation.

This advocates just not to look at improving software engineering, but also the systems Engineering aspects. For example, looking at various methods for bring variant management at the software level does not completely bring the needed improving, while bringing in PLE along with variant management at software layers.

In order to increase the speed of introduction of new variant/ product to the markets, usage of model driven development would be advised so that the failure rate of new product development is reduced and product being shelved at the later stage could be avoided. The traceability of requirements to models become important, so that there is closed loop usage of simulation right from system level and generate code helps out down development time by at least 40% and reduces design defects by up to 60%.

Managing requirements in a multi-disciplinary context is a challenge. An efficient requirement model like an East- IDL which helps to record and manage all the aspects right from sub –systems, safety conformance and timing related aspects will be the key. This should serve as the single source of truth for further developments. Having all the requirements related to different parts of the system as a single source is a journey well started.

In order to manage the various aspects of software engineering efficiently and being able to track the progress of a program as and when it occurs will be key lever in efficiency improvement. Usage of ALM (Application lifecycle Management tools) becomes crucial. Some of the key benefits of using a right ALM toolset could result in the following benefits:

  • A tool chain covering and linking the entire software lifecycle
  • Harmonized use-cases across SW engineering
  • Supporting different methodologies (SCRUM, Kanban, waterfall)
  • State-of-the-art communication (feeds, subscriptions, chats)
  • Providing information and status of project artifacts in real-time
  • Moving from gut driven decision to a data driven
  • Risk management and planning
  • Quicker time-to-market by streamlining development process
  • Shorter development cycles and improved productivity
  • Increased collaboration between business and engineering teams
  • Adherence to standards like ASPICE and ISO26262
  • Continuous improvement of processes for better releases
  • Derive and deliver variants smoothly
  • Connected Development

Combining the ALM features and applying it to the systems Engineering as well could lead to a development environment that not only connects the various disciplines in the organization but also enabling smooth communication and breaking the process barriers.

Hence with this approach organization could move from SILO engineering to collaborative Engineering.

We at Bosch automotive have been embracing this new way of working and hope to reap improvements in efficiency and improve the communication barriers across the BUs


Contact for more: Veena B M