Rollup/Consolidation Strategy Recommendations

[Dean]

We are planning a Construction Program that may have several hundred
individual projects. Each of these projects will be very similar with just
the location changing. The same people will be working on all of the
projects. I see several options:
1. Create one big file in Project Pro 2002 for uploading to PWA 2002. If we
do this, at what point do we need to be concerned about performance issues
due to large numbers of tasks in the file?
2. Create hundreds of similar Project files, upload and link together to get
a master view
3. Some other approach that is recommended by others

Any thoughts, suggestions, recommendations, and/or words of warning would be
greatly appreciated.

TIA
dean

 

[Gaurav Wason]

How many task are thinking to add in each project?
How Many Projects?

I can warn you regarding the linking as it tries to open all the project (In
background) that does makes the system run slow and much worse in performance
than master project.

Are all the projects that you have dependent on each other.
--
Gaurav Wason
(e-mail address removed)
MCP - Project Server
Project Made Easy
http://projectmadeeasy.com

 

[Dean]

about 150 tasks per project, and 100-200 projects for a total of 15,000 to
30,000 tasks.