Dynamic Instabilities and Stabilization Methods in Distributed Real-Time Scheduling of Manufacturing Systems 4: A Run-Truncating Priority-Queue Supervisor Keeps Every Buffer Bounded When ρₘ < 1Research Paper
Motivation
A flexible manufacturing system routes several part types through a set of machines; a machine that switches from one kind of part to another must spend a set-up time first. Each machine has to decide, in real time and from local information only, which of its waiting buffers to work on and for how long. Long runs waste little time on set-ups but starve other buffers; short runs do the opposite.
Kumar and Seidman (IEEE TAC 35(3), 1990) showed in §III of the paper that natural distributed rules (clearing policies, which keep processing a buffer until it is empty) can be unstable when parts revisit machines, even though every machine has enough capacity. Their §IV gives a sufficient condition for a subclass of such rules to be stable, which is stricter than the capacity condition. §V, the subject of this mission, asks for something stronger: a simple, distributed mechanism that a supervisor can add to any scheduling policy and that makes the system stable whenever the capacity condition alone holds.
Timeline. Perkins and Kumar (1989) proved that the capacity condition is sufficient for the existence of some stabilizing policy, and that every clear-a-fraction policy is stable on acyclic systems. Kumar and Seidman (1990) gave the instability examples for nonacyclic systems and the universal supervisor formalized here.
Setting
There are part types and machines. Part type arrives at rate and follows a route of operations; operation is done by machine and takes per part. Parts awaiting operation wait in buffer , with level . Machine serves , and switching from to costs . Flows are continuous: a machine processing a nonempty buffer drains it at rate , the output feeds instantly, and a machine on an empty buffer passes its inflow through. Each machine works in runs: a set-up, then a processing phase on one buffer.
The load of machine and the capacity condition are
The system is stable if for every buffer.
The supervisor picks with
and thresholds . It truncates every processing run of at ; it keeps a first-come first-served queue of the buffers that are not being processed and whose level exceeds ; when a run ends and , the head of is processed next, for exactly unless it clears earlier. When is empty the underlying policy is free. Write (26) and , the backlog of part type for machine .
Formalization targets
Goal: Theorem 2
Under (1), (24) and , every supervised trajectory, from every initial state, satisfies
The bound is allowed to depend on the trajectory; no uniformity in the initial state is claimed.
Milestones: Lemma 1
- A buffer that enters at completes its next run by (25).
- If it enters with , that run lowers the backlog: .
- A buffer that enters at and stays above (strictly above after ) up to has .
- Any interval on which has length at most .
Significance
The theorem separates two concerns of real-time scheduling. The underlying policy can be tuned for performance (low set-up overhead, short buffers) without any stability analysis; the supervisor guarantees stability under exactly the condition that is necessary for it. The mechanism is distributed: each machine uses only its own buffer levels. With it enforces FCFS with truncated runs; with large and it never intervenes on a policy that is already stable, so the degree of intervention is tunable. Combined with the §III instability examples, it shows that instability of clearing policies is a design defect that a local safeguard removes.
The result is proved in the paper; to our knowledge it has no machine-checked proof. This mission produces a formal model of continuous-flow manufacturing systems with set-up times and runs, a formal definition of the supervisor, and the four parts of Lemma 1 as reusable statements about it. Part 3) is stated with a corrected hypothesis (see Formalization scope).
Difficulty
The underlying policy is arbitrary, so no structure of the trajectory between interventions can be used: the policy may idle on empty buffers, switch at will, and re-select a buffer as soon as its run is truncated. The natural approach of bounding the total work at a machine fails, because work arrives at machine from upstream machines whose behaviour depends on itself through re-entrant routes, so a machine-by-machine argument is circular. A further difficulty is that the supervisor acts only on buffers above their thresholds, so a buffer can be ignored for as long as it sits at or below ; any bound has to account for the time spent below the threshold and for repeated re-entries into , with a set-up paid at each.
Formalization scope
- Model. Part types
Fin P, machinesFin M, buffersΣ p, Fin (n p); paper index is Lean index . Time is real with . Set-up times satisfy : a set-up is paid only on a switch. No transport delays or assembly, as in the paper. - Runs. Each machine is always in a run (no idling outside runs); a run is never cut during its set-up; run starts do not accumulate; zero-length runs are allowed. Processing is at rate at most and only in a processing phase of , and at exactly while is nonempty.
- Queue. Membership of is determined by the trajectory: not on the current run and level strictly above . The FCFS key is the start of the current sojourn; ties, including the initial queue at time , are broken arbitrarily, so every initial queue order is covered. A buffer whose run just ended is in at that instant if its level exceeds .
- Lemma 1. Parts 1)–3) assume, as the page does, that the buffer enters at . Part 3) adds on : with the printed non-strict hypothesis the buffer can sit at exactly , never be re-queued, and wait arbitrarily long. In 4), is .
- Ruled out. The base policy is not restricted to clearing, CAF or any fixed rule, the system is not restricted to few machines or acyclic routes, and the hypothesis of the goal is (24), not . A non-vacuity witness (one machine, one buffer) shows the class of supervised trajectories is nonempty.
- Reusable. The trajectory model (runs, set-ups, processing law) is the same as in the other missions of this series and applies to any distributed scheduling policy with set-ups.
Contributions welcome: proofs of the Lemma 1 parts, and lemmas on the model (Lipschitz continuity of levels, monotonicity of a buffer's level while it is not processed).
Selected references
- P. R. Kumar and T. I. Seidman, Dynamic instabilities and stabilization methods in distributed real-time scheduling of manufacturing systems, IEEE Trans. Automat. Control 35(3), 289–298, 1990. https://doi.org/10.1109/9.50339
- J. R. Perkins and P. R. Kumar, Stable, distributed, real-time scheduling of flexible manufacturing/assembly/disassembly systems, IEEE Trans. Automat. Control 34(2), 139–148, 1989. https://doi.org/10.1109/9.21085