Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Links between multiple projects

7 replies [Last post]
Thu, 2007-09-20 06:37
Bob Foden
User offline. Last seen 7 years 2 weeks ago. Offline
Joined: 20 Sep 2007
Posts: 33
Groups: None
Hello all. I’m a virgin to the site so bear with me if I contravene any protocols.

The problem I have is that my client does not want to invest in MSP Server but I have to manage a number of separate plans. These have logic links between them. When I make a change to a plan name (ie revision update) I then lose the links (not unsurprisingly). Is there a way to get MSP to easily recognise the changes or, preferably automatically make them ?

Thanks

Bob
Top

Replies

Fri, 2007-10-05 03:52
#1
Bob Foden
User offline. Last seen 7 years 2 weeks ago. Offline
Joined: 20 Sep 2007
Posts: 33
Groups: None
Tony,

Thanks for that. It pretty much mirrors what I’ve ended up doing so at least I now have some confidence that I’ve got the best (?) solution.

Bob
Top
Tue, 2007-10-02 08:25
#2
Tony McClennon
User offline. Last seen 10 weeks 6 days ago. Offline
Joined: 19 Nov 2002
Posts: 97
Groups: None
Bob,

On one of our programmes, we have the same issue.

What I have done is to ensure that the sub-projects always keeps the same file name (e.g. ProjectXXXX_Master.mpp) and is stored in the same location. At issue, it is given an issue and revision reference (e.g. Issue 01 Rev 01) but only within the header or footer, not in the file name.

When the schedule is updated, first of all the user saves a copy of the file as ProjectXXXX_Iss01_Rev01.mpp, which effectively gives an archive copy. The Master file then has it’s header updated to show Issue 01 Rev 02 (or whatever convention is used).

In this way, each issue of the schedule can be identified by it’s unique Issue/Revision reference, whilst the links from the master schedule will always link to the file named ProjectXXXX_Master.mpp.

Hope this is of help.
Top
Thu, 2007-09-20 10:00
#3
Nicolas Igersheim
User offline. Last seen 7 years 15 weeks ago. Offline
Joined: 25 Jun 2007
Posts: 62
Groups: Petro-Chem / Oil & Gas
Hi all,

Further to what Alexandre suggests


I would open and "save as" using always the same
name and location each and every project.
this way links should not be broken

hth
Top
Thu, 2007-09-20 09:16
#4
Bob Foden
User offline. Last seen 7 years 2 weeks ago. Offline
Joined: 20 Sep 2007
Posts: 33
Groups: None
Alexandre,

Thanks for your response. Each plan has a separate owner and they amend their own plans so I want to restrict each plan to just their relevant content.

Bob
Top
Thu, 2007-09-20 06:45
#5
Stephen Grady
User offline. Last seen 16 years 44 weeks ago. Offline
Joined: 13 Aug 2003
Posts: 6
Groups: None
Hi Bob,

Might I suggest convincing your client to purchase Primavera?

There are enterprise packages available which would eliminate the problem of loosing your logic links and enable you to successfully manage multiple projects from a single enterprise.

Failing this, good luck with your quest for a solution within MSP.

Regards

Steve
Top