Integrating MBSE and PLM to enhance System Engineering Processes

Transcription

1 Integrating MBSE and PLM to enhance System Engineering Processes Stephane GUIGNAR

2 Agenda 1 Aras at a glance 2 Introduction & Context 3 Integrating MBSE and PLM - Benefits 4 emo 5 Conclusion 2

3 Aras at a Glance 3

4 Aras overview THE PROUCT INNOVATION PLATFORM TO POWER THE BUSINESS OF ENGINEERING Global Operations Veteran PLM Team North America, Europe and Asia Focus on markets with complex products and processes Automotive & Industrial Aerospace & efense High Tech Electronics Consumer Goods Life Sciences Energy Business Results Ranked PLM Leader by Forrester Over 300 subscribers worldwide More than 100 partners Most growing PLM solution in the Market 65% growth average/year for past 3 years 96%+ renewal rate on Subscriptions Best customer experience Over 1,000 open users Innovating in our Technology, eployment and Business Model 4

5 Introduction & context 5

6 Product/System esign Challenges Product/System complexity isconnected processes & tools Legacy PM fail Excel hell. hello MBSE, SysML, RFLP and PLM 6

7 Systems Engineering Process Major Improvements Verification and Validation Improved traceability Reuse supported Fewer late-stage integration issues System models integrated with physical structures Source: VPE TU Kaiserslautern (modified) Services Mechanical Electronic Software isciplines synchronized 7

8 Systems Engineering Evolution Test Science Systems Test Science Assemblies Sub- Systems Systems Operations Assemblies Others Sub- Systems Operations Others Today: Standalone models related through documents. Source: INCOSE MBSE Workshop, Jan 2014 Future: Shared system model with multiple views, and connected to discipline models. Reusable, model-based engineering with virtual product development and simulation capability. 8

9 MBSE and PLM «Model-Based Engineering (MBE) an approach to engineering that uses models as an integral part of the technical baseline that includes the requirements, analysis, design, implementation, and verification of a capability, system, and/or product throughout the acquisition life cycle» Final Report, Model-Based Engineering Subcommittee NIA (February 2011) «Model-based engineering (MBE) the combination of PLM and MBSE is the enabler for the Internet of Things and Industrie 4.0» GfSE PLM4MBSE Working Group 9

10 Relationship / Linking Barrier Need to break the Traceability wall in PLM A A A A SN #6 A SN #6 A SN #6 B B P1 C C C C C C G H J Q E K L O R S I F M G H J Q F K L O R S I P2 J H Q F G T K L O R I F SN #89 G T J K L O SN #44 I Q SN #53 R S F G T J H Q SN #89 K L O SN #44 R S I G I T A L T WIN F G T J H SN #97 SN #71 Q SN #71 K L O SN #44 R S 10 SYSTEM MOEL AS ESIGNE AS ORERE S AS PLANNE AS BUILT I G I T A L T H R E A Logical Physical AS ELIVERE AS SERVICE

11 Integrating MBSE and PLM 11

12 Integrating MBSE and PLM Systems Engineering needs PLM System Architecture is at the core of product development PLM brings engineering domains together RFLP as an abstraction of SysML RFLP is bigger than SysML Allows to map between product domains Neutralizes local SysML tool database architectures Open to all via API RFLP PLM already has the data & processes Reusable domain parts and assemblies ( carry over ) Model Lifecycle Management igital Thread that connects igital Twins 12

13 RFLP and esign omains Logical block a hierarchical structure L1 Critical to reuse of PLM content ( carry over ) L2 L3 PLM: Mechanical logical Part (with options and variants) PLM: Electronic hierarchical schematic block L6 L4 L5 L9 PLM: Software functional block PLM: Parameters allow to negotiate L7 L8 Port a semantic network Critical to negotiate contracts PLM: Ports define connections (vs structures) PLM: Port Functions define what and how 13

14 Aras Approach Extending the Core Model of PLM Platform Concept evelopment Manufacturing Service «realize» «verify» Function «satisfy» «realize» Test Logical Port Flow Ф Parameter Unit Constraint Signal Х [..] {..} 14

15 MBSE - PLM Use cases 1 Top/own System model first, then detailed Product design 1 2 esign everywhere at once System model is collaborated with on-the-fly as needed 2 3 Redesign Field driven change 3 15

16 MBSE PLM Benefits for Trade-off Study F1 Revision B Existing Function Reuse Compare variants L1 L2 L6 L7 L8 L11 L3 L4 L5 L9 L10 F2 F3 F7 F10 F4 F5 F6 F8 F9 F11 Revision B B G C E H E Variant 1 Variant 2 B C E Alternative 1 Existing Assembly Reuse F12 G Alternative 2 F13 H Architectural esign LOGICAL F14 F15 F16 FUNCTIONAL Revision A New Function E Proposed New Assembly 16

17 MBSE PLM Benefits for Trade-off Study Automated P Allocation along changes L1 B MCA omain Modeling L2 L3 BOM C Alternative 1 L4 E L6 L7 L8 L11 L5 L9 L10 G H E Alternative 2 LIBRARY Parameter Х Size Weight Align with other libraries: e.g. Cameo QUV (ISO-80000) Library Architectural esign LOGICAL AS ESIGNE Unit [..] Constraint {..} 17

18 MBSE PLM Benefits for Trade-off Study Trade-off Study as part of the digital thread available for all B Brake WS0158 L1 L2 L3 C E Rotor Rotus 25 Caliper Alphine K3 Pad MK 25 L6 L7 L8 L4 L5 G H E Brake WS0210 Rotor Rotus 25 Caliper Alphine K3 Pad MK 30 L9 L10 L11 Architectural esign LOGICAL Brake WX0300 Rotor Caliper Pad AS ESIGNE Modeling tool executes a series of simulations that identify all combinations of the parts that meet the brake model behavioral targets and returns results to PLM 18

19 emo 19

20 Aras No Magic Integration emo Business Goals Use a previous car platform in PLM to create the next car platform brake for an electric car Maximize carry over through reuse of existing designs, parts, and assemblies Process Goals Improve productivity of Systems Engineers that use SysML tools Leverage PLM processes of change management, configuration control and life cycle management 20

21 Aras No Magic Integration emo 21 Aras PLM Platform Individual R, F, L, and P items as libraries of reusable IP accumulated 1 over time System Platforms as specific RFLP structures including related SysMLlike diagram view 2 A new Product Platform specification by copying and editing existing RFLP 3 structures Aras updates RFLP structure of the Product Platform including Parts, and 8 trade study results No Magic SysML Tools A new SysML model automatically created from the RFLP structures in Aras 4 Systems Engineer (SE) evolves the model and focusses on the brake system 5 Aras dynamically returns the list of existing brake parts that match SysML parameters 6 Magicraw runs study to identify sets of parts that meet targets and returns results to Aras 7

22 Aras No Magic Integration emo Aras PLM Platform No Magic SysML Tools Engineers collaborate on the results, select the best option, and finalize the 9 RFLP model Final RFLP is committed to a Report - a complete specification of the new 10 Product Platform 22

23 Conclusion 23

24 Conclusion MBSE PLM Integration benefits Flexible Use Cases Synchronization of SysML and PLM product platforms Engineering development process vs formal configuration, revision and release control Simplifies Reuse (SySML Library, Platform,.) Structures esign Collaboration for all omain isciplines Bridges Architectural and omain Specific ecisions esign Justification as part of the igital Thread and Available for All Supports IoT feedbacks and continuous engineering 24

25 Aras is collaborating with users, tool vendors, academia, standards organizations 25

26 Aras White Paper: integrating MBSE and PLM English Version: French Version: 26