Skip to main content
Planview Customer Success Center

Looking for best practices with using the RMV and entering Planned Hours (2010)

QUESTION
Looking for best practices with using the Resource Management View and entering Planned Hours.
We are having a lot of struggles with using the RMV and entering planned hours in a certain situation. We are looking for some best practices or a better understanding of why it works this way. Our resource managers plan once a month at the end of the month. Here is the situation:

I create a task and assign it to Bob. It runs June 1 - August 31 for 90 hours. So Changepoint loads it as 30 hours per month on the RMV. June = 30, July = 30, August = 30.
Now Bob in June only works 10 Actual Hours on the task and the 20 hours he did not get to has to be put into September. So when the resource manager plans at the end of June they see: July 30, August 30. They now use the RMV and add 20 hours to September, so it shows July 30, August 30, September 20.

And here is the problem. Adding that 20 to September now changes the total planned hours of the task from 90 to 110. But the task in reality is only still 90 as the 20 from June weren't used. So the PM has to go in after the resource manager and adjust the task back to 90. This has become very time consuming and problematic.


ANSWER
The way the planned hours work depends on the allocation (loading) method chosen by the system administrator.
The RMV doesn’t replace past planned hours with actuals. If they want that to happen, they could add fiscal periods to the project and select an allocation method that replaces past planned information with actuals (0, 1 or 2). They would have to launch the RMV after the fiscal period ends and the project is rolled up. That’s when the planned hours in the past are updated.