P
PJH
We're using Server in an enterprise-project environment, where projects are
several years long and "tasks" are usually 3-30 months long (fixed-duration,
non-effort driven). Our work resources are actually groups of people,
crossing many projects. This leads to a couple of problems:
-The sheer volume of data in the system (tens of millions of
assignment-days) causes some performance problems
-The calendar precision (i.e. work days) is actually more distracting than
useful -- resource availability varies by month due to differing work days
per month, for example. (For us the natural increment of planning time is a
month.)
One thought: What if we set up the resource calendars to only have one work
day per month? This would greatly reduce the volume of data in the system,
make the resource availability the same for each month, and keep the planned
work per month the same when shifting a task forward or backward.
The obvious concern is that a goofy resource calendar like this would
interfere with project scheduling. But the potential benefits are
significant...
Any thoughts/experiences/wisdom from anyone who's tried or contemplated this?
several years long and "tasks" are usually 3-30 months long (fixed-duration,
non-effort driven). Our work resources are actually groups of people,
crossing many projects. This leads to a couple of problems:
-The sheer volume of data in the system (tens of millions of
assignment-days) causes some performance problems
-The calendar precision (i.e. work days) is actually more distracting than
useful -- resource availability varies by month due to differing work days
per month, for example. (For us the natural increment of planning time is a
month.)
One thought: What if we set up the resource calendars to only have one work
day per month? This would greatly reduce the volume of data in the system,
make the resource availability the same for each month, and keep the planned
work per month the same when shifting a task forward or backward.
The obvious concern is that a goofy resource calendar like this would
interfere with project scheduling. But the potential benefits are
significant...
Any thoughts/experiences/wisdom from anyone who's tried or contemplated this?