The Convergence of PLM and MBSE Will This Decrease or Increase the Risk with PLM Projects

Transcription

1 The Convergence of PLM and MBSE Will This Decrease or Increase the Risk with PLM Projects Perspectives on PLM and Model Based System Engineering University of Kaiserslautern Institute for Virtual Product Engineering EIGNER Engineering CONSULT Prof. Dr.-Ing. Martin Eigner VPE Folie: 1

2 Prof. Dr.-Ing. Martin Eigner Institut for Virtual Product Engineering (VPE) + EIGNER Engineering Consult CV Martin Eigner: Tool Maker University of Karlsruhe Mechanical Engineering, Economy 1980 PhD in Applied Informatics Robert Bosch GmbH Technical Organization and IT / EE Development 1985 Founding EIGNER+PARTNER PDM/PLM Solution Provider 1999 Founding EIGNER Inc. Burlington (Headquarter) 2001/2003 Company sold to Agile (now ORACLE) President since 2003 since 2004 since 1980 since 1985 since 1987 since 2005 Founding EIGNER Engineering Consult University of Kaiserslautern Institute for Virtual Product Engineering 13 books related to CAD, PLM and IT Honored Member of German Engineering Association Founding and Board Member of ProSTEP Association Member of the WiGeP (Berliner Kreis), acatech TN Product Creation. ENGINEERING CONSULT VPE Folie: 2

3 Agenda 1 Interdisciplinary and Integrated Products and Processes 2 Modell Based Systems Engineering / Frontloading 3 I The Role of PLM in an MBSE Environment 4 I Summary VPE Folie: 3

4 Disciplines ENGINEERING CONSULT PLM Vision Integrated and federated product and process model along - Product lifecycle, - Disciplines and - Supply Chain Services Software Electronics Mechanics OEM Requirements Definition Product Planning Product Design Process Planning Production Operation Recycling 1 st Tier Product Lifecycle 2 nd Tier VPE Folie: 4

5 Software Becomes a Dominant Factor of the Product Mechatronic Mechanic Mechatronic IT Mechatronic Mechanic IT Mechanik Source: vgl. [me] Electronic Electronic yesterday (1968) tomorrow When Software becomes dominant, why should we use methods from Mechanic & Hierarchical Requirements and Function Structure? VPE Folie: 6

6 Managing Interdiciplinary Complexity Managing complexity of technical systems Now.. - Increase of Software and personal interactions - Different engineering disciplines required - More fragmented and specialized systems - Organizations involved Interconnectivity among Subsystems - No longer treated as stand alone - Part of a larger Whole behavior [Source: Systems Engineering Handbook (INCOSE)] Services Software Mechanics Electronics [Based on: execpastor.com] VPE Folie: 7

7 New Products: Beyond Mechatronic: Cybertronic Autonomeous Parking and Driving User Interaction (UML) act [Activity] ParkhausApp [ ParkhausApp ] Gebäudeausrüstung Allocation of Parkingslot Dauerparker KundenID übertragen KundenID übermitteln Standort ermitteln Kundenkonto? Standardparkplatz Anmeldung am Parkhaus KundenID Eigner BMW Z4 übermitteln Academic Version for Teaching Only Commercial Development is strictly Prohibited KundenID übermitteln Parkhaus Check-in-App bdd [Model] Data [ autonomes Parksystem ] «Log ical System Element» autonomes Parksystem parts Datenbank : Benutzerverwaltung Parkhaus Kaiserslautern IPhoneApp «Log ical System Element» cybertroninisches Parkhaus ParkhausApp Benutzerdaten parts values Benutzerdaten : Einfahrtkontrolle KundenID : String : ParkplatzZuweisung Position : String : Einfahrtkontrolle : Fahrzeug leitsystem Wegpunkte Wegpunkte BMW «Log ical System Element» Fahrzeugsteuerung parts : Antrieb : Lenkung : Bremssystem Academic Version for Teaching Only Commercial Development is strictly Prohibited Waypoints {(12.4,12.5), } Autonomeous Parking Ihr Fahrzeugdaten Automatisches Guten zugewiesener Tag, ubermitteln? Herr Einparken Parkplatz: Eigner starten? 1453 akzeptieren Logical Building Blocks (SysML) Parkingslot #: SW Entwicklung Length < 5 m Automobilbau VPE Folie: 8

