Overtime

[TVDave]

I hope this is simple:

How can I make overtime hours for a day with no regular hours. I must have
a Tech travel on Sunday, thus the Tech is paid OT rate for those hours. But
the Task Usage page will not let me set Work or Regulars hours to zero and
set Overtime Hours to 8.

TV Dave

 

[JulieD]

Hi Dave

would a solution be to use another cost rate table as each resource can have
up to 5 different rate tables where they are paid differently for a task.

So if you had a travel on sunday task, you could set up cost rate table b
for the resource (double click on resource, go into cost tab) and then in
the task usage / resource usage view, double click on the the task and set
the rate table (bottom right of screen) to B

Cheers
JulieD

 

[TVDave]

Julie:

It does not fix the basic problem, the overtime hours in my POAM do not
match the OT hours in my bid to the customer. I bid on a task to provide on
site support, 10 hours a day for 3 weeks. (Actually there are several
subtasks with similar task requirments.) Thus my tech time for the POAM
should be 210 hours for that sub task, with 120 hours ST and 90 hours OT. I
can make the totals work out, but the daily ST/OT is out whack. The customer
wants to see it with Sat and Sun = 10 hours OT and weekdays are 8+2.
Weekdays are no problem, but weekends will not let me have all hours are OT.
I am sure there is some calender or resource definition that will allow me to
put in whatever hours I want on each day. I am just tired of Project doing
automatic stuff and not letting me present this task as it will actually be
worked.

TV Dave

 

[JulieD]

Hi Dave

i had another read of your post and realised that what you're trying to do
is to set WORK on the task to 0 and OT to the appropriate number of hours -
and my understanding is that the WORK field and the OT field don't interact
like that ... according to page 387 of my "Using Project 2000 Special
Edition" pub by QUE:

"If you assing overtime work, the total work to be done on the assignment
remains the same, but the amount of work that is scheduled during regular
working-time hours is reduced by the amount of the overtime"

-- which means the value in the Work column remains at say, 210 hours but
the OT column shows 90. If you like one option would be to create a
"Regular Time" column with a formula that works out the difference between
Work and OT.

.... what interests me is that you say that the weekdays are no problem - you
can show 8 in the work column/row and 2 in the overtime column/row ... this
might be what is being displayed but Project then is only calculating 6
hours at the standard cost and 2 hours at the ot cost not 8 and 2.

Cheers
julieD

 

[Steve House [MVP]]

Try this solution:

FYI the Work field is a total equal to the sum of regular work and OT work.
If you see 8 hours work and 2 hours OT in the usage view, that means 8 hours
total *including* the 2 hours of OT, ie, *6* hours Standard Work and 2 hours
OT.

1. Task X, 5days, Starts Monday
2. Travel, 1day, Task Calendar 24 hours, "Task Calendar overrides Resource
Calendar" set on
3. Task Y, 5 days

Link all tasks FS. Assign Fred to all. Split screen and re-format bottom
window to Resource Work. Shows 8 hours total work on Travel task. Enter 8
hours in the OT column (task turns into a milestone with zero duration -
that's because OT doesn't count for duration so 8 hours work with all of
them in OT means the duration is zero). Total Work remains at 8 hours.
Remove Split. Switch to Resource Usage View. Be sure to get both! OT Work
is "planned OT." "Actual OT Work" is just that. Right click the right hand
side and add the rows for Overtime Work and Actual Overtime Work to the
view. Travel will show scheduled for 8 hours Work, 8 hours OT Work on
Friday night. For actuals, enter 8 hours in the Actual Overtime Work row
for the day travel actually occured. You'll see 8 hours in all 4 fields -
Work, Actual Work, OT Work, Actual OT Work. Task will revert from a
milestone diamond back to a normal task bar on the date(s) travel took place
after entering the actuals.