As noted in the MBE Overview section of this website, a Model Based Enterprise (MBE) is a digital tapestry which has been optimized around a core set of annotated product models.  A more formal definition is:  MBE is an integrated and collaborative environment, founded on 3D product definition shared across the enterprise, enabling rapid, seamless, and affordable deployment of products from concept to disposal.

The 3D product definition or set of annotated models referred to here is the Model Based Definition (MBD).  Again a more formal definition is:

The Model Based Definition (MBD) is created at the beginning of the lifecycle then reused throughout the enterprise, thus creating the Model Based Enterprise (MBE).

MBE 3D Drawing

These are but two definitions that are being used to define a relatively simple concept that can have a very complex implementation.  This is because MBE or the Digital Tapestry covers data produced by many different disciplines and users.  As such, each segment can be broken down even further to address these other areas.  Figure 1 depicts one way to break down the core concepts of MBE.

Each concept is depicted as a circle in this Venn diagram.  As the circles overlap, another concept is depicted.  The three outer concepts, Acquisition, Operations and Maintenance depict the major points in a product lifecycle. 

Moving in, the inner circle describes the foundational concepts of MBE itself:

  • Data: Refers to the source data itsself.  It can also be thought of as one of the digital threads.
  • Management:  Refers to the need to organize the massive amounts of data contained within a digital tapestry.  This can be applied to the overall data set or down to the organizational schema used in the annotated models making up the Model Based Definition (MBD).
  • Secure & Controlled:  Refers to the ability to control access and secure the data once it has been managed.

The overlaps between these circles are the most important part of the Model Based Enterprise.  By applying the other concepts successfully, Data Reuse is enabled.  This means that access can be provided for the user to the data they need to do their job when they need it without having to recreate it.  And finally, at the core of MBE is a Single Digital Master.  This means there is only one source for defining a product.  There may be many derivatives that other applications create for either their use or to present relevant information to the user.  These are typically created automatically and must be programmatically verified back to the original so there is little or no human labor needed.

As one continues to look at the many aspects of MBE, there are three other tenants that need further discussion.  See the links below for more information on these:

/body>