I would like to ask whether there are any detail description on the planning calculation logic in addition to the user manual on the "PROJECT PLANNING CALCULATION" ?
I noticed that for some tasks, the planning calculation planned the task to dates and work assignment which differ from the defined validated dates, planning mode, and resource allocation rate. In addition, for some tasks, even with the planning calculation option - "Plan with overuse (infinite overbooking capacity)" selected, the calculation did not plan overuse or skipped allocation on certain days (which the resource still has capacity for allocation) which cannot meet the validated dates with planning mode - "Regular between dates".
I would like to ask whether there are any detail description on the planning calculation logic in addition to the user manual on the "PROJECT PLANNING CALCULATION" ?
No, user manual doies not enter into such detail.
But during our training courses, we explore this subjet.
Thanks for your reply. Good to know that training courses would be helpful.
Just want to check if the cases mentioned in previous post are normal or there are bugs/setting issues in the calculation. I tried to repeat a case mentioned and attached the screenshots for your reference. The task validated start date is 2021/5/7 and end date is 2021/5/20 with planning mode as soon as possible. In the assigned resources, a few have work allocated on 2021/5/21 instead, while they have capacity on 2021/5/7 such that the work can be distributed within 2021/5/7 and 2021/5/20. In the plan calculation, the planning calculation option - "Plan with overuse (infinite overbooking capacity)" is selected. Is there any issue in the calculation or settings required?
Yes, this mays be accurate.
The "Plan with overuse (infinite overbooking capacity)" will have effect only between project.
This means the resource will be planned on several project for its full capacity.
But inside same project, capacity of resource is respected, otherwise, every activity "as soon as possible" will be done in one single day
So the calculation may be correct if the ressource is busy on another activity on same project.
Many thanks for your explanation on the calculation. I think the situation you mentioned does explain for some of the cases, while for the case mentioned in previous post, for resource D and F, all the tasks assigned to them are shown in the screenshot. For resource D, all the task shown in the screenshot belongs to the same project. For resource F, except the first row, other tasks shown in the screenshot are the same project as resource D. If accordingly to your explanation, day May 7 should be able to plan workload = 1 day such that the workload would be allocated through till May20 instead of May 21, right? Please advise there is any misunderstanding. Thanks!
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Cookies settings
×
Functional Cookies
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Please login to see yours activities!
Other cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.