.... "Also if you have a constraint date of February 15, 2010 but due to the lack of progress and the logic the date for this activity is calculated to be later than February 15, 2010. This is also a unsatisfied constraint date"
Seems like Zoltan hit the nail on the head, "as projected will not be met".
Member for
21 years 7 months
Member for21 years8 months
Submitted by Rafael Davila on Tue, 2009-12-15 13:10
Does the report specify the unsatisfied constraints activities? Remember the report not only warns about last update period but also warns about other prior periods, if any prior constrained date activity was updated before with a date after the constraint it still will show.
About correcting out-of-sequence logic, easier said than done, at home usually we do not resolve out-of-sequence when progress override option is a better approximation on logic than the infamous retained logic option many do favor.
On the Activities with the "Unsatisfied constraints" my initial thoughts were on the same lines as yours but the prject data date is 18/10/09 and the constraints in question are 08/01/10 & 02/02/10 both are unprogressed. So not sure what it is telling me!
On the Activities with the "Unsatisfied relationships" I also schedule on retained logic. I did re-schedule on progress overide & interestinlgy did get a different result
0 on retained logic & 7 on progress overide.
I have got 22 activities that are out of sequence so I am assuming that 7 of the 22 are causing a delay to a successor somewhere down the line. So that bit does seem to make sense.
Rob
Member for
21 years 7 months
Member for21 years8 months
Submitted by Rafael Davila on Tue, 2009-12-15 12:02
Activities with unsatisfied constraints? 2 , none have any relationships ==>> most probably constraint date was earlier than DD and you did not actualized those two activities, the updating moved them to the DD.
Activities with unsatisfied relationships? 0, I am on retained logic ==>> retained logic does not allow unsatisfied relationship to happen, if you switch to progress override, out-of-sequence will happen and unsatisfied relationships will also happen.
Remember neither retained logic nor progress override solve the issue on out-of-sequence, you still got to solve the logic issue. The way I schedule my jobs this is usually fixed with a change in lag durations, as they are somewhat arbitrary, just you planned to wait some time and then you change your mind. This is difficult to swallow for those who insist scheduling is an exact science and the problem is on your use of lag.
Member for
21 years 7 monthsRE: What does this Mean? (Unsatisfied constraints / Relati
.... "Also if you have a constraint date of February 15, 2010 but due to the lack of progress and the logic the date for this activity is calculated to be later than February 15, 2010. This is also a unsatisfied constraint date"
Seems like Zoltan hit the nail on the head, "as projected will not be met".
Member for
21 years 7 monthsRE: What does this Mean? (Unsatisfied constraints / Relati
Rob
Does the report specify the unsatisfied constraints activities? Remember the report not only warns about last update period but also warns about other prior periods, if any prior constrained date activity was updated before with a date after the constraint it still will show.
About correcting out-of-sequence logic, easier said than done, at home usually we do not resolve out-of-sequence when progress override option is a better approximation on logic than the infamous retained logic option many do favor.
Best regards,
Rafael
Member for
21 years 9 monthsRE: What does this Mean? (Unsatisfied constraints / Relati
Hi Rafael,
Thanks for the reply.
On the Activities with the "Unsatisfied constraints" my initial thoughts were on the same lines as yours but the prject data date is 18/10/09 and the constraints in question are 08/01/10 & 02/02/10 both are unprogressed. So not sure what it is telling me!
On the Activities with the "Unsatisfied relationships" I also schedule on retained logic. I did re-schedule on progress overide & interestinlgy did get a different result
0 on retained logic & 7 on progress overide.
I have got 22 activities that are out of sequence so I am assuming that 7 of the 22 are causing a delay to a successor somewhere down the line. So that bit does seem to make sense.
Rob
Member for
21 years 7 monthsRE: What does this Mean? (Unsatisfied constraints / Relati
Rob,
Activities with unsatisfied constraints? 2 , none have any relationships ==>> most probably constraint date was earlier than DD and you did not actualized those two activities, the updating moved them to the DD.
Activities with unsatisfied relationships? 0, I am on retained logic ==>> retained logic does not allow unsatisfied relationship to happen, if you switch to progress override, out-of-sequence will happen and unsatisfied relationships will also happen.
Remember neither retained logic nor progress override solve the issue on out-of-sequence, you still got to solve the logic issue. The way I schedule my jobs this is usually fixed with a change in lag durations, as they are somewhat arbitrary, just you planned to wait some time and then you change your mind. This is difficult to swallow for those who insist scheduling is an exact science and the problem is on your use of lag.
This from my experience using other software.
Best regards,
Rafael