Workload Control (WLC)

1. What Is Workload Control (WLC)?

Workload Control (WLC) is a production planning and control approach that regulates how much work enters a factory’s shop floor. Rather than starting every available order immediately, it holds jobs in a pre-shop pool and releases them against workload limits. Its purpose is to control congestion, production lead times, and work in process.

For manufacturers of industrial machinery and capital equipment, the central question is practical: which jobs should start now, given their delivery commitments and the demands they will place on machining, fabrication, assembly, and testing?

2. Origin and Background

Origin: WLC developed through several research streams rather than one universally accepted inventor. Its documented antecedents include Oliver Wight’s 1970 work on input/output control. Wolfgang Bechte’s load-oriented order-release research appeared in the early 1980s; subsequent contributions included Hans-Peter Wiendahl’s load-oriented manufacturing control and the hierarchical approaches developed by Brian Kingsman, Linda Hendry, and colleagues at Lancaster University.

The underlying problem was excessive and unstable queues in manufacturing. The research developed beyond releasing jobs to encompass customer enquiries, delivery-date quotations, order acceptance, and capacity decisions. WLC therefore remains broader than a shop-floor scheduling rule: it connects commercial commitments with production loading.

3. How Workload Control (WLC) Works

In the abbreviation, W and L denote workload, and C denotes control; they are not separate analytical stages. Workload is normally expressed as estimated operation time at each controlled resource, rather than simply the number of orders.

A comprehensive WLC approach connects several decisions:

• Customer enquiry: Evaluate whether the requested delivery date is realistic given existing commitments.
• Order acceptance: Decide which commitments to take on and whether capacity adjustments are needed.
• Order release: Admit selected jobs from the pre-shop pool without exceeding defined workload norms.
• Shop-floor control: Sequence released work and update workload records as operations finish.

A workload norm is a control threshold, not a resource’s theoretical maximum capacity. Direct load is work already waiting at a resource; indirect load is work still upstream that will require that resource. Aggregate methods account for both. Corrected-aggregate methods adjust contributions using routing position; this changes the accounting, not the processing actually required. Norms must match the selected accounting method.

Release can be periodic, continuous, or hybrid. Hybrid methods can permit controlled releases between scheduled reviews to prevent resource starvation. Input control regulates incoming work; output control adjusts capacity, for example through additional staffed hours. Neither should be confused with maximizing every machine’s utilization.

For an equipment factory, use production jobs or subassembly batches as the units of control, while preserving their connection to the finished machine. Measure pool waiting as well as shop-floor throughput time: moving queues upstream is not, by itself, a customer lead-time improvement.

4. When to Use Workload Control (WLC)

WLC is particularly well suited to high-variety, make-to-order job shops, where orders follow different routes and compete for shared resources. Relevant questions include whether to release another fabricated frame, whether a machining queue reflects excessive loading, and whether a promised shipment requires additional assembly or testing capacity.

It is less compelling as the primary control for a stable, repetitive production line. Although research includes successful make-to-stock applications, that does not establish universal suitability. Engineering-intensive equipment projects also require controls for design readiness and assembly dependencies beyond basic workload accounting.

Useful inputs include routings, operation-time estimates, completion feedback, due dates, and resource availability. Bring planners, supervisors, engineering, procurement, and sales into the design. Plan effort around data cleanup, historical testing, and a live pilot—not just an executive workshop. WLC is misleading when nominal capacity substitutes for staffed capability, or incomplete routings conceal downstream demand.

5. How to Apply Workload Control (WLC): Step-by-Step

The following sequence is a practical adaptation for an equipment factory, not a single standardized WLC methodology. Implementation research emphasizes the importance of contextual fit, organizational responsibilities, and usable information systems.

1. Clarify the decision and scope.

   Define the release boundary, controlled resources, product families, and delivery objective. Start with one coherent production area. Distinguish manufacturing completion from shipment, customer acceptance, and commissioning.

2. Gather and validate inputs.

   Extract open orders, routings, remaining operation hours, due dates, and capacity calendars. Check estimates with operators. Identify missing components, drawing approvals, tooling, inspection requirements, and outsourced operations.

3. Define the units of analysis.

   Use identifiable production jobs or batches. Group machines only where they are genuinely interchangeable. Track scarce labor separately when a machine’s availability does not imply an appropriately skilled operator is available.

4. Build the control artifact.

   Create a pool register and resource-load dashboard. Record each job’s readiness, priority, route, and workload contributions. Specify the accounting method, norms, release cadence, and how completed operations remove load.

5. Interpret the results.

   Identify which resource prevents each release. Separate genuine congestion from stale records or unrealistic standards. Check whether an apparently empty downstream station has sufficient work approaching it.

6. Translate findings into operating rules.

   Redesign production planning and scheduling around explicit release permissions, dispatch priorities, capacity responses, and escalation rules. When an urgent job cannot fit, decide deliberately whether to add capacity, subcontract, or revisit the commitment.

7. Test sensitivities.

   Replay representative order histories or simulate alternative norms. Test downtime, longer setups, rework, changing order mix, and labor shortages. Evaluate delivery performance and total lead time alongside released workload and throughput.

