Abstract
Flexibility, reactiveness and reliable estimations of development efforts - all these are key factors for competitiveness. Bus this aligns with a daily trade-off in simulation - work attractive solutions out under time and cost pressure and -agile" boundary conditions.What we also experience regularly are the barriers between the responsible entities with respect to tool chain, semantics and workflows. An approach to technically and process-related bridge these issues is to systematically embed simulation processes into the product development.
3. content
The PLM understanding differs considerably from the needs of simulation engineers. Many existing solutions in the market have their origin in the PLM-world and try to integrate SDM functions like processes, data lifecycle, collaboration and many more. Our market feedback here is that simulation engineers do not feel comfortable due to high system rigidness or tool complexity.
The presented approach is to integrate a dedicated SDM system into a PLM system. Thus the project benefits from PLM structure and organisation on the one hand; on the other hand we can provide a simulation fitted environment and combine the advantages of both worlds.
In order to optimise the interaction between the project partners (i.e. design - simulation) a second key idea is to provide a "box strategy". By clearly specifying the required content of a task (box) we minimise information loss and friction between the process partners. The integrated system will also support the communication between the partners and provide templates for an easy task creation. Thus the handover of a task can easily be standardised accompanied by a growth of efficiency and quality.
Another benefit of this approach is the user acceptance of a system. Simulation engineers need very specific information during their daily work. Their data volumes
exceed by far the volumes of CAD or test engineers. The responsiveness of the system is a key factor for acceptance and efficiency. Centrally providing knowhow, workflows and methods is one necessity. The freedom to escape and try out simulation methods outside of the system or fixed workflows is another one. This is all taken into consideration in order to provide maximum flexibility for the respective needs of the enterprise and the single engineer.
4. perspective
Complexity of future products is increasing continuously. Key aspects like loT, Industrie 4.0 and Digitalisation lead to more and more integration of hardware, software, electric, electronics and services. Business models change and require integrated development systems. The future will be a combination of best practice tools ideally available under one central GUI. Thus successful companies will work in aligned and structured processes provided by flexible and highly customisable systems. The integration of newest virtual technologies will end up in both space and power for innovation and efficiency as well as cost reduction.
