Connect981 – Content Dev

RSC Sphere: Quality, Compliance and Traceability

The Quality, Compliance and Traceability Sphere demonstrates how audit-grade credibility is built directly into execution workflows. It connects nonconformance, corrective action, inspection, traceability, and audit evidence into a continuous operational loop. The content emphasizes how quality systems must interact with live work rather than exist as parallel documentation processes. This sphere proves that compliance and execution can reinforce each other instead of competing for attention.

  • Critical Characteristic (CC)

    A Critical Characteristic (CC) is a specific product or process attribute that is identified as having a significant impact on safety, regulatory compliance, or the fit, form, or function of a part or assembly. In regulated manufacturing environments such as aerospace, defense, and medical devices, CCs are formally called out, controlled, and verified to reduce the risk of severe failures.

    What a Critical Characteristic includes

    A Critical Characteristic commonly refers to any measurable feature where an out-of-tolerance or incorrect condition could:

    • Compromise safety or airworthiness
    • Violate a regulatory, contractual, or customer requirement
    • Prevent the part from meeting required fit, form, or function
    • Cause loss of performance that is not easily detectable in service

    Examples in an industrial context include:

    • Critical dimensions and tolerances (hole diameter, wall thickness, concentricity)
    • Material or heat-treatment requirements (alloy type, hardness, temper condition)
    • Special process parameters (plating thickness, weld penetration, cure time/temperature)
    • Software or configuration items that affect control logic or safety interlocks

    Operational meaning on the shop floor

    In operations and quality systems, Critical Characteristics are typically:

    • Identified in drawings, specifications, control plans, and FMEA outputs
    • Ballooned and numbered in inspection plans and AS9102 First Article Inspection (FAI) reports
    • Tagged in MES, QMS, or PLM systems for special handling and traceability
    • Subject to enhanced inspection, measurement system analysis, and documented acceptance criteria
    • Linked to specific process controls, operator qualifications, or special process approvals

    Recording results for CCs is often required at the characteristic level, with clear traceability to the lot, work order, operator, equipment, and inspection gage used.

    Relationship to risk and compliance

    CCs are usually identified through risk-based methods such as FMEA, hazard analysis, or regulatory assessments. Once identified, they are managed through:

    • Control plans that specify how the characteristic is produced and verified
    • Documented inspection plans, sampling strategies, and acceptance criteria
    • Nonconformance and CAPA workflows when CCs are found out of specification
    • Evidence records used for audits, customer reviews, and regulatory inspections

    Common confusion

    Critical Characteristic vs. Key Characteristic (KC)

    Both terms refer to important product or process features, but they are not always interchangeable:

    • Critical Characteristic (CC): Typically tied to safety, regulatory, or functional risk. Failure can have severe consequences and often triggers stricter controls and traceability.
    • Key Characteristic (KC): Often used for features that strongly influence product performance, manufacturability, or variation control, but may not always be directly safety-related.

    Specific industries, customers, or standards may define these terms differently. It is common to find organization- or customer-specific definitions for CCs in quality manuals, procedures, or contracts.

    Connection to aerospace and AS9102

    In aerospace manufacturing, Critical Characteristics are frequently identified on engineering drawings and then carried into AS9102 First Article Inspection documentation. Each CC is ballooned, numbered as an inspection characteristic, and must have documented results. Digital FAI and MES systems often represent CCs explicitly to support traceability, inspection evidence, and audit readiness across the product lifecycle.

  • IATF

    IATF most commonly refers to the International Automotive Task Force, a global group of automotive manufacturers and related trade associations that oversees and maintains the IATF 16949 quality management system (QMS) standard for the automotive sector.

    What IATF is

    The International Automotive Task Force is a collaborative industry body that:

    • Develops and maintains the IATF 16949 automotive QMS standard
    • Defines rules for certification and oversight of certification bodies for IATF 16949
    • Provides interpretations and sanctioned guidance related to the standard
    • Coordinates with other standardization and quality organizations in the automotive industry

    In manufacturing and industrial operations, IATF most often appears in the context of quality and compliance requirements for organizations that design, manufacture, or supply automotive parts and systems.

    What IATF is not

    • IATF is not a government regulator or legal authority.
    • IATF does not itself certify organizations; certification is performed by approved certification bodies under IATF rules.
    • IATF is not the same as the standard “IATF 16949”; it is the group that owns and maintains that standard.

    Operational meaning in manufacturing

    In day-to-day automotive and component manufacturing, references to IATF typically involve:

    • Designing and operating a quality management system that meets IATF 16949 requirements
    • Coordinating audits by IATF-recognized certification bodies
    • Aligning production, quality, and supplier management processes with IATF 16949 rules and interpretations
    • Integrating QMS requirements into MES, ERP, and other manufacturing IT/OT systems for traceability and defect prevention

    Organizations may choose to implement an IATF 16949-compliant QMS and undergo third-party certification, particularly when supplying OEMs that reference IATF 16949 in their supplier requirements.

    Common confusion

    • IATF vs. IATF 16949: IATF is the task force (the organization); IATF 16949 is the QMS standard they maintain.
    • IATF vs. ISO: ISO is an international standards organization that publishes many standards. IATF 16949 is based on ISO 9001 but is owned and maintained by the International Automotive Task Force, not ISO alone.

    Context from the automotive industry

    In the automotive industry, “IATF” almost always refers to the International Automotive Task Force and its associated QMS framework. OEMs and Tier 1 suppliers frequently reference IATF 16949 requirements in their purchasing conditions, supplier quality manuals, and audit checklists, affecting how manufacturing plants configure quality processes, documentation, and electronic systems.

  • nonconformance

    Core meaning

    Nonconformance (often written as **non-conformance** or **nonconformity**) commonly refers to a documented failure of a product, process, service, or management system to meet specified requirements. These requirements may come from:

    – Internal specifications, drawings, or work instructions
    – Customer requirements or contracts
    – Regulatory or industry standards
    – Quality management system procedures

    In regulated manufacturing, a nonconformance typically triggers formal recording, evaluation, disposition, and follow-up actions.

    How nonconformance is used in operations

    In industrial and regulated environments, nonconformance is a structured quality event, not just a generic defect. It is usually managed through a defined workflow that may include:

    – **Detection and recording**: A deviation is found during incoming inspection, in-process checks, final inspection, testing, or post-delivery feedback and logged in a quality or MES/NCR system.
    – **Classification**: The issue is categorized (e.g., critical, major, minor; product vs. process vs. documentation).
    – **Containment**: Affected material, product, or documentation is identified, segregated, or placed on hold to prevent unintended use.
    – **Disposition**: A formal decision is made, such as scrap, rework, repair, use-as-is under concession/waiver, or return to supplier.
    – **Investigation**: Root causes and contributing factors are analyzed, often linking to corrective and preventive action (CAPA) processes.
    – **Documentation and traceability**: Records are retained to demonstrate control, trace impact, and show compliance during audits.

    Examples in manufacturing:
    – A machined aerospace component exceeds a critical dimensional tolerance.
    – A batch record is incomplete or signed by an unauthorized operator.
    – A software change to an MES recipe is implemented without following the approved change-control procedure.

    Boundaries and what it is not

    To avoid confusion, it is useful to distinguish nonconformance from related terms:

    – **Nonconformance vs. defect**: A defect is a specific flaw in a product or service. A nonconformance is the broader event of not meeting a requirement and may be tied to product, process, system, or documentation.
    – **Nonconformance vs. deviation**: “Deviation” often refers to a temporary, pre-approved departure from a requirement. Nonconformance usually refers to an unplanned or undesired departure discovered after it occurs.
    – **Nonconformance vs. noncompliance**: Noncompliance is generally used for failures to meet laws or regulatory obligations. Nonconformance is commonly used for failures against internal or contractual requirements, though some organizations use the terms interchangeably.
    – **Nonconformance vs. CAPA**: Nonconformance is the event; CAPA is the structured follow-up activity intended to correct causes and prevent recurrence.

    Nonconformance does **not** imply regulatory enforcement action by itself, and it is not by definition a safety incident, though it may be related to one.

    System and data perspective

    In OT/IT and quality systems, nonconformance is typically represented as a specific record type, such as a **Nonconformance Report (NCR)** or **Nonconformity record**, which may include:

    – Unique identifier and date/time stamps
    – Linkage to batches, lots, serial numbers, equipment, and operators
    – Description of requirement and how it was not met
    – Classification (severity, type, source, detection point)
    – Disposition decisions and approvals
    – Links to investigations, CAPA, and rework instructions

    MES, QMS, ERP, and PLM systems often integrate nonconformance data to support traceability, material status control, and cost-of-quality analysis.

    Site context: nonconformance in high-risk, regulated manufacturing

    In sectors such as aerospace, pharmaceuticals, and medical devices, nonconformance events are tightly controlled and highly traceable. Managing a nonconformance in these environments may:

    – Invalidate qualified parts or certified materials
    – Require engineering review, revalidation, or requalification
    – Trigger supplier notifications or customer concessions
    – Introduce schedule risk due to investigations and approvals

    Because of this, nonconformance management is a central element of quality systems and risk control in regulated, high-cost manufacturing operations.

    Common confusion and terminology variants

    Organizations and standards use slightly different terms, including:

    – **Nonconformance** and **nonconformity** (both widely used; many quality standards use “nonconformity”)
    – **Non-conformance** (hyphenated spelling)
    – **NCR (Nonconformance Report)** or **NCMR (Nonconforming Material Report)** for the record documenting the issue

    When precision matters, it is useful to:

    – Reserve **nonconformance/nonconformity** for the condition or event.
    – Use **NCR/NCMR** for the specific document or record that captures it.
    – Distinguish between product nonconformance, process nonconformance, and system/procedural nonconformance in reporting and analysis.

  • NDT

    Core meaning

    NDT (nondestructive testing) commonly refers to a family of inspection methods used to detect discontinuities, defects, or material property variations in parts, welds, structures, or assemblies **without** impairing their intended use.

    In industrial and regulated manufacturing environments, NDT is used to confirm product integrity, fitness for service, and compliance with specifications and standards, while leaving the item in serviceable condition.

    Typical methods in manufacturing

    Common NDT methods used in factories and industrial plants include:

    – **Visual testing (VT)** – direct or remote visual examination, often with magnification or borescopes.
    – **Liquid penetrant testing (PT)** – dye or fluorescent liquids applied to reveal surface-breaking defects.
    – **Magnetic particle testing (MT)** – magnetic fields and particles used to find surface and near-surface flaws in ferromagnetic materials.
    – **Radiographic testing (RT)** – X-rays or gamma rays used to image internal features of welds, castings, and structures.
    – **Ultrasonic testing (UT)** – high-frequency sound waves used to detect internal flaws, wall thickness, and bonding.
    – **Eddy current testing (ET)** – electromagnetic techniques for surface and near-surface defects, often on conductive alloys.
    – **Thermography and other advanced methods** – infrared, acoustic emission, phased array UT, and digital radiography, among others.

    NDT may be automated, semi-automated, or fully manual, and often produces both human-readable reports and stored digital inspection records.

    Use in regulated and aerospace manufacturing

    In regulated industries (such as aerospace, nuclear, medical devices, and oil & gas), NDT is typically classified as a **special process**, because the quality of the result cannot be fully verified by later inspection and depends strongly on:

    – Qualified procedures and validated techniques
    – Calibrated equipment and controlled parameters
    – Certified NDT personnel
    – Traceable and reviewable records

    NDT is often integrated with Manufacturing Execution Systems (MES) or quality systems to:

    – Link inspection results to specific parts, lots, or serial numbers
    – Enforce that required NDT processes are performed at defined steps
    – Capture parameter data and images (e.g., radiographs, UT data files)
    – Support electronic review, disposition, and long-term traceability

    Boundaries and exclusions

    NDT **includes** techniques that:

    – Leave the inspected item in a condition suitable for its intended use
    – Are designed to monitor material condition, integrity, or structure

    NDT **does not typically include**:

    – **Destructive testing** (e.g., tensile tests that break samples, sectioning welds, metallographic mounts)
    – **Routine in-process measurements** that alter the part (e.g., coupons sacrificed for testing, samples removed from a batch)
    – **General preventive maintenance checks** that do not use defined NDT methods (e.g., simple visual housekeeping checks)

    Common confusion and alternate uses

    – **NDT vs. NDE vs. NDI**:
    – NDT (nondestructive testing) focuses on the act of testing for defects.
    – NDE (nondestructive evaluation) is often used where quantitative assessment of material properties or remaining life is emphasized.
    – NDI (nondestructive inspection) is a closely related term, often used interchangeably with NDT in aerospace and defense.

    – **NDT vs. quality inspection**:
    – NDT is a subset of quality inspection focused on nondestructive techniques.
    – Other inspections (dimensional checks, gauging, destructive sample tests) are part of quality control but are not NDT unless they meet the nondestructive criterion and use recognized methods.

    Site context: NDT as a special process

    Within the site’s focus on industrial and regulated manufacturing systems, NDT is treated as a **special process** that:

    – Is tightly linked to product release and certification decisions
    – Requires controlled procedures, qualification, and traceable records
    – Often benefits from MES or other digital systems for routing control, data capture, image and report management, and audit-ready traceability across the product lifecycle.

  • role-based approval

    Core meaning

    Role-based approval is an access and control pattern in which the authority to approve an action, change, or record is granted based on a person’s assigned role rather than their individual identity. Approval rights are tied to roles (for example, Production Supervisor, QA Reviewer, Maintenance Engineer) and users inherit these rights when they are assigned to those roles.

    In industrial and regulated environments, role-based approval is commonly implemented in MES, LIMS, ERP, and quality systems to control who may:

    – Approve or reject production steps or electronic batch records
    – Approve changes to recipes, master data, or equipment status
    – Approve deviations, CAPAs, or nonconformance dispositions
    – Approve release of materials, intermediates, or finished goods

    How it works in operational systems

    In typical OT/IT and MES workflows, role-based approval:

    – **Uses defined roles:** System administrators define roles (e.g., Operator, Shift Lead, QA Manager) and associate each role with specific approval permissions.
    – **Assigns users to roles:** Individual users are linked to one or more roles via an identity and access management (IAM) mechanism, directory service, or local user management.
    – **Controls approval steps:** Workflow steps that require approval (such as sign-offs, status changes, or parameter updates) check the user’s roles before allowing the approval action.
    – **Captures traceability:** The system records the identity of the approver, their role(s), timestamp, and the object or decision being approved, supporting audit trails and investigations.

    Boundaries and what it is not

    Role-based approval:

    – **Is about authorization logic, not the workflow itself.** It defines who can approve, not the full sequence of process steps.
    – **Is distinct from person-specific approval.** Approvals are granted to roles, even though individual users are ultimately logged as approvers.
    – **Is distinct from role-based access control (RBAC), but related.** RBAC is the broader model for permissions; role-based approval is a specific use of RBAC for approval actions.
    – **Does not guarantee compliance by itself.** It is one element of a broader control framework that may also include segregation of duties, training, validation, and procedural controls.

    Use with AI and automated decision support (site context)

    When AI-generated recommendations are incorporated into MES or other manufacturing workflows, role-based approval is often used as a safeguard:

    – AI proposes parameter changes, dispositions, or next actions.
    – Users with an appropriate role (e.g., Process Engineer, QA Approver) review the AI recommendation.
    – The system enforces that only those roles can approve applying the recommendation to live production data or equipment.
    – The approval action, including the role and the underlying AI suggestion, is recorded for traceability and later review.

    This pattern allows AI to support decision-making while keeping final authority with defined human roles, which is common in regulated and safety-critical operations.

    Common confusions

    – **Role-based approval vs. electronic signature:** An electronic signature is the mechanism by which a user signs or approves (e.g., credentials, cryptographic methods). Role-based approval determines whether a user is allowed to perform that signature for a given action.
    – **Role-based approval vs. automatic enforcement:** Automatic enforcement applies decisions without human approval. Role-based approval requires a user in a permitted role to actively review and approve the action before it takes effect.

    Typical examples in manufacturing systems

    – A **QA Reviewer** role is required to approve batch record completion before product release in an MES.
    – A **Process Owner** role is required to approve changes to a validated recipe or control limit in a batch management system.
    – A **Maintenance Supervisor** role is required to approve returning equipment to service after a critical repair.

    In each case, the system checks the role, not just the username, to determine whether the approval is permitted.

  • GMP

    GMP stands for Good Manufacturing Practice. It commonly refers to a set of regulations, legally binding requirements, and supporting guidelines that govern how certain products are consistently manufactured and controlled to defined quality standards. GMP is most strongly associated with regulated industries such as pharmaceuticals, biotechnology, medical devices, food, and cosmetics.

    GMP focuses on the manufacturing process and environment rather than only on final product testing. It addresses how materials, equipment, facilities, methods, documentation, and personnel are managed so that products are fit for use, traceable, and produced in a controlled and reproducible way.

    What GMP typically covers

    While specific GMP requirements vary by industry and jurisdiction, they commonly include expectations for:

    • Organization and personnel: Roles, responsibilities, training, and qualification of staff involved in production and quality activities.
    • Premises and equipment: Design, maintenance, cleaning, and qualification of facilities, utilities, and equipment used in manufacturing and testing.
    • Documentation and records: Controlled procedures, instructions, batch records, logs, and data that provide traceable evidence of how each batch was produced and tested.
    • Materials management: Approval, receipt, storage, handling, labeling, and reconciliation of raw materials, components, intermediates, and packaging materials.
    • Production controls: Validated processes, in-process controls, line clearance, status labeling, and checks to ensure operations follow approved methods.
    • Quality control and testing: Sampling, specifications, analytical testing, stability programs, and review before release of materials and finished product.
    • Change control and deviations: Formal management of changes, deviations, nonconformances, investigations, and corrective and preventive actions (CAPA).
    • Computerized systems: Validation and control of MES, LIMS, ERP, and other GxP-relevant systems that store or process manufacturing and quality data.

    GMP in industrial and manufacturing systems

    In regulated manufacturing environments, GMP requirements influence how operations technology (OT) and information technology (IT) systems are specified, implemented, and maintained. Common impacts include:

    • Use of validated MES, batch systems, and quality systems to enforce recipe control, electronic records, and electronic signatures.
    • Configuration management, version control, and documented change control for software, master data, and procedures.
    • Audit trails, access control, and data integrity controls for production and quality records.
    • Integration of GMP-relevant data flows between shop-floor systems and enterprise systems (for example, MES to ERP or QMS) with traceability and documented interfaces.

    Regulatory context

    GMP is implemented through specific regulatory frameworks and guidance documents issued by authorities and international organizations. Examples include, without citing full text:

    • Pharmaceutical and biopharmaceutical GMP regulations in various regions.
    • Medical device quality and manufacturing regulations that incorporate GMP concepts.
    • Food and dietary supplement manufacturing regulations that define current Good Manufacturing Practice for those products.

    In practice, manufacturers often refer to “GMP” or “cGMP” as shorthand for the applicable current laws, regulations, and guidance that control how they must design and run their manufacturing and quality systems.

    Common confusion

    • GMP vs. cGMP: “cGMP” typically means “current Good Manufacturing Practice” and emphasizes that practices and interpretations evolve over time. In many organizations, the terms are used interchangeably, but regulators often stress the “current” aspect.
    • GMP vs. quality management system (QMS): A QMS is the broader management framework for quality across an organization. GMP requirements usually form a regulated subset within the overall QMS, focused on manufacturing and control of specific product types.
    • GMP vs. ISO 9001: ISO 9001 is a generic quality management standard. GMP requirements are product- and sector-specific, more prescriptive for manufacturing controls, and typically linked directly to regulatory oversight.

    Relation to the standards landscape

    Within a manufacturing standards stack, GMP requirements sit alongside other frameworks such as ISO-based quality systems, industry-specific standards, and technical or data standards. Plants in regulated sectors often run GMP-compliant processes on top of MES, ERP, and QMS platforms, with strong emphasis on validation, documented procedures, and controlled integration between systems.

  • risk-based thinking

    Risk-based thinking is a systematic approach to identifying, evaluating, and addressing risks and opportunities within processes, products, and systems. It commonly refers to integrating consideration of risk into routine planning, decision making, and improvement activities rather than treating risk assessment as a one-time or stand-alone exercise.

    In industrial and regulated manufacturing environments, risk-based thinking is used to prioritize controls, inspections, resources, and improvements according to the potential impact on safety, product quality, compliance, and business continuity. It is a foundational concept in quality management standards that follow the ISO High-Level Structure, including standards used in automotive, aerospace, and other regulated sectors.

    Key elements of risk-based thinking

    Risk-based thinking typically includes:

    • Identifying risks and opportunities related to processes, equipment, software, suppliers, people, and external factors.
    • Evaluating likelihood and impact on quality, safety, regulatory compliance, delivery, and cost.
    • Prioritizing actions so that higher-risk items receive more attention, control, and monitoring.
    • Embedding risk awareness into processes, such as change control, design reviews, maintenance planning, process validation, and supplier management.
    • Reviewing and updating risk assumptions based on nonconformities, audit findings, process data, and field performance.

    Operational meaning in manufacturing

    Operationally, risk-based thinking shows up in activities such as:

    • Defining process controls and inspection plans based on process risk levels rather than treating all steps equally.
    • Using risk criteria in engineering change control to determine required reviews, validations, and approvals.
    • Applying risk assessment when introducing new equipment, automation, MES functionality, or software changes that affect production or release decisions.
    • Prioritizing corrective and preventive actions (CAPA) and improvement projects using risk to product quality and compliance as a key factor.
    • Linking documented risk analyses to procedures, work instructions, and electronic records so that risk considerations are traceable.

    Relation to standards

    Risk-based thinking is embedded in many modern management system standards. For example, quality standards for automotive and aerospace manufacturing expect organizations to apply risk-based thinking to:

    • Context and planning of the quality management system.
    • Product and process design and development.
    • Operational control, including production, service provision, and outsourcing.
    • Performance evaluation, audits, and continual improvement.

    In these frameworks, formal methods such as FMEA, hazard analysis, and fault tree analysis can be used, but they are not the only way to implement risk-based thinking. The core requirement is that decisions and controls are demonstrably influenced by consideration of risk and opportunity.

    Common confusion

    Risk-based thinking vs. formal risk assessment: Risk-based thinking is a broader mindset and approach that may use formal tools but is not limited to them. A formal risk assessment is usually a documented, structured analysis performed at a specific point in time.

    Risk-based thinking vs. compliance-only focus: Risk-based thinking looks at risk to quality, safety, and business performance in addition to regulatory requirements, rather than focusing solely on whether a rule is met.

    Tie to the IATF 16949 / ISO context

    In standards that follow the ISO High-Level Structure, such as those used for automotive quality management, risk-based thinking is expected across planning, operation, performance evaluation, and improvement. Organizations are generally expected to demonstrate how risk considerations influence their processes, documented information, and evidence used in internal and external audits.

  • ISO/TS 16949

    ISO/TS 16949 was an international technical specification that defined quality management system (QMS) requirements for organizations in the automotive production and relevant service parts supply chain. It was based on ISO 9001 and added automotive-specific requirements for design, development, production, and service of automotive-related products.

    The specification was developed jointly by the International Organization for Standardization (ISO) and the International Automotive Task Force (IATF). It aligned multiple regional automotive quality requirements into a single, globally recognized framework for automotive manufacturers and their suppliers.

    Scope and application

    ISO/TS 16949 applied to:

    • Organizations that manufacture production or service parts for the automotive industry
    • Facilities involved in design, development, production, installation, or servicing of automotive products
    • Supply chain companies that needed to demonstrate a harmonized, ISO 9001-based QMS tailored to automotive risks and requirements

    Operationally, ISO/TS 16949 influenced how plants structured their QMS, documented processes, controlled production operations, managed nonconformities, and interacted with customer-specific automotive requirements. It also drove expectations for supplier audits, corrective actions, and ongoing performance monitoring across the extended supply chain.

    Status and relationship to IATF 16949

    ISO/TS 16949 has been superseded by IATF 16949. The IATF, which co-developed ISO/TS 16949, took full ownership and released IATF 16949 as a standalone automotive QMS standard, still built on the ISO 9001 framework but no longer published as an ISO technical specification.

    In current usage, references to ISO/TS 16949 often appear in legacy documentation, historical audit records, or long-lifecycle manufacturing programs that were originally aligned to this specification before transitioning to IATF 16949 and current ISO 9001 revisions.

    Operational relevance in manufacturing environments

    In industrial and regulated operations, ISO/TS 16949 commonly shows up in:

    • Legacy QMS documentation and procedures that were written under ISO/TS 16949 requirements
    • Supplier qualification files and historical audit reports for automotive suppliers
    • Integration points between QMS, MES, ERP, and document control systems that were originally configured to ISO/TS 16949 structures

    Plants that operated under ISO/TS 16949 typically synchronized process controls, traceability, nonconformance management, and corrective action workflows across shop-floor and quality systems, and then adapted those same structures when migrating to IATF 16949.

    Common confusion

    • ISO/TS 16949 vs IATF 16949: ISO/TS 16949 was the older ISO technical specification. IATF 16949 is the current automotive QMS standard owned and maintained by the IATF, aligned with ISO 9001 but no longer issued as an ISO/TS.
    • ISO/TS 16949 vs ISO 9001: ISO 9001 is a generic QMS standard for any industry. ISO/TS 16949 built on ISO 9001 and added automotive sector-specific requirements, including customer-specific and supply chain requirements tailored to automotive risks.