C
Coop
We thought a simple approach to initially implement would be best. We have
tasks, whose finish and start dates are strictly driven by asap dependencies
and durations (at least that is our intent). Where we have hard dates, we
implemented the deadline feature to handle so MSProject would not change the
way it calculates. We also had to add the resources we expected to be able
to access the MSProject version of the schedule (vs. web), so we handled that
by having one task at the end of the schedule with those folks identified in
'resource name' (not sure if this is contributing to a problem). The only
other field we leverage is 'enterprise text 1' to hold the role name of the
intented 'doer', but that should be okay I think. But we have the following
anomalies we cannot explain/fix. We feel as though they may be related and
may have something to do with high level settings that we have set
incorrectly based on our approach (not sure if this is at the enterprise
level or perhaps the review Calculation or Schedule tabs under
tools/options). Any help would be much appreciated. Problems are as follows:
-the status does not reflect properly i.e. Late, on Schedule, future, etc.
This is a real problem for us because we were hoping to use this field to
communicate Red, Yellow, Green to our execs.
-some durations we can change, some not...Wizard tells us we are creating a
schedule conflict - not sure why, as again, we only have asap constraints
Again, I am not clear that we have the proper 'switches' set based on the
simple approach we are taking (described above).
In the Schedule Options, we have
fixed units checked - doesnt seem like this should matter based on approach?
split in progress checked - seems like we want this
Tasks will honor constraints - seems like it wouldn't matter?
the two durations are estimates fields - not sure why that would be a problem?
In the Calculation Options, we have
Updating task status updates resource status checked - shouldn't matter?
Inserted projects calculated like summary checked - fine?
actual costs calculated by MSProj checked - shouldn't matter?
Hoping those out there with more experience than I might know of something
or point me somewhere.
I have been reading up on work and units (those terms come up alot)...seems
as though they are only important if you are using resources???
tasks, whose finish and start dates are strictly driven by asap dependencies
and durations (at least that is our intent). Where we have hard dates, we
implemented the deadline feature to handle so MSProject would not change the
way it calculates. We also had to add the resources we expected to be able
to access the MSProject version of the schedule (vs. web), so we handled that
by having one task at the end of the schedule with those folks identified in
'resource name' (not sure if this is contributing to a problem). The only
other field we leverage is 'enterprise text 1' to hold the role name of the
intented 'doer', but that should be okay I think. But we have the following
anomalies we cannot explain/fix. We feel as though they may be related and
may have something to do with high level settings that we have set
incorrectly based on our approach (not sure if this is at the enterprise
level or perhaps the review Calculation or Schedule tabs under
tools/options). Any help would be much appreciated. Problems are as follows:
-the status does not reflect properly i.e. Late, on Schedule, future, etc.
This is a real problem for us because we were hoping to use this field to
communicate Red, Yellow, Green to our execs.
-some durations we can change, some not...Wizard tells us we are creating a
schedule conflict - not sure why, as again, we only have asap constraints
Again, I am not clear that we have the proper 'switches' set based on the
simple approach we are taking (described above).
In the Schedule Options, we have
fixed units checked - doesnt seem like this should matter based on approach?
split in progress checked - seems like we want this
Tasks will honor constraints - seems like it wouldn't matter?
the two durations are estimates fields - not sure why that would be a problem?
In the Calculation Options, we have
Updating task status updates resource status checked - shouldn't matter?
Inserted projects calculated like summary checked - fine?
actual costs calculated by MSProj checked - shouldn't matter?
Hoping those out there with more experience than I might know of something
or point me somewhere.
I have been reading up on work and units (those terms come up alot)...seems
as though they are only important if you are using resources???
