Hi
While trying to find a solution to my topic "9528-planning-calculation", I realize that I got a problem with resource affectation.
Have a look to affectation :
As you can see, there is a "hole" on the bottom of screenshot (between 01/08/2018 and 30/04/2019)
Almost all projects are cut in 2 parts (before 01/08/2018 and after 30/04/2019) except "P052_L001 - 1 - Lot unique" and "P047 - Bilans Normalisés - LOT 3 - Univers & Rapports BO"
I checked all start date and end date in each affectation, I see nothing wrong.
Can you explain me why I got this behaviour ?
Regards
Hi,
Yes, the "hole" is stange.
Ticket #3664 recorded for analysis.
First remarks :
- these allocations are very complex, are they really needed to be so complex (several allocations to project...)
- you don't need to allocate resource to "Absence" if it is an "administrative" project
Hi
Happy to see that you consider the "hole" as strange behaviour.
Some answers to your question :
these allocations are very complex, are they really needed to be so complex (several allocations to project...)
As you know, there are many steps during software lifecycle. For example, a project manager will work more during build steps and less during run step. In fact, if I could (If I had enough time to do it), allocations would be more complex because during build step a project manager will work more during specification and test steps and less during development step. That's why you can see several allocations to project. It's the way I found to be near reality.
you don't need to allocate resource to "Absence" if it is an "administrative" project
If I don't allocate resource to "Absence", I won't be able to plan holidays (In France, you have to take rest to respect the law :cheer:). In a year, there are 365 days minus 104 days for week end minus 7 days for public holidays. It lets 254 days for working days. In my company, a resource can take until 42 days for vacation by year (25 days for holidays and 17 days for RTT). 42 days divided by 254 days is near 16% of working days ... If I don't "lock" this vacation time with allocation to "administrative project", I could believe that a resource is available more than 100% by year. Later, I will divide year with 2 periods : June to October (In France, Act imposes that a resource takes 20 days for holidays during this period else you have to give until 2 days more for the fractionning of vacation ... Dura Lex Sed Lex) and November to May for the remaining part. But I will wait that you solve my "hole" problem 😉
Regards
As you know, there are many steps during software lifecycle. For example, a project manager will work more during build steps and less during run step. In fact, if I could (If I had enough time to do it), allocations would be more complex because during build step a project manager will work more during specification and test steps and less during development step. That's why you can see several allocations to project. It's the way I found to be near reality.
I would be interested in seeing your planning.
You should not need to define effort of resource for each period.
It is very hard to change when projets "slides" to later dates.
When planning is correctly defined with tasks for each period, and correct planning mode, repartition of work will be automatic.
Hi
Here is a sample :
As you can see there are many steps.
- Between August 2018 and April 2019, the project manager should work around 40% of his time on this project
- Between May 2019 and August 2019, the project manager should work around 25% of his time
- Between September 2019 and December 2019, the project manager should work around 35% of his time
- Between January 2020 and December 2020, the project manager should work around 5% of his time
I don't know how projeqtor could calculate a correct repartition of work if I don't set affectation with availability.
Setting availability help me to see if a resource is affected more than 100% of his time (which means that I had to work to find another resource to do the job ...)
Regards
Yes.
But I thing you missunderstand how to plan a projets.
No tool will required to define allocation rate per periods.
You just have to change "assignment rate", on each activity.
So Allocation to project can be 100%, and you play only on allocation rate for each activity.
This will be much more fluent : allocation period will auto extend if activity is extended.
And last (but not least), as you did, your allocation rates will have absolutely no effect as you did not define assigned work on activities...
Please read user manual about planning rules 😉
Yes.
But I thing you missunderstand how to plan a projets.
In projeqtor, it's true.
You just have to change "assignment rate", on each activity.
You said before that my allocations were complex. It won't be better if I do the job for each task...
And last (but not least), as you did, your allocation rates will have absolutely no effect as you did not define assigned work on activities...
I know that, it was just à light sample on your demo database.
Please remind my topic "9528-planning-calculation", when assigned work is set, Projeqtor is unable to calculate the planning...
Please read user manual about planning rules 😉
I read it but rules are not clear 🙁 or I did not find the good pages...
Regards
You said before that my allocations were complex. It won't be better if I do the job for each task...
No, it will be much more easy with assignments to activities.
And it will be dynamic : just extend duration of activity will take into account changes for availability; you won't have to update allocation to project
I know that, it was just à light sample on your demo database.
Please remind my topic "9528-planning-calculation", when assigned work is set, Projeqtor is unable to calculate the planning...
I think you mostly use planning mode "don't start before validated start date". But this mode will always plan "as soon as possible" after start date.
Possible you need "fix duration" planning mode (and then have dependency if you want to start after given date) or "regular between dates"
ProjeQtOr is not a tool to "draw" a planning, but to calculate the best planning (shortest duration) depending on contraints cyou define.
Hi
ProjeQtOr is not a tool to "draw" a planning
I know that and it's why I use it 😉
If I use only assignments to activities instead of affectations to project, I loose view on resource availability.
It is very interesting to know if a ressource is "used" more than 100% on a period.
I tried to use both affectations and assignments but Projeqtor "failed" to plan activities.
Anyway, thank you for time you spent to answer my questions.
Soon, I will have a training to Projeqtor planification. It'll be easier.
Regards

