In aerospace manufacturing, MES should contain the controlled execution record for how work is performed, verified, paused, deviated, and completed on the shop floor. It should not become a dumping ground for every engineering, planning, quality, maintenance, or ERP function. In practice, MES owns work order execution, operator guidance, traceability, inspection capture, electronic travelers, status, and production evidence, while integrating to PLM, ERP, QMS, calibration, maintenance, and document control systems where those remain the systems of record.
What commonly belongs in MES
The exact boundary depends on the plant, program, customer requirements, validation approach, and existing system landscape. Still, the following functions commonly belong in MES for aerospace manufacturing:
- Electronic travelers and operation execution: routing steps, hold points, sign-offs, buyoff logic, operation status, WIP visibility, and completion records.
- Digital work instructions as executed: operator-facing instructions, visual aids, controlled references, and revision enforcement. The engineering or document authority may still live in PLM or a document control system.
- Serial, lot, and genealogy tracking: material consumption, component installation, kit verification, substitutions where allowed, and as-built traceability.
- Labor, time, and resource capture: who performed the work, when it was performed, and which station, tool, fixture, machine, or program was used, where that level of traceability is required.
- In-process inspection capture: inspection results, characteristic-level measurements, pass/fail checks, sampling records, defect observations, and links to gages or test equipment.
- Shop-floor quality events: nonconformance initiation, containment status, rework execution, repair steps, and links to MRB, CAPA, or QMS workflows when those are handled outside MES.
- Equipment and process data tied to production: machine status, test results, torque data, oven or autoclave cycles, environmental readings, and other validated data that must be associated with a serial number, lot, operation, or batch.
- Electronic signatures and audit trails: approval events, operator attestations, supervisor buyoffs, timestamped changes, and evidence needed to reconstruct the execution history.
- Training or qualification checks: usually as an enforcement point in MES, with the authoritative training record often maintained in an LMS, HR system, or QMS.
What usually should not be owned by MES
MES should not usually be the master system for engineering design, financial planning, procurement, costing, supplier contracts, formal document control, or enterprise quality governance. It may consume or reference that information, but ownership often sits elsewhere.
- PLM typically owns engineering definitions, product structures, CAD, approved design data, and engineering change control.
- ERP typically owns demand, MRP, purchasing, inventory accounting, costing, shipment, and financial transactions.
- QMS often owns formal nonconformance disposition, CAPA, audit management, supplier quality, and quality-system records.
- EAM or maintenance systems usually own preventive maintenance plans, work orders, asset history, and maintenance compliance records.
- Document control systems may remain the authority for released procedures, specifications, and controlled documents.
- Data platforms or historians may own high-volume time-series data and analytics datasets, while MES stores or references the subset needed for production traceability.
The practical boundary test
A useful test is this: does the data prove what was built, who performed or verified the work, which materials and revisions were used, which equipment or tooling was involved, what measurements were recorded, and whether the step was completed under the right approval state? If yes, MES is usually involved either as the owner of the record or as the execution layer that captures and links the evidence.
If the data defines the product, plans enterprise supply, controls financial valuation, manages formal engineering release, or governs the quality system beyond the shop-floor event, MES should usually integrate with the authoritative system instead of replacing it.
Brownfield reality matters
Most aerospace plants are brownfield environments with existing ERP, PLM, QMS, MRO, maintenance, test, and legacy MES systems. A clean replacement of all adjacent systems is usually unrealistic. The qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, and long equipment lifecycles are too large for many programs.
For that reason, MES scope should be defined around controlled execution and evidence capture first. The integration model should then specify which system is authoritative for each data object, how revisions are synchronized, how exceptions are handled, and what happens when an interface is unavailable.
Common failure modes
- Duplicating master data without governance: part numbers, routings, operations, documents, and specifications drift between MES, ERP, and PLM.
- Putting uncontrolled instructions in MES: operators see convenient content that is not aligned with released engineering or quality documentation.
- Capturing process data without validation: machine or IIoT data is collected but cannot be trusted as production evidence because timestamps, units, calibration status, or serial-number linkage are weak.
- Overloading MES with QMS decisions: nonconformance disposition, MRB authority, or CAPA ownership is blurred, creating approval and audit-trail problems.
- Ignoring manual fallback controls: downtime procedures, paper contingency records, and reconciliation rules are not defined before MES becomes operationally critical.
The right MES scope is therefore not “everything on the shop floor.” It is the controlled layer that guides, records, enforces, and proves manufacturing execution, with clear interfaces to the systems that own engineering, planning, quality governance, maintenance, and enterprise records.