Difference between project versions

[Marc Daoust]

Can anyone help as to what exactly is the difference between a .published
project and a .target, or .archive, etc type project.

Thanks

Marc

 

[Gary L. Chefetz \(MVP\)]

Marc:

Any version other than <dot>published is a user defined snapshot-in-time
version of a project captured by a Project manager. PS Administrators define
the version extensions allowed on the server, and users avail themselves to
these at will.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-

 

[Marc]

Hello Gary,

WhatI am looking for would be more on the lines of; what are the potential impacts if any when using different versions of the same project? Do the resources get counted in double?

Thanks
Marc

 

[Gary L. Chefetz \(MVP\)]

Marc:

Only the published version is considered for resource demand and allocation

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-

Hello Gary,

WhatI am looking for would be more on the lines of; what are the potential

impacts if any when using different versions of the same project? Do the
resources get counted in double?

 

[Stephen Eyton-Jones]

Hi Gary...I'd like to expand on this....

So, if I take that one step further, and create a version called .master and create a master project with all the linked projects now 'internalized' (all data in the project) into the master and save it into the Server and publish it as a .master, can I then have access to a master project that I can view and work with in views and assure myself that they will not double count my resources or be considered for resourcing? I would redo this linking and saving process monthly (probably save a shell of the linked project(s)) and saving as an all in one project as a snapshot of the current master plan that we would report from for that month. The key is in being sure I don't mess up the resource assignments etc.
I realize that I could likley do the same in an MPP file but that data would not be available to PWA users, which is my goal.

What do you think?

Steve

 

[Gary L. Chefetz \(MVP\)]

Stephen:

I don't know about saving versions of Master Plans; if the system allows it,
or what you might get out of it. I don't think it makes sense in the Project
Server environment. Master projects do not contain the details of the
subprojects, so there's little value that isn't easily exceeded by using a
baseline.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-

Hi Gary...I'd like to expand on this....

So, if I take that one step further, and create a version called .master

and create a master project with all the linked projects now 'internalized'
(all data in the project) into the master and save it into the Server and
publish it as a .master, can I then have access to a master project that I
can view and work with in views and assure myself that they will not double
count my resources or be considered for resourcing? I would redo this
linking and saving process monthly (probably save a shell of the linked
project(s)) and saving as an all in one project as a snapshot of the current
master plan that we would report from for that month. The key is in being
sure I don't mess up the resource assignments etc.

I realize that I could likley do the same in an MPP file but that data

would not be available to PWA users, which is my goal.