Users availability multiplied by how many groups they are in

[JDavies549]

Hi all,

I'm still getting to grips with SPM, but am getting there slowly. I have created an availability report, which is designed to show a users' availability in given month, by person days. For someone who is only attached to one group, it works as expected. E.g. 20 working days available in Feb 2025 to dedicate to project work. However, for someone who works across multiple groups, it's multiplying their allocation. E.g. someone is attached to 3 groups and in Feb 2025 they have 60 available working days to be assigned to a project. Obviously, this is not feasible. Non project time is where I have allocated an operational plan to consume 20% of their time for admin/bau work etc, which is also being multiplied.

Ideally, I'd like to show a single view of someone's availability across all groups but not have them multiplied. I can separate reports by group, but that would then take a manual intervention to look at two or more reports and caluclate availability. Does anyone know a way around this or has encountered it before?

Thanks,

[PaulaaO · Accepted solution]

Hi - not sure if you're referring to the new resourcing functionality using Resource Assignments or the "old" one using Resource Plans. If it's the latter, then you should not have resources part of more than 1 group (with pps_resource role attached to it). This multiplication of availability is expected behaviour and I am not aware of a work around for it (perhaps someone else from the Community might).

Have you explored the possibility to use Resource Roles or Skills instead? For example a resource can be in the Project Manager group but associated with 2 resource roles: Jnr PM and Standard PM => this would allow correct resource aggregates values (capacity, availability) and enabling a resource to be part of more resource pools, so to speak 🙂

Hope this helps

[JDavies549]

Thank you PaulaaO for taking the time to respond. We are using the 'old' Resource Plans for this piece of work. It's a shame that ServiceNow is unable to register that a user is unique, despite being a member of a few groups. It also looks like it calculates working days correctly, but then it multiplies it as though having 60 working days in February is acceptable. A part of me feels like it should pick up on this, but maybe I think it's too simple! We'll have to try and find some workaround for it for the time being.

As for the resource roles and skills, this is not something we have really looked at. I'm not sure if we have this as part of our package? (I'm not involved with the management of the platform). However, thanks for mentioning it, as it may be something we'll need to move to in future 🙂