8 Beyond Mechatronic: CYBERTRONIC Many mechatronical products, system and subsystems, communicating each other. Example: Airplane: status landing behavior reverse engine / Flaps (10%) VPE Folie: 9

9 Challenges for the Manufacturing Industry Software Intensive Products Connectivity Regulation Servitization Digitization Globalization Personalization Source: PTC MBSE: Model Based Systems Engineering VPE Folie: 10

10 Agenda 1 Introduction Interdisciplinary and Integrated Products and Processes 2 Modell Based Systems Engineering 3 I The Role of PLM in an MBSE Environment 4 I Summary VPE Folie: 11

11 Model Based Systems Engineering + PLM Requirements Definition Product Planning Design Process Planning Production System Model System Model Simulation Model CASE M-CAD E-CAD PLM Backbone Targets Validation R F Requirements Engineering and Specification (Requirements, Functions and Behavior) Virtuelle Tests Physical Tests Simulation Model L Logical System Design and multiphysical Simulation Simuation Testing CASE Model E-CAD Model M-CAD Model P Dicipline Specific Design Dienstleistung Hybride Tests (z.b. HIL) Mechanik Disciplin Specific E/E Detailling Software Modellbildung und -analyse Source: VPE Research Project mecpro² (T. Gilz) VPE Folie: 12

12 The old Product Development Process (PDP) Document centric PDP Concept Specification System Specification Subsystem Specification Function Specification Design Specification Implementation Many non integrated SW Tools Word, Excel, Visio, Powerpoint, etc. No consistency and traceability of documents Gaps between different development phases and stakeholder No guaranteed Quality No traceability regarding international standards (ISO 26262, EN50128, DO178B) Quelle: nach VIF Graz VPE Folie: 13

13 Model Based Product Development Process Concept Specification System Specification Requirements model Technical System Model IT based Models are the basic of all development phases and they are transferable to the next phase The integration is based on formal models and not on documents Traceability is guaranteed (ISO 26262, EN50128, DO178B) Subsystem Specification Behavioral Model The documentation is derivated from the model Function Specification Design Specification Behavioral Model Implementation The models must be administrated (versioning, revisioning, configuration) Quelle: nach VIF Graz VPE Folie: 14

14 Specification (e.g. in SysML) req Beispielanforderungsdiagramm «DeveloperRequirement» Winkel Id= EF_06 Text= Der Endwinkel soll 90 Grad betragen. Text= Id= «DeveloperRequirement»... «DeveloperRequirement» Masse Schlitten Id= EF_07 Text= Der Schlitten soll maximal 1kg wiegen. Anforderungen bdd Beispiel Blockdefinition Struktur «trace» Controller SollWinkel = 90 SollGeschwindigkeit = 0 MotorStellen() ibd Inverses Pendel «trace» Multi-Physical Description and Simulation Models «UserRequirement» vertikale Position Id= BF_04 Der Pendelstab soll in vertikaler Position Motor gehalten werden. Pendelstab Rotationssensor Drehgelenk Induktivität = Länge = 1 Trägheitsmoment = Verhalten... Masse = 0.9 w phi Schwerpunkt =... «trace» Controller v s Schlitten steuert «UserRequirement» Masse Länge = 0.1 Translationssensor Id= BF_05 Höhe = 0.05 Das System soll Schwerpunkt eine Gesamtmasse =... von 4 kg nicht überschreiten. liefert Information stm Zustände Inverses Pendel Schlitten in Mittelposition Pendelstab Pendel aufschwingen Schlitten nach links Position < max. links /Motor(rechts) Schlitten Position > max. rechts /Motor(links) Pendel senkrecht stellen Pendel halten Motor «Block» Rotationssensor Winkel <> 90 Winkel Winkelgeschwindigkeit WinkelMessen() Geschwindigkeit WinkelgeschwindigkeitMessen()... Rotationsgelenk Translationsgelenk Startwinkel = Schlitten nach rechts Winkel > 70 Schlitten regeln Winkel <70 or Winkel > 110 Pendel nicht mehr haltbar First simulations (e.g. Matlab/Simscape/Modelica) Simulation models CASE models System model E-CAD models M-CAD models Library Mapping of requirements, functions und logical solution elements link analysis models, ports and parameters VPE Folie: 15

