Connect981 – Content Dev

RSC Cluster: Aerospace Compliance Execution Systems for AS9100, AS9102 and Regulated Supply Chains

AS9100 vs AS9102: How Digital Compliance Architectures Support Both Standards
AS9100 and AS9102 are often discussed separately, but aerospace manufacturers do not execute them separately in real operations. One governs the broader quality management system, while the other defines how first article inspection is planned, documented, and approved. On the shop floor, in engineering release, and during customer or registrar audits, the same people, records, revisions, and product data must support both.

That is why the real design challenge is not choosing between standards. It is building a digital compliance architecture that lets documented procedures, work execution, inspection evidence, and traceable records flow through one connected system. A strong approach uses a shared operational backbone rather than a stand-alone FAI tool on one side and a disconnected quality system on the other. For broader context on that model, see this central aerospace compliance execution hub.

For teams putting this topic into daily operation, execution systems for aerospace manufacturing, supply chain and supplier execution, shop floor execution control help connect the concept to traceability, work-order reality, and audit-ready evidence.

The same operating model also depends on quality management workflows, a connected execution platform, Connect 981’s aerospace execution solutions, real aerospace execution examples, especially when decisions have to move across quality, production, suppliers, and program leadership without losing context.

In practice, this means aligning QMS workflows, document control, product configuration, production travelers, inspection records, nonconformance handling, and corrective action into a common compliance layer. A platform such as Connect981 fits into that layer by connecting ERP, PLM, MES, and quality processes so that first article work is not treated as an isolated documentation exercise.

Regulatory Context: Why AS9100 and AS9102 Must Share a Digital Backbone

How AS9100 and AS9102 differ in scope and intent

AS9100 defines the requirements for an aerospace quality management system. It governs how an organization controls documented information, plans operations, manages risk, handles providers, monitors performance, addresses nonconformity, and drives corrective action. It is enterprise-wide and process-oriented.

AS9102 is narrower but more execution-specific. It standardizes first article inspection by requiring documented verification that a part or assembly matches drawing, specification, and purchase order requirements. It focuses on product realization at a critical transition point: proving that a manufacturing process can produce conforming hardware before routine production continues.

In other words, AS9100 asks whether the organization has controlled quality processes. AS9102 asks whether a specific product realization event has been fully verified and documented. Digital architecture has to support both questions with the same underlying data.

Where the standards overlap in aerospace production reality

The overlap appears in everyday aerospace production workflows. The FAIR depends on released drawings, revision-controlled specifications, approved suppliers, calibrated measurement resources, trained personnel, and controlled records. Those are all part of the AS9100 environment. If any of those controls are weak, the FAI package may still be assembled, but the organization will struggle to defend the result during an audit or customer review.

For example, a machined flight hardware component may pass dimensional verification, yet the FAIR is still incomplete if the material certification, special process records, or design revision lineage are unclear. The first article package is therefore not just an inspection file. It is a compiled expression of the broader quality system.

Risks of treating FAI as a separate, stand-alone system

When FAI is managed in a separate spreadsheet-driven or point-tool process, several risks emerge:
- drawing revisions and characteristic definitions may drift from the current engineering release
- part, lot, and operation history may not match the production traveler
- nonconformances found during FAI may never feed into the CAPA process
- duplicate entry creates transcription errors across forms, routers, and quality records
- audit preparation becomes a manual record-reconciliation effort
The result is not only inefficiency. It is a structural traceability problem. Aerospace manufacturers need a digital backbone where FAI, production execution, and QMS records reference the same product, revision, and workflow objects.

Mapping AS9100 Clauses to Digital System Capabilities

Documented information (Clause 7.5) and controlled digital work instructions

Clause 7.5 requires organizations to control documented information so the right content is available, current, protected, and traceable. In digital terms, that means more than storing PDFs in a document repository. It means connecting controlled procedures and work instructions to execution points.

A useful system pattern is role-based delivery of revision-controlled work instructions within the production or quality workflow itself. Operators, inspectors, and engineers should see the applicable instruction, drawing revision, and supporting media at the moment of work. The system should log acknowledgement, execution time, electronic signoff, and supersession when revisions change.

