Strange values in admin project

[M.R.H.]

Hi all,

I would like to ask for help with administrative projects. We're using
admin projects to track vacations etc. for about 100 employees. During this
usage we find some strange values in non-working time inserted by users
trough PWA. Our administrative project is generating random values (f.e.
hundredths of hours, 8 hours for many weeks every day) to some users. Problem
is, that they didn't insert this values trough PWA. Do you know reason for
this, please?

Thank you, M.R.H.

 

[Mike]

Administrative projects must not be used for planning (e.g. holiday
planning). They should only collect time.
An easy test is to display the remaining work column. If it has any
values then you are "planning", and the plan will misbehave,

Regards

Mike

 

[M.R.H.]

Hello Mike,

is this information somewere defined by MS? This is attribute of admin
projects, or I don't understand to this, why we can't use it for planning -
in this case are admin projects unavailing, or not? We need to see, if the
given source is available, or not in future, not in past.

Truly, I do not understand to this?

Thank you for cooperation. MRH

Mike píše:

 

[Mike]

Mike

Administrative plans have special characteristics and do not behave in
the same way as regular plans. Their purpose is to capture unplanned
time e.g. sickness, meetings, whatever categories you define. When you
assign a resources to these tasks, the work value is zero, however it
is published to their timesheet so that they can book time. This is
posted back to the plan owner who follows the normal update process. If
you start to interfere with the settings in the admin plan you will
have problems. If you wish to plan support or planned absence
(training, holidays, etc) you must create a normal plan (and not an
administrative plan).

Hope this helps

Regards

Mike

 

[M.R.H.]

Hello, Mike,

Great, this is information, I needed - our people did this mistake, so it
is great, that I can foreclose this issue in future.

BTW, one more question - what about recommendation for not changing time of
end of task (category) in admin projects
(http://office.microsoft.com/en-us/assistance/HA011038751033.aspx). We tried
to fix task in time (e.g. limit category for year), but it was unsuccessfull,
because category was enlarginf its end automaticly. Did we made a mistake in
this? MS also recommends to not changing also linking, duration etc. - can
you please explain me why?

Thank you a lot, Mike, you are helping me very much. MRH



Mike píše:

 

[Mike]

Mike

Not totally clear on your question,however following might help

Admin plans should be time limited certainly no more than a year.
By default each admin task you create has a duration of one day.
There is no reason why you cannot change this duration to say 250 days
(i.e. a year)

The benefit from doing this is that when you update the plan it avoids
message which advise you that assignment is outside task dates which
gets a little irritating

Tasks in an admin plan should not have constraints applied,by default
they start at the project start date, in reality they start when the
first time is booked. Because these tasks are fixed duration this
typically means they may finish later than intended (because they
started later) If this is an issue, simply change the duration.

Logic links are not relevant. In general do not change any of the
options in an Admin plan.

regards

Mike

 

[Mike Glen]

Hi Mike,

As has been said many times... In future, try posting on the server
newsgroup as this one is closing down. Please see FAQ Item: 24. Project
Newsgroups. FAQs, companion products and other useful Project information
can be seen at this web address:http://project.mvps.org/faqs.htm .

Mike Glen
Project MVP

 

[M.R.H.]

Ok, I understand, thank you a lot for help.

Mike píše: