Optimization Rules List

Name

Description

ActivityJitStartDateWeight Multiplied by the days between Now and the Activity JitStartDate. Lower values are chosen earlier.
Highest Throughput Jobs with higher calculated Throughput are chosen earlier.
Highest Throughput per Drum Hour Calculated by dividing Throughput of Drum Jobs by the hours of Drum Capacity they use. Higher values are chosen first.
HotWeight Multiplied by a fixed constant and added to the score sum if the Job is Hot. Otherwise ignored. Higher values are chosen earlier.
IsFirmWeight Multiplied by a fixed constant and added to the balanced composite sum if the Job is Firm. Otherwise ignored. Higher values are chosen earlier.
JobEntryDateWeight Multiplied by the days between Now and the Job Entry Date. Lower values are chosen earlier.
JobNeedDateWeight Multiplied by the days between Now and the Job NeedDate. Lower values are chosen earlier.
LatePenaltyCostWeight Multiplied by the Job Late Penalty Cost. Higher values are chosen earlier.
LeastEligibleResourcesWeight Multiplied by the number of eligible resources. Lower values are chosen earlier.
MaterialItemGroupWeight If this operation and the previous operation both require a material in the same material group then the score equals a fixed constant multiplied by this weight.
MOInProcessWeight If any of the MO's activities are in-process (marked as Started, Running, etc.) then this weight is multiplied by a fixed constant. Higher values are chosen earlier. This can be used to reduce work-in-process inventory by attempting to finish M.O. that have already been started instead of starting on a new M.O.
MoNeedDateWeight Multiplied by the days between Now and the Manufacturing Order NeedDate. Lower values are chosen earlier.
NearestHigherSetupNbrWeight The difference of current setup number and previous setup number is calculated and multiplied by this weight.Favoring selection of Operations that have a Setup Number higher than and nearer to the current Operation's setup number.
NearestLowerSetupNbrWeight The difference of current setup number and previous setup number is calculated and multiplied by this weight. Favors selection of Operations that have a Setup Number lower than and nearer to the current Operation.
NearestSawtoothSetupNbrWeight Favors selection of Operations that have a Setup Number closest to the current Operation's Setup Number and moving in the current direction, increasing or decreasing Setup Numbers. For example, if previous setup numbers have been 20 and 30 respectively, operation with setup number 40 is favored over operation with setup number 10.
NearestSetupNbrWeight Multiplied by the absolute difference between the current Operation's Setup Number and the Setup Number of the evaluated Operation. Lower values are chosen earlier. Whether the setup number is higher or lower does not have an impact.
OnlyDispatchBestComposites For SingleTasking resources, when this value is set the dispatcher for this resource will only only dispatch the activities with the best balanced composite value. This is useful for integration purposes where you are trying to represent the schedule of another system within APS.net. For instance if you are want to represent the results of a bucketed schedule you could set the bucket time as the release time of operation and set your balanced composite rule to use the bucket time for computing the balanced composite value. With this flag checked the operations in each successive bucket will be be scheduled first. For example the bucket one operations will all have the same highest balenced composite dispatch value and so will be scheduled before the operations in the second bucket.
OperationAttributeInfos Depending on type of attribute optimize type picked the weight is multiplied by a value to determine the score. This value is determine based on the attribute on the previous operation. For example, if Optimize type is set to "Same Attribute code" then the score is calculated by multiplying the weight by a fixed constant only if this attribute's code is equal to previous operations attribute code.
OperationNeedDateWeight Multiplied by the days between Now and the Operation NeedDate. Lower values are chosen earlier.
PriorityWeight Multiplied by Job Priority. Lower values are chosen earlier. The minimum value is 0.
ProfitWeight Multiplied by the Job Profit. Higher values are chosen earlier.
QueueWeight Preference is given to Operations that have been in Queue longer. Multiplied by the days between Now and the Operation's Latest Constraint Date. Lower values are chosen earlier.
RevenueWeight Multiplied by the Job Revenue. Higher values are chosen earlier.
RunHoursWeight Multiplied by Activity Run Hours. Lower values are chosen earlier.
SameCustomerWeight Added to the balance composite sum if the Job Customer of the current activity and this activity are equal. Otherwise it is ignored. Higher values are chosen earlier.
SameMoProductDescWeight Added to the balance composite sum if the M.O. Product Description of the current activity and this activity are equal. Otherwise it is ignored. Higher values are chosen earlier.
SameMoProductNameWeight Added to the balance composite sum if the M.O. Product Name of the current activity and this activity are equal. Otherwise it is ignored. Higher values are chosen earlier.
SameSetupCodeWeight Added to the balance composite sum if the setup code of the current activity and this activity are equal. Otherwise it is ignored. Higher values are chosen earlier.
SetupHoursWeight Multiplied by Activity Setup Hours. Lower values are chosen earlier.