Timescale

P

Piper5150

I believe it would be of great use to many users if we had the option to set
the timescale to 1/2 months. That is a common pay period and period of
performance
for many industries.

Thanks

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...ba27-1c0baf0a6bf7&dg=microsoft.public.project
 
J

John

Piper5150 said:
I believe it would be of great use to many users if we had the option to set
the timescale to 1/2 months. That is a common pay period and period of
performance
for many industries.

Thanks

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/community/en-us/default.mspx?mid=3a866ea9-3c97
-4af0-ba27-1c0baf0a6bf7&dg=microsoft.public.project

Piper5150,
So what exactly would a half month be? How about those months with 31
days or February during a leap year?

I think what you really want is bi-weekly (i.e. every other week) as
that is a "common pay period for many industries".

John
Project MVP
 
S

Steve House [Project MVP]

In addition to John's comments, Project is a work scheduling application,
NOT an accounting nor time and billing nor payroll application. I'm going
to schedule tasks based on when I need the work done and the length of the
task will be based on the work required, not the payroll periods. In that
sense, the company's pay periods are irrelevant to managing the Project
since from the PM perspective, all you're concerned aobut is when the
company accrues the obligation to pay for some work and how much it's going
to cost - you could care less when the accounting department has to cut the
cheque. Even more so, in many projects some fo the work cost is paid to
hourly workers getting paid every week, other may be every two weeks, other
work may be to salaried workers getting paid on a monthly basis, other work
to casual day workers paid daily, and yet others to contractors getting paid
on completion of the work an acceptance of the dleiverable. So what then?
 
J

JackD

John said:
Piper5150,
So what exactly would a half month be? How about those months with 31
days or February during a leap year?

I think what you really want is bi-weekly (i.e. every other week) as
that is a "common pay period for many industries".

John
Project MVP

John,

It is also "common" to be paid twice a month. Typically the first and the
fifteenth. I can't recall any job I've had when I wasn't paid either monthly
or that way.

But to not be completely disagreeable, Project is not a pay tracking tool.
Maybe it is good that it is difficult to do this!

-Jack
 
P

Piper5150

Oh believe me I don't care about payroll and shit like that. All I know is
that my bosses live in a world where they want all the MS stuff to do
whatever they want. Unfortunately our contracts, hours worked, and then
about 2 or 3 degrees from that accounting comes into it. But my managers
won't accept no for an answer sometimes. Just needed some ammo to go back at
them and say, "See, you are crazy people!"

I know what Project is designed for. I've been using it for 7 years. Just
the bosses don't know what it's for! :)

Cheers
 
D

Dean C

Steve,
If Microsoft shared your view of Project as simply a scheduling tool it
would make Project lose market share. Project is a project Management tool,
not simply a schedule tool. I've been fighting with our Earned Value
Management community about the fact that you cannot identify accounting
period start and end dates in Project. To me, the easy solution is to look at
weeks, then do reports that show which fiscal months those weeks belong to.
For any Government contracting, the schedule tool must be integrated with the
financial system, which is normally a monthly system. That means that when
you load resources in Project, Project needs to know which fiscal month
resource costs should be rolled up to.
 
J

John

Dean C said:
Steve,
If Microsoft shared your view of Project as simply a scheduling tool it
would make Project lose market share. Project is a project Management tool,
not simply a schedule tool. I've been fighting with our Earned Value
Management community about the fact that you cannot identify accounting
period start and end dates in Project. To me, the easy solution is to look at
weeks, then do reports that show which fiscal months those weeks belong to.
For any Government contracting, the schedule tool must be integrated with the
financial system, which is normally a monthly system. That means that when
you load resources in Project, Project needs to know which fiscal month
resource costs should be rolled up to.

Dean,
You are right about the accounting month limitation. However, we
overcame this years ago by using VBA to re-structure standard calendar
month data into accounting month data (generally based on 4-4-5) with an
export to Excel. Granted, this approach is not necessarily convenient
but the tools are available (i.e a part of Project) and have been for
many years. Based on my years of association with Project and this
newsgroup my conclusion is that the Project developers have not added
the overhead necessary for accounting month performance because the
customer base (very few users need that functionality) does not warrant
it.

As far as integrating Project data with the financial system, there are
(and have been) other applications that interface the data (e.g. IPM by
Microframe)

John
Project MVP
 
R

Radioactivedad

Steve House said:
In addition to John's comments, Project is a work scheduling application,
NOT an accounting nor time and billing nor payroll application. I'm going
to schedule tasks based on when I need the work done and the length of the
task will be based on the work required, not the payroll periods. In that
sense, the company's pay periods are irrelevant to managing the Project
since from the PM perspective, all you're concerned aobut is when the
company accrues the obligation to pay for some work and how much it's going
to cost - you could care less when the accounting department has to cut the
cheque. Even more so, in many projects some fo the work cost is paid to
hourly workers getting paid every week, other may be every two weeks, other
work may be to salaried workers getting paid on a monthly basis, other work
to casual day workers paid daily, and yet others to contractors getting paid
on completion of the work an acceptance of the dleiverable. So what then?

I think that Steve's assessment of the intended use of Project is
ridiculously narrow; but unfortunately Microsoft seems to agree with him. If
Project proports to do Earned Value Management (which it does) it has to be
flexible as to the ACWP status dates, which obviously is determined by a
companies fiscal calender. It includes the Status Date project field to
accomodate EVM; but it provides no convenient way to reorient the Timescale
to view all data along these bondaries (e.g. the typical 13 period fiscal
calender). This is programming laziness. Obviously we want to view our data
in the same date increments that actual costs are accrued and reported by our
finance departments. For example, it is only natural to want to see time
phased BCWS and BCWP, aligned to the same dates as ACWP will be recorded; but
no, microsoft has concluded that this is not useful, in complete ignorance of
how real project managers work.

To let microsoft off the hook by saying that VBA or other techniques can
provide this fundamental behavior is unacceptable. I use tools because they
make my life easier, not to be forced into becoming a co-developer to make
the thing useful. Project Scheduler 8 by Scitor allows this and virtually
every other real-world data view I have ever wanted, FROM THE MENUS, without
having to customize every view or learn a programming language. The
government is pushing me towards Project, but after experiencing some of
these silly oversights in this product, I will be pushing back like crazy to
continue using Scitor PS8.

-Scott
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top