Skip to main content
Planview Customer Success Center

How are project team entries used when calculating the allocation for task assignments?

Answer:

Due to the complex calculations when multiple tasks and multiple resource requests are involved, the current design would process resource requests as follows, in order to avoid a potential performance impact:

·         If two or more resource requests overlap, they are treated as one bucket

·         If they do not overlap then they are treated as distinct buckets

Since the two resource requests in question overlap, they are treated as one bucket. That means a total of 60hrs is treated as one single bucket that is available between Jan 1st and Mar 31st, and can be allocated to any month in Jan-Feb-Mar period. Therefore 49.59hrs in Jan is a valid allocation.

Had the two requests been "distinct", the system would not allocate more than 40 hours to Jan.

Example:

R and G below represent two resource requests, in a timeline where each character symbolizes a day. In this example, Case I and Case III have two “distinct” requests, while Case II has two overlapping requests therefore treated like one single request:

CASE (I) contiguous but not overlapping , treated as 2 distinct requests

RRRR,_,_,_,_

,_,_,_,_GGGG

 

CASE (II) overlapping, treated as 1 single request

RRRR,_,_,_,_

,_,_GGGGGG

 

CASE (III) with 1 day gap, treated as 2 distinct requests

 RRR,_,_,_,_,_

,_,_,_,_GGGG

 

Additional notes:

In order to avoid the complexities, it is suggested to have one resource request per resource, per project