Amit Fisher

Program Director, Systems Technical Client Relationship Manager IBM Software Group, Rational Email: [email protected]

Closing the gap between Systems level Modeling and Physical simulation in Model Based Systems Engineering

Presentation Number: M-12 © 2014 IBM Corporation

Software and Systems Engineering | Rational The value of being right has never been greater and the cost of being wrong has never been greater… March 26, 2012 Galaxy S Galaxy S II 20 million units 40 million units Galaxy S III 50 million units

Samsung Galaxy S IV sales expected to pass 100 million

On 25 May 2012, an uncrewed variant of SpaceX Dragon became the first commercial spacecraft to successfully attach to the International Space Station 2 October 10, 2012 Jan 28, 2013 “

At Apple, we strive to make world-class products that deliver the best experience possible to our customers.

With the launch of our new Maps last week, we fell

short on this commitment. We are extremely sorry for the frustration this has caused our customers and we are doing everything we can to make Maps better.

”

Tim Cook Apple ’s CEO © 2014 IBM Corporation

Software and Systems Engineering | Rational Why now?

10X faster

adoption

http://www.theatlantic.com/technology/archive/2012/04/the-100-year-march-of Auto Radio Color TV ~80 years ~30 years ~20 years © 2014 IBM Corporation

Software and Systems Engineering | Rational Why now?

10X faster

adoption Smartphone Adoption Rate Fastest in Tech History

“The rate of Android and iOS device adoption among international users has out paced the 1980s PC revolution, the 1990s Internet boom, and the social networking craze “

Innovation

Smartphone

# of years to get to ~60% penetration

2 years !

“133.7 million people in the U.S. owned smartphones (57 percent mobile market penetration) during the three months ending in February 2013,

up 8 percent since November ”

© 2014 IBM Corporation

Software and Systems Engineering | Rational Customers directions… Industry Challenge: Increasing product complexity, pressure for shorter time to market and complex supply chains require systems manufactures to make decisions faster and earlier in the lifecycle

“Design decisions made during conceptual phase are almost never changed. The cost is too high…” European Aerospace Manufacture “We need to commit and provide TCO assessment as early as RFP phase loss of tender, troubled projects…” – over estimation leads to underestimation lead to US Aerospace Manufacture 70% of Lifecycle cost is committed in Conceptual System Design Phase of the Lifecycle ”. Source: DARPA Gap between level of investment and importance… “We became mainly a system integrator of more than 325 suppliers across the globe. Defining integration interface early in the program was both critical and hard…” US Aerospace Manufacture “Daimler coordinated the development of a new standard that enable a virtual product development that can be assembled from a set of models assembled digitally ” European Auto Manufacture

© 2014 IBM Corporation 5

6 Software and Systems Engineering | Rational In parallel, our products become smarter, and more complex… © 2014 IBM Corporation

Software and Systems Engineering | Rational The traditional V approach to Systems Engineering needs respond to these challenges… but represents a waterfall like approach: Product Development Process Requirements Capture & Analysis Systems Engineering Deliver and Deploy System Acceptance 1. “Multi-discipline engineering “starts only after the Systems Engineering and Requirement Engineering phases 2. Integration of the multi disciplined artifact is being done only at the implementation phase (

physical

prototype level) System Validation and Acceptance Systems Analysis & Design Detail Design Multi-Disciplined Engineering Software Mechanical Electronics Module Integration & Test (Sub-)System Integration Testing Integration and Verification Implementation & Unit Test 4. Redesign cycles are common as issues are discovered only at integration testing phase 3. Module and system integration testing is done only after implementation phase. © 2014 IBM Corporation

IBM Confidential

8 Software and Systems Engineering | Rational Continuous Engineering - game-changing capabilities

Continuous Engineering

connected products

is an enterprise capability that helps to by helping engineers

accelerate learning speed

delivery of increasingly complex and throughout the lifecycle, while managing

cost

,

quality

and

risk

.

•

Strategic Reuse

“Don’t reinvent the wheel”

Strategic reuse across the engineering lifecycle – to increase design efficiencies, engineer product lines, and tame complexity

•

Continuous Verification

“Measure twice, cut once”

Verify requirements and design at all stages of the product lifecycle – to prevent rework achieve faster time to quality and

•

Unlocking Engineering Knowledge

