AS9100 Nonconformance Software: Connecting NCRs, Work Orders, Serials, and CAPA

There is one question on an Aviation, Space, and Defence Quality Management System (QMS) standard (AS9100) audit that quietly tests your whole system. The auditor points at a part and says, "Show me the full history of this nonconforming unit". Not the non-conformance report (NCR) on its own, but the whole story: which work order produced it, which serials were affected, what disposition was authorised, what corrective action followed, and how you proved it never reached a customer.

In a well-connected system, that answer takes minutes. In most real-world factories, it takes a frantic afternoon of cross-referencing across systems that were never built to talk to each other. An auditor's nightmare.

AS9100 nonconformance software is a connected system that links each non-conformance report to the work order that produced the part, the serials affected, the authorised disposition, and the corrective action that followed, so any auditor query can be answered from a single record rather than reconstructed by hand.

Why Is the Question of Nonconformance So Revealing

AS9100D treats nonconformance as far more than a form to file. Under clause 8.7, Control of Nonconforming Outputs, you have to identify and control any output that does not meet requirements so it cannot be used or delivered by mistake, then deal with it through correction, segregation, customer notification or acceptance under concession, with the responsibility and authority for each disposition clearly defined. Aerospace adds its own teeth: a "repair" or "use-as-is" disposition needs sign-off from the design-responsible organisation or someone holding delegated authority.

That is only half the obligation. Controlling the part under clause 8.7 is a separate discipline from fixing the root cause, which lives under clause 10.2, Nonconformity and corrective action. An NCR records and disposes of the unit in front of you. Corrective and Preventive Action (CAPA) asks why it happened and stops it from recurring. Auditors expect to see both and to see them linked to one another.

Layer traceability on top, and the demand grows sharper still. Identification and traceability under clause 8.5.2, together with configuration management, means you are expected to reconstruct an as-planned versus as-built record for any serial or lot an auditor selects, backed by evidence rather than recollection.

What Makes Traceability So Difficult in Practice

Here is the catch that consultancy checklists rarely mention. In most aerospace and defence suppliers, this information is split across systems that were never designed to share information. NCRs and CAPAs live in the QMS. Work orders, routings, serials, and material genealogy live in the enterprise resource planning (ERP) or manufacturing execution system (MES). The two halves were bought at different times for different reasons, and a consistent key linking an ERP lot to a QMS nonconformance often does not exist.

So, when the auditor asks for the full history, someone must stitch it together by hand: export the NCR, find the matching work order, trace the affected serials, locate the disposition approval, then pull the linked CAPA. Every manual step is a chance for a mismatch, and every mismatch is a potential finding. This also does not take into account the time wasted on manually patching information together. The gap is not a lack of data, but a lack of connection between the data you already hold in multiple locations.

What One Connected System Looks Like

The fix is not yet another silo. It is a single source of information where the relationships already exist.

Picture a nonconformance record that is linked, by design, to the work order that produced the part, the specific serials or lot involved, the disposition and who authorised it, and the CAPA that followed. Open the part details, and you see its complete history. Open the CAPA, and you see every nonconformance feeding it. Nothing has to be reconstructed, because nothing was ever separated in the first place.

This is where Kinabase fits in. As a configurable operations platform, it lets you store NCRs, work orders, serials, dispositions, and corrective actions as connected records rather than disconnected sheets or tools. Permissions govern who can authorise a disposition. Each record keeps its own history. The auditor's question stops being a stress test and becomes a quick lookup.

It sits deliberately between two extremes: tighter than a stack of spreadsheets bridging your QMS and ERP, and lighter than ripping out the production systems your team already depends on.

If reconstructing part history is costing you days you do not have, the answer may be connection rather than replacement. Explore how Kinabase works for aerospace and defence teams, or book a conversation with our team to map it to your own QMS and ERP.