Total Quality Management & ISO Standards

Chapter 15
Integrated, Digital and Future Quality Management

Graduate Program in Operation Management (GPOM)
Total Quality Management & ISO Standards   •   Graduate

Integrated, Digital and Future Quality Management

Introduction and Context

Quality management is no longer confined to product inspection, process capability, or compliance with ISO 9001. Contemporary organizations operate interconnected production, service, information, environmental, and human systems. A supplier disruption may create both a quality defect and a carbon increase; a cyberattack may corrupt inspection data; an unsafe process may also produce nonconforming output; and an algorithm intended to predict failures may reproduce historical bias. Consequently, quality must be managed as an integrated organizational capability.

This chapter examines the integration of quality with environmental management, occupational health and safety, information security, sustainability, and digital technologies. It also evaluates electronic quality management systems (e-QMS), the Internet of Things (IoT), digital twins, automation, advanced analytics, and responsible artificial intelligence (AI). The discussion emphasizes governance, assurance, cybersecurity, data quality, organizational change, and the limitations of technological solutions.

Learning Objectives

By the end of this chapter, students should be able to:

  1. Explain the logic and benefits of integrated management systems.
  2. Relate ISO 9001, ISO 14001, ISO 45001, ISO/IEC 27001, and sustainability practices.
  3. Design an e-QMS architecture that supports traceability, corrective action, and risk-based decision-making.
  4. Distinguish IoT monitoring, digital twins, automation, analytics, and AI.
  5. Evaluate predictive-quality models using appropriate performance and process measures.
  6. Assess cybersecurity, data governance, human factors, and responsible-AI risks.
  7. Critically examine emerging directions in ISO standards and future quality management.

1. From Separate Standards to Integrated Management

A management system is a set of interrelated processes, responsibilities, policies, resources, and controls used to achieve organizational objectives. A quality management system (QMS) focuses on consistent fulfilment of customer and applicable requirements. Other systems address environmental performance, worker health and safety, information security, energy, business continuity, or social responsibility.

Historically, organizations implemented these systems independently. This produced duplicated audits, conflicting procedures, multiple document repositories, and competing performance indicators. Integration seeks one coherent management architecture while preserving the technical requirements of each discipline.

The ISO high-level structure supports integration. Many modern ISO management-system standards use common concepts such as organizational context, leadership, planning, support, operation, performance evaluation, and improvement. This common structure does not mean that standards are identical. ISO 14001 requires attention to environmental aspects and impacts; ISO 45001 emphasizes hazards, worker participation, and prevention of injury and ill health; ISO/IEC 27001 addresses information-security risks and controls. Integration therefore means coordinated governance, not elimination of specialist expertise.

1.1 The principal standards

Standard or frameworkPrimary concernDistinctive management emphasis
ISO 9001Quality managementCustomer requirements, process control, risk-based thinking, improvement
ISO 14001Environmental managementEnvironmental aspects, compliance obligations, life-cycle perspective
ISO 45001Occupational health and safetyHazard elimination, risk reduction, worker consultation and participation
ISO/IEC 27001Information securityConfidentiality, integrity, availability, risk treatment and controls
ISO 50001Energy managementEnergy performance, energy review, measurement and continual improvement
ISO 31000Risk management guidancePrinciples and framework for managing risk across the organization
ISO 26000Social responsibility guidanceAccountability, ethics, stakeholders, human rights and community impact

ISO 26000 is guidance rather than a certifiable management-system standard. Likewise, sustainability reporting frameworks and regulatory schemes may complement, but do not replace, management-system requirements.

1.2 Integration architecture

An integrated management system (IMS) should be designed around organizational processes rather than around standards. A product-development process, for example, can include quality requirements, environmental design criteria, safety-by-design reviews, protection of intellectual property, and sustainability objectives in one workflow.

A useful architecture has four layers:

  1. Governance layer: policy, accountability, objectives, risk appetite, legal obligations, and review by top management.
  2. Process layer: core and support processes, process owners, inputs, outputs, controls, and interfaces.
  3. Assurance layer: audits, inspections, monitoring, testing, incident investigation, management review, and corrective action.
  4. Information layer: master data, records, evidence, dashboards, access controls, retention rules, and analytics.

Integration should be assessed by the quality of coordination, not by the number of standards displayed on a certificate. A weakly integrated system can hide accountability gaps beneath a sophisticated document structure.

1.3 Risk and opportunity across disciplines

