Interoperability challenges are a common issue when working with modernized engineering data and technology. This is largely due to the multitude of systems and software found across the typical manufacturing enterprise and supply chain—a level of complexity that can make machine-to-machine data translations difficult.
The complicated systems and software ecosystem of the average enterprise reflects the marketplace at large. One major challenge associated with the complex matrix of software and tools on the market is determining how to communicate native model based definition (MBD) datasets to people and systems downstream so it can be consumed throughout the enterprise and supply chain. One method to surmount this challenge is to utilize neutral computer-aided design (CAD) formats, like quality information framework (QIF).
What Is QIF?
QIF is defined by the Digital Metrology Standards Consortium (DMSC), as follows:
“An ISO standard that supports digital thread concepts in engineering applications ranging from product design through manufacturing to quality inspection. Based on XML, the QIF standard contains a Library of XML Schema ensuring both data integrity and data interoperability in Model Based Enterprise implementation.”
Similar to Step242, QIF is a structured and modernized approach to creating derivative files from the authoritative CAD format. The information framework enables CAD translations from one system to many because it is built to be compatible with and consumed by most metrology software.
Translating Native CAD Data Into QIF
If a CAD system has the capability to author machine-readable product manufacturing information (PMI) to industry standards, there is a good chance QIF can be utilized. To bridge the gap and export engineering data – including all MBD elements (geometry, PMI, attributes, and presentation states) – from the native CAD source into QIF, a connector or plugin is required. QIF is an open-source format, but organizations who want to utilize the framework typically leverage an existing translator tool to integrate the data. For example, Capvidia is a CAD software company that produces a tool for translating native CAD into the QIF format.
Once the MBD elements have been harvested from the native CAD system, they must then be validated to ensure all data is translated correctly. When translating data out of the native source into the neutral source it is imperative to have a robust and standardized PMI authoring method so that consistent results populate in QIF. The decomposition of requirements in the framework is dependent on how PMI is authored. As such, if PMI is authored in a nonstandard manner, it can create inconsistent and erroneous results during data translation.
What Happens Once MBD Data Is Translated Into QIF?
Once data has been validated, QIF characterizes all the engineering requirements – including key attributes and PMI found across all presentation states – by assigning each requirement with a unique ID number, a “characteristic ID”.
Figure 1 shows how engineering data is displayed in the QIF derivative after being translated from the native source. There are two notable factors shown in the graphic below. First, the geometry and PMI shown in the QIF derivative are an exact copy of the data in the native file. Second, as the MBD data moves from the native source into QIF, characterization visibly occurs as characteristic IDs are assigned to each engineering requirement.
Figure 1: Native MBD Translated to QIF, Harvesting All the Native MBD Elements
QIF Library Framework
The QIF library framework below, created by Capvidia, highlights several instances where the framework can be utilized:
Figure 2: QIF Library Framework
All elements of the QIF library have integration ability which allows the data to flow from one area to another. However, there are varying levels of maturity associated with each portion of the QIF library. Maturity levels range from early, exploratory stages to advanced levels of proficiency and industry adoption.
Currently, QIF MBD and QIF plans receive the most emphasis within the framework because they are furthest along in progression. Due to high levels of maturity and focus already present in these areas, the remainder of the article will revolve around QIF MBD and QIF plans.
QIF Use Cases That Support Data Interoperability and the Automation of Standard Work
QIF is a vehicle that can improve the interoperability of engineering data into select downstream software and systems due to its XML based neutral format. Adoption rates of QIF into software and tools are growing across the industry because the framework allows engineering data to flow more easily throughout manufacturing, quality, and metrology phases.
Additionally, QIF can be used in many scenarios to automate common human-authored workflows. The framework is dependable and robust because all workflows are automated through a single authoritative source, which is QIF.
QIF has several use cases throughout the enterprise, and each contain significant depth and levels of complexity. Below are four QIF use cases that emphasize automation of standard human-authored workflows and drive improvements in data interoperability:
- Assigning Characteristic IDs to Engineering Requirements
Assigning characteristics to engineering requirements is a common manual task for somebody working in quality and metrology. Because of its traditionally human-authored nature, characterization is error prone, time consuming, and lacks persistent IDs across revisions. With the use of QIF, it is possible to mitigate the need for human characterization. Characterizing requirements can be automated through the combination of the QIF export process and the use of Capvidia’s software tools, MBDConnect and MBDVidia.
When MBD is translated into QIF, the software tools automatically start decomposing engineering requirements behind the scenes and assigning a parent ID. If necessary, the tools will further decompose requirements into child IDs (instance IDs of the parent), creating a parent/child relationship.
Figure 3 highlights how QIF decomposes engineering requirements and creates a parent/child relationship. In this example, the IDs listed as “2” and “3” are the parent requirement for the hole pattern, size, and location requirements. “2” and “3” are further broken down into child (instance) requirements, “2.X” and “3.X”, respectively for each instance.
Figure 3: Parent and Child Characteristic IDs
The automatic characterization of engineering requirements is powerful because it aids in keeping persistent IDs across all revisions during a part’s lifecycle. Additionally, having a fully characterized set of requirements is a foundational element to creating a traceable digital thread as QIF is consumed across the enterprise and supply chain.
- Generating a Bill of Characteristics
Like characterizing requirements, generating a completely characterized bill of characteristics (BoC) is generally a manual task within quality and metrology. Due to the complexity of the process, a BoC is frequently not created at all, or left incomplete.
With the use of QIF, it’s no longer necessary to create the BoC of engineering requirements in MBD by hand. QIF auto generates the creation process showing a complete set of requirements, including all the parent/child relationships, characteristic IDs, measurement objects, PMI, and datum reference frames within the model. See Figure 4 for an example of an auto-generated characterized BoC using Capvidia’s MBDVidia software.
Figure 4: Characterized Bill of Characteristics (BoC)
Having a complete set of characterized requirements is important because it allows the BoC to be consumed by downstream software and even expressed through Excel-based templates. Within Excel, the BoC data can be tailored and filtered depending on the viewpoint and standard work activity being performed. This minimizes the need for human-duplicated information based on job role and viewpoint. Data can then be exported into consumable formats such as HTML and Excel from a single authoritative source.
- Automating Creation of Commonly Used Reports
QIF can be used to auto generate common reports such as first article inspection (FAI) and measurement plan templates by leveraging QIF and the characterized BoC. Automating report creation can save a substantial amount of time, especially for parts and processes that necessitate several reports. See Figure 5 for a snapshot of a simple report generated using Capvidia’s MBDVidia software.
Figure 5: Sample AS9102 Report
- Automating Metrology Planning
Metrology measurement plans are traditionally created manually by reviewing engineering requirements through a manually characterized 2D engineering drawing. Now, through the use of QIF, that process can be automated by importing QIF directly into select metrology software packages. Machine interpretation that adheres to industry standards eliminates human error and saves a considerable amount of time on initial creation of the inspection plan. It also serves to extend the digital thread into metrology via reuse of QIF.
QIF is recognized by popular metrology software providers because it enables the reuse of geometry, PMI, measurement objects, and characterization of requirements when automating the creation of measurement plans. See Figure 6 for a snapshot of a QIF model being virtually simulated and programmed in Metrologic’s Silma X4 software.
Figure 6: Sample Measurement Plan
Using QIF as the Single Source of Truth
Within the four simple use cases above, QIF was used as the authoring source. When QIF is used as the single authoritative source across an enterprise, characterization will be consistent throughout and a reliable, traceable digital thread will be generated.
Although the significant depth and complexity inherent in QIF can be daunting, the benefits it can provide are far reaching across the enterprise and supply chain. Between reducing process time, improving the flow of data, and creating a consistent derivative file, QIF can positively impact MBD within your organization. To provide more insight into details of the framework, the QIF standard has been made available for free download by the DMSC. To speak to a subject matter expert about potential benefits and additional use cases of QIF, or to learn more about the QIF implementation process, get in touch here.
Share This Article!
