11.5 Hours of Overtime on Weekends

[akphidelt]

Hey guys, I'm relatively new to Projects. I looked on Google for the answer
but couldn't find anything.

I work in a remote location where the schedule is 7 days a week 11.5 hours a
day. 8 hours of ST, 3.5 hours of OT.

Also, no matter how many hours you worked in the week, weekends are counted
as overtime. So we get 11.5 hours of Overtime on Saturday and Sunday
regardless.

I worked the Calendars right in my Project, where 2 days = 23 hours in
Duration. But the Cost comes out to $1,380 which is just 11.5 * Straight Time
Rate

My St Time test is $60/hr and Ot is $80/hr

Any thoughts?
Thanks a lot in advance for any help.

 

[vanita]

Hi

In Calendar > Options, no. of working hours for each day should remain 8
hrs. So, 2 days should be 16 hrs. Overtime is not included in standard
calendar time. It is over and above that.

Overtime work is allocated through 'Resource Usage' view in the 'Overtime
work' column. Or through 'Overtime' row after formatting the view to show
this row through Format > Detail Styles.

I hope it helps.
Vanita

 

[reza]

akphidelt--
i think you should task usage view or resource usage view.
then in right column (with yellow color), right click -- details styles --
in availabe fields choose actual work & actual overtime work --- move to
right with click show button then click OK.
so, in this view you should fill your actual work and actual overtime work.

i hope this is what you mean and hope this will help you.

thanks

 

[Steve House [MVP]]

Overtime is defined as work peformed at times OTHER THAN what is defined as
normal working-times by the working time calendar. If your calendar says
that Sat and Sun are normal workdays and each day's normal working hours are
11.5 hours per day, then by definition no portion of the work done during
those days and hours is overtime. Duration is defined as the time between
start and finish in working-time calendar units - duration time only
includes straight time, never overtime. What are you trying to do here -
figure out the schedule and costs of the tasks or compute your actual
payroll? In the scenario you describe I'm not sure you can do both.

 

[akphidelt]

The problem is, in the oil industry, the 3.5 hours is not considered
"overtime". We start calculating our overtime after 11.5 hours of work in a
day. But the contract pays any day you work more then 8 hours, it's overtime
pay, any weekend you work it's overtime pay. So a resource has a 3 weeks of 7
days a week 11.5 hours a day of time. That's the standard calendar which we
don't consider overtime work.

Is there a possible work around... maybe created 2 resources for each
resource we have? Or maybe I can use some VBA to override the
actual/estimated costs?

 

[akphidelt]

Because oil prices are so low our client is squeezing us pretty tight to cut
cost and be as accurate as possible with our schedules/estimates.

So they want to see how much it cost/how long it will take to do a task.
Then they want it progressed accurately with actual work performed/actual
cost per resource.

I have our entire resource pool loaded in with accurate ST Rates and OT
Rates and their calendars set to show their 3 on 3 off or 2 on 3 off
schedules.

But with out being able to calculate our "overtime" hours in to it, the Cost
are significantly off in both estimates/actuals. We technically don't
consider those hours as overtime. Our overtime tracking starts arter 11.5
hours. It's just in the contract how people get paid their OT rates at
certain times.

Can you think of any work around or solution to solve this problem?

Overtime is defined as work peformed at times OTHER THAN what is defined as
normal working-times by the working time calendar. If your calendar says
that Sat and Sun are normal workdays and each day's normal working hours are
11.5 hours per day, then by definition no portion of the work done during
those days and hours is overtime. Duration is defined as the time between
start and finish in working-time calendar units - duration time only
includes straight time, never overtime. What are you trying to do here -
figure out the schedule and costs of the tasks or compute your actual
payroll? In the scenario you describe I'm not sure you can do both.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs

Hey guys, I'm relatively new to Projects. I looked on Google for the
answer
but couldn't find anything.

I work in a remote location where the schedule is 7 days a week 11.5 hours
a
day. 8 hours of ST, 3.5 hours of OT.

Also, no matter how many hours you worked in the week, weekends are
counted
as overtime. So we get 11.5 hours of Overtime on Saturday and Sunday
regardless.

I worked the Calendars right in my Project, where 2 days = 23 hours in
Duration. But the Cost comes out to $1,380 which is just 11.5 * Straight
Time
Rate

My St Time test is $60/hr and Ot is $80/hr

Any thoughts?
Thanks a lot in advance for any help.

 

[vanita]

Hi
As I understand your problem:
* for alloting work to a resource you use 11.5 hrs a day, 7 days a week as
the ST
* for calculating cost that is to be shown to the client, beyond 8 hrs a day
i.e extra 3.5 hrs per day and work on weekends is considered as overtime cost.
* but for internal accounting the above cost is calculated at standard cost.

You want all this to happen with MS Project and you want actual cost
accounting also to happen with above two methods.

I think there is a solution:
* Create a calendar with Standard 8 hrs working, 5 days a week
* In Cost Rate A which is the default rate, give the Standard and Overtime
rates as per the client's reqs.
* In Cost Rate B (through Resource information box), give the Standard and
Overtime rates same as the Standard rate. This is for your internal
accounting.
* When we assign resources, these are automatically assigned through Cost
Rate A.
* So, when you have to do costing as per the client's reqs. this is fine.
But when the costing is to be done as per internal accounting you may apply
cost rate B to those resources which are working on different rates.
* Or keep a copy of your schedule. In one file apply Cost Rate A and in
another Cost Rate B.

I hope your problem would be resolved.
Vanita

--
Project Management consultant and trainer
(e-mail address removed)

Because oil prices are so low our client is squeezing us pretty tight to cut
cost and be as accurate as possible with our schedules/estimates.

So they want to see how much it cost/how long it will take to do a task.
Then they want it progressed accurately with actual work performed/actual
cost per resource.

I have our entire resource pool loaded in with accurate ST Rates and OT
Rates and their calendars set to show their 3 on 3 off or 2 on 3 off
schedules.

But with out being able to calculate our "overtime" hours in to it, the Cost
are significantly off in both estimates/actuals. We technically don't
consider those hours as overtime. Our overtime tracking starts arter 11.5
hours. It's just in the contract how people get paid their OT rates at
certain times.

Can you think of any work around or solution to solve this problem?

Overtime is defined as work peformed at times OTHER THAN what is defined as
normal working-times by the working time calendar. If your calendar says
that Sat and Sun are normal workdays and each day's normal working hours are
11.5 hours per day, then by definition no portion of the work done during
those days and hours is overtime. Duration is defined as the time between
start and finish in working-time calendar units - duration time only
includes straight time, never overtime. What are you trying to do here -
figure out the schedule and costs of the tasks or compute your actual
payroll? In the scenario you describe I'm not sure you can do both.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs

Hey guys, I'm relatively new to Projects. I looked on Google for the
answer
but couldn't find anything.

I work in a remote location where the schedule is 7 days a week 11.5 hours
a
day. 8 hours of ST, 3.5 hours of OT.

Also, no matter how many hours you worked in the week, weekends are
counted
as overtime. So we get 11.5 hours of Overtime on Saturday and Sunday
regardless.

I worked the Calendars right in my Project, where 2 days = 23 hours in
Duration. But the Cost comes out to $1,380 which is just 11.5 * Straight
Time
Rate

My St Time test is $60/hr and Ot is $80/hr

Any thoughts?
Thanks a lot in advance for any help.

 

[akphidelt]

Vanita, thanks a lot for the help. However the problem still exists. It's not
going to be used for internal accounting. It's simply going to be used for
tracking Estimates which are based off bill rates per resource... and actual
cost which are based off the bill rates. The internal accounting stuff all
gets handled some where else at our main office.

I just can not see how Project can not handle construction/maintenance work
that is not based off a standard work week calendar. Is there any way to turn
every cost/duration calculation off and I can just do all the work through
our web application and then just import the new data?

This is what we want to accomplish
--An hours estimate is created by our estimators per task
--We set up the tasks/relationships based off the engineers drawings
--Based off resource calendars, the supers assign resources to each task
--This generates the estimate which is a very accurate estimate since the
estimate comes directly from the resources
--When the project starts we start plugging in a resources actual work
performed on a task to generate actual cost of the task

So the problem still is there, if I manual add ot hours it shortens up the
project. It doesn't read weekends as overtime, doesn't read the extra 3.5
hours of work in a day as overtime cost. So the estimate is always lower then
it should be, same with the actuals.

The previous Project Manager here told me the reason they use excel instead
of Project was because of the hour issue of which we work. I didn't believe
him but now I can see there problem. Except I'm 100 times more efficient on a
computer so I'm sure there is some kind of work around. Could we use VBA to
set up a routine that manual overrides the calculated cost?

Hi
As I understand your problem:
* for alloting work to a resource you use 11.5 hrs a day, 7 days a week as
the ST
* for calculating cost that is to be shown to the client, beyond 8 hrs a day
i.e extra 3.5 hrs per day and work on weekends is considered as overtime cost.
* but for internal accounting the above cost is calculated at standard cost.

You want all this to happen with MS Project and you want actual cost
accounting also to happen with above two methods.

I think there is a solution:
* Create a calendar with Standard 8 hrs working, 5 days a week
* In Cost Rate A which is the default rate, give the Standard and Overtime
rates as per the client's reqs.
* In Cost Rate B (through Resource information box), give the Standard and
Overtime rates same as the Standard rate. This is for your internal
accounting.
* When we assign resources, these are automatically assigned through Cost
Rate A.
* So, when you have to do costing as per the client's reqs. this is fine.
But when the costing is to be done as per internal accounting you may apply
cost rate B to those resources which are working on different rates.
* Or keep a copy of your schedule. In one file apply Cost Rate A and in
another Cost Rate B.

I hope your problem would be resolved.
Vanita

--
Project Management consultant and trainer
(e-mail address removed)

Because oil prices are so low our client is squeezing us pretty tight to cut
cost and be as accurate as possible with our schedules/estimates.

So they want to see how much it cost/how long it will take to do a task.
Then they want it progressed accurately with actual work performed/actual
cost per resource.

I have our entire resource pool loaded in with accurate ST Rates and OT
Rates and their calendars set to show their 3 on 3 off or 2 on 3 off
schedules.

But with out being able to calculate our "overtime" hours in to it, the Cost
are significantly off in both estimates/actuals. We technically don't
consider those hours as overtime. Our overtime tracking starts arter 11.5
hours. It's just in the contract how people get paid their OT rates at
certain times.

Can you think of any work around or solution to solve this problem?

Overtime is defined as work peformed at times OTHER THAN what is defined as
normal working-times by the working time calendar. If your calendar says
that Sat and Sun are normal workdays and each day's normal working hours are
11.5 hours per day, then by definition no portion of the work done during
those days and hours is overtime. Duration is defined as the time between
start and finish in working-time calendar units - duration time only
includes straight time, never overtime. What are you trying to do here -
figure out the schedule and costs of the tasks or compute your actual
payroll? In the scenario you describe I'm not sure you can do both.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs



Hey guys, I'm relatively new to Projects. I looked on Google for the
answer
but couldn't find anything.

I work in a remote location where the schedule is 7 days a week 11.5 hours
a
day. 8 hours of ST, 3.5 hours of OT.

Also, no matter how many hours you worked in the week, weekends are
counted
as overtime. So we get 11.5 hours of Overtime on Saturday and Sunday
regardless.

I worked the Calendars right in my Project, where 2 days = 23 hours in
Duration. But the Cost comes out to $1,380 which is just 11.5 * Straight
Time
Rate

My St Time test is $60/hr and Ot is $80/hr

Any thoughts?
Thanks a lot in advance for any help.

 

[Steve House [MVP]]

My view is that Project's cost figures are to help you estimate the internal
costs of doing the work and are not intended to be an actual cash accounting
of the project. It deals with estimates and averages, not balance sheets.
So if for example your standard workweek is 11.5 hours per day, 7 days a
week and you use that for your standard calendar so the times on the tasks
come out right. For simplicity of illustration lets say that the actual
straight time wage is $10 per hour and overtime is $15 per hour. If the
standard day consists of 8 hours at straight time and 3.5 hours of overtime,
the average pay for a worker over the course of a standard day is (8*$10) +
(3.5*$15) or $132.50 per day. $132.50 per day divided by 11.5 hours per day
equals a standard rate of $11.52 per hour. Hours over 11.5 per day are at
the overtime rate of $15 per hour.

Since you also have weekends to contend with you'd need to adjust further -
your standard calendar is 11.5 hours per day, 7 days per week, 5 days at a
mix of straight time and overtime and two days at pure overtime. So your
rate calculation becomes ((5*8*$10) + (5*3.5 * $15) + (2*11.5*$15)) divided
by (7*11.5 hours) or $12.41 per hour for the standard rate. This is the rate
you use for the standard rate in the resource's rate information. Remember
standard rate is applied to work done within the regular working time
calendar so using this average makes the costs come out right as long as the
management horizon is a week or longer.

Common practice is to use a burdened labour cost which includes salary,
benefits, hiring costs, overheads, training, facilities costs, etc. rather
than just wages. Also while you may have workers in category X earning
anywhere from $10 per hour for newbies up to $25 per hour for old hands,
often one would use a single standard rate of $15 per hour (or whatever) for
everyone in the category for staffing and budget planning purposes. To
repeat, the objective is to arrive an estimate of total internal costs of
doing the project versus not doing it, not an accounting of the actual
payroll expenditures and materials purchases.