This dynamic causes reporting against the analysis data to be challenging at times. On preliminary examination, much of the analysis data resides in the Reporting database, but some of the critical data such as project dependency data appears to be maintained only in the Publishing database. Reporting on Portfolio Analysis is a topic for another paper. The user should treat the Portfolio Analysis module as a virtual sandbox to test various scenarios. Those scenarios, such as revised cost constraints, adjusted start dates, and the incremental addition of resources do not affect the actual project data stored in Project Server. Some organizations will opt to develop custom workflow to push those data points into project schedules, but in the absence of such workflow, none of those scenarios will actually affect the project schedules saved in Project Server. Figure : Project Server Data Schema The one exception to this rule is that when the user clicks on the Commit button, up to six specific project level fields will be populated. These fields will not change the schedule in any way. For more information on committing specific scenarios, refer to page 120 of this document. Terminology Overview A “project portfolio” is usually defined as a centralized collection of projects managed jointly to enhance advantages to the organization or to minimize risk. From a technical standpoint, within Project Server 2010, a portfolio of projects should be defined as a set of projects that share the same cost or resource constraints. Users of Project Portfolio Server 2007 may get confused by the use of terminology within this document. To clarify, the Portfolio Analysis module is a component of Project Server 2010. Within the Portfolio Analysis module are two primary functions: Cost Analysis and Resource Analysis. These two functions roughly correlate to Microsoft Project Portfolio Server 2007 as follows: 2007 Terminology 2010 Terminology Project Portfolio Server 2007 Portfolio Analysis Module Portfolio Optimizer Cost Analysis Function Portfolio Planner Resource Analysis Function (also referred to as Schedule Analysis) Table : PPM Terminology Changes
This dynamic causes reporting against the analysis data to be challenging at times. On preliminary examination, much of the analysis data resides in the Reporting database, but some of the critical data such as project dependency data appears to be maintained only in the Publishing database. Reporting on Portfolio Analysis is a topic for another paper. The user should treat the Portfolio Analysis module as a virtual sandbox to test various scenarios. Those scenarios, such as revised cost constraints, adjusted start dates, and the incremental addition of resources do not affect the actual project data stored in Project Server. Some organizations will opt to develop custom workflow to push those data points into project schedules, but in the absence of such workflow, none of those scenarios will actually affect the project schedules saved in Project Server. Figure : Project Server Data Schema The one exception to this rule is that when the user clicks on the Commit button, up to six specific project level fields will be populated. These fields will not change the schedule in any way. For more information on committing specific scenarios, refer to page 120 of this document. Terminology Overview A “project portfolio” is usually defined as a centralized collection of projects managed jointly to enhance advantages to the organization or to minimize risk. From a technical standpoint, within Project Server 2010, a portfolio of projects should be defined as a set of projects that share the same cost or resource constraints. Users of Project Portfolio Server 2007 may get confused by the use of terminology within this document. To clarify, the Portfolio Analysis module is a component of Project Server 2010. Within the Portfolio Analysis module are two primary functions: Cost Analysis and Resource Analysis. These two functions roughly correlate to Microsoft Project Portfolio Server 2007 as follows: 2007 Terminology 2010 Terminology Project Portfolio Server 2007 Portfolio Analysis Module Portfolio Optimizer Cost Analysis Function Portfolio Planner Resource Analysis Function (also referred to as Schedule Analysis) Table : PPM Terminology Changes