22 — Quality, nonconformance and concessions

Quality work makes conformity achievable, detects departures and prevents unresolved departures from becoming invisible in delivery. Inspection is one part of that work. It cannot compensate for an ambiguous requirement, an inaccessible connection or a production method that cannot consistently produce the specified result. A useful quality system therefore begins before manufacture and continues through supplier delivery, assembly, testing and support.

For the four utility vehicles, the practical question is whether each delivered configuration meets its applicable requirements, and what authorised action follows when it does not. Vehicle 01 may contain completed work; Vehicle 02 may have affected material on order; Vehicles 03 and 04 may still allow the manufacturing method to be improved before it is used. The response must address all three situations without assuming that they share the same physical condition.

Plan the evidence before the work

Quality planning translates product and process requirements into controls. Identify characteristics needing inspection, the stage at which they can be assessed, the method and equipment, the competence required, the acceptance criteria and the record retained. Engineering supplies technical requirements; manufacturing engineering supplies the process; quality establishes the assurance arrangement with those owners. Production must be able to perform it in the actual workplace.

The cooling-module boundary illustrates why this planning is specific. Bracket location and attachment, hose connections and electrical mating require different checks. Some characteristics can be established on the prepared module, while cross-boundary joints exist only after installation in the vehicle. Supplier inspection of a radiator does not prove the integrity of a vehicle hose joint, and a complete harness certificate does not prove correct mating at the fan.

Place checks before access is lost. A hold point prevents further work until an identified release has been given. A witness arrangement provides an opportunity for an authorised observer under agreed conditions. Define the consequences of absence or delay contractually where suppliers or customers are involved; do not assume that a missed visit automatically waives inspection. Record what was actually inspected and by whom.

Sampling, complete inspection and process assurance answer different questions. Choose among them using the consequences of failure, process capability, contractual obligations and the ability to detect defects later. Four vehicles do not automatically justify inspecting every characteristic by every possible method. Equally, low volume does not make an inaccessible safety-relevant connection unimportant. The control should address the failure mechanism and the evidence needed for the decision.

Describe a departure without guessing its cause

A nonconformance is a recorded failure to satisfy an applicable requirement. The record should identify that requirement and its revision, the observed condition, the affected item or operation, and the known extent. Separate observation from explanation. “Connector cannot mate with installed harness” is an observation; “supplier fitted the wrong connector” is a causal conclusion that needs investigation.

First establish the comparison basis. An item can appear different from a current drawing while correctly matching the approved earlier configuration applicable to that vehicle. Conversely, a component can match its own drawing but form an incompatible pair at an integration boundary. Check the intended configuration before concluding either that the product is defective or that the inspection is wrong.

Use a provisional anomaly record where the requirement or configuration is not yet clear, but preserve containment while the uncertainty is resolved. A missing supplier certificate is an evidence deficiency even if the hardware later proves conforming. A failed measurement may arise from the product, method, equipment or environment. Investigation should distinguish those possibilities without deleting the original result.

Containment protects the next decision

Containment prevents unintended use, movement or delivery while the extent and disposition are established. It can include physical segregation, stock blocking, operation holds and notification to other locations. The restriction must reach the people and systems capable of moving or using the item. A red label in one bay is insufficient if a planner elsewhere can allocate the same stock as available.

For a suspect cooling connector, identify received lots, supplier work in progress, allocated kits and installed modules. Trace both mating sides. A supplier's statement that the issue concerns only its latest delivery needs reconciliation with actual receipt and installation records. Where traceability is incomplete, widen containment until evidence supports narrowing it. Record the basis for release from containment as carefully as the original hold.

Containment does not establish the permanent remedy. Sorting stock can protect tomorrow's build while leaving the manufacturing cause untouched. Stopping all four vehicles may also be unnecessarily disruptive if the issue is demonstrably restricted to a particular supplied configuration. An authorised quality decision should define the protected boundary, owner, review trigger and information needed to change it.

Disposition requires the right authority

A disposition determines what happens to the affected product. In this operating model, rework restores the specified condition; repair establishes an acceptable condition that may differ from the original definition; use as is accepts a bounded departure without corrective physical work; rejection or scrap prevents the item from entering its intended use. Programme terminology and contractual rights must be aligned before these terms control transactions.

A concrete example of contractual authority appears in the Jet Propulsion Laboratory's supplier clause QC120. It distinguishes rework from repair and reserves concurrence for particular supplier dispositions. Those are JPL subcontract provisions, not universal vehicle-programme rules. They demonstrate why supplier authority must be established from the applicable agreement rather than inferred from technical capability. JPL QC120: Nonconformance Processing and Material Review.

Engineering assesses technical acceptability and the consequences for interfaces, performance, life and support. Quality controls the case, checks completion and maintains its evidence. Production or the supplier performs authorised work. Procurement and commercial management establish contractual consequences. Customer concurrence is obtained where the agreement reserves that right; any applicable regulatory authority remains separate. A material review board can coordinate these decisions, but its meeting title does not grant powers its members do not hold.

