beginner: difficulties with timeline
Featured Partner
Top Posters
Zine Eddine
2 posts
Alex Lyaschenko
27 posts
mxsiegel
0 posts
Mattvtek
0 posts
Gareth Evans
3 posts
PP Admin
3, 129 posts
Rajkamal Tangirala
5 posts
Rahul Kumar
1 posts
blake333_
0 posts
Jeamiell Ostrovsky
2 posts
Our Partners
agree
One needs to consider the following factors when deciding which method to use to level a schedule.
1. The number of activities and relationships
2. The number of resources requiring leveling
3. The capability of the software
4. The skill level of the person using the software
5. Is the schedule to be statused or is the schedule a one off.
If I have a small schedule, say 20 activities, with one resource to level, and I am completing a what if analysis in MSP, I may use method 1, and drag an activity to level the histogram if I did not want to waste my time.
If I have a medium sized building project where I had a single crew completing some work and I wanted to show the crew the order I wanted them to complete the work in I would use method 2 and add some sequencing logic to order the tasks and level the resources. In this type of project it is acceptable to use this method and it creates a critical path that is resource driven. I would also add notes in the notes section stating the logic is sequencing logic.
If I have a large commissioning schedule with say 5,00 activities and 10 resources that have to be leveled I would use method 3.
There are a number of issues with leveling. Firstly a person needs to be very familiar with the software and understand all the issues that prevent a schedule from leveling. And secondly it is a requirement of a number of contracts to show a critical path and therefore method 2 has to be used level a schedule to show a critical path created by that resource.
I would agree that method 1 is not the best but both method 2 and 3 do both have their applications.
Paul E Harris
Eastwood Harris Pty Ltd
Planning and Scheduling Book Publishers
www.eh.com.au
Paul, both method 1 and 2 are nor preferable. These 2 will let the network more complicated. Method 3, resource levelling is the right direction.
Andreas
Microsoft Project, like most project planning and scheduling software packages, by default does not resource level which is the term used to prevent over allocation of resources. I would think the software is running as it is designed.
There are three basic methods principals of preventing resource allocation.
1. Applying constraints to activities so that tasks do not start until resources become available. This is usually not recommended as a delay in another task may result in an over allocation of resources.
2. Adding additional relationships, often called "Sequencing Logic" to prevent over allocation of resources.
3. Using the Resource Leveling feature of Microsoft Project.
I live in Melbourne, feel free to call me on 04 1118 7701 should you wish to discuss this with me a little further.
Regards
Paul E Harris
Eastwood Harris Pty Ltd
Planning and Scheduling Book Publishers
www.eh.com.au