Hello team.
Once again I very much want to receive your dear help.
I have a work resource that has been allocated a task with 5% (11 mins) of its availability, in a 220 mins task. (...this task also has other work resources).
In the task usage view, in the control table, this resource is updated with the actual work of 5 mins. It is from this moment that the calculations of real start and real end give me incorrect data. I would like to know why is this happening?
Thanks for the screen shot, it gave me what I needed to analyze your scenario. One interesting observation, not related to your questions but curious nonetheless, is that the projector was assigned at 50% yet you entered 240 minutes of work. That should result in a Peak value of 109% but your screen shot shows 100%. When I emulated your task the projector shows a 109% Peak value. I don't know why yours is different.
With respect to your question, the reason you get the schedule alert is because you have set the task as fixed duration. If the task type is fixed work or fixed units, you will not get the message. However, by entering the actual work value in the timescale data you are fixing (confining) the 5 minutes of actual work to that day (Monday). The total work for that resource is 11 minutes on Monday. To resolve the mismatch for Monday, Project adjusts the original 11 minutes on Monday to the actual 5 minutes on Monday but Project needs to do something with the remaining 6 minutes so it alerts you that the 6 minutes will need to move to the next day, thus the conflict with the fixed duration of the task.
You can avoid this problem by entering the 5 minutes into the Actual Work field on the left side of the screen. That still leaves 6 minutes of remaining work for that resource but you have not "committed" the 5 minutes of actual work to Monday only so the fixed duration can still be valid and no alert will be issued.
So what to do with the 6 minutes remaining work for that resource? If the resource is all done, set remaining work to zero and Project will adjust the work value to be the actual work value of 5 minutes. If the resource is not done, then you need to decide if the resource will perform the remaining 6 minutes of work on Monday or will it indeed flow into the next day.
Something to wrap your head around.
John
Thank you so much for the explanation John. It helped a lot.
But I would like to know how it turned out in your case "Real Start and Real End of the Dr. Amadeu Resource with the hours displayed. In my case it was like this,
(The resource has 5 minutes as real work, but in the spreadsheet it shows 100 minutes) .... Is this normal?
You're welcome and thanks for the feedback.
May I assume that by "real start" and "real end" you mean the Actual Start and Actual Finish fields. Is that true?
Unfortunately, once again your screen shot doesn't show enough information to answer your question. Let me see a screen shot that shows the Task Usage view with all these fields and the timescale data.
John
I took a quick look at your plan and I see a problem that needs to be addressed. There are dependencies on summary lines and that is bad practice. Refer to the following Wiki article:
With respect to your question about why the highlighted resources show a period of performance which is greater than their actual work (e.g. Dr Amadeu Lemos period of performance is 9:00 AM to 10:40 AM which is 100 minutes, but his actual work is only 5 minutes), I cannot tell unless I know EXACTLY how his actual work was entered. For example, into which field did you enter the actual work? Did you manually enter an actual finish date?
This is the screen shot showing how the actual work data was "logged" by Project into the timescaled data (what you call the "spreadsheet"). But I can't tell how that data was logged without a step-by-step accounting of his work and progress from initial assignment to assignment completion.
John