Using the SyteLine Scheduler, you can group several potentially different items on different jobs into a batch and process that batch through, for example, an oven or a paint booth. After the batch is processed, the different jobs then continue on their own routing.
Batching affects only the Scheduler, not the Planner.
Each batch definition describes how batches are formed, including a routing that processes the batched parts. The Operations forms includes a batch definition field. Any operation on which a batch definition is specified is referred to as the batch operation. In a jobs or production schedule routing, an operation (the batch operation) references a batch definition when the job or production schedule can be combined with other jobs or productions schedules for processing. This causes batches to be formed, based on the rules defined on the Batch Definitions form, and transfers control to the batch definition routing. At the end of the batch definition routing, the job or PS returns to its original routing and continues processing as normal.
You can use the Batched Productions form to define specific jobs and production schedules to be batched together. These jobs and production schedules are combined into batches based on the definition and not on the rules defined on the Batch Definitions form. The routing from the batch definition is copied and attached to the batched production, similar to the way current operations are copied to job operations when jobs are released. A batch routing cannot have batches defined on its routing (no batches of batches) and cannot define materials, status, or costing; these are defined on the batch operation.
If the Batch Definition field on the appropriate Operations form specifies a batch operation, then in the Scheduler the job or production schedule proceeds to the batch routing, ignoring the resource requirements and operating times on the operation. If batches are in process, they are placed at the correct operation in the batch routing based on the time recorded on the Batch Definition Operations form. For example, if the batch operation has an operation time of 10 hours, and 4 hours are reported against it, at the beginning of the Scheduler run the batched operation that is 4 hours from the beginning of the batch routing is identified as the current operation, and LSTATUS000 records are created to indicate that situation.
The Planner uses the operation as defined, and does not use the batch routing. Planning (operations and material), data collection, and costing are unaffected by this process, because there are still resource requirements and data collection processed against the batch operation.
Follow these general steps to define and run batches:
On this form, you define rules to specify how batches are formed:
Use these steps to create a user-defined batch:
These utility forms are also available for dealing with batched productions: Change Batched Production Status Utility, Batched Production Removal Utility, and Batched Production Creation Utility.
Use the Batch Summary form to see the batching results of a Scheduling run: which jobs and production schedules were batched together, how long jobs waited to be batched, and how long they were batched together.
Using the Batch Definition Tree
Change Batched Production Status Utility