Simplifying MBSE Tasks with Capella and MapleMBSE

© 2020 Maplesoft, a division of Waterloo Maple Inc.
MapleMBSE
An Excel-basedMBSE Tool for
IntegratingSpreadsheet-basedTasks with Capella SystemsModels
PaulGoossens,VPMBSESolutions
BharaniMohan,MBSEDeveloper

Challenges to Adoption of MBSE

Challenges to Adoption of MBSE
People & Processes!
Chami, Mohammad & Bruel, Jean-Michel.
(2018). A Survey on MBSE Adoption Challenges.

Capella…
Systems Model
“Single Source of Truth”
Structure
Behavior
Requirements
Parameters
How to scale Systems Engineering
beyond Systems Engineers?
Architecture
Systems Engineers
Results
Spreadsheets
Documents
Email, etc
Project Stakeholders
Engineering, UX, software,
Business processes,
project management,
procurement etc
Parameters, Constraints, etc

Capella…
Systems Model
Structure
Behavior
Requirements
Parameters
Architecture
Systems Engineers
Results
Spreadsheets
Documents
Email, etc
Business processes,
project management,
procurement etc
Parameters, Constraints, etc
Time-
wasting
rework

Capella…
Systems Model
Structure
Behavior
Requirements
Parameters
Design Changes
Architecture
Systems Engineers
Business processes,
project management,
procurement etc
Task-specific Views
V&V: Compliance Tests
Trade studies, FMEA, etc
MapleMBSE
Design Review

Systems Model
Structure
Behavior
Requirements
Parameters
Model updates
Model updates
MapleMBSE
Systems Engineering for All Project Stakeholders
MapleMBSE
Intuitive, Excel-based UI for viewing, entering,
and modifying system design information
Synchronized bi-directional updates
between Excel and systems model
Integration with standard SE platforms, such as
Rhapsody, MagicDraw/Teamwork Cloud (SysML)
and Capella
Customizable UI for task-
specific views and analyses

• Tasks that require large quantities of information to be integrated with
the systems model, eg Equipment Lists (MEL)
• Tasks that require specialist skills/knowledge to generate information
needed in the systems model, eg Requirement decomposition
• Tasks that are already being performed using spreadsheets, safety
analysis, FMEA, energy/mass/cost budgets
• Tasks that require analysis of the systems model, eg impact analysis,
Design Structure (DSM), Traceability
Application – Identifying the Ideal use-case

Typical Tasks in the Arcadia Work-flow

It is a list of all the part in a System/Sub-
System with common attributes
• Mass, Quantity, sub-system, Part
Number, type, Power, etc.
• Import a list of component from Lunar
Relay Satellite Communications
Systems
10
MEL Import

• Domain extension using PVMT add-
ons
• Defined scope to Physical
Component
• Added new properties based on the
importing excel sheet
11
MEL Import

Demonstration work-flow: FMEA
MapleMBSE
Capella
Excel
Capella Model
Systems Engineer
• System architecture
• Requirements
• MapleMBSE Templates &
Configurations
Safety Engineer
• Identify failure modes
• Determine severity, frequency,
ease of detection
• Determine RPN

Physical Components
from Capella model
Create identified failure
modes as model
elements
PVMT add-ons
Create a FMEA table
S O D
Calculate RPN
iterative
process
Demonstration work-flow: FMEA
Add mitigating actions for
failure modes into the
Capella model
Update model

