- Jul 16, 2024
What is MBSE?
- Joseph Shepherd
- Research, Digital-Engineering
- 0 comments
MBSE is the formalized application of modeling to support systems requirements, design, analysis, verification, and validation activities. It spans the entire system lifecycle, from conceptual design to decommissioning. Unlike DBSE, which relies heavily on documents, MBSE leverages models as a single source of truth.
The Problem
Traditional systems engineering (SE) practices are error prone, time consuming, and expensive. They rely heavily on documents and subject matter expertise (SME), which is difficult for companies to scale and apply with any sort of consistency. Below are some of the challenges with traditional systems engineering practices.
Complexity: Large engineering projects are often very complex with tens of thousands, or more, of requirements and dependencies. These programs become very difficult to represent and understand using traditional SE methods. This leads to errors and cost overruns.
Inaccuracies: Errors and design flaws can cause significant delays and costs if they aren’t caught early. Traditionally these flaws aren’t caught until late in the design and manufacturing process and often make their way into the final product.
-
Costs: Expertise and time are costly entities. The reliance on SMEs means traditional SE methods take time and rely heavily on scarce resources. All this means higher costs and increased time to market.
The Gap in Practice
Traditional SE processes lack the level of transparency and discoverability necessary to empower an effective and consistent systems design experience. Existing processes are often document based and very manual. This results in duplicated effort, inconsistencies due to SME interpretation and application, and places significant strain on resources.
Origin Story
The term “Model-Based Systems Engineering” was first publicly used by A. Wayne Wymore in his book of the same name. During the early years of the Systems Modeling Language (SysML) project (2003-2005), the term was commonly used to distinguish SysML from its parent language, UML v2, which was software-centric and associated with Model-Driven Development (MDD). The standardization of SysML in 2006 led to widespread adoption of MBSE processes emphasizing SysML.
In 2007, INCOSE introduced the “MBSE 2020 Vision,” which broadened the scope beyond SysML and supported other modeling language standards. The vision aimed to replace document-centric approaches with fully integrated MBSE practices in systems engineering processes. Since 2014, MBSE has also encompassed Modeling and Simulation, bridging the gap between system model specifications and related software simulations.
Why Now?
The convergence of cloud computing and AI, coupled with the increased need to response to global threats with new and advanced assets and innovations, hesitates the transition from costly, manual DBSE process to a more streamlined and effective MBSE approach. While the increase in global threats is specific to the defense industry, any vendors who designs and manufactures products are under increased pressure to bring new innovations to market faster and cheaper than ever before. Likewise, the decision to shift to MBSE is being forced on defense vendors. Most Requests for Proposals (RFPs) now require an MBSE based response. These growing complexities along with the limitations of traditional, document-based approaches means vendors who do not adapt will continue to struggle to address these challenges. Thise who do adapt will see benefits such as those listed below.
Reduced Errors and Inconsistencies: MBSE minimizes the risk of errors and inconsistencies common in document-centric systems. Models provide traceability, ensuring stakeholders work with consistent information.
Improved Communication and Collaboration: MBSE fosters better communication among stakeholders, leading to faster, more accurate decision-making.
Efficiency: By streamlining tasks like documentation and validation, MBSE frees engineers to focus on complex tasks like system design and analysis.
Challenges in Implementing MBSE
Many vendors will tell you the path forward is long and challenging. That doesn’t mean it’s not worth the journey. There are some common pitfalls to avoid however, and smart vendors can make the transition easier by addressing these challenges up front.
Cultural Shift: Transitioning from DBSE to MBSE requires a mindset shift. Stakeholders must embrace modeling as a primary means of collaboration and communication. Vendors should not take this lightly.
Tooling and Training: Organizations need suitable modeling tools and training programs to empower their teams. Likewise, Integrating MBSE into existing workflows can be challenging. It requires aligning processes, data, and tools. Great experience leads to consistent adoption.
Data Access: The greatest challenge that faces defense vendors is access to the right data at the right time.
Collaborating Across Boundaries: The ability to conduct collaborative design across internal boundaries and with external vendors is a huge leap forward in capability but comes with significant security challenges. Smart vendors are investing in secure, compartmentalized collaboration capabilities that extend their reach while protecting their IP.
Proven Paths Forward
While there are many possible missteps and landmines along the way there are also proven strategies that can help safely navigate the journey. Certain patterns exist that, when properly applied, can make the path a safer and simpler one to follow. Some of these are listed below.
Start Incrementally: Begin with pilot projects or specific subsystems. Gradually expand MBSE adoption across the organization. Just get started. Movement is more important than being comprehensive at this stage.
Training and Education: Invest in training programs to upskill engineers and stakeholders on MBSE concepts and tools. This is a whole new way of working so don’t leave training to chance.
Standardize Modeling Languages: Choose a standard modeling language (e.g., SysML) to ensure consistency and interoperability. It’s important that everyone speaks the same language in a precise manner.
Collaborate Across Disciplines: Involve cross-functional teams (e.g., systems engineers, software developers, domain experts) to create comprehensive models. Pull in your partners to create explosive scale.
Measure Success: Establish metrics to track improvements in cost, schedule, and defect reduction.
Choose a Path: It’s important that vendors are intentional about their path forward. Some may require vendors to focus on operational efficiencies first while others may be more customer centric or even require the creation of entirely new business units. The important thing is to make incremental progress versus trying to boil the ocean.
Conclusion
Many vendors find themselves exploring MBSE to satisfy growing customer demand while maintaining their strategic position in the market. This new way of working is a significant leap forward for vendors who have multiple decades or more rooted in traditional systems engineering practices. However, by being intentional in their planning, smart vendors can chart a sensible journey from their current state to a desired future state that benefits from a modern model-based systems engineering approach.
References: