Linking across projects

[Karen]

I want to compare two projects to see if certain experiments are scheduled
for the same day. If so, it needs to be changed. WIll linking across projects
help me to achieve this? I have over 60 projects to track so being able to
view conflicts is very important. If not use linking, what else should I try?

 

[John]

I want to compare two projects to see if certain experiments are scheduled
for the same day. If so, it needs to be changed. WIll linking across projects
help me to achieve this? I have over 60 projects to track so being able to
view conflicts is very important. If not use linking, what else should I try?

Karen,
Comparing and linking are two completely different concepts. Comparing
is normally used to detect changes that have occurred between two
version of a project file (e.g. last month's version versus this month's
version). On the other hand linking is used to dynamically connect tasks
in one file with those of another. For example, one file might represent
tasks performed by a design function and another file might represent
tasks performed by a build and test group. There is likely to be
"handoff" of tasks between the two files. Cross-project linking is one
method of setting up the "handoff".

In your case, I would suggest that all the experiments be laid out in a
single project file. Concurrency of those experiments may be impacted by
several factors. For example, equipment and facilities may be limited,
or resources to perform the experiments may be limited and dealing with
the potential overlap may require different approaches.

John
Project MVP

 

[Karen]

I currently have all of the projects in one file but it is rather cumbersome
to try and make sure there are no conflicts. I was hoping to find something
to help me with that. Thank you for your response.

 

[John]

I currently have all of the projects in one file but it is rather cumbersome
to try and make sure there are no conflicts. I was hoping to find something
to help me with that. Thank you for your response.

Karen,
I'm a little confused. Your original post said you wanted to compare two
projects but your latest post says everything is all in one file. What
exactly do you have?

As far as conflicts, what exactly are your looking for? How are you
checking for conflicts?

I'm sure we can help you out. We just need to understand what you have
and your end goal.

John
Project MVP

 

[Karen]

I have 60 projects in one master project file. I'd like to be able to tell:

1)If isotopes being produced (between projects) are falling on the same day,
then I have to reschedule. I would like to be able to tell at a glance which
projects have the same task falling on the same day. The production of
isotopes can only be done once a day and no others can be done for any other
projects.

2) same for similar types of tasks across multiple projects.

Is that any better? I think my wording is a problem because I didn't know
compare was a function in Project.

 

[John]

I have 60 projects in one master project file. I'd like to be able to tell:

1)If isotopes being produced (between projects) are falling on the same day,
then I have to reschedule. I would like to be able to tell at a glance which
projects have the same task falling on the same day. The production of
isotopes can only be done once a day and no others can be done for any other
projects.

2) same for similar types of tasks across multiple projects.

Is that any better? I think my wording is a problem because I didn't know
compare was a function in Project.

Karen,
Project has a utility called "Compare Project versions" - that's where
the compare concept comes from. Although just for reference, that
utility does not work with consolidated master files.

Your best bet might be to set up a time based filter, (take a look at
the built in Date Range filter), so you can easily isolate all tasks
during a certain time period (e.g. a given day) in the master. Then you
can re-schedule as necessary to avoid the conflicts.

As an alternate to the Date Range filter, you could use a spare number
or flag field to designate those tasks that have potential conflicts.
Filtering on the field will quickly isolate tasks of interest.

John
Project MVP