Scheduling Shared Equipment Across Multiple Product Lines: Allocation Strategies

One 5-axis CNC machining center. Aerospace orders consuming 70% of its time. Commercial machining consuming the other 30%. A single machine, two product lines, two sets of customers, two different priority logics, and a plant manager sitting between them trying to keep both sides happy while meeting the monthly revenue target.

This is the shared equipment problem, and it's endemic to small and mid-size job shops. Shops in the $5M-$50M revenue range typically can't justify dedicated equipment per product line — the capital cost doesn't pencil out until utilization is consistently high enough to warrant investment. So the same machines serve multiple product lines simultaneously, creating scheduling conflicts that no infinite-capacity ERP was designed to handle.

The shops that manage shared equipment well have explicit allocation strategies, documented priority rules, and scheduling systems that enforce those rules before conflicts reach the shop floor. The shops that don't manage it well have a culture of whoever yells loudest gets the machine next — which maximizes stress and minimizes throughput simultaneously.

This post covers the core allocation strategies for shared equipment, how to model shared resources in APS software, and the customer-facing implications of every allocation decision.

For foundational context on how shared resources interact with capacity, see our guide to finite capacity planning.

Why Shared Equipment Creates Scheduling Complexity That Dedicated Equipment Doesn't

When equipment is dedicated to a single product line, scheduling decisions for that product line are independent of all others. Each product line has its own capacity pool. Overloads and underloads are internal problems with internal solutions.

When equipment is shared, every scheduling decision for one product line directly consumes capacity from the pool available to every other product line. The interactions are immediate:

• Accepting a large aerospace order in week 3 may push commercial jobs in weeks 3-4 into a capacity deficit — even if commercial demand hasn't changed.
• A quality hold on an aerospace run that requires a machine reset costs commercial capacity, not just aerospace capacity.
• Setup time optimization that favors aerospace (grouping by material family) may be setup-time-inefficient for commercial (different material families) and vice versa.

The scheduling complexity grows with the number of product lines sharing the resource. Two product lines on one machine is manageable with explicit priority rules. Three product lines with different priority logics on two machines that sometimes share and sometimes don't is an optimization problem that requires scheduling software to solve correctly.

Strategy 1: Priority-Based Allocation

Priority-based allocation assigns each product line a hierarchy that governs scheduling decisions when capacity is insufficient for all demand. Jobs from the highest-priority product line schedule first; remaining capacity is offered to lower-priority product lines in sequence.

Priority tiers are commonly assigned based on:

Contractual obligation. Defense and aerospace contracts with firm delivery dates and liquidated damages clauses are the clearest case for highest priority. A $50,000 late delivery penalty on a $200,000 order is a 25% margin hit that overrides almost every other business consideration.

Strategic account status. A customer relationship representing 20% of annual revenue may warrant priority regardless of contractual terms, because the relationship value exceeds any individual order.

Margin contribution. When no contractual or strategic differentiation exists, rank product lines by their contribution margin per unit of shared equipment time. Higher-margin product families get capacity preference.

Customer SLA commitments. If you've contractually committed to lead time windows for specific customer classes, those commitments drive priority regardless of margin.

The critical discipline in priority-based allocation is limiting tier 1. If every product line manager successfully argues their jobs are highest priority, the priority system fails. Priority rules only function when priority is genuinely scarce — when tier 1 is reserved for jobs where there are real, specific consequences for not prioritizing them.

A practical implementation: define tier 1 as "jobs with penalty clause exposure or strategic account status requiring VP approval to deprioritize." Everything else is tier 2, ranked by revenue-per-constraint-hour within the tier. The tier 2 ranking optimizes throughput. The tier 1 override protects relationships and contractual compliance.

Strategy 2: Time-Fencing Dedicated Windows

Time-fencing allocates specific time blocks on the shared resource to each product line. Aerospace gets Monday-Wednesday. Commercial gets Thursday-Friday. Within their window, each product line manages its own queue, priority, and setup sequence without competing for the resource.

Time-fencing works well when:

