© 2013 © 2016 Aras aras.com.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

FPGA (Field Programmable Gate Array)
Visual Scripting of XML
Professor John Hosking, Dean of Engineering and Computer Science Models, Modelling, MBSE.
1 Autodesk’s Manufacturing Solutions Kvalitetssikring i engineering processen Mads Storgaard.
Product Lifecycle Management (PLM) Organisational Strategy –Need for structural change –IT tools –Increased integration (rather than “point solutions”)
Page 1 © 2007, UGS Corp. All rights reserved UGS PLM Software Integrating MBSE and PLM Wayne Collier Senior Functional Architect
Version Enterprise Architect Redefines Modeling in 2006 An Agile and Scalable modeling solution Provides Full Lifecycle.
Annual SERC Research Review - Student Presentation, October 5-6, Extending Model Based System Engineering to Utilize 3D Virtual Environments Peter.
Free Mini Course: Applying SysML with MagicDraw
Product Lifecycle Management Solutions of Enterprise Group 8 楊士霆 (d927821) 吳友仁 (g923836) 白珊慈 (g923840)
CAM-I Scalable Flexible Manufacturing Initiative NGMS Task 6.1.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
1 Introduction to Software Engineering Lecture 1.
OSLC PLM Workgroup visit URL for terms of usage1 OSLC PLM Workgroup PLM Scenarios Systems Engineering scenario “Systems Engineer Reacts to Changed Requirements”
OSLC PLM Reference model April Summary of the OSLC PLM Reference Model V0.4 April 4th 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
International Workshop Jan 21– 24, 2012 Jacksonville, Fl USA Model-based Systems Engineering (MBSE) Initiative Slides by Henson Graves Presented by Matthew.
STEP for Multi-Disciplinary Model Management: “Intelligent PDM”
XASTRO-2 Presentation CCSDS SAWG th November 2004.
OSLC PLM Workgroup 7/12/20101 The PLM Reference model in the context of SE Scenario #1 V0.6 December 7 th 2010 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
The Lockheed Martin Digital Tapestry
© 2014 Phoenix Integration, Inc. All Rights Reserved phoenix-int.com Simulation Workflow Automation and Model Management MBSE Workshop / INCOSE IW 2014.
INCOSE IW12 MBSE Workshop 15 INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, PhD Raytheon
Model Based Systems Engineering Visualization Steven Corns Missouri University of Science & Technology.
Agenda 1.Mechanical Design Capabilities 2.Electrical & Electronics Design Capabilities 3.Plant Automation and Test Bench Design Softnice Inc.
International Workshop Jan 21– 24, 2012 Jacksonville, Fl USA INCOSE IW 2012 MBSE Requirement Flowdown Workshop - Outbrief - John C. Watson Principal Member.
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
Technical Operations 12 th July 2010 Dr Phil Spiby Eurostep Limited Integrating Systems Engineering Information with AP233.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
PLM-MBSE integration discussion
MBSE – Usability Working Group IS2011 Supporting the Emergence of Usability in the Community of practice.
Multi-disciplinary Approach for Industrial Phases in Space Projects Evolution of classic SE into MBSE Harald EisenmannAstrium Satellites Joachim Fuchs.
1 Ontological Foundations For SysML Henson Graves September 2010.
Uwe Kaufmann SysML adoption issues OMG SysML Roadmap WG
OSLC PLM Reference model February Summary of the OSLC PLM Reference Model V0.2 February 22 nd 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
MBSE Panel Integrating MBSE into a Multi-Disciplinary Engineering Environment An ELECTRICAL SYSTEM ENGINEERING Perspective Alex Jimenez Jet Propulsion.
Copyright © 2014 InterCAX LLC. All Rights Reserved. SLIM for Model-Based Systems Engineering Manas Bajaj, PhD Chief Systems Officer
Status of SysML v2 Planning & Requirements Berlin, Germany June 16, roadmap:sysml_assessment_and_roadmap_working_group.
The New Generation of CAD Tools
Background - Business Vision
Model-based design inspection based on traceability information models and design slicing Shiva Nejati April 15, 2015.
Session 10 Dr. Dan C. Surber, ESEP
Interface Concepts Modeling Core Team
Is HLA Meeting The Challenge in Enabling SBA?
Integrating Data From Multiple Schedules
Anchor Elements PLM administrative view on the system model
Developing a Layered Reference Model for Information
SMS Roundtable Discussion NAFEMS Americas 2016, Seattle, WA, USA
INCOSE Usability Working Group
PLM4MBSE working group update
SysML v2 Usability Working Session
SysML 2.0 Interface Concepts Modeling Core Team
Ron Williamson, PhD Systems Engineer, Raytheon 20 June 2011
SysML Training Crash Course
Exploring Application Lifecycle Management and Its Role in PLM
SysML 2.0 – Systems Engineering Process (SEP) Working Group
Systems Engineering Concept Model (SECM) Status Update
ASSESS Initiative Update
Your Facility Your Information
System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
Integrating MBSE and PLM
Verification Concepts for SysmL v2
Verification Concepts for SysmL v2
INCOSE Atlanta Chapter Monthly Meeting
INCOSE IW 2014 Town Hall January 27, 2014
Verification Concepts for SysmL v2
SysML 2.0 Interface Concepts Modeling Core Team
MBSE for PLM: Part of the Digital Systems Life Cycle
Status of SysML v2 Planning & Requirements
Presentation transcript:

© 2013 © 2016 Aras aras.com

MBSE and the Business of Engineering © 2013 MBSE and the Business of Engineering Pawel Chadzynski Sr. Director, Product Management, Aras Michael Pfenning PLM Consultant, XPLM No Magic World Symposium, Allen, May 2016 © 2016 Aras aras.com

Product complexity is increasing And creating system design challenges © 2015 Product Complexity Connected Systems of Systems Software Product as a System Electronic 3D Mechanical Product as a Service Electrical 2D Mechanical Smart Connected Products Smart Products Early Products Time © 2016 Aras aras.com

Product vs. Behavior Are these cars products with lots of parts? © 2015 Are these cars products with lots of parts? Or is it a system with behavior working with lots of other systems with behaviors? Is plane a product with lots of parts? Or is it a system with behavior working with lots of other systems with behavior? © 2016 Aras aras.com

Forces new organizational thinking Product vs. Behavior © 2015 Are these cars products with lots of parts? Or is it a system with behavior working with lots of other systems with behaviors? Is plane a product with lots of parts? Or is it a system with behavior working with lots of other systems with behavior? Forces new organizational thinking © 2016 Aras aras.com

V-Process supports Systems Engineering © 2015 V-Process supports Systems Engineering Behavior appears after integration!!! Sub-system integration Requirements System architecting System validation design Component test Needs Process, manufacture, assembly Needs System Requirements System architecting System validation integration Sub-system design Process, manufacture, assembly Component test S E M In theory In reality © 2016 Aras aras.com

MBSE spans many tools & data models © 2015 MBSE spans many tools & data models Behavior part of every design step Domain specific designs © 2016 Aras aras.com

MBSE is not MBD or 3D Mockup © 2013 MBSE – Model-Based Systems Engineering MBD – Model Based Drawing/Design 1. Structure 2. Behavior 3. Requirements 4. Parametrics All eliminate paper documents/drawings but only MBSE captures system behavior © 2016 Aras aras.com

Connecting System models to Design domains in PLM MCAD ALM Testing Manufacture ECAD OK, but how ? © 2016 Aras aras.com

Cross-domain link challenge © 2015 MCAD – deep IP in PLM MCAD file = PLM Part/Assembly (BOM) MCAD files mapped to PLM Parts Electronic/Electrical – no IP in PLM Schematic block? Interconnect/layout blocks? Software – no IP in PLM IDE files  PLM Part/Assembly (BOM) Build process? Released binary? System model – TBD in PLM Requirements? Block diagrams (functional & logical)? Models as input, Reports as outputs? Behavioral complexity is here Parts and part structures are already live in PLM It will take more finesse than this! PLM does not understand ECAD structures (manufacturing files and off-shelf BOM is not a structure) PLM does not understand software structures (binary file is not a structure) PLM does not understand or manage RFL at all © 2015 Aras

MBSE and PDM Model Rev 1 Model Rev 2 Model Rev 3 © 2016 Aras aras.com

MBSE and PLM – today’s target Mechanical System Rev 1 System Rev 2 System Rev 3 © 2016 Aras aras.com