A common risk register can link causes, events, consequences, controls, owners, and indicators. However, organizations should avoid reducing all risks to a single numerical score. Risk scores can create false precision, particularly when likelihood and consequence estimates are subjective.

For a simple expected-loss estimate, when outcomes are mutually exclusive and probabilities are credible:

E(L) = ∑ᵢ pᵢ Lᵢ

Here, pi is the probability of outcome i, Li is its monetary or operational loss, and E(L) is expected loss. The estimate is useful for comparing alternatives, but it does not capture all ethical, legal, reputational, or catastrophic effects. It assumes that the listed outcomes are sufficiently complete and that the probabilities and losses are decision-relevant.

2. Quality, Environment, Safety, Security and Sustainability as One System

Integration is strongest when shared objectives are translated into operational controls. Consider a compressed-air system. Quality requires stable pressure and contamination control; environmental management seeks reduced energy consumption and emissions; occupational safety requires safe maintenance and noise control; information security requires secure monitoring devices; sustainability requires consideration of equipment life, materials, and supplier practices.

The same process can therefore have multiple performance dimensions. A dashboard that displays only defect rates may encourage operators to increase inspection or rework, possibly raising energy use and waste. A balanced system monitors outcomes and unintended consequences.

2.1 Life-cycle thinking

Life-cycle thinking extends quality beyond the factory gate. It considers design, sourcing, production, distribution, use, maintenance, and end-of-life. It does not require an organization to control every stage directly; it requires relevant stages and influence to be considered.

Quality engineering and sustainability can reinforce each other through durable design, repairability, reduced material variation, lower scrap, energy-efficient processes, and supplier development. They can also conflict. For instance, a lower-carbon material may have higher defect variability or require new worker-safety controls. Decisions should therefore use multi-criteria analysis rather than one-dimensional optimization.

2.2 Worker participation and culture

ISO 45001 places particular emphasis on consultation and participation of workers. This principle is also essential to quality and digital transformation. Operators possess tacit knowledge about abnormal conditions, workarounds, and emerging failure modes. A system that collects sensor data while ignoring worker observations is not truly intelligent.

Quality culture is demonstrated through resource allocation and managerial behavior. If production targets routinely override stop-work authority, reporting of near misses, or nonconformity containment, formal policies have little practical effect.

3. The Electronic Quality Management System

An e-QMS is a controlled digital environment for managing quality processes, records, workflows, approvals, competence information, audits, complaints, supplier quality, nonconformities, corrective and preventive actions, and management review. It is not simply a paper procedure converted to PDF.

3.1 Core capabilities

A mature e-QMS commonly includes:

  • controlled documents and version history;
  • requirements and configuration management;
  • training and competence records;
  • inspection and test plans;
  • nonconformity and deviation management;
  • root-cause analysis and corrective action;
  • supplier qualification and performance monitoring;
  • audit planning and evidence capture;
  • complaints, returns, and field-failure analysis;
  • electronic signatures and approval controls;
  • dashboards linked to authoritative source data.

Workflow automation can ensure that a detected nonconformity is assigned, contained, investigated, reviewed, and closed with evidence. Yet automation of a poor workflow merely accelerates poor control.

3.2 Data model and traceability

Traceability depends on stable identifiers and relationships among items such as customer requirement, product configuration, batch, serial number, material lot, process parameters, inspection result, operator qualification, equipment status, and release decision. Data lineage should answer: where did the value originate, who changed it, when was it changed, under which authorization, and where was it used?

Important data-quality dimensions include accuracy, completeness, consistency, timeliness, validity, uniqueness, and integrity. A record can be accurate but not timely; complete but incorrectly classified. Quality analytics are only as reliable as the data-generating process.

3.3 Implementation principles

Successful implementation begins with process mapping and information requirements, not software selection. Organizations should:

  1. identify critical decisions and required evidence;
  2. simplify and standardize workflows before digitizing them;
  3. define data ownership and master-data rules;
  4. integrate the e-QMS with enterprise resource planning, manufacturing execution, laboratory, maintenance, and supplier systems where justified;
  5. validate configurations and interfaces according to intended use;
  6. pilot with users and measure adoption;
  7. establish change control, access review, backup, retention, and disaster recovery.

A cloud service may reduce infrastructure burden, but it does not transfer accountability for data classification, access rights, supplier assurance, regulatory obligations, or business continuity.

4. IoT, Automation and Digital Twins

The Industrial Internet of Things connects sensors, machines, products, and software to collect and exchange data. Typical quality applications include vibration monitoring, temperature control, vision inspection, environmental sensing, tool-wear detection, and condition-based maintenance.

