Model-Based Systems Engineering

Model complex requirements with ease

What is model based systems engineering (MBSE)?


Model-based systems engineering is a methodology for using models to design and visualize complex products, to satisfy requitements and assess trade-offs before allocating tasks to the appropriate engineering disciplines, mechanical, electronic, software, etc. MBSE simplifies the design of complex systems by using a common language for multidisciplinary collaborators. MBSE is most often used in safety-critical industries where meeting regulatory compliance is essential.

Linking systems of systems for a competitive advantage

The ramifications of manual, document-based system engineering approaches can be felt across the extended enterprise. Cost, quality, and safety issues stem from difficulties in sharing, maintaining, and re-using inconsistent information scattered between drawings, spreadsheets, and word documents.

Solutions from PTC provide a collaborative, visual approach for better communication, clarity, and maintainability of all product data. MBSE applies modeling, tools, and methods to improve your systems engineering programs and projects, spurring technological innovation and positively impacting costs and productivity. Quality and regulatory compliance is also improved as risks are discovered and mitigated sooner.

overlaycontent

What are the features of MBSE?

While not every product requires MBSE, there are huge benefits to those projects that do. Learn more about why MBSE is a key factor to success for complex products.

While not every product requires MBSE, there are huge benefits to those projects that do. Learn more about why MBSE is a key factor to success for complex products.

Standards-based modeling

Visual modeling with data and diagrams, as well as common systems-level language (SysML), UML for software, OVM for variability, IE for data models, and BPMN and UAF for enterprise architects.

Visual modeling with data and diagrams, as well as common systems-level language (SysML), UML for software, OVM for variability, IE for data models, and BPMN and UAF for enterprise architects.

Multidisciplinary collaboration

Enjoy whole-team transparency with live, multiuser scalable modeling tool and full built-in configuration management.

Enjoy whole-team transparency with live, multiuser scalable modeling tool and full built-in configuration management.

System-level simulation

Visually simulate systems-level model functionality, record the system results for analysis, and co-simulate with third-party simulators and ThingWorx.

Visually simulate systems-level model functionality, record the system results for analysis, and co-simulate with third-party simulators and ThingWorx.

Systems of systems

Asset-based system of systems architecture, with interface management and change impact analysis, parallel working and supply chains, OMG reusable asset specification, and mapping to PLM and IoT designs.

Asset-based system of systems architecture, with interface management and change impact analysis, parallel working and supply chains, OMG reusable asset specification, and mapping to PLM and IoT designs.

System product lines

Graphical, product line modeling drives module inclusion, parameters, and numbers of parts, and defines product line configuration logic and rules.

Graphical, product line modeling drives module inclusion, parameters, and numbers of parts, and defines product line configuration logic and rules.

What are the components of MBSE?

MBSE is a multidisciplinary and collaborative approach to designing and maintaining complex systems, including engineering simulation software and mapping requirements. System architecture modeling both shows and describes a system’s architecture through a digital representation. This is the framework that the rest of the product development will follow. The ‘S’ can also stand for software architecture modeling, which similarly describes and provides a visual representation of the software project. Engineering simulation software allows users to run designs to check the performance of the product or requirements. Mapping the requirements before building and coding helps ensure they are properly defined and aligned.

overlaycontent

What tools are used in MBSE?

MBSE is a combination of a few different concepts in engineering. It unites modeling, systems thinking, and systems engineering. Since MBSE encompasses three different schools, there are several different sets of tools that make up MBSE.

Some of the tools used in MBSE are:

  • Modeling tools
  • Simulation tools
  • Analysis tools
  • Requirements management tools
  • Software development
  • Configuration management
  • Project management

Systems modeling language

There are multiple modeling languages used in MBSE. The primary modeling language is called SysML, which is the systems modeling language. This language is the universal modeling language that supports systems engineering applications and establishes a uniform way of representing models. Other related modeling languages include:

  • UML (unified modeling language for software)
  • UAF (Unified Architecture Framework)
  • OVM (Variability Diagram Orthogonal Variability Modeling)

Depending on what a project entails, there may be different modeling languages used to define the specifications.

MBSE software tools

MBSE software tools include:

  • Systems modeling tool
  • SoS Library
  • System PLE
  • Visual System simulation
  • Trade study analysis
  • Automated system design review
    • Modular design
    • Use case modeling
    • Incremental modeling
    • Functional modeling
    • Visual modeling with data and diagrams

Simulation and analysis tools

MBSE simulation and analysis tools include:

  • Static simulation
  • Dynamic simulation
  • Visual, functional simulation
  • Co-simulation

Requirements management tools

Requirements management tools

  • Requirements and stories management for
    • Business requirements
    • System requirements
    • User requirements
  • Requirements related test management

Cross discipline configuration management with MBSE

null

Learn how PTC’s Digital Thread seamlessly weaves together PLM, Requirements Engineering, Test Management, and MBSE, fostering remarkable collaboration and coordination across disciplines. Start your Digital Thread journey to enable streamlined processes, heightened innovation, and impeccable product quality.

