Should digital work instructions replace or sit alongside an MES in aerospace factories?

Digital work instructions should usually sit alongside an MES, or be delivered as a controlled function inside the MES, rather than replace it. In aerospace factories, work instructions are not the same thing as manufacturing execution control. They can guide operators, present approved content, collect confirmations, and support evidence capture, but they normally do not replace MES responsibilities such as routing enforcement, WIP status, genealogy, labor and material transactions, nonconformance linkage, equipment status, and integration with ERP, PLM, QMS, and maintenance systems.

The practical distinction

Digital work instructions are primarily an operator guidance and standard work layer. They answer questions such as what step to perform, what visual aid to use, what torque value applies, what inspection point is required, and what evidence must be captured.

An MES is typically the execution system of record, or at least part of that record. It controls or records which order is being run, which routing applies, which serial or lot is affected, which materials were consumed, which operation is complete, which exception occurred, and what data must be passed to ERP, QMS, PLM, or customer-facing traceability systems.

Some MES platforms include strong digital work instruction capability. Some do not. Some plants use a separate work instruction platform because the MES is old, rigid, poorly adopted, or difficult to change. The architecture can be valid either way, but the system-of-record boundaries must be explicit.

When work instructions can stand alone

A standalone digital work instruction system can be reasonable when the scope is limited to operator guidance, visual standard work, training reinforcement, or controlled content delivery. It may also be useful as a phased modernization step where replacing or heavily modifying the MES would carry too much validation cost, downtime risk, or integration disruption.

That does not make it a replacement for MES. If the standalone system starts collecting production status, quality evidence, serial history, buyoff records, or inspection results, it has moved into regulated execution territory. At that point, access control, version control, audit trails, data retention, electronic record expectations, validation, and change control become material concerns.

Why full MES replacement is usually unrealistic

In brownfield aerospace environments, replacing an MES just to improve work instructions is often unrealistic. Existing MES deployments may be tied into ERP, PLM, QMS, maintenance systems, inspection systems, label printing, machine interfaces, customer reporting, and long-running program records. Replacing that stack can create qualification burden, validation cost, downtime risk, integration complexity, and traceability disruption.

This is especially true where programs have long lifecycles, qualified processes, customer-specific requirements, or established audit evidence flows. A cleaner user interface does not, by itself, justify breaking a validated execution chain.

What must be defined before choosing the architecture

The important decision is not whether digital work instructions are separate or embedded. The important decision is which system owns each controlled function.

• PLM or document control: often owns engineering definition, released drawings, specifications, and controlled source documents.
• MES: often owns routing execution, operation status, WIP movement, genealogy, production records, and shopfloor transactions.
• Digital work instruction system: may own step presentation, visual guidance, operator prompts, and some task-level data capture.
• QMS: often owns nonconformance, disposition, CAPA, audit records, and quality workflows.
• ERP: often owns demand, work orders, inventory valuation, purchasing, and financial transactions.

These boundaries vary by site. They need to be documented, validated where required, and protected through change control. Ambiguity is a common failure mode.

Common failure modes

The first failure mode is duplicate truth. If the MES routing says one thing, the digital instruction says another, and the drawing or planning document says a third, the plant has not digitized control. It has digitized confusion.

The second failure mode is weak revision governance. Aerospace work instructions often depend on engineering revision, part number, serial effectivity, operation, configuration, customer requirement, and sometimes repair disposition. If the instruction platform cannot enforce the correct revision for the correct job, manual controls will still be required.

The third failure mode is unvalidated data capture. If operator confirmations, inspection values, photos, torque readings, or signoffs are used as production or quality records, the system must be assessed accordingly. Audit trails, timestamps, identity controls, retention, backup, and record retrieval matter.

The fourth failure mode is poor integration. If operators must complete the same step in a work instruction system and then re-enter completion in MES, adoption suffers and data quality degrades. Integration does not need to be perfect on day one, but duplicate entry should be treated as a risk, not as a neutral inconvenience.

A reasonable target state

For many aerospace factories, the realistic target is coexistence: keep the MES as the execution backbone, use digital work instructions to improve operator guidance and evidence capture, and integrate the two where the business case and compliance risk justify it. In some cases, the work instruction capability should be native to the MES. In others, a separate layer is acceptable if ownership, synchronization, validation, and auditability are controlled.

The safest answer is therefore not “replace the MES.” It is to define the execution record, decide which system owns each part of it, and avoid introducing another uncontrolled source of production truth.