S
Scott Robertson
Hi,
I have posted some parts of this query before in project server
newsgroups I would appreciate any input you may have!
Our setup
We currently have approximately 12 projects, including 2 administrative
projects to capture time against overhead activities, linked to a
shared resource pool of 50 people. Each of these 50 people records
their time daily against these projects through project web access.
Our requirements
We need to be able to reliably generate the following reports:
1. The hours actually worked per person per project (or per task) per
week.
2. The planned work remaining per person per project.
3. A comparison of actual work vs planned work per task
Our problems
The biggest problem is that we have been unable to reliably report
actual work to date via the timesheet view. Although superficially the
view appears to be correct, when we validate the data it is "patchy"
with actual effort missing for some people for some activities. (We
have confirmed that these actual submissions have been accepted by the
relevant project manager).
We have identified that hours appearing as actual work for an
individual on one report may not appear in the subsequent report. For
example, one individual appears to have done 25 hours on Project X
during week commencing 9th January; however the next time we generate
this report there is no time reported for that individual for that
project in that week.
When staff try to view their historical inputs through the timesheet
view the data is not displaying correctly.
Where we have subsequently tried to report similar data via the OLAP
cube, our observations remain the same - i.e. the hours reported are
unreliable, and frequently missing large blocks of work.
Finally, we also appear to have identified situations in which actual
work recorded on a specific day on a specific task either appears
against a different task on that day, or against a different day.
Clearly in this situation we cannot rely on any of the work reporting.
Steps taken to date
1. We have conducted a series of controlled tests, entering data from 2
individuals into a test plan, and assessing the reporting - this has
demonstrated the inconsistencies mentionned above.
2. We have generated a series of SQL queries against the database to
extract the data and compared the outputs against the OLAP and PWA
views - again this highlights inconsistencies.
SQL includes looking at:
Timephased actual work protected
MSP_WEB_WORK
Microsoft Office Project 2003 SDK - Timephased Data
Key questions
1. Are there any remaining known issues regarding work capture and
reporting following the release of Service Pack 2a?
2. Is anyone else out there using Server to meet these requirements? Is
it working effectively for you?
3. Has anyone else encoutered this problem - what are the likely
causes?
Scott
I have posted some parts of this query before in project server
newsgroups I would appreciate any input you may have!
Our setup
We currently have approximately 12 projects, including 2 administrative
projects to capture time against overhead activities, linked to a
shared resource pool of 50 people. Each of these 50 people records
their time daily against these projects through project web access.
Our requirements
We need to be able to reliably generate the following reports:
1. The hours actually worked per person per project (or per task) per
week.
2. The planned work remaining per person per project.
3. A comparison of actual work vs planned work per task
Our problems
The biggest problem is that we have been unable to reliably report
actual work to date via the timesheet view. Although superficially the
view appears to be correct, when we validate the data it is "patchy"
with actual effort missing for some people for some activities. (We
have confirmed that these actual submissions have been accepted by the
relevant project manager).
We have identified that hours appearing as actual work for an
individual on one report may not appear in the subsequent report. For
example, one individual appears to have done 25 hours on Project X
during week commencing 9th January; however the next time we generate
this report there is no time reported for that individual for that
project in that week.
When staff try to view their historical inputs through the timesheet
view the data is not displaying correctly.
Where we have subsequently tried to report similar data via the OLAP
cube, our observations remain the same - i.e. the hours reported are
unreliable, and frequently missing large blocks of work.
Finally, we also appear to have identified situations in which actual
work recorded on a specific day on a specific task either appears
against a different task on that day, or against a different day.
Clearly in this situation we cannot rely on any of the work reporting.
Steps taken to date
1. We have conducted a series of controlled tests, entering data from 2
individuals into a test plan, and assessing the reporting - this has
demonstrated the inconsistencies mentionned above.
2. We have generated a series of SQL queries against the database to
extract the data and compared the outputs against the OLAP and PWA
views - again this highlights inconsistencies.
SQL includes looking at:
Timephased actual work protected
MSP_WEB_WORK
Microsoft Office Project 2003 SDK - Timephased Data
Key questions
1. Are there any remaining known issues regarding work capture and
reporting following the release of Service Pack 2a?
2. Is anyone else out there using Server to meet these requirements? Is
it working effectively for you?
3. Has anyone else encoutered this problem - what are the likely
causes?
Scott