On graph-based design languages for consistent multi-disciplinary models

Transcription

1 Presented at: Rudolph, S.: On graph-based design languages for consistent multi-disciplinary models. 9th MODPROD May 11, Workshop 2011 on Model-Based Product Development, Linköping University, Sweden, February 3-4, On graph-based design languages for consistent multi-disciplinary models Similarity Mechanics Group Head (ISD) Germany

2 problem statement (part I) systems engineering perspective system = system of systems (system as free combination of (sub-)systems) system of systems systems (currently) very difficult in CAD system manipulations system topology (creation and modification) system parameters (creation and modification) systems modeling framework is needed to freely combine (sub-)systems (design, simulate, analyse and evaluate) available in (parametric) CAD slide 2 / 26

3 problem statement (part II) information technology perspective data consistency (origin and formats) environment representations operational needs top-level requirements budget, schedule, risk concept exploration demonstration validation future: dream of a unified digital master model engineering development operations, support functional design Source: US Air Force logistics, support HW/SW development HW/SW design status quo: fragmentation and inconsistency of data modeling framework is needed to seemlessly integrate major standard engineering tools (CAD (Catia V5, ), MBS (Adams, ), FEM (Ansys, ), controls (Matlab, ), CFD (Fluent, ), CAS (Mathematica, ), thermal (ESARAD-TMS,)), slide 3 / 26

4 problem statement (part III) information flow data consistency (origin and formats) CAD n(n-1)/2 interfaces central model only n interfaces CAD MBS FEM CFD model MBS FEM CFD CAS CAS model interfaces to propagate design changes from engineering domains: tool to tool (CAD (Catia V5, ), MBS (Adams, ), FEM (Nastran, ), controls (Matlab, ), CFD (Fluent, ), CAS (Mathematica, ), thermal (Esatan-TMS,)) slide 4 / 26

5 problem statement (part IV) an act of designing means making decisions = result of a scientific study of the system (under a set of boundary conditions) study of sytem = creation of a model of the system (under a set of idealizations) question system boundary conditions idealizations model answer The design process means answering a sequence of related questions needs a sequence of related models (under a set of boundary conditions requirements) requirements model model model product slide 5 / 26

6 problem solution (part I) the design process in an engineering view means answering a sequence of related questions needs a sequence of related models (under a set of boundary conditions requirements which define the product) requirements model model.. model product this design process in a model-driven architecture (MDA) view can be encoded in graph-based design language which execute - model-to-model (M2M) transformations model model - model-to-text (M2T) transformations model text for design analysis needs: analysis and simulation for design process needs: synthesis, decision making model CAD MBS FEM CFD CFD slide 6 / 26

7 problem solution (part II) design language (human definition and programming) design language (human compilation and execution) CAD CATIA V5 SOLID WORKS VRML MBS ADAMS vocabulary rules production system design compiler 43 design graph FEM CFD ANSYS NASTRAN MSC Laminate Modeler, FLUENT STAR-CD STAR-CCM+ typically model-to-model transformations typically model-to-text transformations CAS MATLAB/ SIMULINK ESATAN-TMS MAPLE MATEMATICA slide 7 / 26

8 problem solution (part III) design language (human definition and programming) design language (machine compilation and execution) CAD-paradigm no longer predominant CAD MBS CATIA V5 SOLID WORKS VRML ADAMS vocabulary rules production system design compiler 43 design graph FEM CFD ANSYS NASTRAN MSC Laminate Modeler, FLUENT STAR-CD STAR-CCM+ language spoken by humans and compiled by a machine CAS MATLAB/ SIMULINK ESATAN-TMS MAPLE MATEMATICA slide 8 / 26

9 problem solution (part IV) design language (human definition and programming) manual or computerassisted design language (machine compilation and execution) closing the design loop (feed-back) CAD MBS CATIA V5 SOLID WORKS VRML ADAMS vocabulary rules production system design compiler 43 design graph FEM CFD ANSYS NASTRAN MSC Laminate Modeler, FLUENT STAR-CD STAR-CCM+ MATLAB/ SIMULINK ESATAN-TMS CAS MAPLE MATEMATICA slide 9 / 26