Case Study: Nissan — Overview
Integration of MapleMBSE with Nissan7 Systems Engineering Process
Nissan7 Modeling with Spreadsheet
through MapleMBSE
Component Function Guide Word Timing Description System Vehicle Severity
F1 Engine
Reduce the engine
rpm at shift-up to
adjust the rotation
difference between
drive shaft and
counter shaft to be
selected
F1 Engine
Reduce the engine
rpm at shift-up to
adjust the rotation
difference between
drive shaft and
counter shaft to be
selected 1-Not_Provided
Do not reduce or increase
engine rpm even if the
controller requests to it
Engine ECU bug
ECU mulfunction
Engine Safety
treatment
Clutch may be
damaged
Unintended
accelaeration A
Counter Measure
Failure ModeFMEA
No.
Target
Cause
Effect (Hazard Analysis)
Physical Means
1st 2nd Body ClutchSignalGenerator Driver Engine Gear1st Gear2nd Gear3rd Gear4th ShiftController Tire
Drivability Keeping up of creeping Keep slowly letting in and out the clutch when the carstarts slowly in the first gear X X X X X
Drivability Keeping up of creeping Slowly engage the clutch when the rotation difference between crank shaft and drive shaft is large X X X X X X X
PerformanceThe DCT shifts gears to reduce fuel consumptionThe DCT should select an optimal gear by considering the drivers direction and the current conditions of the car X X X
Safety The DCT must assure the safety Functiontotemporarily keepthe current gearwheneverit receivesany illegalinstructionsordetectswrong condition X
Safety The DCT must assure the safety The DCT never selects any gear that is not safe X
Drivability The DCT shoud shift smoothly Reduce the engine rpm at shift-uptoadjust the rotationdifference betweendrive shaft andcountershaft tobe selected X X X
Requirements
Function
Integrated Model
Management
Score 223 320 308
Adopted TRUE TRUE
Criterion Weight
Reduce the engine
rpm at shift-up to
adjust the rotation
difference between
drive shaft and
counter shaft to be
selected
The DCT properly
adjusts the time to
engage the clutch to
alleviate shock
The DCT should select
an optimal gear by
considering the
drivers direction and
the current conditions
of the car
Good efficiency at low rpm 8 1 3 4
Good efficiency at mid rpm 7 3 6 6
Good efficiency at high rpm 6 4 3 3
Low heat emission 8 7 8 7
Cost 10 5 10 8
Robustness 8 8 9 10
Nissan’s Process
Source: Miyashita, Hisashi, Hideki Tai, and Shunichi Amano,
IBM Research - Tokyo, "Controlled modeling environment
using flexibly-formatted spreadsheets." in ICSE 2014, ACM

Case Study: Nissan — Productivity
MapleMBSE is proven to be effective for many engineers to develop the design of a vehicle
system collaboratively, which leads to significant improvement in design performance for Nissan
0
40
80
120
160
MapleMBSE MBSE Tool
Operating Time[min]
Context Diagram
Use Case Diagram
Trade off Matrix
6 Guide Words
[min]
Context
Diagram
Use Case
Diagram
Trade off
Matrix
6 Guide
Words
Total
MapleMBSE 6 5 5 14 30
MBSE Tool 10 20 32 67 129
30
129
[min]

Case Study: Nissan — Effectiveness
According to our experiments (presented in ICSE 2014) of Automotive SysML modeling,
MapleMBSE greatly improves productivity across all system-design tasks
MapleMBSE almost halves the
time!
MapleMBSE reduced the
errors to 1/4!
MapleMBSE
MBSE Tool
MapleMBSE
MBSE Tool

Case Study: Nissan — Error Analysis
Result suggest that typical modeling tools impose unfamiliar UI and complexities of
SysML on users
MapleMBSE MBSE tool
Simple mistakes only
(1) Familiar, intuitive Excel UI
(2) Spreadsheets optimized to do the tasks
(3) No need for deep knowledge of the modeling language (SysML)Source: Miyashita, Hisashi, Hideki Tai, and Shunichi Amano,

MapleMBSE
Facilitate Design Collaboration Across the Enterprise
Electronics
Mechanical
Software
UX
Procurement
Project Management
Broaden Engagement with the
Systems Engineering Process
Reduce Risk,
Errors and CostsRamp Up,
Right Away
Fully
Customizable
IT
Systems
Engineering
Systems
Model

Questions?
www.maplembse.com
pgoossens@maplesoft.com

