Organizing project in server - master/subprojects - milestones

[Jason]

Hi,

We have a huge project plan consisting of tens of thousands of tasks.
I'm trying to figure out what would be the best way to organize this data on
server.
Plan must be in smaller pieces so that responsible persons can check out
their part of the project.
One option is to divide plan in subplans and create a master projects from
them. Doing so leads us for horizontal and vertical
master projects where each subproject is a part of two master projects, is
this a problem? We don't use
enterprice resources in this project.
The other option would be to define a naming-standard for projects and use
filtering options for reporting. Updating progress
would then be more time-consuming since each plan should be updated
separately.

In both options, we need to keep Predessors and Successors between
subprojects.
Is this possible when using sub/master projects? Will dependecies retain
when people start to work on plans?
Does checking in/out of both sub and master plans cause problems?
What about in a situation having separate projects i.e. having own files for
each subprojects but no master plans? Is it possible
to create dependecies between different plans?


For reporting we need several views having milestones-view the most
important.
In PWA, how do you create a milestones view? Is it possible to report
becoming,
completed and missed milestones in Project Center or by implementing
OLAP-cube?

By default, Project Center doesn't show Task Details of subprojects inserted
into Master, instead there's
only subproject's name as a task, is it possible to outdent subproject-tasks
when viewing master project?


Any ideas? Thank You.

 

[Gary L. Chefetz [MVP]]

Jason:

I'm afraid you need more than a newsgroup discussion to tackle this problem
correctly. Some bottom lines:

You're on target with breaking up the plan. It's a must.
Your challenge is how
Master plans are fine for rolling up information, but you must manage the
updates through the individual plans - there's at least a day's discussion
on point alone.
Some combination of all of your ideas will work to deliver your end goal,
but I suggest that you tap into some solid expertise to help you sort it
out.