Confused about offerings

[Kerry Purdy]

Hi,
With Project 2003 I had a basic understanding of the difference between
standard and professional with server (communication through emails, outlook
calendars & tasks lists etc.)
With Project 2007 EPM solution I am quite confused about all of the
offerings. Different titles/terminology is used, even on the MS website.
This is my understanding and my confusions, I would be so very grateful if
someone could help me out please.
EPM is the top level title of offerings, EPM consists of Project Server, Web
Access (licence required for each client wishing to access the project files
of site - they do need Microsoft project pro installed), Portfolio server
(align projects with business strategies) and portfolio web access (again to
view files off-site with having project installed, licence required for each
user).
Companies have to have Project Professional and project server as a base.
They can then decide to:-
(1) keep just pro and server (resource communication can be managed through
their outlook accounts, calendar and tasks lists and emails are fired/updated
automatically(
(2) + web access (as above but additionally allowing clients to view the
project file off-site with having to install Microsoft project)
(3) + portfolio server (resource communication and align projects with the
company business strategies)
(4) + portfolio server & portfolio web access (as above with the additional
option of off-site access)
This is where i now get really really stuck, (if i have even got it right so
far!) are all of these options together called the EPM Solution? Where does
the automatic SharePoint connectivity come in, with the project file, related
documents etc being stored in a sharepoint site. Which bit controls the
timesheets. Very confused.
Whilst mentioning SharePoint, I guess you could also use a standard
sharepoint site as just storage and manually add the project file, related
documents, announcements and contacts etc. you could do this even with
Project standard, just using a sharepoint site as a storage facility.
Also, there is a sharepoint site which can be used as a project planner
without even having microsoft project, shows a gantt chart and a calendar and
a task list, no links if memory serves me correctly - a basic offering for
simple projects.
Thank you so much for your help.
Kerry

 

[Andrew Lavinsky]

It's still pretty much the same model as in 2003.

You have the client, Standard and Professional, with Professional providing
the tie-ins to the server product.
You have Project Server (which includes PWA)

Project Server then sits on top of SharePoint. SharePoint comes in two flavors:

WSS: Basic, free
MOSS: The enhanced version of WSS, not free

So you need to pick which version of SharePoint you would like to go with
when implementing Project Server. WSS provides basic collaboration services
and may be good enough for your needs. You will need a Project Server Client
Access License for each user accessing project data via Project Server -
and each Professional license comes with a CAL.

Portfolio Server is a (relatively) newer product in the mix, which provides
tools to develop business cases and identify the optimal portfolio of projects,
ROI, etc. Portfolio Server is not required for either the client or the
Project Server to work, but provides additional functionality to the stack.

All of those products are referred to as "EPM"

if you are seriously considering going with the EPM stack, I would highly
recommend you contact a consulting shop and/or your Microsoft license representative.
They'll be able to clarify all of this.

Does that help?

-A

 

[Dale Howard [MVP]]

Andrew --

That was an entirely thorough and cogent explanation of the Microsoft EPM
solution. Thanks for sharing it with Kerry!

 

[Kerry Purdy]

Fab, thanks very much.

Kerry.

It's still pretty much the same model as in 2003.

You have the client, Standard and Professional, with Professional providing
the tie-ins to the server product.
You have Project Server (which includes PWA)

Project Server then sits on top of SharePoint. SharePoint comes in two flavors:

WSS: Basic, free
MOSS: The enhanced version of WSS, not free

So you need to pick which version of SharePoint you would like to go with
when implementing Project Server. WSS provides basic collaboration services
and may be good enough for your needs. You will need a Project Server Client
Access License for each user accessing project data via Project Server -
and each Professional license comes with a CAL.

Portfolio Server is a (relatively) newer product in the mix, which provides
tools to develop business cases and identify the optimal portfolio of projects,
ROI, etc. Portfolio Server is not required for either the client or the
Project Server to work, but provides additional functionality to the stack.

All of those products are referred to as "EPM"

if you are seriously considering going with the EPM stack, I would highly
recommend you contact a consulting shop and/or your Microsoft license representative.
They'll be able to clarify all of this.

Does that help?

-A

 

[Kerry Purdy]

Hi Andrew,

Other than the Sharepoint clarification was i about on the mark??

Kerry.

 

[Andrew Lavinsky]

I think so.....

Hi Andrew,

Other than the Sharepoint clarification was i about on the mark??

Kerry.

 

[Steve]

Just for the record...

Project Server runs on top of WSS, not MOSS 2007. When you install MOSS, you
get WSS, or you can load it separately for free.

Here is a complete list of requirements:
http://office.microsoft.com/en-us/epmsolution/FX101662321033.aspx

HTH