For aerospace teams, this matters because an FAI completed against an outdated characteristic list or obsolete note set is not a documentation nuisance. It is evidence of broken configuration control.

Operational control (Clause 8) via workflows, inspections, and travelers

Clause 8 is where digital execution architecture becomes especially important. Operational control depends on planned workflows, process gates, inspection points, acceptance criteria, and release controls. A disconnected stack forces teams to reconstruct these controls from multiple systems and paper packets.

A shared compliance layer can orchestrate the sequence instead. Engineering release triggers a production traveler. The traveler references approved operations and required inspections. First article requirements are automatically flagged based on part status, drawing change, or process change. Inspection results, attachments, and signatures become part of the same record chain.

This architecture is stronger than simple form automation because it enforces process logic. Work cannot move forward until required evidence exists. That is how software supports compliance execution without implying that software itself guarantees certification.

Nonconformity and corrective action (Clause 10.2) in software

Clause 10.2 requires a disciplined response to nonconformity, including correction, evaluation, root cause, and action to prevent recurrence where appropriate. In many organizations, FAI findings live in one folder while corrective action records live in another. That creates a blind spot between product verification and systemic learning.

Digital architecture should let an AS9102 finding open or reference a nonconformance record directly. If repeated dimensional issues, documentation gaps, or supplier defects appear during first article, the system should route them into the organization’s established disposition and CAPA path. This creates a defensible chain from detected issue to containment to root-cause action.

For audit readiness, the important point is linkage. Auditors and customers want to see that product issues found in first article do not disappear after the FAIR is signed.

Operationalizing AS9102 FAI in a Shared Compliance Layer

Digital FAI forms, ballooned characteristics, and PLM integrations

AS9102 execution works best when the FAIR is generated from controlled product data rather than hand-built from drawings and spreadsheets. A shared compliance architecture pulls part number, drawing revision, approved BOM context, and characteristic definitions from PLM or engineering sources, then structures them into digital FAI forms.

Ballooned characteristics can be linked to actual measurement tasks, CMM outputs, photos, certificates, and operator comments. This reduces manual transcription and keeps the FAIR synchronized with the controlled design baseline. For aerospace suppliers handling frequent revision changes, that synchronization is often the difference between a clean package and a customer rejection.

Linking FAI to production travelers, NCs, and CAPA records

First article should not sit outside the traveler history. The FAIR should reference the exact manufacturing route, work order, machine or process steps where relevant, serialized or lot-based material evidence, and any deviations or concessions encountered during build. If an out-of-tolerance feature triggers an NC, the FAIR and NC should point to each other.

This is where a compliance execution layer adds value. Instead of treating the FAIR as the final document bundle, it treats FAI as an event within a larger production and quality record. Connect981 can support this pattern by connecting workflow objects across engineering, execution, and quality so teams can navigate from first article package to traveler history to corrective action without manual record hunting.

Using FAI data as a baseline for ongoing process control

AS9102 is often viewed as a one-time requirement, but digitally structured FAI data has ongoing value. The first article establishes the initial verified configuration and characteristic baseline. That baseline can then inform in-process inspection plans, control thresholds, operator guidance, and future change impact analysis.

For example, if a critical hole pattern required repeated adjustment during first article, that information should influence routine inspection frequency and process monitoring during rate production. In a mature architecture, the FAIR is not a dead-end PDF. It is a baseline dataset that continues to inform process control under the broader AS9100 system.

Reference Architectures for Unified AS9100/AS9102 Execution

Core system components: ERP, PLM, MES, QMS, and compliance layer

Most aerospace manufacturers already have several core systems in place. ERP manages orders, inventory, and purchasing. PLM governs design release and product configuration. MES or equivalent factory systems manage execution steps and resource tracking. QMS tools handle documents, audits, nonconformance, and CAPA.

The architectural problem is that these systems rarely share a complete operational context on their own. A compliance layer sits across them and coordinates the workflows, evidence capture, approvals, and traceability links needed for regulated manufacturing. It does not replace every enterprise system. It connects them around controlled execution.

Data flows from design release through first article to rate production

