model-driven innovation

31
© 2017 Maplesoft, a division of Waterloo Maple Inc. Model-Driven Innovation The Role of Multi-domain Dynamic Models for Functional Verification in Model-based Systems Engineering (MBSE) Paul Goossens, VP, Engineering Solutions, Maplesoft Joydeep Banerjee, Application Engineer, Maplesoft Andy Ko, Ph.D., Manager of Engineering Services, Phoenix Integration NIST MBE Summit 2017, Gaithersburg, MD

Upload: others

Post on 28-Dec-2021

7 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Model-Driven InnovationThe Role of Multi-domain Dynamic Models for Functional Verification in Model-based Systems Engineering (MBSE)

Paul Goossens, VP, Engineering Solutions, MaplesoftJoydeep Banerjee, Application Engineer, MaplesoftAndy Ko, Ph.D., Manager of Engineering Services, Phoenix Integration

NIST MBE Summit 2017, Gaithersburg, MD

Page 2: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

ReleaseCandidate

System Validation

System Integration

Subsystem Test

Unit Test

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

ImplementationSoftware/Hardware/

Procurement

Unit Test Plan

Unit Test Plan

Subsystem Verification Plan

System Verification Plan

System Validation Plan

Customer/Market Feedback

$

$$$$$

Detect Design Issues Early

Avoid High Cost of Late-stage Design Changes

Design-change costs increase significantly when required later in the development process

Systems Design & Development Process

Concept Product

$$$$

Adapted from: Forsberg, Kevin, Hal Mooz, and Howard Cotterman.Visualizing Project Management. John Wiley & Sons. Hoboken, NJ. 2005.

Page 3: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

req [Package] Reqs

Performance<<Requirement>>

ID = P001

This vehicle performance must be sporty and provide an affordable driving range for inter-city mobility.

DrivingRange<<PropertyBasedRequirement>>

ID = P002

The driving range must be longer than 300km in the normal drive mode.

lowerBound:RhpReal=300units:RhpString=km

Performance::Velocity<<PropertyBasedRequirement>>

ID = P003

The max velocity must be larger than 130km/h

lowerBound:RhpReal=130units:RhpString=km/h

Performance::Accererlation<<PropertyBasedRequirement>>

ID = P004

The max vehicle acceralation needs to be larger than 4m/s^2 but must be lower than 10m/s^2

lowerBound:RhpReal=4upperBound:RhpReal=10units:RhpString=m/s^2

SystemLimitation<<Requirement>>

ID = S001

For safety and regulations, the vehicle must conform to the conditions defined here

SystemLimitation::BatteryTempera<<PropertyBasedRequirement>>

ID = S002

The battery temperature must be between 250K and 320 K

lowerBound:RhpReal=250upperBound:RhpReal=320units:RhpString=K

SystemLimitation::VehicleWeight<<PropertyBasedRequirement>>

ID = S003

The total weight must not exceed 1900kg

upperBound:RhpReal=19...units:RhpString=kg

weight:Kilogram=1800<<Attribute>>

<<satisfy>>

range:Meter<<Attribute>>

<<satisfy>>

Model-based Systems Engineering vs Model-based Engineering

I say “system engineering”, you say “systems engineering”.…Let’s call the whole thing off…

With apologies to George and Ira…

Page 4: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Model-based Systems Engineering vs Model-based Engineering

Architectural ModelsAnalytical Models

Consistency: Faithful to all known and relevant aspects of the system at the current time

Page 5: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

ReleaseCandidate

System Validation

System Integration

Subsystem Test

Unit Test

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

ImplementationSoftware/Hardware/

Procurement

Unit Test Plan

Unit Test Plan

Subsystem Verification Plan

System Verification Plan

System Validation Plan

Customer/Market Feedback

Systems Design & Development ProcessFunctional Verification

Concept Product

Page 6: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Functional Mockup

ReleaseCandidate

System Validation

System Integration

Sub-system Test

Unit Test

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

ImplementationSoftware/Hardware/

Procurement

Compliance Test Plan

Concept Product

Systems Design & Development ProcessFunctional Verification

Page 7: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Functional Mockup