10 (iterative design loop) necessary initial effort graph-based design language (in UML) design process (generic) vocabulary (as UML classes) vocabulary rules program rules (as UML model-transformations) model simulation program (as UML activity diagram) consists of a sequence of design rules evaluation slide 10 / 26

11 evolution of design languages international, vendor-independent format and development tools productivity, quality und security by - code expansion - code re-use - code generation abstraction high + rule exec + constraints + plugins design languages modeling languages object-oriented languages public class Plane{ private String name; } with capability of - abstraction - hierarchization - modularization - visualization of information assembler languages MOVF id1, R1 ADDF R2, R1 machine code procedurale languages int main(int argc, char **argv) { fprintf(stdout, Hello ); } adapted from Gruhn et al. (2006) design of complex SW/HW-systems low time slide 11 / 26

12 class decomposition courtesy Peter Arnold Similarity Mechanics Group 2010 slide 12 / 26 13th NASA-ESA Workshop on PDE, May 11-13, 2011

13 class decomposition courtesy Peter Arnold Similarity Mechanics Group 2010 Vertical tail Horizontal tail Fuselage Wing Engine slide 13 / 26 13th NASA-ESA Workshop on PDE, May 11-13, 2011

14 class decomposition courtesy Peter Arnold Similarity Mechanics Group 2010 slide 14 / 26 13th NASA-ESA Workshop on PDE, May 11-13, 2011

15 class diagram courtesy Peter Arnold Similarity Mechanics Group 2010 holistic aircraft description - topology - parametrics - geometry - physics (constraints) slide 15 / 26

16 aircraft design language detail view wing (topology, parameters) product line aircraft family (external) (internal) detail view aircraft panel slide 16 / 26

17 aircraft design language conventional and unconventional aircraft generated from the same design language Böhnke, D., Reichwein, A. and Rudolph, S.: Design Language for Airplane Geometries using the Unified Modeling Language Proceedings of the ASME 2009 International Design Engineering Technical Conferences slide 17 / 26

18 design rule definition rule: add left and right engines to plane rule: specialization of a generic cable to a specific type (cast, slots added) slide 18 / 26

19 system design and integration video 1 slide 19 / 26

20 aircraft panel courtesy Jan-Philipp Fuhr Similarity Mechanics Group MSc Thesis 2010 slide 20 / 26

21 aircraft panel (mapped to CATIA V5) generation time approx. 15 mins (about 2/3 spent for CATIA V5 model) fuselage section - 4 panels - lateral and longitudinal structural connections - riveting - parameters: nframe=5 nstringer=6 Fuhr, J.-P., Beilstein, L. and Rudolph, S.: A validation method using design languages for weight approximation formulae in the early aircraft design phase. Proceedings EUCOMAS 2010 Conference, Berlin, June 7-8, slide 21 / 26

22 digital factory integration integrated design and generation of the digital factory along the digital design phase using graph-based design languages simulation and analysis - choice of tools - choice of layout - path generation - and much more slide 22 / 26

23 digital factory simulation video 2 slide 23 / 26

24 birth market study design language scope feasibility / requirements list study conceptualdesign detailed design true problem scope of design software tools: CAD, MBS, FEM, CFD,, PDM, ERP, fuctional verification recycling maintenance repair production production prototypes planning assembly digital factory verification death go/no-go go/no-go product-life-cycle design freeze product freeze go/no-go problem A: downstream you find out, whether you made profits, but the decision making occurs upstream. (The) solution for necessary feedback is front-loading design languages problem B: product design and production definitions need full interoperability of CAD, MBS, FEM, CFD, in consistent model representations. (The) solution: design languages problem C: product design and production aren t isolated, but embedded in the context of a product family. (The) solution for know-how re-use design languages slide 24 / 26

25 design paradigm change past: sequential engineering P1 P2 P3 P4 P5 Pn present: concurrent/simultaneous engineering P2 P4 P1 Pn P5 P3 organization problems model consistency effort increases with size and complexity interfaces defined by organization future: digital engineering automation P1 P2 P3 P4 P5 Pn advantages consistent models automated simulations automated knowledge processing in engineering design more design variants in less time with higher level of confidence speed-up of 8 weeks to 8 mins is possible in product design slide 25 / 26