J
JimS
I have about a dozen project segments, each running 200-3,000 tasks that are
parts of the same project. They are managed by different managers, and are
somewhat interdependent, but mostly dependent on another project managed in
Primavera P6 offsite.
I need to pull these project schedules together, particularly to identify
their interdependencies, but also to share resources. 90% of the resources
are dedicated to a project segment, but the other 10% are cross-allocated.
Examples:
An engineer is responsible for training and execution of commissioning, but
is also responsible to review and approve others' work from other teams.
I know the absolute best way to handle this is MS Project Server (assuming I
don't want to use Primavera....) I don't think I'm going to have that option,
so I think there are two other options:
1. All the subprojects stored in a single place, with version control and
(hopefully) checkout capability. What I don't know is if this provides for
shared resources and the ability to reschedule the entire project at once. It
does allow each manager to status his/her own project segments without
onerous controls.
2. A single project with subproject heirarchy. This seems onerous in terms
of access by users for progressing, etc. It also has risks that the whole
project could be ruined by a single mistake, however well-intentioned.
If I opt for option 1, and create a "main" project that could, for example,
contain "links" back to the P6 "master" schedule, and contain all the
resources, shared or otherwise, with all the "subprojects" linking back to
it, that would seem ideal. Is that practical? appropriate?
Resources?
parts of the same project. They are managed by different managers, and are
somewhat interdependent, but mostly dependent on another project managed in
Primavera P6 offsite.
I need to pull these project schedules together, particularly to identify
their interdependencies, but also to share resources. 90% of the resources
are dedicated to a project segment, but the other 10% are cross-allocated.
Examples:
An engineer is responsible for training and execution of commissioning, but
is also responsible to review and approve others' work from other teams.
I know the absolute best way to handle this is MS Project Server (assuming I
don't want to use Primavera....) I don't think I'm going to have that option,
so I think there are two other options:
1. All the subprojects stored in a single place, with version control and
(hopefully) checkout capability. What I don't know is if this provides for
shared resources and the ability to reschedule the entire project at once. It
does allow each manager to status his/her own project segments without
onerous controls.
2. A single project with subproject heirarchy. This seems onerous in terms
of access by users for progressing, etc. It also has risks that the whole
project could be ruined by a single mistake, however well-intentioned.
If I opt for option 1, and create a "main" project that could, for example,
contain "links" back to the P6 "master" schedule, and contain all the
resources, shared or otherwise, with all the "subprojects" linking back to
it, that would seem ideal. Is that practical? appropriate?
Resources?