ReleaseCandidate

System Validation

System Integration

Sub-system Test

Unit Test

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

ImplementationSoftware/Hardware/

Procurement

Compliance Test Plan

Concept Product

Systems Design & Development ProcessFunctional Verification

Page 8: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Functional Mockup

ReleaseCandidate

System Validation

System Integration

Sub-system Test

Unit Test

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

ImplementationSoftware/Hardware/

Procurement

Compliance Test Plan

Concept Product

Systems Design & Development ProcessFunctional Verification

Page 9: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Functional Mockup

ReleaseCandidate

System Validation

System Integration

Sub-system Test

Unit Test

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

ImplementationSoftware/Hardware/

Procurement

Compliance Test Plan

Concept Product

Systems Design & Development ProcessFunctional Verification

Page 10: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Functional Mockup

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

Integration

Verification

Validation

ImplementationSoftware/Hardware/

Procurement

Compliance Test Planreq [Package] Reqs

Performance<<Requirement>>

ID = P001

This vehicle performance must be sporty and provide an affordable driving range for inter-city mobility.

DrivingRange<<PropertyBasedRequirement>>

ID = P002

The driving range must be longer than 300km in the normal drive mode.

lowerBound:RhpReal=300units:RhpString=km

Performance::Velocity<<PropertyBasedRequirement>>

ID = P003

The max velocity must be larger than 130km/h

lowerBound:RhpReal=130units:RhpString=km/h

Performance::Accererlation<<PropertyBasedRequirement>>

ID = P004

The max vehicle acceralation needs to be larger than 4m/s^2 but must be lower than 10m/s^2

lowerBound:RhpReal=4upperBound:RhpReal=10units:RhpString=m/s^2

SystemLimitation<<Requirement>>

ID = S001

For safety and regulations, the vehicle must conform to the conditions defined here

SystemLimitation::BatteryTempera<<PropertyBasedRequirement>>

ID = S002

The battery temperature must be between 250K and 320 K

lowerBound:RhpReal=250upperBound:RhpReal=320units:RhpString=K

SystemLimitation::VehicleWeight<<PropertyBasedRequirement>>

ID = S003

The total weight must not exceed 1900kg

upperBound:RhpReal=19...units:RhpString=kg

weight:Kilogram=1800<<Attribute>>

<<satisfy>>

range:Meter<<Attribute>>

<<satisfy>>

CAD, FEA, CFD, Spice, Saber…

Maple, MapleSim, Simulink…

DOORS, Rhapsody, MagicDraw…

Systems Design & Development ProcessFunctional Verification

Page 11: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Functional Mockup

SystemRequirements

Functional Specification

System-levelSynthesis

Subsystem Design

Detailed Design

Detailed Analysis

ImplementationSoftware/Hardware/

Procurement

Compliance Test Planreq [Package] Reqs

Performance<<Requirement>>

ID = P001

This vehicle performance must be sporty and provide an affordable driving range for inter-city mobility.

DrivingRange<<PropertyBasedRequirement>>

ID = P002

The driving range must be longer than 300km in the normal drive mode.

lowerBound:RhpReal=300units:RhpString=km

Performance::Velocity<<PropertyBasedRequirement>>

ID = P003

The max velocity must be larger than 130km/h

lowerBound:RhpReal=130units:RhpString=km/h

Performance::Accererlation<<PropertyBasedRequirement>>

ID = P004

The max vehicle acceralation needs to be larger than 4m/s^2 but must be lower than 10m/s^2

lowerBound:RhpReal=4upperBound:RhpReal=10units:RhpString=m/s^2

SystemLimitation<<Requirement>>

ID = S001

For safety and regulations, the vehicle must conform to the conditions defined here

SystemLimitation::BatteryTempera<<PropertyBasedRequirement>>

ID = S002

The battery temperature must be between 250K and 320 K

lowerBound:RhpReal=250upperBound:RhpReal=320units:RhpString=K

SystemLimitation::VehicleWeight<<PropertyBasedRequirement>>

ID = S003

The total weight must not exceed 1900kg

upperBound:RhpReal=19...units:RhpString=kg

