You’ve convinced the powers-that-be that your company should use Model-based Systems Engineering. You’ve done an extensive trade study and picked the tool that you want to use. You’ve completed the budget and IT hurdles to put the tool into the hands of all your engineers. Now what? How does this new tool fit into your product development process? How do you capture your project’s data in the tool? Which diagrams should you use? How do you create your regulatory submission documentation?
The out-of-the-box model database schema included in most tools is overwhelming, has a steep learning curve, and caused our engineers to spend more time cursing at the computer than ensuring the success of their projects. We knew there had to be a better way, so we completely abandoned the standard frameworks and built our own. What to include in our model, how those items are connected, and what documents we must export were carefully debated, tested, and refined.
We have successfully utilized MBSE with our custom schema on numerous projects across several industries. MBSE has been so well-received that our project engineers and customers are demanding direct access to our models. They watched our systems engineers navigate through the model and quickly answer important questions like ‘What is the impact of changing that requirement?’ They are no longer interested in reviewing the documents that we’ve exported from the MBSE tool, they want to go straight to the source. Since one of the professed advantages of MBSE is to increase collaboration, this is a major victory.
The upcoming webinar Getting Started with MBSE in Product Development on February 15th will walk you through how we have incorporated MBSE into the product development process. It will detail exactly how to build your model and what to focus on in each phase of a project.
This topic was originally presented at the INCOSE International Symposium in Edinburgh in July 2016. The accompanying paper is a detailed and practical guide to setting up your own MBSE tool.