Project summary task not updating
“Hammock”* and “Level of Effort” (LOE) tasks in project schedules provide two similar approaches to summarizing and reporting the overall time consumed by a collection of other tasks.Typically, hammock or LOE tasks are used to represent the indirect management and other support activities associated with the primary tasks, and they are often loaded with management and other indirect resources.This satisfies the requirement that such tasks not be included in any calculations of the project’s Critical Path.Since some users have reported inadvertent introduction of splits into hammock tasks during cost updating, I added a little mini-procedure to close all such splits that are 100% in the future, prior to updating the hammock duration.This macro/vba code comprises a subroutine and a custom function that should be pasted together into a single module in the Visual Basic Editor.
it sets an early constraint (SNET or FNET) and adjusts the task duration so that the task spans between the two linked dates.The start dates for a hammock were defined by its Start-Start predecessors; finish dates came from its Finish-Finish successors; the same activity could not be included in both groups.Oracle’s Primavera P6, a newer application, allows for LOE activities that inherit their dates from the primary tasks that are included in their “predecessors” and “successors” lists.Hammock and LOE tasks are essentially the same, though minor differences exist in the implementation by different software.
Since hammocks and LOE tasks do not possess any driving logic, they should be excluded from any formal definition of the Critical Path for the project.
Unfortunately, even if the links remain stable and updated (which is not guaranteed), the sources of these adjustments remain hidden.