Schedule Levels...

When producing programmes for a project, I use the following levels of programmes:

• LEVEL 1 : Project Management overview schedule/programme, by Project Phase.
• LEVEL 2 : Area or Process/Utility Unit schedule/programme, by Project Phase by Area or Unit.
• LEVEL 3 : Discipline schedule/programme, by Project Phase by Area/Unit by Single or Multi-disciplines.
• LEVEL 4 : Main Activities schedule/programme, by Project Phase by Area/Unit by Single or Multi-disciplines by Main Activities.
• LEVEL 5 : Detail Activities schedule/programme, by Project Phase by Area/Unit by Single or Multi-disciplines by Detail Activities.
• LEVEL 6 : Micro-detail Activities schedule/programme, by Project Phase by Area/Unit by Single or Multi-disciplines by Micro-detail Activities.

One School of Thought:

Level 1 to 5 should have a standard definition.
My definition of level 1 - 4 is as follows:

1. Level 1 - Whole Project
2. Level 2 - Section or Zone ie Block A Block B etc
3. Level 3 - Task Summary
4. Level 4 - Task - which is where the logic is applied

Many planners place logic at level 3 using SS FF links with lags to create overlaps.This is bad planning practice because you do not get a dynamic and resposive critical path.

Another School of Thought:

I use is something along these lines.

1. Level 1 - The Project
2. Level 2 - Discipline
   1. Level 2 1. Site Prep, 2.2 Earthworks etc etc
3. Level 3 - Area / location
4. Level 3.1 CH 0-300 3.2 CH 300-600

I then use activity coding if I want to see all the works for CH0-300 etc