In aerospace, a “traditional MES” is usually a broad, monolithic application intended to control and record most aspects of production. An “execution layer” is a thinner, more focused layer that sits closer to operators and equipment, handling day-to-day execution, guidance, and traceability while coexisting with ERP, PLM, QMS, and often legacy MES.
What is a traditional MES in aerospace?
Traditional aerospace MES platforms typically:
- Provide end-to-end manufacturing functions inside one product (work orders, routings, labor booking, WIP, basic quality, some planning and reporting).
- Expect to be the primary system of record for shop-floor execution data.
- Use a single, vendor-controlled data model that upstream and downstream systems must integrate into.
- Are deployed as large, multi-year programs with extensive validation, qualification, and change control.
- Are often tightly coupled to specific plants, product lines, or equipment generations, making major upgrades or replacements difficult.
In many aerospace plants, MES is also intertwined with customizations, local add-ons, and plant IT scripts accumulated over years. That makes it hard to change without significant downtime and re-validation effort.
What is an execution layer?
An execution layer is a focused set of capabilities that sits between enterprise systems and the physical workstations, cells, and lines. It typically:
- Handles real-time work execution: dispatching operations, enforcing sequences, capturing as-built data, and recording operator actions.
- Delivers digital work instructions, data collection, tool checks, and signoffs at the point of use.
- Integrates with ERP, PLM, QMS, and sometimes an existing MES instead of trying to replace them outright.
- Acts as a “system of engagement” for operators, with upstream systems remaining systems of record where appropriate.
- Is typically modular and scoped rollout by cell, line, or program, rather than all-at-once across the plant.
In practical terms, the execution layer is where travelers, operations, inspections, and deviations are actually performed and recorded, while higher-level systems continue to own master data, planning, and some quality and configuration control.
Key differences in scope and responsibility
The main differences between an execution layer and a traditional MES are about how much they try to own and how they coexist with the rest of your stack.
- Scope breadth
Traditional MES: Tries to cover a wide functional scope (dispatch, WIP, some scheduling, basic quality, reporting) in a single platform.
Execution layer: Focuses on execution, guidance, and traceability at the station or cell, and relies on ERP / PLM / QMS for master data and many higher-level workflows.
- System of record vs system of engagement
Traditional MES: Often positioned as the primary system of record for shop-floor events, sometimes duplicating or owning data that could reside in ERP or PLM.
Execution layer: Usually acts as the primary system of engagement and data capture, then synchronizes key records (as-built, nonconformance data, test results) back to systems of record.
- Integration posture
Traditional MES: Integrations are often point-to-point and heavy; the MES expects other systems to conform to its data model.
Execution layer: Typically designed for interoperability from the start, with APIs and connectors to ERP, PLM, QMS, existing MES, and equipment. Quality of integration still varies significantly by vendor and implementation.
- Granularity and usability at the workstation
Traditional MES: Operator interfaces can be generic, form-heavy, and less tailored to complex aerospace work content.
Execution layer: Usually optimized for detailed work instructions, configuration-specific content, data collection, and enforcement at the operation level.
- Deployment style
Traditional MES: Large, multi-year deployments; big-bang or large waves; difficult to iterate once validated.
Execution layer: Often deployed incrementally (cell, line, program), then expanded. Still requires validation and change control but can be easier to iterate if scoped correctly.
Why an execution layer is attractive in brownfield aerospace plants
Most aerospace environments already have ERP, some form of MES, a QMS, and PLM or PDM. Replacing any of these outright is high risk due to:
- Qualification and validation burdens for software that affects product quality and airworthiness records.
- Downtime constraints in HMLV environments with tight delivery dates and penalty risk.
- Complex, poorly documented integrations to legacy systems and test equipment.
- Long equipment and program lifecycles where systems must support decades of traceability.
Because of this, full MES rip-and-replace projects frequently stall or deliver less than promised. An execution layer can instead:
- Layer on top of existing ERP / MES / QMS / PLM to address operator experience, digital travelers, and traceability gaps without immediately decommissioning legacy platforms.
- Target specific problem areas such as paper travelers, manual FAI support, nonconformance capture, or incomplete as-built records.
- Provide a path to gradually migrate execution logic and records into a more modern platform while keeping legacy systems online as long as needed.
However, this approach is not risk-free. It depends heavily on integration quality, master data governance, and clear responsibility boundaries between systems. Poorly designed layering can create duplicate data, inconsistent records, and higher audit risk.
Implications for traceability and compliance
Neither a traditional MES nor an execution layer guarantees AS9100, AS9102, or other compliance outcomes. In both cases you need:
- Clear process definitions for how travelers, inspections, concessions, and MRB decisions are executed and recorded.
- Documented and validated integrations so that as-built, as-inspected, and configuration data are consistent across systems.
- Change control over workflows, forms, labels, reports, and interfaces that affect quality records.
- Governance over who owns the “official” record for each type of data (ERP vs MES vs execution layer vs QMS vs PLM).
An execution layer can make it easier to enforce step-by-step execution and capture complete evidence at the point of work, which can help audit readiness if implemented and validated correctly. But it also introduces another system that must be controlled, qualified where relevant, and kept in sync with the rest of your stack.
When to lean toward one vs the other
In practice, most aerospace organizations end up with some combination of both patterns:
- Leaning on traditional MES makes sense when:
- You already have an MES that is validated, stable, and well-integrated for core functions.
- Your change appetite is low and you are primarily optimizing within an existing architecture.
- Adding an execution layer makes sense when:
- Your existing MES or ERP-centric approach cannot realistically handle the detail and variability of work instructions, variants, or inspection requirements.
- You need to improve operator guidance, digital travelers, and as-built traceability without triggering a full MES replacement.
- You have multiple plants or programs and need a consistent execution experience across different legacy stacks.
Either way, the decision should be based on a realistic assessment of current systems, integration debt, validation cost, and the specific execution gaps you are trying to close, not on labels like “MES” versus “execution layer.”