Automation executes predefined actions, such as rejecting a unit outside tolerance or stopping a machine after a safety interlock. Analytics interprets data to describe, diagnose, predict, or prescribe. AI may support complex pattern recognition, but it does not remove the need for process knowledge and control.

A digital twin is a maintained digital representation of a physical asset, process, or system that is connected to relevant data and supports analysis or decision-making. A static three-dimensional model is not necessarily a digital twin. The twin must have an explicit purpose, defined boundaries, data relationships, update logic, and validation expectations.

4.1 Predictive quality

Predictive quality attempts to identify conditions associated with future nonconformity before the defect occurs. A simplified binary classification model may estimate:

P(Y = 1 | X) = f(X)

Here, Y = 1 denotes a defined future event, such as nonconformance; X is a vector of available features, such as temperature, pressure, material lot, and cycle time; and f is a statistical or machine-learning model. The conditional probability is meaningful only when the target is clearly defined, data are representative, and the deployment environment is sufficiently similar to the development environment.

For a binary classifier, the confusion matrix contains true positives, false positives, true negatives, and false negatives. Important measures include:

Precision = TP ÷ (TP + FP)
Recall = TP ÷ (TP + FN)

Precision is the proportion of predicted positives that are actually positive. Recall is the proportion of actual positives detected. TP, FP, and FN denote true positives, false positives, and false negatives. These measures are defined when the relevant denominators are nonzero. In safety-critical or high-cost applications, recall may be prioritized, but excessive false alarms can create alert fatigue and undermine trust.

For a quality process with stable, approximately normal individual observations, a conventional standardized value is:

z = (x − μ) ÷ σ

Here, x is an observation, μ is the process mean, and σ is the process standard deviation. The formula is descriptive and does not prove normality or statistical control. If the process is unstable, the mean and standard deviation may not represent future performance.

4.2 Model validation and drift

A predictive model should be evaluated using data separated by time, product family, or site where appropriate. Randomly splitting highly correlated observations can produce optimistic results through leakage. Validation should examine:

  • discrimination: can the model distinguish cases?
  • calibration: do predicted probabilities correspond to observed frequencies?
  • operational value: does intervention reduce defects or risk?
  • fairness: does performance differ systematically across relevant groups or suppliers?
  • robustness: does performance survive sensor failure, recipe changes, and seasonality?
  • explainability: can responsible personnel understand and challenge the recommendation?

Concept drift occurs when relationships between inputs and outcomes change. Data drift occurs when input distributions change. Both require monitoring, retraining rules, and human review. A model should be treated as a controlled process component, with versioning, approval, performance limits, and retirement criteria.

5. Responsible AI and Human-Centred Quality

Responsible AI is the governance of AI so that it is lawful, safe, secure, fair, transparent, accountable, and aligned with legitimate organizational purposes. In quality management, risks include incorrect automated release decisions, biased supplier ratings, exposure of confidential designs, fabricated explanations, and automation bias—the tendency to accept a machine recommendation without adequate challenge.

A practical control framework includes:

  1. Purpose limitation: define the decision the system may support and prohibit unauthorized uses.
  2. Data governance: document provenance, consent or legal basis where relevant, retention, quality, and permitted use.
  3. Human authority: specify who can override, stop, or appeal a system decision.
  4. Technical assurance: test accuracy, robustness, cybersecurity, adversarial resilience, and failure modes.
  5. Transparency: communicate system capabilities, limitations, and confidence appropriately.
  6. Monitoring: detect drift, disparate error rates, unsafe recommendations, and unauthorized changes.
  7. Accountability: assign owners for design, deployment, operation, and incident response.

Generative AI requires additional controls because outputs may be plausible but false. It should not be treated as an authoritative source for specifications, regulatory interpretation, or release decisions without verification against approved records.

6. Cybersecurity and Data Governance in Quality Systems

Digital quality creates an expanded attack surface. Threats include ransomware, credential theft, malicious alteration of inspection results, sensor spoofing, insecure remote access, supply-chain compromise, and denial of service. Information security is therefore a quality concern: compromised data can produce defective, unsafe, or noncompliant decisions.

ISO/IEC 27001 uses a risk-based information-security management approach. In practice, organizations should classify quality data according to confidentiality, integrity, and availability requirements. Integrity is especially critical for test results, calibration records, electronic approvals, recipes, and product-release evidence.

