Im trying to understand how the affectation rate works.

It works fine thank you 👿

Right now I leave it at 100%

IT is default, and works fine in many cases.

and doesn't seems to be logic.

all depends what you expect

To match the productivity with the affetaction rate I was wonder in what time frame is based.

It is based on a daily bases.
Once again RTFM : hit F1 on Activity page, move 2 pages up to get to page 3/5 of activity, whare assignment is explained.

I have activity type A that I can do 2 per week, and activity B I can do 4 per week.

2 what, 4 what.
Number of activities ?
If you have activity A, it means you'll work on this activity, not run several times activities of this kind...

Weekly basis affectation for type A is 50% and for type B is 25%

This means (to explain) thant you can work 0,5 days per day on A and 0,25 days per day on B (respectively 4 hours and 2 hours for 8 hours day).

Monthly basis (lets say 4 weeks) (8 activities) type A = 12.5% (1/8th) and (16 activities) type B = 6,25% (1/16th)
Or in yearly basis (52 weeks) type A = 0,96% (1/104th) and type B = 0,48% (1/208th)

You lost me there 🙁
I'm afraid you have a unit issue : projeqtor is Work driven PM tool, so you have to deal with "how many days (or hours) I'll work on this activity"

So in what time frame I'll need to measure productivity to be related with affectation rate?

In days (or hours dependeing of global parametering)

well, I see I have an issue with the concept itself :side:

with this I got it.

This means (to explain) thant you can work 0,5 days per day on A and 0,25 days per day on B (respectively 4 hours and 2 hours for 8 hours day).

I will measure it in hours and assign % based on weekly hours, that suits best for me. Has this affectation impact on the planning calculation?
and would make sense, add a resources to a project with none rate and set the rate on the subactivities where the resource is used?

Thanks a lot!!

Has this affectation impact on the planning calculation?

Of course, if is done for that.

and would make sense, add a resources to a project with none rate and set the rate on the subactivities where the resource is used?

No, you should not set project affectation rate to zero. This is an extra control on project : you cannot work more than rate% on a weekly basis. This mean that if you set a 50% affectation rate on a project, you cannot work more than 2,5 days (5 x 50%) per week on this project (on all the tasks of that project).

Ok, is sort of what i'm looking for. When I say set to none the affectation I mean leave it blank, not zero, and then set the affectation on each activity.

I'm getting lost on why or when I would set affectation on the subactivity or on the parent project or activity.

I'm interested on time control on subactivity level more than on the overall project. then would make more sense to set affectation on subactivities rather than on parent project?

You must define affectation to project :
- to give the resource access to elements of the project
- to be able to select resource in assignment definition
Affectation rate limits planning calculation on weekly basis
([Resource capacity] x [affectation rate] x 5 days per week on the project max)

You must define assignement to activity :
- to plan the work on the activity
- so that resource can enter real work on activity
Assignment rate limits planning calculation on daily basis
([Resource capacity] x [assignment rate] x 1 days per day on the activity max)

Ok now I get, I didn't realize there was a difference between affectation rate and assignment rate.
Thank you very much.
You are being very helpful and projeqtor too 😀