A concession is a bounded authorisation to accept a departure under defined conditions. Identify the affected instances or lots, requirement, technical justification, limits, inspections, support consequences and acceptance authority. Avoid open-ended wording such as “acceptable for this programme” when the assessment concerns one vehicle. A delivery concession does not automatically permit future manufacture to the same departure.

A connector mismatch during build

Suppose Vehicle 01's cooling module cannot mate with the supplier harness. Production stops the affected connection operation and records the installed module identity, harness identity, applicable instructions and observed mismatch. It protects the open connectors and prevents a local adaptor from being introduced without definition. Other released work can continue if it does not conceal or compromise the investigation.

Engineering compares the supplier proposal, accepted interface baseline and delivered items. If the supplier changed the connector without approval, the issue concerns supplied conformity and contractual control. If the programme approved the change but failed to update harness procurement, the same physical mismatch exposes an internal implementation failure. If both items match their individual definitions but their interface was never reconciled, the definition itself needs correction. These causes require different recurrence actions.

Returning the module, replacing the harness, or defining a compatible adaptor are possible routes, not predetermined solutions. An adaptor would need controlled mechanical, electrical and environmental definition, installation instructions, verification and support provision. A workshop demonstration that the fan turns is insufficient to justify every required characteristic. Technical authority selects an acceptable solution; commercial authority settles the supplier obligations and cost consequences.

Vehicle 02's ordered equipment must be checked before despatch or receipt. Vehicles 03 and 04 need compatible released definitions and plans. Vehicle 01 requires its own completed repair or replacement evidence and any retest. The case can therefore contain several implementation actions under one investigation, with independent unit closure. One supplier replacement shipment cannot close every affected vehicle automatically.

A design change is a different decision

The customer's revised hot-climate and payload requirements in DOORS do not by themselves make previously conforming work defective. Establish what baseline applies, whether the revised obligation has been accepted, and which vehicles must implement it. Engineering then assesses the required solution. Commercial authority deals with changed scope and commitments. Quality ensures the resulting implementation and acceptance conditions are clear.

A nonconformance can reveal that the design needs changing, but its disposition and the permanent change remain distinct records. A concession might authorise Vehicle 01's bounded condition while a revised design is introduced on Vehicles 03 and 04. The evidence must show why that split is acceptable. Repeated concessions should trigger review of whether the baseline, supplier capability or production process is unsuitable; they must not silently create an alternative standard.

Link the disposition to the permanent change where one is required. The permanent change needs impact assessment, authorised definition and downstream implementation closure. The nonconformance needs containment, disposition and evidence that the affected product reached its authorised condition. Closing one does not prove the other complete.

Verify the remedy and prevent recurrence

Correction addresses the identified item. Corrective action addresses the cause of recurrence. Replacing a mismatched connector corrects the vehicle; establishing a reliable supplier interface-change notification and approval route may address the cause. A training action is justified only where competence contributed to the failure. It will not fix an exchange that systematically drops applicability.

Verify the completed remedy against its authorised instructions. Inspect affected neighbouring work and repeat tests invalidated by disturbance. A connector replacement can require renewed electrical checks; removal of the module may disturb hoses or mountings. The extent follows the actual intervention and engineering assessment. Preserve superseded results with their context rather than presenting them as current evidence.

Evaluate corrective-action effectiveness after there has been a meaningful opportunity for recurrence. An amended procedure and a completed briefing establish implementation, not effectiveness. Review subsequent supplier submissions, builds or exchanges for the failure mechanism. Where no further production occurs, record the limit of the available evidence and carry relevant controls into support or the next programme.

Records, systems and scale

A quality case needs durable links to requirements, definitions, supplier deliveries, orders, vehicle occurrences, physical instances, dispositions and results. SAP inventory restrictions can support containment; detailed quality-case ownership and execution evidence must be assigned explicitly. Teamcenter can provide lifecycle context in the selected architecture, while NX and Capital hold relevant authoring detail. No platform name guarantees a complete investigation or the authority to accept its conclusion.

At major defence and infrastructure scale, millions of occurrences and years of manufacture make extent assessment central. A common lot may span sites, contracts and already delivered units. Thousands of people need clear restrictions without receiving irrelevant detail. Expensive supplier contracts may reserve approval rights and impose notification duties that differ across packages. Manage those boundaries explicitly instead of imposing a single assumed concession route.

Report recurrence and escaped defects alongside case closure. A high closure rate can conceal repeated use-as-is decisions, missing implementation evidence or transfer of the problem into service. A useful quality view shows the affected population, current containment, authorised disposition, completed unit actions and unresolved acceptance consequences. Verification and acceptance then judge what that evidence establishes for the delivered configuration.