Remaining work unreliable

T

Tony

We are currently experiencing weird and unpredictable changes in
remaining work and task duration in several projects in our Project
Server database. It appears to be happening when synchronizing actuals
to protected actuals (the system is set up for managed time periods).
For example remaining work on an assignment changes from 75 to 45.5
hours after syncing, while no actuals on the affected task were out of
sync in the first place.

Does anyone:

1) experience similar behaviour
2) have an explanation
3) have a solution

Let's solve this people.... ;-)
 
G

Gary L. Chefetz [MVP]

Tony:

One would need the entire sequence of events executed as well as specific
characteristics of the tasks in question to even begin to answer your
question. Are you using fixed duration tasks that are marked as effort
driven? This will certainly appear to cause strange behaviors when it comes
to calculating work values in Project.
 
T

Tony

We are using fixed duration tasks, but with the effort driven checkbox
disabled. The thing I don't understand is that "sync to protected
actuals" seems to affect remaing work; I was under the impression that
it should only adjust actual work. Another strange thing is that the
units % goes sky high (as in 6600%) for the particular problem
assignment. Other charateristics of the problem tasks: they are split
and all have multiple resource assignments. Any help would be much
apprceciated.....
 
Top