“Turn Insight into Outcomes”

Access, unlock and understand all engineering information , regardless of source – to enable the right decisions at the right times

© 2014 IBM Corporation

9 Software and Systems Engineering | Rational The new “V in V” process - early and continuous feedback in early systems design phases Requirements Capture & Analysis Systems Engineering Product Development Process Deliver and Deploy System Validation and Acceptance Deploy and Monitor System Acceptance Systems Analysis & Design Virtual System Integration Testing Detail Design Virtual Analysis Integration Simulation Optimization Virtual Module Integration & Test verificatio n

Virtual

Multi-Disciplined Engineering verificatio n (Sub-)System Integration Testing Module Integration & Test

Physical

Multi-Disciplined Engineering implementation Implementation & Unit Testing © 2014 IBM Corporation

Software and Systems Engineering | Rational Marrying two model driven approaches into an integrated solution  Model Based Systems Engineering ( MBSE) and languages describing system architecture are gaining momentum and market adoption.

– Focus is on the

structure

of the systems (composition) and the

interactions

between subsystems and components 

“Model Driven Systems Engineering is Systems Engineering ”, INCOSE IW, 2013

The value resides in the combination of the different domain-specific analysis technologies and systems level modeling. Closing the gap creates a comprehensive, “system as a whole” analysis platform.

 In parallel, various CAE technologies are being used on a day-to-day basis for domain specific analysis such as Mechanical, Electrical, Electronics, Thermal, Acoustics and more.

– These analysis technologies have evolved over the years with minimal integration consideration © 2014 IBM Corporation 10

Software and Systems Engineering | Rational Why now? Two new Open Standards to leverage © 2014 IBM Corporation

