Discontinuous Bars

2 solutions

1. change the data date TIME to 8:00 am

2. go to bars and select the actual work bar and change the timescale to current Current bar

Hi there,

I wrote an article named How to remove the gap between actual bar and remaining bar in schedule update in Primavera P6.

I believe that it can solve your issue. Kindly refer to this link : https://doduykhuong.com/2020/01/29/how-to-remove-the-gap-between-actual-bar-and-remaining-bar-in-schedule-update-in-primavera-p6/

Regards,

Khuong.

Hi,

i tried all the solutions that you mentioned but unfortunately non of them work with me i do not know why!! ,i searched about all possible solutions but no use, so kindly please if any body has another solution can help me to solve this problem (discontinuous bars)...



thanks for all

HI,

You will get a discontinous bar, if you are using "Retained Logic" while scheduling your project and some of the activties do not follow the planned logic and work out of sequence. Try using "Progress override" and you will see that discountinuity will go away. For a more detailed description of what each of these options mean check the following link http://primaverablog.in/2011/07/scheduling-options-%E2%80%93-progressing-activities/ .

Regards

Amit Parmar

I hope this might solve your issue of discontinious bars 

1) Select view bars

2) Highlight the Actual Bar and change the Time Scale from Actual Bar to Current Bar

3) Select ok

4) Actual Bar now Stretches form the Actual Start to the "Remaining Early Start"

Now the Progress will be based on Remaining Duration.

Regards.

Hi Ferdinand,

I agree with them, however if you don't want to do what they have suggested which is actually true, then you can perform some tricks here. Try to create a new bar --> Timescale "Current", Filter "In Progress".

Best regards,

Arnold

Long answer:

This will happen for one of two reasons:

1) You have eg an activity with only a single FF predecessor, an actual start date, and the remaining duration is less than the difference between the data date and the early finish (which is constrained by the FF predecessor). The activity has started, it can't finish before a certain date and there isn't enough duration to cover the gap.

To fix this: Correct the relationships, remaining duration, data date or actual start date. Or if all these are correct, leave it alone.

2) You have OOS (Out of Sequence) working and are scheduling using the retained logic option. eg Activity B has a single FS(0) predecessor from Activity A. Activity B has an actual start and progress applied but Activity A has not yet finished (OOS working). The retained logic option says in this circumstance that the remaining duration of activity B should be delayed until after Activity A has finished, which will create a gap in the time bar.

To fix this: correct the relationships (this is good practise to do anyway). Or if you are lazy, just change your scheduling options from 'retained logic' to 'progress overide'.

Short answer:

Correct the relationships.

in my experience, the gap is caused by the following:

1. Timescale - I supposed P6 calculates in hours or in minutes; Try showing your timescale in Days.

2. Time period settings or working hours - if you're using 8 hours or 10 hours per day, then there's a big gap, as you know one day is 24 hours. Try to use 24 hours per day work period.

3. Out-of-sequence activities - quite difficult to explain...I leave this up to others

oh, by the way, don't forget weekends and holidays, these creates a very long gap

Ferdinand,

BTW, this can also happen in FS relationship, for example, activity A has a FS relationship with Ativity B. If activity B started before activity A then you will have the same situation.

Regards,

Daniel

Ferdinand,

The information given by Primavera Australia is true, check your links/relationship and check if the original logic is still true especially on SS and FF relationships (check lags). This happens when an activity is not yet supposed to start as originally anticipated or planned but has actually started early.

Cheers,

Daniel