15 System Model CASE Model Specification (e.g. in SysML/ModelicaML) req Beispielanforderungsdiagramm «DeveloperRequirement» Winkel Id= EF_06 Text= Der Endwinkel soll 90 Grad betragen. Text= Id= «DeveloperRequirement»... «DeveloperRequirement» Masse Schlitten Id= EF_07 Text= Der Schlitten soll maximal 1kg wiegen. Anforderungen bdd Beispiel Blockdefinition Struktur «trace» Controller SollWinkel = 90 SollGeschwindigkeit = 0 MotorStellen() «trace» «trace» «UserRequirement» vertikale Position Id= BF_04 Der Pendelstab soll in vertikaler Position Motor gehalten werden. Induktivität = Trägheitsmoment =... Schlitten steuert «UserRequirement» Länge Masse = 0.1 Id= BF_05 Höhe = 0.05 Das System soll Schwerpunkt eine Gesamtmasse =... von 4 kg nicht überschreiten. liefert Information Inverses Pendel Pendelstab Länge = 1 Masse = 0.9 Schwerpunkt =... «Block» Rotationssensor Winkel Winkelgeschwindigkeit WinkelMessen() WinkelgeschwindigkeitMessen()... Rotationsgelenk Startwinkel = Discipline specific Development (e.g. CASE) Simulations models CASE models System model E-CAD models M-CAD Models VPE Folie: 16

16 M-CAD Multi-Physical Simulation Models Bridging of M-CAD with multi-physical simulation models - Takeover of information of Assemblies Kinematic relations 3D geometry Kinematic relations 3D geometry Simulation models CASE models System model E-CAD models M-CAD models F1_300_InvPendel.ASM F3_300_Pendelstab.PRT F3_300_Schlitten.PRT F3_300_RotGelenk.PRT F3_300_Motor.PRT F3_300_Schlitten.PRT Baugruppenstruktur M-CAD Multiphysikalische Simulationen mit Detailgeometrie VPE Folie: 17

17 System Model Must be Administrated by PLM Source: Discussions with Chris Paredis, Georgia Tech System Models + PLM = SysLM VPE Folie: 18

18 Agenda 1 Introduction Interdisciplinary PDP 2 Modell Based Systems Engineering / Frontloading 3 I The Role of PLM in an MBSE Environment 4 I Summary VPE Folie: 19

19 Product and Process Centric Backbone for SysML Plan Concept Design Validate Production Support Requirements BOM System /Functional BOM Engineering BOM Simulation/Testing BOM Manufacturing BOM Service BOM Focus Systems Lifecycle Management (SysLM) Production Systems (ERP/MES) VPE Folie: 20

20 MBSE as an integrated part of a SysLM concept Plan Concept Design Engineering (authoring systems in concept design, M-CAD, E-CAD, CASE) Requirements structure System /Functional BOM (e.g. SysML) Engineering BOM Requirements management tools System requirements System structure CAD/CASE authoring systems 4XX_200.ASM System behavior L224_300_200_HS.ASM F1_300_200_G.ASM F3_300_211_B.PRT F3_300_238_F.PRT Requirements structure Deriving Product hierarchical Lifecycle Management structure information (PLM) (e.g. via XML) System /Functional BOM System requirements System structure Engineering BOM All data in one PDM system System requirements model System structure model System behavior model VPE Folie: 21

