Here's how you get what you want: as Alexandre suggests, apply a SNET (or better a FNET) constraint of 18May'22 to ID6. Then also apply a Deadline=18May'22 to ID6. (Use a clocktime format so you can confirm the time of day is the same for both.) The result will be TS=0 on ID6 and TS=3d on ID47.
Here your ID6 is a "Contract Date Milestone" for PAT complete. I would also recommend a separate "Forecast Date Milestone" for PAT complete - logically inserted between ID47 and ID6, but with no constraint or deadline.
OKay i did do that. But then the date become 18MAY but the float becomes 8 days. I am guessing its calculating the float from the end date of the project which is 27MAY2022
Member for
22 years 9 months
Member for22 years9 months
Submitted by Alexandre Faul… on Thu, 2020-04-30 19:40
Member for
18 years 11 monthsHere's how you get what you
Here's how you get what you want: as Alexandre suggests, apply a SNET (or better a FNET) constraint of 18May'22 to ID6. Then also apply a Deadline=18May'22 to ID6. (Use a clocktime format so you can confirm the time of day is the same for both.) The result will be TS=0 on ID6 and TS=3d on ID47.
Here your ID6 is a "Contract Date Milestone" for PAT complete. I would also recommend a separate "Forecast Date Milestone" for PAT complete - logically inserted between ID47 and ID6, but with no constraint or deadline.
Good luck, tom
Member for
13 years 1 monthOKay i did do that. But then
OKay i did do that. But then the date become 18MAY but the float becomes 8 days. I am guessing its calculating the float from the end date of the project which is 27MAY2022
Member for
22 years 9 monthsHello,I don't understand why
Hello,
I don't understand why you put a FNLT constraint on activityy #6;
try a Start No Earlier Than instead and set the date on May 18th
Alexandre