Tuesday, May 08, 2012 9:03 AM
Project Server 2010: could someone explain how exactly the timesheet planned and actuals work regarding administrative non-working time (our scenario is in auto-approval environment, so we don't care about timesheet approvals)? Based on our installation experience, the following facts occur:
1) When a user Saves (not Send) a timesheet with actuals on vacation (even on future timesheets), then these hours are considered non-working and as such they have the impact on changing the project plans and availabality
2) When the user submits planned time (not actual) in their timesheet, then the timesheet is greyed out for these days and our reports on timesheet actuals do not show the vacation hours (because they remained on "planned" category).
So, my question is: What is the difference between actual and planned hours in timesheet? Don't they overlap with each other? If the system lets us save actual time on future timesheet, then our resources do not need to edit the "planned" actuals for vacation/illness, is that correct?
Tuesday, May 08, 2012 4:07 PM
While technically, they may seem the same,The biggest difference in my opinion is from a data integrity stand point.
Just because somebody plans 5 days of vacation means that they use all the vacation. Logging time against Planned and then Actual provides a clearly differentiated way for tracking vacation hours etc., especially for organizations who use this data very diligently for their attendance system.
And overall, it does not make logical sense to have actuals reported in future, does it :)
Here is some more detail on this topic, if it might help:
Prasanna Adavi, PMP, MCTS http://thinkepm.blogspot.com
- Edited by Prasanna Adavi Tuesday, May 08, 2012 4:07 PM
Wednesday, May 09, 2012 8:18 AM
thanks for the reply.
In principal I won't disagree. However, the users find confusing the fact they are able to insert planned hours only to non-working categories on their timesheet. I won't blame them, because planned time as a concept is managed through Project Plans or Resource calendars. We've seen cases when a resource inputs their vacation on the "planned" field for an entire period/week and sends the timesheet for auto-approval. Since the resource availability is correctly updated with non-working days, no one notices that the actual hours for this user are zero; all seems good until the end of month when the corresponding report is extracted. Even worse, the total hours of this user's actual vacations do not include this week.
In my opinion, resource planning should be kept out of timesheets.
Wednesday, May 09, 2012 5:29 PMOwner
If you are not interested in resource planning in the timesheets spyrosnb then I would suggest unchecking the 'Planned' option in the ribbon so that only the actual line is available.
Wednesday, May 09, 2012 6:38 PM
I didn't mean that I don't want planning to be displayed in timesheet, I just don't agree with resource planning being done with timesheets. It is nice that the planned hours are there serving informative purposes, it's just misleading that in certain categories it can be edited also.
Saturday, May 26, 2012 4:00 PM