Introduction: The Missing Link in the Digital Thread

Model‑Based Definition (MBD) has become the de‑facto method for product definition in aerospace, defense, automotive, and industrial sectors. 3‑D annotated models now replace 2‑D drawings as the authoritative source for representing and communicating the product’s nominal shape and it acceptable deviation from nominal via tolerances and specifications.

Problem: While product design data are fully digital, verification workflows remain fragmented. Tolerances are re‑interpreted across disparate systems, balloon numbers are renumbered during revisions, and requirements lose traceability during product change cycles. Consequently, the digital thread often breaks at the boundary between design and inspection.

Current question: How can enterprise stakeholders ensure that a verification requirement remains uniquely identifiable and traceable from design intent through manufacturing, and into  inspection execution?

The Model-Based Characteristics (MBC) Standard, developed by the Digital Metrology Standards Consortium (DMSC), establishes a standardized approach to the persistent identification and association of verification requirements, enabling consistent and uniquely identifiable linkage across the product definition and the digital thread.

The Core Problem: Identification and Persistence

A fundamental requirement for a digital thread is the ability to uniquely and persistently identify verification requirements across the product lifecycle.

A tolerance defined in a model must:

• Be traceable to its originating requirement
• Be identifiable during inspection planning
• Appear consistently in nonconformance reporting
• Persist across revisions and system migrations
• Remain machine-readable for automation

Historically, organizations have addressed this need using internal conventions such as balloon numbering, spreadsheets, product lifecycle management (PLM) attributes, or inspection software mappings. While effective within a local context, these approaches often lack consistency and scalability across enterprise and supply chain environments.

The MBC Standard establishes a standardized identification framework to address this gap.

What the MBC Standard Defines

The Model-Based Characteristics (MBC) Standard defines a structured approach for identifying and augmenting Product Characteristics (PCs), which represent verification requirements applied to a product or its features.

A Product Characteristic may represent:

• A dimensional tolerance like GD&T
• A surface specification
• A requirement expressed in a local or general note
• A requirement defined in a supplemental support specification

Each Product Characteristic includes a dual-identifier scheme:

• A human-readable tag (e.g., PC007) an easy reference for engineers and documentation
• A machine-readable universally unique identifier (UUID) (e.g., 550e8400‑e29b‑41d4‑a716‑446655440000) an immutable key for software agents, ensuring cross‑system persistence

This dual-identifier structure provides both usability and persistence, enabling consistent identification across tools, revisions, and organizations.  The PC-Tag is locally unique within the specified product definition whereas the PC-UUID is generated once and never changes, even when the MBD model is revised or exported to another format.

In practice, each verification requirement is associated with a persistent identifier, enabling reliable traceability throughout the product lifecycle.

Structured Augmentations: Making Characteristics Actionable

In addition to identification, the MBC Standard defines structured augmentations that formalize commonly used enterprise practices.

Criticality Classification (CC)
Criticality classifications allow organizations to designate characteristics that are safety-critical, mission-critical, or otherwise significant. MBC standardizes how this information is associated with a Product Characteristic, ensuring that criticality is explicitly defined and digitally connected.

Product Requirement Association (PRA)
Product Requirement Associations create an explicit link between a Product Characteristic and its originating product requirement. This supports traceability during audits, engineering change management, and nonconformance analysis.

Verification Plan Requirement (VPR)
Verification Plan Requirements define how a characteristic is to be verified, including method, sampling plan, and context. This provides a direct connection between product definition and quality execution.

Together, these augmentations extend Product Characteristics from static annotations to structured, lifecycle-aware data elements.

From Ballooned Drawings to Digital Identification

Traditional verification workflows have relied on ballooned drawings, where each tolerance is assigned a balloon number used in inspection documentation.

While widely used, ballooning suffers from several limitations:

• Renumbering during revisions severs traceability
• Manual mapping increases the risk of errors
• Limited interoperability between CAD/PLM/inspection tools
• Poor scalability across suppliers

The MBC Standard replaces informal identification schemes with persistent digital anchors embedded directly within the model.  The result is a scalable and a standards‑based architecture.

Designed for Real Manufacturing Complexity

Manufacturing environments frequently involve complex scenarios in which a single requirement applies to multiple features, patterns, or annotation structures.

The MBC Identification Framework addresses these conditions through structured extension identifiers, enabling:

• Multiple feature associations (e.g., 8X)
• Repetitive feature patterns (e.g., bolt-hole patterns)
• Multi-faceted annotations (e.g., combined of tolerances within one annotation)
• Grouped requirements
• Product definition notes (e.g., general, flagged or local, supplemental) inside the primary MBD model.
• Supplemental support specifications outside the primary MBD model

Alignment with QIF and the Broader Ecosystem

The Quality Information Framework (QIF) defines a downstream Characteristic object that includes definition, nominal, item, and measurement data. MBC pre‑defines the upstream characteristic within the MBD model, ensuring that QIF‑consuming tools receive a fully populated, traceable object.

Key integration points include:

• Product Design Definition:  Persistent PC Tags with UUID and augmentations.
• Product Quality Planning: Direct import of PC data into QIF-based planning tools
• Inspection Programming: Automatic generation of measurement plans from VPR.
• Measurement Execution: Real-time linkage of measured data back to the original PC UUID
• Reporting and Analysis: Measurement results consistently related to a PC ID
• Feedback: Closed-loop updates to design (e.g., tolerance changes via PRA)

Strategic Importance for Now

Enterprises now demand:

• Multi‑CAD interoperability across global design teams.
• Supplier‑wide traceability from OEM to Tier‑2.
• Structured, machine‑readable data for AI‑driven analytics.
• Long‑term digital resilience (data remains usable despite tool migrations).

Proprietary, ad‑hoc tagging cannot meet these expectations. MBC delivers:

• Vendor‑independent persistence (UUID).
• Enterprise‑scale scalability (single PC per requirement (geometrical, textual)).
• Lifecycle continuity (design → planning → inspection → feedback).
• Ready‑for‑automation data (criticality, verification method, requirement linkage).

Thus, MBC is a foundational infrastructure that transforms MBD from a visual design artifact into an executable, data‑rich product definition

Conclusion: The Strategic Impact

The Model‑Based Characteristics Standard formalizes the identification, augmentation, and exchange of verification requirements within a model‑based environment. By embedding persistent identifiers and structured metadata directly in the MBD model, MBC:

• Eliminates ambiguity and manual re‑keying.
• Guarantees end‑to‑end traceability.
• Enables seamless interoperability across PLM, QIF, and inspection systems.
• Prepares product data for advanced analytics and AI.

For organizations pursuing a true digital thread, adopting MBC is not a peripheral improvement—it is a strategic prerequisite for a resilient, automated, and globally synchronized product realization ecosystem.

Learn More

For detailed identifier schemas, augmentation syntax, extension mechanisms, and mapping examples, refer to the full MBC specification and presentation materials published by the Digital Metrology Standards Consortium.

If your organization is advancing MBD, QIF adoption, or digital thread initiatives, now is the time to evaluate how Model-Based Characteristics fit into your strategy.

The post Model-Based Characteristics: Enabling Persistent Identification in the Digital Thread appeared first on DMSC.

The post A New Era for Digital Manufacturing: DMSC & WMG Bring the MBE & QIF Summit to Europe for the First Time appeared first on DMSC.