Model-based Systems Engineering
Complex systems have always existed, and manufacturing has always tested even the brightest engineers. But in recent decades there has been a profound increase in the level of complexity with which most companies must cope and also a rapid increase in the rate at which complexity is accelerating. Never before have manufacturers been so challenged to design, build and deliver new products on time, on cost and that meet customers’ performance expectations.
Meeting these challenges requires a profoundly different Model-based approach that is digitally threaded from MBSE to MBD to SPDM and all into PLM as your Digital Engineering Hub.
Would you like to review an end-to-end Master Data Model for the Next Generation of MBx? Contact Us
The Model-based Systems Engineering Environment
Requirements Driven Design > Multi-Domain Systems Engineering > Continuous Verification & Validation
The MBSE Value Proposition – Executive Summary
Implementing MBSE will result in increased efficiency and cost savings in the systems engineering process. By using models to represent the system, engineers can quickly and easily evaluate different design options and scenarios. This enables them to identify potential issues and make design changes earlier in the process, which can result in cost savings by avoiding rework and late-stage design changes
MBSE can also help to improve system quality and performance. By using models to represent the system, engineers can perform simulations and analyses to evaluate the performance of the system under different conditions. This helps to identify potential issues and optimize the design for improved performance and reliability while reducing Post Launch Quality Programs, and associated Warranty Costs
Requirements management is a critical component of the systems engineering process. By using models to represent the system, requirements can be linked directly to the system components and subsystems. This increases requirements/design yield and reuse while better enabling design verification resulting in a reduction of late-stage design changes and poor time to market performances.
MBSE can also help to enhance system understanding and documentation. With MBSE, the system is represented in a visual, intuitive way that can be easily understood by all stakeholders. This helps to improve the documentation of the system, making it easier to understand and maintain over time
Coupled with our “Next Generation” PLM initiative and the implementation of an end-to-end digital thread, MBSE will enable the implementation of Lean Pull workflows that will reduce the administrative overhead associated with Product Data creation, administration, packaging & distribution
Implementing MBSE will improve risk management in the systems engineering process. By using models to represent the system, engineers can more effectively and efficiently perform simulations and analyses to identify potential risks and evaluate different risk mitigation strategies. This helps to minimize the potential impact of risks on the system development process.
MBSE delivers a Model-based fully integrated environment to better enable the process of Product Integration (where engineers spend most of there design and verification time). This end to-end digitally threaded environment will reduce late-stage design changes, increase design productivity thereby enabling the implementation of more product features per program while reducing time to market and increasing Top Line Margin
Implementing MBSE for a Measurable ROI
Some initial words of wisdom
It is critical to view MBSE as a major component of a comprehensive end-to-end Digitally Threaded Engineering Environment and while a phased implementation approach can be taken, you can only do so effectively and efficiently with an up-front understanding of some critical data threads and integration points:
- Stakeholder Needs constructs/data model and their relationship to your Technical Requirements constructs and data model
- Technical Requirements data model and its relationship to your Trade Study suite and data requirements
- Technical Requirements constructs/data model and their relationship to SysML constructs (Logical, Functional, Physical) and data model
- SysML data model and its relationship to your Verification and Validation data requirements (managing Component Characteristics)
- SysML data model and how you will move Component Characteristics into CAD e.g., CAD Skeletons
- SysML Physical Block Library and its relationship to Part Objects and the Part Classification schema in PLM
- How you will digitally associate SysML Physical Blocks to Part Objects in PLM
- How you might construct Physical Models to enable automated production of EBoM Data
- How you will digitally associate Stakeholder Needs, Technical Requirements, System Models to their relative Programs/Projects within PLM
- How you will manage verification and validation data within an SPDM and digitally associate it with relative Programs/Projects within PLM
- How you will extend your Lifecycle States and Controls within PLM to enable Lifecycle Management/Revision Control of Stakeholder Needs, Technical Requirements, System Models through the PLM ECO functionality
- Et Cetera
Assuring you have a good understanding regarding how the whole system will eventually connect via Data Threading and Application Integrations will enable you to take a Phased Implementation approach. This will reduce the volume of reconfigurations required across the landscape to align and integrate it as you move through each phase. It will additionally reduce the volume of manually triggered / manual data transformations required as you continue to extend and integrate the end-to-end landscape
