High-Mix EMS Changes Every Day. How Do You Keep Production Under Control?
High-mix EMS operations face changing demand, shortages, priorities, setups and WIP every day. Control comes from connecting forecast, scarce-component allocation, sequencing, WIP status, subcontracting and delivery commitments on an enterprise-grade Epicor foundation with Epicor Mars industry execution.
The short answer
High-mix EMS production stays under control when changing priorities are converted into explicit operating decisions instead of constant local firefighting. The business needs one connected view of demand confidence, component readiness, scarce-material allocation, line sequence, WIP status, outside processing and customer delivery risk.
That requires two layers working together. Epicor provides the enterprise-grade ERP foundation for orders, purchasing, inventory, planning, finance and governance. Epicor Mars adds the electronics/EMS industry layer for barcode-driven execution, component identity, WIP status, quality, traceability and shop-floor control.
The objective is not to freeze a high-mix factory. Change is normal. The objective is to make each change visible enough that management understands what moved, why it moved, what was displaced and what consequence follows.
High mix creates a different control problem
In a stable high-volume environment, a production plan can remain relatively consistent.
High-mix EMS behaves differently.
A typical day can include:
- one customer accelerating an order;
- a critical component arriving late;
- another component failing incoming inspection;
- an ECN changing the product revision;
- an SMT feeder setup taking longer than expected;
- a pilot build requiring engineering support;
- one job waiting at test;
- another leaving the factory for coating;
- a third returning from rework.
None of these events is extraordinary on its own.
The control problem comes from their interaction.
When each team responds locally, the factory can become busy while the customer schedule becomes less reliable.
Start by separating demand types. Not all demand deserves the same operational commitment.
Forecast demand can guide purchasing and capacity preparation.
Firm orders create stronger obligations.
Customer expedites may justify priority changes, but only after the displaced work is understood.
Internal planning signals should not be mistaken for customer commitments.
A useful demand model distinguishes:
- forecast;
- planned order;
- firm customer order;
- engineering/NPI demand;
- service or repair demand;
- approved expedite.
Forecast, Firm Order or Customer Expedite: Which Demand Should Drive EMS Planning? focuses on how to keep those signals from creating unnecessary churn. Scarce components create management choices. When one component is short and several orders need it, the system cannot solve the business decision by itself.
Management needs to choose.
Useful criteria can include:
- contractual due date;
- customer priority;
- strategic importance;
- order value or margin;
- remaining kit readiness;
- availability of an approved alternate;
- partial-shipment option;
- expected recovery date;
- downstream capacity.
The important point is that allocation should be a controlled decision rather than the result of whoever escalates first.
One Component, Three Urgent Orders: Who Gets the Scarce Stock? examines that governance.
Sequence the line around real changeover cost. Earliest due date is important, but high-mix SMT has physical setup consequences.
Two jobs can be equally urgent yet create very different changeover burden.
A sequence can be improved by considering:
- common components;
- feeder setup;
- stencil or tooling;
- program readiness;
- board family;
- material availability;
- inspection or test dependency.
The objective is not to optimize setup at the expense of customer commitment.
It is to make the trade-off explicit.
Too Many Changeovers? How Do You Sequence High-Mix SMT Without Breaking Priorities? looks at the execution logic.
WIP status is more than open or complete
An ERP work order can remain open for many reasons.
The production-control team needs to know whether the WIP is:
- waiting to start;
- waiting for material;
- queued at an operation;
- under test;
- on quality hold;
- in rework;
- waiting for engineering;
- at a subcontractor;
- complete but waiting for final release.
Without these distinctions, every open order looks equally active.
The Work Order Is Open. Where Is the WIP—and Why Has It Stopped? explains why WIP state is essential for high-mix control. Outside processing must remain part of the job. Some EMS products leave the plant temporarily for coating, machining, special inspection, programming or another external process.
That handoff should not make the work disappear from production control.
The business still needs to know:
- what quantity left;
- which revision;
- which lot or serial identity;
- expected return;
- supplier status;
- quality disposition;
- next operation.
The Job Left the Factory for Outside Processing. Do You Still Control It? covers how to preserve continuity.
Customer promise must reflect operational evidence. A due date in ERP is not automatically a reliable customer promise.
The date becomes stronger when critical material, constrained capacity, WIP position, test requirements and subcontract return all support it.
Customer service therefore needs an operational view of delivery risk, not only a requested or planned date.
Can You Promise the Ship Date Before Material, Capacity and WIP Agree? explores this final connection. Build one priority model. A factory cannot operate efficiently if every department maintains its own priority list.
Sales may prioritize customer value.
Planning may prioritize due date.
Production may prioritize setup efficiency.
Purchasing may prioritize shortage recovery.
Quality may prioritize held material.
Management needs a common rule for resolving conflicts.
The rule does not need to be mathematically perfect.
It needs to be transparent enough that people understand why one job moved ahead of another.
Separate normal priority from expedite
If half the jobs are urgent, the label has lost meaning.
Define what qualifies as an expedite.
Examples might include:
- contractual consequence;
- major customer escalation;
- line-down risk;
- approved recovery action;
- executive decision.
The expedite should have an owner and an expiry.
A job should not remain permanently “hot” after the original reason disappears. Make displacement visible. When an urgent job moves forward, something else usually moves backward.
Record the displaced orders where the effect is material.
This forces the organization to acknowledge the consequence.
It also improves customer communication because management can see which commitments are now at risk. Use frozen windows carefully. High-mix planning still benefits from a short execution window that is protected from casual change.
The window can be hours, a shift or several days depending on the operation.
Inside it, changes should require stronger approval because material has been staged, feeders prepared, operators assigned and downstream processes coordinated.
A frozen window should not prevent real emergency response.
It should make change cost visible.
Protect constrained resources. The most important resource may not be the SMT line itself.
It could be:
- selective solder;
- conformal coating;
- functional test;
- programming;
- AOI review;
- specialized manual assembly;
- a skilled technician.
High-mix control should identify which resource is deciding flow for the current mix.
Optimizing unconstrained operations will not fix the bottleneck.
Use WIP age as an exception
Quantity of WIP matters.
Age of WIP often tells management more.
A job sitting for several days between operations can indicate:
- hidden shortage;
- quality hold;
- test bottleneck;
- engineering question;
- subcontract delay;
- priority confusion.
Age-based exceptions help surface work that is disappearing inside the factory. Keep quality status in production control. A job can be physically at the next operation but not released by quality.
Material can be present but on hold.
Rework can be complete but waiting for disposition.
Quality status should therefore be part of the same execution picture.
This is especially important in electronics where traceability and customer-specific controls can make a small hold operationally significant.
Use Epicor Mars to capture industry-specific events. Epicor provides the enterprise context.
Epicor Mars adds events that are closer to electronics execution:
- material scan;
- lot/serial identity;
- operation start/complete;
- WIP movement;
- inspection;
- defect/rework;
- component consumption;
- genealogy.
These events make the enterprise work order more informative without creating a competing ERP. Keep enterprise ownership clear. A layered architecture works only when data ownership is explicit.
Epicor should remain authoritative for enterprise transactions such as sales orders, purchasing, inventory valuation, planning and finance.
Epicor Mars should handle the EMS-specific operational interactions that need a more focused shop-floor experience.
The integration should return the required material, production, quality and completion events to the enterprise record.
Manage change by exception
The production-control team should not manually review every normal order every hour.
Focus on exceptions such as:
- critical component shortage;
- due date at risk;
- WIP age above threshold;
- quality hold;
- repeated rework;
- subcontract late return;
- schedule movement inside frozen window;
- expedite displacing another customer order.
Exception-driven control keeps attention on the small number of jobs that need a decision. Use priority rules that survive shift changes. A production-control model is weak if only one planner understands the true priority.
The priority logic should be visible enough that another shift can continue the same decisions.
Useful evidence includes:
- customer commitment;
- expedite approval;
- material readiness;
- WIP position;
- constrained resource;
- shortage recovery;
- quality status.
The goal is not to eliminate judgment.
It is to stop judgment from becoming private knowledge.
Distinguish system date from management priority. A due date can remain unchanged while management temporarily changes the sequence.
Do not hide the priority decision by editing dates solely to force the schedule.
Preserve the customer commitment and represent the operational priority separately where possible.
This keeps historical promise performance understandable. Review schedule churn as a cost. Every near-term change can trigger:
- material restaging;
- feeder preparation changes;
- extra setup;
- interrupted WIP;
- new customer communication;
- overtime.
Track significant schedule movement.
If the same job moves several times before starting, the business may be spending real capacity on planning noise.
Use one escalation path for blocked jobs
When a job is blocked, the production team should know who owns the next decision.
Examples:
- purchasing for supply;
- quality for inspection/hold;
- engineering for revision or deviation;
- planning for allocation;
- customer service for date change.
A clear escalation path reduces time spent forwarding messages around departments. Close the loop between flow and financial impact. High-mix instability can affect margin through premium freight, overtime, setup, scrap and idle time.
Epicor provides the enterprise financial context.
Epicor Mars provides the execution evidence that explains why those costs occurred.
Together they allow management to connect operational instability with the jobs and customers that created it.
Define what “under control” means. High-mix control should not be judged by whether nothing changes.
A better test is whether the organization can answer, at any point:
- which orders are most at risk;
- which component or process is driving that risk;
- what decision has been made;
- who owns the next action;
- what customer commitment changes if the issue is not recovered.
When those answers are available from one connected operating record, management can respond to volatility without turning every exception into a crisis.
That is the practical difference between a flexible factory and an unstable one.
Keep the review rhythm predictable. Volatile factories still benefit from a stable management cadence.
Use a short daily exception review for near-term execution and a separate weekly review for recurring structural issues such as chronic shortages, setup loss, subcontract delay and test bottlenecks.
This prevents every problem from being treated as an immediate scheduling emergency while still keeping the urgent decisions visible.
That separation also gives management time to solve recurring root causes instead of letting every daily exception return as tomorrow's emergency.
This makes high-mix control sustainable across shifts, sites and changing customer pressure.
What management should measure
Useful measures include:
- forecast-to-firm conversion;
- expedites created and expired;
- scarce-component allocation decisions;
- jobs displaced by priority change;
- SMT changeovers;
- schedule changes inside frozen window;
- WIP age by operation;
- work orders on quality hold;
- subcontract WIP overdue;
- jobs with customer date unsupported by current material or capacity;
- manual reconciliation between Epicor and shop-floor records.
The purpose is not more dashboards.
The measures should help management understand why flow is unstable.
A practical daily high-mix review
Use a short exception review.
For each at-risk job, ask:
1. What is the customer commitment?
2. Is critical material ready?
3. Is any component allocated elsewhere?
4. What is the next constrained operation?
5. Where is the WIP physically and operationally?
6. Is quality or rework blocking progress?
7. Is any subcontract step outstanding?
8. If priority changes, what job is displaced?
9. What customer date changes if nothing is done?
This gives planning, purchasing, production and customer service a common operating picture.
Where Epicor Mars fits in high-mix production control
For high-mix production control, the key system-design question is how to keep enterprise control and electronics-specific execution on the same operating thread. Epicor provides the enterprise-grade ERP foundation for customer orders, purchasing, inventory, planning, costing, finance, approvals and governance. Epicor Mars extends that foundation with the EMS industry context needed at the point of work, including demand class and execution status.
That connection is directly relevant to High-Mix EMS Changes Every Day. How Do You Keep Production Under Control?. High-mix EMS operations face changing demand, shortages, priorities, setups and WIP every day. Control comes from connecting forecast, scarce-component allocation, sequencing, WIP status, subcontracting and delivery commitments on an enterprise-grade Epicor foundation with Epicor Mars industry execution. When the Epicor Mars execution record stays tied to the Epicor work order, material and customer context, management can compare the business commitment with what the factory actually executed without maintaining a second source of truth.
For high-mix production control, that complementary positioning is the point: Epicor remains the enterprise-grade foundation, while Epicor Mars adds the EMS workflows needed to make this particular control operational on the factory floor. Explore Epicor Mars for electronics manufacturing.
Frequently asked questions
Can high-mix EMS ever have a stable schedule?
Yes, but stability means controlled change, not zero change. Protect near-term execution while allowing explicit exceptions.
Should the system decide which customer gets scarce components?
It can provide evidence, but allocation is often a management decision involving customer, commercial and operational priorities.
Is WIP visibility the same as machine monitoring?
No. WIP visibility answers where the job is, what state it is in and why it is waiting.
Why is Epicor still important if Epicor Mars manages shop-floor execution?
Because enterprise orders, purchasing, inventory, planning, costing, finance and governance need a robust system of record. Epicor Mars extends that foundation with electronics-specific execution.
What is the first improvement to make?
Choose one daily priority meeting and replace separate spreadsheets with one exception view that connects material, WIP, quality and customer commitment.