Small aerospace suppliers can justify an execution layer on top of ERP, but not by default. It is warranted when it clearly reduces compliance risk, manual overhead, and schedule/rework volatility that ERP, paper, and spreadsheets cannot realistically manage.
What an execution layer is (in this context)
For small suppliers this usually means a lightweight manufacturing execution capability: digital travelers, work-in-process visibility, electronic sign-offs, and basic traceability & quality workflows that sit between ERP and the shop floor. It is not a full replacement for ERP or QMS.
When it is usually justified for small aerospace shops
Adding an execution layer is easier to justify when at least some of the following are true:
- AS9100 / AS9102 evidence is painful: Paper packets, missing signatures, late FAI data, or scramble work before audits and customer visits.
- Traceability expectations are growing: Part, lot, and material genealogy are required, but are currently split across ERP, spreadsheets, and paper travelers.
- High-mix, low-volume reality: Many routings, frequent engineering changes, and customer-specific variants that make printed travelers obsolete quickly.
- Rework and NCRs are frequent: Nonconformances, concessions, and rework loops are hard to control or reconstruct after the fact.
- Schedule promises vs. reality diverge: ERP dates exist, but supervisors manage by whiteboards, emails, and expedites.
- Missed or late documentation is driving chargebacks or scorecard risk: Customers are pushing for better delivery plus documentation performance.
If none of these problems are material, a small supplier is often better off tightening existing ERP, QMS, and basic digital work-instruction practices before adding a separate execution system.
How small suppliers should think about scope
Full-blown MES programs often fail in small aerospace environments because they are scoped too broadly and collide with ERP and QMS responsibilities. A more realistic execution layer for a small shop usually focuses on:
- Digital travelers and routing: The same routing as ERP, but with step-level status, timestamps, and operator sign-offs.
- Operator guidance: Current work instructions, drawings, and revision-controlled attachments at the point of use.
- Electronic traceability: Capturing material lots, serials, tool IDs, and key characteristics as the part moves through the process.
- Basic NCR & rework control: Logging nonconformances in a structured way, tying them to specific work orders, lots, and characteristics.
- Realistic WIP visibility: Which jobs are at which work center, what is blocked, and what is ready, aligned to ERP orders but more granular than ERP can provide.
Trying to replace ERP planning, inventory, or purchasing with a new execution tool almost always introduces risk and revalidation burden that small suppliers cannot absorb.
Typical benefits, and what they depend on
When scoped tightly and implemented well, small suppliers can see:
- Lower documentation risk: More complete traveler packets and audit trails, fewer missing sign-offs or inspection records.
- Faster, cleaner FAIs: Easier to compile evidence for AS9102 and customer FAI packages if data is captured inline instead of after the fact.
- Reduced manual status chasing: Supervisors and planners spend less time walking the floor or calling for status updates.
- Better control of rework and concessions: Clearer lineage for NCRs and deviations, improving both compliance and cost visibility.
Actual results depend heavily on:
- Data quality in ERP: Item masters, routings, and revision data must be good enough to drive coherent travelers.
- Integration quality: Work orders, operations, and completions must sync reliably; manual rekeying negates many benefits.
- Process discipline: Operators must actually use the system at the point of work, and supervisors must enforce it.
- Validation and change control: Especially for regulated work, changes to digital travelers or inspection logic must be controlled and documented.
Key tradeoffs and risks for small suppliers
Small aerospace shops must weigh the following carefully:
- Implementation and adoption effort: Even a small execution layer requires process mapping, configuration, integration, training, and usually some validation. This can strain a small team.
- Brownfield integration: Existing ERP, QMS, and document-control systems rarely align cleanly. Interfaces often start “simple” and become fragile as edge cases accumulate.
- Long equipment and system lifecycles: Once you embed an execution layer into daily work and quality records, ripping it out later is expensive and disruptive. You are committing to maintain it through audits, staff turnover, and customer reviews.
- Qualification burden: For some customers and programs, digital changes in how work is executed or documented require customer approval, updated procedures, and objective evidence that the new process is controlled.
- Scope creep toward full MES: A small project can expand into scheduling, SPC, maintenance, and more, quickly outgrowing what the shop can realistically support.
Why “full replacement” strategies often fail
Attempting to replace ERP or QMS with a new execution layer is rarely justifiable for small aerospace suppliers:
- Downtime and cutover risk: Extended downtime is usually not acceptable, and dual-running systems is costly and error-prone.
- Integration complexity: ERP is already woven into purchasing, invoicing, and inventory; pulling it out or bypassing it breaks downstream processes.
- Traceability and change control: Rebuilding historical traceability and evidence trails in a new system to satisfy auditors and customers can be prohibitive.
- Customer and regulator expectations: Changing the “system of record” can trigger requalification, procedure updates, and new audit questions that the shop is not resourced to handle.
For most small suppliers, a limited execution layer that coexists with ERP and QMS, and is carefully bounded, is more realistic than a wholesale system replacement.
Practical decision criteria
A small aerospace supplier can often justify an execution layer when all of the following are answered “yes”:
- You can identify specific, recurring problems (e.g., late FAI, missing records, manual traveler rebuilds, chronic expedite chaos) that the execution layer directly addresses.
- You can keep ERP as the system of record for inventory, cost, and financials, and QMS as the system of record for formal NCR, CAPA, and document control.
- You can start with a narrow scope: a subset of part families, a single cell, or a well-defined value stream, and expand only after it is stable.
- You have at least minimal internal ownership (operations + quality + IT) for process design, integration oversight, and ongoing administration.
- You are prepared to document and, where needed, validate the new workflows as part of your AS9100 system.
If those cannot be met, strengthening existing ERP usage, work-instruction governance, and basic digital recordkeeping is usually a safer first step than introducing a new execution layer.