overlaycontent
Industry applications of MBSE

Automotive

MBSE has huge advantages for automotive OEMs and their suppliers. Complex system design capabilities make the integration of software and hardware easier. Enhanced transparency and traceability reduce the time to meet compliance and the ability to collaborate internally and externally with suppliers helps to accelerate the time to development.

Aerospace and defense

MBSE can advance aerospace and defense development by reducing risk in development and helping stakeholders to collaborate in real time to map requirements before beginning to build their products. The A&D industry faces strict regulatory requirements and extremely complex products. Traceability from requirements through the bill of materials can save A&D organizations time and money when building their products.

MBSE case studies

See how your peers are benefiting from a MBSE approach.

alstom-logo-margin.svg
cira-italiano-aerospace-logo-margin.svg
ego-black-logo-margin.svg

Alstom

See how Alstom Transport delivers better products faster using an MBSE approach.

Watch the Video

Centro Italiano Ricerche Aerospaziali

The Centro Italiano Ricerche Aerospaziali achieved design collaboration and communication goals, reduced design costs, and improved quality through PTC Modeler.

Learn More

e.GO

Deployed PTC Modeler as a single source of truth solution for product data and requirements management.

PTC’s MBSE software

PTC Modeler is an award-winning standards-based systems and software modeling solution that empowers architects and engineers to explore design alternatives, simulate design behavior, and communicate product requirements.

Windchill Asset Library enables a system-of-systems approach to MBSE that allows you to design subsystems in separate models and link them together into higher-level system models without duplicating data, so you can design the same way you build systems.

Windchill Process Director is a process definition and deployment solution aimed at providing an efficient approach to the challenge of defining organizational processes and aiding project managers to be more productive. Process quality improvement is supported through easy online maintenance that can be delivered to new and existing projects.

Key product features

Implement techniques that offer a common visual language and structured engineering approach.

Live multi-user database: Enterprise solution enabling systems engineers to collaborate on designs, at the same time, without passing files or requiring check-in/out

Industry-standard system modeling: Intuitive, visual design using the OMG SysML standard design complex system and systems of systems

Asset-based modular systems modeling: Modular systems of systems design approach, using the unique Windchill Asset Library to link models

Visual simulations: Visually simulate and co-simulate system functionality early in the design lifecycle for problem detection

Automated design review: Validate complex system designs early in the design lifecycle through automated design reviews

Variability modeling: Extend model-based systems engineering with system product line modeling and flow down into PLM

Assets management: Asset-based modular system design for systems of systems

Integrated software design: Flow down into software modeling and automated code generation for major programming languages and PTC’s ThingWorx IoT platform

PTC integration: Windchill and third-party integration using extended OSLC

Model-based systems engineering (MBSE) FAQs

What is the difference between systems engineering and MBSE?

Both MBSE and systems engineering focus on simplifying complex engineering artifacts for collaboration across different multidisciplinary teams. For MBSE, those artifacts are consolidated using system design models, making it a visual format. Models are more able to adapt in real time to changes and provide a more dynamic understanding of the system. Systems engineering relies more heavily on documents and drawings. Both are extremely valuable before developing complex systems, but MBSE and the unified SysML language make it easy to work with for many different stakeholders.

Is MBSE agile?

Yes, having visibility of an entire system at once makes it easy to make changes in real time and continue to iterate on designs throughout the modeling process. Since MBSE begins before beginning to build hardware or even software, it gives a high-level overview that allows for changes to be made quickly and efficiently with no cost or loss of work. Additionally, the DSDM (Dynamic System Development Method) agile methodology is specifically supported by PTC Modeler.

How to implement MBSE into your organization

Implementing MBSE in your organization should be strategic. First, you should evaluate your existing processes and whether you have the right people in place. The next step is to examine your current capabilities, tools, and systems engineering skills, and identify where it can add value. Based on this evaluation exercise you can then create a road map, including training and infrastructure. This will help ensure a strategic implementation for MBSE. This assessment can be facilitated by PTC through our tailored walkthroughs. Tailored walkthroughs provided by our solutions consulting experts allow you to try the software firsthand before implementation.

What are some challenges associated with MBSE?

Implementing MBSE requires a skilled workforce to enable users to best use their platforms. This means investing in the right people and processes. Hiring the right teams or acquiring the right talent through resource investment can help with implementation challenges. Change management is another challenge, but once the company culture has adapted to working with MBSE as part of their larger product development process, it will eventually improve time to market and development cycles. MBSE is made for complex systems, so it can take time and resources to establish within a company, but the return on investment is well worth it.

Simplify complex systems design

Please wait while your request is being submitted...