• Product lines have predictable, relatively stable weekly demand.
• Setup sequences within each product line are efficient (the machine runs in a family pattern within the window).
• Cross-contamination between windows is rare (most jobs complete within their allocated window).

Time-fencing fails when:

• Weekly demand variation is high (a large order can overwhelm the allocated window).
• Setup between product lines is significant (the machine loses production time at each window boundary to changeover from one product family to the other).
• Jobs routinely run long and spill into the next product line's window, creating daily boundary conflicts.

The practical fix for most time-fencing implementations is a managed buffer zone at each boundary, as described in the practitioner Q&A. The hard boundary becomes a preference, with explicit overflow capacity available to the product line whose window is ending.

Time-fencing has a significant advantage over pure priority-based scheduling: it gives each product line's schedulers a predictable, stable capacity block to plan against. When aerospace knows it has 24 hours of machine time Monday-Wednesday, it can commit to customer dates with confidence. Priority-based scheduling gives no such predictability — if commercial demand spikes, aerospace's effective capacity in a given week is unknowable until the schedule runs.

Strategy 3: Revenue-Per-Constraint-Hour Optimization

Revenue-per-constraint-hour scheduling sequences all jobs from all product lines at the shared resource by their contribution margin divided by their time requirement at the constrained work center. The job with the highest margin-per-constraint-hour runs first, regardless of product line.

This approach maximizes total shop throughput from the constraint. It is mathematically optimal for shop-level profitability. It is also politically difficult to implement because it explicitly trades lower-margin product lines against higher-margin ones in a visible way.

The calculation:

Priority Score = Contribution Margin ($) / Constraint Hours Required

A job with $12,000 gross margin requiring 6 hours at the 5-axis CNC scores $2,000/hour. A job with $4,500 gross margin requiring 1.5 hours at the 5-axis CNC scores $3,000/hour.

The second job runs first, even if the first job arrived earlier, because it generates more margin per unit of constrained resource consumed.

Revenue-per-constraint-hour scheduling requires reliable margin data per job — not just revenue, but contribution margin after direct material and labor. In job shops without job-level costing, this data often doesn't exist or isn't timely enough to use in scheduling decisions. Where the data does exist, this approach generates the highest financial return from a shared bottleneck.

Modeling Shared Equipment in APS Software

Shared equipment scheduling exposes the limits of standard ERP scheduling modules. Most ERP scheduling assigns jobs to work centers based on routing and lead time, without the ability to apply product-line-specific priority rules or time-fence constraints to a single work center.

Advanced planning and scheduling (APS) systems handle shared equipment through work center allocation logic that can encode:

Product-line capacity pools. Define a 5-axis CNC as having 40 hours per week, allocated 28 hours to aerospace and 12 hours to commercial. Each product line's scheduling engine treats its allocated pool as its effective capacity. Neither can exceed its allocation without explicit override.

Priority rule overrides per resource. The shared CNC may use contractual-priority rules for aerospace jobs and revenue-per-constraint-hour rules for commercial jobs — different priority logic for different product lines on the same physical machine.

Time-fence constraints as resource calendars. Model the aerospace window and commercial window as separate resource availability calendars for the same physical machine. Aerospace jobs see the machine as available Monday-Wednesday. Commercial jobs see it as available Thursday-Friday. Changeover time between windows is blocked in both calendars.

Conflict escalation rules. When both product lines have tier-1 priority jobs competing for the same time slot, the system should escalate the conflict explicitly rather than resolving it automatically by an arbitrary rule. Automatic resolution of genuine priority conflicts obscures the problem; explicit escalation forces the right decision-makers into the conversation.

RMDB's work center configuration supports all of these modeling approaches. See RMDB's resource scheduling capabilities for specifics on allocation pool configuration and priority rule assignment.

Customer-Facing Implications of Shared Bottleneck Decisions

Every shared bottleneck allocation decision is simultaneously a scheduling decision and a customer commitment decision. The two cannot be decoupled.

