What data should be integrated to support AS9100 traceability requirements?

AS9100 does not prescribe a single data model or system, but auditors will expect that you can reliably reconstruct what was built, with what, by whom, when, under which controls, and with which results. In practice, this requires integrating a defined set of core data across your existing ERP, MES, PLM, QMS, and supplier systems.

1. Product and configuration data

This data connects requirements to what was actually produced.

• Part numbers and revisions at each BOM level
• Serialized vs lot-controlled part definitions
• Engineering BOM and manufacturing BOM, including alternates and substitutions
• Configuration identifiers (block, dash numbers, effectivity ranges, aircraft/tail number where applicable)
• Approved deviation / concession records that impact configuration
• Applicable specifications, drawings, standards, and controlled document revisions

In brownfield environments this usually means mapping PLM/engineering data (drawings, EBOM, specs) to ERP item masters and routings, then exposing it in MES or digital travelers. Weak or manual mapping here is a common traceability failure mode.

2. Work order and routing execution data

This data provides the as-built process history.

• Work order identifiers, including parent/child WO relationships
• Routings and operation steps, including required sequences and key characteristics
• Planned vs actual operation start/finish timestamps
• Operator and inspector IDs or badges for each operation requiring signoff
• Work centers, machines, and cells where work was performed
• Process parameters that must be recorded (e.g., torque, temperature, cure time, pressures) where required by plan or specification
• Digital traveler or paper traveler identifiers to tie physical records to system data

For AS9100 traceability, it is not enough for this data to exist; it must be uniquely linked to specific work orders, serial numbers, and revision levels, with audit trails that show who changed what and when.

3. Material and component genealogy data

Genealogy links finished units back to materials and components, including suppliers.

• Raw material heat/lot numbers and certificates of conformance (CoC)
• Special material attributes (e.g., alloy, temper, batch, expiration date)
• Serial or lot numbers of purchased components assembled into each higher-level part
• Supplier identifiers and PO numbers for traceable items
• Receiving inspection results and release status (e.g., accepted, conditional, MRB)
• Material issue and return transactions from stores to work order or operation

Practically, this means integrating ERP inventory and purchasing data with MES genealogy so you can answer: “This shipped serial number contains which lot/serials from which suppliers, tied to which CoCs?” Lack of a consistent key between ERP lots and MES consumption records is a common integration gap.

4. Process and special process data

Special processes are a focus area for AS9100 and customer audits.

• Identification of operations classified as special processes
• Process parameters required by specification (e.g., oven profiles, plating baths, weld parameters)
• Records of process qualification (e.g., NADCAP approvals) and expiry dates
• Calibration status of instruments used to control or monitor the process
• Sub-tier processor data (supplier, PO, job numbers, certs) for outsourced special processes

This data often resides partially in QMS, partially in standalone systems (e.g., oven chart recorders, plating logs), and partially on paper. Integrating at least the identifiers and references (job number, batch ID, chart ID) into your core traceability model is important so you can locate the underlying evidence quickly.

5. Inspection, test, and measurement data

Inspection and test evidence links requirements and risk controls to results.

• In-process and final inspection records tied to operation, work order, and serial/lot
• AS9102 first article inspection (FAI) records and ballooned characteristic mappings where required
• Key characteristic and critical feature measurement results
• Functional test results (e.g., pass/fail, measured values, test sequence IDs)
• Gage IDs and calibration status for instruments used
• Sampling plans and acceptance criteria references (linked to controlled documents, not duplicated)

Integration often requires linking QMS or FAI tools, standalone test rigs, and SPC systems back to work orders and serials in MES/ERP. Failure modes include test systems that only store local CSV files with no unique linkage to serial/lot, which weakens traceability.

6. Nonconformance, MRB, and corrective action data

AS9100 expects nonconformity and corrective action to be traceable and connected to product history.

• NCR records tied to specific work orders, serials/lots, and operations
• MRB decisions (use-as-is, repair, scrap, rework) and authorized signatories
• Rework instructions and additional inspection/test requirements
• Concession/deviation numbers and their effectivity
• CAPA records when systemic issues are identified

In many brownfield environments, NCRs live in a QMS and work orders live in ERP/MES. At minimum, you need reliable cross-references (e.g., NCR number on the work order and work order/serial on the NCR) plus consistent master data so reports and audits can traverse both directions.

7. Equipment, tooling, and calibration data

While often managed in separate maintenance or calibration systems, some elements should be integrated into the traceability chain.

• Machine IDs and work centers associated with operations and work orders
• Tooling IDs for critical or unique tools, fixtures, or jigs
• Calibration status and due dates for measurement devices used in inspections or tests
• Maintenance events that could impact product quality (e.g., major overhauls or failures during production)

Integration can be as simple as recording equipment and gage IDs against each operation/inspection record, with the underlying calibration and maintenance evidence stored in your maintenance or metrology system but reachable via those IDs.

8. Supplier and outsourced process data

For AS9100, traceability extends into the supply chain where required by contract or risk.

• Supplier part and lot/serial numbers linked to your internal part and work orders
• Purchase order and line-item references for traceable materials and components
• Certifications and CoCs from suppliers and special processors
• Evidence of source inspection or customer release, where applicable
• Records of split lots and how they are distributed across work orders

ERP usually holds supplier and PO data, while documents (CoCs, certs, test reports) are stored in QMS, PLM, or file systems. To support traceability, integrate the identifiers at minimum (PO, supplier, lot/serial, cert ID) and maintain controlled storage for the documents with clear linkages.

9. Document control and revision linkages

AS9100 auditors will look for coherence between what was required and what was actually used.

• Document IDs and revision levels for drawings, specs, and work instructions used at each operation
• Change control records (ECOs, ECRs) and their effectivity dates or serial ranges
• Evidence that the correct revision was available and used at time of manufacture

This requires some level of integration between PLM or document control systems and your execution system (MES or digital travelers), at least to pull and display the correct revision and to record which revision was applied at the time of build.

10. Practical integration priorities and tradeoffs

In a brownfield, regulated environment, fully unified traceability across all systems is rarely achieved in one step and full replacement strategies usually fail due to validation cost, downtime risk, and integration complexity. A pragmatic approach is to:

• Define the “single source” system for each data class (e.g., ERP for lots, PLM for EBOM, QMS for NCRs) and standardize identifiers.
• Focus integration on the links that auditors and customers most often request: serial/lot genealogy, special process evidence, inspection/test records, and NCR/MRB decisions.
• Use digital travelers or MES as the spine that references ERP, PLM, and QMS data, rather than trying to consolidate everything in one platform.
• Ensure robust audit trails, access control, and validation/change control for any system that holds or brokers traceability records.

What is “enough” data integration depends on your product risk, customer requirements, and the maturity of your systems. The consistent requirement is that you can reliably reconstruct an as-planned vs as-built story, backed by evidence, for any serial or lot a customer or auditor selects.