Timesheet Cubes and Time Collection PS2007

[Mike Mahoney]

PS 2007 generate 3 cubes to do with timesheet analysis.
TIMESHEET
EPM_TIMESHEET
MSP_PROJECT_TIMESHEET

TIMESHEET contains all the basic timesheet data, period, resource name
and project. It does not contain any additional project or resource
attributes.

EPM_TIMESHEET develops TIMESHEET (a little). It has the same basic
structure but it modifies the task list details. As a consequence all
Admin category time is removed as well as any time booked at Project
top-level (as opposed to specific task). I have also noticed instance
of specific tasks "losing" time booking in this cube. So this cube
does NOT contain a complete analysis of timesheets

MSP_PROJECT_TIMESHEET is a virtual cube which combines EPM_TIMESHEET
with RESOURCE and ASSIGNMENT Timephased cubes. Thie allows you to
slice and dice timesheet data by project and resource custom fields
and also to compare actual timesheet time with MSP actuals and
planned, EXCEPT for the missing (top level) DATA!.
Time may be booked at the top level for convenience or because a team
member does not have specific assignments or because you implement
Activity plans to collect specific support/admin effort.

So can anyone from Microsoft tell me if the EPM_TIMESHEET cube is by
design or contains a bug?

Regards

Mike

 

[Bill Busby]

Be VERY careful about allowing resources to charge time to the top level of
any project. This time cannot be imported into task assignments and will not
be reflected in the project plan.

The only way to prevent this would be to develop and event handler to
prevent adding a top level reference to a project on the timesheet.

 

[Mike Mahoney]

Be VERY careful about allowing resources to charge time to the top level of
any project. This time cannot be imported into task assignments and will not
be reflected in the project plan.

The only way to prevent this would be to develop and event handler to
prevent adding a top level reference to a project on the timesheet.

--
William Busby
Project Management









- Show quoted text -

Bill

Isn't this one of the reasons time collection was separated from
progress capture.

Aside from this you cannot prevent a team member from doing this on
his timesheet

Mike

 

[Gary L. Chefetz [MVP]]

Mike:

I don't know if anyone has an answer to this, but consider the consequences
of having it there. How would you dimension it? I think an operable
assumption is that if you plan at a different level of granularity than at
which you collect time, that you are not going to try to use time to drive
your schedules. Once you begin the exercise of connecting high-level time
data to projects, you embark on a fairly subjective exercise where you have
to make some arbitrary decisions about handling it. So, it seems that this
is a good place for custom reports or cube extensions.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com