Characteristics of a future mechatronic product creation process in the automobile industry

Transcription

1 Status 08. Mai Characteristics of a future mechatronic product creation process in the automobile industry ProSTEP Symposium Berlin May, 13th 2009 Ralf Lamberti, Daimler AG Ralf Lamberti, Robert Winterstein Daimler AG, Olivier Sappin Dassault Systèmes

2 GR / PPP / Status 08. Mai Overview Motivation and Trends Vision and Paradigm Shifts Implementation within a Demonstrator System Template Collaboration System Simulation Community-Driven Innovation Conclusion

3 GR / PPP / Status 08. Mai Global Trends affecting the Automotive Industry Environmental Sustainability Changing Markets Demographic Changes Social Behaviour CO 2, global warming Shrinking reserves, Peak-Oil Alternative energy-sources, Biofuels, Solar Consolidation in and stagnation of triad-markets Growth in emerging markets, BRIC Increasing Urbanization Silver Markets and Third Agers Rising Affluence: more and wealthier rich persons Social Net, Web 2.0, Communities Empowered Customers, Savvy Consumers Economic Downturn Silicon and Steel Increasing competition Overcapacities Cost pressure Increasing E/E- and SW-usage, linking with Mechanics to Mechatronics Increasing product complexity

4 GR / PPP / Status 08. Mai Facing the Challenges Solution Approaches Business Model Innovation New mobility concepts, e.g. car2go New sales channels, e.g. Mercedes Young Classics Project Better Place Open source car, OSCAR Social and Organizational Innovations Diversity International and intercultural cooperation models Home offices and alternative work models Product Innovation Process Innovation New and connected driving assistance systems Green Technologies: alternative powertrain systems, e.g. electric vehicle, fuel cell, hybrid, downsizing Green Luxury Diversification of products into small niches Standardization and reuse in products, e.g. module, platforms, cross-vehicle architectures Complexity management Engineering domain integration Supplier and customer integration

5 GR / PPP / Status 08. Mai Trends in IT Tools for engineering CAD-System Authoring Systems PDM/BoM IT-Infrastructure CATIA V5 Parametric part Modeling Associativity Isolated Aspects Mechanics, Kin. Req., Functions EE, SW, Logic,.. PDM: Smaragd BOM: Dialog CMI: CATIA Interf. Monolithic Authoring and PDM Systems On the Way to Future Next Generation Systems Engineering PLM Platform based Collaboration Complete digital System Representation Associativity Linked Product Model Next Generation PDM PDM Backbone with Domain specific TDM Next Generation IT Service Oriented Architectures Role based Workplace

6 Trends in development and engineering methodology Development within Product Domains User community innovation Alliances and Outsourcing Low Cost Countries Knowledge Integration Function Orientation Standardized reusable generic concepts Separated Development of Mechanics and EE/SW Isolated internal Development process at OEM Cooperation with Design Offices in Europe Engineering Books of Knowledge, Data Bases, Documents, Lessons Learnt Focus on EE-Systems Generic Standards for BiW, Modules, Requirements, Test cases, Production On the Way to Future Concurrent Development of complex mechatronic Systems Web community based cooperation and open innovation Worldwide Designand Simulation- Cooperations with Partners and Suppliers Context based provision of Knowledge. On line Intranet search based on Company structures For Entire Product Function Structure Mapping Components Function Simulation Generic best Practice Standards for entire Product and Production Definition GR / PPP / Status 08. Mai

7 GR / PPP / Status 08. Mai Overview Motivation and Trends Vision and Paradigm Shifts Implementation within a Demonstrator System Template Collaboration System Simulation Community-Driven Innovation Conclusion

8 GR / PPP / Status 08. Mai Vision Using the world of knowledge to converge to mechatronic system engineering by Definition of a generic, collaborative, holistic system development method in the product creation Daimler

9 GR / PPP / Status Mai Partnership between DAIMLER Research/ MBtech / DS / IBM Executive Sponsorship DS Vision DAIMLER Vision Create next generation PLM for Daimler Product Creation Product Creation Synchronized Vision Greenfield Work Packages Validate V6 concept against Product Creation Vision Development of Vision Demonstrator

10 GR / PPP / Status 08. Mai Paradigm Shift 1 From Mechanical Part Design to Mechatronic System Development Liftgate Body Interior Exterior Trim E/E SW Today: Digital Product definition is separated for Requirements, Functions, Logic, Mechanics, EE, SW. Projects for definition of standardized generic product information are running isolated. The paradigm of Template technology is applied to geometrical part design and validation only. Requirements Function Validation

11 GR / PPP / Status 08. Mai Paradigm Shift 1 From Mechanical Part Design to Mechatronic System Development What if you could start development of a car program with a predefined, complete generic product template, containing best practice concepts and interdisciplinary dependencies?

12 Paradigm Shift 2 From sequential Product Development to collaborative Solution Finding Today: Each domain develops independently from the others in a sequential process providing a domain specific optimum for each task. Requirement Functional Process Validation Logical Product Validation Physical Mechanical E/E SW GR / PPP / Status 08. Mai

