I dont think that Overtime is the problem. I have project that has 14 structures on it. Not including the on & off site utilities. I have a critical path that runs through 2 of them. They all have to be done but 2 have the largest amount of activities in them and they both are on a Critical path to keep both of them moving. There are some off-site activitys that involve getting power to the site. This one is part of a change order and the owner wants me to take it off of CP so that he can say we dont get extra time to do the extra work.
You are very correct in saying that situation changes all the time as regards to critical path and floats all the time but if the critical path is identified carefully chance are it will remain more or less critical all through the life cycle of project.
As I understand Critical Path Analysis is the core of schedule control. Critical activities and paths are defined by the project management team based on the past experience and present constraints rather than just by running P3.
It has nothing to do with the number of critical paths.
But, if any activity has been scheduled with overtime in-built, one should not do that and if overtime activity is on a critical path, then it is not supposed to be. (No harm in giving overtime, but always beneficial as a planner not to schedule with overtime).
Primavera is working according to "Critical Path METHOD". This does not mean that a critical path is so important as discussions make believe. If you use your time and resources in a proper way, you will have a critical PROJECT. (or a waste of resources) Of course one path ist the longest, but in most projects this can change very easy to a total different path, so dont focus to much on it.
An other thing is, if you look at the discussion "Float in program.. Whom does it belong to?" Actually this question cannot been answered so easily - so take care that a schedule is linked in such a proper way that no float is clearly vissible. And if there is no float - there will be no critical path. So do not show too much critical path as this will mean that somebody wants to take your float!
Do take care that, dont schedule a project so that overtime is required to complete it, since if probelsm are encountered, it may not be possible to work more overtime to solve them.
Adjusting the resources is not always possible. Applying overtime often increases errors, leading to rework,
which may mean that you don’t get the job done any faster than if you had simply worked a normal schedule.
Further, there is always a point of diminishing returns when you add bodies to a task. At some point the workers just get in one another’s way, actually slowing work down rather than speeding it. Overtime should be kept in reserve in case it is needed to resolve problems, and it is never a good idea to schedule a project so that overtime needs to be worked just to meet the original schedule.
You are being told correctly as "you should not have too many critical paths on your schedule".
Theoratically you are correct that in big complex networks we can have a number of longest path or zero TF paths. This however is something mechanical and the role of project management team in general and the planning engineer in particular is to study the network closely and identify the critical activities which really have the potential to delay the project and keep a tight focus on their progress.
In absence of a clearly identified critical path and having lots of critical activites will lead to loosing focus and also will have less or no control over all of them. So usually we adjust our network and keep one critical path and then there are two or three more which we call near criticcal paths.
There is a field in activity view called critical that has a yes or no value. Depending on the way you have chosen to calculate (longest path or least float). In Version 5 you can calcuate multiple float paths to determine near critical paths. Bottom line is you can create a filter that keys on the "critical" field.
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.
Nice paper on As-Built Critical Path (ABCP)
http://www.planningengineers.org/publications/papers.aspx
Cheers,
Raviraj A Bhedase
I dont think that Overtime is the problem. I have project that has 14 structures on it. Not including the on & off site utilities. I have a critical path that runs through 2 of them. They all have to be done but 2 have the largest amount of activities in them and they both are on a Critical path to keep both of them moving. There are some off-site activitys that involve getting power to the site. This one is part of a change order and the owner wants me to take it off of CP so that he can say we dont get extra time to do the extra work.
I think this is BS.
Dear Hannes,
You are very correct in saying that situation changes all the time as regards to critical path and floats all the time but if the critical path is identified carefully chance are it will remain more or less critical all through the life cycle of project.
As I understand Critical Path Analysis is the core of schedule control. Critical activities and paths are defined by the project management team based on the past experience and present constraints rather than just by running P3.
Regards,
Ashraf
Ashraf,
It has nothing to do with the number of critical paths.
But, if any activity has been scheduled with overtime in-built, one should not do that and if overtime activity is on a critical path, then it is not supposed to be. (No harm in giving overtime, but always beneficial as a planner not to schedule with overtime).
Just a advise.
Cheers,
Raviraj
Some remarks to Critical paths:
Primavera is working according to "Critical Path METHOD". This does not mean that a critical path is so important as discussions make believe. If you use your time and resources in a proper way, you will have a critical PROJECT. (or a waste of resources) Of course one path ist the longest, but in most projects this can change very easy to a total different path, so dont focus to much on it.
An other thing is, if you look at the discussion "Float in program.. Whom does it belong to?" Actually this question cannot been answered so easily - so take care that a schedule is linked in such a proper way that no float is clearly vissible. And if there is no float - there will be no critical path. So do not show too much critical path as this will mean that somebody wants to take your float!
Ravi,
What is the point you are trying to make?
What has working overtime to do with having a number of critical paths in the project network?
Regards,
Ashraf
Hi Ben,
Do take care that, dont schedule a project so that overtime is required to complete it, since if probelsm are encountered, it may not be possible to work more overtime to solve them.
Adjusting the resources is not always possible. Applying overtime often increases errors, leading to rework,
which may mean that you don’t get the job done any faster than if you had simply worked a normal schedule.
Further, there is always a point of diminishing returns when you add bodies to a task. At some point the workers just get in one another’s way, actually slowing work down rather than speeding it. Overtime should be kept in reserve in case it is needed to resolve problems, and it is never a good idea to schedule a project so that overtime needs to be worked just to meet the original schedule.
Cheers,
Raviraj A Bhedase
Hi Ben,
You are being told correctly as "you should not have too many critical paths on your schedule".
Theoratically you are correct that in big complex networks we can have a number of longest path or zero TF paths. This however is something mechanical and the role of project management team in general and the planning engineer in particular is to study the network closely and identify the critical activities which really have the potential to delay the project and keep a tight focus on their progress.
In absence of a clearly identified critical path and having lots of critical activites will lead to loosing focus and also will have less or no control over all of them. So usually we adjust our network and keep one critical path and then there are two or three more which we call near criticcal paths.
Regards,
Ashraf
Sorry if this is off subject. I am being told that I can not have "To many multiple paths on my critical path"
Does anyone have a stance on this subject? What constitutes a critical path other than float or path??
Why can’t there be several paths that all come down to Substantial completion?
There is a field in activity view called critical that has a yes or no value. Depending on the way you have chosen to calculate (longest path or least float). In Version 5 you can calcuate multiple float paths to determine near critical paths. Bottom line is you can create a filter that keys on the "critical" field.
Failing that you could filter on Longest Path EQ Yes
You should find a filter already there called "near critical activities". Or create your own TF<1 will select all critical activities.