1 / 24

The value of being right has never been greater

Amit Fisher Program Director, Systems Technical Client Relationship Manager IBM Software Group, Rational Email: amfisher@us.ibm.com. Closing the gap between Systems level Modeling and Physical simulation in Model Based Systems Engineering Presentation Number: M-12.

shiloh
Download Presentation

The value of being right has never been greater

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Amit FisherProgram Director, Systems Technical Client Relationship ManagerIBM Software Group, Rational Email: amfisher@us.ibm.com Closing the gap between Systems level Modeling and Physical simulation in Model Based Systems EngineeringPresentation Number: M-12

  2. and the cost of being wrong has never been greater… The value of being right has never been greater March 26, 2012 October 10, 2012 Galaxy S - 20 million units Galaxy S II - 40 million units Galaxy S III - 50 million units Samsung Galaxy S IV sales expected to pass 100 million 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 On 25 May 2012, an uncrewed variant of SpaceX Dragon became the first commercial spacecraft to successfully attach to the International Space Station

  3. Why now? 10X faster adoption http://www.theatlantic.com/technology/archive/2012/04/the-100-year-march-of-technology-in-1-graph/255573/

  4. 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 “ “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”

  5. 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 70% of Lifecycle cost is committed in Conceptual System Design Phase of the Lifecycle”. Source: DARPA “We need to commit and provide TCO assessment as early as RFP phase – over estimation leads to loss of tender, underestimation lead to troubled projects…” US Aerospace Manufacture “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 Gap between level of investment and importance… “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

  6. In parallel, our products become smarter, and more complex…

  7. The traditional V approach to Systems Engineering needs respond to these challenges… but represents a waterfall like approach: 4. Redesign cycles are common as issues are discovered only at integration testing phase Product Development Process System Acceptance Deliver and Deploy Systems Engineering RequirementsCapture & Analysis System Validation and Acceptance 1. “Multi-discipline engineering “starts only after the Systems Engineering and Requirement Engineering phases Systems Analysis & Design (Sub-)System Integration Testing Multi-Disciplined Engineering Software Mechanical Electronics DetailDesign 3. Module and system integration testing is done only after implementation phase. Integration and Verification Module Integration & Test Implementation & Unit Test 2. Integration of the multi-disciplined artifact is being done only at the implementation phase ( physical prototype level) 7 IBM Confidential

  8. Continuous Engineering - game-changing capabilities Continuous Engineering is an enterprise capability that helps to speed delivery of increasingly complex and connected products by helping engineers acceleratelearning 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 and achieve faster time to quality • 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

  9. The new “V in V” process - early and continuous feedback in early systems design phases Product Development Process Deliver and Deploy Deploy and Monitor Systems Engineering System Validation and Acceptance System Acceptance RequirementsCapture & Analysis verification Virtual Analysis Integration Systems Analysis & Design Virtual System Integration Testing (Sub-)System Integration Testing Simulation Optimization DetailDesign verification Virtual Multi-Disciplined Engineering Physical Multi-Disciplined Engineering Virtual Module Integration & Test Module Integration & Test implementation Implementation & Unit Testing

  10. 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 • 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 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.

  11. Why now? Two new Open Standards to leverage

  12. 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. Enginewith ECU Gearboxwith ECU Thermalsystems Automatedcargo 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

  13. supplier1 supplier2 supplier3 supplier4 supplier5 OEM ? supplier2 supplier1 supplier3 supplier5 supplier4 Solution • Reuse of supplier models by OEM: • DLL (model import) and/or • Tool coupling (co-simulation) • Protection of model IP of supplier tool 1 tool 5 tool 3 tool 2 tool 4 OEM FMI ! supplier1 Added Value • Early validation of design • Increased processefficiency and quality OEM supplier2 supplier3 Functional Mock-up Interface Problems / Needs • Component development by supplier • Integration by OEM • Many different simulation tools Blocwitz, Otter, et al, adapted from: https://trac.fmi-standard.org/export/700/branches/public/docs/Modelica2011/The_Functional_Mockup_Interface.ppt

  14. Emerging tool ecosystem - FMI

  15. 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

  16. 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

  17. Simulink model computation algorithm Hybrid Simulation Platform Vision Models Simulation center System Requirements HiL components Textual requirements SW Domian FMU1 FMU2 FMU3 Modelica Plant Model UML based behavioral model System model Contracts/ Simulation Monitors Physical Domain Models, designs and results repository Version control and dependency analysis

  18. FMU export from SysML (RHP 8.0.6) • Features • Support FMI 1.0 for Model-exchange • Exported FMU can use Rhapsody animation capabilities

  19. 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

  20. Example ; FMU export plugin - typical tool chain FMU export from IBM Rhapsody and simulation in SimulationX FMU SysML block SimulationX model Results FMU SysML block FMU SysML block Other components (Simulink, FMUs, Modelica)

  21. Example: Automatic Transmission • Systems engineering requirements: • Acceleration performance (0…100 km/h) • Top speed in individual gears • Speed or load limits on individual components • System composition • Domain specific behavioral models SysML Simulink UML Statechart Modelica

  22. Example : ITI SimulationX / IBM Rhapsody Integration

  23. 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

  24. 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

More Related