When aerospace takes shared capacity in weeks 3-4 to meet a contractual delivery, commercial customers in weeks 3-4 will receive later delivery dates. Those delivery dates need to be communicated accurately and early — not discovered when the order is already late.

This creates a specific data requirement: customer-quoted lead times must reflect actual shared-equipment availability at the time of quoting, not a standard lead time that assumes full capacity access. A commercial customer quoted 3-week lead time during a period when commercial capacity is 12 hours/week instead of 18 hours/week should be quoted 4-week lead time. Quoting standard lead time and then missing it is a service failure that was created at the quoting desk, not on the shop floor.

The shared equipment scheduling decision must therefore be visible to whoever is quoting customer lead times. In practice, this means:

Available-to-promise logic that reflects shared-equipment allocation. Sales should see committed capacity by product line across the planning horizon when quoting dates, not just overall shop load.

Demand management discipline that prevents commercial bookings from exceeding commercial capacity allocation. A $15M commercial order booked into a period where commercial capacity is already committed doesn't help — it creates a delivery crisis and a customer relationship problem simultaneously.

Early notification protocols when allocation overrides occur. If an aerospace emergency requires pulling commercial capacity in week 3, commercial customers affected in week 3 should be notified within 24 hours — not discovered when their job isn't shipped.

Real Job Shop Examples: $5M-$50M Revenue Range

Example 1: 12-person precision machining, $8M revenue. One 5-axis CNC running aerospace and commercial. Original approach: whoever was loudest got the machine. On-time delivery: 61%. After implementing priority-based allocation (aerospace contracts in tier 1, commercial by revenue-per-constraint-hour), on-time delivery reached 84% within 6 months. The key change was not the priority logic — it was making the priority logic explicit so schedulers could execute it consistently instead of responding to whoever was applying the most pressure.

Example 2: 25-person metal fabrication, $22M revenue. Two laser cutters shared between automotive tooling (high-mix, high-precision) and commercial structural fabrication (lower-mix, high-volume). Time-fencing solution: automotive on day shift, commercial on second shift. Changeover between shifts requires a 45-minute laser recalibration. Result: automotive on-time delivery improved from 71% to 89% within 3 months because automotive schedulers could finally plan to a stable, predictable capacity window. Commercial delivery improved from 79% to 85% for the same reason.

Example 3: 45-person job shop, $38M revenue. Three product lines (defense, aerospace, commercial industrial) sharing 4 CNC work centers at varying levels. Pure priority-based allocation failed because defense had blanket tier-1 status for nearly all jobs. Implemented a hybrid: time-fencing Monday-Thursday for defense/aerospace (20 hours/week each), commercial running full capacity Friday plus second-shift access Monday-Thursday. Revenue-per-constraint-hour ranking within commercial. On-time delivery across all product lines improved 12-18 percentage points within one year. More importantly, quoting accuracy improved because sales could see committed capacity by product line rather than aggregate shop load.

When Shared Equipment Signals a Capacity Investment Decision

The shared equipment scheduling problem becomes an investment decision when allocation conflicts become structural rather than episodic. Signs that a shared bottleneck has outgrown its allocation framework:

• Tier-1 jobs from multiple product lines are competing for the same time slots more than 20% of weeks.
• Overall utilization on the shared resource consistently exceeds 88-90% across product lines combined.
• Allocation override decisions are being made at VP level more than once per month.
• Customer-facing lead time quotes are being extended repeatedly to manage the allocation backlog.

At this point, the scheduling question becomes a capacity question: add a second machine, qualify an outsourcing partner for overflow, or manage demand by accepting fewer orders in lower-priority product lines. RMDB's capacity analysis tools can quantify the constraint load across product lines and model the throughput impact of each investment option — giving plant managers the data to make the capital case before the delivery crisis forces the decision reactively.

Shared equipment conflicts resolved before they reach the floor. Contact User Solutions to see how RMDB handles multi-product-line capacity allocation, priority rules, and time-fencing for shared bottleneck resources. Trusted by GE, Cummins, BAE Systems for 35+ years of finite capacity scheduling.