Product configurator MES integration
Connect accepted product configurations to controlled manufacturing execution.
Configurix can preserve customer choices, dimensions and project revisions as configured demand moves through ERP or PLM into MES. A dependable integration proves which production order, BOM, routing and instructions were executed—and what the factory actually built.
One execution trace
Configured demand to as-built result
Accepted configuration
CFG-4821 · revision 7
Production order
PO-88420 · released
MES execution
JOB-3187 · in progress
As-built trace
serial · quality · actuals
Configurix explains and records configured demand. ERP, PLM and MES retain their accepted order, engineering and execution responsibilities. Stable identity and controlled acknowledgement connect the lifecycle.
Integration definition
A sales configuration is the demand. MES controls the execution.
A configured product can start the production lifecycle, but it is not automatically a released order, manufacturing BOM, routing or work instruction. The integration must transform customer intent into an executable baseline, reject incomplete or unapproved demand and return enough acknowledgement to prove what happened.
Released production demand
- Production-order and configured-product identity
- Accepted BOM, routing, operation and work-center context
- Quantity, unit, plant, priority and requested dates
- Configuration, engineering and order revisions
- Work instructions, drawings and approved documents
- Hold, review and release status
Controlled shop-floor execution
- Order dispatch and operation start or completion
- Operator, resource, equipment and station context
- Material issue, lot, serial and consumption evidence
- Measurements, inspection and quality results
- Rework, deviation, nonconformance and disposition
- Actual time, quantity, yield and scrap
Execution acknowledgement
- Accepted, rejected, blocked or duplicate delivery
- MES order, job, batch or serial identifiers
- Operation progress and completion status
- Actual quantities, consumption and genealogy
- Quality, exception and change references
- Reconciliation against the released baseline
Interactive MES integration planner
Define the production release before connecting the shop floor.
Choose the closest architecture. The result identifies the contracts and acceptance evidence to prioritize; actual objects, systems and safety responsibilities depend on the working manufacturing environment and signed Configurix scope.
System-of-record matrix
Put every decision at the correct enterprise or production layer.
| System | Primary responsibility | Boundary to prove |
|---|---|---|
| Configurix | Customer, dealer or sales choices; valid interactive state; 3D; scoped price; quote; accepted project revision | Preserve the exact commercial and product intent, but do not present the browser scene as a released production order. |
| CRM or CPQ | Account, opportunity, commercial approval, proposal and customer decision context | A won opportunity is a commercial trigger, not proof that material, routing or shop-floor data is ready. |
| PLM and CAD | Engineering definition, structures, CAD, drawings, revisions, maturity, effectivity and controlled technical change | Name the technical release that permits production and the path for an order-specific exception. |
| ERP | Operational items, plants, production or sales orders, planning, inventory, cost, procurement and finance | ERP commonly releases the order and receives confirmations, even when Configurix supplied the original configured demand. |
| MES or MOM | Dispatch, jobs, operations, instructions, resources, consumption, genealogy, quality, actuals and execution state | MES executes an accepted production baseline; it should not silently reinterpret an incomplete sales configuration. |
| Machines and controls | Physical process, equipment state, sensing, control, machine programs and recorded production signals | Machine connectivity and control need their own safety, validation, cybersecurity and operational ownership. |
ISA-95 provides a useful conceptual boundary between business planning and logistics and manufacturing operations management. Real products can combine responsibilities; the implementation still needs one accountable source for every field and transition.
Canonical execution contract
Carry identity, release and purpose with every production field.
A production payload is not a random export of everything known about a product. It is a versioned contract for one downstream action, with enough context to validate, reject, execute, acknowledge and reconcile it.
identityConfiguration, quote, customer order, production order, material, operation, job and external-system IDs
baselineConfiguration, price, product, EBOM, MBOM, routing, drawing, instruction and order revisions
scopePlant, site, production line, work center, resource, market, account and requested delivery context
productConfigured parameters, selected choices, derived values, dimensions and approved exception status
materialsComponent identity, hierarchy, quantity, unit, occurrence, substitution, lot or serial requirement
operationsSequence, operation, activity, duration, skill, resource, tooling, predecessor and completion criteria
documentsDrawing, work instruction, inspection plan, attachment identity, revision and controlled access link
qualityCharacteristic, target, tolerance, method, sample, result, nonconformance and disposition fields
deliveryEvent or request ID, correlation, idempotency, status, reason, retry and acknowledgement
actualsStarted and completed timestamps, operator, equipment, yield, scrap, consumption, genealogy and final state
Object model
Six related records. Six different meanings.
Customer configuration
What the buyer, dealer or salesperson selected, saw, priced and approved in a specific Configurix revision.
Owner · Configurix
Configured-order request
A structured demand package that asks operational systems to validate, transform or create an executable order.
Owner · Configurix, middleware or ERP by scope
Production order
The operational authorization to produce a quantity of an item at a plant with accepted dates and status.
Owner · Usually ERP or planning
Manufacturing BOM and routing
The plant-specific materials, quantities and operation sequence accepted for the production order.
Owner · ERP, PLM, planning or manufacturing engineering
MES job or execution record
The dispatched and executed work with operators, resources, material, quality, progress and actual results.
Owner · MES or manufacturing operations management
As-built trace
The evidence of what was actually consumed, produced, inspected, changed and completed for the result.
Owner · MES, quality and connected operational systems
Configuration-to-production lifecycle
Make every release, execution and confirmation observable.
Accept configuration
Freeze one Configurix project revision with product choices, dimensions, price status, quote and customer decision.
Validate production eligibility
Confirm technical release, commercial approval, plant, material, quantity, requested date and exception status.
Create operational order
Create or update the responsible ERP, planning or approved order object with a stable correlation to the project.
Resolve materials and operations
Select the accepted BOM, routing, instructions, tools, inspection requirements and order-specific values.
Release to MES
Send the production baseline atomically or through an accepted staged process and record the receiving MES identity.
Execute and control
Dispatch work, capture operators, resources, consumption, measurements, exceptions, rework and progress.
Confirm actuals
Return yield, scrap, material, time, completion, genealogy and quality context to the responsible enterprise systems.
Reconcile and govern change
Compare released, acknowledged and completed records; control revisions, cancellations, supersession and saved evidence.
Integration patterns
Choose the path that matches the factory’s real order authority.
ERP-mediated production order
ERP remains the operational order authority and already owns the accepted MES integration.
Control: Preserve Configurix project and revision identifiers through the ERP and MES records.
PLM-to-MES technical package
MES needs released engineering structures, documents or change context from PLM alongside the order.
Control: Prove that order, structure, CAD and instruction revisions form one compatible baseline.
Event-driven order release
Accepted order or release events start asynchronous retrieval and transformation.
Control: Use stable event IDs, ordering rules, idempotency, retries, dead-letter handling and reconciliation.
Managed file or message exchange
The plant uses reviewed IDoc, B2MML, CSV, XML, JSON or another established batch contract.
Control: Treat file name, checksum, schema, sequence, rejection report and archive as contract fields.
Order-specific fabrication service
Configured dimensions require a controlled calculation, cut-list, nesting or work-package service before MES.
Control: Separate calculated output from released output and keep every derived line traceable to inputs and version.
Hybrid digital thread
ERP, PLM, MES, quality, machines and Configurix each own part of the lifecycle.
Control: Use one correlation model across configuration, order, structure, job, serial, exception and completion.
Implementation blueprint
Start with one accepted product and one real production path.
Define the operational outcome
Name the exact MES record, user decision or execution step the integration must enable.
Map system authority
Assign every product, engineering, order, material, operation, document, quality and actual field to one owner.
Choose representative fixtures
Use normal, maximum, minimum, option-heavy, revised, invalid and engineering-review configurations.
Specify the production contract
Document IDs, revisions, units, hierarchy, operations, states, documents, errors and acknowledgements.
Build safe transformation
Validate source status, map deterministic values, reject missing authority and make retries idempotent.
Prove shop-floor usability
Verify the operator sees the correct job, materials, instructions and inspections at the correct station.
Test feedback and recovery
Cover actuals, genealogy, quality, partial completion, cancellation, duplicate delivery and unavailable systems.
Operate with evidence
Monitor lag, rejection, reconciliation, change impact and support ownership after every release.
Security and resilience
Protect production even when connected systems fail.
- Separate customer, dealer, integration, plant, operator, supervisor and administrator privileges.
- Use least-privilege service identities with controlled scopes, rotation and environment separation.
- Validate every product, order, material, operation, document and actual field at the receiving boundary.
- Protect drawings, work instructions, recipes, machine information and manufacturing intellectual property.
- Authenticate events and webhooks; handle replay, duplicate, delayed, reordered and forged messages.
- Keep production systems resilient when public websites, CRM, pricing or nonessential services are unavailable.
- Record release, acknowledgement, execution, exception and administrative actions without exposing secrets.
- Define plant-network, cloud, remote-access, backup, recovery and incident responsibilities with operations.
Acceptance evidence
Test the resulting job, not only the message.
- 1A valid accepted configuration creates or updates exactly one intended downstream order and MES execution record.
- 2An unapproved, draft, technically pending or commercially rejected project cannot be released to production.
- 3Minimum, maximum and unusual valid dimensions produce the expected materials, quantities, operations and instructions.
- 4An incompatible option or missing required value is rejected before shop-floor release with a usable reason.
- 5Configuration, EBOM, MBOM, routing, drawing, instruction and price revisions remain identifiable and compatible.
- 6A repeated request or timed-out retry does not create a second order, job, material issue or completion.
- 7A changed or cancelled order updates, holds or supersedes the correct MES record according to the accepted state model.
- 8Operators at each station see only the correct jobs, documents, material and actions for their role and resource.
- 9Lot, serial or component genealogy connects the consumed material to the produced identity where required.
- 10Yield, scrap, consumption, time, quality and completion feedback reach the correct enterprise record once.
- 11A nonconformance or engineering deviation blocks, routes or permits work exactly as the approved process requires.
- 12Full reconciliation identifies missing, extra, stale, rejected and mismatched records across the chosen time window.
Failure patterns
Where configurator-to-MES projects create false confidence.
The sales configuration is sent directly to the shop floor
Commercial choices have not been transformed into an accepted production order, structure, routing or release state.
Every item list is called a production BOM
A quote line, sales BOM, EBOM, MBOM, pick list and cut list have different owners and acceptance needs.
Revision identity disappears
Operators cannot prove which product, drawing, instruction or configuration baseline they executed.
Success means the API returned 200
The receiving job may still be rejected, incomplete, duplicated, mapped wrongly or never executed.
Changes overwrite work in progress
A new configuration or engineering revision silently changes jobs already released or started.
Feedback is a final status only
Material, quantity, quality, genealogy and exception evidence cannot explain what actually happened.
Operators work around the interface
Instructions, fields or sequences do not match the real station, so execution evidence becomes unreliable.
No one owns reconciliation
Delivery gaps remain invisible because source, middleware and MES dashboards each show only their own success.
Primary technical references
Design from documented manufacturing boundaries and execution behavior.
ISA · ISA-95 enterprise-control integration
Official overview of the model, terminology and information boundary between level 4 business planning and level 3 manufacturing operations management.
Open primary sourceSAP · Digital Manufacturing integration guide
Official integration architecture for exchanging master, transaction and machine data with manufacturing execution.
Open primary sourceSAP · S/4HANA or ERP technical integration
Official order, material, yield, scrap, communication and monitoring context for SAP Digital Manufacturing integration.
Open primary sourceSAP · Order processing mode
Official documentation for ERP order-specific BOM and routing behavior in SAP Digital Manufacturing execution.
Open primary sourceSiemens · Opcenter Execution Discrete
Official MES context for high-variation discrete production, work orders, BOM and process complexity, genealogy, exceptions and change.
Open primary sourceMicrosoft · Manufacturing execution registration
Official definitions for jobs, operator time, item consumption, production-floor registration and operational feedback.
Open primary sourceNIST · Digital Thread for Smart Manufacturing
Primary public research context for connecting design, manufacturing and product-support information through open exchange.
Open primary sourceMES integration FAQ
Detailed answers for product, engineering, manufacturing, IT and operations teams.
Bring one configured product and one production path
Map customer intent to accepted manufacturing execution.
We can define Configurix, ERP, PLM and MES authority; stable identities; production-order, BOM, routing and document contracts; feedback; exceptions; recovery and working acceptance tests.