Integrating Model-Based Systems Engineering and Value-Based Design with an NEA Scout Small Satellite Example

Author(s):  
Garima Bhatia ◽  
Bryan Mesmer
2017 ◽  
Vol 26 (1) ◽  
pp. 77-92 ◽  
Author(s):  
Caroline Lange ◽  
Jan Thimo Grundmann ◽  
Michael Kretzenbacher ◽  
Philipp Martin Fischer

Despite popular belief, space missions are not always one-of-a-kind, but are frequently benefiting from explicit or implicit reuse of different types. The Venus Express mission is one example of cost savings by reusing existing hardware in a new mission context. Other examples are based on the platform approach, popular, for example, in geostationary telecommunication satellites, which benefits from a pre-planned reuse and its application to a family of missions with commonality. While the latter is handled more strategically, promising more gain in its execution, the Venus Express example is more of an ad hoc nature. Given the increasing importance of design reuse, the practical question to be answered in this article is how to promote it using effective engineering methods and processes. Model-based systems engineering often advertises itself as especially beneficial to reuse projects and we provide a systematic review of the respective capabilities in this article. Furthermore, we describe two reuse application examples: an asteroid nanolander based on the Mobile Asteroid Surface Scout lander currently flying onboard Hayabusa2 and a Small Satellite Platform for Earth science missions. With Mobile Asteroid Surface Scout’s heritage generating strong interest for future small body missions, this creates a case for what we call ad hoc reuse. Conversely, the Small Satellite Technology Platform, which is currently in its definition phase, can be classified as systematic reuse case with the aim of developing a commonality-based small satellite family, suitable for a set of rapidly recurring missions in low Earth orbit. Our study of the Mobile Asteroid Surface Scout-2 reuse case has provided insights into reuse requirements, which are mapped to typical model-based systems engineering features that create value beyond those offered by classical approaches. The article identifies key areas where model-based systems engineering provides benefits in reuse cases: requirements reuse, system context analysis as well as interface compatibility checking. It further outlines an overall approach regarding tools and development processes.


Konstruktion ◽  
2020 ◽  
Vol 72 (11-12) ◽  
pp. 76-83
Author(s):  
Jens Pottebaum ◽  
Iris Gräßler

Inhalt Unscharfe Anforderungen, verschiedene Lösungs-alternativen oder eingeschränkt gültige Simulationsmodelle sind Beispiele für inhärente Unsicherheit in der Produktentwicklung. Im vorliegenden Beitrag wird ein modellbasierter Ansatz vorgestellt, der das industriell etablierte Denken in Sicherheitsfaktoren um qualitative Aspekte ergänzt. Modelle der Informationsqualität helfen, die Unsicherheit von Ent- wicklungsartefakten beschreibend zu charakterisieren. Mittels semantischer Technologien wird Unsicherheit so wirklich handhabbar – nicht im Sinne einer Berechnung, sondern im Sinne einer qualitativen Interpretation. Dadurch entsteht wertvolles Wissen für die iterative Anforderungsanalyse, die Bewertung alternativer System-Architekturen oder für die Rekonfiguration von Simulationen.


2021 ◽  
Vol 12 (3) ◽  
pp. 97
Author(s):  
Christian Raulf ◽  
Moritz Proff ◽  
Tobias Huth ◽  
Thomas Vietor

Today, vehicle development is already in a process of substantial transformation. Mobility trends can be derived from global megatrends and have a significant influence on the requirements of the developed vehicles. The sociological, technological, economic, ecological, and political developments can be determined by using the scenario technique. The results are recorded in the form of differently shaped scenarios; however, they are mainly document-based. In order to ensure a holistic approach in the sense of model-based systems engineering and to be able to trace the interrelationships of the fast-changing trends and requirements, it is necessary to implement future scenarios in the system model. For this purpose, a method is proposed that enables the consideration of future scenarios in model-based vehicle development. The procedure of the method is presented, and the location of the future scenarios within the system architectures is named. The method is applied and the resulting system views are derived based on the application example of an autonomous people mover. With the help of the described method, it is possible to show the effects of a change of scenario (e.g., best-case and worst-case) and the connections with the highest level of requirements: stakeholder needs.


ATZ worldwide ◽  
2021 ◽  
Vol 123 (7-8) ◽  
pp. 66-71
Author(s):  
Thorsten Weyer ◽  
Marcel Goger ◽  
Walter Koch ◽  
Birgit Kremer

2021 ◽  
Vol 1 ◽  
pp. 3369-3378
Author(s):  
Stephan Husung ◽  
Christian Weber ◽  
Atif Mahboob ◽  
Sven Kleiner

AbstractModel-Based Systems Engineering (MBSE) is an efficient approach to support product development in order to meet today's challenges. The MBSE approach includes methods and, above all, modelling approaches of the technical system with the aim of continuous use in development. The objective of this paper is to use the potential of the MBSE models and to show the added value of such models on the system level when used as a single source. With this objective, this paper presents a three-step approach to systematically identify and apply meaningful modelling approaches within MBSE, based on the needs during the development process. Furthermore, an FMEA example is included in this paper to elaborate the use of MBSE in the system failure analysis.


Sign in / Sign up

Export Citation Format

Share Document