21 MBSE as an integrated part of a SysLM concept Plan Concept Design Engineering (authoring systems in concept design, M-CAD, E-CAD, CASE) Requirements structure System /Functional BOM (e.g. SysML) Engineering BOM Requirements management tools System requirements System structure CAD/CASE authoring systems 4XX_200.ASM System behavior L224_300_200_HS.ASM F1_300_200_G.ASM F3_300_211_B.PRT F3_300_238_F.PRT Product Lifecycle Management (PLM) Requirements structure System /Functional BOM System requirements System structure A change in system requirements Engineering BOM All data in one PDM system System requirements model System structure model System behavior model VPE Folie: 22

22 MBSE as an integrated part of a SysLM concept Plan Concept Design Engineering (authoring systems in concept design, M-CAD, E-CAD, CASE) Requirements structure System /Functional BOM (e.g. SysML) Engineering BOM Requirements management tools System requirements System structure CAD/CASE authoring systems 4XX_200.ASM System behavior L224_300_200_HS.ASM F1_300_200_G.ASM F3_300_211_B.PRT F3_300_238_F.PRT Product Lifecycle Management (PLM) Requirements structure System /Functional BOM System requirements System structure A change in E-BOM structure Engineering BOM All data in one PDM system System requirements model System structure model System behavior model VPE Folie: 23

23 Core concept of SE VPE data model Reduced data schema (co VPE Folie: 24

24 Agenda 1 Introduction Interdisciplinary PDP 2 Modell Based Systems Engineering / Frontloading 3 I The Role of PLM in an MBSE Environment 4 I Summary VPE Folie: 25

25 ECM related Items (Configured Items) (orange new MBSE itrems) Supply Chain Simulations Documents/ Documentation Software Function/ Behavior Manufacturing/ Assembly Resources/ Process Planning 4711 Requirements Simulation/DMU Test/PMU Maintenance Customer Feedback Classification/ Commonality/ reuse Where Used? Items (M,E,SW) E-BOM M-BOM VPE Folie: 26

26 Summary There are existing IT-Tools for all phases of an integrated interdisciplinary Product Development Process (SysML, Simulink/Simscape/Matlab, Modelica, MKS, CAD-M/E, Case) There is no accepted, integrated and interdisciplinary design theory and customers have no experiences with this new approach The integration of the System Model and their artifacts Requirements, Functions, Behavior and Logical Building Blocks with PLM/SysLM is absolutely necessary because of traceability regarding international standards (ISO 26262, EN50128, DO178B) The completeness, usability and acceptance of these new tools and processes is not existing but f.e.sysml is a worldwide Standard (OMG) and we should focus on further development The Integration of Mechanic, Electronic and Software along the Product Lifecycle even without the early phases is real challenging..and very seldom realized in industry The risk with the PLM/SysLM project becomes higher with more objects to administrate. But the real problems of unsuccessful PLM implementation is not the quantity of objects, but. VPE Folie: 27

27 Typical PDM/PLM scenarios - Jump as a tiger land as a carpet runner - No vision no budget, vision but no budget, no vision but budget - No Champion, no leadership - MyPLM = I need my own PDM/PLM Solution - To many own developed or over customized PDP/PLM solutions - Missing milestone plan, missing long term perspective - Redundancy and overlapping with legacy systems (ERP), who is master? - No PDM/PLM awareness on management level ( no father, no mother ) - Wrong people to execute the PDM/PLM project - No balance between central defined and executed functions (f.e. engineering item master, ECM process, multi-disciplinary E-BOM) and flexible regional, product or discipline dependent solutions (f.e. TDM,...) - Customers want 150%, suppliers promise 120% and deliver 68% - No guidance from the Solutions Provider and from Management - IT drives processes and not vice versa... - Detailed analysis of technique (System A 3,34 points, System B 3,29 points,...) - Missing user acceptance VPE Folie: 28

28 Further questions VPE Folie: 29