Hammocks, LOE and summary activities are three completely different types of activity; unfortunately the ignorance of many software developers (or developers placing their marketing needs ahead of accuracy) has resulted in mass confusion to the point where even the current PMBOK® Guide 5th Edition is confusing.
All three activity types can be used to carry resources for a period of time and both summary activities and hammocks can be used to create summary reports, but the differences in the way these three activity types are created and used is significant.
Summary activities are part of the schedule’s coding structure and roll up a series of directly related activities within the schedule’s coding structure into one summary task (sometimes called ‘Main Activities’). Most tools have the ability to incorporate several layers of summary activity which can be designed to align with the project’s work breakdown structure (WBS).
Summary activities do not have a set duration; the duration is calculated from the underlying activities in the coding structure and where float is shown the summary float is based on the float on the last activity.
The summary activities start is the earliest ES of the underlying activities, its finish is the latest EF of the underlying activities and its latest finish is the latest LF of the underlying activities. Summary activities should not be linked: the logical linking in the schedule should always occur at the activity level.
Summary activities are used for reporting purposes and can also carry costs and resources attributed to the portion of the schedule they summarise.
Level of effort (LOE) activities are aligned with LOE work packages in the WBS, and earned value systems. The Earned Value standards define LOE work packages as having a set duration and once started, the work package is assumed to progress as planned (there is no schedule variance until after the package is complete). LOE is used for work packages where progress cannot easily be measured and nature of the work is unsuitable for using ‘apportioned effort’ to calculate progress. Typically, LOE is used for ‘overhead’ resources and costs such as the project’s project management effort, security, quality inspections, etc.
The equivalent use in a schedule is a normal activity with a defined duration that carries a set of resources or costs (based on the LOE work package) and where progress will be assumed to equal plan once the activity starts.
The advantage of LOE over summary activities is the LOE duration is not dependent on any roll up of underlying activities and each LOE activity is independent of the overall project coding structure. It is not uncommon to see several LOE activities assigned to an ‘overhead’ section within the overall project coding structure. The use of LOE activities allows the schedule to accurately reflect the data in the WBS and EV systems.
The disadvantage of LOE (seen in the diagram above) is the LOE activity can easily turn into a critical activity based on its unchanging duration. This means the activity has to be carefully managed by the scheduler.
LOE activities should be logically linked into the schedule in preference to positioning the activity with a constraint, and in most respects are normal activities. LOE activities are used to carry costs and resources attributed to the time period of their set duration.
Hammock activities are a cross between a link and an activity. A hammock is an activity that spans between two points in a schedule. Having no set duration of its own, its duration is derived from the difference in time between the two ‘connection points’ in the schedule. It can be thought of as ‘hanging’ between these two points in the same way a normal hammock may hang between two trees.
While a hammock has no predetermined duration, it can have descriptions, codes, calendars, resources, costs and other attributes of a normal activity. Hammocks are very useful for carrying time related costs and determining the duration of supporting equipment needed for a project, as well as being used to create summary reports.
Hammocks originated in Activity-on-Arrow networks as activities which are connected across a series of activities from the ‘i node’ of a specific start activity to the ‘j node’ of the last activity in the span. The hammock’s duration is calculated from its ‘i node’ early start (ES) to its ‘j node’ late finish (LF), and is derived from the number of working periods in the calendar attributed to the Hammock between these two dates.
Hammocks in precedence networks (PDM) have a similar function but are activities linked Start-to-Start at the beginning to the first activity in the span, and Finish-to-Finish at the end to the last activity in the span.
As with both LOE and summary activities, hammocks can be used to carry overhead costs and resources for a section of the project, rather than trying to spreading them out across all of the associated activities.
The example I use when teaching is using a hammock to understand the time a tower crane will be needed on a high rise construction project. The start of the crane working on the site is driven by the concreting of the foundations and erection of the crane. It is then required through to the time the last heavy lifting to the roof is finished (typically roof mounted plant and equipment) once this activity is finished the crane can be removed. The duration of the hammock is derived from the timing of these two events and is calculated automatically by scheduling tools that implement hammocks correctly (along with the total cost of the resource).
Importantly, the duration and cost are recalculated each time the schedule is adjusted during planning or when the schedule is updated during the progress of work on site so the project’s overall cost and resource requirements remain accurately aligned to the actual needs of the project.
The benefit of a hammock over LOE is the hammock’s duration is flexible and adjusts automatically as the underlying logic in the schedule changes, whereas LOE activities have a set duration that requires manual adjustment.
The benefit of a hammock over a summary activity is that its connection points do not need to be in the same part of the schedule’s coding/summarisation structure. Summary activities are an integral part of the schedule’s coding structure and can only summarise lower level tasks that are directly connected within the coding system.
Hammocks are not dependent on any coding structure and therefore the hammock can connect from any point in the schedule logic to any other point; in the example above, from the part of the schedule dealing with excavation and foundations to the part of the schedule dealing with installing mechanical plant and equipment.
Summary activities, LOE and hammocks are distinctly different activity types; each has its advantages and limitations and very few tools correctly implement all three types. One of the few tools in the current market that implements hammocks properly is Micro Planner X-Pert; it’s worth downloading a free sample version of this tool to see how they work.
Unfortunately many software tools that do not have the capability to implement hammocks correctly try to hide this deficiency by confusing a hammock with either an LOE or a summary activity. Others choose to misname functions that are close to one of the three basic options, for example, Primavera calling its implementation of a hammock ‘Level of Effort’; why Oracle would choose to call a task that has a variable duration an LOE task when the key determinate of a LOE work package is a set duration is beyond my comprehension.
More generally, the fundamental question as to why the publishers of scheduling tools continue this confusing practice is hard to understand. Is it ignorance, or deliberate misinformation intended to create a perceived competitive advantage? From the perspective of trying to develop a professional practice around the project controls function, neither of these reasons is acceptable!
Every other profession take great care to ensure their special language and naming conventions are accurate and unambiguous. Until scheduling reaches this basic level of maturity, where one name consistently means one thing, all we are doing is creating confusion and devaluing everything we do.