A practical reference flow looks like this:
1. Engineering releases a controlled design revision in PLM.
2. The compliance layer receives the revision context and determines whether a new or partial FAI is required.
3. ERP and production planning generate the applicable work order and material context.
4. MES or digital traveler workflows execute the build with required checkpoints.
5. Inspection and FAI tasks capture measured results, attachments, certifications, and signatures.
6. Any discrepancies create linked NC records and, when needed, CAPA actions.
7. Approved FAIR output becomes part of the device history or production record set and informs recurring inspection control.
The key design principle is shared identifiers and shared revision context. Without those, organizations end up with parallel records that cannot be trusted at audit time.

Example architecture using Connect981 as the compliance execution layer

In a Connect981-centered architecture, the platform acts as the process orchestration and evidence-capture layer between enterprise systems and regulated work. Engineering metadata and revision status can feed digital workflows. Production and quality steps can be executed through controlled travelers, checklists, and forms. FAI records can inherit product context rather than requiring manual re-entry. Nonconformances and corrective actions can remain linked to the originating part, operation, and FAIR.

This approach is especially useful in multi-program aerospace environments where the same organization must manage machined parts, assemblies, supplier-provided subcomponents, and customer-specific documentation requirements within one operating model.

Implementation Considerations and Common Pitfalls

Avoiding duplicate data models for FAI and production quality

One of the most common mistakes is building a special FAI data model that duplicates product, revision, and characteristic data already maintained elsewhere. This creates reconciliation work every time engineering changes occur. It also undermines confidence in which record is authoritative.

Instead, organizations should define master sources for product structure, drawing revision, supplier approval status, and quality record types. The compliance layer should reference and contextualize that data, not recreate it unnecessarily.

Ensuring traceability from AS9102 FAIRs back to AS9100 processes

Traceability must run in both directions. Teams should be able to start with a FAIR and see the approved design inputs, traveler execution, operator or inspector signoffs, attached certifications, and any associated nonconformance actions. They should also be able to start from a QMS audit trail or CAPA record and identify the affected first article or product configuration.

That bidirectional traceability is what turns a collection of records into a compliance architecture. It is also what helps organizations answer customer questions quickly without assembling ad hoc evidence packages.

Change management for quality and engineering teams

Digital architecture projects fail when they are treated as software deployments rather than operating-model changes. Quality teams may be used to completing FAIR packages after the fact. Engineering may be used to handing over static drawings without structured characteristic data. Production may still rely on local spreadsheets or paper annotations.

Implementation therefore needs governance around data ownership, workflow design, revision discipline, training, and exception handling. The goal is not to digitize old paperwork exactly as-is. The goal is to redesign how evidence is captured at the point of work.

Roadmap: Phasing in a Unified AS9100/AS9102 Digital Stack

Assessing current system gaps and paper-based touchpoints

Start by mapping where compliance evidence is created today. Identify how drawings are released, how travelers are issued, how first article packages are assembled, where inspection data lives, and how nonconformances move into corrective action. The biggest gaps usually appear at handoffs between engineering, production, and quality.

Paper signoffs, spreadsheet characteristic lists, email approvals, and shared-drive certificate storage are all indicators that the compliance chain is fragmented.

Prioritizing high-risk programs and components

Not every workflow must be digitized at once. Aerospace manufacturers usually get the fastest value by targeting high-risk products first: new program introductions, flight-critical hardware, complex assemblies, or supplier-intensive parts with demanding customer documentation requirements. These areas tend to suffer most from disconnected records and manual FAI preparation.

A phased rollout also makes it easier to validate data mappings, train users, and refine workflow logic before expanding across additional programs or facilities.

Measuring outcomes in audit readiness and defect prevention

The best success metrics are operational, not purely administrative. Useful measures include time to assemble a FAIR package, number of FAI documentation errors, cycle time from discrepancy to disposition, speed of audit evidence retrieval, and recurrence rate of first-article-detected issues in ongoing production.

When architecture is working well, teams spend less time reconstructing history and more time controlling process performance. That is the real benefit of designing AS9100 and AS9102 support together: one digital compliance backbone can improve both audit readiness and production discipline.

