I suspect your present strategy is eventually going to paint you into a
corner. You might be able to get it to work but I'm skeptical. Summary
tasks and subtasks detail out the physical activities involved in completing
the project and are not a breakdown of the people doing them. A subtask
represents one of a set of activities that goes into whatever project phase
or module is summarized by the summary task. There certainly may be a
one-to-one correspondence of a task and the resource doing it, in fact that
is one of the ways you can decide how far to decompose the project's work,
but the subtask represents the thing they're doing and not the resource that
is doing it. The position of the taskbar in the Gantt chart represents
when they're doing that particular thing and shows its start and the end,
after which the resource goes home never to do that same task again. He
might repeatedly do other identical tasks with the same name but each
occurance is a different task. MS Project's primary focus is on scheduling
when those various tasks will occur within the overall scope of the project.
Your multiple rates are easily handled with the rate information in the
resource definitions without resorting to creating multiple occurances of
the same resource. After you put in Joe Blow in the resource sheet, double
click on the ID number to the left of his name. In the Resource Information
page that opens there's a costs tab. Clicking that will show you 5 rate
tables designated A through E. When you asssign Joe to a task, you can
switch to the resource usage view and see the day-by-day workhours spread
out on the timeline. It will show the resource name and indented under it
will be the tasks to which he is assigned. Clicking on the ID number
associated with the specific task assignment gives you a details page that
includes which rate table for the resource that should be applied to that
task. In my classes I use an example of filming a movie - Betty's basic
function on our crew is as an assistant director but she can also serve as a
camera operator if needed. Her rate table A shows a standard rate of $25
per hr while rate table B shows $20 per hour. The task is "Shoot scene 3"
and Betty is assigned as one of the resources. If she's acting as an AD,
her assignment details show using rate table A. If she's acting as a second
camera operator, the assignment details will set to show rate table B is to
be applied.
A project is defined as a "time limited undertaking producing a unique
product or result." So far you haven't mentioned having done any analysis
of what that result is to be or breaking down the work into the specific
tasks required to achieve it. From what you've said so far, you don't
really have a project at all. You mentioned, for example, "two people that
are part time and will only work as required, need to spread their hours
somehow." But what work exactly will they do, what will trigger their being
required, how will you know when that requirement has begun or ended? You
need to explicitly define and quantify those variables before you can even
begin to schedule and distribute their work.
As I said before, if you're contracted just to supply manpower for 6 months,
without a clearly defined deliverable resulting from their work, and you're
looking to track their work schedules and report on contract hours by
activity consumed over time, MS Project or any project management
application for that matter is a less than optimal choice.
HTH
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs