Both the solutions in the first two posts will give you what you want.
I strongly advise you setup a dummy project of 6 to 10 activities and trial these solutions thoroughly before applying either. -You need to understand fully the implications before you risk using them on a live project, and your last post suggests you don't understand them very well at the moment.
Personally, I would use mandatory constraints rather than lag, as you would have to manually adjust the lag values after each update to maintain the float calculations you want, whereas mandatory constraints will not suffer from this. Mandatory constraints are also easier to toggle on and off, so you can turn them on for reporting purposes, and then take them off again to see the "true" critical path running through your project and actually plan the job properly.
Be aware though that both the solutions presented run the risk of generating "false" dates downstream of where you add the lag or constraint. -Which is why it's so important to know what you are doing when you use them.
thanx guys but i dont want to show float according to one project completion date
i want to show float according to each sections completion date
I searched for long on the net and apparently the only way to do this in P6 is to split the sections up and create mini programs for each section so that primavera sees each section as a program on its own and then calculates the critical path and float for that section on its own, how true is this ?
The milestones in every section should be linked with the Project Completion Date milestone and add lags equal to Projected Cpmpletion date - Milestone dates.
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.
Reece,
Milestone Date of ??? to be linked to last activity within a Section.
Is this milestone is your projected date to complete the section or the entire project?
sorry guys i think my wording and question was wrong, i understand how float works and that it needs to be linked up
it should have read float = milestone date - last activity in section completion date
see below
http://www.aboutcivil.com/answers/Primavera/Multiple-Critical-Paths-P6-In-MSP-I-set-a-deadline-date-on-milestones-and-it_579
Reece,
Both the solutions in the first two posts will give you what you want.
I strongly advise you setup a dummy project of 6 to 10 activities and trial these solutions thoroughly before applying either. -You need to understand fully the implications before you risk using them on a live project, and your last post suggests you don't understand them very well at the moment.
Personally, I would use mandatory constraints rather than lag, as you would have to manually adjust the lag values after each update to maintain the float calculations you want, whereas mandatory constraints will not suffer from this. Mandatory constraints are also easier to toggle on and off, so you can turn them on for reporting purposes, and then take them off again to see the "true" critical path running through your project and actually plan the job properly.
Be aware though that both the solutions presented run the risk of generating "false" dates downstream of where you add the lag or constraint. -Which is why it's so important to know what you are doing when you use them.
Cheers,
G
thanx guys but i dont want to show float according to one project completion date
i want to show float according to each sections completion date
I searched for long on the net and apparently the only way to do this in P6 is to split the sections up and create mini programs for each section so that primavera sees each section as a program on its own and then calculates the critical path and float for that section on its own, how true is this ?
Hi,
The milestones in every section should be linked with the Project Completion Date milestone and add lags equal to Projected Cpmpletion date - Milestone dates.
Did you try to assign mandatory constraints of these milestone ?