MBD Ready Check

Non-semantic annotations pose a significant challenge to the effective implementation of Model-Based Definition (MBD) because they are not machine-readable, preventing the reliable reuse of Product Manufacturing Information (PMI) in downstream processes such as manufacturing, inspection, and quality.

To address this challenge, MBDVidia's 3D workflow includes the MBD Ready Check, a semantic validation capability designed to evaluate PMI quality and ensure annotations are machine-readable. The tool identifies potential semantic issues, highlights areas that may impact downstream consumption, and helps users improve the overall quality of their MBD data.

The MBD Ready Check evaluates PMI for semantic accuracy and provides users with the option to automatically fix issues (where available), manually resolve them, or ignore non-critical findings. This ensures that MBD models are not only visually correct, but also semantically rich and ready for reliable downstream use.

Where to find MBD Ready Check

The MBD Ready Check button is located in the Tools tab. Selecting it will open a separate panel.

Opening the MBD Ready Check panel displays a toolbar with the following five functions:

MBD Ready Check categories

The MBD Ready Check tree categorizes all encountered problems, displaying the number of remaining and total issues in brackets.

Auxiliary Face

Annotations linked to auxiliary faces are problematic, as these faces do not contribute to the formation of solids. Establishing such connections is considered incorrect. This can be fixed by reconnecting the annotation to solid model geometry.

Auxiliary Edge

Annotations are linked to auxiliary edges, which do not contribute to forming solids. Associating annotations with these edges is incorrect.

Auxiliary Vertex

Annotations pointing to auxiliary vertexes. Auxiliary vertexes do not participate in forming solids. Linking annotations with them is incorrect.

Model Edge

An annotation references a model edge, which is part of the solid model geometry, unlike auxiliary edges. However, model edges are generally not suitable references for annotations, because edges are derived, unstable, and ambiguous while referencing surfaces is stable, measurable, and standards compliant. The only exception to this rule is when a constructed feature type is attached to the model edge.

Missing Feature

Annotations reference fewer features than they should (e.g., one instead of two). This applies to tolerances related to features such as “distance between,” “distance from,” “angle between,” and “angle from,” which need to be connected to two features.

Second, when directional zone limits are specified on an annotation (e.g., “A<->B”), MBD Ready Check will evaluate the feature in relation to the zone limit markers (e.g., “A” and “B”) to confirm that all areas between “A” and “B” are referenced.

Incorrect Feature

Annotations that are physically connected to a feature but incorrect in meaning. For instance, the flatness of the inner hole diameter feature is not a valid concept.

If there are additional references that do not form feature pairs with any other feature’s references, the issue will be flagged under this category. These extra features will be highlighted as problematic, and an auto‑fix option is available to remove any features that do not form valid pairs with others.

Incomplete Feature

The annotation is attached to an incomplete feature, depending on the type of annotation.

When all-around or all-over is specified by the tolerance, MBD Ready Check will examine the feature to ensure that its coverage on the geometry aligns with the all-around/all-over flag.

Isolated Annotation

Annotations that are unrelated or connected to any specific features.

Incorrect Orientation

Annotations attached to an orientation, location, or runout tolerance that conflict with the model geometry.

For instance, the parallelism of the feature surface relative to datum feature “C” cannot be applied if they are not parallel.

Incorrect Datum

If multiple datums are created that reference the same surface, or if a datum symbol is incorrectly applied, it can lead to significant confusion and errors in downstream processes. Such issues are flagged in the incorrect datum category.

• The datum name is repeated multiple times.

• Multiple datums have the same references.

• Datum symbol is incorrect.

Incorrect Nominal

The displayed value on the model does not align with the true model value, often due to rounding.

Incorrect Feature Counter

Annotations without a feature multiplier are linked to several features, while annotations with a feature multiplier (e.g., "6X") may not match the actual number of attached features. For instance, in the image below, the feature multiplier is six but is connected to four holes (the red ones; the green holes are proposed as the solution to this issue).

Additional issue that is flagged in this category is when annotation has a counter defined as text around, but the counter was not semantically recognized. This means recognized counter does not match the text. This issue can mostly be present for legacy data such as older QIF files or files that were manually edited. For this issue auto-fix is available which will sync the counter specified as text around with its semantic recognition.

Non-Semantic Annotation

Annotations created as text notes, rather than specific semantic annotations, may not be usable in downstream applications until they are properly recognized and converted into their semantic representations.

Incorrect Grouping

Annotations that are grouped incorrectly. For instance, if a length is placed in the same group as a geometric tolerance with a diameter as the zone shape symbol, or when PMIs in the group share the same references.

Not in a Saved View

Annotations that are not assigned to any saved view can create confusion and pose challenges. Although these annotations exist on the model, users who rely solely on Saved Views may remain unaware of their presence, leading to potential misunderstandings or oversight.

Standard Violation

A standard violation can occur due to various factors. For instance:

• The diameter is placed in a group of geometrical tolerances that does not have the diameter symbol.
  

• A datum is included into the same group as a geometric tolerance that references that datum in its Datum Reference Frame.

  

• Continuous feature symbol is missing.

  

• The zone boundaries referenced in the annotation are not defined on the model.

  

Decimal Places

This category flags issues where the number of decimal places in the annotation is not correct and is not according to standard.

Bad Practice

This category pertains to instances where annotations are generated in a manner that does not align with established standards.

At the moment, Bad Practice covers only overwritten dimensions, but the list is set to grow in the future. As new examples of bad practices are identified, their descriptions will be included in this list.

Ignored

Other PMI that don`t meet MBD Ready Check criteria will be put in this category. Issues from other categories can be ignored as well.

How to fix it?

Each reported issue comes with one of the following options for applying a fix:

Automatic Repair

A suggested automatic fix is available. You can auto fix just specific annotation that was flagged if it has an obvious fix. In addition, if we want to auto fix all issues that were flagged, right clicking the top of the category tree and select Automatic Repair will auto fix them.

Choice

For some reported issues there are multiple suggested fixes that are displayed as tree nodes under the problem. MBDReady check ranks these fixes based on the likelihood of each being the intended design. When you select a node representing a solution, the proposed fix will be highlighted in green on the model.

Manual Repair

You can always choose to fix the annotation manually. In some situations where no obvious design intent can be automatically found, this will be your only option. By selecting Manual Repair, the Reconnect panel will open, letting you reconnect the annotation to the relevant features.

Annotations need to be linked to Features, not just geometry. Before reaching this step, you might need to manually create a feature representing the geometry you want to control with the tolerance. This is usually done automatically during the Reconnect process but can also be handled manually in the Features section of the Tools ribbon.

Ignore Problem

The Ignore Problem option dismisses the specific problem reported so it is not flagged in that specific category, but the same annotation may still be flagged under other relevant categories.

Ignore Annotation and Unignore

The Ignore Annotation option excludes the selected annotation from the MBD Ready Check process, meaning it will not be evaluated through any category. This allows you to bypass issues or warnings tied to that annotation while keeping it present in the model. If an annotation has been moved to Ignored category by the user, you can still return it to its original category. Simply select the annotation and use the Unignore command to move it back.

Results - MBD Ready Score

To get more details about the MBD Ready Score, simply open the Information Panel after activating MBD Ready Check. You'll find additional data there that can be copied as plain text.

FAQ