Connect981 – Content Dev

RSC Cluster: Audit and Compliance Readiness (AS9100, LPAs and Process Audits)

The Audit and Compliance Readiness Cluster focuses on turning audit preparation into continuous evidence rather than episodic panic. It explains what auditors actually expect to see across training, revision control, traceability, and execution records. The content covers internal audits, layered process audits, and AS9100 expectations using real operational examples. This cluster helps organizations stay audit-ready by design, not by scramble.

  • measurement system

    A measurement system is the complete set of elements used to generate a measurement result. It commonly includes the measuring instrument or sensor, the method of measurement, the software or data collection tools, the operator, the environment, and the procedures used to collect, calculate, record, and interpret the value.

    In manufacturing and regulated operations, the term is broader than a single gage or device. A caliper, CMM, vision system, weigh scale, temperature probe, or inline sensor may be part of a measurement system, but the system also includes how the measurement is taken, under what conditions, by whom, and how the result is stored or used.

    What it includes

    • Measurement equipment such as gages, sensors, test instruments, or inspection machines

    • Fixtures, reference standards, and calibration status

    • Methods, work instructions, and acceptance criteria

    • Operators or inspectors and their technique

    • Software, data interfaces, and recordkeeping used to capture results

    • Environmental conditions that can affect results, such as temperature, vibration, humidity, or lighting

    Operational meaning

    Measurement systems appear anywhere a process needs data to verify product conformance, monitor process performance, or support release and traceability records. Examples include in-process dimensional checks on a machining line, automated torque measurement at assembly, or environmental monitoring recorded in MES or quality systems.

    Because decisions are made from the data, the reliability of the measurement system matters. In practice, organizations often evaluate whether the system is stable, accurate enough for its intended use, and capable of producing repeatable and reproducible results. This is why the term is often discussed alongside measurement system analysis, gage R&R, calibration, and metrology.

    Common confusion

    Measurement system is often confused with measuring device or gage. A device is only one component of the full system.

    It is also commonly confused with measurement system analysis (MSA). MSA is the evaluation of a measurement system’s performance, not the measurement system itself.

    In some contexts, people use the term to mean a unit convention such as metric or imperial. That meaning exists in general language, but in manufacturing and quality contexts, measurement system usually refers to the full arrangement used to produce measurement data.

  • How should we prepare production and engineering staff for interviews?

    Preparing production and engineering staff for interviews in regulated, brownfield environments is less about “media training” and more about setting clear expectations, boundaries, and evidence standards.

    Clarify purpose and scope up front

    Before interviews, communicate:

    • Why the interviews are happening (e.g., process assessment, tool selection, root cause investigation, audit prep).
    • Scope of topics (e.g., only machining and inspection workflows, not HR or commercial topics).
    • What will be done with the information (e.g., used to map current state, inform requirements, support CAPA documentation).
    • Who will see the output (internal leadership only, external vendor, regulator, customer, etc.).

    The aim is transparency, so staff are not guessing whether they are in a performance review, an audit, or a design workshop.

    Define boundaries: confidentiality, safety, and compliance

    In regulated environments, staff must understand what they can and cannot share:

    • Export controls & technical data: Remind staff not to disclose controlled technical data, proprietary parameters, or customer-identifying details unless the interview arrangement explicitly allows it and NDAs are in place.
    • Safety and legal topics: Make clear that interviews are not a substitute for incident reporting. If safety or compliance issues surface, they should also go through established channels.
    • Confidential programs/customers: Instruct staff to use generic descriptions where needed (e.g., “military customer” instead of specific program names) unless cleared.

    Provide written guidance if external consultants or vendors are involved, so staff do not rely on memory in the moment.

    Ask for facts, not “right answers”

    A common failure mode is over-coaching people to say what management wishes were true. That undermines root cause analysis and system design. Instead, emphasize:

    • “Describe what you actually do, not what the procedure says.”
    • “If you use a workaround, say so, and explain why.”
    • “If you are unsure, say you are unsure.”

    Reassure staff that the goal is to understand the system and constraints, not to assign blame. This is especially important when discussing deviations, nonconformances, or CAPA history.

    Connect to traceability and evidence

    In regulated manufacturing, interviews should tie back to tangible evidence. Prepare staff to:

    • Reference actual records they work with (e.g., travelers, MES screens, QMS forms, logbooks, calibration certificates).
    • Explain where data lives (MES, ERP, QMS, spreadsheets, paper binders) and who updates it.
    • Describe how they prove work was done (signatures, electronic signoffs, scan events, device logs).

    Encouraging this mindset early limits vague discussion and helps external parties understand real traceability gaps, integration debt, and manual handoffs.

    Map roles across the brownfield stack

    Production and engineering staff often interact with a fragmented toolchain. Before interviews, help them outline:

    • The systems they actually touch: legacy MES screens, homegrown Access tools, PLM viewers, email-based workflows, shared drives, etc.
    • Where they feel friction: double entry between MES and ERP, manual report building, re-typing from paper into QMS, etc.
    • Dependencies on upstream/downstream functions: e.g., engineering change notices, supplier certs, inspection labs, outside processors.

    This is particularly important if interviews are part of a digital initiative, since full replacement is usually constrained by validation burden, downtime risk, and qualification of long-lived equipment. Interviewers need a realistic view of coexistence requirements, not an idealized “greenfield” picture.

    Align on known constraints and non-negotiables

    Help staff articulate the constraints that shape their choices:

    • Regulatory / customer requirements: retention periods, required signatures, inspection regimes, serialization rules.
    • Operational constraints: single qualified machine for a critical operation, limited calibration windows, batch sizes driven by furnace or autoclave capacity.
    • Change control: what it takes to change a work instruction, qualify a new software version, or adjust a process parameter.

    Interviewers should hear these explicitly. They drive why “simple” solutions or full system replacements are often not viable without extensive validation and planned downtime.

    Brief on interview logistics

    Operational realities matter. Before interviews:

    • Schedule around production: Avoid peak hours, changeovers, or critical builds when people cannot step away.
    • Clarify expected duration and whether participants should be in a control room, at a machine, or in a conference room.
    • Confirm coverage so operators or supervisors are not forced to choose between answering questions and meeting takt time or batch release.

    Where possible, communicate that candid feedback will not be held against individuals for productivity loss during the interview window.

    Give examples of the depth you expect

    To avoid shallow or overly high-level responses, provide concrete examples of the depth desired. For instance, ask staff to be ready to walk through:

    • End-to-end process for a representative part: from order release, through manufacturing steps, inspection, rework, and final acceptance.
    • Recent nonconformance or deviation: how it was detected, documented, investigated, and closed in the QMS or CAPA system.
    • Typical exception paths: rush orders, line-down events, or supplier quality issues.

    This helps interviewers uncover real root causes, manual work, and system interactions rather than an idealized process map.

    Set expectations for disagreements and gaps

    In many plants, procedures, QMS records, and actual practice do not fully align. Prepare staff by stating:

    • It is normal for engineering, quality, IT, and production to have different views of the “same” process.
    • They should flag inconsistencies (“the spec says X, but in reality we do Y because Z”).
    • Identified gaps may drive follow-up actions (e.g., procedure updates, training, system changes), but those will follow established change-control pathways.

    Making this explicit reduces the instinct to hide messy reality, which is exactly what interviewers need to see to design workable improvements.

    Explicitly avoid answer coaching

    For regulated environments, it is important not to train people to give “audit-proof” but inaccurate answers. Make clear:

    • Your role is to clarify context and boundaries, not to script answers.
    • Staff should not memorize talking points that differ from actual practice.
    • If they do not know the answer, the acceptable response is “I don’t know, but this is where we would check.”

    This is especially important if interviewers are customers, auditors, or regulators. Over-coaching can increase risk if inconsistencies are discovered.

    Link preparation to your specific initiative

    If the interviews are part of a specific project (e.g., MES replacement, new traceability solution, or CAPA effectiveness review), tailor the briefing to that context:

    • Explain which systems or processes are in scope, and which are not.
    • Clarify that any new tools must coexist with legacy systems for the foreseeable future, so participants should describe all integrations and manual touchpoints.
    • Ask staff to be explicit about validation or qualification constraints that could block or slow changes.

    This helps interviewers gather the information they need to design realistic roadmaps that respect long equipment lifecycles, change control, and limited downtime.

  • What types of documents must be controlled under AS9100?

    Under AS9100, the practical answer is: any documented information your organization needs to run the quality management system, control product realization, demonstrate conformity, or provide objective evidence should be controlled.

    So no, it is not just a small set of quality manual documents. In most aerospace manufacturing environments, document control typically extends to both internally created documents and externally provided documents that affect product, process, inspection, release, or traceability.

    What is commonly controlled

    • Quality manuals or equivalent top-level QMS documentation, if your organization maintains them

    • Policies, procedures, SOPs, and process maps

    • Work instructions, standard work, setup sheets, and operator guidance

    • Engineering drawings, models, specifications, parts lists, and technical data packages when used for production or verification

    • Inspection plans, test methods, sampling instructions, and acceptance criteria

    • Forms, templates, and checklists where version matters

    • Production routers, travelers, job packets, and manufacturing planning documents

    • Training documents tied to qualified methods or controlled processes

    • Supplier quality requirements, flow-down documents, and approved external specifications

    • Customer requirements, customer-provided specifications, and contract quality clauses when they govern execution

    • Calibration, maintenance, validation, and qualification procedures where applicable

    • Risk management procedures, change control procedures, nonconformance procedures, and corrective action procedures

    • Records retention and disposition instructions

    External documents also matter

    AS9100 document control is not limited to what you author internally. If external documents are necessary for planning, operation, inspection, or compliance to customer and regulatory requirements, those documents generally need identification, current revision control, availability at point of use, and protection from unintended use of obsolete versions.

    Examples include customer drawings, industry specifications, process standards, supplier instructions, and certain regulatory or statutory references used in execution. The exact list varies by product, contract, and process risk.

    What usually must be controlled as records

    Some documents are controlled because they instruct work. Others are controlled because they provide evidence after the fact. In practice, organizations usually control retention, access, integrity, and disposition for records such as:

    • Training records and qualification records

    • Inspection and test results

    • First article and verification records

    • Material certifications and traceability records

    • Nonconformance, concession, deviation, and corrective action records

    • Internal audit results and management review outputs

    • Supplier performance and approval records

    • Configuration and change history where applicable

    The control method for a record is not always the same as for a work instruction, but both still require governance.

    What determines the real scope

    The required scope depends on your actual operating model. A small machine shop, a complex assembly site, and an MRO environment will not control exactly the same document set. The scope is usually shaped by:

    • Product complexity and criticality

    • Customer-specific requirements and flowed-down clauses

    • Special processes and validation requirements

    • How much work is paper-based versus digital

    • Whether engineering, planning, quality, and operations are integrated or fragmented across systems

    • Retention and traceability expectations

    If a document can change how work is done, how product is accepted, or how evidence is produced, assume it needs some level of control unless your process definition clearly says otherwise.

    Brownfield reality

    In many plants, controlled documents are spread across ERP, MES, PLM, QMS, file shares, network folders, email attachments, and paper binders. That is common, but it increases revision risk and makes evidence collection harder.

    A full rip-and-replace approach is often not realistic in regulated aerospace environments. It can fail because of qualification burden, validation effort, downtime risk, integration complexity, and the need to preserve traceability across long asset and program lifecycles. In practice, many organizations improve control by defining system ownership, approved sources of truth, revision synchronization rules, and change control across existing platforms rather than replacing everything at once.

    That means document control under AS9100 is partly a process question and partly a systems governance question. If your PLM holds drawings, your MES issues work instructions, and your QMS manages procedures, the control framework has to work across all three. If those handoffs are weak, compliance risk rises even if each individual system looks acceptable on its own.

    Common failure modes

    • Operators using printed or locally saved obsolete instructions

    • Drawings updated in engineering systems but not propagated to execution systems

    • Uncontrolled spreadsheet templates used for acceptance decisions

    • Customer specifications referenced in contracts but not maintained at current revision

    • Records stored in shared drives without retention, access, or change-history discipline

    • Training content changed without corresponding approval or retraining impact assessment

    Those are not edge cases. They are common in mixed-system environments.

    Bottom line

    AS9100 does not give a short universal checklist of only a few documents that must be controlled. The safer interpretation is broader: control all documented information that is necessary to run the QMS, perform and verify the work, meet customer and applicable requirements, and preserve traceable evidence. The exact inventory is site-specific and should be defined through your processes, document hierarchy, and change-control model.

  • What is the purpose of ISA-95?

    ISA-95 is a standard that defines a common way to model, name, and exchange information between enterprise systems (such as ERP and planning) and manufacturing operations systems (such as MES, SCADA, and process control). Its primary purpose is to reduce ambiguity and custom engineering effort when integrating IT and OT in complex industrial environments.

    Core purposes of ISA-95

    • Define clear boundaries between system levels: ISA-95 describes functional levels from business planning and logistics down to process control. This helps plants decide which functions belong in ERP, MES, LIMS, SCADA, historians, and equipment controllers, instead of pushing everything into one system.
    • Standardize models and terminology: It provides reference models for production, materials, equipment, personnel, and work definitions. Using these models gives teams and vendors a shared language for data structures, interfaces, and responsibilities.
    • Guide integration between enterprise and manufacturing systems: ISA-95 focuses on the interfaces between business systems (for example, order management, MRP) and manufacturing operations management (for example, dispatching, tracking, genealogy). It helps specify what data flows where, and in which direction, without prescribing specific technologies.
    • Support interoperability in multi-vendor environments: By aligning to ISA-95 models, different MES, ERP, and automation vendors can integrate more predictably. This does not eliminate custom work, but it can reduce the degree of point-to-point, one-off interface design.
    • Enable traceability and consistent data structures: ISA-95 models for material lots, equipment, production schedules, and production records help structure traceability data in a way that is maintainable across long asset lifecycles and audits.

    What ISA-95 does not do

    • It does not guarantee compliance or audit outcomes: Using ISA-95-aligned models can support traceability and documentation, but it is not a compliance framework and does not replace regulatory or quality system requirements.
    • It does not specify technology or products: ISA-95 does not dictate which vendor, database, protocol, or architecture to use. It is a logical and information model standard, not an implementation blueprint.
    • It does not remove the need for validation or change control: In regulated environments, any ISA-95-based integration still requires requirements definition, risk assessment, testing, validation, and formal change control.

    Why ISA-95 matters in brownfield, regulated environments

    Most regulated plants run a mix of legacy ERP, MES, historians, and custom integrations. Replacing these outright is often unrealistic because of qualification burden, validation cost, downtime risk, and complex OT/IT dependencies.

    Within this reality, ISA-95 is useful because it:

    • Provides a reference for rationalizing existing systems: You can map current functions and data flows to ISA-95 models to see overlaps, gaps, and inappropriate responsibilities (for example, ERP doing dispatch logic that belongs in MES).
    • Reduces risk when adding or upgrading systems: When introducing a new MES, historian, or integration platform, ISA-95 gives a structured way to define interface requirements and avoid destabilizing validated processes.
    • Supports long-term maintainability: Standardized information models make interface documentation and change impact analysis more straightforward across many years of incremental upgrades.

    Typical ways organizations use ISA-95

    • Architecture and roadmap planning: Define which capabilities live at which level (ERP, MES, SCADA, equipment) and identify where custom logic should be refactored over time.
    • Integration specifications: Use ISA-95 objects and terminology when writing interface specifications between ERP, MES, LIMS, historians, and PLC/SCADA systems.
    • Data modeling and master data governance: Align concepts like material definitions, equipment hierarchies, and work definitions with ISA-95 so they can be shared and governed consistently across systems.
    • Vendor evaluation and RFPs: Ask vendors to describe how their products map to ISA-95 models and functions to expose gaps, overlaps, and integration assumptions early.

    In short, the purpose of ISA-95 is to provide a shared, structured framework for how enterprise and manufacturing systems should interact, so that integration in complex, regulated, and long-lived manufacturing environments is more consistent, transparent, and maintainable over time.

  • Which standard regulates batch processes?

    There is no single global standard that regulates all batch processes in the legal or compliance sense. Instead, there are widely adopted technical standards for how batch processes are modeled and controlled, plus separate regulatory frameworks that apply by industry and jurisdiction.

    Core technical standard: ISA‑88 / IEC 61512

    For most industrial batch processes, especially in pharmaceuticals, specialty chemicals, and food & beverage, the foundational technical standard is:

    • ISA‑88 (S88), also published as IEC 61512: “Batch Control”

    ISA‑88 defines:

    • A standard batch control model and terminology (procedures, operations, phases)
    • Separation of process design from equipment design
    • Recipe types (general, site, master, control recipes)
    • Equipment models (enterprise/site/area/unit, etc.)

    ISA‑88 is not a regulatory statute or binding regulation. It is a consensus engineering standard. It helps align control systems, MES, and recipe structures, and it can make validation, change control, and integration more systematic. But by itself it does not guarantee compliance or a favorable audit outcome.

    Related standards often used with batch processes

    Depending on your environment, other standards commonly coexist with ISA‑88:

    • ISA‑95: For modeling and integrating information flows between enterprise systems (ERP, PLM, QMS) and control/MES layers. Batch recipes and genealogy often sit at this interface.
    • GAMP 5 (guidance, not a standard): For approaching computerized system validation in GxP environments, including batch control and MES.
    • IEC 61508 / IEC 61511: For functional safety in process industries, sometimes relevant when batch steps involve safety instrumented functions.

    None of these are regulations in themselves; they are frameworks that can support your compliance posture if implemented and validated appropriately.

    Regulatory frameworks that apply to batch processes

    What actually regulates your batch process is typically industry- and region-specific. Examples include:

    • Pharmaceuticals / biopharma: FDA 21 CFR Parts 210/211 (drug GMP), 21 CFR Part 11 (electronic records and signatures), and EU/EMA GMP requirements. These govern how you manufacture, document, validate, and control batch production, not just which technical standard you use.
    • Medical devices: FDA 21 CFR Part 820 and ISO 13485, which may apply when device manufacturing uses batch processes.
    • Food & beverage: FDA/USDA rules in the US, EU food regulations, and HACCP-based requirements, which influence batch traceability, hygiene, and recall readiness.
    • Chemicals and other process industries: Environmental, safety, and product stewardship regulations (for example, OSHA PSM in the US, REACH in the EU) that affect how batch operations are designed and documented.

    In all of these, regulators do not usually mandate “you must use ISA‑88” but they expect clear procedures, traceability, validated control systems, and robust change control. An ISA‑88-aligned batch model often makes it easier to demonstrate these elements.

    Brownfield and coexistence considerations

    In real plants, batch processes usually sit within a brownfield stack: legacy DCS/PLC control, historical batch servers, and MES/ERP/QMS systems from multiple vendors. Introducing or tightening ISA‑88 alignment typically means:

    • Mapping existing unit operations and equipment to the ISA‑88 models without disrupting validated recipes.
    • Refactoring recipes and control logic incrementally to avoid large outages and revalidation scope.
    • Coexisting with non‑ISA‑88 legacy units where full retrofit is not economically or operationally viable.

    Attempting a full rip‑and‑replace of batch control, MES, or ERP purely “to comply with ISA‑88” is rarely justified in regulated, long‑lifecycle environments. The qualification burden, downtime risk, integration complexity, and impact on existing traceability and change histories often outweigh the benefits unless there is a broader modernization or capacity driver.

    Key takeaway

    ISA‑88 (IEC 61512) is the primary technical standard for structuring and controlling batch processes, but it does not itself regulate them. Your actual regulatory obligations come from industry‑specific GMP, safety, environmental, and quality regulations. An ISA‑88‑aligned architecture can support, but not guarantee, compliance, and must be implemented with careful validation, change control, and integration planning in existing plants.

  • Does IEC 62443 help with AS9100 or aviation authority audits?

    IEC 62443 does not provide AS9100 certification and it does not guarantee positive outcomes with aviation authorities. It is a cybersecurity standard for industrial automation and control systems, not a quality management or aviation regulatory standard. However, a well implemented IEC 62443 program can support AS9100 and aviation authority audits in several indirect but concrete ways.

    Where IEC 62443 can help AS9100 audits

    AS9100:2016 requires evidence-based risk management, configuration control, and protection of production systems and data. IEC 62443 can help you demonstrate:

    • Structured risk management for OT/ICS: Threat and risk assessments, security levels, and zone/conduit models can be mapped to AS9100 requirements on risk-based thinking and operational risk control, especially for manufacturing systems that affect product conformity.
    • Configuration management of production assets: IEC 62443 practices around hardening, patching, account management, and backup/restore can be used as objective evidence that critical manufacturing equipment and supporting IT/OT systems are controlled and protected.
    • Change control and validation impact assessments: A security program aligned to IEC 62443 usually creates clearer inventories, dependencies, and criticality rankings. That can support AS9100 change control, by making it easier to show that changes to OT/ICS are identified, assessed for risk, and verified/validated before use.
    • Business continuity for production systems: Backup, recovery, and incident handling practices required in a mature 62443 implementation can strengthen your demonstration of contingency planning and risk mitigation for loss of data or systems that impact quality or delivery.
    • Supplier and outsourced process control: If key suppliers or special process providers operate your tooling, test rigs, or data services, 62443-based requirements can be incorporated into supplier controls. That supports AS9100 clauses on external provider control, as long as the requirements and monitoring are documented.

    In practice, auditors often look favorably on a recognized framework like IEC 62443 because it shows you are not treating OT security as ad hoc. But they will still test how it is implemented and whether it ties into your QMS.

    Where IEC 62443 does not help (or is irrelevant)

    • No substitute for a QMS: IEC 62443 does not address many core AS9100 areas such as design & development, configuration management of product, FAI/PPAP, nonconformance and CAPA, or customer-specific requirements. You cannot claim AS9100 conformity by pointing to 62443.
    • Does not remove the need for process validation: Even if a control is recommended by IEC 62443 (for example, application whitelisting on test equipment), you still must validate any change that can affect product quality or compliance and maintain full traceability under your QMS.
    • Does not guarantee audit outcomes: Auditors and aviation authorities focus on whether your documented processes are followed, controlled, and effective. Misaligned or partially implemented 62443 controls can actually raise concerns if the gap between policy and practice is large.

    How IEC 62443 can support aviation authority expectations

    Aviation authorities (e.g., FAA, EASA, national authorities) are primarily interested in product safety, airworthiness, and continued operational safety. For manufacturing operations, they care that:

    • Production and test systems that affect airworthiness-related characteristics are controlled and reliable.
    • Data that supports design, manufacturing, and continued airworthiness is complete, accurate, and preserved.
    • Changes to systems that can affect product conformity or safety are identified, assessed, and controlled.

    IEC 62443 can support these expectations when it is:

    • Linked to product and process risk: You identify which OT/ICS assets can affect airworthiness-related features and prioritize 62443 controls accordingly. This mapping is key if you want to use 62443 evidence in an audit or regulatory conversation.
    • Integrated into existing QMS and SMS processes: Cybersecurity-related risks, incidents, and changes are routed through existing risk, change, CAPA, and safety management system workflows, not handled in a disconnected “IT-only” channel.
    • Under formal document and configuration control: Policies, network diagrams, zone/conduit models, and security requirements are version-controlled, reviewed, and approved in the same disciplined way as other controlled documents.

    A regulator or delegated oversight team may not ask for IEC 62443 by name, but they can use its artifacts (asset inventories, risk assessments, control matrices, incident records) as corroborating evidence that risks to critical manufacturing systems and data are being actively managed.

    Brownfield reality and implementation tradeoffs

    In aerospace manufacturing, OT environments are typically brownfield and highly heterogeneous: legacy CNC and special process equipment, multiple MES generations, custom test stands, and tightly validated integrations. This strongly shapes how useful IEC 62443 is in practice.

    • Full 62443 “from scratch” is rarely feasible: Re-architecting the entire OT network or replacing legacy systems purely to meet 62443 objectives usually collides with validation cost, extended downtime, and recertification risk. This is often unjustifiable for qualified equipment with long remaining lifecycles.
    • Incremental, risk-based adoption works better: Most plants start by using 62443 concepts (asset inventory, zoning, hardened configurations, monitored remote access) around the most critical or exposed systems, then extend coverage over time as maintenance windows and re-validation opportunities arise.
    • Coexistence with existing MES/ERP/QMS: IEC 62443 does not replace your existing systems. Instead, controls (for example, authentication, logging, backup) must be layered around them and integrated into existing change control, deviation, and CAPA processes. Misalignment between security changes and QMS workflows is a common failure mode.
    • Evidence management overhead: To be useful in AS9100 or authority audits, 62443 controls must produce durable, traceable evidence (logs, approvals, test results, exceptions). This increases documentation and coordination demands across OT, IT, quality, and engineering.

    Practical ways to use IEC 62443 as supporting evidence

    If you already follow IEC 62443 in your OT environment, you can leverage it to strengthen AS9100 and aviation authority audits by:

    • Referencing your OT/ICS cybersecurity policy and zone/conduit model as objective evidence under risk management and infrastructure control clauses.
    • Showing that change requests for OT systems (patches, configuration changes, new remote access methods) are evaluated for security impact and processed through the same formal change control as other production changes.
    • Providing asset inventories and criticality rankings that link OT systems to specific product lines, special processes, or airworthiness-relevant functions.
    • Demonstrating that backup, recovery, and incident response exercises for key OT systems are planned, executed, and documented, and that lessons learned feed CAPA processes.

    All of this depends on actual implementation quality. A paper-only or partially implemented 62443 program will not help and can create audit risk once auditors start sampling records and interviewing staff.

    Summary

    IEC 62443 is not an AS9100 or aviation regulatory standard and does not guarantee certification or specific audit outcomes. It can, however, provide a structured framework for protecting OT/ICS in a way that aligns with AS9100 and aviation authority expectations around risk management, system control, and data integrity. In brownfield aerospace environments, the most effective use of IEC 62443 is incremental and tightly integrated into existing QMS, validation, and change control practices, with realistic expectations about what can be changed on legacy equipment.

  • Supplier NCR: Managing Escaped Defects and Supplier Accountability

    Supplier NCR: Managing Escaped Defects and Supplier Accountability

    1. Introduction: What Is a Supplier NCR and Why It Matters in 2026

    A supplier NCR is not just another quality form. In aerospace manufacturing and MRO, it is the controlled record that links an external supplier’s defect to containment, investigation, disposition, and accountability across the supply chain.

    A Nonconformance Report (NCR) is a controlled quality record used to formally document, investigate, and resolve nonconformities identified during any phase of the product or service lifecycle. NCRs are important because they establish a controlled, auditable process for documenting and resolving deviations from specifications, procedures, or regulatory requirements, ensuring compliance with industry standards.

    In plain terms, non conformance is the condition. A non conformance report is the formal record. A supplier NCR is the supplier-quality version of that record, used when the identified non conformance originates with an external provider. For example, if turbine blades delivered in March 2026 arrive with blade tip thickness outside drawing tolerance by +0.005 inches, the issue is not only dimensional. It is a supplier non conformance that needs traceability, containment, supplier response, and disposition.

    Product non-conformance occurs when a product fails to meet specified requirements, standards, or expectations set by design, regulations, or customer needs. Common causes of product non-conformance include deviations from design specifications, quality standards, or customer requirements.

    This article answers the operational questions that matter: when to issue a supplier NCR, how it differs from an internal NCR, what evidence to require from the supplier, and when the issue becomes SCAR or CAPA-like escalation. Connect981 works with aerospace OEMs, Tier 1s, and MRO organizations, so the focus here is practical: escaped defects, supplier accountability, response windows, external traceability, and audit-ready execution.

    2. Supplier NCR vs Internal NCR: Key Differences

    Internal quality issues are usually contained inside one organization’s quality systems. A supplier NCR crosses company boundaries. That changes ownership, evidence, commercial exposure, and the way relevant stakeholders need to coordinate.

    • An internal NCR normally belongs to internal quality assurance, engineering, production, or maintenance teams. A supplier NCR shifts investigation and corrective measures to the external supplier, while the buyer still controls risk management and final disposition.
    • Internal NCRs usually reference internal procedures, travelers, routing records, and work instructions. Supplier NCRs must connect to purchase orders, contracts, supplier quality clauses, Certificates of Conformance, heat lots, inspection records, and sub-tier documentation.
    • Internal defects are often resolved within the factory. Supplier NCRs link quality control to procurement, warranty terms, replacement costs, approved supplier status, and supplier scorecards.
    • Supplier NCRs can affect sourcing decisions. Repeated major non conformance reports may move a supplier into development status, increase inspection requirements, or remove the supplier from the Approved Supplier List.
    • Legal consequences are different. A supplier NCR may support chargebacks, return to vendor decisions, replacement claims, or contract remedies if materials, parts, or services fail to meet agreed standards.
    • Audit readiness is broader. For AS9100 and customer requirements, especially in airline MRO contracts, external evidence must show that the organization controlled non conforming product from suppliers and protected downstream use.
    • Supplier NCRs require clearer record keeping because the traceability boundary sits outside the buyer’s facility. Lot genealogy, calibration records, raw materials history, special process evidence, and sub-tier flowdowns may all be required.
    • Regulatory compliance decreases the likelihood of defects and increases accountability in the supply chain. In practice, this means supplier NCR records must be suitable for customer audits, FAA or EASA review, and contractual documentation requirements.

    3. When to Issue a Supplier NCR: Triggers and Thresholds

    A supplier NCR should not be used for every minor blemish. It should be issued when supplier-origin non compliance meets defined procedures, acceptance criteria, or risk thresholds.

    Quality inspections typically catch flaws during incoming inspection, material handling, or on the production floor. An NCR may be issued when suppliers fail to provide materials, parts, or services that meet the agreed-upon standards, which can stem from various issues such as quality control failures or process deviations.

    Typical supplier NCR triggers include incoming inspection failures. A March 2025 batch of composite panels that fails ultrasonic inspection for delamination should open a supplier NCR if the panels do not meet specified requirements. The same applies to wrong alloy composition, missing material certification, incorrect coating, or heat treatment outside specification.

    A supplier NCR should also be opened for field-found escaped defects traced to a supplier lot. If a hydraulic actuator fails during service and the investigation points to supplier-provided seals from a defined batch, the response should not stop at replacing one unit. Addressing supplier non-conformance promptly is critical to mitigating the risk of product failure and safeguarding end-users, as it can directly cause final product non-conformances if left undetected.

    Repeated minor defects can justify a supplier NCR when they form a trend. For example, three consecutive months above 1,000 ppm for cosmetic damage, burrs, incomplete cure, or packaging damage may indicate process drift. The immediate defect may be minor, but the pattern is quality data that deserves formal review.

    Serious process non compliance found during supplier audits is another trigger. In 2024, an internal audits cycle might uncover undocumented process changes at a machining supplier, unapproved tooling, or use of a sub-tier special processor without approval. Those findings can require a supplier NCR even before defective hardware is found.

    Customer complaints should also feed the supplier NCR workflow. If a customer return, warranty claim, or in-service MRO finding maps back to a supplier part, the organization should address instances through a formal process rather than treat the complaint as an isolated fix.

    Qualitative triggers matter as much as numbers. Any safety hazards, regulatory non compliance, airworthiness concern, or critical characteristic failure should open a supplier NCR regardless of quantity. Quantitative triggers, such as three major supplier NCRs in 12 months, should be written into the QMS so authorized personnel apply them consistently.

    4. The Supplier NCR Process Step-by-Step

    The supplier ncr process follows the same core logic used in ISO 9001 and AS9100 quality management systems, but it adds supplier interaction, external evidence, and commercial accountability. Quality Management Systems (QMS) are essential for ensuring compliance with industry standards and regulations, such as ISO 9001, AS9100, and IATF 16949, which require organizations to manage nonconformities and take corrective actions.

    The nonconformance report process typically includes steps such as detection and reporting, evaluation and classification, root cause analysis, implementation of corrective actions, verification and closure, and follow-up and monitoring. A well-defined Non-Conformance Report (NCR) process is critical within quality management systems as it helps organizations track and manage issues that may arise during the production or implementation of products or services, ultimately supporting continuous improvement.

    1. Detect the issue at receiving, in-process inspection, first article inspection, MRO teardown, or post-delivery feedback. The identified non conformance must be described clearly enough for the supplier to reproduce the concern.
    2. Contain the affected material. Quarantine parts, prevent further use, apply hold tags, and bracket affected serial numbers, lot numbers, work orders, and shipments.
    3. Create the non conformance report ncr. Include supplier name, PO number, part number, serial or lot numbers, drawing revision, requirement violated, defect description, quantity affected, detection source, risk rating, and immediate containment.
    4. Notify relevant stakeholders. Supplier quality, the buyer, program manager, engineering, quality assurance, and sometimes the customer need timely visibility. Many aerospace supplier manuals require acknowledgement or containment response within 24 to 48 hours. Acro’s supplier quality manual, for example, calls for initial containment within 24 hours and longer-term actions within seven calendar days.
    5. Classify risk. Major, minor, and critical categories should reflect product quality, safety, regulatory requirements, customer requirements, and production impact.
    6. Require supplier investigation. Root cause analysis (RCA) is a structured investigation phase used to determine the underlying cause or combination of causes that led to a nonconformance, ensuring that corrective actions address the root cause to prevent recurrence.
    7. Review corrective actions and preventive actions. RCA may involve cross-functional input from various departments such as QA, engineering, production, maintenance, and regulatory affairs, and is performed using validated methodologies like the 5 Whys technique or Ishikawa diagram.
    8. Verify and close. The objective of root cause analysis is not only to resolve the immediate issue but also to identify additional preventive actions for similar processes or areas to prevent future occurrences.

    Quality Management System (QMS) software plays a crucial role in nonconformance management by standardizing workflows, automating routing and approval processes, ensuring version control, and maintaining full traceability of records, which is vital for compliance and quality assurance. In Connect981, this workflow can be digitized across work orders, suppliers, inspection records, and approval steps without replacing the existing ERP or MES.

    An aerospace technician is meticulously inspecting a precision metal component on a clean shop floor, ensuring compliance with quality management systems and specified quality standards. This routine inspection is part of a structured process aimed at addressing quality issues and maintaining product quality in the aerospace industry.

    5. Containment: When It Must Happen at Supplier Level

    Containment in a supplier NCR means immediate action to stop further non conformances from reaching production, MRO, customers, or the field. Local containment at the buyer is necessary, but it is not always enough.

    Supplier-level containment is mandatory when parts have already moved across multiple sites, serialized aerospace hardware has shipped worldwide, the supplier still has work-in-progress in production, or the issue may affect adjacent lots. The purpose is risk mitigation before the defect becomes harder to find.

    Practical supplier containment requirements should include:

    • Require same-day acknowledgement when the issue affects safety, fit, function, or delivery to a customer.
    • Require a 24 to 48 hour interim containment plan, with named owners and affected lot numbers.
    • Stop production when the failure mode suggests the process is still producing suspect parts.
    • Quarantine work-in-progress, finished goods, and stock at the supplier site.
    • Expand inspection to adjacent lots and related part numbers when raw materials, tooling, fixtures, or operators overlap.
    • Temporarily increase inspection frequency, often to 100 percent screening until the process is stable.
    • Require supporting documentation that shows quantity inspected, quantity rejected, serial numbers affected, and disposition status.
    • Confirm whether sub-tier suppliers must also place material on hold.

    A practical example is a 2025 fastener supplier placing a line on hold, quarantining lots 24-031 through 24-037, and re-inspecting 100 percent of inventory within 72 hours. AMETEK supplier requirements similarly emphasize segregating suspect product and submitting containment plans quickly, which reflects how aerospace buyers expect suppliers to control risk.

    6. What Evidence to Require from Suppliers

    Robust quality assurance depends on objective evidence, not reassurance. A supplier response that says “operator error corrected” is not enough for aerospace, MRO, or other regulated industries such as medical device manufacturing.

    The supplier NCR response should require clear evidence categories:

    • Inspection data sets, including nominal values, actual values, tolerance limits, gage IDs, CMM output, and sampling basis.
    • Photos or video of the defect, packaging condition, tooling setup, fixture location, or marking issue.
    • Batch, lot, heat, and raw materials documentation showing traceability to Certificates of Conformance and purchase requirements.
    • Calibration records for inspection equipment and production equipment used to accept the affected product.
    • Traveler sheets, routing records, operator logs, and work instruction revisions that show what process was actually followed.
    • Control charts, capability data, and SPC history for critical or key characteristics.
    • Special process evidence, including NDT, heat treatment, coating, plating, welding, and sub-tier processor approvals.
    • Updated FMEAs, control plans, training records, effective dates, and revised work instructions when process improvement is required.
    • Verification of effectiveness, such as post-correction inspection data, internal audit results, field return monitoring, or stable SPC trends.

    A standard supplier response should follow a structured process: problem statement, containment, root cause analysis, corrective actions, verification of effectiveness, and corrective and preventive actions. For major or safety-related issues, attachments should be required, not optional.

    Digital traceability expectations are high in aerospace. The NCR record should link serial numbers, lot numbers, PO lines, inspection data, supplier documents, and relevant documentation in a document management system. VIRTEX supplier requirements, for example, call for retention of material and inspection records for 10 years unless otherwise specified, which reflects common aerospace documentation practice.

    Medical device manufacturers face similar expectations for medical devices, where evidence, traceability, and documented corrective and preventive activity are required to maintain product quality and ensure quality. The industries differ, but the record discipline is familiar.

    A quality engineer is reviewing precision inspection results next to aerospace components, focusing on quality management systems and ensuring compliance with specified quality standards. The engineer analyzes data to address quality issues and implement corrective actions, contributing to continuous improvement in the supply chain.

    7. Disposition, Escalation, and When a Supplier NCR Becomes a SCAR/CAPA

    Disposition is the formal decision on what happens to the nonconforming material. Common dispositions for non-conforming items include scrap, rework/repair, return to vendor, or use as-is with concessions.

    For supplier non conformances, disposition options usually include use-as-is with engineering justification, rework by supplier, rework by buyer with chargeback, scrap, repair, downgrade, or return to supplier. The decision should be made by authorized personnel, with engineering and quality approval where required.

    Addressing product non-conformance involves identifying and documenting issues, analyzing root causes, notifying stakeholders, and implementing corrective actions to prevent recurrence. The same discipline applies to supplier NCRs, but external accountability must be explicit.

    Escalation to SCAR or CAPA-like control is appropriate when:

    • The supplier has repeated non conformances in a 6 to 12 month period.
    • A defect has critical safety, airworthiness, regulatory compliance, or customer impact.
    • Customer complaints show the defect reached the field or an MRO customer.
    • The supplier misses response windows or provides weak root cause analysis.
    • The supplier cannot show process control, training, calibration, or special process approval.
    • The same underlying cause appears across multiple part numbers or sites.
    • The buyer’s risk assessments show unacceptable recurrence or severity.
    • The issue creates wasted resources, major schedule disruption, or exposure to non compliance.

    A supplier NCR becomes a SCAR when deeper supplier corrective actions are required. SCAR usually demands management review at the supplier, formal root cause, corrective measures, preventive actions, milestone tracking, and effectiveness verification. In many organizations, the SCAR behaves like an external capa process.

    The link to internal CAPA matters. Systemic supplier issues may require internal corrective and preventive review of supplier selection, incoming inspection strategy, contract review, design tolerances, or sourcing policy. A good QMS defines escalation logic, such as three major NCRs in 12 months automatically triggering SCAR, with approval roles and deadlines documented.

    8. Integrating Supplier NCRs with Internal Audits and Customer Feedback

    Supplier NCRs should not live in isolation. They should feed internal audits, supplier reviews, risk registers, customer complaints analysis, and management review.

    During an annual 2025 AS9100 internal audit cycle, auditors should verify that supplier NCRs are issued consistently, contain required evidence, follow response windows, and close only after verification. Internal audits should also test whether corrective actions were implemented and whether recurrence was monitored.

    Audit findings can themselves trigger supplier NCRs. Missing inspection records, undocumented process changes, unapproved sub-tier outsourcing, or weak calibration control all indicate supplier control problems. Even when no defective hardware has been found, the process weakness may justify formal supplier action.

    Customer feedback closes the loop. Field returns, in-service failures, warranty claims, and airline MRO findings should be mapped back to supplier lots when possible. If the supplier origin is confirmed or strongly suspected, the supplier NCR becomes the mechanism to address quality issues and prevent recurrence.

    Trend review is essential. Teams should identify trends by supplier, defect type, response time, containment quality, recurrence rate, and cost of poor quality. This data analysis supports continuous improvement because it shows where supplier development, inspection changes, or sourcing decisions will have the most effect.

    The key components are consistency and follow-through. A supplier NCR that closes without evidence, verification, or monitoring is only administrative closure. It does not improve quality.

    9. Using Supplier NCR Data for Quality Assurance and Competitive Advantage

    Well-structured supplier NCR data supports proactive quality assurance, cost reduction, supplier development, and better sourcing decisions. The NCR process can track vendor defect rates, enforce quality standards, and hold suppliers accountable for replacement costs.

    Useful metrics include the number of supplier NCRs by supplier, defect rate by part family, average response time, containment timeliness, closure cycle time, repeat defect percentage, escaped defects versus caught-at-receipt defects, and cost of poor quality. Mature teams also track whether corrective actions remained effective after 30, 60, or 90 days.

    Supplier scorecards should include both product quality and response behavior. A supplier with a low defect count but poor containment discipline may still be a risk. A supplier with recurring defects but strong root cause analysis and verified process improvement may be a better long-term candidate for development.

    Supplier non-conformance occurs when incoming raw materials or outsourced components fail to meet established design criteria or quality standards, which can lead to operational inefficiencies and increased costs. That data should feed quarterly business reviews, dual-sourcing decisions, preferred supplier status, and targeted supplier audits.

    From 2024 through 2026, aerospace companies have increasingly used AI-assisted analytics to find patterns across ncr data: defect types, tooling, operators, materials, sub-tier suppliers, and late response behavior. The goal is not to replace engineering judgment. The goal is to surface weak signals sooner.

    Digital platforms like Connect981 centralize quality data, integrate it with ERP and MES records, and give teams a shared view across factories and suppliers. The outcome is a practical competitive advantage: fewer disruptions, stronger compliance posture, better customer satisfaction, and stronger successful project execution.

    An aerospace production team is gathered in a factory setting, reviewing components and inspection records, focusing on quality management systems and ensuring compliance with specified quality standards. They are engaged in discussions about non conformance reports and corrective actions to address quality issues and improve product quality.

    10. How Connect981 Supports Supplier NCR Workflows

    Connect981 is a unified aerospace operations platform that helps teams digitize supplier NCR workflows without forcing a full ERP or MES replacement. It connects defect logging, work execution, supplier data, document control, and traceability in one operational layer.

    Teams can configure low-code workflows for supplier NCR initiation, review, approvals, supplier communication, MRB disposition, and escalation. Digital quality checks, defect logging, parts traceability, supplier collaboration, and automated alerts help enforce response windows instead of relying on email threads and spreadsheets.

    For audit readiness, Connect981 links supplier NCR records to work orders, serial numbers, PO data, inspection results, documents, and approval history. That traceability supports AS9100, FAA, EASA, ITAR, and customer audits because the record shows what happened, who approved it, and what evidence was used.

    A practical example: a Tier 1 aerospace supplier using Connect981 to manage more than 200 supplier NCRs in 2025 could reduce average closure time from 30 days to 12 days by standardizing templates, automating notifications, and making supplier evidence visible in one workflow.

    Request a demo to see how supplier NCR workflows run in Connect981.

    11. Practical Checklist: Designing a Robust Supplier NCR Procedure

    • Define when a supplier NCR is required and when a minor issue can be handled locally.
    • Specify thresholds for ppm, repeat defects, customer impact, and safety risk.
    • Map roles for supplier quality, procurement, engineering, quality management, MRB, and program leadership.
    • Require same-day acknowledgement for critical issues and 24 to 48 hour containment response.
    • Define required evidence for inspection, traceability, calibration, process controls, and training.
    • Include clear disposition paths: scrap, rework, repair, return to vendor, and use-as-is concession.
    • Document escalation logic to SCAR, CAPA, and management review.
    • Link supplier NCRs to internal audits, customer complaints, supplier scorecards, and risk reviews.
    • Require external traceability for serial numbers, lots, batches, raw materials, and sub-tier processors.
    • Control non compliance through documented approvals, version control, and closure verification.
    • Ensure documentation is suitable for regulatory and customer audits.
    • Use routine inspections, dashboards, and follow-up monitoring to confirm corrective actions remain effective.

    12. Conclusion

    A disciplined supplier NCR process improves quality control by making supplier-origin defects visible, traceable, and actionable. It protects production, MRO operations, and customers by forcing a clear sequence: containment, evidence, root cause analysis, disposition, corrective actions, verification, and monitoring.

    The distinction matters. Internal NCRs address problems inside the organization. Supplier NCRs manage external accountability across contracts, purchase orders, supplier scorecards, and regulatory expectations. Strong procedures define response windows, evidence requirements, escalation logic, and ownership before a high-risk escape occurs.

    As aerospace and MRO supply chains become more complex through 2030, supplier non conformance management will only become more important. Digitalization with platforms like Connect981 helps teams move beyond spreadsheets and email into a connected, audit-ready supplier NCR process that supports compliance, supplier collaboration, and reliable execution.

  • Why do many aerospace customers require ISO 9001 or AS9100?

    Many aerospace customers require ISO 9001 or AS9100 because these standards provide a common, auditable framework for how a supplier manages quality and risk. Customers are not buying the certificate itself; they are reducing risk in their supply chain by insisting on a baseline level of process control and governance.

    Key reasons aerospace customers insist on ISO 9001 / AS9100

    • Risk reduction in a safety-critical domain
      Flight safety and mission success depend on parts and services that perform as specified, often for decades. ISO 9001 and AS9100 require documented processes, structured risk management, and controls that lower the probability of systemic quality failures, escapes, and configuration errors.
    • Standardized expectations for quality management
      Tier 1s and OEMs source from hundreds or thousands of suppliers worldwide. Requiring ISO 9001 or AS9100 means they do not have to invent a unique quality management framework for each supplier. They can map their own procedures, audits, and scorecards to a widely understood standard.
    • Easier supplier approval and ongoing oversight
      When a supplier is certified by a recognized body, customers can leverage that certification as one input to their supplier approval and surveillance process. It does not replace customer audits, but it can shorten initial qualification, focus audits on higher-risk areas, and reduce repeated basic checks.
    • Alignment with regulatory and customer audit expectations
      Many aerospace regulators, primes, and defense customers expect evidence of a controlled quality management system. AS9100 in particular is designed for aerospace and is deeply embedded in customer audit checklists, procedures, and contract language.
    • Improved traceability and configuration control
      Aerospace programs require strong document control, change management, and traceability. AS9100 extends ISO 9001 with explicit requirements around configuration management, product safety, and risk that are directly relevant to long-life aerospace hardware and MRO work.
    • Evidence for due diligence and liability management
      When something goes wrong, customers must show they used reasonable care in supplier selection and oversight. Requiring ISO 9001 or AS9100 is part of that evidence: it shows that suppliers are at least operating under a recognized quality framework with regular third-party audits.

    Why AS9100 is often preferred over ISO 9001 in aerospace

    • Aerospace-specific additions
      AS9100 builds on ISO 9001 and adds requirements specific to aviation, space, and defense, including configuration management, product safety, counterfeit-part controls, and more rigorous risk management.
    • Integration with other aerospace standards
      AS9100-certified organizations are generally better aligned with related aerospace requirements such as AS9102 for First Article Inspection, because the underlying disciplines (document control, records, inspection planning, NCR/CAPA) are already formalized.
    • Recognition in aerospace supply chains
      Many primes and large Tier 1s state AS9100 explicitly in supplier requirements or flowdowns. ISO 9001 alone is sometimes accepted for lower-risk items or services, but AS9100 is often expected for flight hardware and critical processes.

    What ISO 9001 / AS9100 does not guarantee

    • No guarantee of defect-free product
      Certification means a system is in place and audited; it does not mean zero defects. Customers still rely on incoming inspection, process audits, FAI/AS9102, and performance data to control risk.
    • No direct compliance or regulatory guarantee
      Having ISO 9001 or AS9100 does not guarantee regulatory compliance, airworthiness approval, or positive audit outcomes. It is one component of a broader compliance and certification landscape.
    • No substitute for robust integration or data quality
      In brownfield environments with mixed MES, ERP, PLM, and QMS systems, certification alone does not resolve integration gaps, poor data discipline, or validation issues. Those remain local implementation and governance challenges.

    Implications for brownfield, long-lifecycle operations

    In established aerospace plants, ISO 9001 or AS9100 requirements must coexist with legacy equipment, homegrown systems, and long-qualified processes. Full replacement of QMS, MES, or ERP tools purely to “align to the standard” is rarely practical because of:

    • Qualification and validation burden for new software and processes
    • Downtime risk when changing systems on critical production lines
    • Complex integrations across existing PLM, ERP, MES, and QMS platforms
    • Traceability, configuration control, and change-control constraints for long-life programs

    In practice, many organizations achieve or maintain ISO 9001 / AS9100 by tightening procedures, records, and controls around their existing toolset rather than wholesale replacement. Customers typically care more about the effectiveness and evidence of your quality system than about which specific software you run, as long as requirements are met and can be demonstrated during audits.

  • What happens if we change our scope after certification?

    Changing the scope after certification is common, but it is not an administrative detail. It usually triggers formal review and, in many cases, additional audit activity from your certification body. How disruptive this is depends on how large the scope change is and how well your change control, validation, and documentation are managed.

    What “scope change” usually means

    Scope changes that matter to a certification body typically include:

    • Adding or removing product families or services covered by the certificate.
    • Adding, closing, or relocating manufacturing sites or key process areas.
    • Introducing new regulated processes (e.g., special processes, cleanroom steps, sterilization, complex software control of production).
    • Major changes to supporting systems that are part of the certified system (e.g., new MES, QMS, ERP modules that affect quality records or release decisions).

    Typical consequences with the certification body

    In most schemes (ISO 9001, 13485, AS9100, IATF 16949, etc.), you should expect:

    • Mandatory notification: You are generally required by your contract with the certification body to inform them about significant scope changes.
    • Scope review: The certification body will assess whether the existing scope statement still reflects reality and whether the current audit program is adequate.
    • Audit adjustment: They may require a special audit, an extension audit, or increased time during the next surveillance/recertification audit.
    • Updated certificate: If they accept the new scope, they will reissue the certificate with an updated scope statement and possibly different site listings.
    • Risk of limitations or suspension: If the change is implemented without adequate controls, validation, or documentation, they can limit the scope, issue nonconformities, or in serious cases suspend or withdraw the certificate.

    Internal work you should expect to do

    Beyond the external audit aspects, a scope change normally requires disciplined internal work:

    • Change control: Raise and approve formal change requests covering processes, equipment, IT systems, and documentation affected by the new scope.
    • Risk assessment: Update risk analyses (e.g., FMEA, process risk reviews) to reflect new products, processes, or sites.
    • Process & documentation updates: Update procedures, work instructions, forms, control plans, and training materials. Ensure obsolete versions are properly controlled.
    • Validation & qualification: Plan and document process validation, software validation, equipment qualification, and data migration checks where relevant.
    • Training & competency: Train operators, engineers, and support functions and retain training and competency records.
    • KPIs & management review: Update metrics and include the scope change, associated risks, and performance impacts in management review.

    Brownfield and system coexistence implications

    In existing plants with mixed legacy and new systems, scope expansion often means:

    • More interfaces: Adding a new line, site, or product may force new integrations between MES, ERP, QMS, PLM, and data historians. These integrations must be controlled and, where applicable, validated.
    • Partial coverage: You may end up with some products or lines under the certified scope and others outside it. You must keep this boundary clear in documentation, routing, and system configuration.
    • Lifecycle constraints: Fully replacing legacy systems purely to align with a new scope is rarely practical in regulated or aerospace-grade environments due to qualification, downtime, and integration risks. Incremental extension and coexistence tend to be more realistic.
    • Traceability challenges: Expanded scope often demands consistent traceability and records across old and new systems. Evidence gaps between systems are a common audit finding if not planned carefully.

    Tradeoffs and risks

    Before changing scope, leadership should understand the tradeoffs:

    • Business benefit vs. audit exposure: Expanded scope can win business or align certificates with actual operations, but it increases what auditors can examine and where they can raise findings.
    • Speed vs. robustness: Fast expansion without mature change control, validation, and training creates a high risk of nonconformities and potentially scope limitations.
    • Uniformity vs. flexibility: Keeping one broad scope across multiple plants and product families simplifies messaging but can hide local weaknesses and increase system complexity. A narrower or staged scope may be safer for immature sites.

    What happens if you do nothing

    If you change your real operational scope but do not update your certification:

    • Your certificate may no longer accurately describe what you do, which auditors and customers can treat as a serious issue.
    • Auditors can raise nonconformities for misalignment between the certificate scope, documented scope, and actual operations.
    • In the worst case, if misrepresentation is seen as deliberate, the certification body can suspend or withdraw the certificate.

    Practical steps when planning a scope change

    To reduce risk:

    • Engage your certification body early, describe the planned change, and ask what level of audit activity they expect.
    • Map which processes, sites, IT systems, and records are newly in-scope and verify that they meet your existing system standards.
    • Ensure validation, qualification, and data integrity activities are complete before presenting the new scope to auditors.
    • Keep clear evidence: change records, risk assessments, validation reports, training records, and updated process maps.

    Net result: you can change your scope after certification, but it should be treated as a controlled change with audit implications, not as a simple wording update.