Controls should include least-privilege access, multifactor authentication, network segmentation, secure configuration, patch management, tested backups, logging, vulnerability management, incident response, supplier assurance, and recovery exercises. Operational technology requires care because immediate patching may disrupt validated or safety-critical processes. Compensating controls and planned maintenance windows may be necessary.

Data governance defines who may create, modify, approve, use, retain, and dispose of data. It should address:

  • ownership and stewardship;
  • metadata and naming conventions;
  • access and segregation of duties;
  • audit trails and electronic signatures;
  • retention and defensible deletion;
  • privacy and cross-border transfer;
  • data quality rules;
  • archival and recovery;
  • third-party and cloud responsibilities.

Cybersecurity is not achieved by buying a security product. It is a continuing management process involving people, technology, suppliers, and organizational behavior.

7. Metrics and Decision-Making

A digital environment can generate thousands of indicators, but measurement abundance is not measurement quality. Measures should be connected to decisions and reviewed for unintended incentives.

Useful quality indicators include first-pass yield, defect rate, customer complaints, cost of poor quality, corrective-action recurrence, audit findings, supplier escapes, process capability, and time to containment. Complementary indicators include energy intensity, waste, injury and near-miss reporting, security incidents, data-quality exceptions, model false-negative rate, and overdue actions.

For a process where each unit is classified as conforming or nonconforming, the observed defect proportion is:

p̂ = d ÷ n

Here, d is the number of nonconforming units and n is the number inspected. The result is a proportion and is multiplied by 100 for a percentage. It is an estimate of the underlying defect probability only under appropriate sampling assumptions; clustered, biased, or changing samples require careful interpretation.

A balanced performance review should ask:

  • Is the measure operationally defined?
  • Is the data source controlled?
  • Does the measure distinguish outcome from activity?
  • What behavior might the measure encourage?
  • Are leading and lagging indicators both present?
  • Are trade-offs visible across quality, safety, environment, security, cost, and delivery?

8. Illustrative Case: Northstar Medical Devices

Background

Northstar Medical Devices, an illustrative manufacturer of infusion-pump components, operated ISO 9001 and ISO 13485-based quality processes, but its inspection, maintenance, environmental, and cybersecurity records were held in separate systems. Customer complaints about intermittent flow variation were increasing.

Problem

The organization initially suspected operator error. Investigation revealed that the complaint rate was associated with a combination of tool wear, ambient temperature, resin-lot variation, and an inspection-camera firmware change. Data were fragmented, timestamps were inconsistent, and several users shared credentials. A proposed machine-learning solution produced high apparent accuracy in testing but had used records from the same production runs in both training and test sets.

Analysis

Northstar formed a cross-functional team involving quality, production, maintenance, engineering, information security, environmental management, and operators. The team mapped the product and information flows, classified critical data, and performed a joint risk assessment. It identified three major weaknesses: inadequate traceability between material lots and inspection results, uncontrolled changes to the camera system, and absence of a formal model-validation process.

Approach and solution

Northstar implemented an integrated workflow. Material lots, machine settings, tool identity, camera version, operator qualification, and inspection outcomes received linked identifiers. A condition-monitoring pilot measured tool vibration and temperature. The predictive model was rebuilt using time-separated validation data and was used initially as an advisory alert rather than an automatic release control.

Cybersecurity controls included individual accounts, multifactor authentication for remote access, network segmentation, immutable audit logs, and tested restoration procedures. Environmental and safety reviews were incorporated into equipment-change approval. Operators could challenge alerts and record contextual causes not visible to sensors.

Outcome

After the pilot, the organization reported fewer unexplained escapes and faster containment, although the model generated false alarms during a seasonal temperature shift. Rather than suppressing the alarms, Northstar introduced environmental features, recalibrated the model, and added a drift threshold requiring engineering review. The company also discovered that some benefits came from improved traceability and disciplined change control rather than from AI itself.

Learning points

The case demonstrates that predictive quality is a socio-technical intervention. Reliable data architecture, process understanding, cybersecurity, worker participation, and controlled experimentation are prerequisites. An algorithm cannot compensate for weak traceability or uncontrolled change.

9. Implementation Road Map

