You can use Oracle Work in Process to schedule production resources and materials, customer delivery requirements, and maintain a smooth production flow. Scheduling establishes expected dates and times for material and resource requirements. Scheduling also establishes expected dates and time for the supply availability of assemblies built on the jobs and repetitive schedules.
Oracle Work in Process uses two scheduling modes - infinite and constraint-based:
The infinite scheduling engine assumes infinite capacity.
Oracle Production Scheduling considers resource and material constraints using sophisticated scheduling algorithms and enforcing minimum run length constraints, and minimizing changeover times on your resources. See: Oracle Production Scheduling Implementation Guide
Scheduling for both the infinite and constraint-based scheduler consider resource usage features such as simultaneous resources, 24 hour resources, and utilization and efficiency factors.
You can choose to include either or both resource efficiency and resource utilization in scheduler calculations. Efficiency effects your production load, and utilization effects capacity. These resource factors are always considered in lead time calculations, and influence resource elapsed time calculated during scheduling. Both the infinite scheduler and the constraint based scheduler use the efficiency and utilization settings in the Work in Process Parameter window when scheduling jobs. See: Defining WIP Parameters
For scheduling calculations, extended resource usages are rounded to the next minute. See: Resource Factors in Lead Time Calculation
You can define the start and completion dates and times for jobs and repetitive schedules. Start and completion dates and times for the operations within these jobs and schedules are scheduled automatically.
You can monitor and prioritize your shop floor activity to meet customer demands using a variety of standard Work in Process reports.
If you enter a job or repetitive schedule start date and time, the completion date and time is automatically determined using forward scheduling. Conversely, if you enter a job or repetitive schedule completion date and time, the start date and time is determined using backward scheduling.
You can define resource usage based on job and repetitive schedule quantity for variable resources or for a fixed amount for fixed resources such as setup and teardown. Scheduling is based on resource usage.
You can specify all the assemblies on a repetitive production line to run at the same production rate on your fixed rate lines. You can specify the production rate by assembly for your variable rate lines.
You can schedule your repetitive production lead time based on routing or line attributes to best simulate your repetitive production process.
You can schedule discrete jobs around bottleneck operations using midpoint scheduling. By setting the midpoint operation start or completion date and time you can automatically forward and backward schedule from that midpoint.
You can define multiple resources at an operation to account for labor, machine, and other activities. Resources are automatically scheduled based on their sequence.
You can schedule resource operations to overlap to account for simultaneous processing of the same job or repetitive schedule in concurrent operations. For example, you can schedule external setup on the next operation to take place while you complete processing at the prior operation.
You can automatically implement discrete reschedule recommendations from Oracle planning products or import them from other sources through the Open Job and Schedule Interface.
You can assign as many resources to an operation as are available. Further, you can make any resource available by shift or around the clock. Scheduling is based on resource availability.
When a group of multiple resources are defined as simultaneous resources, the scheduler uses the one resource having the longest duration to calculate start and end dates for the group. See: Resource Factors in Lead Time Calculation
If these resources are scheduled as Yes, that is, the resource start and completion dates are used to schedule the operation. For example, if you have two operations, and the first operation has simultaneous resources assigned, both resources are scheduled with a value of Yes. The resources in the operation following this resource are scheduled as Prior or Next.
For simultaneous resource sets with at least one Prior or Next resource - the set can only contain resources of the same scheduled type, or scheduled type equal to No.
Other Sources
Oracle Production Scheduling Implementation Guide