Integration of Architecture and Maintenance Points of View in an MBSE Context

ABSTRACT In most cases, over 80% of a system's cost is already committed during the preliminary design review (PDR) of the life cycle (Claxton 1993 and NASA 2017). Overruns often occur because requirements of certain stakeholders, such as those related to maintainability, are not involved in the system design process early enough. Consequently, a collaborative effort during the design stage should involve the requirements of key stakeholders and decision‐makers. In this perspective, domain ontologies and the sharing of needs should facilitate a common agreement. Systems engineers are key stakeholders to guarantee the viability of the solution system. The integration of domain ontologies within a model‐based systems engineering framework will enable the interconnection of the heterogeneous data needed to integrate maintenance issues into collaborative system design. Adding maintenance requirements earlier in the design process will help limit additional costs and delays.

Authors

Publication Details

Journal
Insight
Published
2025-12-01
DOI
https://doi.org/10.1002/inst.70021
Primary Topic
Systems Engineering Methodologies and Applications
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Integration of Architecture and Maintenance Points of View in an MBSE Context

G. Boutet, Jean‐Michel Bruel, Nathalie Hernández, Christophe Ducamp et al.
Insight
Systems Engineering Methodologies and Applications
article

Integration of Architecture and Maintenance Points of View in an MBSE Context

G. Boutet, Jean‐Michel Bruel, Nathalie Hernández, Christophe Ducamp, Sophie Ebersold, Nicolas Sarda, Kim Loubat
article en

Abstract

ABSTRACT In most cases, over 80% of a system's cost is already committed during the preliminary design review (PDR) of the life cycle (Claxton 1993 and NASA 2017). Overruns often occur because requirements of certain stakeholders, such as those related to maintainability, are not involved in the system design process early enough. Consequently, a collaborative effort during the design stage should involve the requirements of key stakeholders and decision‐makers. In this perspective, domain ontologies and the sharing of needs should facilitate a common agreement. Systems engineers are key stakeholders to guarantee the viability of the solution system. The integration of domain ontologies within a model‐based systems engineering framework will enable the interconnection of the heterogeneous data needed to integrate maintenance issues into collaborative system design. Adding maintenance requirements earlier in the design process will help limit additional costs and delays.

InsightVol. 28(6)
Openalex Percentile: Top 51%
Systems Engineering Methodologies and Applications
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.