Operation planned too early on bottleneck operation

To analyze or document the issue, start with the Schedule Report for the bottleneck resource and display the minimum required information. These are the information that you must display at the least:

  • Order ID and operation number
  • Planned start
  • Planned end
  • Internal order priority
  • Internal network priority
  • Remaining production time
  • Remaining setup time
  • Sequence status
  • Planned start before pullup (MOPSFP)
  • Earliest start (MOPEAS)

If you sort the orders by priority, you can view the planned sequence. If you sort the orders by change in network priority, you can view if pull-up has been done.

When an operation is scheduled and there is no free capacity for the perfect JIT plan, this usually results in a bottleneck resource being overloaded. In this case, the operation is either delayed or an alternative plan with free capacity is created in a gap. If an operation has a short operation time, short capacity gaps may be utilized and planned to finish earlier than the due date (Latest start or end).