Open Workbench User Guide

Autoschedule Projects

For example, if the task has a priority of 0 through 9, it is given the highest priority during scheduling. If the task has a priority of 11 through 36, it is given the lowest priority during scheduling.

In the case of dependencies, Autoschedule assumes that a predecessor task has a priority at least equal to its successor. In some cases, dependency relationships override individual task priority during the scheduling process.

Override Task Lock during Autoschedule

You can override the lock on tasks while autoscheduling. For example, if you have a task that is locked between February 25, 2008 and April 4, 2008, Autoschedule distributes the assignment's ETC to the task between the two dates. If you do not override the lock and Autoschedule changes the task's end date to April 25, 2008, the assignment's ETC remains between February 25, 2008 and April 4, 2008. However, if you choose not to override the lock, the assignment's ETC is distributed between February 25, 2008 and

April 25, 2008, per the assignment's loading pattern.

When scheduling locked tasks using this option, Autoschedule adheres to the following rules:

■

Assignments that have a fixed loading pattern set are not be scheduled (No change in behavior). Variable assignments that have Front, Back, or Uniform loading are scheduled.

■

Variable assignments that have a loading pattern other than fixed on locked tasks are scheduled before any other assignments. If a variable assignment is on a fixed task, it is scheduled before any assignment on variable tasks.

■

■

Variable assignments on locked tasks are scheduled without regard to the resource's work on other tasks, within the same project.

The assignment does not get over allocated and the assignment’s loading pattern is honored.

■

When forward scheduling, work is distributed between the task's Actuals Thru date or the Autoschedule date, whichever is later, and the task's finish date. If the

Autoschedule date is later than the task’s finish date, all work is placed on the task’s

Finish Date since the task duration can not be extended because the task is fixed.

■

■

When backward scheduling, work is distributed between the task's Finish Date or the Autoschedule date, whichever is earlier, and the task's Start date or the Actuals

Thru date. If the Autoschedule date is prior to the latter of the task Start date and the Actuals Thru date, all work is placed on the later date.

When scheduling variable assignments on locked and fixed tasks, neither the task's start nor finish are changed.

84 User Guide