From the terminology you use, I think you are using Primavera P6?
If so you can set a Project-level "must finish by" constraint of 1st Jan 18 from within the Enterprise>Projects screen, then delete the contractual milestone, and filter on longest path.
Should get you what you need.
The other option if you are wedded to the contractual milestone being there, is to work out how much float the longest path has (typically how much float your planned completion milestone has), and then filter for total float less than or equal to that value.
This second approach may give you some spruious results if you have other hard constraints in your schedule, or use multiple calendars which can confuse Primavera's float calcs.
Cheers,
G
Member for
21 years 7 months
Member for21 years8 months
Submitted by Rafael Davila on Tue, 2016-09-06 02:38
You can keep fixed in place the Contractual Milestone(s) with start and finish date constraints, without any successor to avoid negative float. Then using the Hammock, a task that will consume delays and reduce in duration without having an impact on your Contract Completion date you can model Terminal Float and Critical Chain Project Management [CCPM] as well.
If the project is delayed because of the contractor there will be no change in contract finish milestone and therefore if there is Terminal Float available it will be reduced at his expense.
Member for
9 years 3 months
Member for9 years3 months
Submitted by Charlotte.Asta… on Mon, 2016-09-05 17:13
Which contract is this under? If it is NEC3 then you are entitled to Terminal Float (this is time owned by the contractor), You can place a bar above contract compltion to on theory fill the gap, if using Asta PP you can use the buffer task function which is task that will consume delays and reduce in duration without having an impact on your Contract Completion date.
Member for
16 years 7 monthsDiane, From the terminology
Diane,
From the terminology you use, I think you are using Primavera P6?
If so you can set a Project-level "must finish by" constraint of 1st Jan 18 from within the Enterprise>Projects screen, then delete the contractual milestone, and filter on longest path.
Should get you what you need.
The other option if you are wedded to the contractual milestone being there, is to work out how much float the longest path has (typically how much float your planned completion milestone has), and then filter for total float less than or equal to that value.
This second approach may give you some spruious results if you have other hard constraints in your schedule, or use multiple calendars which can confuse Primavera's float calcs.
Cheers,
G
Member for
21 years 7 monthsYou can keep fixed in place
You can keep fixed in place the Contractual Milestone(s) with start and finish date constraints, without any successor to avoid negative float. Then using the Hammock, a task that will consume delays and reduce in duration without having an impact on your Contract Completion date you can model Terminal Float and Critical Chain Project Management [CCPM] as well.
If the project is delayed because of the contractor there will be no change in contract finish milestone and therefore if there is Terminal Float available it will be reduced at his expense.
Member for
9 years 3 monthsHi Diane,Which contract is
Hi Diane,
Which contract is this under? If it is NEC3 then you are entitled to Terminal Float (this is time owned by the contractor), You can place a bar above contract compltion to on theory fill the gap, if using Asta PP you can use the buffer task function which is task that will consume delays and reduce in duration without having an impact on your Contract Completion date.
I hope this helps.
Charlotte.