Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Planification probl...
 
Notifications
Clear all

Planification problem - Predecessor End to Start not respected

13 Posts
2 Users
0 Reactions
5,975 Views
 HEU
(@quantamedical)
Posts: 58
Active Member
Topic starter
 
[#6927]

Hi team projeqtor;

We need your help because we encountered a problem with planification.

On a project that use predecessor chaining rule, we have many task that are planified to start before predecessor ending.
All task concerned are test session plannified on planningMode : as Soon as possible (9)
there is only one predecessor by task (testsession)

Planning of both task

Detail of predecessor test session (with end date on red)

Detail on successor test session with contraint date

Database View of Planning Element

Do you have any ideas to explain this case, a solution so that this constraint is respected whatever the other constraints that apply

Thanks for your help


 
Posted : 17 Sep 2020 11H36
(@alain-fourastie)
Posts: 366
Active Member Moderator
 

Hi,

Have you replanned the project ?
if not, do it. Same behaviour ?


 
Posted : 18 Sep 2020 16H18
 HEU
(@quantamedical)
Posts: 58
Active Member
Topic starter
 

Of course, at least 20 time since problem was discovered

Planning is recalculated each day

Same behaviour

Thanks


 
Posted : 18 Sep 2020 16H43
(@alain-fourastie)
Posts: 366
Active Member Moderator
 

OK,

Gonna try to reproduce and find the solution !


 
Posted : 18 Sep 2020 16H46
 HEU
(@quantamedical)
Posts: 58
Active Member
Topic starter
 

No milestone linked to this task


 
Posted : 18 Sep 2020 17H26
(@alain-fourastie)
Posts: 366
Active Member Moderator
 

Is there some real work entered into the succesor ?
Is the sucessor is planified with a special mode as regular beetween to dates or planified intervention ?


 
Posted : 18 Sep 2020 17H27
 HEU
(@quantamedical)
Posts: 58
Active Member
Topic starter
 

You can show that on capture on first post


 
Posted : 18 Sep 2020 17H31
(@alain-fourastie)
Posts: 366
Active Member Moderator
 

i m only interested by pic of activity with id 3653 . thank you


 
Posted : 18 Sep 2020 17H52
 HEU
(@quantamedical)
Posts: 58
Active Member
Topic starter
 

 
Posted : 18 Sep 2020 17H55
(@alain-fourastie)
Posts: 366
Active Member Moderator
 

Ok thanks, still investigating.
Project or activity is not fixed. No real work, no special mode of planification, recalculation ok, no error with milestone, it is weird, trying to find the key.


 
Posted : 18 Sep 2020 18H10
(@alain-fourastie)
Posts: 366
Active Member Moderator
 

the resource is she still allocuted to this project.? i think so ! But please check her FTE ( If=0 behaviours are blocked)


 
Posted : 18 Sep 2020 18H32
 HEU
(@quantamedical)
Posts: 58
Active Member
Topic starter
 

On task 3014, ressource is Faly

NB : Project QUANTA VIEW 5.400 is a sub project of PROJECT "PROJET"

On task 3653, ressource is Hery
NB : this task have no problem ..

NB : Project QUANTA VIEW 5.400 is a sub project of PROJECT "PROJET"


 
Posted : 21 Sep 2020 11H56
 HEU
(@quantamedical)
Posts: 58
Active Member
Topic starter
 

I found origin of problem :
there is an E-E predecessor dependency on parent (Task 3014 have parent "Developpement" 3639)
3639 have predecessor End to End with task already ended "Validation du cahier des charges" (3643) and "Création environnements développement & validation" (3855)
In principle, the development task (3639) cannot be completed until the 2 predecessor tasks are completed.

but there seems to be an interpretation problem which causes the start date to be the end date of the E-E task and the E-S constraint of the 2567 task is not taken into account
When i delete both E-E predecessor of developpement (3639) , start date of 3014 taken account of 2567 E-S constraint


 
Posted : 23 Sep 2020 11H34
Share:

Scroll to Top