Donna, the only way I have seen the monthly, quarterly and yearly numbers
were accurately created was to work with our development team who build a
lookup table of hours per month, per quarter and per year, and the FTE calc
is built around looking up the number of hours in a month quarter, or year,
then create the following 3 measures...FTE required month, FTE required qtr,
FTE required Annual. I also calculate same for Capacity FTE per month, per
qtr, per year.
Then depending upon the time value being displayed, I will use the
appropriate FTE value to display over the appropriate time dimension...it
required some custom code, that extends the OLAP cube, but that little look
up table on hours per month...made it all work. wish it was much easier,
but each time I have asked a microsoft person, I get a bit of blank stares of
not understanding why one would want to display OLAP cube data in FTE format.
Some users do not want to accept an estimated fte, but prefer an exact
number, with precision that matched their own manual calcluations. I think
this is a powerful feature that could significantly enhance interpretation of
OLAP data and acceptability of OLAP data. Hope this helps? I needed a
developer to work with me to make it work.... one downside I found if you
get more than 600 projects in project server, and extend the OLAP cube build
logic... cube build time will begin to grow because of all the lookups.
worked ok, for PS project count size under 600. Great opportunities here.
TomB