MapleMBSE Architecture Overview
MapleMBSE enables systems-model development Excel. Since it is built on top of
EMF, we can integrate many modeling tools by providing Adapters
MapleMBSE
Model Spreadsheets in Excel
Update
Change Event
End-user
EMF-based Interface
Teamwork
Cloud
CapellaRhapsody etc…MapleMBSE Adapters
Configurations,
TemplatesSystems Expert

• Examples(querying operational activity):
– data-source oparch =
Root/ownedModelRoots[SystemEngineering]/ownedArchitectures[
oa::OperationalAnalysis]
– data-source opRootFun =
oparch/ownedFunctionPkg[oa::OperationalActivityPkg|name =
"Operational
Activities"]/ownedOperationalActivities[oa::OperationalActivity|n
ame = "Root Operational Activity"]
– data-source opFunction
=opRootFun/ownedFunctions[oa::OperationalActivity]
• […] part is called a qualifier
2
1
QPE: Query Path Expression
Query Path Expression is something like a simplified XPath to query model elements
Model
Root Operational
Activity
Operational
Activity

MapleMBSE Demos on YouTube
Introduction to MapleMBSE
High-level overview of how MapleMBSE allows
engagement with the systems engineering process by
all project stake-holders across the enterprise
Easy-to-use Excel-based UI for Systems Engineering
MapleMBSE gives you an intuitive, Excel®-based
interface for easily entering system definitions
without having to be an expert in your company’s
MBSE tool.
Allows all stakeholders to contribute to the Systems
Engineering process
With MapleMBSE, you don’t need to be a systems
engineering expert to contribute to the process. Task-
specific views are excel-based and show each
stakeholder only what they need to see.
Simplifies information-entry, reducing risk of errors
MapleMBSE allows you to use natural language and
numerical inputs to reduce errors associated with the
complex entry mechanisms of MBSE tools.
Offers rapid customization of model views and data
integration
Because every systems engineering project is
different, MapleMBSE allows you to provide
customized model views that best suit the task at
hand.
MapleMBSE and No Magic Teamwork Cloud Work-
flow
Detailed demonstration of how MapleMBSE users
can interact with systems models on Teamwork Cloud
for No Magic/Dassault Systemes

MapleMBSE Demos on YouTube
MapleMBSE Demo with Rhapsody and MagicDraw
This shows how MapleMBSE works with Rational
Rhapsody and MagicDraw, both well-established
diagramming tools used extensively by system engineers.
Fundamentally, the spreadsheets are a “views” into the
system model that can be edited by adding more detailed
structures and requirements then submitted back into the
system model.
MapleSim ModelCenter Demo
This shows how the data in a systems model can be
integrated with other simulation and analysis tools (in this
case, Maple and MapleSim) to perform functional
verification of a proposed system design, using
ModelCenter from Phoenix Integration. By simulating the
system’s dynamic performance over a range of duty
cycles, key properties can be tested to ensure compliance
with the requirements very early in the design process.
JPL/OpenMBEE Managed Excel
This is a demo that was developed by one of our
customers, JPL, that shows the workflow between
different stakeholders who perform different tasks, but
the results of these tasks have a direct impact on other.
Both can work in MapleMBSE without needing to work in
MagicDraw at all.
JPL/OpenMBEE MultiBranch Excel
customers, JPL, that shows how different stakeholders can
be working on different branches of the same system
model. MapleMBSE automatically builds the view that is
scoped by the branch of the model that is selected.
JPL/Syndeia Excel NX Integration
customers, JPL, that shows the integration of MapleMBSE
with Siemens NX through Syndeia from Intercax, and
MagicDraw and CAMEO Systems Modeler from No Magic.

Simplifying MBSE Tasks with Capella and MapleMBSE

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Simplifying MBSE Tasks with Capella and MapleMBSE

Similar to Simplifying MBSE Tasks with Capella and MapleMBSE (20)

More from Obeo

More from Obeo (19)

Recently uploaded

Recently uploaded (20)

Simplifying MBSE Tasks with Capella and MapleMBSE