Big problem : planning not working as expected - not able to plan tasks

Sure !

Here it is (not much work assigned due to the problem I face )

Availability of resources


Monthly planning Resource/project/activity:

Yes,

You will find here all affectations for Jean-Yves (and yes, he has a lot of work but not yet implemented correctly in Projeqtor )

First, which line correspond to project with WBS 166.1 ?

It's affectation ID 141

Second : are you sure all these are projects ?
You may quickly face performance issues and great difficulty to manage project if you define project for waht could be a task...

Well, I have to synchronize with an ERP where all these projects were existing... I think in the future we will try to limit the number of projects, but :

• We have defined subprojects in projects for several reasons :
• Some subprojects do not follow the same type as others (I don't think this is manageable at activity level
• In most subprojects there are already quite a lot of activities. People affected in each subproject are not the same as on others. Maybe there could be a better mean to manage this.

A little bit more precision about the way I have understood projeqtor (once more, I may be wrong !).

Avoid to define projects for only few-days tasks.

Currently there are no projects defined for only few days. Projects are created for :

• Customer project, whatever the time it takes (from 1 week (rare !) to 2 years)
• Internal and administrative tasks, which can be repetitive. For example, the "Reunions internes" project is a constant opened project to place all internal meetings not linked directly to an other project.

For these types of project (ex. Reunions Internes), I assign people at 0% rate, and they can enter the real work in real work allocation. I don't see how to do better.

You may quickly face performance issues and great difficulty to manage project if you define project for waht could be a task...

I tried this morning to define a project with tasks as phases instead of subprojects, but I'm facing a problem :
Resources are working on multiple projects. Most of the time, there are some days or some weeks on a project, at 50% or 100% rate on this project, then work on another project, and back to the original project. This is due to time to get prototypes or time to get other teams work finished or time to get customer's validation.
To assign a resource on a task the resource must be affected in the corresponding project. But it can be quite easy to slice affectation on specific subprojects, but it is quite hard to do it on main project (we have to maintain <100% global project affectation for each resource). What is the best way to do then ?