Copyright © 2014 InterCAX LLC. All Rights Reserved. SLIM for Model-Based Systems Engineering Manas Bajaj, PhD Chief Systems Officer Presentation at INCOSE IW 2014 Los Angeles Model Management Working Group Jan 26,

Copyright © 2014 InterCAX LLC. All Rights Reserved. A week in the life of a system engineer

Copyright © 2014 InterCAX LLC. All Rights Reserved. Challenge Point-to-Point Ad-Hoc Information Flows Use of models in systems engineering IS NOT model-based systems engineering (MBSE) 3

Copyright © 2014 InterCAX LLC. All Rights Reserved Model-Based Systems Engineering analysis & simulation models CAD models spreadsheets Operational concepts documents But most of the engineering will still be done with the same tools (CAD/ CAE) and much of the detailed design information will still be stored in spreadsheets and databases, not in the SysML model. So, The System Model is the SysML Model plus…

Copyright © 2014 InterCAX LLC. All Rights Reserved. But how do we realize the MBSE vision? Heterogeneous models (languages and tools) Multi-fidelity models Connections across models – granularity – purpose Semantics of models and their connections Concurrent evolution of models Models distributed in repositories Version managed models and their elements …but we need a unifying system architecture 5

Copyright © 2014 InterCAX LLC. All Rights Reserved. System LIfecycle Management (SLIM) Enabling Model-Based Systems Engineering 6

Copyright © 2014 InterCAX LLC. All Rights Reserved. Total System Model Bill-of-Systems (BOS) 7

Copyright © 2014 InterCAX LLC. All Rights Reserved. Total System Model History 8 Technical Data Packages auto-generated from TSM graph

Copyright © 2014 InterCAX LLC. All Rights Reserved. 9 SLIM Dashboard

Copyright © 2014 InterCAX LLC. All Rights Reserved. Basic SLIM Functions Connect SysMLPLM/Repository Generate Update Execute Check Description (Integration patterns) SLIM creates a connection between existing elements in the SysML element and repository. This may be a simple traceable link or a detailed data mapping between element attributes. These connections are stored and managed by SLIM. SLIM generates an element on one side from an element on the other. SLIM manages a persistent connection between them. SLIM checks for changes at the repository end of a connection. This may include generation of a difference report. SLIM updates the element at one end of the connection based on the element at the other end. This may include changes in the element structure or attribute values. SLIM triggers execution of an element (e.g. a MATLAB function) managed in the repository as part of a SysML model execution.

Copyright © 2014 InterCAX LLC. All Rights Reserved. TSM = Graph of Artifacts and Connections 11 Artifacts Concept-based -Requirements -Part -Shape -Function -Relationships… Tool/repository-based -SysML artifacts -Teamcenter artifacts -Windchill artifacts -MySQL database artifact -CAD model artifact -Excel model artifact -MATLAB/Mathematica model artifact -… Artifacts Concept-based -Requirements -Part -Shape -Function -Relationships… Tool/repository-based -SysML artifacts -Teamcenter artifacts -Windchill artifacts -MySQL database artifact -CAD model artifact -Excel model artifact -MATLAB/Mathematica model artifact -… Connections -Purpose / behavior -Executable (services) -Reference, Data map, Function wrap, Model Transform,… Connections -Purpose / behavior -Executable (services) -Reference, Data map, Function wrap, Model Transform,…

Copyright © 2014 InterCAX LLC. All Rights Reserved. Understanding model semantics to make sense of connections SysML – Requirements, Blocks, Properties (value, part, reference, constraint), Constraint Blocks, Activity, State Machines, Interaction, Use cases… Teamcenter – Item, Part, Part Occurrence, Requirement, Paragraph, Requirement Spec (and their revisions), Precise/Imprecise BOM, Trace Link (Direct/Indirect),… Windchill – Product, Requirement, Part, Document, EPMDocument (and their masters), Part usage, Part occurrence, … CAD (NX, Creo) – Assembly, part, shape, parameters, mass properties, … Database (MySQL) – Datable, Table, Row, Columns, … 12 Connection and Integration Patterns

Copyright © 2014 InterCAX LLC. All Rights Reserved. SLIM + Analysis Expanding our SysML parametric solvers in the context of the Total System Model in SLIM – ParaMagic, Melody, ParaSolver, Solvea –

Copyright © 2014 InterCAX LLC. All Rights Reserved. Status of SLIM SLIM 1.0 beta launched in Dec 2013 as plugins for MagicDraw and Rhapsody Ability to connect to / generate / compare / sync SysML elements with model elements in Teamcenter, Windchill, MySQL database, and local/shared file systems SLIM 1.0 launch planned for Feb 2014 Visit for detailswww.intercax.com/slim Demo on Mon Jan 10:45 AM in the Model Management Working Group session 14

Copyright © 2014 InterCAX LLC. All Rights Reserved. Where is SLIM Going? New Architecture Elements: e.g. Functions, Use Cases, State Models,… New SysML Tools: Artisan, EA New Repositories: Enovia, Git, Subversion New Databases: Oracle, MS Excel SysML-MCAD: NX, Creo SysML-Requirements: CRADLE, DOORS SysML-Simulation: MATLAB, Simulink New Capabilities will be driven by Customer Demand 15

Copyright © 2014 InterCAX LLC. All Rights Reserved. We would love to hear from you… Manas Bajaj, PhD Chief Systems Officer web:

Copyright © 2013 InterCAX LLC. All Rights Reserved. SLIM: SYSML-CAD INTEGRATION 17

Copyright © 2014 InterCAX LLC. All Rights Reserved. Viewing CAD models connected to SysML model elements 18 Use Case 1 – If a SysML element is connected to a CAD file, user can visualize the CAD file from the SysML dashboard

Copyright © 2014 InterCAX LLC. All Rights Reserved. SysML-Creo/ProE Data Map Use Case 2 – Selected parameters from a CAD file are used to generate a corresponding SysML block and value properties.

Copyright © 2014 InterCAX LLC. All Rights Reserved. SysML-Creo Data Map