The researchers, led by Shahlokhon Gafurova of Bukhara State University in Uzbekistan, call this body of data quality-oriented big data: the subset of an organization’s data assets that is acquired, integrated, and analyzed to support decisions about the quality of products, services, and processes. Its defining feature, they argue, is consequence. When ordinary enterprise data is wrong, the result may be a misdirected advertisement. When quality-oriented data is wrong, the result is a defective product shipped to customers, a safety signal missed, or a supplier wrongly cleared. This distinction matters because the properties that make big data valuable, namely volume, velocity, and variety, are the same properties that make it difficult to manage. Variety in particular means that quality-relevant data arrive in incompatible schemas, units, granularities, and time bases, so the apparently simple act of asking a question across sources presupposes a substantial integration effort.

The paper positions itself against the rapidly growing literature on Quality 4.0, a term describing the alignment of quality management practices with the technological capabilities of Industry 4.0. That literature has produced valuable insights into definitions, readiness factors, and implementation barriers, but the authors contend it has a systematic blind spot: it treats the data lifecycle as a black box. The Quality 4.0 literature generally presumes that relevant data exist, that they can be brought together, and that they are trustworthy enough to feed analytical models. Research in data management suggests none of these presumptions is safe. Data integration remains one of the hardest and most expensive problems in enterprise computing, and machine learning pipelines in production settings fail far more often because of data problems than because of modeling problems. Field studies of high-stakes artificial intelligence have documented data cascades, in which small compromises in data work compound into serious downstream failures.

To close this gap, the authors propose a layered conceptual architecture that organizes the lifecycle of quality-oriented big data into five interconnected layers. Four of them form a vertical value chain: multi-source acquisition, integration and data fusion, data quality assurance, and analytics and knowledge extraction. The fifth layer, data governance and ethics, is deliberately drawn as a cross-cutting spine rather than a stage, because governance decisions constrain and enable every other layer, from what may be collected to how model outputs may be used. The architecture should be read through two flows. The upward flow is the value flow, in which raw signals gain meaning through fusion, gain trustworthiness through assurance, and gain decision relevance through analytics. The downward flow is the feedback flow, in which analytical findings redirect acquisition, refine fusion, and recalibrate assurance. Together, the two flows make the architecture a loop, consistent with the closed-loop character of quality work.

At the base of the architecture sits acquisition, which the authors insist is a design problem rather than a passive recording problem. Three design decisions carry particular weight. The first is coverage: which processes, machines, and product families are instrumented, and which remain dark. Coverage decisions create the blind spots within which quality problems can develop unobserved, and they are rarely revisited once made. The second is representativeness: whether captured data reflect the full operating envelope of the process, including rare but consequential conditions. The machine learning literature is unambiguous that collection-stage bias is among the most damaging and least visible defects a dataset can carry, because no downstream procedure can recover information that was never captured. The third is metadata at capture: recording the provenance, calibration state, and context of each stream at the moment it is acquired. Each characteristic failure of this layer, from blind spots to orphaned data whose meaning is unrecoverable, is invisible at the point where it is committed and expensive at the point where it is discovered.

The second layer converts many streams into one coherent body of evidence, and for quality-oriented data two integration tasks stand out. The first is product genealogy: linking every unit of output to the materials, machines, parameters, operators, and environmental conditions that produced it, across systems that were never designed to share keys. Genealogy is the backbone of root-cause analysis, recall management, and supplier quality, and it is an entity-resolution problem of considerable difficulty. The second is temporal alignment: placing measurements from sources with different clocks, sampling rates, and latencies onto a common time base. Quality analytics is intensely temporal, because cause precedes effect along a process flow, and misaligned time bases manufacture spurious lead-lag relationships. Both failure modes are insidious because they pass silently through statistical checks: the integrated data are internally well formed, they are simply wrong about the world.

