Create a FAIR from QIF: What MBD, QIF, and MBC Change About First Article Inspection

The 3D CAD model your customer sent already carries every tolerance on the part. Dimensions, GD&T, surface finish, notes, all of it annotated on the geometry by the engineering team that designed it. And yet the first article inspection still starts the way it did twenty years ago: someone opens a PDF, numbers the characteristics by hand, and types each one into Form 3.

That gap is not a standards problem anymore. Model-Based Definition put the requirements on the model. The Quality Information Framework gave them a format every inspection tool can read. And as of this year, Model-Based Characteristics gives each requirement a permanent identity that survives revisions and handoffs. What has not caught up is the handoff itself: moving that engineering data across organizations and across competing software without someone re-keying it. That handoff is exactly where a first article inspection report gets built.

Why the Drawing Became the First Article Inspection Bottleneck

A 2D drawing is a translation layer between engineering and manufacturing. Every time it is read, a person re-interprets geometry and tolerances that were already unambiguous in the 3D CAD. For an AS9102 first article, that interpretation happens at least twice: once when the quality engineer balloons the drawing, and again when the inspector matches measurements back to balloon numbers.

The cost is not abstract. For drawings with 250 to 500 characteristics, a realistic range for precision manufacturing in aerospace, quality engineers consistently report spending two to eight hours on ballooning alone. A complete manual FAIR runs four to eight hours per part. Then the drawing revises, the balloons renumber, and the inspection plan built against the old numbers is reconciled by hand. Every step is a chance for a transcription error to reach production, and every error found late is rework or a rejected report.

Now multiply by the supply chain, where the same drawings are ballooned by every organization that touches them. The OEM balloons the drawing for its own records. The Tier 1 balloons it again for its FAIR. The Tier 2 machining the detail balloons it a third time. Same part. Same product characteristics. Three independent numbering schemes, none of which agree.

That is the inefficiency the model-based standards were written to remove. Not ballooning itself, but ballooning as a repeated, disconnected process performed on engineering data that was defined once, precisely, upstream. The efficiency gain is in identifying each characteristic once.

MBD, QIF, and MBC: What Each Standard Does

The three standards are often spoken of together, and they do work as a set. Each solves a different part of the problem.

Model-Based Definition: The 3D Model as Product Definition

MBD is the practice of making the annotated 3D CAD model, not the 2D drawing, the authoritative product definition. The model carries Product and Manufacturing Information (PMI) directly on the geometry: dimensions, GD&T per ASME Y14.5, surface finish, material specifications, and notes. ASME Y14.41 and its international counterpart ISO 16792 define how that manufacturing information is represented so it reads the same in every CAD system, and so the design intent survives the trip from engineering to the manufacturing floor.

The practical consequence: an MBD model can be queried programmatically, so a CMM program, an inspection plan, or a bill of characteristics is generated from the primary source rather than re-derived by a person reading a sheet. Critical dimensions, materials, and process specifications are identified at the source, not rediscovered during inspection planning.

Quality Information Framework: What QIF Means

QIF stands for Quality Information Framework, and it is the format quality data travels in. It is a vendor-neutral, CAD-agnostic XML standard for representing measurement plans, part characteristics, measurement resources, actual results, and statistics. It was published as ANSI/QIF 3.0 and elevated to ISO 23952:2020, which is why a QIF file appears as an import and publish option in CMM software, MBD tools, and inspection planning systems from different vendors. Interoperability is the point: a QIF file written by one tool reads the same in the next.

QIF is maintained by the Digital Metrology Standards Consortium (DMSC), the ANSI-accredited body that also maintains DMIS, the standard that governs how coordinate measuring machines are programmed. Its members include Lockheed Martin, Pratt & Whitney, Honeywell, Hexagon, Renishaw, and Mitutoyo America: the OEMs that flow down model-based requirements and the metrology vendors that measure against them.

Model-Based Characteristics: Persistent Identification

MBC is the newest of the three, approved as an American National Standard on May 31, 2026. It closes a specific gap. MBD says what a tolerance is. QIF says how it was measured. Neither gives the tolerance a permanent identity that survives a revision, a CAD translation, or a handoff to another company's software.

MBC does. Each product characteristic gets a human-readable PC-Tag (PC007, for example) and a machine-readable UUID that is generated once and never changes. Revise the design, transfer it to a supplier running different software, send it out in a different format: the identifier holds. Optional augmentations flag critical characteristics, link each one to its specification, and define how to validate it.

Persistent identification is what manual balloon numbering always tried to be. The balloon number was a local convention that broke on every revision and every handoff. The UUID is a permanent one that does not, and traceability from design intent to measured result rides on it.

Together, these three standards are what quality professionals mean by the digital thread: a single requirement, defined once in engineering, traceable through inspection planning, measurement, nonconformance, and analytics without re-entry.

The Digital Thread Is Solved. The Handoff Is Not.

Ron Trout, VP, General Manager at Net-Inspect, made the point directly at the 2026 MBE and QIF Summit: the technical challenge of the digital thread is largely solved by MBD and QIF. The barrier is securely sharing that information across every tier of a supply chain and across the many software tools those tiers run.

Consider how the data actually moves. Requirements flow down from the OEM through prime, second-tier, third-tier, and sub-tier shops. Inspection information flows back up the same chain. Every company boundary and every tool boundary is a place where a characteristic's identity gets re-mapped, re-numbered, or dropped, and the quality control reporting that comes back is only as trustworthy as the weakest handoff. For the business on either end, that is a traceability and cost problem.

MBD and QIF unlock the data. Something still has to connect it.

