Work in Process Scheduling
This chapter describes how discrete jobs and repetitive schedules are scheduled.
This chapter covers the following topics:
- Overview of Work in Process Scheduling
- Discrete Scheduling
- Detailed Scheduling
- Discrete Rescheduling
- Repetitive Line Scheduling
- Repetitive Line Rescheduling
- Repetitive Line Capacity Changes
Overview of Work in Process Scheduling
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, and two constraint-based applications—Manufacturing Scheduling and Production Scheduling. The infinite scheduling engine assumes infinite capacity.
-
If you have Oracle Manufacturing Scheduling installed, you can enable the constraint-based scheduler which considers resource and material constraints. All scheduling is based on the calendars, shifts, departments, resources, routing, and planning you define in Oracle Bills of Material - and jobs and production lines defined in Work in Process.
-
Production Scheduling uses sophisticated scheduling algorithms and optimizes production, enforcing minimum run length constraints, and minimizing changeover times on your resources. See: Supply Chain Planning Production Scheduling
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
Date and Time Scheduling
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.
Forward and Backward Scheduling Options
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.
Fixed and Variable Rate Production Lines
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.
Fixed and Routing Based Line Lead Time Options
You can schedule your repetitive production lead time based on routing or line attributes to best simulate your repetitive production process.
Planning Based Rescheduling
You can automatically implement discrete reschedule recommendations from Oracle planning products or import them from other sources through the Open Job and Schedule Interface.
Midpoint Scheduling
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.
Multiple Resources per Operation Scheduling
You can define multiple resources at an operation to account for labor, machine, and other activities. Resources are automatically scheduled based on their sequence.
Simultaneous Resources
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.
Fixed and Variable Resource 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.
Resource Availability Scheduling
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.
Operation Resource Overlap Scheduling
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.
Constraint-based Scheduling
Oracle provides constraint-based scheduling enabling you to schedule discrete jobs and operations based on priorities, resources, and material availability:
-
With Oracle Manufacturing Scheduling; the Scheduler Workbench is the graphical interface used to schedule single discrete jobs, and reschedule pending jobs on the entire shop floor. See: Scheduling Single Discrete Jobs, Oracle Manufacturing Scheduling User's Guide, and Features, Oracle Manufacturing Scheduling User's Guide
-
Production Scheduling is a constraint-based automated scheduling tool using s algorithms to optimizes production, enforce constraints, and minimize changeover times on your resources. See: Supply Chain Planning Production Scheduling
Dispatch Reporting
You can monitor and prioritize your shop floor activity to meet customer demands using a variety of standard Work in Process reports.
Related Topics
Overview of Oracle Bills of Material, Oracle Bills of Material User's Guide
Scheduling Single Discrete Jobs, Oracle Manufacturing Scheduling User's Guide
Rescheduling All Jobs or Pending Scheduling Jobs, Oracle Manufacturing Scheduling User's Guide
Supply Chain Planning Production Scheduling
Discrete Scheduling
When you define a job, you must enter either a start or completion date and time. If the job assembly has a routing, dates and times are automatically scheduled for the operations, resources, and material requirements for the job using detailed scheduling.
If the job assembly does not have a routing, it can be scheduled in one of two ways. You can manually schedule the jobs by entering both the start and completion dates. You can also enter either a start or completion date and allow the system to calculate the missing date based on the item lead time.
Start Date
This is the date and time that you plan to start the job. You can choose start dates and times earlier than the current date to maintain relative date priorities for department schedules and material requirements. You can choose start dates that are not on the manufacturing calendar. In this case, the system plans for work to start on the next valid date.
When you specify the start date and time, the system forward schedules the job and automatically calculates the job completion date and time using detailed scheduling based on the assembly's routing. If no routing exists, the system forward schedules using the fixed and variable lead times for the assembly from the item master. If no routing and no lead time exist, you must enter both the start and completion dates.
Completion Date
This is the date and time on which you plan to complete the job. You can choose completion dates and times earlier than the current date to maintain relative date priorities for department schedules and material requirements. If you choose completion dates that are not on the manufacturing calendar, the system plans for work to complete on the next valid date.
When you specify the job completion date and time, the system backward schedules the job and automatically calculates the job start date and time using detailed scheduling based on the assembly's routing. If no routing exists, the system backward schedules using the fixed and variable lead times for the assembly from the item master. If no routing and no lead time exist, you must enter both the start and completion dates.
When you import jobs and schedules or automatically create discrete jobs from planned orders, the system uses the due date from the planned order as the scheduled completion date and uses backward scheduling to determine the start date. When the system automatically creates final assembly orders, it also uses backward scheduling from the order due date to determine the job start date.
Note: The start date that Oracle planning products recommend may not exactly match with the start date of the actual job. Differences between the planning and work in process lead times can arise due to more precise scheduling of shifts and resources by Work in Process.
Operations Dates
Each operation in the routing is scheduled using detailed scheduling. The start date and time of the first operation generally equals the start date and time for the job. The scheduled completion date and time for the job generally equals the scheduled completion date and time of the last operation in the routing. If the resource is not active on a shift at the start or completion dates and times of the job, the first and last operation dates and times do not match the start and completion dates of the job. In addition, you can manually schedule the first and last operation dates and times to differ from the job start and completion dates and times.
Material Requirements Dates
The system schedules material requirements so that they are required on the start date and time of the operation where they are consumed. For example, if you use component A in operation sequence 30 and operation sequence 30 is scheduled to start on 01-JAN at 12:15, then the component is required on 01-JAN at 12:15 regardless of the start and completion dates and times of the job. If there is no routing, all material requirements are required on the job start date and time.
Related Topics
Detailed Scheduling
The system uses detailed scheduling to schedule discrete production. The lead time rollup process in Oracle Bills of Material also uses detailed scheduling to calculate lead times used by Oracle planning products.
Detailed scheduling applies resource usage defined:
-
by routings and resources to resource availability
-
defined by the calendar shifts and exceptions on a minute by minute basis
-
to determine job start and end times (calculated to the minute) and operation start and end times
You provide resource usage information used by detailed scheduling when you assign resources to a routing in Oracle Bills of Material.
For example, assume you have defined the following routing and you want to use it to schedule a discrete job for a quantity of 1000 assemblies:
Routing to Schedule Discrete Job
| Op Seq | Res Seq | Resource | Basis | Usage Rate or Amount | Activity | Scheduled | Assigned Units | Scheduled Units |
|---|---|---|---|---|---|---|---|---|
| 10 | 1 | Punch press | Item | 0.1 | Run | Yes | 1 | 100 |
| 10 | 2 | Punch press | Lot | 1 | Teardown | Next | 1 | 1 |
| 20 | 1 | Queue | Lot | 4 | Queue | Yes | 1 | 4 |
| 20 | 2 | Machinist | Item | 0.05 | Labor | No | 3 | 0 |
| 20 | 3 | Drill press | Item | 0.05 | Run | Yes | 3 | 50 |
| 20 | 4 | Inspector | Item | 0.01 | Quality | Yes | 1 | 10 |
| 30 | 1 | Plating preparation | Lot | 1 | Setup | Prior | 1 | 1 |
| 30 | 2 | Plating | Item | 0.01 | Run | Yes | 1 | 10 |
Note: All units of measure are in hours.
Multiple Resources
You can assign multiple resources per operation to schedule labor, machine, and other activities you perform within an operation. Detailed scheduling schedules multiple resources sequentially based on their resource sequence number.
In the Routing to Schedule Discrete Job table, operation sequence 30 has two resources: Plating and Plating preparation. Detailed scheduling schedules these resources sequentially based on their resource sequence number.
Constraint-based Scheduling of Resources
Constraint-based scheduling considers the capacity for the resource. You can also set up simultaneous and alternate resources. Simultaneous resources consist of two or more resources scheduled with the same start date and time. Alternate resources are used instead of the primary resource.
-
Reschedule the start and end dates of a resource
-
Delete or add a day of capacity, adjusting for overtime shifts or shop closures
-
Add or delete resource units when either extra resources are obtainable or resources are unavailable
-
Adjust Assigned Units or Usage Rate for the resource on the job routing
See: Adding and Updating Resources, Defining Manufacturing Scheduling Resources and Supply Chain Planning Production Scheduling
Lot or Item Basis
You can use a resource basis of Lot to schedule fixed resource requirements such as setup or teardown. You can use a resource basis of Item to schedule resources whose requirements change in proportion to the number of assemblies being built.
In the Routing to Schedule Discrete Job table, operation sequence 10 has resource sequence 2, Punch press, with a basis of Lot to schedule one hour of teardown activity for each job.
Operation sequence 10, resource sequence 1 has 1 hours of runtime activity for each assembly unit on the job. Therefore, a job for an assembly quantity of 1000 requires 100 hours of runtime activity.
Assigned Units
You can assign multiple units of a resource to work concurrently at an operation. In the Routing to Schedule Discrete Job table, for operation sequence 20, resource sequence 3, you have three drill press resources in your plant that you have assigned to the routing. Detailed scheduling schedules assuming all three are applied to the job. In other words, if your job has 50 hours of drill press resource required, detailed scheduling would schedule 16.67 elapsed hours (50 resource hours required/3 resources available).
Scheduled Options
You can assign resources to an operation, but not have them scheduled. In the Routing to Schedule Discrete Job table, you might have a machinist resource who periodically checks the progress of the drill press resource. Since the machinist resource is not on the critical path you would not schedule, but you would likely want to cost, the machinist resource.
You can assign resources used solely for scheduling, even though these resources do not actually provide value added work. In the Routing to Schedule Discrete Job table, at operation sequence 20, resource sequence 1, you can simulate 4 hours of queue time to schedule the time assemblies wait before the drill press resource frees up from other scheduled work.
Note: Detailed scheduling is not a finite scheduling algorithm. However, you schedule resources to simulate load that other jobs place on a department and resource and thus achieve scheduling results similar to those created by finite scheduling algorithms.
You can schedule operations to overlap to account for simultaneous processing of the same job in concurrent operations. For example, you can schedule setup resources of the next operation to overlap with processing resources of the current operation. Or, you can schedule teardown resources at the prior operation to overlap with processing resources at the current operation.
In the Routing to Schedule Discrete Job table, operation sequence 10, resource sequence 2 has one hour of teardown that can be performed after the assemblies have moved to the next operation. As such, the Scheduled field is set to Next.
Operation sequence 30, resource sequence 1 has one hour of setup activity that can begin before the assemblies arriving at operation sequence. As such, the Scheduled field is set to Prior.
Shift Calendar
Detailed scheduling uses the shift calendar to determine resource availability. Therefore, resources can only be scheduled when they are available. If you assume round the clock resource availability, the job for 1000 assemblies, using the routing in the Routing to Schedule Discrete Job table, would require 141.67 processing hours or approximately 5.6 workdays.
On the other hand, if you assume a single 8 hour day, single shift calendar for all resources, the processing hours would remain 141.67 hours, but the workdays would stretch to approximately 17.7.
Forward and Backward Scheduling
When you forward schedule, detailed scheduling starts at the job start date and time and computes the job completion date and time. When you backward schedule, detailed scheduling ends at the job completion date and time and computes the job start date and time.
If the job start date and time is before the first scheduled resource in the first operation becomes available, no work can take place until that resource becomes available. Likewise for backward scheduling, if the completion date and time for the job conflict with the availability of the last scheduled resource in the last operation, the job cannot be completed until the last operation is complete. Resources may or may not be available depending on their shift availability.
The following diagram depicts how the detailed scheduler would schedule the routing from the Routing to Schedule Discrete Job table, assuming round the clock resource availability:
Related Topics
Overview of Routings, Oracle Bills of Material User's Guide
Creating a Routing, Oracle Bills of Material User's Guide
Creating and Implementing Firm Planned Orders, Oracle Advanced Supply Implementation and User's Guide
Releasing Recommendations, Oracle Advanced Supply Implementation and User's Guide
Discrete Rescheduling
You can reschedule discrete jobs by modifying discrete job operations, by importing modified jobs and schedules, and by replanning planned orders using Oracle planning products.
Operation Dates
You can reschedule any existing job. You can reschedule around the start or completion date of any discrete job operation. For example, you can do midpoint rescheduling to schedule both forward and backward from any operation within the routing. You can also manually reschedule operation start and completion dates. See: Adding and Updating Operations.
Discrete Job Changes
You can change start and completion dates and times of discrete jobs. The operations and material requirements of the job are automatically forward or backward scheduled depending on the date you changed. This rescheduling is based on the operation and requirements of the job, not the bill and routing you define in Oracle Bills of Material.
If you increase or decrease the job quantity, the job is automatically rescheduled based on the revised quantity. If you change the alternate routing, the routing revision, or revision date and time or routing reference (for non-standard jobs only) of a job with a status of Unreleased, the job is rescheduled based on the new routing.
Planned Orders
You can automatically implement reschedule recommendations from Oracle planning products. You can choose the specific jobs you want to reschedule based on the criteria you enter in the Planner Workbench. The system then automatically reschedules job operation and material requirement start and completion dates and times.
Job Import
You can import suggested repetitive schedules from other planning system into Work in Process. You can choose the specific jobs you want to reschedule based on the criteria you enter in the planning system. Job operation and material requirement start and completion dates and times are automatically rescheduled. See: Work Order Interface and Importing Jobs and Schedules.
Capacity Modifications
For each resource on a shift, you can override the number of resource units available (such as number of machines) and specify additions or reductions to the amount of time the resource is available on that shift. And, you can group capacity modifications into sets that you can use when you generate a capacity plan to simulate capacity changes. In Work in Process, these capacity modifications are considered when you define new jobs and/or reschedule existing jobs.
Workday Calendar and Shifts
You can change the workday calendar and modify shifts at any time. The system takes these changes into account when you define new jobs and/or reschedule existing jobs. You can transact on non-workdays as long as they occur in a valid period. See: Overview of Workday Calendar, Oracle Bills of Material user's Guide.
Constraint-based Rescheduling
If you are using Manufacturing Scheduling or Production Scheduling, the constraint-based scheduling engine enables you to reschedule jobs based on date constraints or available resources and material. When you reschedule all jobs or pending scheduling jobs from the Schedule Discrete Jobs window, the constraint-based scheduling engine uses the requested due date and scheduling priority:
-
The highest priority jobs are scheduled first
-
Jobs with the same priority are scheduled based on the earliest requested due date
-
Firm jobs and any associated operations are not rescheduled
Related Topics
Supply Chain Planning Production Scheduling
Repetitive Line Scheduling
Repetitive line scheduling is used to schedule repetitive production. When you define repetitive schedules you must specify the line on which you plan to produce the repetitive assembly and the quantity you plan to build. Then, repetitive line scheduling uses the line start and stop times, production rate, and lead time, along with the workday calendar to schedule your repetitive schedules.
Production Lines
When you define lines you must specify the start and stop times of the line. You must also specify the minimum and maximum hourly rate on the line.
The repetitive line scheduling method uses line start and stop times to calculate how long the line runs each day. For example, if you run the line from 8:00 am to 5:00 pm, you would enter a start time of 08:00 and a stop time of 17:00. The repetitive line scheduling method does not use the shift calendar dates and times you defined in Oracle Bills of Material. The repetitive line scheduling method does use the days on and days off from the workday calendar.
Production Rate
When you associate a line and assembly you must set the hourly production rate. In other words, you define the hourly production run rate used to schedule that assembly on that line. For line/assembly associations with a fixed lead time rate line, all assemblies should use the same production rate. For variable rate lines, you need to specify different rates for each assembly. The production rate cannot be greater than the maximum rate on the line.
Lead Times
For lines with a lead time basis of Fixed, you must enter a fixed lead time for the line. For lines with a lead time basis of Routing-based, the lead time is calculated by applying the detailed scheduling algorithm to the routing of the assembly. The lead time for a repetitive schedule is the amount of time it takes to complete the first unit.
Repetitive Schedule Quantities
You define the daily production quantity, processing days, and total production quantity when you manually define a schedule.
Daily Quantity
The daily quantity is the number of completed assemblies you plan to produce on the schedule each day. The daily quantity can only be a positive number including decimals, such as 1.25. A warning message displays if you define a daily quantity for a schedule that is greater than the line's maximum hourly rate times the production hours.
You can choose a daily quantity that is less than or equal to the daily line capacity:
production rate X (line stop time - line start time)
In that case, you build the entire daily quantity for that schedule in less than a full day. For example, if the production rate is 100 per hour for 10 hours and the daily quantity for a schedule is 500 per day, you can build the 500 in half a day. The remaining line capacity of 500 is then free for other production.
Over-schedule Line By Daily Quantity
You can temporarily over-schedule a production line to simulate overtime or a production rate increase. You can choose a daily quantity greater than the daily line capacity. For example, if the production rate is 100 units per hour for 10 hours, the daily line capacity is 1000 units. You can define a schedule for 1200 units, thereby over-scheduling the line. The system warns you that you are over-scheduling the line and interprets this over-schedule as an increase in the production rate, not a change in start and stop times. In this example, the system would assume a production rate of 120 units per hour for 10 hours to get 1200 units per day.
Processing Days
Processing days are the number of days you plan to work on the repetitive schedule. Processing days can be any positive number including decimal (partial) days. A full processing day for the schedule on a line may not require the entire capacity of the line if the daily quantity is less than the daily line capacity. For example, a full processing day on a schedule at a daily quantity of 500 on a line with a production rate of 100 per hour and 10 available hours can be built with a half day of line capacity.
The total quantity is the number of completed assemblies you plan to produce on the repetitive schedule. The total quantity equals the daily quantity multiplied by the processing days. The total quantity can only be a positive number including decimal quantities.
When you manually define a repetitive schedule, you can enter either the daily quantity or the total quantity. You can enter both if you choose. If you enter either quantity and processing days information, the system automatically calculates the other quantity for you.
Lead Times
Lead time is the amount of time that it takes to complete the first assembly on a repetitive schedule from start to finish. Lead time equals the difference between the FUSD and the FUCD. The system calculates lead time based on the routing for lines with a lead time basis of Routing based. The system defaults the lead time from the production line for repetitive schedules on production lines with a lead time basis of Fixed.
Repetitive Schedule Dates and Days
You enter dates First Unit/Last Unit Start and First Unit/Last Unit Completion Dates and times, and processing days when you manually define a repetitive schedule.
First Unit/Last Unit Start and First Unit/Last Unit Completion Dates
The first unit start date (FUSD) is the date and time you plan to begin production on the first assembly on a repetitive schedule. You can enter a start date and time earlier than the current date to maintain relative priorities.
The LUSD (last unit start date) is the date and time you plan to begin production of the last assembly on a repetitive schedule.
The FUCD (first unit completion date) is the date and time you plan to complete production of the first assembly on a repetitive schedule. This date equals the FUSD plus the lead time.
The LUCD (last unit completion date) is the date and time you plan to complete production of the last assembly on a repetitive schedule.
Forward Scheduling
For repetitive schedules with routings, if you enter FUSD or FUCD and times, the system uses forward scheduling to calculate the other dates. If you enter FUCD or LUCD and time, the system uses backward scheduling to calculate the other dates. If you do not have a routing for an assembly on a line with a lead time basis of Routing based, you must manually schedule the lead time. In other words, if you enter the FUSD and time, you must enter the FUCD and time to set the lead time for the schedule.
If you do not have a routing for an assembly on a line with a lead time basis of Routing based, you must manually schedule the lead time. In other words, if you enter the FUSD and time, you must enter the FUCD and time to set the lead time for the schedule.
You can also forward or backward schedule a schedule if its assembly has either a fixed or variable lead time or both. If the assembly has both a fixed and variable lead time, the lead time for the repetitive schedule is calculated as follows:
(job or schedule quantity x variable lead time) + fixed lead time
The following diagram illustrates repetitive schedule dates.
You cannot overlap repetitive schedules for the same assembly on the same line. In other words, you cannot have the FUSD of one schedule fall between the FUSD and LUSD of a prior schedule. For example, if the LUSD on the prior schedule is 24-MAY at 12:00, then the FUSD of the next schedule for that assembly on that line must be at least 24-MAY at 12:01.
If you do not have a routing for an assembly on a line with a lead time basis of Routing based, you must manually schedule the lead time. In other words, if you enter the FUSD and time, you must enter the FUCD and time to set the lead time for the schedule.
Sequencing Repetitive Assemblies on a Line
If you build multiple repetitive assemblies on a single production line, you can sequence production to maximize efficiency and customer service. You can then query all schedules defined for an assembly on the line and check the sequencing based on the schedule dates. You can then reschedule the schedules.
To further assist you with sequencing, the system provides several additional features. For example, you can define all schedules for an assembly on a single line.
Furthermore, because the system uses both dates and times to schedule repetitive production, you can decide the proper scheduling sequence then schedule production to the minute to match your sequence.
Lastly, you can use the Open Job and Schedule Interface to import sequence optimized repetitive planning suggestions. For example, if you have an automated sequencing program, you can insert output records from this program into the Open Job and Schedule Interface table. These records can then be imported into Work in Process.
Related Topics
Open Job and Schedule Interface
Associating Lines and Assemblies
Repetitive Line Rescheduling
You can reschedule repetitive schedules by changing quantities, dates, and routing revisions.
Repetitive Schedule Changes
You can change the daily production quantity, processing days, and total quantity of a repetitive schedule. You can change any quantity and the system reschedules all other dates and quantities on that schedule accordingly. For example:
-
Changing the daily production rate on a repetitive schedule causes the total quantity to change accordingly based on the processing days.
-
Changing the processing days causes the total quantity to change according to the daily quantity.
-
Changing the total quantity on a schedule does not impact the daily quantity. Instead increasing the total quantity causes the processing days to increase. Conversely, reducing the total quantity decreases the processing days.
If you change repetitive schedule quantities, you must select a date around which to reschedule. The system then keeps this date constant while automatically changing the other dates accordingly. For instance, if you increase the processing days on a repetitive schedule and choose to keep the first unit start and completion dates constant, the system pushes out the last unit start date and last unit completion date and increases the total quantity.
Repetitive Schedule Dates
You can change the dates and times on a repetitive schedule. When you change dates and times, the system reschedules unreleased and released schedules the same way. If you change the first unit start date, first unit completion date, last unit start date, or last unit completion date, the system reschedules the repetitive schedule to adjust the remaining start and completion dates. Changing any of the four start and completion dates does not impact the processing days, total quantity, daily quantity, or lead time. You cannot change dates and times so that schedules for the same assembly on the same line overlap.
You cannot change the lead time on a schedule. For fixed rate lines, the line determines the lead time. For routing-based lines, the routing determines the lead time. When you change dates on a repetitive schedule, all the other attributes of that schedule, such as bill revision, remain the same.
Bill Revisions and Dates
You can change the bill revision and dates for any unreleased or pending repetitive schedule.
Routing Revisions and Dates
If you change the routing revision or revision date for any repetitive schedule with a status of Unreleased or Pending - Mass loaded, the system automatically reschedules based on the new routing. For routing-based lines this may impact the dates. For fixed rate lines, changing the routing does not impact the dates.
Related Topics
Repetitive Line Capacity Changes
You can make repetitive schedule adjustments to your repetitive production capacity to reflect short term issues in matching your repetitive production supply and demand. You can also change line attributes such as start and stop time, and production rate to reflect ongoing changes in your repetitive line capabilities.
Temporary Increase in Capacity
You have several options for temporarily increasing repetitive production output. You can increase the production hours on a line by working overtime. You can also increase the production rate by adding workers to a line, or you can increase the load on an under utilized line.
The system lets you temporarily over-schedule a production to simulate overtime or production rate increase. You can choose a daily quantity greater than the daily line capacity when you define a repetitive schedule. Over-scheduling is interpreted as an increase in the production rate between the defined line start and stop times, not as an increase in the line's production hours.
You can also increase the load on an under utilized line by simply associating the line with the assembly then manually defining a repetitive schedule for the assembly on that line.
Temporary Decrease in Capacity
You have several options for temporarily decreasing repetitive production output. You can decrease production hours on a line temporarily by shutting down the line earlier than usual. You can also temporarily decrease the production rate by reassigning workers to other lines or by temporarily shutting down the under utilized line.
The system lets you under-schedule a line any time you define a repetitive schedule. You can choose a daily quantity less than the daily line capacity. Under-scheduling is interpreted as running for a shorter interval at the defined production rate and within the line start and stop time.
You can choose not to define schedules on a line if you do not need the supply. As such, the line would likely be under utilized.
Permanent Increase in Capacity
You have several options for permanently increasing your repetitive production outputs. In real life, you can run existing lines longer, you can speed up production on the line, or you can add lines.
To run lines longer or faster, you can change the start and stop times on a line, add days to the workday calendar, or increase the production rate. All new schedules planned and defined after this change reflect these new attributes. Existing repetitive schedules are not impacted.
You can define new lines and associate them with existing repetitive assemblies to increase your repetitive capacity as well.
Permanent Decrease in Capacity
To permanently decrease your repetitive production capacity, you can shorten your production hours, decrease your production rate, or shut down under utilized lines.
The system lets you shorten your production hours by changing line start and stop times or by removing days from the workday calendar. You can also decrease the production rate for a line and all the repetitive assemblies that use the line. All new repetitive schedules planned and defined after this change reflect this new rate. Finally, you can remove a line from production by removing its association to any repetitive assemblies.
Related Topics