AS9100 Rev D is not just a wording refresh. It restructures the aerospace quality management system (QMS) around ISO 9001:2015 and adds aerospace-specific expectations that affect how you run operations, manage risk, and maintain evidence across brownfield systems.
Alignment with ISO 9001:2015 and High-Level Structure
AS9100 Rev D adopts the Annex SL high-level structure of ISO 9001:2015. This affects how your QMS is organized and audited:
- New clause structure (4 through 10) that changes where requirements “live,” even when the intent is similar to Rev C.
- Greater emphasis on organizational context and interested parties, which can require updated risk registers and documented assumptions.
- Knowledge management and documented information concepts replace older, more prescriptive document/control language.
Practically, many organizations had to re-map procedures, forms, and electronic workflows (QMS, MES, PLM, ERP) to the new structure, without guaranteeing better performance unless this was done thoughtfully.
Risk-Based Thinking Instead of Preventive Action
Rev D embeds risk-based thinking throughout the standard instead of treating preventive action as a separate clause:
- Risk is now explicitly required in planning, operational control, and change management.
- “Preventive action” as a standalone requirement is removed, but the underlying intent is expected to show up in how you identify and mitigate risk in processes, suppliers, and changes.
- In regulated, long-lifecycle aerospace programs, this usually means refreshing FMEAs, control plans, and supplier risk models, not just rewriting procedures.
This is often where brownfield pain shows up: legacy systems may not capture risk data consistently across design, planning, production, and MRO, so evidence of risk-based thinking can be fragmented.
Product Safety Requirements
Rev D introduces dedicated requirements for product safety:
- Formal processes to manage product safety across the lifecycle, including design, manufacturing, maintenance, and support.
- Expectations for communication of safety-related information, including alerts and potential safety issues.
- Integration of safety considerations into change control, nonconformance management, and release decisions.
This typically drives tighter linkages between engineering change, MRB/NCR workflows, and release processes in MES/ERP. It does not guarantee safety outcomes; it raises the bar on structured controls and traceable decision-making.
Counterfeit-Part Prevention
AS9100 Rev D strengthens and clarifies requirements around counterfeit-part prevention:
- Explicit requirement for a counterfeit-part prevention process, covering detection, prevention, and response.
- Greater scrutiny on traceability of parts, especially when purchasing from brokers or non-OEM sources.
- Need for documented controls in purchasing, receiving, verification, and material control, often tied into serial/lot genealogy in digital systems.
In brownfield environments, this often exposes integration gaps between purchasing (ERP), receiving inspection, and production records (MES). Rev D expects coherent, traceable evidence, not standalone spreadsheets.
Configuration Management Enhancements
Rev D maintains configuration management as a core aerospace requirement, but with more explicit expectations:
- Stronger linkage between configuration baselines, changes, and delivered product.
- Emphasis on configuration across the lifecycle, including maintenance and repair where applicable.
- Expectation that configuration status is accurate, controlled, and demonstrable through records, not tribal knowledge.
Plants with mixed PLM, MES, and paper travelers often find that Rev D drives a push toward clearer part/document revision control, and better synchronization between digital and paper-based work instructions.
Project Management and Operational Planning
Rev D adds and clarifies requirements related to project management:
- Explicit focus on managing project stages, responsibilities, interfaces, and risk.
- Alignment between contract requirements, planning (routers, travelers), and actual execution data.
- Greater expectation that complex, multi-plant or multi-supplier programs are managed with formal, documented controls, not only tribal knowledge.
This affects how you plan and monitor complex aerospace work orders and major modification programs, especially when multiple IT systems and suppliers are involved.
Awareness, Human Factors, and Ethics
Rev D builds on ISO 9001:2015 personnel requirements and adds aerospace-specific expectations:
- Increased emphasis on awareness of the importance of quality, product safety, and ethical behavior.
- Recognition of human factors in nonconformities and errors, especially in maintenance and inspection.
- Evidence of training, communication, and reinforcement, not just one-time signoffs.
For operations, this often results in updated training content, digital work instructions, and reinforcement mechanisms such as layered process audits or toolbox talks, with better records to support audits.
Special Processes, Verification, and External Providers
AS9100 Rev D clarifies requirements around:
- Control of special processes, including process qualification and periodic verification.
- Use of external providers, with more explicit oversight, performance monitoring, and risk-based controls.
- Flowdown of requirements to sub-tier suppliers and evidence that the flowdown is understood and implemented.
This usually creates additional work where supplier management is handled in ERP and quality is handled in a separate QMS or homegrown tool. Rev D does not mandate new software, but it makes weak integration and poor traceability more visible in audits.
Documented Information and Evidence
With Rev D, “documents and records” are consolidated into “documented information” following ISO 9001:2015:
- Greater flexibility in format (paper, digital, hybrid), but with higher expectations on control, access, and retention.
- Need to show clear revision control, approval, and traceability for procedures, work instructions, and records.
- In long-lifecycle aerospace programs, this interacts directly with how legacy systems, archives, and newer digital tools coexist.
Full replacement of legacy document and record systems is often unrealistic due to validation burden, historical record retention needs, and downtime risk. Many organizations instead layer controlled digital tools on top and define clear interfaces, then show auditors how the pieces fit together.
Transition and Brownfield Considerations
Moving from earlier revisions (such as Rev C) to Rev D typically requires more than re-labeling procedures:
- Re-mapping the QMS to the new clause structure and updating cross-references in procedures, forms, and electronic workflows.
- Strengthening risk, product safety, and counterfeit-part controls, with traceable evidence in NCR/CAPA, change control, and supplier management processes.
- Reviewing integration points among QMS, MES, ERP, PLM, and supplier portals so that configuration management and traceability can be demonstrated across systems.
- Updating training and awareness materials to cover Rev D expectations, especially for leadership, engineering, quality, and supply chain roles.
Because many aerospace plants operate with legacy machines and validated software, complete system replacement to “be Rev D compliant” is rarely necessary and often impractical. Instead, most organizations enhance controls, evidence, and governance on top of existing systems while maintaining validation status and minimizing disruption.
Summary
Compared to earlier revisions, AS9100 Rev D:
- Aligns with ISO 9001:2015 and its structure.
- Integrates risk-based thinking throughout the QMS.
- Adds explicit requirements for product safety and counterfeit-part prevention.
- Clarifies expectations for configuration management and project management.
- Strengthens controls over external providers and special processes.
- Raises the bar on documented information, training, human factors, and ethics.
The impact on a given plant depends heavily on current process maturity, system integration quality, and how well existing practices already align with these expectations.
