S
Steve
MSP 2007: I have been using an offline implementation of a master schedule. I
use one schedule called Master Schedule with a few lines of text that serve
as the first two levels of the outline. The third outline level is comprised
of embedded schedules. It looks like this;
+Task
+Subtask
+Embedded subproject 1
+Embedded subproject 2
+Embedded subproject 3
+Task
+Subtask
+Embedded subproject 4
+Embedded subproject 5
+Embedded subproject 6
+Embedded subproject 7
+Task
+Subtask
+Embedded subproject 8
+Embedded subproject 9
+Embedded subproject 10
....And so on.
My company is making a strong push to PWA and now they want my subprojects
on PWA and I am being told that I can only have my subprojects embedded into
one project. I have dabbled with PWA and I actually have a few projects
embedded into more than one project with no problem at all.
We have two groups that need to see my schedules. One group has been using
my 'master schedule' for years and we use it and look at it in detail at
least once a week. We are all in the same office so there is no need for PWA.
The second group is on a larger scale and they are the ones pushing PWA. They
also want my master schedule on PWA. The problem is that they have their own
version of a master schedule that will include one of my subprojects at a
time. They will use all of them, but only one subproject per 'master' because
they cover all departments of the individual projects. My 'master' is all of
the projects for my department. Everything is embedded read only. I don't
understand why there would be a problem embeddeding the projects in more than
one file, other than possibly file integrity, but that is why I have made
them read only. Is there some sort of issue I am unaware of?
use one schedule called Master Schedule with a few lines of text that serve
as the first two levels of the outline. The third outline level is comprised
of embedded schedules. It looks like this;
+Task
+Subtask
+Embedded subproject 1
+Embedded subproject 2
+Embedded subproject 3
+Task
+Subtask
+Embedded subproject 4
+Embedded subproject 5
+Embedded subproject 6
+Embedded subproject 7
+Task
+Subtask
+Embedded subproject 8
+Embedded subproject 9
+Embedded subproject 10
....And so on.
My company is making a strong push to PWA and now they want my subprojects
on PWA and I am being told that I can only have my subprojects embedded into
one project. I have dabbled with PWA and I actually have a few projects
embedded into more than one project with no problem at all.
We have two groups that need to see my schedules. One group has been using
my 'master schedule' for years and we use it and look at it in detail at
least once a week. We are all in the same office so there is no need for PWA.
The second group is on a larger scale and they are the ones pushing PWA. They
also want my master schedule on PWA. The problem is that they have their own
version of a master schedule that will include one of my subprojects at a
time. They will use all of them, but only one subproject per 'master' because
they cover all departments of the individual projects. My 'master' is all of
the projects for my department. Everything is embedded read only. I don't
understand why there would be a problem embeddeding the projects in more than
one file, other than possibly file integrity, but that is why I have made
them read only. Is there some sort of issue I am unaware of?