J
Just Fun
When using a template file to create the next great project ( a new home), I
want to maximize the use of the tasks and resources that remain the same.
I am moving beyond the use of single project files to using multiple
projects and pools and a master project for reporting. I have read Mike
Glen's articles regarding multiple projects but I don't see anything that
prepares me for the insertion of projects that I create from a template.
What I need to understand is what to expect when I link the new project
(that I derive from the Template Project) to the Resource Pool.
Here's what I have:
MSP 2003 Standard.
The Template File is not linked to the Resource Pool. I have resources in
the Template that are just like the ones in the Pool such as Management;
Construction Admin; Construction Manager; Construction Superintendent; and
others such as Architect, key subcontractors and building authorities.
In the Template File, the tasks that are always the same and assigned to the
resources as usual, represent about 95% of the planning for the new homes we
build. The last 5% are the options or uniquenesses of the home and the
subtle changes to task durations. Rarely does the logic (precedence) change.
While I use the resources in the pool, they sometimes evolve during the
course of several months or several houses (projects). I am fearful of them
getting out of sync with what I have in the Template File that are
pre-assigned to tasks.
Should I be concerned? Are there any caveats? What happens when I link a new
project (made from a template that has resources in it) with the pool that
has similar (the same) resources?
When I link this to a master project, will the resources be duplicated?
In a separate thread I will ask about the process of closing out the project
and un-linking the pool and removing the finished home from the Master
Project. What happens if I want to do reporting on the finished project
after the completion and un-linking of the files? I mention it here just so
that you can see how I expect the entire project life cycle to proceed.
John Hansen
want to maximize the use of the tasks and resources that remain the same.
I am moving beyond the use of single project files to using multiple
projects and pools and a master project for reporting. I have read Mike
Glen's articles regarding multiple projects but I don't see anything that
prepares me for the insertion of projects that I create from a template.
What I need to understand is what to expect when I link the new project
(that I derive from the Template Project) to the Resource Pool.
Here's what I have:
MSP 2003 Standard.
The Template File is not linked to the Resource Pool. I have resources in
the Template that are just like the ones in the Pool such as Management;
Construction Admin; Construction Manager; Construction Superintendent; and
others such as Architect, key subcontractors and building authorities.
In the Template File, the tasks that are always the same and assigned to the
resources as usual, represent about 95% of the planning for the new homes we
build. The last 5% are the options or uniquenesses of the home and the
subtle changes to task durations. Rarely does the logic (precedence) change.
While I use the resources in the pool, they sometimes evolve during the
course of several months or several houses (projects). I am fearful of them
getting out of sync with what I have in the Template File that are
pre-assigned to tasks.
Should I be concerned? Are there any caveats? What happens when I link a new
project (made from a template that has resources in it) with the pool that
has similar (the same) resources?
When I link this to a master project, will the resources be duplicated?
In a separate thread I will ask about the process of closing out the project
and un-linking the pool and removing the finished home from the Master
Project. What happens if I want to do reporting on the finished project
after the completion and un-linking of the files? I mention it here just so
that you can see how I expect the entire project life cycle to proceed.
John Hansen
