The IT infrastructure of the company is quite heterogeneous and far from being integrated. It consists of different CAD systems for mechanical design, Altium for E/E development with only a rudimentary integration into Agile e6 PLM and various tools for software development which are linked to a homegrown Application Lifecycle Management (ALM) environment. The company has made a great effort to integrate the tool chain to comply with ASPICE and other standards that require traceability from requirements classification to test and validation. “Nevertheless, software development is still separated from the PLM world”, as András Balogh and Patrick Schäfer, IT Architect Engineering IT explain.
Starting with a proof of concept
With the help of PROSTEP the project team elaborated a long list of requirements to select a short list of PLM vendors with whom the company will start a proof of concept early next year. „We have defined test cases along the whole product lifecycle, starting with Requirements Engineering up to Functional Modeling and regarding the Bill of Material (BOM), a Multi-BOM Management,” explains Brandner. At present the company is handling just one (Manufacturing) BOM in the PLM system, “which means a tremendous effort for the engineers as every change in the supply chain, in logistics or in manufacturing falls back on them”, says Xander.
After the proof of concept, thyssenkrupp Presta will do a longer pilot phase using the old and new PLM systems in parallel. The idea is to migrate functional areas like Requirements Engineering or Master Data Management (MDM) to the new environment and roll it out globally to all domains involved in the process. “A migration by projects or sites would cause to much disruption in the organization as there are many legacy data being reused in new projects,” explains Brandner.
A common Requirements Engineering from the system level down to the domain-specific requirements will be one of the key functions of the new PLM solution and an important enabler of MBSE. Customer requirements are generally managed in DOORS, but – except for hardware and software – there is no traceability to design an implementation. For software the company uses a proprietary AutoSAR tool integrated with requirements management and test specification, as Balogh says: “Ideally, we would like to use the same environment for the management of customer requirements, internal system requirements and software- and hardware requirements to ensure cohesive traceability over the whole process down the (left side) of the V-model.”
“The biggest challenge on the technical side will be the integration of the different tools into the new Presta System Lifecycle Management Backbone”, as Brandner continues. thyssenkrupp Presta will probably have to replace some of the existing tools that might not be designed for easy integration. Even bigger will be the challenge to adapt the organization to the new ways of cross-domain collaboration and communication which might require changes in responsibility and new roles. “It does not make sense to work in the new environment with an organization which is 30 or more years old;” concludes Balogh.
* SysLM or SLM in thyssenkrupp Steering specific wording.