Hello Patrick, thank you very much for these series. I have one question regarding the use of SS and FF to relationship between two activities. What's the logic behind using these both relationships at same time?
The purpose is that it allows both activities to happen concurrently without creating what's called a "loose end". If an activity's only successor relationship type is a SS, there is nothing tying in the finish date to the network. Therefore, technically the finish date of the activity could be delayed indefinitely and it would not affect the overall completion date. So it's good scheduling practice to have both the start date and the finish date of an activity tied back into the schedule network.
Hello Patrick, thank you very much for these series. I have one question regarding the use of SS and FF to relationship between two activities. What's the logic behind using these both relationships at same time?
The purpose is that it allows both activities to happen concurrently without creating what's called a "loose end". If an activity's only successor relationship type is a SS, there is nothing tying in the finish date to the network. Therefore, technically the finish date of the activity could be delayed indefinitely and it would not affect the overall completion date. So it's good scheduling practice to have both the start date and the finish date of an activity tied back into the schedule network.
Hey Pat, can you run through the schedule 6e? I'm trying to figure out how to filter/sort by dates. Thanks!
Hey Mark - Thanks for reaching out. Here you go: ua-cam.com/video/FbIJfX7hSR0/v-deo.html