MBSE and PLM – real target Electronic Software Harness Mechanical System Rev 1 System Rev 2 System Rev 3 © 2016 Aras aras.com

MBSE-PLM use cases © 2013 The goal is a full traceability between requirements, models, and product details Top/Down – System model first, then detailed Product design Design everywhere at once – System model is collaborated with on-the-fly Redesign – Field driven requirements changed 1 1 2 2 3 3 © 2016 Aras aras.com

No system context, only domain specific BOM structures PLM Connectors today As Designed B C F E D G I H K M O L J Q R S A Software ALM Mechanical CAD Electronic CAD No system context, only domain specific BOM structures Connectors © 2016 Aras aras.com

That’s why MBSE needs PLM PLM manages post design evolution of physical structures - with strong configuration and change management control across life stages As Designed As Ordered B C F D G I H J K O L Q R S A As Planned As Built As Delivered As Serviced A A A SN #6 A SN #6 A SN #6 B P1 C C C C C D D D D D F SN #89 F SN #89 F SN #97 E F P2 G G G G F T T T H I G J J J J T K K K K J K O L L L L L M O SN #44 O SN #44 O SN #44 O I H H Q Q SN #53 Q SN #71 Q SN #71 “As Designed” is not a true Digital Twin of the “thing” in the field R I H R R R S Q S S S R S © 2016 Aras aras.com

Add System Model structures in PLM Required Functional Logical As Designed As Ordered B C F D G I H J K O L Q R S A As Planned As Built As Delivered As Serviced R1 F1 L1 A A A A SN #6 A SN #6 A SN #6 R2 F2 L2 B P1 C C C R3 SysML tool connector F3 L3 C C D D D R4 F4 L4 D D F SN #89 F SN #89 F SN #97 R5 F5 L5 E F P2 G G G R6 F6 L6 G F T T T R7 F7 L7 H I G J J J R8 F8 L8 J T K K K R9 F9 L9 K J K O L L L L R10 F10 L10 L M O SN #44 O SN #44 O SN #44 R11 F11 L11 O I H H R12 F12 Q Q SN #53 Q SN #71 Q SN #71 R13 F13 R I H R R R R14 F14 S Q S S S F15 R F16 S Required Functional Logical © 2016 Aras aras.com

Logical <> As Designed Traceability gap As Delivered As Built As Planned As Ordered As Designed Logical Functional Required As Serviced R2 R7 R3 R8 R5 R6 R4 R9 R10 R11 F2 F8 F6 F4 F11 F10 F12 F9 F5 F7 F3 L2 L7 L3 L8 L5 L6 L4 L9 L10 B C F E D G I H K M O L J P1 P2 T SN #89 SN #44 SN #97 R14 R13 F13 Q R S SN #53 A SN #6 SN #71 L11 F15 F14 F16 F1 L1 R1 R12 Concept/Link Barrier Logical <> As Designed © 2016 Aras aras.com

Logical <> As Designed Traceability gap As Delivered As Built As Planned As Ordered As Designed Logical Functional Required As Serviced R2 R7 R3 R8 R5 R6 R4 R9 R10 R11 F2 F8 F6 F4 F11 F10 F12 F9 F5 F7 F3 L2 L7 L3 L8 L5 L6 L4 L9 L10 B C F E D G I H K M O L J P1 P2 T SN #89 SN #44 SN #97 R14 R13 F13 Q R S SN #53 A SN #6 SN #71 L11 F15 F14 F16 F1 L1 R1 R12 Concept/Link Barrier Logical <> As Designed © 2016 Aras aras.com

Add SysML Requirement & Logical structures Software ALM SE Requirements SE Logical System Model Mechanical CAD Created by connector Electronic CAD © 2016 Aras aras.com

Add Requirements decomposition ALM Requirements Software ALM MCAD Requirements SE Requirements SE Logical Referenced automatically or manually via connectors System Model Mechanical CAD ECAD Requirements Electronic CAD Each domain has its own requirements breakdown © 2016 Aras aras.com

Add Logical to Physical ALM Requirements ALM Structure Not really “physical” Software ALM MCAD Requirements MCAD Structure SE Requirements SE Logical System Model Mechanical CAD ECAD Requirements ECAD Structure Linked by connectors or manually within PLM (a diagram-like visual drag/drop process?) Electronic CAD © 2016 Aras aras.com

