Introduction
Omitting and Holding Jobs are ways that we can control the Jobs or the flow of Operations that are being scheduled. Although both options essentially stop the Job from being scheduled at some degree, there are some key differences between the two.
Hold: A Hold can be placed at the Job, Manufacturing Order, or Operation level. Once a Hold has been placed, that Job, Manufacturing Order, or Operation cannot be scheduled for work until a designated “Hold Until” date. Typically Holds are accompanied by a reason that can be set by a drop down. The following reasons are common for a Job/MO/Operation for being placed on hold:
- Material Hold
- Tooling Hold
- Production Hold
- Engineering Hold
- Customer Hold
- Quality Hold
- Lack of Material
- Design Change Pending
Omit: Omitting can only occur at the Operation level and unlike a Hold, there isn’t a Hold Until date; the Omitted Operation will simply never be scheduled, and the flow of Operations will continue as if the omitted Operation never existed. A Hold performs differently in that an Operation placed on Hold affects all of its downstream Operations and, if placed on Hold long enough, can be come either a Capacity or Material bottleneck, or both.
An example where Omitting an Operation would be helpful would be in the production of a kit that deviates slightly from the standard. For example, we might have a standard routing that calls for a painting operation to be before an assembly operation. If an order came in for that kit, but unpainted, the painting operation could be omitted in APS, where the alternative would other wise be the manual creation and import an entirely new routing.
Omitted Operations Flags
There are three different flags for Operations regarding omission:
NotOmitted: This is an operation that is not omitted and will be scheduled regularly like all other operations.
OmittedByUser: This is an operation that is manually omitted by User choice. The operation will not be scheduled and allow its successor operations to continue without this particular Operation.
OmittedAutomatically: This is an operation that was automatically omitted due to an error in the import. Typically the error involves a missing Capability being referred to by the Required Capability of the Operation. If no such Capability exists within APS, a user can set the System Options to automatically omit the Operation and allow the rest of the Job to be imported without further interruption.