AS9100 and AS9102 should therefore be seen as complementary demands on the same aerospace operating system. One defines how the organization controls quality. The other tests whether those controls produce a verified product realization outcome. A unified digital architecture connects the two through shared data, executable workflows, and traceable records.
March 24, 2026
AS9145
AS9145 is an aviation, space, and defense industry standard that defines how Advanced Product Quality Planning (APQP) and the Production Part Approval Process (PPAP) are applied to aerospace products and supply chains. It is published by the International Aerospace Quality Group (IAQG) and is intended to provide a structured, phased approach to planning, validating, and controlling product realization activities.

What AS9145 covers

AS9145 commonly includes:
- A phased APQP model for aerospace programs, covering concept, design and development, process development, product and process validation, and ongoing production.
- Requirements for control plans, process flow diagrams, and PFMEAs that link risks, controls, and verification activities.
- Guidance on identifying and managing key characteristics and significant process characteristics.
- PPAP-style submission and approval expectations for production parts and assemblies, including evidence such as capability studies, inspection records, and material certifications.
- Supplier involvement, cross-functional planning, and use of common quality tools across the extended supply chain.
In operations, AS9145 typically appears as program-level quality planning templates, gated reviews, and specified deliverables that suppliers must provide before and during production. It interacts with manufacturing execution systems (MES), quality systems, and document control through artifacts such as control plans, process FMEAs, and validation records.

What AS9145 is not
- It is not a general quality management system standard like AS9100 or ISO 9001, although it is usually aligned with them.
- It is not a replacement for specific quality tools such as SPC, MSA, or 8D. Instead, it structures where and how those tools are applied within a program.
- It is not limited to any single product type. It applies to components, assemblies, and systems across aviation, space, and defense.
AS9145 in manufacturing and supply chains

Within industrial and regulated manufacturing environments, AS9145 is often used to:
- Define a common APQP framework for OEMs and suppliers on aerospace programs.
- Coordinate design, process engineering, quality, and supply chain activities through formal APQP phases and reviews.
- Drive documentation and evidence requirements that are traceable in QMS, PLM, and MES, such as control plans linked to routings and inspection plans.
- Standardize PPAP-style part approval packages for aerospace products, especially for new product introduction or significant changes.
Common confusion
- AS9145 vs. AS9100: AS9100 defines requirements for an aerospace quality management system. AS9145 focuses specifically on structured product & process quality planning and part approval within that system.
- AS9145 vs. AS9102: AS9102 covers First Article Inspection (FAI), which verifies the first production article. AS9145 covers broader APQP and PPAP activities across the entire product realization lifecycle, which may include FAI as one element.
- AS9145 vs. automotive APQP/PPAP: AS9145 adapts APQP and PPAP concepts from automotive practice but tailors terminology, expectations, and deliverables to aviation, space, and defense requirements.
Derived-from context: relationship to SPC and APQP

In the context of existing quality tools, AS9145 does not replace APQP or statistical process control (SPC). Instead, it formalizes how APQP phases are structured and where tools such as SPC, process capability studies, and measurement system analysis are expected to be applied, particularly around key characteristics and supplier planning for aerospace programs.
March 23, 2026
special processes

Core meaning

In manufacturing and regulated industries, **special processes** are processes whose resulting output **cannot be fully verified by subsequent inspection or testing**, and therefore must be controlled primarily through:

– prior qualification of the process,
– qualification of equipment and facilities,
– qualification and ongoing approval of personnel, and
– tightly controlled parameters and documentation.

The quality of the product is assured by demonstrating that the process is consistently capable, rather than by checking every characteristic of the finished item.

Common examples include:

– welding, brazing, soldering
– heat treatment
– non-destructive testing (NDT) and some surface treatments
– plating, anodizing, coating and painting
– certain composite layup and curing operations

Use in industrial and regulated environments

In regulated environments (such as aerospace, medical devices, and pharmaceuticals), special processes typically:

– require **formal procedures, work instructions, and records** that prove the process was followed as qualified,
– are often governed by **industry standards or customer specifications**, and
– are subject to **periodic requalification or reapproval** when equipment, materials, methods, or key parameters change.

