Is there a field like WORK that I can use to roll up automatically

已答复 Is there a field like WORK that I can use to roll up automatically

  • Freitag, 8. Oktober 2010 00:01
     
     

    Hello

    Here is the question....

    We want to place the hours of each report somewhere so they roll up and we don't think we can use the field WORK since we assigned the hours it will take to do the reports as an aggregate with each resource.

    Here is why..............

    We want to have a list of Reports in the schedule and when the specs are completed (From another separate project) we will assign that report to a specific report resource. We do NOT want to try and pre-assign specific reports as there are to many and we will NOT know ahead of time which ones will come over. The hours it takes to do each specific report varies.

    We figured out how many resources it would take to do the work and than created a resource bucket task so we could tell how long it will take to do the work. When a report is assigned we will simply deduct the hours of that report from the resource bucket task and link the report task (Ex. report 1 to the bucket task). We were NOT going to allow them to report time to the bucket task ... only to the specific report when it was assigned. the average hours of each bucket task per resource is around 650 hours.  ....way more than the 80 hours per task should be from a best practice perspective

    We can baseline so we will know if we are getting behind if the buket task moves beyond the Baseline finish date of the bucket task.

    We need to also monitor the list of reports that we linked all together to make sure we can complete them all when we said we would. Right now we have no hours in the WORK field as we didn't want to double count hours (we have the report hours in the bucket task per resource).

    Thanks 

Alle Antworten

  • Freitag, 8. Oktober 2010 04:12
    Moderator
     
     Beantwortet
    If you are deducting the work from the bucket task and assigning it to the resource task, then it should be no problem using the Work field. I don't see how that would double count.
    Jack Dahlgren blogs at:
    Project and Retrovention
    and rarely Twitter
  • Freitag, 8. Oktober 2010 11:54
     
     

    We wanted a way to know what the total hours of ALL those individual Reports were at any point in time without including those hours in the grand total of work that was required to be accomplished. So we were thinking about using another field to track those hours just to give us a running total of what we had left.

    We were thinking of than moving the assigned report out of that summary and linking it to the Resource that is being assigned that report and that subtracting it from the resource bucket task.

    Maybe there is a better way to do this.

  • Freitag, 8. Oktober 2010 14:57
    Moderator
     
     

    We wanted a way to know what the total hours of ALL those individual Reports were at any point in time without including those hours in the grand total of work that was required to be accomplished. So we were thinking about using another field to track those hours just to give us a running total of what we had left.

    We were thinking of than moving the assigned report out of that summary and linking it to the Resource that is being assigned that report and that subtracting it from the resource bucket task.

    Maybe there is a better way to do this.


    Project gives you three fields to track work; Work, Actual Work, Remaining Work (and another 11 work fields in the baseline)

    Update tasks with actual work and then you can simply look at remaining work to see what is left.

    You can also code the tasks using a custom field so that you can group the work together (ie: tag all the reports and group by that tag) and you will get a summary of work for reports vs bucket as well as work, actual work and remaining work.

    There are probably a half dozen better ways to do what you want which are built-in to project.


    Jack Dahlgren blogs at:
    Project and Retrovention
    and rarely Twitter
  • Freitag, 8. Oktober 2010 15:58
     
     

    Yes, thanks for describing the above as we are also aware of these as well.

    It looks like I am not being clear in what I am describing for sure.

    Just trying to have all of the Reports and their hours in the schedule as well as in a sense re-distributing those hours in bucket tasks per resource since we can NOT pre-assign the work AND not double counting the hours in the grand total of hours. So....I have 30,000 hours of reports and I know what reports will be coming to me by number (ex. 1-1,000). I have even listed those in the schedules with 0 hours in the WORK field and the specific hours in the Baseline10 field. I also listed the resources in the plan and gave them hours in the WORK field in a bucket task to accomplish the work. Resource 1 may have 500 hours in that bucket task. I can't count the 500 hours of Resource 1 PLUS 500 hours of reports as that will be double counting if I go and include it in the schedule that way.........placing all the values in WORK. I would end up with 60,000 hours with everything in the WORK field.

    Bucket task       Predecessors =(1ss)  500 hours in work   Resource 1  Baseline = 500 hours  

    Summary level Reports = 3000  under that summary level is Reports1 through 1000 at anywhere from 10-200 hours each = 3000 hours. Right now we have 0 in WORK and each report hours in Baseline10 Work 

    Scenario 1...........

    We assign Resource 1  Report 1 of 50 hours and link that to the bucket task because we want to show what he is actually working on...

    We move ID 10 Report1 to where Resource 1 is and link it to Bucket list. We also move 50 hours to WORK field and we want to deduct this from the Baseline10 Total so we know how much WORK is left. This may be overkill since we have the 30,000 hours if we added up all teh assigned bucket hours in BASELINE.

    ID 10 Report 1     predecessor = (1ss) 50 hours of work   Resource 1  Baseline = 50 hours  actual work=50  remaining work=0

    Deduct 50 from the bucket list because if we don't nothing will ever get deducted

    Bucket task       Predecessor = 10  Work=450hrs    Resource 1    Baseline =450 hours  remaining work = 450 hours

    Scenario 2......

    We move ID 10 Report1 to where Resource 1 is and link it to Bucket list. We also move 50 hours to WORK field and we want to deduct this from the Baseline10 Total so we know how much WORK is left. This may be overkill since we have the 30,000 hours if we added up all teh assigned bucket hours in BASELINE.

    ID 10 Report 1     predecessor = (1ss) 0 hours of work   Resource 1  Baseline = 0 hours  actual work=0  remaining work=0 (We treat as a milestone with the 50 hours in Baseline10)

    Let Resource 1 post his time to teh Bucket task

    Bucket task       Predecessor = 10  Work=500hrs    Resource 1    Baseline =500 hours  remaining work = 450 hours actuals =50

    Scenario 3 .... ?

    I all the scenarios we wnated to keep a running total of what was left where we listed all the reports in teh schedule before they are assigned.

    Anyway, I at least hope this is clearer

    Thanks

  • Samstag, 9. Oktober 2010 12:02
     
     
    Any other suggestions on this? What would Scenario 3 be?
  • Samstag, 9. Oktober 2010 12:41
     
     

    Actually, Never mind....and Thanks

    Jack's group by suggestion is perfect