Software and Systems Engineering | Rational Functional Mock-up Interface (FMI)  Open Standard for models exchange and tools integration  FMI 1.0 published in 2010 by ITEA2 MODELISAR (29 partners, 30 M €)  FMI 2.0 published in October 2013 by Modelica Association Project (23 companies and research institutes, https://www.fmi-standard.org/development )  FMI is supported by more than 40 tools ( https://www.fmi-standard.org/tools ) etc.

Engine with ECU Gearbox with ECU Thermal systems Automated cargo door Chassis components, roadway, ECU (e.g. ESP) functional mockup interface for model exchange and tool coupling Blocwitz, Otter, et al, adapted from: https://trac.fmi-standard.org/export/700/branches/public/docs/Modelica2011/The_Functional_Mockup_Interface.ppt

© 2014 IBM Corporation

Software and Systems Engineering | Rational

Functional Mock-up Interface

supplier1 Problems / Needs Component development by supplier Integration by OEM Many different simulation tools supplier2 supplier3 supplier4 supplier5 OEM ?

Solution Reuse of supplier models by OEM: DLL ( model import ) and/or Tool coupling ( co-simulation ) Protection of model IP of supplier Added Value Early validation of design Increased process efficiency and quality supplier1 supplier2 supplier3 supplier4 supplier5 tool 1 tool 2 tool 3 FMI tool 4 tool 5 OEM supplier1 !

OEM supplier2 supplier3 Blocwitz, Otter, et al, adapted from: https://trac.fmi-standard.org/export/700/branches/public/docs/Modelica2011/The_Functional_Mockup_Interface.ppt

13 © 2014 IBM Corporation

Software and Systems Engineering | Rational Emerging tool ecosystem - FMI 14 © 2014 IBM Corporation

Software and Systems Engineering | Rational Closing the gap between Systems level Modeling and Physical simulation - Hybrid Simulation Platform  Allow heterogeneous behavior modeling of the system using domain specific languages and tools (Simulink, Modelica, SysML/Rhapsody)  Allow earlier design run-time verification by simulation, monitoring, analysis of the emergent behavior of the system model  Improve communication between engineering domains (SE, control, mechanical, electrical and etc.) by providing virtual lab environment for all stakeholders  Use accepted open standards and methodologies instead of brittle tools specific ad-hoc solutions

15

© 2014 IBM Corporation

Software and Systems Engineering | Rational Approach  Leverage SysML to specify hybrid (continuous and discrete) system behavior using composition of FMUs and SysML components.  Use FMI to include models from other tools and languages (e.g., Simulink)  Contribute SysML behavioral models to hybrid simulation using FMI  Use joint simulation of components from different tools to analyze the emergent system behavior  Formalize requirements to simulation monitors to allow automatic run-time verification © 2014 IBM Corporation

Software and Systems Engineering | Rational Hybrid Simulation Platform Vision Models SW Domian Simulink model computation algorithm HiL components System Requirements Textual requirements UML based behavioral model 1

Comp1

System model 1

comp2

Contracts/ Simulation Monitors 1

comp3

Physical Domain Modelica Plant Model Simulation center FMU1 FMU2 FMU3 Models, designs and results repository Version control and dependency analysis 17 © 2014 IBM Corporation

Software and Systems Engineering | Rational FMU export from SysML (RHP 8.0.6)  Features – Support FMI 1.0 for Model-exchange – Exported FMU can use Rhapsody animation capabilities

SysML element

Block Output flow port Input flow port Attribute with no corresponding flow port SysML attribute with <> stereotype Initial value of attribute Flow port or attribute with <> stereotype

FMI element

FMU Scalar output discrete variable Scalar input (discrete or continuous) variable Scalar internal discrete variable Scalar internal parameter variable Start value of scalar variable No FMU element

18

© 2014 IBM Corporation

19 Software and Systems Engineering | Rational Example : ITI SimulationX / IBM Rhapsody Integration

Systems Engineering – Rhapsody

• Requirements management • System composition • •

Behavioral modeling

Results monitoring/guarding Model Exchange through

FMU System Simulation –SimulationX

•

Dynamic modeling

• Component library management • Universal

simulation engine

© 2014 IBM Corporation

Software and Systems Engineering | Rational Example ; FMU export plugin - typical tool chain FMU export from IBM Rhapsody and simulation in SimulationX SysML block SysML block SysML block FMU FMU FMU SimulationX model Results Other components (Simulink, FMUs, Modelica) 20 © 2014 IBM Corporation

Software and Systems Engineering | Rational

Example: Automatic Transmission

 Systems engineering requirements: ID = 1 «Requirement» Driveline performance – Acceleration performance (0…100 km/h) The car should accelerate in less than 11s from 0 to 100 km/hr – Top speed in individual gears – Speed or load limits on individual components 1

Driver:DriverM

Attributes «fixed» pulse1_amplitude:F...

out_y:FMIReal ID = 2 «Requirement» Sequential operation of controller The car should reach at least 170 km/hr in 4th gear SysML accPedal:RhpReal 1

rHPController2:RHPController2

Attributes accPedal:RhpReal=0 actualGear:RhpInteger=0 omGB:RhpReal ID = 3 «Requirement» Engine speed Engine speed should not exceed 5500 rpm 1 y2:FMIReal

sensor_CAN:FilterDelay

Attributes  System composition Operations y1:FMIReal 1

actuator:FilterDelay

Attributes u1:FMIReal Operations inA 1 inB inC inD

aT1

Attributes inE om u2:FMIReal in1 1

mapEngine1

om Attributes ctr1 engGear shiftTime ctr2 ctr1 1 v

driveline4WD1

Attributes ctr1  Domain specific behavioral models UML Statechart Simulink NeutralGear tm(swTimeout) Gear1 Reactions actualGear=1; ...

tm(swTimeout) Modelica [omGBomParam12] [omGB

[omGB>omParam23] tm(swTimeout) tm(swTimeout) [omGBomParam34] tm(swTimeout) 21 © 2014 IBM Corporation

22 Software and Systems Engineering | Rational Example : ITI SimulationX / IBM Rhapsody Integration © 2014 IBM Corporation

Software and Systems Engineering | Rational EXAMPLE: iCyPhy - multi-domain simulation • Composition of multiple Model of Computation under single Framework utilizing FMI • • • Heterogynous modeling and co-simulation SysML as entry point for Heterogynous modeling and analysis Hocks to commercial tools such as Rational Rhapsody, Modelica and Simulink • Performance analysis • • Aspect based Hocks to standard architecture languages such as systemsC and AADL © 2014 IBM Corporation

24 Software and Systems Engineering | Rational What can you do next ?  Engage with IBM to get detailed demo of new FMI based integration capabilities  Jointly define a small pilot to evaluate needs and value  Engage with IBM to influence product directions © 2014 IBM Corporation