OPC UA and QIF address different layers of the industrial data stack. OPC UA handles real-time operational data from shop floor equipment — machine states, cycle times, process parameters, alarm conditions. QIF handles quality measurement data — dimensional results, inspection plans, nonconformance records, statistical summaries.
Most solution providers sell one or the other. The ones who understand how they work together have access to a fundamentally different conversation — and a fundamentally different deal size.
The gap these two standards address together
Consider a CNC machining center producing a precision aerospace component. The machine generates real-time process data via OPC UA: spindle speed, tool wear indicators, feed rate, temperature. Downstream, a CMM measures the finished part and generates inspection results via QIF: dimensional deviations, surface finish measurements, GD&T conformance status.
These two data streams exist in isolation at most manufacturers. The process engineer looks at the OPC UA data. The quality engineer looks at the QIF data. Neither has a systematic way to correlate a recurring dimensional deviation with a specific process parameter — even though that correlation is the key to eliminating the root cause.
The integration of OPC UA process data with QIF quality data is what closes this loop. It enables predictive quality: using process parameter trends to predict measurement outcomes before the part reaches the CMM. This is not theoretical — it is being implemented at advanced manufacturers in automotive and aerospace today.
“The manufacturer who can correlate a spindle temperature excursion with a diameter deviation has a fundamentally different quality cost structure than one who cannot.”
Why this integration story is difficult to tell
The OPC UA and QIF communities have historically been separate. OPC UA is primarily an automation and connectivity standard, championed by the automation vendors (Siemens, Rockwell, Beckhoff) and the IIoT platform community. QIF is primarily a quality and metrology standard, championed by the CMM vendors (Hexagon, Zeiss, Renishaw) and the quality software community.
Solution providers tend to live in one community or the other. A systems integrator who does OPC UA connectivity work typically does not do CMM integration. A metrology software ISV typically does not do OPC UA implementation.
This creates a genuine gap in the market — and a genuine opportunity for the solution provider who can credibly bridge it. You do not need to build the entire integration yourself. You need to understand how the two standards relate and be able to articulate the business case for connecting them. The implementation can follow a partner relationship.
The ISA-95 context
ISA-95 (IEC 62264) defines the hierarchical model for manufacturing operations management — the levels from field devices through enterprise systems. In this model, OPC UA operates primarily at Levels 1 through 3 (device to operations). QIF operates at Level 3 (quality management within site operations) and connects upward to Level 4 (enterprise quality systems, PLM).
Understanding this hierarchy matters for the sales conversation because it determines who the stakeholders are. An OPC UA conversation involves the automation engineer, the MES project lead, and the IT infrastructure manager. A QIF conversation involves the quality manager, the PLM administrator, and the regulatory compliance team.
An OPC UA plus QIF conversation involves all of them — and it is typically sponsored by the VP of Operations or the CTO, because it is a cross-functional data strategy decision rather than a departmental tool selection.
How to position the combined story for your specific offering
Whether you are selling edge infrastructure, MES software, CMM integration services, or quality management systems, the OPC UA plus QIF narrative gives you a way to position your offering as part of a larger architecture — not as an isolated product.
The positioning framework is simple: identify where your offering sits in the data flow, and name the two data standards on either side of it. An edge gateway vendor can say: “We collect OPC UA data from your shop floor equipment and structure it for consumption by your QIF-compatible quality systems.” A CMM software vendor can say: “We generate QIF output that closes the loop back to your OPC UA process data.” A systems integrator can say: “We design and implement the data architecture that connects your OPC UA operational data to your QIF quality records.”
Each of these positioning statements is more strategic than “we sell [product category].” Each of them opens a conversation about data architecture rather than product features. And each of them leads to a larger deal with more stakeholders.
KEY TAKEAWAY OPC UA and QIF together enable predictive quality — the correlation of process parameters with inspection outcomes. Solution providers who can articulate this integration access VP-level buyers and larger deal sizes
2BMobile → 2BMobile builds positioning and messaging for solution providers at the OT/IT convergence layer. Talk to us about your integration story.