13 GR / PPP / Status 08. Mai Paradigm Shift 2 From sequential Product Development to collaborative Solution Finding What if you could collaborate with all development partners sitting around a virtual round table to find globally optimal solutions for your task?

14 GR / PPP / Status 08. Mai Paradigm Shift 3 From isolated Function Simulation to Co-Simulation of System Behaviour Today: Each function is simulated, validated and tested individually. There is no interdependence between simulations in the digital world.

15 GR / PPP / Status 08. Mai Paradigm Shift 3 From isolated Function Simulation to Co-Simulation of System Behaviour Controller logic E Motor Drive Voltage Torque Rotation Angle Current Kinematic Force What if you could simulate the complete complex system behaviour with all subfunctions in parallel and with respect of all interdependencies between the subsystems? Gas spring model Speed Force Counterforce Counterforce

16 GR / PPP / Status 08. Mai Paradigm Shift 4 From bulkheaded in-house Development to Community driven Creativity People Today: Product development and innovation is performed exclusively inhouse in the OEM s R&D with some selected suppliers.

17 GR / PPP / Status 08. Mai Paradigm Shift 4 From bulkheaded in-house Development to Community driven Creativity What if you could motivate your customers to cooperate with you in product innovation and so using the huge creative potential of the worldwide internet community to innovate your brand?

18 GR / PPP / Status 08. Mai Overview Motivation and Trends Vision and Paradigm Shifts Implementation within a Demonstrator System Template Collaboration System Simulation Community-Driven Innovation Conclusion

19 GR / PPP / Status Mail Introduction to the automatic lift gate Why to choose a Power Lift Gate mechatronic System Template? Mechanical and non-mechanical aspects must be considered o Mechanical o E/E and Software System elements are interdependent (i.e. E-motor Drive - Liftgate Kinematics) Validation must be performed as complete system Liftgate Body Interior Exterior Trim E/E SW

20 GR / PPP / Status 08. Mai Storybook Demonstrator Product rating Virtual experience User Driven Innovation 3D draft design Status report in dashboard Simulate system behaviour Use of System Template Configure for specific car concept Adapt to specific car specifications Detailing of digital product model People Implement solution Collaborative solution finding Change request for modif requirement

21 System Template Requirements Production Validation Functions Integration Validation Specification Logic Detailing phase Mechanical E/E Software System Template: A system template is the reunification of standard requirements, -functions, -product and validation models related to a given system The behaviors between Requirements, Functions, Product models and Validation models are already realized in the system template The system template is configurable and adaptable GR / PPP / Status 08. Mai

22 GR / PPP / Status 08. Mai Collaborative Finding of a Globally Optimal Solution Requirement Change Max. Standing Height > 1900 mm Ad hoc online conferences for a collaborative solution finding Easy impact analysis and solution comparison from different perspectives Parallel work and investigation with domain specific applications on same product model Increase Opening Angle 1 Hinge Gas Spring? Assembly Benefit Fast solution finding of a globally optimal and combined solutions Ad hoc modifications on the product model are published to all participants Reduction of iteration loops Move Lock 3 Reduce Gate Thickness 2 Lock Loading Gate Trim.??? Power Dr. Opening H. Lock Trim.? Realization?? Find ad hoc a global optimal solution by combining contributions from all sides

23 GR / PPP / Status 08. Mai Motivation for System Simulation Initial Situation: Car consists of subsystems e.g. SW, electrics, mechanics, System functionalities to be verified on system level. Aspired functionality defined by requirements. System validation should be done both in the digital and real world Aspired Work Methods Entire system simulation All the system functions are simulated in parallel Integration of encapsulated external models Simulation results are always coupled with corresponding requirements Mechanical System Controller logic E-Motor Drive Voltage Torque Rotation Angle Current Gas spring model Position Force Position Counterforce Seal Force Force Counterforce

24 1 Community-driven Innovation Storybook - Outline Mercedes-Benz uploaded design study to online-community and -experience! Use this link for a new experience! Customers are informed via newsletter or RSS feed reader. 8 A user discussion on the taillights starts. 3 4 Other users rate and discuss the design. 5 2 Customer experiences vehicle and registers with the community. Customer leaves a comment: How do you like the backlights? Experience our new taillight design! Please use this link. 7 New taillights are integrated into design experience and users are informed. A customer designs LED backlights of his own and publishes them on the platform. 6 Marketing analyzes user feedback and selects one proposal. Design is provided to engineering environment. Engineering creates a new system based on proposed design. Vision: The customer-community uses its creative potential to actively contribute to product innovation. GR / PPP / Status 08. Mai

25 GR / PPP / Status 08. Mai This Vision is more than just a Day Dream it is work in progress The Tech Groundwork is being laid Data and Information backbone Crosslinked Product Data Worldwide Collaboration Plattform for Co-Simulation Web based Design Tools It s up to us to Provide a culture of innovation Be ready to respond to challenges Adapt the development processes Be open for organizational changes Go for the next generation processes