The development and processing of software components throughout their entire life cycle is carried out on an ALM (Application Lifecycle Management) platform, while the hardware is managed in the PLM (Product Lifecycle Management) environment. As a result, component information and the associated software components are stored in separate systems. There have been many reasons for this in the past, e.g.
- different methods and procedures,
- different structures of the data and metadata to be processed,
- different workflows, and
- non-uniform requirements for comprehensive processes such as interdisciplinary configuration management (Cross Domain Configuration Management).
But the separate handling of hardware and software components leads to the well-known “silo thinking”, e.g. notifications of changes that affect software and hardware simultaneously are not being synchronized between the two systems. This means that highly error-prone, manual processes have to solve the underlying problems – at the cost of quality and efficiency.
So how could the two worlds ALM and PLM be linked transparently and comprehensibly to ensure quality and consistency and to increase the efficiency of joint development? An omniscient “ALM-PLM system” is not realistic because of the enormous migration effort, the complexity and the major differences between the two disciplines. In fact, the disciplines ALM and PLM demand a holistic approach to integrate their respective data and processes with the help of a common federal backbone. This process does not take place in one step, so an adjusted catalogue of measures must be defined depending on the desired target state in the maturity model and the current actual situation.