Project Sample consists of 4 activities and finish milestone.
Activities 1, 2 and 4 have 10 days duration, duration of activity 3 is 1 day, activity 5 has zero duration (milestone).
Activity 2 follows activity 1, activity 4 follows activity 3. Activities 2 and 4 precede activity 5. All dependencies are Finish-to-Start.
Project resources include one unit of resource A and one unit of resource B.
Resource A is assigned to activities 1 and 3, resource B is assigned to activities 2 and 4.
Project schedule calculated by P3e using default leveling algorithm has 30 days duration – project starts with activity 1, then 2, then 4. Activity 3 is planned after activity 1 finish.
The same schedule is calculated by MS Project. These packages calculate the same resource-constrained schedules but different activity floats. Both results are wrong.
P3e shows that activity 4 has 10 days float. Can you explain this? It is interesting to understand the meaning of 10 days total float of the last activity in the schedule.
By the way the optimal schedule for this project lasts 21 day and starts with activity 3.
Try this example or any other project with limited resources. You will notice that total floats calculated in resource-constrained schedules are not feasible. Most planners do not level project resources and just do not notice serious problems with resource constrained scheduling that exist in many packages.
I found the answer in the book. The calculation is, depending on your settings (early or late), the float between the earliest early start and the latest early start for the activites under that summary level. I find it to be a confusing number for a project manager and trying to explain it didnt help. What would be nice is if I could show the activity float without the summary.
This came about when a client p.m. asked why there was float in an area that the critical path "passed through". He ended up righting it off to another quirk of P3.
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.
Thanks a lot Vladimir,
Now it is clear to me.
Regards.
Marcio Eduardo.
Marcio,
I suggest to consider one very simple example.
Project Sample consists of 4 activities and finish milestone.
Activities 1, 2 and 4 have 10 days duration, duration of activity 3 is 1 day, activity 5 has zero duration (milestone).
Activity 2 follows activity 1, activity 4 follows activity 3. Activities 2 and 4 precede activity 5. All dependencies are Finish-to-Start.
Project resources include one unit of resource A and one unit of resource B.
Resource A is assigned to activities 1 and 3, resource B is assigned to activities 2 and 4.
Project schedule calculated by P3e using default leveling algorithm has 30 days duration – project starts with activity 1, then 2, then 4. Activity 3 is planned after activity 1 finish.
The same schedule is calculated by MS Project. These packages calculate the same resource-constrained schedules but different activity floats. Both results are wrong.
P3e shows that activity 4 has 10 days float. Can you explain this? It is interesting to understand the meaning of 10 days total float of the last activity in the schedule.
By the way the optimal schedule for this project lasts 21 day and starts with activity 3.
Try this example or any other project with limited resources. You will notice that total floats calculated in resource-constrained schedules are not feasible. Most planners do not level project resources and just do not notice serious problems with resource constrained scheduling that exist in many packages.
Happy New Year!
Vladimir
Hi Vladimir,
Sorry, didnt know that. Coul u please explain me better?
Best Regards.
I hope that you know that P3e calculates wrong floats when resources are limited?
-100 negative float is bigger than -1 negative float.
Regards.
Marcio
Biggest negative float is the one closer to Zero
DO you agree ??
-100 and -1 Which one is bigger??
HEHE
Alex
I siad "biggest total float " ... but i was trying to say "biggest negative float"
Regards.
Dear all
A summary float under a group of activities is the "Least (minimun)" float within that group of activity
Why?? SIMPLE
because you want to know how critical is that group fo activity are when they are summarised.
Of if just one activity within that group of activity have a negative float the summary bar will also have a negative float
HTH
ALex
Hi Dave;
Thanks for your explanation. Is it in the P3e manual? Could u tell me the page so i can read?
Regards.
Marcio Eduardo
Marcio,
I found the answer in the book. The calculation is, depending on your settings (early or late), the float between the earliest early start and the latest early start for the activites under that summary level. I find it to be a confusing number for a project manager and trying to explain it didnt help. What would be nice is if I could show the activity float without the summary.
This came about when a client p.m. asked why there was float in an area that the critical path "passed through". He ended up righting it off to another quirk of P3.
Not usefull.
Thanks,
Dave
Dave;
As i know, in P3e, total float for summary bars is equal to the biggest total float in the activities that are under summary bar.
But im not totaly sure.
Regards.