Re: changing timeline to account for different types of accounting months?
From: Rob Schneider (rmschne_at_removetheones_b1e1e1b.net.net)
Date: 02/09/04
- Next message: Chris B.: "Earned Value for specified Periods?"
- Previous message: Rob Schneider: "Re: MS Project 2003 Demo"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: changing timeline to account for different types of accounting months?"
- Next in thread: John: "Re: changing timeline to account for different types of accounting months?"
- Reply: John: "Re: changing timeline to account for different types of accounting months?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 09 Feb 2004 23:26:41 +0000
John's approach, unless I'm missing something, is to dump the data into
Excel for analysis ... and not move uncompleted work inside of Project
into psuedo-February dates. It's not really a matter of keeping it
simple in Project so much as to keep the work scheduled/planned on the
dates it actually scheduled/planned. I guess if there are no knock on
affects by changing dates, and taht everyone knows that the dates are
"wrong" ... well, then it would work. It's the movement of data in
Project for accounting purposes I'm having a conceptual problem with ...
Hope this is useful to you. Let us know.
rms
anonymous@discussions.microsoft.com wrote:
> We have to move any uncompleted work for that week into
> February in MS Project so our EV model can pick up that
> week's remaining work for ETCs.
>
> I agree to keep it simple in MS Project but we have to
> figure out a work around for the accounting issue. The
> other posting answer was our "plan B" and we will most
> likely go with that. Thanks for your input!
>
> L Kelly
>
>
>>-----Original Message-----
>>First, Project is not really an accounting program. That
>
> being said, I'm
>
>>not sure why you can't you keep the dates in Project as
>
> is? Any work
>
>>scheduled for week of Jan 26 is indeed on those dates.
>
> You know it.
>
>>It's fact. It's just, by definition "February". Don't
>
> move the work
>
>>into February in Project even though it's going to be
>
> done on the part
>
>>of "February" you call January 26. I think you need to
>
> keep the
>
>>accounting aspects, and computations about accounting
>
> aspects of project
>
>>data, outside of Project. Leave Project aligned with the
>
> real calendar.
>
>>After all, on Friday January 23rd I wouldn't think that
>
> folks talk about
>
>>their planned work on Monday January 25th as "next
>
> month". They think of
>
>>it probably first as "after the weekend", or "next
>
> Monday", or "on the
>
>>25th". Project plans are for people. Keep it simple for
>
> them.
>
>>Am I missing something? Is there an absolute requirement
>
> to add this
>
>>complexity into Project?
>>
>>Hope this is useful to you. Let us know.
>>
>>rms
>>
>>
>>
>>
>>L Kelly wrote:
>>
>>>Question regarding MS Project Timeline:
>>>
>>>My company recently changed to an accounting system
>
> where
>
>>>each month ends on the 4th Sunday of each month as
>
> opposed
>
>>>to the last friday of the month. As far as I know, MS
>>>Project only deals with actual calendar months.
>>>
>>>Example - schedule is baselined as normal (so Jan 31 is
>>>the end of the calendar month in Project). January 2004
>>>accounting-wise really ends on Jan 25, 2004. So the
>
> week
>
>>>of Jan 26-30 is really in the accounting month of
>>>February. So any work not completed by Jan 25 has to be
>>>moved to start after Jan 31. This causes a week
>
> schedule
>
>>>slip compared to the baseline which finishes Jan 31. We
>>>have had to go back and readjust the baseline spread to
>>>move this week of baseline into February to avoid
>
> charging
>
>>>the program an unfair week's slip of the schedule for
>
> any
>
>>>of those tasks. We now have to do this every month
>
> where
>
>>>the 4th Sunday of the month is not the end of the month
>
> or
>
>>>when it's the end of the quarter.
>>>
>>>We were afraid this is the only way to fix this when
>>>establishing the baseline but does anyone know a way to
>>>change MS Project calendar to match an accounting
>
> calendar
>
>>>(that's different from the real calendar) like this
>>>without having to set the task dates in the next month?
>>>Back to my example - I don't want the tasks for Jan 26-
>
> 30
>
>>>to have to be set in actual month of February when I
>>>baseline because that doesn't help the project team
>
> manage
>
>>>their schedule correctly. They will be doing the work
>
> the
>
>>>week of Jan 26-30 and schedule dependencies need to be
>
> set
>
>>>correctly based on the actual dates.
>>>
>>>Any insight would be most helpful! THANKS!
>>
>>.
>>
- Next message: Chris B.: "Earned Value for specified Periods?"
- Previous message: Rob Schneider: "Re: MS Project 2003 Demo"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: changing timeline to account for different types of accounting months?"
- Next in thread: John: "Re: changing timeline to account for different types of accounting months?"
- Reply: John: "Re: changing timeline to account for different types of accounting months?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|