8. Align stakeholders and iterate.

   Assign a release owner, completion-data owners, and exception authority. Pilot through representative operating conditions. Review overrides and recalibrate before extending the design to other factories.

6. Example: Workload Control (WLC) in Action

Fictional example: Northbridge builds customized packaging machinery. Its planners release component jobs as soon as drawings are approved. Machining queues grow, while assembly supervisors repeatedly expedite missing subassemblies.

The operations director selects WLC to control job admission. The pilot covers machining, assembly, and testing, using an unweighted aggregate-load method. Jobs enter the eligible pool only after required drawings, materials, and tooling are ready. The following numbers are illustrative operation-hours, not industry benchmarks.

Job A would raise machining load to 104 hours, exceeding its norm, so it remains in the pool. Job B fits all three limits and can be released. After eight machining hours are completed, Job A also fits, provided other loads have not increased.

Because A has the earlier delivery commitment, the planner also evaluates additional qualified machining capacity rather than treating the limit as an excuse for lateness. Northbridge introduces daily load updates, tracks subassembly availability at assembly, and judges the pilot on delivery reliability, total lead time, and sustained throughput—not merely fewer jobs on the floor.

7. Strengths and Limitations

Strengths

• Controls admission: Addresses congestion before another job joins the production queues.
• Handles variety: Uses routing-specific work content instead of assuming every order consumes equal capacity.
• Connects promises and production: Links delivery quotations with workload and capacity decisions.
• Complements dispatching: Release control and shop-floor sequencing can reinforce each other.

Limitations

Norm selection and load accounting materially affect results. Tight limits can starve resources; loose limits can leave congestion largely unchanged. Research also identifies a gap between promising simulation results and practical implementation, including human behavior, data requirements, and organizational adoption.

For equipment production, supplement WLC wherever parallel subassemblies must converge, specialist qualifications restrict capacity, or external processing determines timing. A workload threshold cannot resolve an unfinished design, guarantee material availability, or provide a detailed feasible assembly schedule.

8. Common Pitfalls and How to Avoid Them

• Counting orders instead of hours: A replacement bracket and a complex housing consume different resources. Use operation-level work content.
• Ignoring future load: A short machining queue can conceal substantial work approaching from fabrication. Include indirect load consistently.
• Releasing incomplete jobs: Starting without drawings or purchased components creates blocked work. Establish readiness gates.
• Copying another factory’s norms: Routing, capacity, and accounting differences invalidate borrowed thresholds. Calibrate locally.
• Hiding pool delays: Better shop-floor statistics can mask worse customer performance. Track the complete order journey.
• Allowing uncontrolled overrides: Expedites can defeat the release policy. Require approval and record consequences for displaced orders.

For a multi-factory rollout, program management support can coordinate routing-data cleanup, system changes, supervisor training, and pilot acceptance. Assign responsibility for these activities before treating the release algorithm as the implementation plan.

9. How Workload Control (WLC) Relates to Other Frameworks

Material requirements planning

Material requirements planning (MRP) establishes what components are needed and when. WLC addresses whether jobs should enter production given resource workloads. Use materials planning to establish readiness, then apply workload-based release; neither substitutes for the other.

Kanban and constant work in process

Kanban authorizes replenishment through defined loops, while constant work in process (CONWIP) limits work within a controlled production system. WLC offers more differentiated resource-load accounting for varied routes and processing requirements. Prefer the simplest control that fits the production configuration; simulation comparisons do not establish a universal winner.

Theory of Constraints and detailed scheduling

Theory of Constraints emphasizes the system’s limiting constraint; WLC can assess loads across multiple resources. Constraint-focused control may be simpler where one dominant bottleneck governs flow. WLC becomes attractive when different order mixes stress different resources. Detailed scheduling answers the subsequent question: which released operation should run on which resource, and when? Combine release control with scheduling where equipment builds have demanding sequencing or assembly dependencies.

10. Key Takeaways

• WLC controls entry into production; it is not merely a priority list.
• High-variety, make-to-order shops are its natural application.
• Use routing-specific workload and locally calibrated norms.
• Connect release decisions with delivery promises and capacity responses.
• Judge success across pool waiting, shop-floor time, throughput, and delivery.
• Supplement the method for material, engineering, and assembly dependencies.

11. FAQs About Workload Control (WLC)

Can a small equipment manufacturer use WLC?

Yes. Begin with a manageable production area, a visible order pool, and a few clearly defined resource groups. The essential requirement is disciplined information and release decisions, not an elaborate software platform. Validate the design before expanding its scope.

What data is essential for WLC?

At minimum, identify each job’s route, estimated remaining operation times, delivery commitment, readiness, and completion status. Establish credible resource availability. More detailed setup, rework, and labor information improves interpretation, but inaccurate detail should not be mistaken for precision.

Does WLC replace detailed scheduling?

No. WLC primarily governs admission and workload, while detailed scheduling allocates operations to resources and times. An industrial equipment factory may need both: controlled release to reduce congestion, followed by sequencing that respects tooling, labor, testing, and assembly dependencies.