I tried the feature you described. It is a large step forward though due to the poor leveling algorithms the results are not reliable.
In the sample project I created the resource constrained float for the project as a whole is 5 days and only two activities are resource critical that is obviously wrong. The project schedule was uploaded at http://www.ephotohut.net/viewpic.cfm?pic=280805100948.jpg
In the text field next to activity names you will find assigned resource abbreviations.
You have to deselect the leveling option "Preserve scheduled early and late dates", otherwise it will keep the critical path of the original unleveled schedule.
I did not see this feature in Primavera software. I will try to have a look. I have an access to P3ec and hope that there is something like this too that I did not notice. Please advise me where to find.
Spider Project calculates Resource Critical Path and resource constrained floats since 1992. So when Goldratt suggested Critical Chain in 1997 I had thought that at last some guy in the West understood that resources are of essence. I talked about Resource Critical Path in my presentations at PMI conferences in 1994 and 1996, but had no feedback.
This discussion probably belongs somewhere else, so with the risk that we get thrown out of this forum category:
I learned about the subject as "resource critical activities" from Fromdahl way before Goldratt started to claim the credit for it.
I don’t know which Primavera product you are referring to but I’m talking about Project Management 4.1 which is part of the IT Project Office (a.k.a. TeamPlay) suite. It shows a critical path that marks resource critical activities, which makes a lot more sense than relying on a precedence float concept that doesn’t hold in resource constrained schedules.
I agree that Primavera suggests more options and one of them that is most valuable is the ability to add custom leveling criteria and priorities. Unfortunately these simple criteria rarely lead to optimal solutions though an initial schedule may be improved. I don’t understand why Primavera and MS Project developers don’t even try to optimize project resource-constrained schedules. There are unused reserves that can save a lot of time and money. One of Spider Project advantages that I consider as the most attractive is its ability to optimize resource-constrained schedules. But it is attractive to those who understands the problem. I suspect (as you do) that most schedulers just believe that the software provides an optimal solution without trying to analyze scheduling results.
I don’t understand what do you mean by "a critical path that is also making sense after leveling".
A set of activities with the zero time reserves constitute resource-critical path (you know it as Critical Chain). Do you mean this or something else? I did not noticed that Primavera started to calculate resource critical path. And Total Float (Slack) fields in both products show wrong reserves if resources are limited.
When I said resource leveling is complex I was certainly referring to the fact that the mainstream scheduling software rarely provides the optimal schedule after leveling.
There are however significant differences between MSP and Primavera Project Management in this respect:
- A leveling log that shows what is directly an indirectly delayed
- The ability to level selective resources
- The ability to add custom leveling criteria and priorities
- The ability to avoid path conversion
- Independent resource leveling (5.1)
And last but not least, a critical path that is also making sense after leveling.
I bet Spider software has a few extras but it is not entirely correct to state that MSP and Primavera are providing the same functionality in this area.
Hope this helps more people to understand that this subject is more than just pushing buttons.
And you will be happy (with MS Project or Primavera – does not matter much) until one day you will discover that the resource constrained schedules advised by the package can be dramatically improved.
It is interesting that nobody discusses the quality of resource constrained schedules produced by PM software.
The MS Project leveling capabilities are very limited and you should certainly not expect any miracles from it.
Furthermore leveling itself is quite complex so you really need to understand what you are doing certainly if want to level resources across multiple projects.
When MSP hits an overallocation it cannot resolve it starts to complain (unless you switch scheduling messages off) and then youll need to find out where that problem comes from.
Here a just a few tips:
- Constraints in the schedule are a big killer for leveling
- If you constrain MSP to schedule "only within the available slack" it cant extend the end date so it has less room to find a solution.
- Make sure your schedules are simple and start going to the schedules in step-wise approach. Add two schedules to the master and see how this works.
- Start with one simple schedule until you have reached acceptable results and dont try to level all 20 concurrent schedules in one go.
Hope this helps,
Niek.
P.S. If the above does not help, buy yourself Primavera Project Management 5.0, open all the 20 schedules in one go and level them like it is a single project.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
Niek,
I tried the feature you described. It is a large step forward though due to the poor leveling algorithms the results are not reliable.
In the sample project I created the resource constrained float for the project as a whole is 5 days and only two activities are resource critical that is obviously wrong. The project schedule was uploaded at http://www.ephotohut.net/viewpic.cfm?pic=280805100948.jpg
In the text field next to activity names you will find assigned resource abbreviations.
In any case it is a great improvement.
What do you think about the sample project?
Regards,
Vladimir
Vladimir,
You have to deselect the leveling option "Preserve scheduled early and late dates", otherwise it will keep the critical path of the original unleveled schedule.
Im curious to hear your findings.
Cheers,
Niek.
Hi Niek,
I did not see this feature in Primavera software. I will try to have a look. I have an access to P3ec and hope that there is something like this too that I did not notice. Please advise me where to find.
Spider Project calculates Resource Critical Path and resource constrained floats since 1992. So when Goldratt suggested Critical Chain in 1997 I had thought that at last some guy in the West understood that resources are of essence. I talked about Resource Critical Path in my presentations at PMI conferences in 1994 and 1996, but had no feedback.
Thank you for an interesting information.
Vladimir
Hi Vladimir,
This discussion probably belongs somewhere else, so with the risk that we get thrown out of this forum category:
I learned about the subject as "resource critical activities" from Fromdahl way before Goldratt started to claim the credit for it.
I don’t know which Primavera product you are referring to but I’m talking about Project Management 4.1 which is part of the IT Project Office (a.k.a. TeamPlay) suite. It shows a critical path that marks resource critical activities, which makes a lot more sense than relying on a precedence float concept that doesn’t hold in resource constrained schedules.
Cheers,
Niek.
Niek,
I agree that Primavera suggests more options and one of them that is most valuable is the ability to add custom leveling criteria and priorities. Unfortunately these simple criteria rarely lead to optimal solutions though an initial schedule may be improved. I don’t understand why Primavera and MS Project developers don’t even try to optimize project resource-constrained schedules. There are unused reserves that can save a lot of time and money. One of Spider Project advantages that I consider as the most attractive is its ability to optimize resource-constrained schedules. But it is attractive to those who understands the problem. I suspect (as you do) that most schedulers just believe that the software provides an optimal solution without trying to analyze scheduling results.
I don’t understand what do you mean by "a critical path that is also making sense after leveling".
A set of activities with the zero time reserves constitute resource-critical path (you know it as Critical Chain). Do you mean this or something else? I did not noticed that Primavera started to calculate resource critical path. And Total Float (Slack) fields in both products show wrong reserves if resources are limited.
Yes Vladimir, you are absolutely right.
When I said resource leveling is complex I was certainly referring to the fact that the mainstream scheduling software rarely provides the optimal schedule after leveling.
There are however significant differences between MSP and Primavera Project Management in this respect:
- A leveling log that shows what is directly an indirectly delayed
- The ability to level selective resources
- The ability to add custom leveling criteria and priorities
- The ability to avoid path conversion
- Independent resource leveling (5.1)
And last but not least, a critical path that is also making sense after leveling.
I bet Spider software has a few extras but it is not entirely correct to state that MSP and Primavera are providing the same functionality in this area.
Hope this helps more people to understand that this subject is more than just pushing buttons.
Cheers,
Niek.
Thank you guys for your help .... will go and look at it in more detail.
And you will be happy (with MS Project or Primavera – does not matter much) until one day you will discover that the resource constrained schedules advised by the package can be dramatically improved.
It is interesting that nobody discusses the quality of resource constrained schedules produced by PM software.
JG,
The MS Project leveling capabilities are very limited and you should certainly not expect any miracles from it.
Furthermore leveling itself is quite complex so you really need to understand what you are doing certainly if want to level resources across multiple projects.
When MSP hits an overallocation it cannot resolve it starts to complain (unless you switch scheduling messages off) and then youll need to find out where that problem comes from.
Here a just a few tips:
- Constraints in the schedule are a big killer for leveling
- If you constrain MSP to schedule "only within the available slack" it cant extend the end date so it has less room to find a solution.
- Make sure your schedules are simple and start going to the schedules in step-wise approach. Add two schedules to the master and see how this works.
- Start with one simple schedule until you have reached acceptable results and dont try to level all 20 concurrent schedules in one go.
Hope this helps,
Niek.
P.S. If the above does not help, buy yourself Primavera Project Management 5.0, open all the 20 schedules in one go and level them like it is a single project.