NATO AQAP 2110 - Quality Assurance Requirements for Design, Development, and Production
5.4 Operation – NATO AQAP 2110 - Quality Assurance Requirements for Design, Development, and Production

NATO AQAP 2110 - Quality Assurance Requirements for Design, Development, and Production 5.4.1.1: 5.4.1.1 Submit an acceptable contract Quality Plan with a requirement and solution compliance matrix before work starts

The Supplier submits an acceptable Quality Plan addressing the contract to the GQAR or Acquirer within an agreed timescale but before work starts (for example at the kick-off meeting for the project or contract, or when the contract or order says), as a clearly identified document or part of one prepared under the contract. The plan documents the contract-specific QMS arrangements (referring to the company-wide system where applicable), the planning of product realisation (product quality requirements, resources, verification, validation, monitoring, inspection and test activities and acceptance criteria, and arrangements for work at external locations), and a matrix tracing each contract requirement to the solution that meets it, justifying how every requirement is fulfilled (which may follow the first issue as an annex within an agreed time). The GQAR or Acquirer may reject plans and revisions; AQAP-2105 sets the content of a deliverable Quality Plan where the contract calls it up. SRD.1: the plan may sit inside the project management plan and costs the Acquirer nothing; AQAP-2105 is invoked when specific plan content is needed, and the compliance matrix may live in a requirements tool. SRD.2: AS9100D requires planning but no deliverable plan. Base clause: ISO 9001:2015 8.1 (planning), with AQAP-2105 for deliverable plans.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in 5.4 Operation – NATO AQAP 2110 - Quality Assurance Requirements for Design, Development, and Production

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.