Organizations can use the following sequence, adapting it to risk and scale:

  1. Establish the case: define customer, regulatory, operational, sustainability, and security drivers.
  2. Assess maturity: review process control, data quality, technology, competence, governance, and culture.
  3. Select critical use cases: prioritize problems where reliable data and measurable intervention exist.
  4. Design the target operating model: define roles, decision rights, interfaces, controls, and escalation.
  5. Build the data foundation: identifiers, master data, lineage, access, retention, and quality rules.
  6. Pilot safely: use a limited process, baseline performance, and predefined success criteria.
  7. Validate and assure: test software, models, interfaces, cybersecurity, usability, and failure recovery.
  8. Scale with change control: standardize successful practices while preserving local risk knowledge.
  9. Review outcomes: assess quality, safety, environmental effects, employee experience, security, and return on investment.

Investment appraisal should include total cost of ownership: implementation, integration, validation, training, licenses, cybersecurity, data stewardship, maintenance, model monitoring, and retirement. Claimed savings should be distinguished from avoided risk and from merely shifted workload.

10. Limitations and Critical Perspectives

Integration can become bureaucratic if every issue is forced into a common form. Standardization may suppress necessary professional judgment. Digital dashboards can encourage surveillance rather than learning. Sensor-based control can marginalize workers, while automated inspection may fail when products, lighting, materials, or suppliers change.

There are also epistemic limits. Historical data reflect past processes, past measurement practices, and past decisions. A model trained on accepted products may learn the biases of inspectors or the limitations of an old measurement system. Correlation does not establish causation. A high-performing classifier may identify a proxy for a defect without revealing a controllable cause.

Sustainability claims require boundaries and evidence. Reducing scrap in one plant may increase upstream environmental burdens. Data centres and connected devices consume energy and require materials. Therefore, digital transformation should itself be evaluated through life-cycle and systems thinking.

11. Emerging ISO and Quality Developments

Future quality systems are likely to address several overlapping developments:

  • stronger integration of climate-related context and interested-party expectations;
  • formal governance of artificial intelligence and automated decision systems;
  • cybersecurity and software supply-chain assurance as routine quality concerns;
  • product and process traceability through interoperable digital records;
  • expanded circular-economy, climate, and life-cycle expectations;
  • resilience to pandemics, geopolitical disruption, and infrastructure failure;
  • competence requirements for data literacy, model oversight, and cyber hygiene;
  • greater use of remote and augmented-reality audits, balanced by evidence and confidentiality controls.

Organizations should distinguish published requirements from draft standards, guidance, regulatory proposals, and market trends. Certification claims must be based on the applicable, current standard and the accredited certification arrangement where accreditation is relevant.

Chapter Summary

Integrated quality management coordinates quality, environmental performance, occupational health and safety, information security, sustainability, and organizational resilience through shared governance and process-based controls. ISO standards provide compatible structures, but each retains distinctive technical requirements.

The e-QMS creates controlled workflows, traceability, evidence, and analytics. IoT supplies operational data; automation executes defined responses; digital twins represent connected physical systems; analytics supports diagnosis and prediction; and AI may identify complex patterns. These technologies are valuable only when data are trustworthy, processes are understood, models are validated, and human accountability remains clear.

Predictive quality requires careful definitions of targets, representative data, temporal validation, monitoring for drift, and attention to false positives and false negatives. Cybersecurity and data governance protect the integrity, confidentiality, and availability of quality information. Responsible AI requires purpose limitation, transparency, human oversight, fairness, technical assurance, and accountability.

The future quality professional is therefore both a systems thinker and a critical evaluator of technology. The central question is not whether an organization is digital, but whether its integrated system produces safer, more sustainable, more reliable, and more trustworthy outcomes.

Key Terms

Integrated management system: A coordinated system combining multiple management disciplines under shared governance and processes.

e-QMS: A digital system for controlling quality processes, records, workflows, and evidence.

High-level structure: Common structural elements used by many ISO management-system standards.

Life-cycle thinking: Considering impacts and requirements across acquisition, production, use, and end-of-life.

Traceability: Ability to follow the history, application, location, or relationship of an item or record.

Data lineage: Documented origin, transformation, movement, and use of data.

Internet of Things: Networked physical devices that sense, communicate, and sometimes act on data.

Digital twin: A connected digital representation of a physical asset, process, or system.

Predictive quality: Use of data and models to anticipate future nonconformity or process deterioration.

Concept drift: Change in the relationship between model inputs and the target outcome.

Data drift: Change in the distribution or characteristics of model inputs.

Responsible AI: Governance ensuring that AI is lawful, safe, fair, secure, transparent, and accountable.

Automation bias: Excessive trust in an automated recommendation or decision.

Data governance: Policies, roles, controls, and practices governing data throughout its life cycle.

Cybersecurity: Protection of systems, networks, and data from unauthorized or harmful activity.