The third layer, data quality assurance, is described as the keystone of the entire structure, the point at which the pipeline either does or does not convert integrated data into trustworthy data. The authors distinguish two shifts that separate assurance in their architecture from traditional data cleansing. The first is from episodic to continuous: in a closed-loop setting fed by streams, quality assurance cannot be a project conducted before analysis but must be a monitoring function that runs alongside the pipeline, validating new data against expectations and raising alarms on drift. The second is from generic to task-conditional. Fitness for use is relative to the use: a real-time process control application is exquisitely sensitive to timeliness and far more tolerant of isolated gaps, while a model trained to predict field failures is sensitive to completeness and representativeness across months of history and indifferent to millisecond latency. The paper maps seven quality dimensions, including accuracy, completeness, consistency, timeliness, validity, traceability, and representativeness, to the specific ways each degrades in multi-source pipelines and the quality decisions each degradation corrupts.

The theoretical core of the paper is a mediation claim stated in falsifiable form. The prevailing intuition, encouraged by the readiness literature, is that acquiring big data capability, meaning infrastructure, tools, and skills, improves organizational quality. The authors argue instead that a central part of this relationship runs through a specific intermediary: data quality. Capability contributes to better quality outcomes in large part because, and to the extent that, it delivers trustworthy data to the analytical layer; where the data foundation is weak, much of the capability accumulates as cost rather than converting into quality. The claim is testable: the mediation account predicts that a substantial share of the capability-to-outcome association should attenuate once data quality is introduced as an intermediate variable. Four additional propositions formalize boundary conditions, task-conditional effects, and the moderating role of governance, each stated so that it could in principle be contradicted by firm-level or pipeline-level evidence.

The governance and ethics layer answers a different kind of question: not what can be done with quality-oriented big data, but what may and should be done, by whom, and under whose accountability. Governance earns its cross-cutting position for a structural reason: it is the only layer whose outputs are constraints and mandates for all the others. Stewardship assignments determine who is accountable for coverage decisions, standards for identifiers determine whether the genealogy problem is tractable, and approval requirements determine which models may act on the process. Ethics enters through the specific character of quality-oriented data, because process data are also people data: operator identifiers, shift patterns, and performance traces are embedded in the same streams that describe machines and materials, so quality analytics borders on workforce surveillance and must be designed deliberately to respect that border. The authors argue that ethical principles take effect only when translated into decision rights, review procedures, and accountable roles.

For organizations, the architecture suggests a different investment logic than the one currently prevailing. The typical pattern is to begin at the analytics layer by procuring tools and then to discover the data layers below as obstacles. If the propositions hold, organizations would be better served by the reverse sequence: auditing acquisition coverage and metadata practice first, making genealogy and temporal alignment explicit engineering objects second, instituting continuous, task-conditional quality monitoring third, and letting the analytical portfolio grow at the pace the assured foundation supports. The authors are careful to note that the framework is conceptual and awaits empirical validation, and that testing the mediation claim will require longitudinal designs capable of ruling out reverse causality and common causes such as quality culture. But if the central claim survives scrutiny, the implication is striking: as quality decisions become more automated and more consequential, the trustworthiness of the data beneath them stops being a technical detail and becomes part of the substance of quality itself, making better managed data one of the most direct paths to better organizational quality.

Subject of Research: A conceptual architecture for managing quality-oriented big data across acquisition, fusion, quality assurance, analytics, and governance in data-driven organizations

Article Title: Managing quality-oriented big data: a conceptual architecture for acquisition, fusion, and analytics in data-driven organizations

Article References: Gafurova, S., Rahmatov, S., Zakhidova, U., Rakhimova, D., & Kabilova, G. (2026). Managing quality-oriented big data: a conceptual architecture for acquisition, fusion, and analytics in data-driven organizations. Frontiers in Big Data, 9, Article 1977331. https://doi.org/10.3389/fdata.2026.1977331

Image Credits: AI Generated

DOI: 10.3389/fdata.2026.1977331

Keywords: big data, data quality, Quality 4.0, data governance, data fusion, data integration, machine learning systems, quality analytics, data-driven organizations, data management, Industry 4.0, data-centric AI