Do OEM-specific quality clauses override the standard AS9102 triggers?

Usually, no.

OEM-specific quality clauses do not automatically override the standard AS9102 first article triggers just because they are customer-specific. In most cases, they either:

• add requirements beyond AS9102,
• define a customer-preferred interpretation or submission method, or
• narrow when the customer expects a full, partial, or delta first article package.

Whether a clause actually changes the practical trigger for your part depends on the contractual hierarchy, the exact wording in the purchase order and flowed-down quality requirements, and whether the customer has explicitly approved an alternate approach. That is a contract interpretation and quality planning issue, not something AS9102 alone resolves.

What is generally true

AS9102 establishes the baseline framework for when first article activity is expected. Customer clauses often sit on top of that baseline. If an OEM clause is more stringent, you typically need to meet the stricter requirement. If a clause appears less stringent or inconsistent, do not assume the AS9102 trigger disappears. You need to verify which requirement governs for that program, part, and revision level.

In practice, experienced aerospace suppliers usually treat this as a hierarchy question:

• contract and purchase order requirements,
• customer-specific quality clauses and appendices,
• drawing and specification notes,
• flowdown requirements to subtier suppliers,
• internal procedures for AS9102 planning and approval.

If those sources conflict, the safe answer is not to guess. Escalate through your contract review and quality review process and get the disposition documented.

Common failure modes

• A team assumes a customer portal workflow or form format replaces the underlying AS9102 requirement. It may only change the submission method.
• A purchase order references customer quality clauses, but manufacturing plans only to the drawing revision and misses a first article trigger tied to process change, location change, or source change.
• A customer clause says partial first article is acceptable in some situations, but there is no documented rationale linking the changed characteristic set to the submitted package.
• Engineering, quality, and supplier quality read different requirement sources and reach different conclusions about whether a delta FAI is enough.
• A subtier performs work affecting fit, form, function, or verification method, but the prime supplier does not update the first article assessment or evidence trail.

What to do in a regulated brownfield environment

Do not rely on a single system field or a single document to answer this. In many plants, the relevant requirement is fragmented across ERP purchase order text, PLM specifications, QMS procedures, customer portals, and supplier quality flowdowns. That is normal in brownfield aerospace operations.

The practical control is to maintain traceable linkage between:

• the contractual source requirement,
• the part and revision affected,
• the event that may trigger first article activity,
• the decision on full, partial, or no new FAI,
• the approver and date,
• the supporting objective evidence.

This is one reason full replacement strategies often fail. Replacing ERP, MES, QMS, or customer-facing quality workflows just to simplify FAI decision logic can create more validation work, integration risk, and traceability gaps than it removes. Most organizations are better served by strengthening requirement mapping, change control, and evidence management across existing systems.

Bottom line

No, OEM-specific clauses do not automatically override standard AS9102 triggers. They may supplement them, tighten them, or in some cases define an approved customer-specific path, but you should only treat them as controlling when the contractual hierarchy and documented customer requirements clearly support that conclusion.

If the wording is ambiguous, the right next step is a documented internal review and, where needed, written customer clarification. That reduces avoidable audit exposure, supplier disputes, and rework caused by unsupported assumptions.