weight:Kilogram=1800<<Attribute>>

<<satisfy>>

range:Meter<<Attribute>>

<<satisfy>>

CAD, FEA, CFD, Spice, Saber…

Maple, MapleSim, Simulink…

DOORS, Rhapsody, MagicDraw…

ModelCenter

Systems Design & Development ProcessFunctional Verification

Page 12: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Domain-Specific Design

MCADeCAD/EDASoftware …

Control (SW)

Electrical

Mechanical

Multi-domain Systems Design

Page 13: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Control (SW)

Electrical

Mechanical

Modelica: Object-oriented Physical Modeling

Page 14: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Control (SW)

Electrical

Mechanical

Functional Verification against formal requirements models

Page 15: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Post-Processing

Dynamic Load Analysis

Vibration Analysis

Inverse Kinematics and Dynamics

Motor Sizing

Symbolic Tools for Design-space Exploration

Page 16: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

PHX ModelCenter

Page 17: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

PHX Systems Engineering Integration Module

• Connect systems architecture models with engineering analyses to calculate system performance, check requirements, and perform design trade-offs

• Capabilities– Execute SysML parametric diagrams to evaluate designs– Perform requirements compliance analysis using modeling and simulation– Perform design trade-off studies– Update SysML models with analysis results– Import engineering analyses into a SysML model

bddreq

paract

Systems Engineering:Architectural Model

Domain Engineering:Executable Analysis Model

Engineering Analysis

MBSE Analyzer

Page 18: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Electric Vehicle: Battery System Thermal Performance

Stored Energy• Battery Capacity• State-of-Charge• Affects driving range

Temperature Control• Heat flow to/from battery• Thermal effects on battery performance• Active/passive cooling system

Battery Power Electronics and Cooling

Page 19: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Electric Vehicle: Battery System Thermal Performance

Safety requirements

Performance requirements

• Battery must operate in a safe temperaturerange

• Roll / pitch acceleration must be under acertain target

• Stopping distance should not be more thana specific target

• Maximum acceleration / speed should be more than designated targets.

• Must be operable within a designated range

Battery requirements

Cooling system

requirements

• Battery mass, energy density• Max/min operating temperature• Max/min peak temperature• Efficiency vs SOC characteristics• State of Health characteristics

• Heat transfer characteristics• Maximum heat transfer rate• Temperature control system• Multi-component cooling• Maximum weight of the system• Critical temperature detection

Page 20: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Architectural ModelRequirement Diagram

Page 21: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Block Definition Diagram (1)Context Def.

Page 22: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Block Definition Diagram (2)

Page 23: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Architectural Model Parametric Diagram

Page 24: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

The Satisfy Relationship with Requirements

Page 25: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Analytical ModelMulti-domain System-level Dynamics

Page 26: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Normal Loading25°C Ambient, Gentle Grades

Time [sec] Time [sec]

Driveshaft Torque [Nm]

Vehicle Speed [km/h] and Altitude [m] Battery Temperature [°C] and Cooling System State [on/off]

Battery State of Charge [0-1]

Max Battery Temperature

Page 27: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Extreme Loading35°C Ambient, Steep Grades

Driveshaft Torque [Nm]

Vehicle Speed [km/h] and Altitude [m] Battery Temperature [°C] and Cooling System State [on/off]

Battery State of Charge [0-1]

Time [sec] Time [sec]

Max Battery Temperature

Page 28: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Requirements Compliance Testing

Page 29: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc. PHX System Engineering Integration Module

ModelCenter

Maple

Requirements Compliance Testing

Rhapsody

MapleSim

Page 30: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

• MBSE: Process is being increasingly automated through architectural modeling tools

• MapleSim provide rapid functional verification of complex multidomain dynamic systems

• Maple provides powerful environment for data pre- and post-processing as well as managing executable requirements

• ModelCenter brings everything together for rapid requirements-compliance testing, trade-off studies, and impact analysis due to changes in design requirements

• Convergence of tools helps realize the Systems Design (“V“) process

Summary

Page 31: Model-Driven Innovation

© 2017 Maplesoft, a division of Waterloo Maple Inc.

Thank You

Questions?