In aerospace manufacturing, the QMS should contain the controlled quality system and the records needed to show that quality processes are defined, followed, reviewed, and improved. It should not be treated as a dumping ground for every production transaction. MES, ERP, PLM, supplier portals, calibration systems, and maintenance systems may all hold quality-relevant data, but the QMS usually owns the governance, quality workflows, approvals, and evidence structure.
The exact boundary is site-specific. It depends on the certified quality system, customer flow-downs, regulatory exposure, validation approach, and how legacy systems are already qualified. Replacing everything with one QMS is usually unrealistic in brownfield aerospace environments because of qualification burden, validation cost, downtime risk, integration complexity, and long equipment and program lifecycles.
What commonly belongs in the QMS
For aerospace manufacturing, the QMS commonly includes or controls:
- Quality manual and process documentation, including controlled procedures, work standards, forms, and required approvals.
- Document control and revision governance, including review, release, obsolescence, access control, and change history.
- Nonconformance management, including NCRs, dispositions, containment, rework, scrap, use-as-is decisions, and escalation paths.
- MRB workflows, where applicable, including technical review, customer approval requirements, and disposition traceability.
- CAPA and root cause workflows, including corrective actions, preventive actions, effectiveness checks, and linkage to evidence.
- Internal audit and process audit records, including findings, action tracking, and closure evidence.
- Supplier quality records, including supplier approvals, supplier nonconformances, delegated inspection controls, scorecards, and corrective action tracking.
- Training and competency records where they are part of controlled quality processes or required qualification evidence.
- Calibration and measurement system controls, if not owned by a separate calibration system, including status, due dates, out-of-tolerance handling, and affected product review.
- Risk and opportunity records tied to the quality system, especially where AS9100-based risk management is required.
- Management review inputs and outputs, including quality objectives, performance trends, audit results, customer complaints, and action items.
- Customer and regulatory quality requirements, including flow-downs that affect inspection, documentation, special processes, retention, or approvals.
What may belong elsewhere, but must connect
Many records that auditors, customers, or quality teams need are not created inside the QMS. That is normal. The important point is that ownership, linkage, and retrieval are controlled.
- MES often owns execution records: routings, operation completion, operator signoffs, inspection results, electronic travelers, as-built records, and shop-floor holds.
- ERP often owns orders, inventory, purchasing, receiving, material movements, and financial disposition of scrap or rework.
- PLM often owns engineering definition, design revisions, bills of material, drawings, models, and engineering change control.
- FAI tools or customer portals may own AS9102 First Article Inspection packages, ballooned characteristics, forms, and customer submissions.
- Maintenance or calibration systems may own asset status, preventive maintenance, gage calibration, and equipment qualification evidence.
The QMS does not have to physically store every one of these records, but it should define how they are controlled, referenced, retained, protected, and made available. Weak links between systems are a common audit and investigation problem.
What should not be forced into QMS without a clear reason
A QMS should not normally become the primary system for production scheduling, inventory control, engineering release, machine data collection, or detailed work execution. Those functions usually belong in ERP, PLM, MES, IIoT, or maintenance systems.
Forcing those functions into QMS can create duplicate records, uncontrolled manual reconciliation, poor usability for operators, and version conflicts. It can also increase validation scope and make future changes harder. If the QMS is used for execution, the organization needs clear process ownership, validated workflows, electronic signature controls where required, and a practical plan for integration with the rest of the stack.
Common failure modes
- The QMS is treated as a document repository, while actual quality decisions happen in email, spreadsheets, or meetings.
- Nonconformance, MRB, and CAPA records are not linked to part numbers, serial numbers, lots, operations, suppliers, or affected orders.
- Engineering changes in PLM are not synchronized with work instructions, inspection plans, or released procedures.
- Training records do not show that operators were qualified to the correct revision at the time of work.
- Supplier quality evidence is outside the controlled system and difficult to retrieve during customer audits or investigations.
- Audit trails exist technically but are not meaningful because users share accounts, attachments are uncontrolled, or approvals happen outside the workflow.
The practical boundary
A good aerospace QMS defines the quality system of record. It may not be the only system of record for every transaction. The defensible approach is to define which system owns each record type, how revisions are controlled, how records are linked, who can approve changes or dispositions, and how evidence is retrieved over the required retention period.
That architecture should be governed through change control and validated according to the organization’s procedures. A QMS can support AS9100-aligned operation, audit readiness, and traceability, but it does not by itself guarantee certification, customer acceptance, or regulatory outcome.