Model calibration: Agreement between predicted probabilities and observed event frequencies.

First-pass yield: Proportion of units completing a process without rework or repair.

Cost of poor quality: Costs associated with prevention failure, appraisal, internal failure, and external failure.

Review Questions

Short Answer Questions

  1. Why is an integrated management system more than a collection of certificates?
  2. What are the four principal layers of an integrated management architecture?
  3. Distinguish an IoT system from a digital twin.
  4. Why is data lineage important in an e-QMS?
  5. What is the difference between data drift and concept drift?

Long Answer Questions

  1. Explain how ISO 9001, ISO 14001, ISO 45001, and ISO/IEC 27001 can be integrated around organizational processes while retaining their distinctive requirements.
  2. Discuss the design and implementation principles of an e-QMS, including workflow, traceability, validation, access control, and change management.
  3. Evaluate the benefits and limitations of predictive quality using IoT data and machine-learning models.
  4. Develop a responsible-AI governance framework for an automated inspection or product-release application.
  5. Discuss how cybersecurity and sustainability should influence the design of future quality-management systems.

Analytical / Application Questions

  1. A factory has rising defects, inconsistent inspection timestamps, shared user accounts, and a proposal to deploy AI. Diagnose the organizational and technical prerequisites that should be addressed before deployment.
  2. Design a balanced scorecard for a digitally enabled production process that includes quality, safety, environmental, cybersecurity, workforce, and predictive-model indicators. Explain possible unintended incentives.
  3. Using the Northstar case, propose a validation and monitoring plan for the predictive model, including data splitting, performance measures, drift detection, human escalation, and retirement criteria.

Multiple Choice Questions with Answers

Question 1

Which statement best describes an integrated management system?

A. A single audit checklist replacing all specialist requirements

B. A coordinated system using shared governance and processes while retaining discipline-specific controls

C. A software package that automatically guarantees compliance

D. A certification issued for digital transformation

Correct Answer: B. A coordinated system using shared governance and processes while retaining discipline-specific controls

Question 2

Which ISO standard primarily addresses information-security management?

A. ISO 9001

B. ISO 14001

C. ISO/IEC 27001

D. ISO 45001

Correct Answer: C. ISO/IEC 27001

Question 3

What distinguishes a digital twin from a static three-dimensional model?

A. A digital twin must be printed before use

B. A digital twin is connected to relevant data and supports analysis or decisions

C. A digital twin contains no operational information

D. A digital twin is used only for marketing visualization

Correct Answer: B. A digital twin is connected to relevant data and supports analysis or decisions

Question 4

In predictive-quality classification, recall is calculated as:

A. TP ÷ (TP + FP)

B. TN ÷ (TN + FN)

C. TP ÷ (TP + FN)

D. FP ÷ (TP + FP)

Correct Answer: C. TP ÷ (TP + FN)

Question 5

A model trained and tested on records from the same production runs may appear overly accurate because of:

A. Data leakage

B. Network segmentation

C. Life-cycle thinking

D. Electronic signatures

Correct Answer: A. Data leakage

Question 6

Which control most directly protects the integrity of inspection records?

A. Unrestricted shared accounts

B. Version control, audit trails, and controlled authorization

C. Deleting historical records monthly

D. Allowing unauthenticated remote access

Correct Answer: B. Version control, audit trails, and controlled authorization

Question 7

A model’s input distribution changes substantially, but the relationship between inputs and outcomes is not yet known to have changed. This is primarily:

A. Data drift

B. Concept drift

C. Automation bias

D. Calibration

Correct Answer: A. Data drift

Question 8

If an inspection process finds 12 nonconforming units in a sample of 600, the observed defect proportion is:

A. 0.2%

B. 2%

C. 5%

D. 20%

Correct Answer: B. 2%

Question 9

Which is a central principle of responsible AI?

A. Allowing the model to make all decisions without appeal

B. Purpose limitation and clearly assigned human accountability

C. Removing data documentation to improve speed

D. Treating generated text as authoritative evidence

Correct Answer: B. Purpose limitation and clearly assigned human accountability

Question 10

Why should worker participation be included in digital quality transformation?

A. Workers are the only source of machine data

B. Workers provide contextual knowledge about abnormal conditions and practical controls

C. Participation eliminates the need for cybersecurity

D. Worker participation guarantees model accuracy

Correct Answer: B. Workers provide contextual knowledge about abnormal conditions and practical controls

Total Quality Management & ISO Standards
Chapter 15 of 15