Fields marked with a * are required

SIGN UP FOR OUR NEWSLETTER

What’s the Difference between MBSE, MBD, MBE and Model Based Development?

References Cited

Model Based Definition (MBD), Model Based Development, Model Based Enterprise (MBE), Model Based System Engineering (MBSE), Mechanical Computer Aided Design (MCAD), Mechanical Computer Aided Engineering (MCAE)

Studies Cited

The ROI of MBD Study

Now that is a whole lot of acronyms. Why talk about all of them together? Well, there seems to a lot of confusion about these kinds of initiatives. You see all of these acronyms have something in common, the phrase Model Based are used to start each of them. So people expect them to be closely interrelated. But really isn’t a definitive source that answers this question. So here, in this post, I’ll share what I’ve learned from a few recent research projects. Furthermore, I’ve created new Reference entries for your use. So with all that out of the way, here’s the high level overview of these initiatives.

Definitions of MBSE, MBD, MBE and Model Based Development

  • Model Based Definition (MBD) is a mechanical engineering initiative where a 3D model with Product Manufacturing Information (PMI) augments or replaces a 2D engineering drawing as design documentationModel Based Enterprise (MBE) is a company wide initiative to augment 3D models with additional information to create new documentation deliverables beyond engineering.
  • Model Based System Engineering (MBSE) is a system engineering initiative to create a digital model of a system that is used by all engineering disciplines and other functional organizations within a company.
  • Model Based Development is a embedded software initiative where a two-sided model is used to verify control requirements and that the code runs on target electronic hardware.

What are the differences?

So, as you can see, these three major sets of initiatives are each relevant to a different engineering domain: mechanical, system and embedded systems. But the more fundamental difference runs much deeper than that. One focuses on documentation that is released by engineering (MBD and MBE). Another provides a single unambiguous definition of the design for engineering coordination (MBSE). The last is used for quick prototyping and test (Model Based Development).

What are the similarities?

That, my friends, was the focus of a briefing I recently led at The Congress on the Future of Engineering Software (COFES) 2016. Unfortunately, most attended that briefing to learn what these initiatives were, not to help in a discussion to answer our question. That’s OK. As I said before, there isn’t a whole lot out there offering definitions or guidance. So what’s the quick answer? Today, these initiatives are related in any way, shape or form… other than the fact that they each use the phrase Model Based in them.

Is there an intersection in the future?

However, that doesn’t mean there isn’t the potential for integration. And actually, I hold out some great hope for that. So follow me along here.

MBSE uses a flowchart model to unambiguously define the components of a system, whether they be hardware or software, and their related requirements and functions. Model Based Development uses a flowchart model to replicate the control side (embedded software) and the plant (the physical parts of the product) to test their interactions. So there is a natural intersection here, even though one commonly uses SysML or Modelica languages and the other uses UML languages. The point here is that their purpose is similar in some regards.

MBD and MBE uses a 3D model of mechanical hardware for documentation, so those initiatives may not be directed related here. However, those blocks in the MBSE or Model Based Development model can be a mechanical hardware component. Now, in the base of MBSE and Model Based Development, the behavior of that mechanical hardware component can be driven by equations and formulas. But, conceivably, that could replaced with a full multi-physics simulation of a complete 3D model. Why not do that today? Latency. Model Based Development, which is used for embedded software development, requires real time reaction of the plant (the representation mimicking the physical aspects of the product) to prototype and test the code. With today’s FEA and dynamics methods, that really isn’t possible.

How far off?

So at some point in the future, either close or far distant, there can be an intersection. But it will take a lot of advancement in technologies to make it work.

The other barrier, and far more serious, is the slow rate of adoption of these types of initiatives. I’m hearing that MBD and MBE are picking up, which I’ll be researching in an upcoming study. But MBSE is still early in terms of adopters. Model Based Development seems to be a bit more advanced in adoption.

Sound Off

Alright folks. Those are my thoughts. Interested in getting your take. Sound off in the discussion!

Chad Jackson is an Industry Analyst at Lifecycle Insights and publisher of the engineering-matters blog. With more than 15 years of industry experience, Chad covers career, managerial and technology topics in engineering. For more details, visit his profile.

Like this post?

Sign up now to get more like it

Fields marked with a * are required

SIGN UP FOR OUR NEWSLETTER