Discrete order release is based on periodic observations of workload in the shop floor. At fixed periods of time, workload on the shop floor is computed, and the decision to release orders is taken. When the orders are released periodically, release mechanisms need the specification of a release period. The length of this period must be less than the smallest slack of the orders in the pool, for avoiding orders’ lateness. Past research (e.g. Land, 2006) has shown, however, that the choice of an appropriate period between releases is a delicate decision, greatly influencing shop performance and that, non-periodic, i.e. continuous, release methods should be emphasized within future research. A long release period may unnecessarily delay orders in the pool (and eventually increase the time they spend in the entire system) and creates a higher risk of resources starvation. A short release period, on the other hand, may hinder the release of orders that could contribute to stable workloads and of orders with high processing content and long routings, negatively affecting the timing of release. The reduced costs of feedback information and the greater simplicity of discrete order release are the most likely explanations for its use by practitioners and most researchers (Bergamaschi et al., 1997).