System of systems modeling with Capella
Download as PPTX, PDF•2 likes•1,596 views
1. The document provides guidelines for modeling systems of systems and internet of things using Capella and ARCADIA. 2. It discusses modeling constituent systems as separate Capella projects due to different stakeholders. 3. The "system to subsystem transition" feature in Capella allows creating sub-projects to represent constituent systems. 4. Capella library projects can be used to reuse components or systems across projects.
System of systems modeling with Capella
- 2. Introduction Please note your microphone is muted Click the Q&A icon and ask your questions 10+ min at the end of the presentation Laurent Delaigue [email protected] www.obeosoft.com Copyright Obeo @2022
- 4. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 4 Introduced to Capella. Shortly after the introduction I built my first very detailed model. Siemens and OBEO announcing partnership and product based on Capella Launched an internal user group at Siemens to promote SMW/Capella Mentored middle school students on Capella and they won Won a state (PA) 4-H State Competition! University Michigan began pilot course with Capella Lunch with Larry Master Class Series Presented Capella Ventilator at two international events University Michigan began pilot course with Capella Launched YouTube Channel Innovating with Capella University of Michigan presents Keynote at INCOSE IW My personal history with Capella Solar Charger 2017 2018 2019 2020 2021 2022
- 5. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 5 Capella can support the modeling System of Systems Multi-Level Mission and Drone Definition: • A System of Systems (SoS) is a collection of independent systems, integrated into a larger system that delivers unique capabilities. • The independent constituent systems collaborate to produce global behavior that they cannot produce alone. INCOSE Systems of System Primer INCOSE-TP-2018-003.01.0
- 6. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 6 Capella meets the unique challenges of System of Systems Constituent Systems Multi-Level Mission and Drone • Unique Issues/Attributes of Constituent Systems • Constituent systems may make decisions or upgrades without considering the rest of the SoS. • Constituent systems may withdraw (possibly without warning) from the SoS if their own goals conflict with SoS goals • Separate constituent systems are often drawn from different engineering disciplines, and the SoS itself is commonly large-scale and usually highly complex. • Testing and verifying upgrades to an SoS is difficult and expensive (sometimes prohibitively) due to scale, complexity and constant evolution INCOSE Systems of System Primer INCOSE-TP-2018-003.01.0
- 7. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 7 Systems of Systems models and Internet of Things models have things in common Battery Powered Hand drill and IOT Charger Multi-Level Mission and Drone System of Systems Strong Weak INCOSE Systems of System Primer INCOSE-TP-2018-003.01.0
- 8. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 8 Guidelines for System of Systems modeling using Capella and ARCADIA Method 1. A Project has only one system, it becomes the “system” of a SoS. 2. A Project should focus on the stakeholders for the “system” of a SoS. 3. A system may be composed of • constituent systems, and/or • components. 4. The Functional Chains deliver the needs of stakeholders across the Constituent Systems and/or Components. 5. System of Systems will result in a set of Capella Projects, due to different stakeholders of CS and Components. 6. Capella projects can use “System to Subsystem transitions” to create sub-projects that represents constituent systems or components of primary project. 7. Capella projects can use a Capella Library Projects to reuse components or constituent systems.
- 9. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 9 Guideline for SoS model: A project has only one system, it becomes the “System” of a SoS Roques, Pascal. “MBSE with the ARCADIA Method and the Capella Tool.” (2016). https://api.semanticscholar.org/CorpusID:9283412
- 10. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 10 Guideline for SoS model: A Project should focus on the stakeholders for the “system” of SoS Roques, Pascal. “MBSE with the ARCADIA Method and the Capella Tool.” (2016). https://api.semanticscholar.org/CorpusID:9283412
- 11. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 11 Guideline for SoS model: A system may be composed of constituent systems, and/or components. Roques, Pascal. “MBSE with the ARCADIA Method and the Capella Tool.” (2016). https://api.semanticscholar.org/CorpusID:9283412
- 12. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 12 Guideline for SoS model: The Functional Chains deliver the needs of stakeholders across the Constituent Systems and Components. Bonnet, Stephane; Voirin, Jean-Luc, Navas. Jaun: “Arcadia and Capella: Augmenting requirement with models to improve the articulation between systems engineering levels and optimize V&V practices. Component = SoS Constituent System SoS Capability
- 13. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 13 Example: SoS Model Level Model – Disaster Recovery System
- 14. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 14 SoS Example – Disaster Recovery System
- 15. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 15 SoS Example –– Disaster Recovery System
- 16. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 16 SoS Example – Disaster Recovery System
- 17. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 17 SoS Example – Disaster Recovery System
- 18. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 18 SoS Example – Disaster Recovery System
- 19. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 19 SoS Example – Disaster Recovery System
- 20. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 20 Guideline for SoS model: System of Systems will result in a set of Capella Projects, due to different stakeholders for CSs and Components. Reasons: • Constituent systems stakeholders may be different than the System. • Constituent systems lifecycles may be different than System. • Many cases they will pre-exist the “System” • System may have intellectual property they do not want to expose to Prime Contractor, Partner or Supplier. • Constituent Systems may be developed by Prime Contractor, Partner or Supplier • Constituent Systems may have Intellectual Property they do not want to place in higher level model.
- 21. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 21 Stakeholders' priorities drive the need for a network of models. INCOSE Systems of System Primer INCOSE-TP-2018-003.01.0
- 22. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 22 Guideline for SoS model: Capella projects can use “System to Subsystem transitions” to create sub-projects Faisandier, A. 2012. Systems Architecture and Design. Belberaud, France: Sinergy'Com. Guide to the Systems Engineering Body of Knowledge (SEBoK),version 2.5, Page 252 Capella rich meta-model support this recursive process. • System to Subsystem Transition • Addon for Capella • Built into Siemens System Modeling Workbench • Components, Functions, and Functional Chains are transitioned • Siemens latest SMW 6 release is leveraging this capability to carve out a portion of a model for transition to SysML V2 https://www.youtube.com/watch?v=njW_zdE_FzI Daly, Jim: Arcadia/Capella for a large complex mechanical system, Apr 2019.
- 23. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 23 Demo - System to System Transition System to Subsystem Transition (Recursion) allow • Creation of a Constituent System From Parent • Selectively transfer content from Parent Model to Constituent System Model
- 24. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 24 Guideline for SoS model: Capella projects can use a Capella Library Project to reuse components or constituent systems. Systems can be composed of pre- existing content. Capella supports reuse with Libraries and REC/RPL concept. • A library can define the Reusable Element. • A library and be referenced by a model and Replicas can be created from the library’s Reusable Element.
- 25. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 25 Demo - Inclusion of FLIR into a model from Siemens Xcelerator
- 26. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 26 Guidelines for System of Systems and Internet of Things modeling using Capella and ARCADIA Method 1. A Project has only one System, it becomes the “system” of a SoS. 2. A Project should focus on the stakeholders for the “system” of a SoS. 3. A system may be composed of • constituent systems (CS), and/or • components. 4. The Functional Chains deliver the needs of stakeholders across the Constituent Systems and/or Components. 5. System of Systems will result in a set of Capella Projects, due to different stakeholders CSs and Components 6. Capella projects can use “System to Subsystem transitions” to create sub-Projects that represents constituent systems or components of primary project. 7. Capella projects can use a Capella Library Project to reuse components or constituent systems.
- 27. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 27 Internet of Things are on the weaker side of the SoS spectrum, but same guidelines apply. Battery Powered Hand drill and IOT Charger Multi-Level Mission and Drone System of Systems Strong Weak Reasons • Stakeholders may be shared. • Constituent System lifecycle may align to “system” or other constituents' systems. • Intellectual Property may still persist. • Suppliers may still be engaged. • IoT infrastructure is a • Constituent System
- 28. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 28 Guideline for IOT model: A project has only one System. Roques, Pascal. “MBSE with the ARCADIA Method and the Capella Tool.” (2016). https://api.semanticscholar.org/CorpusID:9283412
- 29. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 29 Guideline for IOT model: A Project should focus on the stakeholders for that system. Roques, Pascal. “MBSE with the ARCADIA Method and the Capella Tool.” (2016). https://api.semanticscholar.org/CorpusID:9283412
- 30. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 30 Guideline for IOT model: A system may be composed of constituent systems, and/or components. Roques, Pascal. “MBSE with the ARCADIA Method and the Capella Tool.” (2016). https://api.semanticscholar.org/CorpusID:9283412
- 31. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 31 Guideline for IOT model: The Functional Chains deliver the needs of stakeholders across the Constituent Systems and Components. Bonnet, Stephane; Voirin, Jean-Luc, Navas. Jaun: “Arcadian and Capella: Augmenting requirement with models to improve the articulation between systems engineering levels and optimize V&V practices.
- 32. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 32 IOT Example - Intelligent Connected Battery Charger
- 33. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 33 IOT Example - Intelligent Connected Battery Charger
- 34. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 34 IOT Example - Intelligent Connected Battery Charger
- 35. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 35 IOT Example - Intelligent Connected Battery Charger
- 36. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 36 IOT Example - Intelligent Connected Battery Charger
- 37. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 37 IOT Example - Intelligent Connected Battery Charger
- 38. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 38 Guideline for IOT model: System of System will result in a set of Capella Projects, due to different stakeholders. Assume it is not going to be all done in one project. Reasons: • Constituent systems Stakeholders may be different than the System. • Constituent systems lifecycles may not be the same. INCOSE Systems of System Primer INCOSE-TP-2018-003.01.0
- 39. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 39 Guideline for IOT model: Capella projects can use “System to Subsystem” transitions to create sub-projects that represents systems of primary project. System to Subsystem Transition (Recursion) is used • Complexity of lower level • Expectation that subsystem does not exist and component.
- 40. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 40 Guideline for IOT model: Capella project can use a Capella Library Project that contain reusable components to build a system.
- 41. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 41 Summary: Guidelines for System of Systems modeling using Capella and ARCADIA Method. 1. A Project has only one System, it becomes the “System” of a SoS 2. A Project should focus on the stakeholders for that “System” of and SoS 3. A system may be composed of • constituent systems, and/or • components. 4. The Functional Chains deliver the needs of stakeholders across the Constituent Systems and Components. 5. System of Systems will result in a set of Capella Projects, due to different stakeholders for the CSs and Components. 6. Capella projects can use “System to Subsystem transitions” to create sub-Projects that represents systems of primary project. 7. Capella projects can use a Capella Library Project that contain reusable components to build a system.
- 42. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 42 Stay tuned to “Innovating with Capella” for LORAWAN Helium Based Solution Battery Powered Hand drill and IOT Charger Multi-Level Mission and Drone System of Systems Strong Weak LORAWAN “Helium” Network Solution
- 43. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 43 Stay tuned to “Innovating with Capella” for LORAWAN Helium Based Solution
- 44. Unrestricted | © Siemens 2022 | 2022-02-17 | Tony Komar| Enterprise Architect | Siemens Digital Industries Software | Where today meets tomorrow. Page 44 Thank you to Capella Community Thales Stephane Bonnet Juan Navas Jean-Luc Voirin OBEO Etienne Juliot Stephane LaCrampe Pascal Rogues Jim Daly
- 45. Q & A Thanks for listening! Do you have any questions? Copyright Obeo @2022
- 46. Stay tuned! ▪ Capella Annual Message by Juan Navas (Thales) Don’t miss an opportunity to learn from Capella experts : ▪ March 21-28, 2022 | 2:00 pm - 5:30 pm UTC+1 An online training program in English, through 6 courses of 3.5 hours each, from Monday to the following Monday. March 15th, 2022 Contact [email protected]
Editor's Notes
- #14: this problem so the effort began bye starting to look at applying Capella to the challenges of developing this ventilator first we looked at the problem and I'm going to walk you through some of the diagrams we produced and starting with delivering the ventilation that you have to do and then we're going to focus into the logical and physical architecture diagrams that were produced from this process
- #15: Focus is on Perform Drone Recon
- #16: Focus is on Perform Drone Recon
- #17: Focus is on Perform Drone Recon.
- #33: this problem so the effort began bye starting to look at applying Capella to the challenges of developing this ventilator first we looked at the problem and I'm going to walk you through some of the diagrams we produced and starting with delivering the ventilation that you have to do and then we're going to focus into the logical and physical architecture diagrams that were produced from this process