Manufacturing execution systems (MES), quality systems, and ERP integrations may:

– track which operations in a routing are designated as special processes,
– enforce that only **qualified operators, certified equipment, and approved materials** are used, and
– capture **full traceability** of process parameters (e.g., temperature profiles, torque settings, lot numbers).

Boundaries and what it is not

Special processes:

– **are defined by verifiability**, not by importance or cost; an operation can be critical but not a special process if all characteristics can be fully inspected afterward.
– are **not limited to a specific industry**; the concept appears in aerospace, automotive, energy, medical, and others.
– are **not the same as critical-to-quality (CTQ) characteristics**, though CTQs often exist within special processes.

A standard machining operation with measurable dimensions is usually **not** considered a special process if all relevant features can be reliably inspected and defects can be detected without destructive testing.

Common confusion and misuse

Special processes are commonly confused with:

– **Critical or key processes**: Many organizations use “critical process” to mean any operation that strongly influences product performance or safety. A process may be critical but not “special” if its output is fully verifiable.
– **Special cause variation (SPC)**: In statistical process control, “special cause” refers to a type of variation, not to the concept of special processes.

When using the term in quality or compliance discussions, it is helpful to confirm whether the intended meaning is **“not fully verifiable by inspection”**, which aligns with how many standards, customers, and auditors use the term.

Site-context application: aerospace and high-cost waste

In aerospace and similar highly regulated sectors, special processes are tightly controlled because:

– parts may rely on **invisible attributes** (e.g., material microstructure after heat treatment, weld integrity) that cannot be checked without damaging the part,
– process failures can force **scrap or extensive rework** of high-value, previously qualified components, and
– significant **revalidation, investigation, and documentation** effort may be triggered when a special process is suspected to be out of control.

As a result, waste or rework involving special processes often has a cost impact far beyond the direct material value, due to lost qualified parts, additional testing, and schedule risk.

March 23, 2026
key characteristic

Core meaning

A **key characteristic** is a product or process feature whose variation has a significant effect on safety, fit, function, performance, reliability, or regulatory compliance. It is explicitly identified so that it can be controlled, measured, and documented with higher priority than non‑critical features.

In industrial and regulated manufacturing, key characteristics commonly refer to:

– Specific dimensions, tolerances, or geometric features
– Material properties (e.g., hardness, tensile strength)
– Process parameters (e.g., temperature, pressure, torque, cure time)
– Software or configuration attributes that affect critical behavior

Use in manufacturing workflows

In day‑to‑day operations, key characteristics are typically:

– Defined during design, process planning, or risk analysis (e.g., FMEA)
– Marked on drawings, specifications, or control plans
– Assigned tighter controls, sampling plans, and reaction plans
– Monitored in SPC systems, MES, or quality systems with prioritized alerts
– Subject to specific traceability and documentation requirements

Example: In aerospace assembly, a fastener torque range, hole diameter, or composite cure cycle temperature may be designated as key characteristics because out‑of‑tolerance values could compromise structural performance or airworthiness.

Boundaries and exclusions

A key characteristic:

– **Includes**: any feature (product or process) where small deviations can cause significant risk or nonconformance
– **Does not automatically include**: every dimension, parameter, or data point on a print or in a recipe
– Is **not the same as** general quality characteristics that have minimal impact on function (e.g., many cosmetic features)

Key characteristics are a subset of all characteristics, selected based on risk, criticality, and impact, not just engineering preference.

Common terminology and confusion

Different industries and standards use related terms such as:

– **Critical to quality (CTQ)**: often overlaps with key characteristics, especially those tied to customer or regulatory requirements.
– **Critical characteristic / safety characteristic**: in some sectors, these may be a more narrowly defined group focused specifically on safety or compliance.

In practice, organizations sometimes:

– Use these terms interchangeably
– Create internal categories (e.g., critical, major, minor characteristics) where key characteristics map to the top one or two levels

When precision matters, the internal or standard‑specific definition should be consulted to understand how key characteristics are classified and managed in that environment.

