Integrating maintenance requirements into system design improves viability and reduces costs in life cycle processes.
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.
No takes yet. Share an insight, caveat, or question.
Loubat et al. (2025) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: