In most aerospace environments, an execution layer is complementary to MES rather than a full replacement. It can displace parts of a legacy MES footprint, but a clean, one-for-one swap is uncommon because of validation burden, integration complexity, and the risk of disrupting certified and qualified processes.
What an execution layer typically does well
Modern execution layers generally focus on:
- Digital work instructions and operator guidance (including model-based and configuration-specific variants)
- Digital travelers, routing enforcement, and in-station checks
- Real-time data capture for torque, measurements, serial numbers, and special process confirmations
- Defect logging, containment triggers, and handoff to NCR/CAPA systems
- Work-center visibility for WIP, queues, and bottlenecks
- Operator experience improvements over aging MES or paper travelers
These capabilities often sit on top of existing ERP/MES/QMS stacks, orchestrating execution on the shop floor while leaving core system-of-record responsibilities in place.
Where MES typically remains the system of record
In aerospace, especially under AS9100 and customer-specific requirements, MES (and sometimes ERP) usually still owns:
- Primary work-order creation and routing definitions, often derived from ERP or PLM/BOM structures
- Master data for resources, work centers, and routings
- Formal lot/serial tracking that ties back to ERP inventory and material control
- Integration to QMS for NCRs, MRB, CAPA, and quality records
- Data structures that support FAI/AS9102 evidence, process capability, and long-term retention
- Interfaces to planning, MRP, and cost accounting in ERP
Execution layers can extend or overlay these functions visually, but replacing them outright affects many validated and audited interfaces, not just the operator screens.
When an execution layer can partially replace MES
An execution layer can effectively replace parts of MES in specific scenarios:
- MES is thin or absent: Sites running ERP plus paper travelers often use an execution layer as their primary shop-floor system, while ERP remains the planning and inventory system of record.
- MES is localized or non-standard: If multiple plants run different legacy systems, an execution layer can standardize execution behavior across them and gradually retire weaker MES components.
- Scope-limited replacement: You may replace MES for specific value streams (for example, composite layup, sub-assembly, or test) where qualification and integration are easier to isolate.
Even in these cases, the execution layer usually integrates tightly with ERP, QMS, PLM, and sometimes a remaining MES core, rather than taking over all responsibilities.
Why full MES replacement is difficult in aerospace
Replacing MES outright in aerospace is possible, but it is rarely fast or low risk. Common constraints include:
- Qualification and validation burden: Any system that impacts configuration control, traceability, or FAI/AS9102 evidence requires formal qualification, validation, and controlled rollout. This is costly and time-consuming, especially across fleets and programs.
- Audit and customer expectations: Customers and regulators expect continuity in how you generate travelers, record genealogy, and maintain audit trails. A MES swap changes many of those data paths at once.
- Integration complexity: MES is often embedded in dozens of interfaces (ERP, PLM, QMS, test stands, special process equipment, portals). Re-pointing all of these to a new execution layer is non-trivial and error-prone.
- Downtime and change-control limits: Major cutovers require coordinated outages and contingency plans for active work orders and serialized hardware. Many sites cannot tolerate large-bang changes without production risk.
- Long equipment and program lifecycles: Running programs and long-lived tooling depend on MES data structures. Disrupting them mid-program can trigger design, documentation, or certification rework.
Because of these factors, many aerospace organizations use the execution layer to de-risk and stage change, rather than attempt a single, full replacement.
Practical coexistence patterns
Most aerospace plants adopt a hybrid model where the execution layer is explicitly complementary:
- ERP and PLM: Remain the source of BOMs, routings, and configuration baselines.
- MES core: Maintains formal work-order lifecycle, serialized WIP, and critical traceability links to ERP.
- Execution layer: Controls in-station behavior, digital work instructions, data capture, and operator workflow. It synchronizes back to MES/ERP for status and genealogy updates.
- QMS: Continues to own NCR, MRB, CAPA, and audit workflows. The execution layer triggers and feeds these processes with contextual data.
This coexistence allows you to modernize execution and evidence collection while minimizing disruption to validated integrations and accounting flows.
Decision guidelines
When deciding whether an execution layer will be complementary or a partial replacement, consider:
- Regulatory scope: Which processes and records are explicitly referenced by customers, regulators, or contracts? Changing systems here carries higher qualification and documentation costs.
- Integration footprint: How many upstream and downstream systems currently depend on MES data and APIs?
- Site and program variability: Do all plants and programs use the same MES and processes, or is there an opportunity to standardize through the execution layer?
- Data ownership clarity: For each object (work order, routing, serial/lot, inspection result), decide which system is the source of truth and design interfaces accordingly.
- Change-control capacity: How many concurrent large changes can your organization reasonably validate, document, and train for without overloading teams?
In many aerospace organizations, the lowest-risk path is to deploy the execution layer first as a complementary overlay, validate its behavior, and only then consider shifting specific MES responsibilities into it in a controlled, incremental way.
