| A look-ahead period can be defined to decide which jobs should be pulled forward to, say, minimize setups, when generating the production schedule.
In-built Scheduling Rules
The in-built scheduling rules are:-
- Preferred Sequence (by job attribute, setup time, process time, critical ratio)
- Minimize Work In Process (WIP) Forwards
- Minimize WIP Backwards
- Selective Bottleneck (TOC)
- Dynamic Bottleneck
- Minimize Overall Setup
Campaigning
The preferred sequence rule is data driven. You can select the criteria by which the preferred sequence is created. Critical ratio is used, for example, to minimize late jobs by dynamically changing the priority of jobs based on a comparison of remaining process time with time to due date.
The minimize WIP rules are sequential rules that endeavour to minimize the make-span for each job. Min WIP forward loads each job forward from the current time, locks the last operation and backward sequences from there. Min WIP backward loads each job from its due date, locks the first operation and forward sequences from there.
The Selective Bottleneck rule is rule is based on the Theory of Constraints (TOC) philosophy. It works by the user selecting the 'Bottleneck Resource' or 'Bottleneck Resource Group'. Each order is then backward scheduled from the Due Date (less Delivery Buffer). Any operations loaded onto a bottleneck resource are offset by the Bottleneck Buffer time (defined in the Resource data table for each resource) which is designed to give some 'slack' such that any delays to operations before the bottleneck resource will not result in it being 'starved' of work. Preactor then detects whether any operations in that job must start before current time. If so then these operations are re-scheduled forwards using up some or the entire bottleneck buffer. If this is consumed then some or the entire delivery buffer may also be used up and the 'At Risk' or 'Late' flag is set.
The Dynamic Bottleneck rule is an improvement over the classical selective bottleneck scheduling where the bottleneck will 'wander' depending on the current product mix that is scheduled. Rather than pre-processing your orders to determine a single bottleneck, the Dynamic Bottleneck Rule calculates the bottleneck individually for each job. Operations 'upstream' of the bottleneck are then backward sequenced inserting a resource buffer like the Selective Bottleneck rule.
The Minimize Overall Setup rule is similar in some respects to the Preferred Sequence rule. However it is focussed purely on minimizing the setup or changeover time on resources. In the Preferred Sequence rule, as each resource becomes idle it selects the next operation to load based on the preferred sequence criteria in the resource database without any consideration of other resources that could also be used. Thus, provided one or more operations can be run on the resource and they lay within the 'Look Ahead Window' one of them will be scheduled based on the preferred sequence. In the Minimize Overall Setup rule, consideration is made across all resources able to run the operation even if they are still busy. The rule does not use the preferred sequence criteria in the resource database. It does however use the 'Look Ahead Window' to decide whether an operation should be available to be scheduled in the same way as the Preferred Sequence rule.
The Campaigning rule is used when a production schedule is to be created in waves and uses a PESP script. When the rule runs, a dialog box asking the user to enter a Reference Date, Campaign Period and Number of Campaigns appears. The first pass of the rule locates all orders where the reference time entered is greater or equal to the due date of the order, these orders are then forward scheduled. The Reference Date is then incremented by the Campaign Period, the Number of Campaigns decremented. The second pass of the rule will again locate all orders where the reference time entered is greater or equal to the due date of the order. The number of passes of the rule will be the same as the number entered into the Number of Campaigns field.
Creating Unique Production Scheduling Rules
Unique production scheduling rules can be created in Preactor 400 APS. There are two methods to do this. Using standard actions in the Preactor Event Script Processor (PESP) a series of actions are selected from a library provided to process jobs in a series of scheduling passes. For example the actions could be...
- Highlight all jobs with attribute Customer = ABC
- Forward schedule
- Highlight all jobs with Order Status = Suggested
- Backward Schedule
- Schedule Remaining Jobs forward by due date
Preactor 400 APS also allows you to create your own production scheduling rules using the Preactor Open Planning Board, and its extensive library of ActiveX methods. In this way almost any scheduling logic can be created.
Material Pegging
Preactor is designed for linking with your MRP/ERP software as well as other packages such as data collection systems, spreadsheets etc. Typically your orders along with their process route information are downloaded into Preactor, scheduling is carried out and the results are passed back to the host.
For many applications this approach is adequate but it fails to overcome one of the basic weaknesses of most ERP/MRP systems in the way they aggregate materials.
Preactor 400 APS has additional functionality for dealing with material and shop order pegging. It will automatically take these shop orders and link (peg) them together. Thus materials from one shop order may be used by one or more other orders. If the first order is delayed you will want all downstream orders to be delayed accordingly, or, perhaps, you may want the materials re-allocated.
Preactor 400 APS uses SMC (Static Material Control) to create the links (pegs) during the download of orders to Preactor from your ERP/MRP system.
|