Microsoft Project Allocation at the summary level

B

Bart Stevens

I am developing a very basic "Road map" of initatives for budgetary
discussions for the coming year, and we are interested in determining
possible scheduling scenarios with these 26 intitatives (read:
projects). My problem is as follows:

1.) There are 26 projects in the road map
2.) Each project has three phases
3.) Each phase may call on up to a dozen teams (which I have
structured as single resources with max units corresponding to number
of individuals) for varying degrees of work. Projects never have equal
amounts of work across phases.
4.) Phases within a project need to remain together- with no slack/lag
in between. For instance, a project with three phases of a month
always needs to stay at three months duration:

Budget 2005
-> Project 1
-> Phase 1
-> Phase 2
-> Phase 3
-> Project 2
....

Our goal is to level resources at the project level, which is a
summary of the three phases. However, when I use the level resources
wizard, and an overallocation occurs at the phase level, it levels at
the phase level. Therefore, a project that must have a duration of,
say, 80 days, blows out to 120 days after resource leveling. Lag
between phases is 40 days in this case

In the case that phase resource requirements in separate projects
cause overallocation, I would like the entire project to move (delay),
but stay at the same duration. I need lag to be 0 days between all
phases, and project durations to stay at, say, 80 days.

Ex: If Project 1 and Project 2 are scheduled to start on 1/1/05, with
three phases of one month in each (for a project total of 90 days),
and there is an overallocation in the SECOND phase of each, I need
Project 2 to start on 2/1/05- instead of still starting on 1/1/05,
with a one month lag/gap between phase 1 and 2 or Project 2. Is this
possible?
 
R

Rod Gill

Hi,

Try experimenting with setting Priority on tasks and projects. In the
Resource Levelling window select the levelling order priority,standard and
see what happens

Basically high priority tasks get scheduled ahead of lower priority tasks.

--
For VBA posts, please use the public.project.developer group.
For any version of Project use public.project
For any version of Project Server use public. project.server

Rod Gill
Project MVP
For Microsoft Project companion projects, best practices and Project VBA
development services
visit www.projectlearning.com/
 

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