The execution layer is where most AS9100 traceability evidence is actually created and connected. In practice this is usually an MES or execution control system, digital travelers, and related shop-floor applications that sit between ERP, PLM and QMS on one side and machines, tooling and operators on the other.
Core role: creating & linking traceability records
AS9100 requires you to demonstrate what was built, how it was built, with what, by whom, and under which controlled conditions. The execution layer supports this by:
- Capturing “as-built” history for each part, assembly, or lot at the time work is done, not after the fact.
- Enforcing routing and operation sequence so that required steps are recorded instead of skipped or bypassed.
- Linking identifiers (part/serial numbers, batch/lot numbers, work orders, NCs, tools, gages) into a coherent genealogy.
- Generating time-stamped records with user IDs, workstation IDs, and status codes that can be queried during audits and investigations.
Material & component traceability
AS9100 expects you to demonstrate control of materials and components used in production. The execution layer typically supports this by:
- Recording material consumption at the operation or work-center level, associating specific lots/serials to the parent assembly or serialized product.
- Verifying material status (released from receiving inspection, shelf-life valid, special storage requirements met) at the point of use.
- Maintaining forward and backward genealogy so you can answer both “what went into this serial number?” and “where else did this lot go?”
How deep this goes (full unit-level genealogy vs. lot-level only) depends on product risk, contract requirements, system configuration, and operator discipline.
Process, equipment & tooling traceability
AS9100 focuses on controlled and repeatable processes. The execution layer supports this by:
- Enforcing approved routings and revisions that originate in PLM/engineering and are released via document control.
- Recording process parameters or key results (where integrated) from machines, test stands, or manual input for special processes and critical operations.
- Associating equipment and tooling (machine IDs, fixture IDs, program numbers) with the work being performed.
- Blocking or warning on out-of-calibration tools or equipment, when integrated with calibration/asset systems.
The strength of this traceability depends on how completely equipment and tooling data are digitized and whether those systems are integrated or still paper-based.
Operator, training & authorization traceability
AS9100 requires you to control who is authorized and competent to perform specific work. Execution systems can support this by:
- Capturing operator IDs for each operation, inspection, or sign-off.
- Enforcing authorization rules (e.g., only qualified welders can start certain operations) when integrated with training records or HR/QMS.
- Maintaining an audit trail of overrides and dual sign-offs for special characteristics or critical steps.
These controls only hold if the execution layer is actually used as the system of record at the station, rather than work being done off-system and back-entered later.
Nonconformance, rework & disposition traceability
AS9100 emphasizes control and documentation of nonconforming outputs. The execution layer is often where nonconformance events are first detected and where the “as-built” trace is updated by:
- Flagging nonconforming parts or operations at the point of detection and routing them into the NCR/MRB process.
- Linking NCR IDs and dispositions (use-as-is, repair, scrap, rework) to specific serial numbers, work orders, and batches.
- Recording rework operations and re-inspections so the final history shows the real path of the product, not just the ideal route.
Whether this lives fully inside MES or is split across MES and a separate QMS/NCR tool is a design choice. The key for AS9100 traceability is consistent identifiers and reliable integration between systems.
Documented information & revision control at the point of use
AS9100 requires control of documented information (work instructions, drawings, specifications). The execution layer helps by:
- Presenting only current, approved versions of work instructions and drawings at the station.
- Linking the revision actually used to each operation or work order, creating evidence that work was done to the correct issue.
- Preventing work start when a routing, spec, or WI has been superseded but not properly released into production.
This relies on disciplined version governance in PLM/engineering and robust change control. If design and process changes are poorly managed, the execution system cannot protect traceability on its own.
Auditability, searchability & evidence retrieval
AS9100 auditors expect you to retrieve traceability evidence quickly and consistently. The execution layer is central to that by:
- Providing queryable histories by serial number, lot, work order, date range, or operation.
- Maintaining system audit trails that show who changed what, when, and under which approval.
- Feeding structured data to QMS and reporting tools to support internal audits, customer audits, and investigations.
The value here depends on data quality, master data discipline, and how well the execution layer is integrated with QMS/ERP. Poor configuration or inconsistent shop-floor use will still result in slow, manual evidence gathering.
Coexistence with ERP, PLM and QMS in brownfield environments
In most aerospace plants, the execution layer does not replace ERP, PLM, or QMS. Instead, it sits between them and the shop floor:
- ERP remains the commercial and high-level manufacturing record system (orders, financial inventory, planning).
- PLM/engineering remains the design and configuration authority (BOMs, routings, specifications).
- QMS remains the home for procedures, audits, CAPA, and higher-level quality management.
- Execution systems create the detailed as-built history and genealogy and push key data back up.
Full replacement of legacy MES or homegrown travelers is often unrealistic in aerospace due to validation cost, qualification of new systems, downtime constraints, and the risk of disrupting established, audited processes. Incremental deployment, focused on high-risk or high-visibility product families, is more typical, with interfaces that keep traceability coherent across old and new systems.
Limits & dependencies
The execution layer is necessary for robust, scalable traceability in complex aerospace operations, but it is not sufficient by itself to “achieve AS9100 compliance.” Its effectiveness is constrained by:
- Configuration and master data quality (BOM/routing correctness, identifier discipline, clear linking rules).
- Integration with ERP, PLM, QMS, calibration, and NCR systems so traceability is end-to-end rather than siloed.
- Process maturity and change control, ensuring engineering changes and procedure updates are reflected before work starts.
- Operator adoption and training, avoiding backfilling and workarounds that undermine the record.
- Validation and qualification of the system where required by customers or regulators.
Used correctly, the execution layer becomes the backbone of AS9100 traceability, but outcomes will vary significantly between plants based on how these dependencies are handled.
