Agree with David, another reaso why, as stated before, if a portion of the activity was realized you must keep on record that portion, you delete only the un-realized portion if the un-realized portion is no longer valid.
Member for
19 years 5 months
Member for19 years5 months
Submitted by David Barnett on Mon, 2013-11-04 14:37
One issue to consider is percentage progress. If there is any cost information attached to the activities they disappear with the activity and would skew you % progress position.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Sat, 2012-03-17 13:44
Keeping in current schedule activities no longer in use can cause some problems, merely changing duration to zero does not means logic after deletion is correct, is not always that simple, the blind application of "dissolve" function shall be avoided unless you know the reassigned links are correct, and this means among other things taking care of inherited lag values. I do not trust "dissolve" functionality at all.
Keep in mind activities are not always auto-updated and they must be actualized to actual dates if they happened or partially happened otherwise non fixed out-of-sequence logic might create issues, particularly with the retained logic option. Resource usage, resource leveling and cost issues can be another source of problems if you keep them.
If a portion of the activity was realized you must keep on record that portion, you delete only the un-realized portion if the un-realized portion is no longer valid.
After a Re-Baseline or an Update I would:
Always add a suffix to new activities codes /ID to prevent use of old activity codes/ID. This will make it clear and transparent they were added after initial Baseline. The suffix should tell me on what update it was added and will help with filtering.
Baselines are meant to be kept frozen, you never add/delete activities from the record/contractual baselines, you create new baselines that can contain new activities and shall not include deleted activities.
Member for
21 years 8 monthsAgree with David, another
Agree with David, another reaso why, as stated before, if a portion of the activity was realized you must keep on record that portion, you delete only the un-realized portion if the un-realized portion is no longer valid.
Member for
19 years 5 monthsOne issue to consider is
One issue to consider is percentage progress. If there is any cost information attached to the activities they disappear with the activity and would skew you % progress position.
Member for
21 years 8 monthsKeeping in current schedule
Keeping in current schedule activities no longer in use can cause some problems, merely changing duration to zero does not means logic after deletion is correct, is not always that simple, the blind application of "dissolve" function shall be avoided unless you know the reassigned links are correct, and this means among other things taking care of inherited lag values. I do not trust "dissolve" functionality at all.
Keep in mind activities are not always auto-updated and they must be actualized to actual dates if they happened or partially happened otherwise non fixed out-of-sequence logic might create issues, particularly with the retained logic option. Resource usage, resource leveling and cost issues can be another source of problems if you keep them.
If a portion of the activity was realized you must keep on record that portion, you delete only the un-realized portion if the un-realized portion is no longer valid.
After a Re-Baseline or an Update I would:
Baselines are meant to be kept frozen, you never add/delete activities from the record/contractual baselines, you create new baselines that can contain new activities and shall not include deleted activities.
Member for
19 years 10 monthsHi Tom Welcome to Plannung
Hi Tom
Welcome to Plannung Plant.
Change unwanted tasks into a zero duration milestone but keep the logic.
Make a note of why you have changed it.
And in future please only hit the Save button once.
Best regards
Mike Testro