This chapter covers the following topics:
Oracle Manufacturing Scheduling provides features to model the work on your shop floor for creating a prototype for scheduling. This enables you to improve responsiveness and optimize scheduling with material and resource information. You set up parameters for modeling, and then use the Scheduler Workbench for a graphical view and to reschedule on the shop floor. The features available for shop floor modeling are:
Scheduling Priorities
Alternate Resources
Simultaneous Resources
Scheduling Objectives
Setups and Changeovers
Penalty Factors
Resource Instances
Capacity Adjustments
Minimum Transfer Quantities
Resource Batching
You can assign a scheduling priority number for jobs. The priority value determines the order resources and material are allocated to jobs. Priority is not considered when a single job is scheduled or rescheduled. See: Defining WIP Scheduling Priority.
Alternate resources consist of other resources, or groups of resources, used instead of the primary resource in the job operation. Alternate resources are invoked when scheduling dates are not feasible due to resource unavailability. See: Defining Simultaneous and Alternate ResourcesAlternate Resources, and Scheduling Jobs with Simultaneous and Alternate Resources.
Simultaneous resources consist of two or more resources working concurrently within a job operation, subject to shift assignments of the individual resource. See: Defining Simultaneous and Alternate Resources and Scheduling Jobs with Simultaneous and Alternate Resources.
You can select the primary goal, or objective, of scheduling and model your system to this application of resources. The choice of objective determines the scheduling logic. See: Setting Up Scheduling Objectives. Scheduling objectives use penalty factors. machine and resource setups, and resource instances.
Penalties for Late or Early Completion and Wait Time
A weighted value, or penalty, can be assigned to scheduling events. Higher penalties induce the scheduling logic to circumvent such an events. For example, different changeovers can be assigned various penalties to sequence production in a particular order.See: Penalty Factors.
Machine and Resource Setups
You can create a performance model for machine and resource setups to include changeover time from one setup to another, including the time required to perform the work. Resources can have multiple setup types. Any two setup types within a resource can have a penalty assigned to weigh one changeover setup versus the other. See: Defining Resource Setup Information.
You can define specific machines to machine resources, and specific employees to labor resources. The resource instance data is viewable in the Resource Property window, including setup start date, setup end date, assigned units, effective start date, effective end date, and serial number. See: Resource Instances.
Resource capacity can be adjusted to respond to machine or personnel availability. You can add, delete, or adjust capacity and resource units. Simulation sets are used and linked to scheduling. They are defined and associated to resources.
Defining Work in Process Parameters
Assigning Resources to a Department, Oracle Bills of Material User's Guide
Minimum transfer quantities on routings enable you to move a portion of assemblies. This allows you to complete jobs more efficiently than waiting for the entire quantity to be completed. See: Minimum Transfer Quantity,.
Resource batching enables you to use a single resource to process multiple jobs simultaneously, preventing a resource from being underutilized. See: Resource Batching.
You can define a minimum transfer quantity for operations on a routing, enabling you to move a portion of some assemblies to the subsequent operation. Scheduling with transfers provides the ability to complete jobs more efficiently than waiting for the entire quantity to move to the next operation. Scheduling algorithms use the minimum transfer quantity values; and processing begins before all assemblies are completed at the current operation.
Minimum transfer quantity functionality is enabled when you enter this value on either the Standard Operations or Routings windows in Oracle Bills of Material. If the job uses a standard operation, the value defaults from the Standard Operations window. If the job uses a routing, either bill of material or work in process routing type, the value defaults from the Routings window.
Creating a Routing, Oracle Bills of Material User's Guide
Creating a Standard Operation, Oracle Bills of Material User's Guide
Manufacturing begins when a sufficient quantity of the assembly is at the operation resource. When the quantity is complete, it moves to the next operation resource.
If this functionality is enabled, the scheduling engine always transfers completions in batches, and the minimum transfer quantity amount applies to all resources in the operation.
This processing does not allow overlapping transfers in the same operation. If a minimum transfer quantity arrives at an operation resource before the previous quantity is completed, work does not begin until the first amount is completed.
The batch amount matches the minimum transfer quantity value. However, the transfer quantities can differ across transfers in order for the completion to equal to the sum of the batches. For example:
If the job quantity is 100,
And the minimum transfer quantity is 30,
You can have transfers of quantities 30, 30 and 40 in order to equal the total of 100.
Transfers are only within operations of a routing.
Note: Network routings do not use minimum transfer quantity functionality.
Resource Settings
Prior and Next Operation Resources: If an operation resource is flagged as Prior on the Resources window, then it can overlap with the previous operation. If it is flagged as Next, then it can overlap with the succeeding operation. However, minimum transfer quantity processing does not allow overlapping batches in the same operation. If you are using minimum transfer quantity batches and they overlap, the quantities skip the Next or Prior resource, and move to subsequent or preceding resource in the routing.
Sequential Operation Resources: In sequential operation resources, the transfer amount determines the schedule of the operation resources. If one of those resources does not have minimum transfer quantity, the schedule is determined by the end time of one and the start time of the other.
Simultaneous Resources: Within any simultaneous set, all transfers in an operation resource coincide.
Resource batching enables you to use resources across multiple jobs. This prevents a resource from being underutilized. Work scheduled using resource batching is equivalent work performed with the same manufacturing processes.
Resource batching creates processing batches which consist of a job/resource combination, and standard operation code if applicable. For each batchable resource, a time window is defined when the system should look for operations to include in the batch.
Note: If using standard operation codes, they must be the same for all the operations in a batch.
You can create a batch that includes jobs of different assembly numbers. The scheduling engine creates batches across multiple jobs and schedules them as a one group when they use the same:
Standard operation code in their routings
Resource setup
Time period duration of the resource
They must also fall within the same batching window.
The resource batching information is defined in the Resources window in Oracle Bills of Material. See: Creating a Routing, Oracle Bills of Material User's Guide. Check the Batchable check box to enable a resource for batching, and enter values for the following fields:
Maximum Batch Capacity: The largest number of units to group in a batch. If there are jobs containing units exceeding this value, the system creates multiple batches.
Batch Capacity UOM: Unit of measure used for the resource batch such as units, area, volume, or weight.
Batching Window: The time frame in which this resource is used when batching. For example, if the batching window value is 3 hours, the resource is available to the processing batch in this 3 hour window.
Batching Window UOM: The unit of measure, expressed in time, used for the Batching Window field.