What is Dangling Activities

Why it matters?

The dangle activity is a type of open-ended activities which may have both predecessor and successor, but none governs these connections, making them more complicated than their counterparts. 

When a schedule has logical ties missing., it can’t be guaranteed that the planned start or finish dates will accurately derived logically in P6.  When an activity has no predecessor, it can be either forced to start on particular dates or left entirely unrestrained. The downside to using constraints is that instead of a logical tie, one or more constraints have been added which prevent the schedule from being flexible due its use. When you leave a scheduled activity fully unrestrained, it continues to move freely every time there’s a change in schedule.

Another downside to it is that the Schedule will not be a reliable tool to show the time impact of delays because it has an incomplete/faulty logic.

Activities with Dangling Start

– They may or may not have predecessor.

– Without predecessor, tasks are open-ended & not preferred in P6 schedule.

– Only exception allowed is a Project Start Milestone.

– They don’t have governing predecessor logic, e.g. FS or SS.  

Activities with Dangling Finish

– They may or may not have successor.

– Without successor, tasks are open-ended & not preferred in P6 schedule.

– Only exception allowed is a Project Finish Milestone.

– They don’t have governing successor logic, e.g. FS or FF.  

Different Scenarios

Scenario 1

  1. In Scenario 1, Task B has a dangling Start Date.
  2. Task B do not have a Predecessor and the Start Date of Task B is dangling [not driven by any governing logic]. 

Scenario 2

  1. In Scenario 2, Task B has a dangling Finish Date.
  2. Task B do not have a Successor and the Finish Date of Task B is dangling [not driven by any governing logic].

Scenario 3

  1. In Scenario 3, Task B has a dangling Start Date.
  2. Task B do not have a Predecessor and the Start Date of Task B is dangling [not driven by any governing logic].

Scenario 4

  1. In Scenario 4, Task B has a dangling Finish Date.
  2. Task B do not have a Successor and the Finish Date of Task B is dangling [do not drive successor, Task C].

Fix Dangling Tasks in P6 using Power BI

Why it matters?

The dangle activity is a type of open-ended activities which has both predecessor and successor, but none governs these connections, making them more complicated than their counterparts. 

When a schedule has logical ties missing., it can’t be guaranteed that the planned start or finish dates will accurately derived logically in P6.  When an activity has no predecessor, it can be either forced to start on particular dates or left entirely unrestrained. The downside to using constraints is that instead of a logical tie, one or more constraints have been added which prevent the schedule from being flexible due its use. When you leave a scheduled activity fully unrestrained, it continues to move freely every time there’s a change in schedule.

Another downside to it is that the Schedule will not be a reliable tool to show the time impact of delays because it has an incomplete/faulty logic.

Share This:

Blogs

© Project Insights. All Rights Reserved.