Multiplicity of SE models as part of the same PLM structure Add multiple models ALM Requirements ALM Structure SE Requirements SE Logical Software ALM System Model_1 MCAD Requirements MCAD Structure Multiplicity of SE models as part of the same PLM structure Mechanical CAD SE Requirements SE Logical ECAD Requirements ECAD Structure System Model_n Electronic CAD © 2016 Aras aras.com

Add “System” properties (data/control flow) ALM Requirements ALM Structure SE Requirements SE Logical Software ALM System Model_1 MCAD Requirements MCAD Structure Mechanical CAD Created/linked by connectors or manually within PLM (a diagram-like visual drag/drop process?) SE Requirements SE Logical ECAD Requirements ECAD Structure System Model_n Electronic CAD © 2016 Aras aras.com

Properties are cross-domain negotiable “Contracts” Makes Requirements quantifiable and PLM SE structures behavioral Linked between any two structural items Value, range, enumerated list Units Fixed or a target (a budget) A domain owner On a structural item or accumulative for an assembly Transformation function on a property link Created/linked by connectors or manually (a diagram-like visual drag/drop process within PLM?) Item A Property x Property y Item B f(x) = y f(y) = x © 2016 Aras aras.com

Add simulation data Software ALM System Model_1 Mechanical CAD ALM Requirements ALM Structure Simulation data SE Requirements SE Logical Software ALM System Model_1 Simulation data MCAD Requirements MCAD Structure Simulation data Mechanical CAD SE Requirements SE Logical ECAD Requirements ECAD Structure System Model_n Simulation data Electronic CAD Simulation data © 2016 Aras aras.com

Connectors extract Logical block abstractions per domain Add Logical to Logical ALM Logical ALM Structure SE Requirements SE Logical Software ALM System Model_1 MCAD Logical MCAD Structure Connectors extract Logical block abstractions per domain Mechanical CAD SE Requirements SE Logical ECAD Logical ECAD Structure System Model_n Electronic CAD © 2016 Aras aras.com

Space to negotiate “Contracts” on a Logical block level Enable Negotiations ALM Logical ALM Structure SE Requirements SE Logical Software ALM System Model_1 MCAD Logical MCAD Structure Space to negotiate “Contracts” on a Logical block level Mechanical CAD SE Requirements SE Logical ECAD Logical ECAD Structure System Model_n Electronic CAD © 2016 Aras aras.com

Result: Complex & Overwhelming ALM Logical ALM Structure SE Requirements SE Logical Software ALM MCAD/ECAD Physical structures … linked with … Requirement decomposition Logical structures ALM/Software structures Multiple SysML models Simulation data Control/Data Flows MPP, QP, V&V, Docs, etc. … plus … System Model_1 MCAD Logical MCAD Structure Mechanical CAD SE Requirements SE Logical ECAD Logical ECAD Structure System Model_n Electronic CAD © 2016 Aras aras.com

Reinvent PLM driven Traceability & Navigation Make PLM “invisible” ALM Logical ALM Structure Connectors SYSmap SYS SE Requirements SE Logical Software ALM System Model_1 MCAD Logical MCAD Structure Mechanical CAD Reinvent PLM driven Traceability & Navigation SE Requirements SE Logical ECAD Logical ECAD Structure System Model_n Electronic CAD © 2016 Aras aras.com

Business of Engineering © 2015 Business of Engineering Continuous System & Product design process PLM Digital Twin & Digital Thread configuration management © 2016 Aras aras.com

Partnering with TU Kaiserslautern: Proof of Concept (MagicDraw) © 2013 TU Kaiserslautern: Proof of Concept (MagicDraw) Airbus/IBM/Aras: OSLC-based ALM/PLM integration XPLM/No Magic: MagicDraw integration Aras/Altium: Bringing ECAD into MBSE © 2016 Aras aras.com

Acknowledgements Airbus IBM Dr. Eigner, TU Kaiserslautern © 2013 Airbus IBM Dr. Eigner, TU Kaiserslautern Dr. Zhang, AVIC Altium No Magic ProSTEP INCOSE OMG OASIS XPLM © 2016 Aras aras.com

© 2013 © 2016 Aras aras.com