Site context: key characteristics and MES/quality systems

In MES and other manufacturing IT/OT systems, key characteristics are often:

– Configured as **priority data points** for data collection and SPC
– Linked to **specific specification limits** and validation rules
– Used to drive **targeted alerts** and **process holds** when readings approach or exceed limits
– Included in **electronic work instructions**, checklists, and digital sign‑offs

For example, to prevent high‑cost scrap in aerospace, an MES might generate alerts and holds specifically tied to key characteristics like structural dimensions, heat‑treat parameters, or software configuration revisions, rather than triggering generic alarms on every minor variation.

March 23, 2026
NDT

Core meaning

NDT (nondestructive testing) commonly refers to a family of inspection methods used to detect discontinuities, defects, or material property variations in parts, welds, structures, or assemblies **without** impairing their intended use.

In industrial and regulated manufacturing environments, NDT is used to confirm product integrity, fitness for service, and compliance with specifications and standards, while leaving the item in serviceable condition.

Typical methods in manufacturing

Common NDT methods used in factories and industrial plants include:

– **Visual testing (VT)** – direct or remote visual examination, often with magnification or borescopes.
– **Liquid penetrant testing (PT)** – dye or fluorescent liquids applied to reveal surface-breaking defects.
– **Magnetic particle testing (MT)** – magnetic fields and particles used to find surface and near-surface flaws in ferromagnetic materials.
– **Radiographic testing (RT)** – X-rays or gamma rays used to image internal features of welds, castings, and structures.
– **Ultrasonic testing (UT)** – high-frequency sound waves used to detect internal flaws, wall thickness, and bonding.
– **Eddy current testing (ET)** – electromagnetic techniques for surface and near-surface defects, often on conductive alloys.
– **Thermography and other advanced methods** – infrared, acoustic emission, phased array UT, and digital radiography, among others.

NDT may be automated, semi-automated, or fully manual, and often produces both human-readable reports and stored digital inspection records.

Use in regulated and aerospace manufacturing

In regulated industries (such as aerospace, nuclear, medical devices, and oil & gas), NDT is typically classified as a **special process**, because the quality of the result cannot be fully verified by later inspection and depends strongly on:

– Qualified procedures and validated techniques
– Calibrated equipment and controlled parameters
– Certified NDT personnel
– Traceable and reviewable records

NDT is often integrated with Manufacturing Execution Systems (MES) or quality systems to:

– Link inspection results to specific parts, lots, or serial numbers
– Enforce that required NDT processes are performed at defined steps
– Capture parameter data and images (e.g., radiographs, UT data files)
– Support electronic review, disposition, and long-term traceability

Boundaries and exclusions

NDT **includes** techniques that:

– Leave the inspected item in a condition suitable for its intended use
– Are designed to monitor material condition, integrity, or structure

NDT **does not typically include**:

– **Destructive testing** (e.g., tensile tests that break samples, sectioning welds, metallographic mounts)
– **Routine in-process measurements** that alter the part (e.g., coupons sacrificed for testing, samples removed from a batch)
– **General preventive maintenance checks** that do not use defined NDT methods (e.g., simple visual housekeeping checks)

Common confusion and alternate uses

– **NDT vs. NDE vs. NDI**:
– NDT (nondestructive testing) focuses on the act of testing for defects.
– NDE (nondestructive evaluation) is often used where quantitative assessment of material properties or remaining life is emphasized.
– NDI (nondestructive inspection) is a closely related term, often used interchangeably with NDT in aerospace and defense.

– **NDT vs. quality inspection**:
– NDT is a subset of quality inspection focused on nondestructive techniques.
– Other inspections (dimensional checks, gauging, destructive sample tests) are part of quality control but are not NDT unless they meet the nondestructive criterion and use recognized methods.

Site context: NDT as a special process

Within the site’s focus on industrial and regulated manufacturing systems, NDT is treated as a **special process** that:

– Is tightly linked to product release and certification decisions
– Requires controlled procedures, qualification, and traceable records
– Often benefits from MES or other digital systems for routing control, data capture, image and report management, and audit-ready traceability across the product lifecycle.

March 23, 2026