z-logo
Premium
JOB RELEASE CONTROL USING A CYCLIC SCHEDULE*
Author(s) -
BOWMAN R. ALAN
Publication year - 2002
Publication title -
production and operations management
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 3.279
H-Index - 110
eISSN - 1937-5956
pISSN - 1059-1478
DOI - 10.1111/j.1937-5956.2002.tb00496.x
Subject(s) - bottleneck , schedule , computer science , critical path method , throughput , path (computing) , job shop , algorithm , task (project management) , mathematical optimization , sequence (biology) , operations research , job shop scheduling , flow shop scheduling , mathematics , engineering , computer network , telecommunications , systems engineering , wireless , embedded system , operating system , biology , genetics
In just‐in‐time inventory management in any manufacturing setting, the general idea has been to release jobs as late as possible (to reduce inventory costs) while still having them arrive at bottleneck machines in time to maintain the desired throughput (by not starving a bottleneck machine). When a cyclic schedule is employed, the throughput is determined by a cyclic sequence of operations known as the cyclic critical path. These operations are not, in general, all performed on a single bottleneck machine. We present an algorithm for releasing jobs that treats this cyclic critical path as the bottleneck. Although this algorithm has the somewhat complex task of not delaying any of these operations on the cyclic critical path, it is greatly simplified by being able to take advantage of the fixed sequence of the cyclic schedule. The result is that the algorithm is relatively simple to implement. Although it uses a simulation‐based analysis, this analysis can all be done and the necessary results stored in advance of its use. We test the algorithm in a job shop environment with stochastic operation times. This algorithm is shown to be effective at reducing inventory while avoiding decreases in throughput.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here