Implementing MBSE – An Enterprise Approach to an Enterprise Problem

Abstract

Model Based Systems Engineering (MBSE) is now widely accepted throughout the industry, from commercial to aerospace and defense. However, while we understand and accept the principles of MBSE, successful adoption and implementation is still a challenge within the industry. The migration from document‐based systems engineering processes to MBSE requires more than purchasing tools and a one‐week course on Systems Modeling Language (SysML). MBSE does not change the practice of Systems Engineering as defined in the INCOSE SE Handbook or ISO/IEEE 15288, but it does affect the way in which systems engineering processes are implemented and supported within and across organizations. Organizations adopting MBSE must address issues such as new skill and competency requirements for systems engineers, model and data management over the lifecycle of the system, and integration with other engineering tools and processes, among others. It is not a tool problem or a modeler problem. It is an enterprise problem and requires an enterprise approach. The approach must be defined and guided by an enterprise architecture, which is broader than just the engineering tools and their interfaces. It includes the enterprise strategic vision, capabilities, operational concepts, organizations, and material solutions required to achieve MBSE adoption, how they relate to one another, and their evolution over time. This paper provides a broad overview of the fundamentals of MBSE adoption and the broader effort of digital engineering transformation, presenting the digital engineering environment as a system‐of‐systems. It presents the use of enterprise architecture as a roadmap for MBSE adoption within the industry.

Towards Developing Metrics to Evaluate Digital Engineering

“…Digital engineering (DE) is an enterprise approach for incorporating data‐driven infrastructure, methods and tools, innovation, and workforce transformation centered on an authoritative source of truth (ASOT) for engineering data 6 . DE aims to integrate design data across the entire system life cycle as well as “bridge the business processes across all functional disciplines.” 7 This requires a high level of intra‐disciplinary collaboration and integration across an engineering business. DE “moves the engineering discipline towards an integrated model‐based approach.” 6 Model‐based systems engineering (MBSE) is the part of this larger DE transformation that enables this integration through the ASOT.…”

“…business processes across all functional disciplines." 7 This requires a high level of intra-disciplinary collaboration and integration across an engineering business. DE "moves the engineering discipline towards an integrated model-based approach."…”

MBSE adoption experiences in organizations: Lessons learned

“…15,33 Infrastructure Infrastructures for tools and the ASoT should be planned and established early. 1,32 How data will be stored, accessed, and exchanged should be thought out as well. 28,53 Leadership/management support "creates a strong MBSE infrastructure."…”

Formal Modeling and Verification of the Functionality of Electronic Urban Railway Control Systems Through a Case Study

“…Engineers are generally familiar with the tools available for modeling, simulation, or analysis in their respective fields, so when they encounter a problem, they immediately examine it using modeling. MBSE is a formalized application of modeling to support the life-cycle activities during the development [24], which intends to bring together the model-centric approaches of various engineering disciplines (e.g., electrical, software). MDD is a philosophy of software development that focuses on high-level models [25].…”