Wanted to see how others might be managing this scenario: If a project manager removes demand hours from a position, how is the resource manager supposed to know that he needs to reduce committed hours accordingly?
so you have a postion where you requested 24h and the resource manager allocated a resource to this position with the requested demand. Thus, no unmet demand. PM then goes into the position and says 'naaaah, I only need 12h for this position' and you remove 12h. Thus, now position shows overallocation ... (12) in red. Right?
I don't think that there's any direct notification about the change. I can only see it in Resource Pool -> Resource Load Breakdown -> Assignment Details, then open the Staffing Profile and there I see it.
Yes, that's what's happenning. The problem isn't so much that there isn't any notification, it's that there is no way (portlet, etc) that a resource manager can find out if these situations exist other than looking at each line in each staffing profile.
Assignment Details will tell you if a resource is over-allocated to his capacity, but a resource can be under capacity and still over-booked (allocation > demand)...no way to know that.
Maybe it's ER time, but it seems like this would be a regular occurance with anyone using resource management.
I do have a case open...4644836201...but I'm not sure they're understanding what I'm asking. The other part is that I would swear that these showed in the resource requests portlet before. Do you (or anyone else) have an instance that is 9.14.0003 or earlier? If so, do lines show in the portlet that have a negative total unmet demand?
(This is the second time I've wanted to verify if some feature I *thought* I remembered was regressed. Typically, PROD is the last environment I upgrade but now I'll be hanging on to another "prior version" one for testing...lesson learned...)
Dirk...exactly, except I don't think you really need the project.
Create staffing profile
Add a position for 100 hrs; send resource request
Add OOTB "Resource Request Portlet"; filter on that staffing profile; you should see the request
Allocate Resource to fulfill demand
Go back to position and change 100 hrs to 50 hrs; this makes (50) unmet demand
Look at the portlet again...does the line show up?
We skipped from 9.14.0003 to 9.14.0005 and I'm pretty sure we were seeing these in pl3's resource request portlet (OOTB one).
After you remove some of the demand, the status will still be "Fulfilled" but the total demand should be negative.
Thanks for your time!
[Side note...if the position was originally Soft Booked, instead of Committed, then when the PM backs off the forecast he gets the Send Resource Requests button active so at least he can generate an email to the resource manager. But if the position was Committed, this option doesn't become available.]
Test on 9.14.0002 shows what you've updated in the case but not here (tststs), that the portlet shows zero und negative unmet demand on that version, but in 9.14.0005 it shows only positive unmet demand.
I didn't find any optional changes in the preferences that would remedy that.
Check document for visualization.
I see that you haven't updated the ticket with PPM-Support since May 22 (tststsv2) either :-)
I have checked the knowledge-base and didn't find anything that would point to a change in behaviour but then I didn't go through the hotfixes relnotes to check.
Since you have a 9x5 SLA and I'm not in your region I will not update the case.
You can use my document to update Randall and point him to me for any open ends but basically he should open up an incident with RnD to reguest the information on where the 'Resource Request List' portlet was changed in the hotfix sets and why now no longer zero or negative unmet demand for STaffing Profile requests is shown any longer.
Thanks again for looking at this. If I read you right, the problem is caused by that fix in pl5? I updated my support case...that issue refers to the portlet showing rows with 0 Unmet Demand. I'd like to suggest that the fix should be to only filter out 0 Unmet Demand rows, and not also negative Unmet Demand rows. As a resource manager, negative unmet demand means I need to adjust allocation just as much as positive unmet demand does.