Hi {name}, welcome back.
Not you?

  • Country
  • Afghanistan
  • Albania
  • Algeria
  • American Samoa
  • Andorra
  • Angola
  • Anguilla
  • Antarctica
  • Antigua and Barbuda
  • Argentina
  • Armenia
  • Aruba
  • Australia
  • Austria
  • Azerbaijan
  • Bahamas
  • Bahrain
  • Bangladesh
  • Barbados
  • Belarus
  • Belgium
  • Belize
  • Benin
  • Bermuda
  • Bhutan
  • Bolivia
  • Bosnia and Herzegovina
  • Botswana
  • Bouvet Island
  • Brazil
  • British Indian Ocean Territory
  • Brunei Darussalam
  • Bulgaria
  • Burkina Faso
  • Burundi
  • Cambodia
  • Cameroon
  • Canada
  • Cape Verde
  • Catalonia
  • Cayman Islands
  • Central African Republic
  • Chad
  • Chile
  • China
  • Christmas Island
  • Cocos (Keeling) Islands
  • Colombia
  • Comoros
  • Congo
  • Congo, Democratic Republic
  • Cook Islands
  • Costa Rica
  • Cote d ivoire
  • Croatia
  • Cuba
  • Cyprus
  • Czech Republic
  • Denmark
  • Djibouti
  • Dominica
  • Dominican Republic
  • East Timor
  • Ecuador
  • Egypt
  • El Salvador
  • Equatorial Guinea
  • Eritrea
  • Estonia
  • Ethiopia
  • Falkland Islands (Malvinas)
  • Faroe Islands
  • Fiji
  • Finland
  • France
  • French Guiana
  • French Polynesia
  • French Southern Territories
  • Gabon
  • Gambia
  • Georgia
  • Germany
  • Ghana
  • Gibraltar
  • Greece
  • Greenland
  • Grenada
  • Guadeloupe
  • Guam
  • Guatemala
  • Guinea
  • Guinea-Bissau
  • Guyana
  • Haiti
  • Heard & McDonald Isl
  • Honduras
  • Hong Kong
  • Hungary
  • Iceland
  • India
  • Indonesia
  • Iraq
  • Ireland
  • Israel
  • Italy
  • Jamaica
  • Japan
  • Jordan
  • Kazakhstan
  • Kenya
  • Kiribati
  • Korea, Republic of
  • Kuwait
  • Kyrgyzstan
  • Lao Peoples Dem. Rep.
  • Latvia
  • Lebanon
  • Lesotho
  • Liberia
  • Libyan Arab Jamahiriya
  • Liechtenstein
  • Lithuania
  • Luxembourg
  • Macau
  • Macedonia
  • Madagascar
  • Malawi
  • Malaysia
  • Maldives
  • Mali
  • Malta
  • Marshall Islands
  • Martinique
  • Mauritania
  • Mauritius
  • Mayotte
  • Mexico
  • Micronesia
  • Moldova, Republic of
  • Monaco
  • Mongolia
  • Montenegro
  • Montserrat
  • Morocco
  • Mozambique
  • Myanmar
  • Namibia
  • Nauru
  • Nepal
  • Netherlands
  • Netherlands Antilles
  • New Caledonia
  • New Zealand
  • Nicaragua
  • Niger
  • Nigeria
  • Niue
  • Norfolk Island
  • Northern Mariana Islands
  • Norway
  • Oman
  • Pakistan
  • Palau
  • Panama
  • Papua New Guinea
  • Paraguay
  • Peru
  • Philippines
  • Pitcairn
  • Poland
  • Portugal
  • Puerto Rico
  • Qatar
  • Reunion
  • Romania
  • Russian Federation
  • Rwanda
  • Saint Helena
  • Saint Kitts and Nevis
  • Saint Lucia
  • Saint Pierre and Miquelon
  • Samoa
  • San Marino
  • Sao Tome and Principe
  • Saudi Arabia
  • Senegal
  • Serbia
  • Seychelles
  • Sierra Leone
  • Singapore
  • Slovakia
  • Slovenia
  • Solomon Islands
  • Somalia
  • South Africa
  • S.Georgia and S.Sandwich Isles
  • Spain
  • Sri Lanka
  • St. Vincent and Grenadines
  • Sudan
  • Svalbard and Jan Mayen Islands
  • Swaziland
  • Sweden
  • Switzerland
  • Taiwan
  • Tajikistan
  • Tanzania United Republic of
  • Thailand
  • Togo
  • Tokelau
  • Tonga
  • Trinidad and Tobago
  • Tunisia
  • Turkey
  • Turkmenistan
  • Turks and Caicos Islands
  • Tuvalu
  • Uganda
  • Ukraine
  • United Arab Emirates
  • United Kingdom
  • Uruguay
  • US Minor Outlying Islands
  • USA
  • Uzbekistan
  • Vanuatu
  • Vatican City State (Holy See)
  • Venezuela
  • Vietnam
  • Virgin Islands (British)
  • Virgin Islands (U.S.)
  • Wallis and Futuna Islands
  • Western Sahara
  • Yemen
  • Zambia
  • Zimbabwe

Click the button below to continue.

Get in Touch