Your Schedule Looks Full. Which Epicor Jobs Are Consuming the Capacity That Matters?
A full schedule does not explain where delivery risk actually sits. Management needs to see which constrained resources, queues, changeovers and overloaded operations are driving job completion risk.
The short answer
A full Epicor schedule does not tell management which jobs are creating delivery risk. The useful capacity view identifies the resources that constrain flow, shows which jobs are competing for those resources and distinguishes productive load from queue, changeover, downtime and planning noise.
Capacity management should focus on the few places where an extra hour actually changes customer delivery or cost.
How this connects to the pillar
The wider plan-to-profit model is covered in Epicor Has the Orders. Can Management See Which Ones Will Actually Make Money?. Capacity is one of the key tests of whether booked demand can be executed profitably.
Utilisation can hide the real bottleneck
A plant may report moderate average utilisation while one work centre runs continuously.
The average looks comfortable because unconstrained resources dilute the pressure.
Management needs a different question: which operation is limiting throughput for the jobs that matter now?
That bottleneck can change by product mix, shift, tooling, labour skill or maintenance condition.
Separate load from queue
High scheduled hours do not always mean useful work is flowing.
Jobs may wait because material is missing, tooling is unavailable, prior operations are incomplete or priorities changed.
If all scheduled load is treated equally, the capacity picture overstates executable demand.
A better view separates work that can run from work that is only occupying the schedule.
Include setup and changeover consequences
Two schedules with the same total hours can have very different practical capacity.
A sequence that creates repeated changeovers may consume more time and introduce more variability than a stable product-family run.
Where setup matters materially, capacity review should include sequence effects.
Otherwise planners may believe capacity exists on paper while operations experiences a much tighter constraint.
Identify jobs that consume scarce capability
Some resources are constrained because of equipment.
Others are constrained because only certain people can perform the work.
Special inspection, programming, certification, engineering support or skilled manual operations can become capacity limits even when machine hours look available.
Epicor planning should be interpreted alongside those real capability constraints.
Use bottleneck visibility to prioritize, not panic
When capacity is constrained, every job cannot be first.
Management should define the priority logic.
Possible considerations include:
- customer commitment;
- downstream dependency;
- margin;
- strategic importance;
- lateness risk;
- material expiry;
- service impact;
- contractual consequence.
The exact rule will differ.
The important point is that supervisors should not need to renegotiate priority informally every shift.
Measure lost capacity by cause
When a constrained resource is idle, the cause matters.
Examples include:
- material shortage;
- missing tooling;
- quality hold;
- labour absence;
- maintenance;
- engineering clarification;
- upstream delay;
- schedule change;
- no operator despite machine availability.
This evidence tells management whether the capacity problem requires investment or process improvement.
Buying another machine will not solve a bottleneck caused mainly by missing material.
Treat overtime as a capacity signal
Overtime can be a legitimate response to peak demand.
Persistent overtime on the same constrained resource is different.
It may indicate a structural capacity gap, unstable scheduling, poor sequence, weak maintenance, underdeveloped skills or demand that should be priced differently.
Track what overtime is protecting.
That makes the cost part of the profitability conversation.
Look at capacity before accepting priority changes
An urgent order does not enter an empty system.
Moving it forward displaces something else.
Before changing priority, management should know which jobs will move, whether the bottleneck will require overtime and what customer or margin consequence follows.
This makes priority decisions explicit rather than allowing schedule disruption to spread invisibly.
Use queue age as an operational indicator
Hours of load describe how much work exists.
Queue age describes how long work has been waiting.
An operation with moderate load but old waiting jobs may have a sequencing, material or execution problem.
Combine load with queue age to identify where work is stuck.
What management should measure
Useful indicators include:
- load on constrained resources;
- executable versus blocked load;
- queue age;
- setup/changeover time;
- lost bottleneck hours by cause;
- overtime by constrained resource;
- jobs displaced by priority changes;
- capacity-related promise misses;
- jobs waiting for specialist skills;
- repeated overload by product family.
These measures show whether the constraint is physical capacity or operating discipline.
ACC context
ACC supports Epicor planning and manufacturing operations. Capacity data becomes most useful when it is tied to real execution conditions and customer commitments rather than reviewed only as aggregate utilisation. Explore ACC’s Epicor capabilities.
Operational review point
Choose the resource currently believed to be the main bottleneck.
Take one week of scheduled and actual work.
Separate productive run time, setup, waiting, downtime and blocked time. Then identify which jobs were delayed and why.
If blocked time dominates, the improvement may be material or process readiness rather than additional physical capacity.
Distinguish theoretical from effective capacity
Calendar hours are not the same as effective capacity.
Maintenance, breaks, staffing, planned downtime, normal yield and setup can all reduce the hours available for productive work.
Capacity assumptions should be realistic enough that the schedule does not rely on hours that operations never truly has.
Review effective capacity when the same resource appears overloaded every planning cycle.
Develop alternate capability deliberately
Where one resource or skill repeatedly constrains delivery, management may reduce risk by developing alternate capability.
That can mean cross-training, qualified alternative equipment, tooling changes, subcontract options or product redesign.
The decision should be based on the economic consequence of the bottleneck, not simply on utilization percentage.
Capacity data becomes strategic when it informs these choices.
Connect maintenance to capacity review
Unplanned downtime on a constrained resource has a different consequence from downtime on an unconstrained one.
Maintenance priorities should therefore consider production criticality as well as equipment condition.
If the same constrained asset repeatedly drives customer delay, the business case for preventive work, spares or redundancy becomes clearer.
Review batch size as a capacity decision
Batch size changes how constrained capacity is consumed.
Large batches can reduce setup frequency but increase queue time and WIP. Small batches may improve flow but create more changeover.
The right balance depends on the product mix and the economics of the constrained resource.
Capacity review should therefore consider lot-size policy rather than treating demand quantity as a fixed scheduling fact.
Use capacity evidence in make-or-buy decisions
When a constrained operation repeatedly limits profitable demand, subcontracting can be an alternative to capital investment.
But the decision should include quality, lead time, supplier reliability and total economic effect.
Epicor capacity and job-cost evidence can help management compare internal overload with the true cost of outside processing.
This turns capacity planning into a strategic sourcing input rather than only a scheduling exercise.
Measure queue time against processing time
A job may spend far more time waiting for a constrained resource than actually being processed.
That ratio is useful because it shows whether the bottleneck problem is true processing shortage or weak flow around the resource.
Long queues can result from releasing too much work, unstable priority or poor material readiness.
Reducing queue can improve lead time even when the machine itself does not run faster.
Review alternate routings with real economics
An alternate resource may technically perform the operation but at a different speed, quality risk or cost.
Capacity planning should not assume all alternatives are equivalent.
Use actual run time, setup, yield and cost evidence when deciding whether alternate routing is a genuine recovery option or only an emergency path.
Keep the capacity model current
Resource calendars and available hours should change when shift patterns, staffing or maintenance assumptions change materially. A capacity model that nobody maintains will eventually teach planners to ignore it, forcing them back to local judgment and spreadsheets.
Review this evidence during normal planning meetings, not only when delivery fails.
Frequently asked questions
Is the most highly utilised resource always the bottleneck?
No. The practical bottleneck is the resource or capability limiting flow for the current demand mix.
Should blocked jobs remain in the capacity plan?
They may need to remain visible, but distinguish blocked load from executable work so planners understand what can actually run.
Does overtime prove that more equipment is needed?
Not necessarily. Review the causes of overtime and lost productive time before assuming the constraint is equipment quantity.
How often can the bottleneck change?
It can change with product mix, staffing, maintenance, material and priorities, so the constraint should be reviewed rather than assumed permanently.