Deadlines, on the other hand, are not used when calculating the schedule, and do not generate scheduling errors. Also, the user is not notified if a Deadline conflicts with a task’s Constraint Date, even when originally entering the Deadline or the constraint.
In a Schedule From Start project, a Deadline behaves like a Finish No Later Than constraint, except that scheduling is not affected. In a Schedule from Finish project, a task (the task has a ALAP constraint) will finish on its Deadline date unless a constraint or link pushes the task Finish to an earlier date.
Microsoft Project 2000 Help defines the calculation of Late Finish as follows: “When you first create a task, its Late Finish date is the same as the project finish date. As you link the task to predecessors and successors and apply any other constraints, Microsoft Project calculates the late finish date as the latest possible date this task could be finished, if all predecessor and successor tasks also start and finish on their late start and late finish dates. These calculations are based on a fixed task duration. If there is a leveling delay on the successor task, this delay is also figured into the date in the Late Finish field.”
When a Deadline is added to the task, Late Finish equals the earlier of the Deadline date or the date calculated according to the preceding definition, except for the following special cases:
· When a task has a MSO or MFO constraint and Tools/Options/Scheduling/ Tasks will always honor their constraint dates is set to ON, the Late Finish equals the Early Finish.
· When one of the task’s successors Late Start minus lag is earlier than the Deadline, the Late Finish equals that successor’s Late Start minus the lag.
· When a task has a SNLT or FNLT constraint, Late Finish is the earliest of Early Finish, Deadline, and any successor’s Late Start minus lag.
· When a task has no successor and Tools/Options/Calculations/”Calculate Multiple Critical Paths” is set to on, the Late Finish equals the Early Finish.
Slack may be increased or decreased according to the effect of the Deadline on Late Finish. This means that it is possible to have positive or negative slack that is greater than if the Deadline was not present.
Although not strictly related to Deadlines, Microsoft Project 2000 has two new calculated fields “Start Slack” and “Finish Slack.” These fields are used to store and display the start and finish slack calculations of a task. Previously these fields were used only in internal scheduling calculations and were not permanently stored. The new fields are also related to leveling.
Start Slack and Finish Slack are calculated as follows:
n Start Slack = Late Start minus Early Start
n Finish Slack = Late Finish minus Early Finish
|
|
For more information, see the Microsoft Project 2000 Online Help Topics Start Slack and Finish Slack. |
|
|
Try This: How a Deadline Affects the Late Finish On the previous page, we reviewed four scenarios where Deadlines do not affect how Late Finish is calculated. Here you will recreate one of those scenarios. |
1. With a partner, select one of the four scenarios as reviewed on the previous page.
2. In a new Project, recreate the scenario.
3. With another group, explain how you created the scenario and discuss the following questions: Why does it make sense for Late Finish not to equal the earlier of the Deadline or the Late Finish Date? How does this affect the calculation of the critical path? How does this affect the way this task is scheduled? How does this affect leveling?
Microsoft Project 2000 includes enhanced functionality of the WBS (Work Breakdown Structure) field. In addition, ten new custom Outline Code fields, Outline Code1 through Outline Code10, have been added for both tasks and resources.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.
