Introduction

Optimization is the process by which APS creates a schedule by assigning Activities to the Resources according to eligibility constraints and business rules such as minimizing setup time or maximizing revenue. Optimization can be done manually, at the user’s discretion, or it can be set to run automatically in configurable time intervals or even at specific times of day.

Key Concepts

Optimization is dependent on a number of settings and it is important to remember that configuring the Optimize can vary in a number of ways:

• Scope: This is the amount of information that will be scheduled. It can be set to Optimize every plant in APS, just one plant, or even by individual department if necessary.
• Time: The Optimize can be set to start after a certain period of time to ensure not only an optimal schedule, but one that is stable, without the volatility that is associated with changes being made too frequently on the shop floor.

Additional Features

Auto Split Manufacturing  Orders:   If checked, then the Resources included in the Optimize which have their AutoSplitSpan more than zero will be considered for automatic Manufacturing Order splitting at the end of Capacity Intervals that they span.

Using Optimization to Model Preference

Many manufacturers use a system of preferences when deciding what products to run on certain machines, or even what routings to use. For example, a certain Item might run better or produce a higher yield on one resource than another. It may require less setup time on one resource than another. Perhaps one resource simply runs faster or more efficiently and it is therefore desired to constantly be busy. One routing may be more favorable than another.

Additionally, even with Infinite Capacity, Rough-Cut scheduling, APS can model level-loading to spread work across multiple Resources and increase utilization.

Product Rule HeadStartSpan: Using Product Rules creates a relationship specifically between an Item and a Resource that is producing it. Within the Product Rule is the HeadStartSpan which determines, for that particular item on that particular resource, how early a Job can be scheduled to that resource. Setting a longer HeadStartSpan for that resource will cause it to be preferred over other available resources. This will only take effect where that Product Rule is being invoked and is most useful when a manufacturer is basing preference on the Product that is being produced.

AlternatePath AutoUseReleaseOffsetDays: Each Manufacturing Order has one or more Alternate Paths. On one of the Alternate Paths (there may only be one) there is a setting for the AutoUseReleaseOffsetDays. This time span goes into effect when the “AutoUse” field is satisfied and will set the Release date for the Job. Defining a smaller time span will favor using that Alternate Path over others.

Resource HeadStart: On the Resource Properties, specifying a larger value will cause that Resource to be favored over other Resources that have the same Capability. This will allow more Jobs to be scheduled to the Resource before resorting to other, less favored, Resources.

Custom Add-in: Should APS not come with built-in functionality that can model the logic behind the manufacturer’s preferences, APS can leverage the fact that it’s written in the .NET Framework and a Custom Add-in could be created to model those preferences.