Portfolio listed Project to Actual EPM Project Schedule

[Noel]

Folks,

We currently use EPM 2007 and will be upgrading to Project Server 2010 soon!

Looking for some guidance in what happens when a "concept" (project) moves
from the Portfolio to the actual Project schedule (EPM) in terms of:-

Our requirements for the portfolio optimisation process requires diverse
selection of fields to be populate, upfront to allow the viewing of data, I’m
assuming that this info will come across as project information data?
Is there a limit on how much / many data fields I can have in the Portfolio
environment?
Can I select a pre determined template for this project to use or will it
just pickup the default Global schedule template?

Answers greatly appreciated

 

[Gary L. Chefetz]

Noel:

The 2010 version handles this very differently than 2007. The actual
distinction between a proposed project and an active or accepted project
boils down to "a step in a workflow." One of the more wonderful features of
2010 is that you can define "project types" that connect a Project Template,
a workflow, and Project Site template. You define project types to handle
all sorts of specific project needs. The marriage of workflows, project
templates and project site templates provide you with the ability to create
a cradle-to-grave lifecycle whereby you can control the project from idea
through post-mortem activities.

Yes, you capture this data as project data, but you have all sorts of new
functionality around this as well. You can cause metadata fields to be
filtered by department and controlled manually or through workflow only. I
can't begin to describe the depth of these capabilities in a newsgroup post.
Standup a trial and explore for yourself. You'll be blown away.