There is no universal right answer. In aerospace, configuration control usually has to be split across systems, with one system clearly designated as the master for each aspect of configuration. Trying to force all configuration control into a single system (ERP or MES alone) often creates more risk than it removes, especially in brownfield, highly validated environments.
What “configuration control” actually touches
Before choosing a system, separate the different layers of configuration you are trying to control:
- Product configuration: part numbers, effectivity, options/variants, engineering BoM, drawings, models.
- Manufacturing configuration: routing, operations, work instructions, tooling, NC programs, inspection plans.
- Commercial / supply configuration: sellable SKUs, contract items, approved manufacturer lists, supplier part numbers.
- As-built / as-maintained configuration: serialized build records, installed configuration, change history in the field.
ERP, MES, and dedicated configuration or PLM systems are each strong in different parts of this stack.
Typical roles for each system
In most aerospace plants today:
- ERP is the commercial and planning system of record: customer part, internal part, revision identifier, planning BoM, and MRP. It is not usually the place to manage detailed process-level configuration or complex change workflows.
- MES is the execution system of record: which specific serialized unit was built to which revision, under which routing, with which operations, NC programs, inspection results, and concessions. It is usually where as-built configuration and genealogy are anchored.
- Dedicated configuration / PLM / CM system (sometimes called PDM or CMDB in this context) is often the engineering configuration authority: full engineering BoM, effectivity, baselines, and formal change control from ECN/ECR through release.
In many regulated aerospace environments, engineering configuration control sits in PLM or a dedicated CM tool, with ERP and MES consuming that data in controlled, versioned ways.
When to anchor configuration in ERP
ERP can be the primary configuration system for:
- Commercial identifiers: sellable SKUs, customer part numbers, contract-level revisions.
- High-level BoM: planning or manufacturing BoM without deep process detail.
- Effectivity at the order level: which revision a customer order or work order is for.
Advantages:
- ERP already drives MRP, purchasing, and shipment; using it for high-level configuration keeps those consistent.
- Finance and supply chain teams typically already trust ERP as the commercial system of record.
Limitations and risks:
- ERP is usually weak at detailed process configuration: work instructions, NC program versions, inspection plan details, or operation-level effectivity.
- Engineering change workflows in ERP are often crude or bolt-ons; tracing from ECN to as-built item at operation level can be difficult.
- Heavily customizing ERP to act as a full configuration management system increases upgrade risk and validation burden.
If you make ERP the master for configuration, you still need tight, validated integration to MES or a configuration-aware system to ensure as-built records match ERP intent.
When to anchor configuration in MES
MES can be the primary configuration system for:
- Manufacturing process configuration: routings, operation definitions, work instructions, inspection steps, NC program references, process parameters.
- As-built configuration and genealogy: which serial number followed which routing and revision, at which station, using which consumables.
- Process-level change control: ensuring that only released instructions and routings are used, with audit trails for who changed what and when.
Advantages:
- MES is close to the shop floor, so routing-level and instruction-level changes can be controlled and enforced at execution.
- It naturally links configuration to evidence: operator signoffs, inspection results, nonconformance records, and test data.
- It can represent operation-level effectivity (e.g., operation 20 changed at serial X) more naturally than ERP.
Limitations and risks:
- MES is usually not the source of engineering truth; it consumes from PLM or ERP. If MES starts inventing independent part numbers or revs, you get divergence.
- If MES becomes the de facto master without clear rules, you can end up with conflicting definitions between MES, ERP, and PLM.
- Retrofitting full configuration discipline into a legacy MES can be as hard as buying or building a dedicated configuration system.
MES is generally the right place to anchor as-built configuration, but it should take engineering and commercial configuration from PLM/CM and ERP, not replace them.
When to use a dedicated configuration or PLM system
A dedicated configuration management or PLM system is usually the best place for engineering configuration control in aerospace, especially for complex assemblies and long lifecycles:
- Engineering BoM and variant structures.
- Formal baselines (prototype, qualification, production).
- Effectivity across serials, lots, customers, or programs.
- ECN/ECR workflows, impact analysis, and approvals.
Advantages:
- Tools are designed around configuration management principles and standards.
- Separates engineering change control from operational planning and execution, reducing pressure to shortcut CM for schedule reasons.
- Can support digital thread use cases: linking models, drawings, requirements, and downstream manufacturing data.
Limitations and risks:
- Requires robust integration to ERP and MES so that part numbers, BoMs, and revisions flow in a controlled, traceable way.
- Introducing a new dedicated system in a brownfield environment adds validation and change management burden.
- If not governed carefully, you can have conflicting “masters” across PLM, ERP, MES for the same part or routing.
Dedicated CM/PLM is rarely a drop-in replacement for ERP and MES. It becomes the upstream authority, and ERP/MES become execution consumers within a defined digital thread.
Practical patterns that work in aerospace
In regulated aerospace plants, successful patterns usually look like one of the following:
- PLM/CM as engineering master, ERP for commercial, MES for as-built
- PLM/CM owns engineering BoM, effectivity, and ECN workflows.
- ERP owns part master, planning BoM, and revision key for orders.
- MES owns routings, work instructions, and as-built genealogy, but cannot create or change key part/rev identifiers without PLM/ERP.
This is the most common for complex OEMs and tier-1s with strong engineering organizations.
- ERP as part / revision master, MES as process and as-built master
- ERP holds part numbers, high-level BoMs, and top-level revision.
- MES holds detailed routings, work instructions, and links them to ERP part/rev.
This is common where PLM is limited or absent, particularly at tier-2/tier-3 suppliers, but requires discipline to keep engineering artifacts aligned.
- Dedicated CM system with light ERP and MES integrations
- CM system or PLM is authoritative for engineering and product configuration.
- ERP is primarily finance/MRP with limited configuration responsibility.
- MES focuses on execution, tightly constrained by CM data and rules.
Common in highly regulated defense programs, but integration and validation costs are significant.
Why “full replacement” strategies often fail
Trying to turn a single system into the universal configuration authority (“we will do all configuration in ERP now,” or “MES will be the only configuration control system”) frequently breaks down because:
- Qualification and validation burden: Replatforming critical configuration control requires extensive testing, documentation, and requalification with customers and authorities.
- Downtime and cutover risk: Migrating all configuration into one system demands big-bang cutovers that many aerospace plants cannot tolerate.
- Integration complexity: Existing QMS, PLM, and supplier portals are already wired to multiple systems. Ripping those out often causes more issues than it solves.
- Traceability and change control: Long asset lifecycles mean you must retain and interpret legacy configuration data for decades; consolidating it into a new system without loss or misinterpretation is nontrivial.
Incremental, clearly scoped changes to system roles, with strong integration and governance, tend to be more successful.
How to decide for your environment
When deciding where to handle configuration control, focus on:
- What is already validated: Changing the system of record for configuration can require revalidation or customer approval.
- Where data is most trusted today: For example, if quality audits always rely on MES traceability, anchoring as-built configuration elsewhere will be disruptive.
- Integration maturity: If ERP–MES and PLM–MES integrations are immature or manual, introducing a dedicated CM system or shifting ownership could increase actual risk.
- Scope of configuration you really need: Do you need variant and effectivity control at the serial level, or just at the order level? Answers change which system is realistic.
- Governance capability: A dedicated CM system without strong governance can create a new failure point instead of solving the problem.
In most aerospace manufacturers, a pragmatic target state is:
- Engineering configuration in PLM or a CM system.
- Commercial and planning configuration in ERP, tightly linked to engineering data.
- Process and as-built configuration in MES, constrained by engineering and ERP masters.
The specifics will depend on your existing stack, integration readiness, and the regulatory and customer expectations you operate under.