That is the role of a shared quality platform, and it is the problem Net-Inspect was built around. More than 11,000 companies across 59 countries work on it, OEMs and their suppliers in the same multi-tenant environment, so the customer flowing down a model-based requirement and the supplier returning a FAIR are working from a single source of truth, with user access controlled at every level. In September 2026, Net-Inspect joined the DMSC to bring that supply chain perspective into the working groups that maintain QIF and MBC.

How to Create a FAIR from QIF

In practice, creating a FAIR from QIF is a four-step process. The automation is in the handoffs, not in a single tool.

1. Model. The part is defined as an MBD model with PMI, and the PMI is validated in an MBD tool. Capvidia's MBDVidia is the established path into Net-Inspect; the two companies have been integration partners since 2017, and MBDVidia extracts PMI from native Creo, NX, SolidWorks, and CATIA as well as STEP AP242. Elysium is a second partner path for model-based engineering data.

2. Publish. The product characteristics are exported as standardized QIF. In MBDVidia this is a single command, Publish to Net-Inspect, and the output carries every characteristic with its identity attached.

3. Ingest. On the Create FAIR page, Import from External accepts QIF directly. The same hub accepts Capvidia output, JT and STEP models, XML, Excel, a completed FAIR that exists only as a PDF, and the major third-party ballooning formats, so first article inspection reports can start from whatever the customer sent. From QIF, the characteristics land on AS9102 Form 3 as the bill of characteristics, already numbered and already carrying their identifiers. Nothing is re-drawn, re-typed, or re-ballooned. The bulk of the FAIR is populated before anyone types a field, and the model reference travels with it, so each characteristic on Form 3 stays tied to the geometry it came from. Material certifications, process documentation, and other supporting documentation attach to the same record.

4. Result. Measurements come back the same way the requirements went out. The Measurement Collection Service reads QIF results from coordinate measuring machines and other inspection machines, alongside 40 other measurement formats, and each result aligns to its source characteristic by UUID. The UUID column on Form 3 shows the linkage. When the model revises, the identifier does not change, so the measurement history does not break and the record stays accurate through production.

The result: a first article inspection report where the model, the characteristics, and the measurements share one identity from design intent to sign-off, prototype or first production lot.

One honest note. Most drawings arriving at supplier quality departments today are still 2D PDFs. For those, the integrated Balloon Tool reads the drawing with OCR and document intelligence and populates Forms 1, 2, and 3 from the ballooned PDF. Both paths land on the same Form 3, so a shop running model-based and drawing-based programs works one FAI process, with the same tooling, reporting, and supplier buy-off. How Automated Ballooning Accelerates First Article Inspection covers the 2D side in detail.

Before Your First Model-Based FAIR: Five Quality Control Checks

The QIF path only works when the upstream engineering data is actually model-based. Five things determine whether it is, worth settling before the first component is machined.

The model carries PMI. A solid body with a separate drawing is not MBD; the tolerances have to be annotated on the 3D CAD geometry, or there is nothing to extract.

The MBD tool writes QIF. MBDVidia does. Tools whose functionality stops at STEP AP242 carry geometry and PMI, but not the quality-data format the inspection process consumes.

The customer flows down the model. Many OEMs still issue the drawing as the contractual authority with the 3D CAD as reference. The FAIR has to match what the purchase order calls out, so confirm which document governs before building against it.

The CMM software writes QIF results. Many current CMM platforms do. The Measurement Collection Service reads proprietary and CSV-style text formats too, but the UUID linkage is cleanest when results arrive as QIF.

Characteristic identifiers survive your current toolchain. This is the MBC test. Trace one characteristic from engineering through inspection planning to the CMM report, identifying it at each stop. If it is a different balloon number at each stop, that is the re-keying the QIF path removes, and the first place accuracy is lost.

Beyond the First Article Inspection Report

The first article is the first place the model's requirements become measurement data. It is not the last. Product quality over a production run, supplier reporting, and process control all draw on the same characteristics.

Today, the same UUID that lands on Form 3 is visible on Record Measurements and the Capability Report, so a characteristic's capability over time ties back to the design that defined it. The direction from here is to carry that identity further: into the quality planning that sits upstream of inspection, onto the 3D CAD model itself, and across every tier of the supply chain that touches the part. Net-Inspect's seat at the DMSC is part of how that direction takes shape, inside the working groups where QIF and MBC continue to evolve.

The standards made that direction possible. MBC made persistent identification of product characteristics an American National Standard in May; QIF has been an ISO standard since 2020. The schema for a characteristic that stays itself from design through SPC exists. The remaining work is connecting the systems it passes through, and that is a supply chain problem before it is a software problem. To see how a QIF file becomes a FAIR in practice, explore the First Article Inspection module, or read the Net-Inspect and Capvidia integration overview.

Frequently Asked Questions

What does QIF mean?

QIF is the Quality Information Framework, an ANSI and ISO standard (ISO 23952:2020) for exchanging quality data between software tools. It is XML-based and can carry an inspection plan, the product characteristics to be measured, the measurement resources, the actual results, or the statistics computed from them. It is maintained by the Digital Metrology Standards Consortium.

Can I convert CSV to QIF?

Several CMM packages write QIF results natively, and some convert a CSV export to QIF. For a Net-Inspect FAIR the conversion is not required: the Measurement Collection Service reads QIF alongside text-based CSV-style formats, so CSV measurements land on Form 3 either way. QIF is the better input when the goal is UUID-level traceability back to the model.

What is the difference between QIF and STEP AP242?

STEP AP242 is the neutral CAD interchange format: geometry and PMI, carried across CAD systems. QIF is the quality-data format: the characteristics, plans, and measurement results that verify the part. A model-based FAIR typically starts from STEP AP242 or native CAD and produces QIF for the inspection process. Net-Inspect accepts both as import types, with QIF as the path that carries characteristic identity.

See how Net-Inspect handles first article inspection