New rates for 2016 - P6 recalcuating prior actuals

Hi All,

we've updated our rates per resource ID by adding the new rates with an effective date of 1st Jan 2016.

For activities that are not yet complete the prior actuals, which have been stored in period performance, are being recalculated at an average rate that has been calculated from the start date vs data date and a balance held in 'in period actuals'.

E.g:

Activity 1 - 10 hours booked at £50 per hour in Dec 2015

Data date 30th Jan 2016

New rate £60 per hour

Actuals calculated as 10 hours at £55 per hour even though all bookings were at £50 per hour.

 

Is there any way around this?

All we're after is all old actuals to be as per the stored period values and not be recalculated.

 

Many thanks!

R
Rafael Davila 👤 Member for 22 years 3 months

For activities that are not yet complete the prior actuals, which have been stored in period performance, are being recalculated at an average rate that has been calculated from the start date vs data date and a balance held in 'in period actuals'.

This can make EV calculations unreliable, especially if:

  1. at low WBS level,
  2. worst if at Activity level,
  3. worst if spanning more than two prior periods.

If there is no failsafe fix, if Hammer's Rule [1] is unreliable then I would look for other ways to report EV and variances.

If I were the client I would question in detail every penny of any adjustment figure, and if this happens frequently I would question your capacity to use the software.

[1] Hammer's Rule: If it does not fit, hit it with a hammer until it fits.

Z
Zoltan Palffy 👤 Member for 16 years 10 months

at what point meaning at what date did you change the rate form L 50 to L 60 ?

it would not use 50 L if the effective date was 1 Jan 2016 and the data date was 31 Jan 2016. IF the effective date was less than the data date and you already performed a store period performance it cant change that cost beased on new rate because the actual are base don the 50 L rate you cant go back in time.

store period performance stores the actual costs generated FROM the rates.

the effective date for the rate will the date the rate starts and is for the whole duration of the activiity

M
Marc Timberlake 👤 Member for 11 years 2 months

Hi Dieter,

 

apologies, I had meant to reply a lot sooner. Thank you for your reply and looking for a possible way to switch off. Much appreciated!

We're having to add an adjustment figure prior to monthly reporting updates now which gets around the issue as we can match to our ERP system actuals but is messy. What we're also finding is that 'store period performance' is saving at the averaged rate as opposed to the current rate.

 

Marc

D
Dieter Wambach 👤 Member for 19 years 4 months

Hi Marc

As far as I know this is by design: Effective Date does mean effective from that date. I don't know a setting to switch off this feature in a way to keep prices for the whole duration of an activity. Even if you'll use a global change, the next "calculate costs from units" will overwrite this again.

I checked the pm.ini for such a setting but couldn't find any.

Regards

Dieter

Forum Sponsor

Top Posters

Josephus Enot
1 posts
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts