It's the definition of "true cost of the project" where you and I
disagree.
IMHO, and I'm not an accountant, the "true cost" only includes the costs
directly attributable to specific project work and nothing else. If you
have an employee in the firm who earns $5000 per month and you use him 10
hours on this specific project during a given month with the rest of his
time being spent elswhere, should all $5000 be charged against the
project's
budget or should only the 10 hours be charged to the project and the rest
to
general operating expense? I say the latter. If only the portion of an
internal employee's time spent on specific project work impacts the
project's budget, why should contractors and equipment be treated any
differently? The same goes for equipment purchases - unless they are
destroyed by doing the project work, they go on the shelf for use in
other
projects after the current is done. Thus their cost to the project is
not
their purchase price but rather the depeciation they acrue while they are
being used, again just for the hours that they are actually utilized - in
a
sense they are 'employees' being paid a 'salary' equal to their
depreciation.
On the other side, there are some costs that are frequently omitted from
the
project budget that I think should be included in it. Most of the MS
Project courseware books say that while non-exempt employee's overtime
rates
are the statutory rate, exempt professional and managerial employees
overtime rates are zero. I disagree - the fact that a manager doesn't
get
paid extra for overtime doesn't mean his work outside of the normal
calendar
has no value. If nothing else, there is an opportunity cost associated
with
the work that properly should be charged against the project budget. An
hour of an exempt employee's time between 7 and 8 pm is worth to the
company
exactly the same as an hour of his time between 2 and 3 pm and should
impact
the prject budget by the same amount. Thus I teach my students that for
exempt employees the overtime rate should not be left zero but rather
should
be set equal to the standard rate.
All of this emphasizes my view that MS Project is NOT a cash accounting
system and it's cost estimating features do not deal in any way or form
with
revenues and expenditures.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit
http://project.mvps.org/faqs.htm for the FAQs
in
message news:B7EA400AEE60433A962193E272D8AECC@RLWM90...
Jan,
While the approach taken by Andrew lets you do the math, Steve's
categorization makes more sense since there is an availability
constraint. The problem I have with Steve's approach is laying-off the
cost to some overhead account which doesn't reflect the true cost of
the
project.
An alternative approach would be to use Steve's categorization but
assign a $800/d cost to the resource and assign it to a specific
sub-task in whatever quantity you need.
=====
Richard Warren [MBA, PMP, MCITP for EPM]
http://richardlwarren.info
-----Original Message-----
From: (e-mail address removed) [mailto:
[email protected]]
Posted At: Saturday, August 02, 2008 11:01 AM
Posted To: microsoft.public.project
Conversation: material costs
Subject: material costs
Hi,
I am having a problem with the resource type "Material"
I am hiring cranes and they cost 800 Euro/day/piece. No matter how
long they are working..
On certaine days I hire more than one and costs should be x times
800..
The std rate can't be defined per day.
cost per use doesn't seem to work either because only one crane is
calculated
I tried to define them as resource type "work"
They disadvantage then is that they add up in the total work hours..
Who knows???
Thanks in advance
Jan