Kelly O --
Administrative projects are not meant to reschedule work in other projects
when a resource submits nonworking time such as vacation. For example, I
submit 5 days of vacation to your administrative project for the week of
August 16-20. You approve and accept my nonworking time update into the
administrative project and save the project. You are assuming that any task
work scheduled for me during that week in any project will be delayed by one
week. I wish administrative projects worked that way, but they do not. If
you want my work to be rescheduled in all projects, then you must manually
enter my nonworking time on my personal calendar in the Enterprise Resource
Pool. If the automatic rescheduling of work around vacations is your reason
for using an Administrative project, then you should probably not be using
this feature.
People are struggling with the implementation of Administrative projects in
Project Server 2003, so you are certainly not the first. For what are
Administrative projects useful, therefore? Administrative projects allow
your organization to track the non-project and nonworking time. Non-project
time is regular work time spent on duties outside of project work, such as
training, help desk duties, database tuning, application support, etc.
Nonworking time is time spent away from work entirely, such as vacations,
sick leave, jury duty, etc. You can also use administrative projects to
determine the cost of all non-project and nonworking time in your
organization. Hope this helps.
Kelly O said:
We have been unable to successfully test the Admin Project feature in MS
EPMS 2003. Although the hours recorded against the project by resources are
posted correctly, the hours are not accounted for in other projects in
relation to the resources' overall availability.
